summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorLovett, Trevor <trevor.lovett@att.com>2018-10-17 14:14:20 -0500
committerLovett, Trevor <trevor.lovett@att.com>2018-10-17 15:01:49 -0500
commit3193a6de8c171baa0b31f00847edd15fb1da0a6d (patch)
treef46255d9e573170fc8c929a6c88ddd027f5c20c8 /docs
parentfd484a3b787b65d3e0073d14f47999f6583f3bcc (diff)
VNFRQTS - Fixing broken links in Use Cases
Issue-ID: VNFRQTS-261 Change-Id: Ieed7a8b2d8f85f4e871d1d47905aa1f465a120dc Signed-off-by: Lovett, Trevor <trevor.lovett@att.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/manual_use_case.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/manual_use_case.rst b/docs/manual_use_case.rst
index 9f04418..cf06467 100644
--- a/docs/manual_use_case.rst
+++ b/docs/manual_use_case.rst
@@ -67,27 +67,27 @@ 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:
- :doc:`The Management Section of the ONAP VNF Guidelines<../../../requirements.git/docs/Chapter7/Configuration-Management.html>`.
+ :doc:`The Management Section of the ONAP VNF Guidelines<../../../vnfrqts/requirements.git/docs/Chapter7/Configuration-Management.html>`.
a. R-41430 is the requirement dictating the need for VNF Healthchecks.
b. The health check may be supported using REST, Ansible, or Chef
* REST health check requirements can be found in the
- :doc:`REST APIs section<../../../requirements.git/docs/Chapter7/Configuration-Management.html#vnf-rest-apis>`
+ :doc:`REST APIs section<../../../vnfrqts./requirements.git/docs/Chapter7/Configuration-Management.html#vnf-rest-apis>`
* The Ansible health check playbook can be found in the
- :doc:`Ansible Playbook Requirements section<../../../requirements.git/docs/Chapter7/Configuration-Management.html#vnf-rest-apis#ansible-playbook-requirements>`
+ :doc:`Ansible Playbook Requirements section<../../../vnfrqts/requirements.git/docs/Chapter7/Configuration-Management.html#vnf-rest-apis#ansible-playbook-requirements>`
2. R-43413 states that a "VNF MUST utilize a modular Heat Orchestration
Template design to support scaling". The description of this design may
be found in the
- :doc:`ONAP VNF Modularity Overview section<../../../requirements.git/docs/Chapter5/Heat/ONAP Heat Orchestration Templates Overview.html#onap-vnf-modularity-overview>`
+ :doc:`ONAP VNF Modularity Overview section<../../../vnfrqts/requirements.git/docs/Chapter5/Heat/ONAP Heat Orchestration Templates Overview.html#onap-vnf-modularity-overview>`
of the Heat Requirements.
a. The ``VF_Module`` to be scaled must be built according to the VNF
Modularity Rules for Incremental Modules
3. Configuration of the VNF must be done via NETCONF, Chef, or Ansible as
- described in the :doc:`Configuration Management<./../../requirements.git/docs/Chapter7/Configuration-Management.html#configuration-management>`
+ described in the :doc:`Configuration Management<../../../vnfrqts/requirements.git/docs/Chapter7/Configuration-Management.html#configuration-management>`
.. |scale_out_design_time| image:: manual_scale_out_design_time.png