[Openstack] More than one compute_driver in nova.conf
GLIKSON at il.ibm.com
Tue Aug 13 06:46:40 UTC 2013
"Jake G." <Dj_dark_junglist at yahoo.com> wrote on 13/08/2013 07:25:04 AM:
> On 2013/08/13, at 12:50, Robert Collins <robertc at robertcollins.net>
> >> I was wondering how to handle changing the compute_driver in
> >> currently have the default
> >> compute_driver = libvirt.LibvirtDriver
> >> libvirt_type=kvm
> >> I want to be able to add the driver for baremetal provisioning, but I
> >> unclear on how to do this.
> >> Can there be more than one compute_driver or do I have to replace
> >> compute_driver = libvirt.LibvirtDriver with the new driver.
> > You need to have a dedicated nova cell/region/cloud for baremetal. We
> > change the scheduler at a fairly fundamental layer - Devananda has
> > plans to rectify this, but probably only after Ironic is stable.
> >> If I can only replace what will happen to my existing KVM and nova
> >> operations?
> > I suggest spinning up a new host rather than modifying your existing
> >> Also, I am just using the bearmetal driver as an example. This
> same question
> >> can be applied to any other feature that requires a different
> >> compute_driver.
> > Baremetal is special - unlike lxc/kvm/qemu baremetal doesn't subdivide
> > an existing hypervisors resources, rather it hands out entire machines
> > - so it has to match exactly rather than matching a subset when
> > comparing flavors.
> > Cheers,
> > Rob
> > --
> > Robert Collins <rbtcollins at hp.com>
> > Distinguished Technologist
> > HP Converged Cloud
> Thanks for the heads up. I can image the damage I would have done to
> my test environment trying to get this going.
> Just to confirm, there is no way to add another compute node that is
> for baremetal only into an existing openstack environment?
For the compute node itself, it seems possible just to have a separate
host running nova-compute configured to work with bare-metal driver, with
a different nova.conf. Regarding the scheduler, support for multiple
configurations will be possible once
https://review.openstack.org/#/c/37407/ is merged (hopefully soon). In the
latest revision, nova.conf will not change, but you will be able to
override scheduler parameters (driver, maybe even host manager) with
flavor extra specs. At least in theory the combination of the two should
allow having 'regular' and bare-metal in the same deployment, IMO.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack