Dave Hatton wrote:
Joseph, Michael
I'm the first to admit my python skills aren't great, so I'm pleased
to see an improvements.
I have made some updates to the updates that Dave H had made to the
action_buildiso.py.
Here is the list of my updates: (P.S. I am new to python so if my
coding sucks, please bear with me)
1. reordered the build iso menu so that systems are first.
How about second with a seperator between the profiles and the
systems, or otherwise a 2-level menu that lets you pick first
"profiles" or "systems"?
I really like seing the profiles on the CD as well as the system. This
allows me to carry out some diagnostics against the profiles if I
screw up the systems entries.
I'd be please to see what the code looked like to have a two level
menu - if only as a selfish learning exercise.
Yeah, that can get a little bit complicated with syslinux, ideally if we
don't do that I'd like to see the profiles, a seperator, and then the
systems.
2. Did not understand why we rely on DHCP when you have a "System".
So I have added the networking information to the kernel line for
systems, thus eliminating the need for DHCP. (This is what I needed
in the boot iso).
This sounds good.
I think this is my poor understanding of how this works. I didn't want
to rely on dhcp either - I just couldn't workout how to append an IP
address. This answers for me a problem I saw today.
Right. If the system has the ip and other network info defined, we can
add the kernel arguments for that on the end of the append line if that
does not take the length of the append line to more than 255.
Should the broadcast address be added as well? For completeness?
Not required AFAIK.
Dave
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
