neutron recipes on compute nodes should not look at attributes from neutron-server nodes

[vuntz]

It could be that an attribute gets added in a migration to the neutron proposal, and this will become visible on the neutron-server node only when chef has run. However, if chef runs on compute nodes first, it will not find the attribute. This could result in the wrong config on the compute nodes for a period of time.

The fix is to adopt the data bag config item work, and extend it (see crowbar#718)

Backport Databag work

• Backport crowbar: Add rake task to regenerate data bag configs crowbar/crowbar-core#954
• Backport Call "rake crowbar:update_config_db" when updating barclamps crowbar/crowbar#2302
• Backport Start moving away from search queries to static config items for cookbooks crowbar/crowbar-core#947
• Backport Start moving away from search queries to static config items for cookbooks crowbar/crowbar-openstack#718

Fix the issue

• @vuntz could you provide some description what would be the work to be done?

[matelakat]

• Start moving away from search queries to static config items for cookbooks  crowbar-core#22 backports:
  • Start moving away from search queries to static config items for cookbooks crowbar/crowbar-core#947
  • crowbar: Add rake task to regenerate data bag configs crowbar/crowbar-core#954
• [backport] Call "rake crowbar:update_config_db" when updating barclamps crowbar#2 backports:
  • Call "rake crowbar:update_config_db" when updating barclamps crowbar/crowbar#2302
• [backport] Start moving away from search queries to static config items for cookbooks #31 backports:
  • Start moving away from search queries to static config items for cookbooks crowbar/crowbar-openstack#718

[vuntz]

@vuntz could you provide some description what would be the work to be done?

If you look at the neutron cookbook, you'll see some recipes which are run on compute nodes too. These ones are the problematic ones. We do something like neutron = search node with role neutron-server; but in case a schema migration happened and chef hasn't run yet on the neutron-server, the attributes will be wrong. So we should instead do something like neutron = Role.load("neutron-config-default") and read the attributes directly from the role.

[vuntz]

Note that this is a bit of a special case: usually, the data bag config item that you backported would be enough; but the problem is that the recipes need to look at, basically, all attributes of the proposal. Which is way more than what the data bag config item contains.

Of course, one alternative is to make the data bag config item contain a copy of the attributes.

[tpatzig]

I think #34 is the same, @vuntz do you agree?

[vuntz]

I think #34 is the same, @vuntz do you agree?

Not completely, unfortunatel.

[vuntz]

@mkoderer this is a true issue, but also a very edge case that wouldn't occur again unless more attributes are added to the neutron barclamp. I'm tempted to drop the critical tag here.