As part of annual planning we have been lining up work that needs to be done and it seems clear that if we try to do migration away from Trusty and Neutron in serial rather than in parallel we will be in trouble timeline wise.
@bd808, @Andrew and I have all talked about it and it seems like the following is the best option to attempt to pursue:
- Setup labtestn (to be renamed) using Debian Jessie which we can pull Mitaka from backports
- Upgrade labtest (to be renamed ;) to Mitaka using the trusty cloud repo (this is so we can mix and match trusty and debian components)
- Upgrade main to Mitaka
This means Mitaka is our "frozen" target for Neutron rather than Liberty but it seems like a necessity, and it's my understanding that Mitaka is the last release of OpenStack where nova-network is tested/supported/available.
(Note we could I think in theory grab packages from http://snapshot.debian.org/package/keystone/ (etc) and attempt to stay on Liberty with debian but it seems far more sane to follow backports last standing in Jessie, especially since @Andrew doesn't think the upgrade will be too bad and the only big open question is some designate changes at the moment)
https://www.stratoscale.com/blog/openstack/openstack-mitaka-whats-new-part-1/
https://docs.openstack.org/releasenotes/nova/mitaka.html
Latest API microversion supported for Mitaka is v2.25
Nova now requires a second database (called ‘API DB’).
A new nova-manage script allows you to perform all online DB migrations once you upgrade your cloud
EC2 API support is fully removed.
https://docs.openstack.org/releasenotes/keystone/mitaka.html
:* keystone-manage bootstrap
https://phabricator.wikimedia.org/source/operations-puppet/browse/production/modules/openstack/templates/bootstrap/keystone/keystone_seed.sh.erb
https://docs.openstack.org/releasenotes/designate/mitaka.html
(Deprecation Notes)
Create / Update / Delete API methods on /v2/pools/ Using these messages will cause unforseen issues with pools. We highly recommend that the policy file be updated to restrict create / update / delete from all users
default-soa-refresh configuration option
https://docs.openstack.org/releasenotes/glance/mitaka.html
(Upgrade Notes)
Metadata definitions previously associated with OS::Nova::Instance have been changed to be associated with OS::Nova::Server in order to align with Heat and Searchlight. You may either upgrade them using glance-manage db load_metadefs [path] [merge] [prefer_new] or glance-manage db upgrade 44.
The task API is being deprecated and it has been made admin only. If deployers of Glance would like to have this API as a public one, it is necessary to change the policy.json file and remove role:admin from every task related field.
https://docs.openstack.org/releasenotes/horizon/mitaka.html
:* multi-region (vxlan and floating ips)
:* rebuild labtestweb2001?
They are creation a separate nova_api DB that makes this transition more complicated in this release.
https://bugs.launchpad.net/tripleo/+bug/1648504
https://review.openstack.org/#/c/408669/
Procedure for in place upgrade of existing ubuntu (labtest => main):
- Add new mitaka cloud repo? -- beware mitaka and neutron config things --
- Upgrade keystone?
- Upgrade glance
- Upgrade nova ( new nova_api db?) (nova_network)
- Upgrade designate (fix scripts? downtime?)