[one-dev] Megam: addon-knife (How can I know a VM is fully launched)
Thomas Alrin
alrin at megam.co.in
Fri May 2 03:13:21 PDT 2014
Hi
In your techniques, you've told to ping the VM, but I don't get IP
at that point.
I want to wait, to get the ip from my VM. When i run a vm in
AWS(public cloud) cloud, I can wait for
/vm_hash['VM']['TEMPLATE'].has_key?('AWS_IP_ADDRESS')/, to get the ip.
In the above case, the key /AWS_IP_ADDRESS /seems to be depends on
AWS cloud.
If i create a vm in private cloud, for which key(like
/AWS_IP_ADDRESS)/ , i can wait to get the ip address?
On Thursday 01 May 2014 08:06 AM, Megam Systems wrote:
> fya.
>
> As we would loose a 12 hr. window, I queued up a request in the dev
> mailing list.
>
> See if these options help you.
>
>
> -------- Original Message --------
> Subject: Re: [one-dev] Megam: addon-knife (How can I know a VM is
> fully launched)
> Date: Wed, 30 Apr 2014 20:23:42 +0200
> From: Ruben S. Montero <rsmontero at opennebula.org>
> To: Megam Systems <gomegam at megam.co.in>
> CC: dev at lists.opennebula.org
>
>
>
> Hi
>
> As mentioned in yout email you are looking for the AWS_IP_ADDRESS key,
> which is only valid for Amazon Hybrid VMs. This value is obtained
> through the monitorization process as reported/updated by Amazon.
>
> In general, as boot time of a VM depends on the software stack running
> wihtin, you cannot rely on the VM status reported by the hypervisors,
> i.e. RUNNING means that the VM is running at hypervisor level but it
> can be stuck in the virtual BIOS because of an error or misconfiguration.
>
> In our internal testing platform we use two techniques:
>
> 1.- Pro-active ping the VM, a simple ping+sleep loop with a timeout.
> 2.- Make the VM callback home to a known URL (you may use onegate for
> this)
>
> Note that both requires connectivity to some extent between the knife
> controller and the VM.
>
> Cheers
>
> Ruben
>
>
>
>
>
> On Wed, Apr 30, 2014 at 4:24 PM, Megam Systems <gomegam at megam.co.in
> <mailto:gomegam at megam.co.in>> wrote:
>
> Dear Dev-OpenNebula,
>
> When working on the addon-knife, upon launching a VM using the
> OpenNebula API, there is a need to wait till the VM is fully
> launched. Currently we wait until an IP address is available from
> the VMPool.
>
> Please find the reference of the code here.
> https://github.com/OpenNebula/addon-knife/blob/master/lib/chef/knife/opennebula_server_create.rb#L168
>
> We need a better way as OpenNebula can run in private clouds as well.
>
> How can we know that a VM is fully launched and running ? What
> parameter (status etc..) helps us to figure out that the VM is
> running.
>
> --
> Cheers,
> Megam Systems; http://www.gomegam.com
> email : gomegam at megam.co.in <mailto:gomegam at megam.co.in>; twitter:
> @megamsystems
> blog : http://blog.megam.co | try : https://www.megam.co
> github: https://github.com/megamsys | youtube :
> youtube.com/indykish <http://youtube.com/indykish>
>
> _______________________________________________
> Dev mailing list
> Dev at lists.opennebula.org <mailto:Dev at lists.opennebula.org>
> http://lists.opennebula.org/listinfo.cgi/dev-opennebula.org
>
> --
> --
> Ruben S. Montero, PhD
> Project co-Lead and Chief Architect
> <http://lists.opennebula.org/listinfo.cgi/dev-opennebula.org>
> OpenNebula - Flexible Enterprise Cloud Made Simple
> <http://lists.opennebula.org/listinfo.cgi/dev-opennebula.org>www.OpenNebula.org
> <http://www.OpenNebula.org> | rsmontero at opennebula.org
> <mailto:rsmontero at opennebula.org> | @OpenNebula
>
>
>
--
With Warm Regards,
Thomas Alrin,
Infrastructure Engineer; Megam Systems;
email: alrin at megam.co.in; cell: +91 9789345999
twitter : @thomasalrin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/dev-opennebula.org/attachments/20140502/394e0484/attachment-0001.htm>
More information about the Dev
mailing list