I think there’s a bit more to it that just having an aggregate:
- Ironic provides its own version of the Host manager class for the scheduler, I’m not sure if that is fully compatible with the non-ironic case. Even in the BP for merging the Ironic driver back into Nova it still looks like this will stay as a sub-class (would be good if they can just be merged IMO) - You’d need to decide how you want to use the aggregate – extra specs in the flavor matching against the aggregate metatdata is one way, you could also do it by matching image metadata (as the ironic images are going to be different from KVM ones) From: Joe Gordon [mailto:[email protected]] Sent: 25 June 2014 05:53 To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [Nova] [ironic]nova scheduler and ironic On Jun 24, 2014 7:02 PM, "Jander lu" <[email protected]<mailto:[email protected]>> wrote: > > hi, guys, I have two confused issue when reading source code. > > 1) can we have ironic driver and KVM driver both exist in the cloud? for > example, I have 8 compute nodes, I make 4 of them with compute_driver = > libvirt and remaining 4 nodes with > compute_driver=nova.virt.ironic.IronicDriver ? > > 2) if it works, how does nova scheduler work to choose the right node in this > case if I want boot a VM or a physical node ? You can use host aggregates to make certain flavors bare metal and others KVM > > > thx all. > > _______________________________________________ > OpenStack-dev mailing list > [email protected]<mailto:[email protected]> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
