[Starlingx-discuss] Fail to change config of nova-compute container

[Kopec, Gerald (Gerry)]

Agree with what Bob is saying that you should normally set remote storage via host label.

In terms of overriding the setting via system helm-override-update command.  If the configuration is set as a per host override, then you have to override it in the overrides/nova_compute/hosts section of the nova config.

Gerry

From: Church, Robert [mailto:Robert.Church at windriver.com]
Sent: Monday, September 09, 2019 12:31 PM
To: Friesen, Chris; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Fail to change config of nova-compute container

As Chris mentioned, we are using a host label to drive this configuration on a per worker basis.

If you want to enable this configuration for a specific openstack worker:

$ system host-lock compute-0
$ system host-label-assign compute-0 remote-storage=enabled
$ system host-unlock compute-0

If you look at the nova plugin, this configuration is set via a per-host override based on the host label.

Your nova.yaml is setting the default configuration not the per-host configuration.

I suspect that if we weren’t setting the per-host override for this value explicitly in the nova plugin based on the presence/absence of the label, then this value would apply to all nova pods across all the compute workers.

Bob


From: Chris Friesen <chris.friesen at windriver.com>
Date: Monday, September 9, 2019 at 11:01 AM
To: "starlingx-discuss at lists.starlingx.io" <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] Fail to change config of nova-compute container

In this case rather than explicitly overriding nova.conf I think the "proper" way to get rbd storage is to set the "remote-storage" label on the node.  This allows the rbd_pool and rbd_cev_conf settings to be configured properly as well.

Chris

On 9/9/2019 9:51 AM, Chris Friesen wrote:
This is arguably a bug...the intent of the "system helm-override-update" command was to allow the admin to override system-configured settings.

Chris

On 9/8/2019 6:27 PM, Lin, Shuicheng wrote:
Hi,
For nova-compute, it is due to this configuration is overrides by sysinv in below code.
https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/helm/nova.py#L363


Best Regards
Shuicheng

From: 胡天昊 [mailto:hu.tianhao at 99cloud.net]
Sent: Friday, September 6, 2019 2:13 PM
To: starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] Fail to change config of nova-compute container

Hi guys,

Recently I got a problem when I try to change config of nova-compute.After run the the following command :

system helm-override-update six-openstack nova openstack --value nova.yml
system application-apply six-openstack

I find that config of every container about nova(just like nova-conductor and nova-scheduler) has changed except nova-compute. Here is my nova.yml file.
conf:
  nova:
    libvirt:
      images_type: rbd
I can find 'images_type: rbd' in /etc/nova/nova.conf in every container about nova but in nova-compute I just find 'images_type: default'.
My system is virtual standard with controller storage r2.0 following the guide(https://docs.starlingx.io/deploy_install_guides/current/virtual_controller_storage.html).
I don't understand why this happened. Can anyone give me some help?

Thanks
Hu Tianhao



_______________________________________________

Starlingx-discuss mailing list

Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>

http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss




_______________________________________________

Starlingx-discuss mailing list

Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>

http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190909/cef46eb8/attachment-0001.html>