<br>I used ESX for a few weeks.... I also had some VM's that were not under the administrative domain of opennebula.<br><br>Here is the process I used, after I applied the patches I sent to the list earlier.<br><br>1. Use VI client to create and install a VM<br>
2. Add contextualization scripts to that VM<br>3. Shutdown the VM and copy it to the shared datastore<br>4. Write an openNebula template for it<br>5. Launch as many instances of that VM as I want!<br><br>As to the original files on the local datastore.... I erased them!<br>
<br>If you have VM's that you can not shut down on a production ESX... Well, you should keep using whatever management system you currently use.<br><br>OpenNebula is an Infrastructure manager, but it can only manage and monitor infrastructure that was deployed by itself.<br>
<br>If you are very very familiar with the database structure used by OpenNebula, I guess that you cloud add a fake instance to the database just to make OpenNebula aware of the external VM, but I would not know where to start, and do not recommend that you try it.<br>
<br>Tiago<br><br><div class="gmail_quote">On Tue, Mar 16, 2010 at 7:26 PM, Jonathan Kelley <span dir="ltr"><<a href="mailto:jkelley@vm-labs.com">jkelley@vm-labs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I apologize for being naive but how do you register the VMs on ESX. I attached my ESX node with ./onehost commands and it show up.<div><br></div><div>Now how do I add the VMs which are not registered on the ESX but live in the datastores on that ESX machine?</div>
<div><br></div><div>Or do they have to live in the shared storage path?</div><div><br></div><div>Thanks,</div><div>Jon</div><div><div></div><div class="h5"><div><br><br><div class="gmail_quote">On Tue, Mar 16, 2010 at 5:54 AM, Tino Vazquez <span dir="ltr"><<a href="mailto:tinova@fdi.ucm.es" target="_blank">tinova@fdi.ucm.es</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
So here is how it works: OpenNebula tries to register the VM, if<br>
already registered, it fails, if not, it registers the image and boots<br>
it up.<br>
<br>
If a VM is previously registered, OpenNebula won't know about it,<br>
won't report it, and will fail if you try to deploy it with onevm.<br>
<div><br>
Regards,<br>
<br>
-Tino<br>
<br>
--<br>
Constantino Vázquez, Grid & Virtualization Technology<br>
Engineer/Researcher: <a href="http://www.dsa-research.org/tinova" target="_blank">http://www.dsa-research.org/tinova</a><br>
DSA Research Group: <a href="http://dsa-research.org" target="_blank">http://dsa-research.org</a><br>
Globus GridWay Metascheduler: <a href="http://www.GridWay.org" target="_blank">http://www.GridWay.org</a><br>
OpenNebula Virtual Infrastructure Engine: <a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a><br>
<br>
<br>
<br>
</div><div><div></div><div>On Mon, Mar 15, 2010 at 12:32 PM, Jonathan Kelley <<a href="mailto:jkelley@vm-labs.com" target="_blank">jkelley@vm-labs.com</a>> wrote:<br>
> Hi Tino,<br>
><br>
> Yes my hosts are registered in esx and I can see them in vSphere, through<br>
> perl API and libvirt. Nothing shows up in opennebula commands. Does the<br>
> driver support esxi 4?<br>
><br>
> Thanks.<br>
> -Jon<br>
><br>
> On Mar 15, 2010, at 6:40 AM, Tino Vazquez <<a href="mailto:tinova@fdi.ucm.es" target="_blank">tinova@fdi.ucm.es</a>> wrote:<br>
><br>
>> Hi Jonathan,<br>
>><br>
>> By register in ESX I mean that the Hypervisor is aware of the VM, even<br>
>> though it may not be running. If you use VMware's Virtual<br>
>> Infrastructure Client (VIC), you will be able to see which VMs are<br>
>> registered in a specific ESX (if they appear in the left side's tree<br>
>> view, then they are registered).<br>
>><br>
>> Regards,<br>
>><br>
>> -Tino<br>
>><br>
>> --<br>
>> Constantino Vázquez, Grid & Virtualization Technology<br>
>> Engineer/Researcher: <a href="http://www.dsa-research.org/tinova" target="_blank">http://www.dsa-research.org/tinova</a><br>
>> DSA Research Group: <a href="http://dsa-research.org" target="_blank">http://dsa-research.org</a><br>
>> Globus GridWay Metascheduler: <a href="http://www.GridWay.org" target="_blank">http://www.GridWay.org</a><br>
>> OpenNebula Virtual Infrastructure Engine: <a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a><br>
>><br>
>><br>
>><br>
>> On Mon, Mar 8, 2010 at 7:17 PM, Jonathan Kelley <<a href="mailto:jkelley@vm-labs.com" target="_blank">jkelley@vm-labs.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi Tino,<br>
>>><br>
>>> Thanks for your response. What do you mean by unregister them? Giving<br>
>>> the vmx file path or something to OpenNebula will then register them?<br>
>>><br>
>>> Thanks,<br>
>>> Jon<br>
>>><br>
>>><br>
>>> On Mon, Mar 8, 2010 at 10:13 AM, Tino Vazquez <<a href="mailto:tinova@fdi.ucm.es" target="_blank">tinova@fdi.ucm.es</a>> wrote:<br>
>>>><br>
>>>> Hi Jonathan,<br>
>>>><br>
>>>> OpenNebula will try and register existing VMs, so any preregistered<br>
>>>> VMs won't be able to be used with OpenNebula. To correctly use them,<br>
>>>> you will need to unregister them by hand first.<br>
>>>><br>
>>>> Hope it helps,<br>
>>>><br>
>>>> -Tino<br>
>>>><br>
>>>> --<br>
>>>> Constantino Vázquez, Grid & Virtualization Technology<br>
>>>> Engineer/Researcher: <a href="http://www.dsa-research.org/tinova" target="_blank">http://www.dsa-research.org/tinova</a><br>
>>>> DSA Research Group: <a href="http://dsa-research.org" target="_blank">http://dsa-research.org</a><br>
>>>> Globus GridWay Metascheduler: <a href="http://www.GridWay.org" target="_blank">http://www.GridWay.org</a><br>
>>>> OpenNebula Virtual Infrastructure Engine: <a href="http://www.OpenNebula.org" target="_blank">http://www.OpenNebula.org</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Tue, Mar 2, 2010 at 9:26 PM, Jonathan Kelley <<a href="mailto:jkelley@vm-labs.com" target="_blank">jkelley@vm-labs.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Hello,<br>
>>>>> I am fairly new to OpenNebula (today) but I got my ESX host to be added<br>
>>>>> (after some problems realizing I absolutely needed FQDN).<br>
>>>>> However my question is what is to come of the VMs that exist on my ESX<br>
>>>>> host.<br>
>>>>> Can OpenNebula register those VMs? Or can I only add/create new ones?<br>
>>>>> I am running OpenNebula 1.4 and ESXi 4.0.<br>
>>>>> Thanks,<br>
>>>>> Jon Kelley<br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Users mailing list<br>
>>>>> <a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
>>>>> <a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
>>>>><br>
>>>>><br>
>>>><br>
>>><br>
><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br>