[doc] Redeploy cinder/compute nodes if new controller added
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Svetlana Karslioglu |
Bug Description
https:/
commit 1d3982f606b5d0d
Author: Dima Shulyak <email address hidden>
Date: Mon Nov 3 13:37:37 2014 +0200
Redeploy cinder/compute nodes if new controller added
Addition of new controller affects cluster messaging,
particularly cinder/computes nodes which is reliant on
rabbitmq_hosts settings
In current orchestration model - the only way to
fix configuration on nodes is to redeploy them.
Configuration will be applied from /etc/astute.yaml and
it is not enough to simply add additional PostDeployment
method in astute
Introduced additional setting for roles_metadata:
- update_required
should store list of roles that dependends on this role
On deployment stage:
- make update_required list for the whole cluster
- select ready nodes without pending_roles and deploy them
No migration added to keep behaviour on old clusters as it is
DocImpact
Closes-Bug: 1368445
Change-Id: I1735a8b0653101
summary: |
- Redeploy cinder/compute nodes if new controller added + [doc] Redeploy cinder/compute nodes if new controller added |
Changed in fuel: | |
milestone: | none → 6.0 |
assignee: | nobody → Dima Shulyak (dshulyak) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in fuel: | |
importance: | High → Medium |
tags: | added: docs |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
Changed in fuel: | |
assignee: | Dima Shulyak (dshulyak) → Fuel Documentation Team (fuel-docs) |
Changed in fuel: | |
importance: | Medium → High |
tags: | added: area-docs |
Changed in fuel: | |
assignee: | Fuel Documentation Team (fuel-docs) → Svetlana Karslioglu (skarslioglu) |
Changed in fuel: | |
status: | In Progress → Won't Fix |
There is a separate section in ops guide about adding new nodes. This change description should land there.