Standard Life-Cycle Operations
- Srinivasa Vellanki
Target release | Casablanca |
|---|---|
Epic | |
Document status | DRAFT |
Document owner | @Srinivasa Vellanki |
Designer | |
Developers | |
QA |
Goals
Enable Designers(Service Designer, VNF Owner or TechOps) to be able to specify the Service, NF(VNF & PNF) and Network Lifecycle Operations
Background and strategic fit
Assumptions
.
Requirements
Title | User Story | Importance | Notes | |
|---|---|---|---|---|
| 1 | Output Parameters for Operations | As a Service Designer I should be able to specify the Output Parameters of Operations | Must Have | |
| 2 | Service Operations | As a Service Designer I should be able to specify the Operations supported by a Service | Must Have |
|
| 3 | VNFC Operations | As a Service Designer I should be able to specify the Operations supported by a VNFC | Must Have |
|
| 4 | PNF Operations | As a Service Designer I should be able to specify the Operations supported by a PNF | Nice to Have |
|
| 5 | Network Operations | As a Service Designer I should be able to specify the Operations supported by a Network | Nice to Have |
|
| 6 | Assign Workflows | Assign a predefined workflow to an Operation to enable re-use of workflows | Must Have |
|
| 7 | Certify Service Operations | As part of Service certification, verify if all the Inputs and Outputs of the Operations are mapped | Must Have |
|
| 8 | Certify VNF Operations | As part of VNF certification, verify if all the Inputs and Outputs of the Operations are mapped | Must Have |
|
| 9 | Certify VNFC Operations | As part of VNF certification, verify if all the Inputs and Outputs of the VNFC Operations are mapped | Must Have |
|
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
|---|---|
Do we need to support Network Operations? Are there any other operations other than Create and Delete? |