Matthias Saou wrote:
Michael DeHaan wrote :
Cobbler is designed for central configuration, so it can be your MAC
database.
Can it really? For Xen guests?
Yes.
koan --virt --system=AA:BB:CC:DD:EE:FF --server=cobbler.example.org
I've played some more with Koan and Xen guests, but apparently even
telling Koan to install a system which has a specific MAC address in
its Cobbler system details creates the Xen guest file with a random MAC
address.
What cobbler and koan version is this?
My DHCP server has only static entries, which means that if
Koan used the MAC address I've put in the Cobbler system it would work,
but the random MAC address won't ever be able to get an IP address (and
this corporate network _must_ stay this way).
Using Koan's "--display", it does seem like the MAC address isn't
obtained from Cobbler.
Am I maybe simply doing something wrong?
On a related note, I do see "virt_path" and "virt_type" in the Cobbler
systems, but I don't see "virt_ram", which would be very useful to be
able to set on a per-system basis in my case.
Conceptually, profiles are there to describe what the purpose of the
system is and it's requirements.
If a profile states that a configuration needs "X" amount of RAM, it is
important to honor that.
The overrides on storage are for cases such as a development profile
being created centrally, and the local user
wanting to install it in a different location (for instance, say they
had a large partition on the domU they wanted
to use).
Overriding the amount of virtual RAM on the koan command line is
possible, but we do not want folks
thinking of RAM requirements for individual systems because that defeats
the point of the profile
abstraction.
Matthias
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
