Allow bay-update to update the node count
Permit bay-update of the count-count parameter to modify an existing bay to have more or less nodes as identified by the new node-count.
Blueprint information
- Status:
- Complete
- Approver:
- Adrian Otto
- Priority:
- High
- Drafter:
- Steven Dake
- Direction:
- Approved
- Assignee:
- hongbin
- Definition:
- Approved
- Series goal:
- Accepted for milestone-2
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- hongbin
- Completed by
- hongbin
Related branches
Related bugs
Sprints
Whiteboard
Size estimate: Small
Hongbin: Implementing this feature needs two steps: 1) change the Heat templates to support scaling, 2) change magnum api and conductor to support node count update. Implementing #1 needs to submit changes to larsks repo, which I am not sure if it will be accepted. If #1 go through, implementing #2 should be straightforward in my opinion.
Note - I am sure larsks would take a stack update feature for this. That said, we may run into a point where we want to make changes that upstream wont accept. I can't think of any now, but if they do occur, we already maintain a cherry-picked fork, so carrying our own work seems ok, as long as we rebase the rest of the work going into that repo (this is how kernel.org operates) - sdake
Gerrit topic: https:/
Addressed by: https:/
Refactor bay_create at k8s conductor
Addressed by: https:/
WIP: Implement update bay node_count
A pull request to larsk repo:
https:/
Addressed by: https:/
Move bay defintion extraction code
Addressed by: https:/
Allow Json patch to take an integer value
Addressed by: https:/
Add support for updating a bay
