Support bay status

Registered by yuanying on 2015-01-14

Bay is created by heat, so bay status should be synchronised by heat.
For example,

- bay should be destroy after heat stack is destroyed.
- pod/service/rc can be created when heat stack is created

Blueprint information

Status:
Complete
Approver:
Adrian Otto
Priority:
Medium
Drafter:
yuanying
Direction:
Approved
Assignee:
yuanying
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
None
Started by
Hua Wang on 2016-04-11
Completed by
Hua Wang on 2016-04-11

Related branches

Sprints

Whiteboard

T-Shirt Size: L

The following states shall be considered valid.

CREATE_IN_PROGRES
CREATE_FAILED
CREATED
UPDATE_IN_PROGRESS
UPDATE_FAILED
UPDATED
DELETE_IN_PROGRESS
DELETE_FAILED
DELETED

Note: CREATED is reached after all pods/services/rcs outstanding to be created in a bay are actually created in the bay.

Here is the implementation discussion in the mailing list: http://lists.openstack.org/pipermail/openstack-dev/2015-March/058898.html

Gerrit topic: https://review.openstack.org/#q,topic:bp/magnum-bay-status,n,z

Addressed by: https://review.openstack.org/153931
    Add status attribute to bay

Gerrit topic: https://review.openstack.org/#q,topic:bay-status,n,z

Addressed by: https://review.openstack.org/159546
    When polling heat set bay status

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.