> Ok,
>
> Thought about this a bit more.
>
> The Perl script would query the Cobbler server, if it find a machine
with
> a certain "tag" such as Virt Type = VirtualCenter or whatever, it
will then
> check if a MAC has been assigned. If no MAC is assigned, it would
then
> send a request to VirtualCenter to create the VM, which would then in
turn
> return the MAC address. It would then update the Cobbler profile for
the server
> with the MAC address, power on the server, and let the auto build
start.
>
I think I like this, though it would be nice to just be able to specify
a specific system to vivify as well.
I'll start out with a basic script, just input device name and it'll go
from there. The fancy stuff can come later ..
> This could be either daemonized or ran how ever often from cron,
with
the idea
> of it being seamless .. Just let it handle all the backend
communication with
> the VirtualCenter server and manage everything else in Cobbler.
>
> Question would be, would I want to add another "Virt Type" to Cobbler
with
> something like "ESX", or would I want to just add something in the
Comments
> that could be parsed out?
>
Making an ESX virt type is good sense, I think.
There was some talk earlier of trying to just have one common VMware
virt type (ESX+server+workstation though I'm not certain
this makes sense).
I'm not sure about the server/workstation stuff and I'm pretty sure that
the perl dev kit doesn't interface with either of those. A separate ESX
type would make more sense, as it can either be a direct connection to a
single ESX server, or the VirtualCenter server. API is the same ..
So should I just pull down the latest dev tree and go ahead and try to
add the type? I got the stable branch installed in my lab ATM ..