diff options
| -rw-r--r-- | docs/Chapter1.rst | 5 | ||||
| -rw-r--r-- | docs/Chapter2.rst | 5 | ||||
| -rw-r--r-- | docs/Chapter3.rst | 5 | ||||
| -rw-r--r-- | docs/Chapter4.rst | 13 | ||||
| -rw-r--r-- | docs/Chapter5.rst | 7 | ||||
| -rw-r--r-- | docs/Chapter6.rst | 5 | ||||
| -rw-r--r-- | docs/Chapter7.rst | 8 | ||||
| -rw-r--r-- | docs/Chapter8.rst | 7 |
8 files changed, 48 insertions, 7 deletions
diff --git a/docs/Chapter1.rst b/docs/Chapter1.rst index 040611d..4b3d522 100644 --- a/docs/Chapter1.rst +++ b/docs/Chapter1.rst @@ -1,3 +1,8 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + **1. Purpose** ============== - The purpose of these requirements is to accelerate adoption of VNF best practices which will increase innovation, minimize customization needed to onboard VNFs as well as reduce implementation complexity, time and cost for all impacted stakeholders. diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index 1a00931..6237e38 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -1,3 +1,8 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + **2. Scope** ============ - The audience for this document are VNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle management requirements for VNFs to be compliant with ONAP. diff --git a/docs/Chapter3.rst b/docs/Chapter3.rst index 5681b4c..88cddeb 100644 --- a/docs/Chapter3.rst +++ b/docs/Chapter3.rst @@ -1,3 +1,8 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + **3. Introduction** ==================== - These requirements are specific to the Amsterdam release of ONAP. It is the initial release of requirements based on a merge of the Open-O and OpenECOMP requirements. diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst index 7beaa45..e970e1e 100644 --- a/docs/Chapter4.rst +++ b/docs/Chapter4.rst @@ -1,4 +1,9 @@ -**4. VNF Development Requirements** +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + +**4. VNF Development Requirements** ==================================== a. VNF Design @@ -108,11 +113,11 @@ applications. Application Resilient Error Handling Requirements -* R-26371 The VNF **MUST** detect connectivity failure for inter VNFC instance and intra/inter VNF and re-establish connectivity automatically to maintain the VNF without manual intervention to provide service continuity. +* R-26371 The VNF **MUST** detect communication failure for inter VNFC instance and intra/inter VNF and re-establish communication automatically to maintain the VNF without manual intervention to provide service continuity. * R-18725 The VNF **MUST** handle the restart of a single VNFC instance without requiring all VNFC instances to be restarted. * R-06668 The VNF **MUST** handle the start or restart of VNFC instances in any order with each VNFC instance establishing or re-establishing required connections or relationships with other VNFC instances and/or VNFs required to perform the VNF function/role without requiring VNFC instance(s) to be started/restarted in a particular order. * R-80070 The VNF **MUST** handle errors and exceptions so that they do not interrupt processing of incoming VNF requests to maintain service continuity. -* R-32695 The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior. +* R-32695 The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior,where the interface and/or functional specification allows for altering behaviour. * R-48356 The VNF **MUST** fully exploit exception handling to the extent that resources (e.g., threads and memory) are released when no longer needed regardless of programming language. * R-67918 The VNF **MUST** handle replication race conditions both locally and geo-located in the event of a data base instance failure to maintain service continuity. * R-36792 The VNF **MUST** automatically retry/resubmit failed requests made by the software to its downstream system to increase the success rate. @@ -214,7 +219,7 @@ Monitoring & Dashboard Requirements * R-48917 The VNF **MUST** monitor for and alert on (both sender and receiver) errant, running longer than expected and missing file transfers, so as to minimize the impact due to file transfer errors. * R-28168 The VNF **SHOULD** use an appropriately configured logging level that can be changed dynamically, so as to not cause performance degradation of the VNF due to excessive logging. * R-87352 The VNF **SHOULD** utilize Cloud health checks, when available from the Network Cloud, from inside the application through APIs to check the network connectivity, dropped packets rate, injection, and auto failover to alternate sites if needed. -* R-16560 The VNF **MUST** conduct a resiliency impact assessment for all inter/intra-connectivity points in the VNF to provide an overall resiliency rating for the VNF to be incorporated into the software design and development of the VNF. +* R-16560 The VNF **SHOULD** conduct a resiliency impact assessment for all inter/intra-connectivity points in the VNF to provide an overall resiliency rating for the VNF to be incorporated into the software design and development of the VNF. c. VNF Security =============== diff --git a/docs/Chapter5.rst b/docs/Chapter5.rst index eff10e0..55d49c7 100644 --- a/docs/Chapter5.rst +++ b/docs/Chapter5.rst @@ -1,4 +1,9 @@ -:tocdepth: 2 +:tocdepth: 2 + +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + **5. VNF Modeling Requirements** ===================================== diff --git a/docs/Chapter6.rst b/docs/Chapter6.rst index ad672b6..aef6849 100644 --- a/docs/Chapter6.rst +++ b/docs/Chapter6.rst @@ -1,3 +1,8 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + **6. Infrastructure Requirements** ===================================== diff --git a/docs/Chapter7.rst b/docs/Chapter7.rst index b90fc03..8d88bab 100644 --- a/docs/Chapter7.rst +++ b/docs/Chapter7.rst @@ -1,4 +1,10 @@ :tocdepth: 2 + +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + **7. ONAP Management Requirements** ===================================== @@ -1049,4 +1055,4 @@ ONAP destinations can be addressed by URLs for RESTful data PUT. Future data set .. |image3| image:: Protocol_Buffers_Driven_Model.png :width: 4.74in - :height: 3.3in
\ No newline at end of file + :height: 3.3in diff --git a/docs/Chapter8.rst b/docs/Chapter8.rst index fbe2d89..6c8b01d 100644 --- a/docs/Chapter8.rst +++ b/docs/Chapter8.rst @@ -1,4 +1,9 @@ -**8. Appendix** +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. Copyright 2017 AT&T Intellectual Property. All rights reserved. + + +**8. Appendix** =============== a. – Chef JSON Key Value Description |