I finally got a passing neutron-grenade run in change [1]. That's the grenade change which populates the placement DB in Stein from the placement-related table contents of the nova_api DB from Rocky. It also writes out the placement.conf file for Stein before starting the Stein services.

As a result, I'm +2 on Dan's mysql-migrate-db.sh script [2].

The grenade change is also dependent on three other changes for neutron [3], ironic [4] and heat [5] grenade jobs to require the openstack/placement project when zuul/devstack-gate clones its required projects before running grenade.sh.

Those are just the related project grenade jobs that are hit as part of the grenade patch. There could be others I'm missing, which means projects might need to update their grenade job definitions after the grenade change merges. It looks like that could be quite a few projects [6]. If the infra/QA teams have a better idea of how to require openstack/placement in stein+ only, I'm all ears. Maybe that's some conditional branch logic we can hack into devstack-gate [7] like we do for neutron? [8]

[1] https://review.openstack.org/#/c/604454/
[2] https://review.openstack.org/#/c/603234/
[3] https://review.openstack.org/#/c/604458/
[4] https://review.openstack.org/#/c/606850/
[5] https://review.openstack.org/#/c/606851/
[6] http://codesearch.openstack.org/?q=export%20PROJECTS%3D%22openstack-dev%5C%2Fgrenade%20%5C%24PROJECTS%22&i=nope&files=&repos= [7] https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstack-vm-gate-wrap.sh#L138 [8] https://github.com/openstack-infra/devstack-gate/blob/95fa4343104eafa655375cce3546d27139211d13/devstack-vm-gate-wrap.sh#L195




OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to