Greetings,
I'm using the Genome project ( http://fedorahosted.org/genome ) to manage a set of VMs. Genome uses Cobbler's XMPRPC API to create a profile for a system before using Koan to create the system.
Recently I upgraded to Cobbler 1.6.3. Afterwards, machines that were Koan'ed were unable to download their kickstart files. It turns out that the Cobbler system profile for those machines did not have a network interface configured. Previously, in Cobbler 1.1.1, an interface was configured by default.
Is there anyway to edit a profile such that all systems descended from it will have a network interface already configured? Otherwise, the alternative is me having to patch the XMLRPC calls in Genome to create the interface when the system is created. ------------------ Regards, Alex Wood
Alex Wood wrote:
Greetings,
I'm using the Genome project ( http://fedorahosted.org/genome ) to manage a set of VMs. Genome uses Cobbler's XMPRPC API to create a profile for a system before using Koan to create the system.
Recently I upgraded to Cobbler 1.6.3. Afterwards, machines that were Koan'ed were unable to download their kickstart files. It turns out that the Cobbler system profile for those machines did not have a network interface configured. Previously, in Cobbler 1.1.1, an interface was configured by default.
VMs created with system records need to explicitly add one, this is intended. There are internals reasons for not creating an "eth0" by default, and these spill over into the virt space.
If you koan by profile, you'll get an interface for free.
Is there anyway to edit a profile such that all systems descended from it will have a network interface already configured? Otherwise, the alternative is me having to patch the XMLRPC calls in Genome to create the interface when the system is created.
Yes, you need to fix Genome to where it creates at least one interface.
Regards, Alex Wood
Is there anyway to edit a profile such that all systems descended from it will have a network interface already configured? Otherwise, the alternative is me having to patch the XMLRPC calls in Genome to create the interface when the system is created.
Yes, you need to fix Genome to where it creates at least one interface.
Just as a follow-up, would such a change be backwards-compatible with older cobbler versions (say 1.1.1 and above)? -------------- Regards, Alex
Alex Wood wrote:
Is there anyway to edit a profile such that all systems descended from it will have a network interface already configured? Otherwise, the alternative is me having to patch the XMLRPC calls in Genome to create the interface when the system is created.
Yes, you need to fix Genome to where it creates at least one interface.
Just as a follow-up, would such a change be backwards-compatible with older cobbler versions (say 1.1.1 and above)?
Regards, Alex
Network interface handling has changed a lot sense then, but the APIs should be compatible. I say should because I haven't tested it. I'm pretty sure it would be fine with 1.4.X.
Still, I should caution you -- 1.1 was just a development build (odd number). It's also 10 months old -- so you are missing a ton of bugfixes.
http://git.fedorahosted.org/git/cobbler?p=cobbler;a=blob_plain;f=CHANGELOG;h...
1.6.4 comes out tomorrow. Perhaps time to schedule an upgrade to make things consistent.
--Michael
cobbler@lists.fedorahosted.org
-
Alex Wood -
Michael DeHaan