Enhance API parameters validation when create Bay

Registered by HouMing Wang on 2015-11-17

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 on 2015-12-08
Completed by
HouMing Wang on 2015-12-30

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/api-parameter-validation,n,z

Addressed by: https://review.openstack.org/246609
    Validate baymodel's flavor when create a bay

Addressed by: https://review.openstack.org/250492
    add neutron client support

Addressed by: https://review.openstack.org/250733
    validate external network when create a bay

Addressed by: https://review.openstack.org/251235
    Validate keypair when create a bay

Addressed by: https://review.openstack.org/251428
    Validate image when create a Bay

Addressed by: https://review.openstack.org/252292
    Register neutron client option

Gerrit topic: https://review.openstack.org/#q,topic:bug/1522060,n,z

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.