diff options
author | 2018-09-01 09:48:13 -0400 | |
---|---|---|
committer | 2018-09-01 09:54:19 -0400 | |
commit | 52b5c09262b614e10bc223dd1811f81760a3337e (patch) | |
tree | 2873aa58ac84715ba8187b7e27e7829044871d3e /docs/guides/onap-developer/architecture/blueprint-enr.rst | |
parent | 40e2182b5f8ce2952abb176bd539bf32ce164464 (diff) |
Cherry pick beijing improvements to master
Replicating changes made when finalizing Beijing branch
in the doc master branch.
Change-Id: Ib1da658aef8cb84f896c6abac23631579ec0b80c
Issue-ID: DOC-280
Signed-off-by: Rich Bennett <rb2745@att.com>
Diffstat (limited to 'docs/guides/onap-developer/architecture/blueprint-enr.rst')
-rw-r--r-- | docs/guides/onap-developer/architecture/blueprint-enr.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/guides/onap-developer/architecture/blueprint-enr.rst b/docs/guides/onap-developer/architecture/blueprint-enr.rst index 8c1616dd8..a3018a195 100644 --- a/docs/guides/onap-developer/architecture/blueprint-enr.rst +++ b/docs/guides/onap-developer/architecture/blueprint-enr.rst @@ -1,5 +1,5 @@ ONAP Blueprint Enrichment -~~~~~~~~~~~~~~~~~~~~~~~~~ +------------------------- The ONAP Beijing release includes four functional enhancements in the areas of manually triggered scaling, change management, and hardware @@ -9,7 +9,7 @@ applicable to any use case; however, to showcase them in a concrete manner, they have been incorporated into VoLTE and vCPE blueprints. Manually Triggered Scaling -^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~ Scale-out and scale-in are two primary benefits of NFV. Scaling can be triggered manually (e.g., by a user or OSS/BSS) or automatically via a @@ -27,7 +27,7 @@ The Beijing release provides the initial support for these capabilities. The community has implemented manually triggered scale-out and scale-in in combination with a specific VNF manager (sVNFM) and demonstrated this with the VoLTE blueprint. An operator uses the Usecase UI (UUI) project -to trigger a scaling operation. UUI communicates with the Service +to trigger a scaleing operation. UUI communicates with the Service Orchestrator (SO). SO uses the VF-C controller, which in turn instructs a vendor-provided sVNFM to implement the scale-out action. @@ -41,7 +41,7 @@ APPC over DMaaP, where APPC picks it up and executes the configuration scale out action on the requested VNF. Change Management -^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~ NFV will bring with it an era of continuous, incremental changes instead of periodic step-function software upgrades, in addition to a constant @@ -69,7 +69,7 @@ the SDN-C controller in terms of running the pre-check, post-check and upgrade through Ansible playbooks. Hardware Platform Awareness (HPA) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Many VNFs have specific hardware requirements to achieve their performance and security goals. These hardware requirements may range |