Enhance API parameters validation when create Bay
Currently the Magnum API parameters validation is not enough to prevent further API failure, due to non-existed or unprivileged OpenStack resources can be referenced and there're no check/validation toward them. We should check whether the OpenStack resources used by Magnum is existed when create or update Magnum resources. For example, when we create a Baymodel, we should check the existence of image, flavor, network in API parameters. If we didn't do this and Baymodel with non-existed image_id is successfully created, the Bay creation use this Baymodel will fail.
Blueprint information
- Status:
- Complete
- Approver:
- Adrian Otto
- Priority:
- High
- Drafter:
- HouMing Wang
- Direction:
- Approved
- Assignee:
- HouMing Wang
- Definition:
- New
- Series goal:
- Accepted for mitaka
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- HouMing Wang
- Completed by
- HouMing Wang
Related branches
Related bugs
Bug #1519748: bay-creation return 400 Bad Request with a valid fixed-network in baymodel | In Progress |
Bug #1519913: the error message should be more specific to users | New |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Validate baymodel's flavor when create a bay
Addressed by: https:/
add neutron client support
Addressed by: https:/
validate external network when create a bay
Addressed by: https:/
Validate keypair when create a bay
Addressed by: https:/
Validate image when create a Bay
Addressed by: https:/
Register neutron client option
Gerrit topic: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.