...
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Development Status
...
Rel I Project REQ Tickets
JIRAJira server ONAP Jira columnIds issuekey,summary,assignee,reporter,status columns key,summary,assignee,reporter,status maximumIssues 1000 jqlQuery key = REQ-716 or ("Epic Link" = REQ-716 and project = REQ) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Story Tickets
arch review,tsc priority,scope status,t-shirt size,m1 approval,m2 approval,m3 approval,m4 approval,rc0 approval,statusJira server ONAP JIRA columns key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions maximumIssues 100 jqlQuery "Epic Link" = REQ-716 and project != "REQ"
|
Rel J Project REQ Tickets
Jira server ONAP JIRAJira columnIds issuekey,summary,assignee,reporter,customfield_10701,customfield_10702,customfield_10703,status columns key,summary,assignee,reporter,integration test plan status,integration test status,integration test time to completeIntegration Test Plan Status,Integration Test Status,Integration Test Time to Complete,status maximumIssues 1000 jqlQuery key = REQ-994 or ("Epic Link" = REQ-716 994 and project = REQ ) serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Backlog Tickets for Rel J
Jira server ONAP JIRAJira columnIds issuekey,summary,issuetype,created,updated,assignee,reporter,priority,status,resolution,subtasks columns key,summary,type,created,updated,assignee,reporter,priority,status,resolution,subtasks,fixversions maximumIssues 100 jqlQuery "Epic Link" = REQ-716 and project != "REQ" POLICY-3777 or "Epic Link" = POLICY-2952 serverId 425b2b0a-557c-3c0c-b515-579789cceedb
JIRA Relelationships and Sequencing
TESTING
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
End to End flow to be Tested
Test Cases and Status
...
NOT YET TESTED
...
COMPLETE
...
PARTIALLY COMPLETE
Function Description
TOSCA Defined Control Loops: Architecture and Design
How to run the Front-End GUI
Investigation of Clamp Common Parameter Handling and Validation.
Investigation of CLAMP for Tosca Control Loop Integration - In Progress
JIRA Relelationships and Sequencing
Persistence Policy Models using JPA/JDBC/Eclipselink/MariaDB
Rough wireframe for TOSCA CL Monitoring GUI
The CLAMP Kubernetes Participant
TOSCA
Reference
...
based Control Loops with the existing CLAMP code in the Policy Framework
TOSCA Control Loops: Scratchpad Page
TESTING
Roadmap
