[openstack-dev] [helm] multiple nova compute nodes

Steve Wilkerson wilkers.steve at gmail.com
Tue Oct 2 23:27:17 UTC 2018

In addition to targeting nodes by labels (these labels are exposed for
overrides in the move chart’s values.yaml, so they can be whatever labels
you wish them to be), you can also disable particular templates in the nova
chart.  You can find these under the ‘manifests:’ key in the chart’s
values.yaml. Each template in the nova chart will have a key that can
toggle whether you deploy that template or not, and these keys should be
named similar to the templates they control.  With this, you can exclude
particular nova components if you desire.

Hope that helps clear things up.


On Tue, Oct 2, 2018 at 6:04 PM Chris Friesen <chris.friesen at windriver.com>

> On 10/2/2018 4:15 PM, Giridhar Jayavelu wrote:
> > Hi,
> > Currently, all nova components are packaged in same helm chart "nova".
> Are there any plans to separate nova-compute from rest of the services ?
> > What should be the approach for deploying multiple nova computes nodes
> using OpenStack helm charts?
> The nova-compute pods are part of a daemonset which will automatically
> create a nova-compute pod on each node that has the
> "openstack-compute-node=enabled" label.
> Chris
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181002/d64ba188/attachment.html>

More information about the OpenStack-dev mailing list