diff options
| author |   Eric Debeau <eric.debeau@orange.com> | 2018-06-06 16:53:33 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2018-06-06 16:53:33 +0000 |
| commit | 1cc2e3b4419d101cce60f7c24ad6a83a0797c227 (patch) | |
| tree | ab760872d22ced267dd27e3b685582da6722017f | |
| parent | cab1b00abddf5fdb682c0964871105f9cb19b121 (diff) | |
| parent | 2bbbd7624052699746f4752ea961b6e1adb376c7 (diff) | |
Merge "Fix Arch/blueprint Doc formatting" into beijing
| -rw-r--r-- | docs/guides/onap-developer/architecture/blueprint-enr.rst | 8 | ||||
| -rw-r--r-- | docs/guides/onap-developer/architecture/onap-architecture.rst | 2 |
2 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 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 diff --git a/docs/guides/onap-developer/architecture/onap-architecture.rst b/docs/guides/onap-developer/architecture/onap-architecture.rst index 9bd6d0512..de921a884 100644 --- a/docs/guides/onap-developer/architecture/onap-architecture.rst +++ b/docs/guides/onap-developer/architecture/onap-architecture.rst @@ -587,7 +587,7 @@ faster than any one product could on its own. .. |image3| image:: media/ONAP-oom.png :width: 2.28472in :height: 2.30625in -.. |image4| image:: media/ONAP-closedloop.jpeg +.. |image4| image:: media/ONAP-closedloop.png :width: 6in :height: 2.6in .. |image5| image:: media/ONAP-vcpe.png |