John Eckersberg wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
First and foremost, the bonding stuff discussed today sounds great and
is something that I'd be interested in helping with and using.
Before we dig too far into that, however, I want to post up something
I've been meaning to finish for the past month or so but just haven't
had the time to flesh it out completely. I'd like to get it applied
(assuming others think it's a good patch :D) before we go tearing up the
interface code even more.
The attached patch adds support for generic interface names, and as a
side-effect allows an arbitrary number of interfaces to be assigned to a
system. This work looks to be a pre-requisite for the bonding examples
anyways, so it should prove useful.
More information is available in the commit log of the patch.
As always, suggestions / gripes / feedback / patches are welcome!
- --
John Eckersberg
Systems Administrator, CIS
Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org
iEYEARECAAYFAkjZlPIACgkQdxt4pd4ztYuBegCfTgcny9hdoLovwWD/UU+QPOwW
QBEAoICMHcU/ji+0teuihbNitB1Pwr+k
=ZuJ9
-----END PGP SIGNATURE-----
------------------------------------------------------------------------
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
Comments:
-- Make test runs clean and general edit commands seem to work fine.
-- I had to modify the network_config snippet we're shipping Cobbler 1.3
to set up the network parts of kickstart (does not do %post config) to
be compatible. This is a new feature and the change was simple, so
that's not too bad. It also makes the "post network config" snippet on
the Wiki incompatible though since we are thinking about including that
in Cobbler also (per recent emails) that's not a problem.
-- Are you planning on adding the multiple interface views to the
webapp, or is that something I need to look into? Either way we should
add an item to Trac with "blocker" status on that one and get that done
for 1.3.
Being able to use arbitrary names for the interfaces is definitely a
bonus. I think it would be fine to simplify and call things "eth0"
though the reason we don't now is because we do not have the
post_network_config snippet in place to ensure the first interface
actually /is/ eth0. We are now using ipappend 2 and such, so this
should be possible in the future. If we include a post_network_config
setup tool that populates /etc/sysconfig/network in %post, then I think
we can simplify and name the default interface eth0. In which case, we
probably /also/ want to add code to auto-rename any "intf0" interfaces
to "eth0" and such as well. Since we are at a development point in the
code, we /can/ do this. Thoughts?
This would mean --interface=X would either take ethN or bondN, if we
also support the bonding case, as opposed to a freeform string.
Either way, this is applied and will be pushed shortly, and I'm opening
a Trac item on the webapp so we don't forget it.
--Michael