12:34 a.m.
Thanks Greg,
this has been discussed before and IIRC the theory is that the
scripts deal w/ whatever you name the interface when you add it to
the system. If you add an interface named 'em1' it would configure
and interface 'em1', just like for 'eth0'.
I will review these network configuration related snippets more
carefully, and then redo my tests. During my today's tests, for
simplicity, I simply used a --kopts to disable the behavior.
[...]
Regards,
-- Zack
1:07 p.m.
New subject: cobbler 2.4.0, Fedora 17, eth0 and em1
Thanks Greg,
> this has been discussed before and IIRC the theory is
> that the scripts deal w/ whatever you name the interface when
> you add it to the system. If you add an interface named 'em1' it
> would configure and interface 'em1', just like for 'eth0'.
I will review these network configuration related snippets
more carefully, and then redo my tests. During my today's tests,
for simplicity, I simply used a --kopts to disable the
behavior.
I just did a quick test. I confirmed your hints with
0. cobbler system getks --name=...
1. cobbler system dumpvars --name=...
The only issue that I encountered so far is that with an existing
system object, I can't change the Interface attribute with --interface=em1.
I had to first delete said system object, and recreate one with a
'cobbler system add'. Is there a quicker way to do such modification?
At work, we deal with CentOS 6.x, SL 6.x, Fedora 17, and Ubuntu
{11.10..12.10} - mostly KVM guests running on hosts using RHEL.
I can script the above, but even with scripting, having the ability
to quickly change interface name should come handy.
Regards,
-- Zack
1:17 p.m.
New subject: cobbler 2.4.0, Fedora 17, eth0 and em1
unfortunately i think the work flow is:
cobbler system edit --name=foo --interface=eth0 --delete-interface
cobbler system edit --name=foo --interface=em1 --ip-address= blahblahblah
-greg
1:30 p.m.
New subject: cobbler 2.4.0, Fedora 17, eth0 and em1
I was really struggling with this until I did an rpm -e biosdevname, and
all my devices are named eth0 like they used to be now. Cobbler dealt with
the device names just fine, but Puppet was having no end of trouble.
On Tue, Nov 20, 2012 at 2:17 PM, Greg Swift <gregswift(a)gmail.com> wrote:
unfortunately i think the work flow is:
cobbler system edit --name=foo --interface=eth0 --delete-interface
cobbler system edit --name=foo --interface=em1 --ip-address= blahblahblah
-greg
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
--
Bret Wortman
The Damascus Group
Fairfax, VA
http://bretwortman.com/
http://twitter.com/BretWortman
1:42 p.m.
New subject: cobbler 2.4.0, Fedora 17, eth0 and em1
Gentlemen, thanks for your feedback. Yes. I am aware of the fact that many people are not
happy with the change. But actually it's the scheme that was used by SunOS/Solaris
for many years.
I am agnostic about such a change. We can't change a vendor's product decision,
so we just go with it.
Regards,
-- Zack
I was really struggling with this until I did an rpm -e biosdevname, and all my devices
are named eth0 like they used to be now. Cobbler dealt with the device names just fine,
but Puppet was having no end of trouble.
unfortunately i think the work flow is:
cobbler system edit --name=foo --interface=eth0 --delete-interface
cobbler system edit --name=foo --interface=em1 --ip-address= blahblahblah
-greg
4200
days inactive
4200
days old
cobbler@lists.fedorahosted.org
4 comments
3 participants
participants (3)
-
Bret Wortman -
Greg Swift -
Zack Perry