I have some pretty good experience with the api. I have code to do
the following tasks.
1. Power control
2. Change portgroup
3. Find and change guest Id given cobbler profile name
4. Cloning
5. Create VM
Sent from my iPhone
On Apr 3, 2009, at 12:08 PM, Jeff Schroeder <jeffschroed(a)gmail.com>
wrote:
On Fri, Apr 3, 2009 at 8:34 AM, Michael DeHaan
<mdehaan(a)redhat.com>
wrote:
> Scott Henson wrote:
>> Jasper Capel wrote:
>>
>>> Hi all,
>>>
>>> Me and Joep Piscaer are planning on doing some Cobbler + ESX/
>>> vCenter
>>> integration. We'd like to be able to deploy virtuals like we can on
>>> xen/kvm using Koan.
>>> However, we're not going to be able to run a tool like Koan on a
>>> vCenter
>>> server, so we'd have to talk to VMware through some sort of API
>>> from
>>> another host.
>>>
>>> Keeping this in mind, how much sense does it make to still
>>> implement
>>> this in Koan? Wouldn't Cobbler be a better place for this piece
>>> of code
>>> to live?
>>>
>>> I'd like some input on this. :)
>>>
>>>
>>
>> I'm currently working on a cobbler system deploy method that will
>> have
>> deployment modules. If VMware gives you an api to talk to, you
>> could
>> simply write a deployment module to talk to it. I would think
>> that is
>> the best way to go.
>>
>>
> ++
>
> There are Perl APIs, at least, for VMware.
Would it be possible to write support for vmware perl apis into
libvirt? Like yum install libvirt-vmware-esx && service libvirtd
restart or something? I've used the VMWare perl API before but never
looked at the license on their API reference. Someone might be able to
pull that off and stay out of hot water. Obviously this would be a
"community" thing though.
--
Jeff Schroeder
Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel