I agree, I was wondering having additional support for such a feature would definitely have value addition for adoption of OpenStack. It can be developed as an optional functionality during host addition which users can opt on case-to-case basis.
Best Regards, Swapnil On Wed, Oct 30, 2013 at 12:20 PM, Russell Bryant <rbry...@redhat.com> wrote: > On 10/30/2013 02:36 AM, Swapnil Kulkarni wrote: > > I had a discussion with russellb regarding this for yesterday, I would > > like to discuss this with the team regarding the blueprint mentioned in > > subject. > > > > > https://blueprints.launchpad.net/nova/+spec/auto-vm-discovery-on-hypervisor > > > > Description: Organizations opting to use openstack can have varied > > amount of workload that they would like to be available directly with > > the use of some discovery workflows. One common usage of this would be > > exising virtual machines present on the hypervisors. If this instances > > can be disovered by the compute agent during discovery, it would help to > > use Openstack to manage the existing workload directly. Auto VM > > Discovery will enable this functionality initially for KVM guests, the > > widely used hypervisor configuration in OpenStack deployments and > > enhance it further for other hypervisors. > > I feel that Nova managing VMs that it didn't create is not an > appropriate use case to support. > > -- > Russell Bryant > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev