...
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
Functionality Name | In or Out | Priority | Stretch |
Clustering placement/query | IN | H | Query capacity and status for a group of resources |
Message bus pub/sub | IN and OUT | H | Publish and subscribe events/notification |
Resource Hierarchy graph | IN | H | Traverse resource Hierarchy in given Cloud |
Container operation | IN | M | Operate containers |
Integration with other project
Functionality Name | In or Out | Priority | Stretch |
| Logging Integration | In | H | Integrate with Logging |
A&AI -Image Manager Integration | In | H | Integrate with A&AI- Image Manager |
| OOF | In | H | Integrate with OOF |
| VFC | In | H | Integrate with VFC on VM status part |
| APPC | In | H | Integrate with APPC on VM status part |
| DCAE | in | H | Integrate with DCAE on Alert/Metrics part |
Epics
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=sanbox and issuetype in (epic) serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...