diff options
Diffstat (limited to 'docs/guides/onap-developer/architecture/blueprint-enr.rst')
| -rw-r--r-- | docs/guides/onap-developer/architecture/blueprint-enr.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/guides/onap-developer/architecture/blueprint-enr.rst b/docs/guides/onap-developer/architecture/blueprint-enr.rst index 404f7d0df..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 @@ -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 |