VNF Management Badge
- Steven wright
The VNF Requirements in Ch7 as of mid August (there are some changes pending for section 7.4 and 7.5 in VNFRQTS-278 - Update Section 7.4 for VES support in Casablanca In Progress and VNFRQTS-289 - PNF plug N play In Progress )
Section | Number of Reqts | Topic |
|---|---|---|
7.1 | 0 | Service Design |
7.2 | 55 | VNF On-boarding and package management |
7.2.1 | 0 | Design Definition |
7.2.2 | 9 | Resource Description |
7.2.3 | 9 | Resource Configuration |
7.2.4 | 18 | Resource Control Loop |
7.2.5 | 7 | Compute, Network, and Storage Requirements |
7.2.6 | 3 | Testing |
7.2.7 | 9 | Licensing Requirements |
7.3 | 114 | Configuration Management |
7.3.1 | 20 | Controller Interactions With VNF |
7.3.2 | 63 | NETCONF Standards and Capabilities |
7.3.2.1 | 63 | VNF Configuration via NETCONF Requirements |
7.3.2.1.1 | 2 | Configuration Management |
7.3.2.1.2 | 61 | NETCONF Server Requirements |
7.3.2.1.2 | 44 | (other- no subheading) ** needs further breakdown/summarization |
7.3.2.1.2 | 11 | Yang Models |
7.3.2.1.2 | 6 | Netconf RFCs |
7.3.3 | 1 | VNF REST APIs |
7.3.4 | 14 | Chef Standards and Capabilities |
7.3.5 | 16 | Ansible Standards and Capabilities |
7.3.6 | 0 | Support of Controller Commands And Southbound Protocols |
7.4 | 27 | Monitoring & Management |
7.4.1 | 0 | Data Model for Event Records |
7.4.2 | 0 | Event Records - Data Structure Description |
7.4.3 | 0 | Data Structure Specification of the Event Record |
7.4.4 | 0 | Transports and Protocols Supporting Resource Interfaces |
7.4.5 | 27 | Monitoring & Management Requirements |
7.4.5.1 | 1 | VNF telemetry via standardized interface |
7.4.5.2 | 0 | Encoding and Serialization |
7.4.5.3 | 1 | JSON |
7.4.5.4 | 0 | KV-GPB/GPB |
7.4.5.5 | 1 | Reporting Frequency |
7.4.5.6 | 8 | Addressing and Delivery Protocol |
7.4.5.7 | 9 | Asynchronous and Synchronous Data Delivery |
7.4.5.8 | 4 | Security |
7.4.5.9 | 3 | Bulk Performance Measurement |
Naively mapping sections to pulldowns would still have (Red) sections with more than 20 reqts, and would need some further breakdown or summarization. pulldowns with 0 or 1 requirement do not make sense, and should be consolidated. This would suggest ~16 pulldowns with an addition pulldown to consolidate the 4 sections with a single reqt, and some further breakdown/ summarization of the 44 reqts in 7.3.2.1.2. Something like:
Section # | Num. of reqts | Pulldown titlep |
|---|---|---|
7.2.2 | 9 | Resource Description |
7.2.3 | 9 | Resource Configuration |
7.2.4 | 18 | Resource Control Loop |
7.2.5 | 7 | Compute, Network, and Storage Requirements |
7.2.6 | 3 | Testing |
7.2.7 | 9 | Licensing Requirements |
7.3.1 | 20 | Controller Interactions With VNF |
7.3.2.1.2 | 11 | Yang Models |
7.3.2.1.2 | 6 | Netconf RFCs |
7.3.4 | 14 | Chef Standards and Capabilities |
7.3.5 | 16 | Ansible Standards and Capabilities |
7.4.5.6 | 8 | Addressing and Delivery Protocol |
7.4.5.7 | 9 | Asynchronous and Synchronous Data Delivery |
7.4.5.8 | 4 | Security |
7.4.5.9 | 3 | Bulk Performance Measurement |
7.3.3 / 7.4.5.1 / 7.4.5.3 / 7.4.5.5 | 4 | VNF REST APIs / VNF telemetry via standardized interface / JSON / Reporting Frequency |
7.3.2.1.2 | 44 | (other- no subheading) ** needs further breakdown/summarization |