Edited config keep getting reset if Crowbar node standing.

SUSE OpenStack Cloud
1

Hi, this a my first post here.

I got a issue about Crowbar:
I need to edit few OpenStack service configure to get my application work.
But if the Administration node running (keep in stand by, not doing deployment), the modified configure always been reset.

How can I keep my configuration?

Already searched words like “reset” “configure”, but I didn’t found any kinds of questions.

Many thanks,
Eddie.

2

On 20/06/17 09:04, eddieak wrote:
[color=blue]

Hi, this a my first post here.

I got a issue about Crowbar:
I need to edit few OpenStack service configure to get my application
work.
But if the Administration node running (keep in stand by, not doing
deployment), the modified configure always been reset.

How can I keep my configuration?

Already searched words like “reset” “configure”, but I didn’t found any
kinds of questions.[/color]

Which version of SUSE (OpenStack) Cloud are you using?

How are you editing the configuration?

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

3

[QUOTE=smflood;38363]On 20/06/17 09:04, eddieak wrote:
[color=blue]

Hi, this a my first post here.

I got a issue about Crowbar:
I need to edit few OpenStack service configure to get my application
work.
But if the Administration node running (keep in stand by, not doing
deployment), the modified configure always been reset.

How can I keep my configuration?

Already searched words like “reset” “configure”, but I didn’t found any
kinds of questions.[/color]

Which version of SUSE (OpenStack) Cloud are you using?

How are you editing the configuration?

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]

Hi, thanks for the reply first!

I’m using OpenStack Cloud 7.

And I edit them by log into the node and edit the service configure file.
Like I want to add iSCSI into Cinder, I’ll edit /etc/cinder/cinder.conf.d/100-cinder.conf
Or edit Heat configure by edit /etc/heat/heat.conf.d/100-heat.conf

But I always get my configure reset.

I know that some settings can set on Crowbar, but sometimes I only need few nodes to use my configure, not all nodes in the role.

Is it possible? Or I’m just edit a wrong file?

(And sorry about my bad English.)

Many thanks,
Eddie.

4

This file is managed by chef (which is what crowbar uses to deploy its configs). Similar to other configuration-management-systems, chef will overwrite files to move them to the state it thinks they should be in.
You can add other files next to it, that can set your config entries and will not be touched by chef, but be read by cinder.
E.g. create a /etc/cinder/cinder.conf.d/420-iscsi.conf with your config entries.

5

[QUOTE=bmwiedemann;38400]This file is managed by chef (which is what crowbar uses to deploy its configs). Similar to other configuration-management-systems, chef will overwrite files to move them to the state it thinks they should be in.
You can add other files next to it, that can set your config entries and will not be touched by chef, but be read by cinder.
E.g. create a /etc/cinder/cinder.conf.d/420-iscsi.conf with your config entries.[/QUOTE]

Hi, thanks for reply!

Only I have to do is create another file that contains the settings that I need. But I had a question.
Which settings will choose if both files have same setting but different value?

For example, I want to add “Tenant_admin” value on “trusted_delegated_roles” in 100-heat.conf
So I create another file called 420-heat.conf, and set “trusted_delegated_roles = Member,Tenant_admin”

On this setting, which file will Heat choose? I just want to make sure.

Eddie.

6

This part is well documented in the SOC7 docs:

[CODE]13.1 Default Configuration Files

By default, a configuration snippet with a basic configuration for each OpenStack component is available in the following directory:

/etc/SERVICE/SERVICE.conf.d/010-SERVICE.conf

For example: /etc/nova/nova.conf.d/010-nova.conf

Those files should not be modified.

13.2 Custom Configuration Files

To adjust or overwrite settings for the respective OpenStack component, add a custom configuration file to the same directory, /etc/SERVICE/SERVICE.conf.d/.
The same applies if you want to configure individual components or roles of an OpenStack component, like nova-api or nova-compute, for example. But in this case, add your custom configuration file to the following directory:
/etc/SERVICE/ROLE.conf.d/
All custom configuration file must follow the rules listed in Section 13.3, “Naming Conventions for Custom Configuration Files”.

13.3 Naming Conventions for Custom Configuration Files

Use the following rules for any configuration files you add:

  • The file name must start with a 3-digit number and a dash. For example: /etc/nova/nova.conf.d/500-nova.conf
  • The file must have the following file name extension: .conf
  • For configuration management systems (for example: Crowbar, Salt), use numbers between 100 and 499.
  • To override settings written by the configuration management system, use numbers starting from 500. They have higher priority.

13.4 Processing Order of Configuration Files

The configuration files are processed in the following order:

/etc/SERVICE/SERVICE.conf

/etc/SERVICE/SERVICE.conf.d/*.conf (in dictionary order)

/etc/SERVICE/ROLE.conf.d/*.conf (in dictionary order)

If conflicting values are set for the same parameter, the last configured value overwrites all previous ones. In particular, values defined in

/etc/SERVICE/SERVICE.conf.d/XXX-SERVICE.conf

overwrite configuration values in

/etc/SERVICE/SERVICE.conf[/CODE]

7

Oops, I didn’t notice that !

Really appreciate!

8

Don’t worry, sometimes you don’t really know what to look for, and the docs are quite a lot to read. :wink: