<div dir="ltr">Exactly, I believe getting new as well as existing workload in any cloud environment is always a plus and I agree this will mostly be a tool/script to be used as per requirement.<br><div class="gmail_extra">
<br clear="all"><div>Best <span></span><span></span>Regards,<br>Swapnil Kulkarni<br><a href="mailto:swapnilkulkarni2608@gmail.com" target="_blank">swapnilkulkarni2608@gmail.com</a><br>+91-87960 10622(c)<br><a href="http://in.linkedin.com/in/coolsvap" title="View public profile" name="SafeHtmlFilter_webProfileURL" target="_blank">http://in.linkedin.com/in/coolsvap</a><br>
<img src="https://www-304.ibm.com/certify/member/ccsc.nsf/CertTiv_sm.gif"><br></div>
<br><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 12:43 PM, Alex Glikson <span dir="ltr"><<a href="mailto:GLIKSON@il.ibm.com" target="_blank">GLIKSON@il.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font face="sans-serif">Maybe a more appropriate approach could
be to have a tool/script that does it, as a one time thing.</font>
<br><font face="sans-serif">For example, it could make sense in
a scenario when Nova DB gets lost or corrupted, a new Nova controller is
deployed, and the DB needs to be recreated. Potentially, since Nova DB
is primarily a cache, this could be done by 'discovery' (maybe with some
manual intervention) - instead of dealing with backup/restore of the DB,
or similar approaches.</font>
<br>
<br><font face="sans-serif">Regards,</font>
<br><font face="sans-serif">Alex</font>
<br>
<br>
<br>
<br>
<br><font color="#5f5f5f" face="sans-serif" size="1">From:
</font><font face="sans-serif" size="1">Russell Bryant <<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></font>
<br><font color="#5f5f5f" face="sans-serif" size="1">To:
</font><font face="sans-serif" size="1"><a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>,
</font>
<br><font color="#5f5f5f" face="sans-serif" size="1">Date:
</font><font face="sans-serif" size="1">30/10/2013 08:52 AM</font>
<br><font color="#5f5f5f" face="sans-serif" size="1">Subject:
</font><font face="sans-serif" size="1">Re: [openstack-dev]
[OpenStack-dev][Nova][Discussion]Blueprint : Auto VM Discovery in OpenStack
for existing workload</font>
<br>
<hr noshade><div class="HOEnZb"><div class="h5">
<br>
<br>
<br><tt><font>On 10/30/2013 02:36 AM, Swapnil Kulkarni wrote:<br>
> I had a discussion with russellb regarding this for yesterday, I would<br>
> like to discuss this with the team regarding the blueprint mentioned
in<br>
> subject.<br>
> <br>
> </font></tt><a href="https://blueprints.launchpad.net/nova/+spec/auto-vm-discovery-on-hypervisor" target="_blank"><tt><font>https://blueprints.launchpad.net/nova/+spec/auto-vm-discovery-on-hypervisor</font></tt></a><tt><font><br>
> <br>
> Description: Organizations opting to use openstack can have varied<br>
> amount of workload that they would like to be available directly with<br>
> the use of some discovery workflows. One common usage of this would
be<br>
> exising virtual machines present on the hypervisors. If this instances<br>
> can be disovered by the compute agent during discovery, it would help
to<br>
> use Openstack to manage the existing workload directly. Auto VM<br>
> Discovery will enable this functionality initially for KVM guests,
the<br>
> widely used hypervisor configuration in OpenStack deployments and<br>
> enhance it further for other hypervisors.<br>
<br>
I feel that Nova managing VMs that it didn't create is not an<br>
appropriate use case to support.<br>
<br>
-- <br>
Russell Bryant<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><tt><font>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font><br>
<br>
</font></tt>
<br></div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>