Add scenario tests based on multiple cells environment
Multiple cells (Nova-Cells-v2) is supported in Pike release.
https:/
This BluePrint provide tests to confirm that the existing Nova API works properly in multiple cells environment.
Example:
* Confirm that the concept of other grouping (Availability Zone, etc.) and the cells can be handled independently.
* When executing the List API, confirm that only the VMs in the belonging cell can be acquired.
* When deleting a VM that failed to be created, confirm that unnecessary records do not remain in the database.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Maho Koshiya
- Direction:
- Needs approval
- Assignee:
- Maho Koshiya
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
We don't really need a blueprint for this work. It would be good to know what gaps in existing testing you think exist. And where do you plan on implementing these tests? In the nova/tests/
If you're considering Tempest, tests there wouldn't really be appropriate because to the end user of the API, they should have no idea if they are talking to a cloud with multiple cells or not, since it's really a deployment issue.
What we don't have today in our CI testing, and that we need someone to work on, is running a devstack multi-node setup with at least two cells. This likely requires some work in the devstack-gate repo to configure devstack per node to tell it which cell it is.
I encourage you to bring this up in a weekly cells v2 meeting for further discussion:
http://
-- mriedem 20171122
