Neutron contains broken migrations between 7-8 release which
leads to unavailable floating ips. Execute fix for 9.0 release too
because we do not have 9.1 release value in nailgun db.
Change-Id: Ia57f4fbc141469fe2af2f2ff948d5fbcd75362dc
Closes-bug:1644190
As per OpenStack licensing guide lines [1]:
[H102 H103] Newly contributed Source Code should be licensed under
the Apache 2.0 license.
[H104] Files with no code shouldn't contain any license header nor
comments, and must be left completely empty.
[1] http://docs.openstack.org/developer/hacking/#openstack-licensing
Change-Id: I72247b1a4b1efdc329d424e269600793b29e5428
This commit introduces the task graphs that
handle osd-upgrade command. Python part is
in a separate commit.
There are 3 graphs:
1. (orig) prepare environment: update repos
2. (seed) set noout & upgrade ceph on target nodes
3. (orig) unset noout and restart
Change-Id: I0ce93831f715ad919acb4420f05b729afb9bb15b
In order to upgrade MOS from 7.0 to 9.1 the following steps should be
made:
* Upgrade Fuel Master node
* Upgrade Fuel Master node from 7.0 to 8.0
Record: docs/records/fuel_master_70_80.json
* Upgrade Fuel Master node from 8.0 to 9.0
Record: docs/records/fuel_master_80_90.json
* Apply 9.1 updates for 9.0 Fuel Master node
Record: docs/records/fuel_master_91_mu.json
* Upgrade MOS Cloud from 7.0 to 9.1
Record: docs/records/cloud_70_91_upgrade.json
Change-Id: I0157b48690d5f746423560ae764514461d1d0e45
Also, on the backup step a status of `mco ping` is serialized in an
upgrade tarball and on the restore step it is compared with the actual
status. All nodes that are not respond are logged.
In additional, the status of `mco ping` is archived on the backup step
and is compared on the restore step with the actual ones.
Change-Id: Ibba81102214998d83614a42cdb21c21bebd8284a
Related-Bug: #1561092
- Add repo list to cluster settings
- Add package list to cluster settings
- Override repo list on computes via Hiera
- Clear old apt configuration
- Rsync latest puppet modules
- Use setup_repositories task to set up new repos
- Upgrade packages
- Remove override
- Roll back repo configuration
Change-Id: I2d3dc57702084dfd5ac771a6f55e11968f86f9f3
This commit allows to execute graphs
on specific nodes. It also adds the
ability to upload graphs to specific
environment (seed/orig) instead of
allowing to upload to both at the same
time.
Change-Id: I560cfed850d356e2fde86f44cc68c200cf693958
Note: this CR implements switch-controlplane `with-graph` only partially.
Some code have been reused due to absence of isolation control in
`fuel-cluster-upgrade-extension`.
Change-Id: Icdaec6f57e73b0e4cdec34bf7307e9429af2cb1c
Appropriate upgrade_levels have to be set after each deploy-changes for
controller and compute nodes because they are cleared. It have to be
solved using advanced configuration feature.
Change-Id: Idbe13e58d2ae0787620211ba0300150ed4e82f39
Partial-Bug: #1624341
The upgrade_levels:compute parameter have to be set after each deploy
changes operation on controllers otherwise live-migration of instances
will not work properly.
Change-Id: I98a89b51102371f7a50d8a182dc61d671dbf7151
Partial-Bug: #1624341
Python 3.3 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it also.
Change-Id: Ic36ee7e9c13350597cd2135182f9d9049e8e7475
The backend name for volumes was changed since Kilo. To make these
volumes back manageable in Mitaka their hostnames have to be changed.
The `cinder-manage volume update_host` command is suitable to do that.
Change-Id: Ieeadd81c714186d58a3e3dfe5fd1223c40d16996
Partial-Bug: #1624341
The radosgw have to be restarted during the upgrade of Ceph otherwise
the object store will be unavailable on the primary controller.
Change-Id: If949b24a6176c3c65ff4c26b089b4997bd991cb5
Related-Bug: #1624341
All environments which are created on the 9.1 Fuel Master node have
fuel_version is equal to 9.1. This release have to be added in
UPGRADE_LEVELS with the 'liberty' compatibility to support N+1 and N+2
upgrades.
Change-Id: Ic4cd045e6d428ce5cfed65f385a689629a232332
Closes-Bug: #1625083
(cherry picked from commit c0145127c2)