Replace cluster size with a new property desired_capacity
The original meaning of the *size* property of a cluster is specifying the current count of nodes belong to this cluster. But actually we can always get this value by counting the length of nodes list. So it is not that necessary to maintain this field in DB. At the same time, we should add a new property *desired_capacity* in Cluster model since it represents the goal of all cluster operations(e.g. creating, scaling). So plan is removing *size* property and adding *desired_capacity* into Cluster DB model.
Blueprint information
- Status:
- Complete
- Approver:
- Qiming Teng
- Priority:
- High
- Drafter:
- Yanyan Hu
- Direction:
- Approved
- Assignee:
- Yanyan Hu
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Yanyan Hu
- Completed by
- Yanyan Hu
Related branches
Related bugs
Sprints
Whiteboard
We may need to check whether scaling operations will always change the desired capacity and also how scaling-policies collaborate with health-policy on this new property.
Gerrit topic: https:/
Addressed by: https:/
Replace cluster size with new property desired_capacity