From: Bozawglanian, Hagop (hb755d) Date: Thu, 26 Jul 2018 19:40:00 +0000 (+0000) Subject: VNFRQTS - Updating links in Beijing. X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=refs%2Fchanges%2F51%2F57751%2F2;p=vnfrqts%2Fusecases.git VNFRQTS - Updating links in Beijing. Updating the links and formatting of Beijing. Change-Id: I492dffee6b20bf8c287dccefa660dfede0e2a9a9 Issue-ID: VNFRQTS-266 Signed-off-by: Bozawglanian, Hagop (hb755d) --- diff --git a/docs/manual_use_case.rst b/docs/manual_use_case.rst index c493c7f..6df8ecf 100644 --- a/docs/manual_use_case.rst +++ b/docs/manual_use_case.rst @@ -29,12 +29,12 @@ VNF Impacts ------------------------ For VNFs to make use of the Manual Scaling Capabilities of ONAP, they must support the following functionality: - 1. VNFs must support a Healthcheck as described in: `The Management Section of the ONAP VNF Guidelines `_. + 1. VNFs must support a Healthcheck as described in: `The Management Section of the ONAP VNF Guidelines `_. a. R-31809 is the requirement dictating the need for VNF Healthchecks. - b. The Ansible Healthcheck Playbook description may be found in `The Ansible Standards and Capabilities Section `_. - 2. VNF Heat Templates must be built according the `VNF Modularity Rules `_. + b. The Ansible Healthcheck Playbook description may be found in `The Ansible Standards and Capabilities Section `_. + 2. VNF Heat Templates must be built according the `VNF Modularity Rules `_. a. The VF_Module to be scaled must be built according the VNF Modularity Rules for Incremental Modules. - 3. Configuration of the VNF must be done via NETCONF, Chef, or Ansible as described in `Configuration Management `_. + 3. Configuration of the VNF must be done via NETCONF, Chef, or Ansible as described in `Configuration Management `_. .. |image0| image:: Scale_Out_Workflow.png