Checks that network roles mapping from original release is a subset of
network roles mapping of new cluster's release.
Change-Id: I521e70bf3df289abf3e71c5c1558faf7126db964
Partial-Bug: #1619162
for creating of network groups in the seed cluster
such as in the original cluster
Change-Id: I17f95756fa26ef0f7df0e969f9f1ba4331047c8d
Closes-Bug: #1616817
* netgroups mapping was changed (additional argument
for the mapping was added - name of node group)
* copying of node group during cluster cloning was added
Depends-On: I2638279371e91f15090c782fc5fdbb434a2e85f8
Partial-bug: #1612297
Change-Id: Ib1689d7b6d673c0d78434dd047a7ebc520c232e7
Co-Authored-By: Ryan Moe <rmoe@mirantis.com>
Co-Authored-By: Andrew Woodward <awoodward@mirantis.com>
Co-Authored-By: Ilya Kharin <akscram@gmail.com>
octane have some dirty hacks to change volumes attributes using nailgun
as a library, such modifications should be done in a extension
Change-Id: I422bb368916f3a319e286edcc6103a2834097a87
Changing of an operating system for clouds nodes is not supported and is
not tested at all. That's why this additional validation was added.
Change-Id: Ibf6db17f783879eff88e2366dfdb0a2871e2aa0a
Change Ia3da3bd809bcca923d53666eca54def78c995f65 broke our handlers as
it incorporated destructive changes to all handlers.
Change-Id: I688e833b1fb8b658f01b7f858a140c315fa513a2
Don't need to assign nics and bonds to netgroups
if network template has been applied to new cluster.
Change-Id: Ibd06de87964bf7a2038899d32e3d8a0189b9cbbd
Partial-bug: 1584044
We have extra SQLs generated in the NetworkManager when passing
node_id instead already loaded SQLAlchemy node object.
Additional changes:
- Bulk insert used in IPs assiging process.
- zip changed on six.moves.zip in the NetworkManager.
- Removed unused function get_admin_ips_for_interfaces from NetworkManager.
Co-Authored-By: Dmitry Guryanov <dguryanov@mirantis.com>
Partial-Bug: #1498365
Change-Id: I0518a5879c775d568de5652dbdd856a0cede80ce
In some upgrade scenarios when shadow environments are used some of
nodes should not be reprovisioned during this procedure. It is useful in
combination when control plane nodes are reprovisioned and data plane
nodes are updated in place.
The update_cluster_assignment method of the objects.Node class was
changed to accept roles and pending_roles for node during the
reassignment. It allows to specify proper roles by the upgrade
extention.
The NodeReassignHandler handler accepts two additional parameters in the
request body:
- reprovision = True (default) - allows to skip the reprovision step
- roles = [] (default) - allows to specify new roles or preserve the
current roles if empty
Two additional methods were added to NailgunClusterAdapter and
NailgunReleaseAdapter respectively.
Change-Id: Iedb20a904e58f5b9a86eb47de8d8d317dc3cc61b
Blueprint: upgrade-major-openstack-environment
Closes-Bug: #1558655
All network-related database queries are moved into the appropriate
object methods. This is being done to make it possible to have an external
network management service.
Blueprint: network-config-refactoring
Change-Id: I4ce965f227c54577659e64f598ff5cdf4c868ed6
is_deployable doesn't really give any additional information for a
release, it is removed. To make change API-backward-compatible, it is
retained as a property dependent on release.state.
New state is added - manageonly, for environments that are not able to
be deployed, but can still be managed.
Change-Id: I518a0114730a2f227c9ef035a376f9a90d3d5bbd
Closes-bug: #1503303
DocImpact
In the 7.0 release the networking templates were introduced. They use
the ip.addrs.vip_type column as names of VIPs and these names differ
from names of previous releases. To solve this we can renamed VIPs of
older releases during upgrade to 7.0 accoring the rules:
management: haproxy -> management
public: haproxy -> public
public: vrouter -> vrouter_pub
Change-Id: Ia77d13ea90408a06896f2a49c6e43d44c6af1d0d
Closes-Bug: #1482577
The patch adds method that assigns a node to an upgrade cluster without
deleting it from DB. This allows to keep ID of the node and IP addresses
assigned to it. The node is booted into the bootstrap image as soon as
it moves to an upgrade cluster.
Implements blueprint: nailgun-api-env-upgrade-extensions
Co-Authored-By: Artur Svechnikov <asvechnikov@mirantis.com>
Change-Id: If10fadd149a32317420778607146d9d12108d3f9
The patch adds an extension which implements the procedure of upgrading
clusters from one major release to another. As a first step of the
procedure the extension provides an ability to create a seed cluster
with the same settings as the original.
Implements blueprint: nailgun-api-env-upgrade-extensions
Change-Id: I22d51a3ffd51a7c88bdcbde0eef6f47b65def1c8
Andreas Jaeger