... to q-ovn-metadata-agent.
To the best of my understanding we decided to keep using the
neutron-legacy devstack module since it is the one used in the gate:
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/thread.html#11544
And we merge new features like the ovn migration only working with
neutron-legacy:
https://review.opendev.org/696592
It seems to me we were a bit inconsistent in naming devstack service
'neutron-ovn-metadata-agent' since legacy style devstack service
names start with 'q-'.
For example this sample config is broken:
https://opendev.org/openstack/neutron/src/branch/master/devstack/ovn-compute-local.conf.sample#L31-L35
stack.sh dies with:
lib/neutron: line 368: neutron_plugin_create_nova_conf: command not found
Because not having a single 'q-' service in that enabled service list
we trip up devstack's 'is_neutron_legacy_enabled' check:
e51cbf0ea9/lib/neutron (L127-L135)
This change renames devstack service neutron-ovn-metadata-agent
to q-ovn-metadata-agent.
I'm not proud to propose this change in 2020 (circa 5 years after
the rename from Quantum to Neutron) so let me know if you see a better
way. :-)
Change-Id: I507a3426e2b63bff49891bd5a51fa9d9999a0ffa
We already have many different jobs defined for Zuul in Neutron repo.
Up to now all those jobs were in .zuul.yaml file but this file growth
really big and it was hard to read and navigate in it.
So this patch proposes to move jobs definitions to zuul.d directory to
separate yaml files per "job types". So there will be now separate files
with definitions for:
* grenade jobs,
* base jobs like functional and fullstack,
* rally jobs,
* tempest multi node jobs,
* tempest single node jobs,
* tripleo jobs.
And maybe others in the future.
Change-Id: Ia77f59fded0e6e0ae328d866a7486af02b50c2d7