Hi,
Thanks for the thoughts all. What would really help would be a
disussion on if you are deploying to vmware, here are the pieces,
steps and process for getting your first VM up. The docs are a bit
thin on the details. Has anyone working this wwritten or started the
howto? Noted the caviares,etc? In reading the current wiki I am still
a bit unclear on how to get my devel team going.
Thanks,
Aaron Lippod
lippold(a)gmail.com
AIM/YAHOO: aaronlippold
On Oct 30, 2008, at 18:43, Michael DeHaan <mdehaan(a)redhat.com> wrote:
Rob Crittenden wrote:
> Aaron Lippold wrote:
>
>> Hello,
>>
>> I was hoping some of the folks working the VMWare Cobbler
>> integration
>> could chat a little on the general work flow for creating VMWare
>> target profiles and how a development team would collaborate on
>> developing them. I have a team now working to develop a set of
>> profiles targeted at VMWare as the host and was hoping the list
>> could
>> help just start the team.
>>
>> The wiki seems a little sparse on what is supported, how to utilize
>> what is supported and what the development road map is.
>>
>> Thanks,
>>
>> Aaron
>>
>
> I worked on the VMWare Workstation support a bit and the thing that
> is
> going to stand in your way whether using Server or Workstation is the
> MAC address. In order to do a PXE boot, cobbler needs to do the MAC
> assignment in the profile so it can write the proper PXE config file.
>
> Cobbler is currently hardcoded to use the Xen MAC address range which
> will not work with VMWare. If you try to pass a non-VMWare address
> space
> it will ignore it and generate its own meaning that the PXE boot will
> fail (because it can't find the config file).
>
FWIW, I have an RFE open on this... based on the --virt-type, have the
"random" mac feature pull an unused MAC range from the available pool,
in the VMware range for VMware, in the Xen range for Xen, etc.
Koan will need similar logic, so it probably also needs to be an
XMLRPC
call.
Until then the workaround is to know the range and manually add a
MAC in
the range.
--Michael
> On my system I simply replaced a function in the cobbler code but
> this
> is hardly portable.
>
> I'm not sure what kind of profile configuration you are looking to
> do. I
> didn't mess around with custom variables in the ks files but I'm
> assuming those will work the same as with any of the other virt
> types.
>
> The vmx file for VMWare is a bit hardcoded presently, limiting you to
> configuring just 1 disk, available RAM, the MAC address and system
> name
> (as far as VMWare is concerned).
>
> Workstation has a few more options but for example, it assumes you
> are
> only installing Linux and picks the most generic setting it can.
>
> I've fiddled with it about as much as I'm going to. It works ok for
> me
> and I can live with the current idiosyncrasies.
>
> rob
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler