diff options
| -rw-r--r-- | docs/featureprojects.rst | 4 | ||||
| -rw-r--r-- | docs/how-to-use-docs/documentation-guide.rst | 82 | ||||
| -rw-r--r-- | docs/how-to-use-docs/include-documentation.rst | 20 | ||||
| -rw-r--r-- | docs/index.rst | 10 | ||||
| -rw-r--r-- | docs/release/installation.introduction.rst | 58 | ||||
| -rw-r--r-- | docs/release/overview.rst | 17 | ||||
| -rw-r--r-- | docs/release/userguide.introduction.rst | 66 |
7 files changed, 141 insertions, 116 deletions
diff --git a/docs/featureprojects.rst b/docs/featureprojects.rst index c35850966..ebab13b19 100644 --- a/docs/featureprojects.rst +++ b/docs/featureprojects.rst @@ -6,7 +6,6 @@ ARMband .. toctree:: :maxdepth: 1 - ../submodules/armband/docs/releasenotes/index ../submodules/armband/docs/installationprocedure/index Barometer @@ -14,7 +13,6 @@ Barometer .. toctree:: :maxdepth: 1 - ../submodules/barometer/docs/release/release-notes/index ../submodules/barometer/docs/release/configguide/index ../submodules/barometer/docs/release/userguide/index @@ -25,7 +23,6 @@ Copper :maxdepth: 1 ../submodules/copper/docs/design/index - ../submodules/copper/docs/releasenotes/index ../submodules/copper/docs/userguide/index ../submodules/copper/docs/installationprocedure/index @@ -37,7 +34,6 @@ Doctor ../submodules/doctor/docs/scenario/index ../submodules/doctor/docs/installationprocedure/index ../submodules/doctor/docs/userguide/index - ../submodules/doctor/docs/releasenotes/index Domino -------- diff --git a/docs/how-to-use-docs/documentation-guide.rst b/docs/how-to-use-docs/documentation-guide.rst index fe5688a92..fb056d4b8 100644 --- a/docs/how-to-use-docs/documentation-guide.rst +++ b/docs/how-to-use-docs/documentation-guide.rst @@ -2,7 +2,9 @@ Documentation Guide ===================== -This page intends to cover the documentation handling for OPNFV. OPNFV projects are expected to create a variety of document types, according to the nature of the project. Some of these are common to projects that develop/integrate features into the OPNFV platform, e.g. Installation Instructions and User/Configurations Guides. Other document types may be project-specific. +This page intends to cover the documentation handling for OPNFV. OPNFV projects are expected to create a variety of document types, +according to the nature of the project. Some of these are common to projects that develop/integrate features into the OPNFV platform, e.g. +Installation Instructions and User/Configurations Guides. Other document types may be project-specific. .. contents:: :depth: 3 @@ -12,13 +14,17 @@ Getting Started with Documentation for Your Project ---------------------------------------------------- OPNFV documentation is automated and integrated into our git & gerrit toolchains. -We use RST document templates in our repositories and automatically render to HTML and PDF versions of the documents in our artifact store, our WiKi is also able to integrate these rendered documents directly allowing projects to use the revision controlled documentation process for project information, content and deliverables. +We use RST document templates in our repositories and automatically render to HTML and PDF versions of the documents in our artifact +store, our WiKi is also able to integrate these rendered documents directly allowing projects to use the revision controlled documentation +process for project information, content and deliverables. Read :ref:`this page <include-documentation>` which elaborates on how documentation is to be included within opnfvdocs. Licencing your documentation ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -All contributions to the OPNFV project are done in accordance with the OPNFV licensing requirements. Documentation in OPNFV is contributed in accordance with the `Creative Commons 4.0 <https://creativecommons.org/licenses/by/4.0/>`_ licence. -All documentation files need to be licensed using the creative commons licence. The following example may be applied in the first lines of all contributed RST files: +All contributions to the OPNFV project are done in accordance with the OPNFV licensing requirements. Documentation in OPNFV is contributed +in accordance with the `Creative Commons 4.0 <https://creativecommons.org/licenses/by/4.0/>`_ licence. +All documentation files need to be licensed using the creative commons licence. The following example may be applied in the first lines of +all contributed RST files: .. code-block:: bash @@ -26,39 +32,54 @@ All documentation files need to be licensed using the creative commons licence. .. http://creativecommons.org/licenses/by/4.0 .. (c) <optionally add copywriters name> -These lines will not be rendered in the html and pdf files. +Or if you want to use the `SPDX https://spdx.org/>`_ Shorthand vs. the Creative Commons URL + +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. SPDX-License-Identifier: CC-BY-4.0 +.. (c) <optionally add copywriters name> + + These lines will not be rendered in the html and pdf files. How and where to store the document content files in your repository ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -All documentation for your project should be structured and stored in the :code:`<repo>/docs/` directory. The documentation toolchain will look in these directories and be triggered on events in these directories when generating documents. +All documentation for your project should be structured and stored in the :code:`<repo>/docs/` directory. The documentation toolchain will +look in these directories and be triggered on events in these directories when generating documents. Document structure and contribution ------------------------------------- -A general structure is proposed for storing and handling documents that are common across many projects but also for documents that may be project specific. The documentation is divided into three areas Release, Development and Testing. Templates for these areas can be found under :code:`opnfvdocs/docs/templates/`. +A general structure is proposed for storing and handling documents that are common across many projects but also for documents that may be +project specific. The documentation is divided into three areas Release, Development and Testing. Templates for these areas can be found +under :code:`opnfvdocs/docs/templates/`. -Project teams are encouraged to use templates provided by the opnfvdocs project to ensure that there is consistency across the community. Following representation shows the expected structure: +Project teams are encouraged to use templates provided by the opnfvdocs project to ensure that there is consistency across the community. +Following representation shows the expected structure: :: - docs/ - ├── development - │ ├── design - │ ├── overview - │ └── requirements - ├── release - │ ├── configguide - │ ├── installation - │ ├── release-notes - │ ├── scenarios - │ │ └── scenario.name - │ └── userguide - └── testing + docs/ + ├── development + │ ├── design + │ ├── overview + │ └── requirements + ├── release + │ ├── configguide + │ ├── installation + │ ├── release-notes + │ ├── scenarios + │ │ └── scenario.name + │ └── userguide + └── testing + ├── developer + └── user Release documentation ^^^^^^^^^^^^^^^^^^^^^^^^ -Release documentation is the set of documents that are published for each OPNFV release. These documents are created and developed following the OPNFV release process and milestones and should reflect the content of the OPNFV release. -These documents have a master index.rst file in the <opnfvdocs> repository and extract content from other repositories. To provide content into these documents place your <content>.rst files in a directory in your repository that matches the master document and add a reference to that file in the correct place in the corresponding index.rst file in :code:`opnfvdocs/docs/release/`. +Release documentation is the set of documents that are published for each OPNFV release. These documents are created and developed +following the OPNFV release process and milestones and should reflect the content of the OPNFV release. +These documents have a master index.rst file in the <opnfvdocs> repository and extract content from other repositories. +To provide content into these documents place your <content>.rst files in a directory in your repository that matches the master document +and add a reference to that file in the correct place in the corresponding index.rst file in :code:`opnfvdocs/docs/release/`. **Platform Overview**: :code:`opnfvdocs/docs/release/overview` @@ -90,11 +111,21 @@ These documents have a master index.rst file in the <opnfvdocs> repository and e Testing documentation ^^^^^^^^^^^^^^^^^^^^^^^^ -*Structure TBD together with test projects* +Documentation created by test projects can be stored under two different sub directories /user or /developemnt. +Release notes will be stored under <repo>/docs/release/release-notes + +**User documentation**: :code:`<repo>/testing/user/` +Will collect the documentation of the test projects allowing the end user to perform testing towards a OPNFV SUT +e.g. Functest/Yardstick/Vsperf/Storperf/Bottlenecks/Qtip installation/config & user guides. + +**Development documentation**: :code:`<repo>/testing/developent/` +Will collect documentation to explain how to create your own test case and leverage existing testing frameworks e.g. developer guides. Development Documentation ^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Documentation not aimed for any specific release such as design documentation, project overview or requirement documentation can be stored under /docs/development. Links to generated documents will be dislayed under Development Documentaiton section on docs.opnfv.org. You are encouraged to establish the following basic structure for your project as needed: +Project specific documents such as design documentation, project overview or requirement documentation can be stored under +/docs/development. Links to generated documents will be dislayed under Development Documentaiton section on docs.opnfv.org. +You are encouraged to establish the following basic structure for your project as needed: **Requirement Documentation**: :code:`<repo>/docs/development/requirements/` @@ -108,4 +139,3 @@ Documentation not aimed for any specific release such as design documentation, p **Project overview**: :code:`<repo>/docs/development/overview` - Folder for any project specific documentation. - diff --git a/docs/how-to-use-docs/include-documentation.rst b/docs/how-to-use-docs/include-documentation.rst index 4cf9f2757..1430b946d 100644 --- a/docs/how-to-use-docs/include-documentation.rst +++ b/docs/how-to-use-docs/include-documentation.rst @@ -1,14 +1,14 @@ .. _include-documentation: -============================= +============================ Including your Documentation -============================= +============================ .. contents:: :depth: 3 :local: In your project repository ----------------------------- +-------------------------- Add your documentation to your repository in the folder structure and according to the templates listed above. The documentation templates you @@ -34,7 +34,7 @@ the documentation to the project repository. git review In OPNFVDocs Composite Documentation --------------------------------------- +------------------------------------ In toctree +++++++++++ @@ -70,7 +70,7 @@ it, example: <submodules/path-to-your-file> As Hyperlink -+++++++++++++ +++++++++++++ It's pretty common to want to reference another location in the OPNFV documentation and it's pretty easy to do with @@ -126,8 +126,8 @@ the opnfvdocs team for review and integration. Be sure to add the project leader of the opnfvdocs project as a reviewer of the change you just pushed in gerrit. -'doc8' Validation --------------------------------------- +'doc8' Validation +----------------- It is recommended that all rst content is validated by `doc8 <https://pypi.python.org/pypi/doc8>`_ standards. To validate your rst files using doc8, install doc8. @@ -143,10 +143,10 @@ doc8 can now be used to check the rst files. Execute as, Testing: Build Documentation Locally ---------------------------------------- +------------------------------------ Composite OPNFVDOCS documentation -+++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++ To build whole documentation under opnfvdocs/, follow these steps: Install virtual environment. @@ -181,7 +181,7 @@ Update submodules, build documentation using tox & then open using any browser. .. note:: Make sure to run `tox -edocs` and not just `tox`. Individual project documentation -+++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++ To test how the documentation renders in HTML, follow these steps: Install virtual environment. diff --git a/docs/index.rst b/docs/index.rst index d89f379b4..777afbfb3 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -29,11 +29,11 @@ Testing Documentation .. toctree:: :maxdepth: 1 - submodules/functest/docs/userguide/index - submodules/bottlenecks/docs/userguide/index - submodules/yardstick/docs/userguide/index - submodules/vswitchperf/docs/index - submodules/storperf/docs/index + submodules/functest/docs/testing/user/index + submodules/bottlenecks/docs/testing/user/index + submodules/yardstick/docs/testing/user/index + submodules/vswitchperf/docs/testing/user/index + submodules/storperf/docs/testing/user/index Development Documentation diff --git a/docs/release/installation.introduction.rst b/docs/release/installation.introduction.rst index 904c2d66b..ab043c4a2 100644 --- a/docs/release/installation.introduction.rst +++ b/docs/release/installation.introduction.rst @@ -29,7 +29,7 @@ it is important to understand your required target platform capabilities before configuring your target scenario. An OPNFV installation requires either a physical, or virtual, infrastructure environment as defined -in the `Pharos specification <http://artifacts.opnfv.org/pharos/colorado/2.0/docs/specification/index.html>`_. +in the `Pharos specification <http://artifacts.opnfv.org/pharos/colorado/2.0/docs/specification/index.html>`. When configuring a physical infrastructure it is strongly advised to follow the Pharos configuration guidelines. @@ -45,14 +45,14 @@ where each scenario will include different source components or configurations. To learn more about the scenarios supported in the Colorado release refer to the scenario description documents provided: -- Accelerated OVS `os-nosdn-ovs <http://artifacts.opnfv.org/ovsnfv/colorado/2.0/docs/scenarios_os-nosdn-ovs/index.html>`_ -- Layer 3 overlay using opendaylight `os-odl-l2-bgpvpn <http://artifacts.opnfv.org/sdnvpn/colorado/2.0/docs/scenarios_os-odl_l2-bgpvpn/index.html>`_ -- FD.io based forwarding using opendaylight SDN `os-odl-12-fdio-noha <http://artifacts.opnfv.org/fds/colorado/2.0/scenarios_os-odl_l2-fdio-noha/index.html>`_ -- High availability service function chaining `os-odl-l2-sfc-ha <http://artifacts.opnfv.org/sfc/colorado/2.0/docs/scenarios_os-odl_l2-sfc-ha/index.html>`_ -- Service function chaining `os-odl-l2-sfc-noha <http://artifacts.opnfv.org/sfc/colorado/2.0/docs/scenarios_os-odl_l2-sfc-noha/index.html>`_ -- Accelerated KVM hypervisor `os-nosdn-kvm-ha <http://artifacts.opnfv.org/kvmfornfv/colorado/2.0/docs/scenarios_os-nosdn-kvm-ha/index.html>`_ -- LXD container hypervisor `os-nosdn-lxd-noha <http://artifacts.opnfv.org/joid/colorado/2.0/docs/scenarios_os-nosdn-lxd-noha/index.html>`_ -- High Availability LXD container hypervisor `os-nosdn-lxd-ha <http://artifacts.opnfv.org/joid/colorado/2.0/docs/scenarios_os-nosdn-lxd-ha/index.html>`_ +- Accelerated OVS `os-nosdn-ovs <http://artifacts.opnfv.org/ovsnfv/colorado/2.0/docs/scenarios_os-nosdn-ovs/index.html>` +- Layer 3 overlay using opendaylight `os-odl-l2-bgpvpn <http://artifacts.opnfv.org/sdnvpn/colorado/2.0/docs/scenarios_os-odl_l2-bgpvpn/index.html>` +- FD.io based forwarding using opendaylight SDN `os-odl-12-fdio-noha <http://artifacts.opnfv.org/fds/colorado/2.0/scenarios_os-odl_l2-fdio-noha/index.html>` +- High availability service function chaining `os-odl-l2-sfc-ha <http://artifacts.opnfv.org/sfc/colorado/2.0/docs/scenarios_os-odl_l2-sfc-ha/index.html>` +- Service function chaining `os-odl-l2-sfc-noha <http://artifacts.opnfv.org/sfc/colorado/2.0/docs/scenarios_os-odl_l2-sfc-noha/index.html>` +- Accelerated KVM hypervisor `os-nosdn-kvm-ha <http://artifacts.opnfv.org/kvmfornfv/colorado/2.0/docs/scenarios_os-nosdn-kvm-ha/index.html>` +- LXD container hypervisor `os-nosdn-lxd-noha <http://artifacts.opnfv.org/joid/colorado/2.0/docs/scenarios_os-nosdn-lxd-noha/index.html>` +- High Availability LXD container hypervisor `os-nosdn-lxd-ha <http://artifacts.opnfv.org/joid/colorado/2.0/docs/scenarios_os-nosdn-lxd-ha/index.html>` Installation Procedure @@ -64,10 +64,10 @@ support for the OPNFV Colorado release are; Apex, Compass4nfv, Fuel and Joid. The instructions for each toolchain can be found in these links: -- `Apex installation instruction <http://artifacts.opnfv.org/apex/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Compass4nfv installation instruction <http://artifacts.opnfv.org/compass4nfv/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Fuel installation instruction <http://artifacts.opnfv.org/fuel/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Joid installation instruction <http://artifacts.opnfv.org/joid/colorado/2.0/docs/installationprocedure/index.html>`_ +- :ref:`Apex installation instruction <apex-installation>` +- :ref:`Compass4nfv installation instruction <compass4nfv-installation>` +- :ref:`Fuel installation instruction <fuel-installation>` +- :ref:`Joid installation instruction <joid-installation>` OPNFV Test Frameworks @@ -81,12 +81,12 @@ select the right test suites to run on your platform from the available projects Many of the OPNFV test project provide user-guide documentation and installation instructions as provided below: -- `Functest user guide <http://artifacts.opnfv.org/functest/colorado/2.0/docs/userguide/index.html>`_ -- `Yardstick user guide <http://artifacts.opnfv.org/yardstick/colorado/2.0/docs/userguide/index.html>`_ -- `vSwitchPerf user guide <http://artifacts.opnfv.org/vswitchperf/colorado/2.0/index.html>`_ -- `Software Fastpath Service Quality Metrics (SFQM) user guide <http://artifacts.opnfv.org/fastpathmetrics/colorado/2.0/index.html>`_ -- `Bottlenecks user guide <http://artifacts.opnfv.org/bottlenecks/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Storage Performance Benchmarking for NFVI (StorPerf) user guide <http://artifacts.opnfv.org/storperf/colorado/2.0/docs/userguide/index.html>`_ +- :ref:`Functest user guide <functest-userguide>` +- :ref:`Yardstick user guide <yardstick-userguidde>` +- :ref:`vSwitchPerf user guide <vswitchperf-userguide>` +- :ref:`Software Fastpath Service Quality Metrics (SFQM) user guide <fastpathmetrics-userguide>` +- :ref:`Bottlenecks user guide <bottlenecks-userguide>` +- :ref:`Storage Performance Benchmarking for NFVI (StorPerf) user guide <storperf-userguide>` Security Notes @@ -95,13 +95,13 @@ Security Notes The following patches were applied to fix security issues discovered in opnfv projects, during the c-release cycle. -- `Removal of private keys <https://gerrit.opnfv.org/gerrit/#/c/21995/>`_ -- `Fix security issues of eval-s in testapi <https://gerrit.opnfv.org/gerrit/#/c/20751/>`_ -- `Implements use of yaml.safe_load <https://gerrit.opnfv.org/gerrit/#/c/20911/>`_ -- `Fix security issues reported by the security audit <https://gerrit.opnfv.org/gerrit/#/c/20693/>`_ -- `Fix issues found in security review <https://gerrit.opnfv.org/gerrit/#/c/21541/>`_ -- `Removing OpenSteak Project <https://gerrit.opnfv.org/gerrit/#/c/22139/>`_ -- `Remove unsed files in open-contrail role <https://gerrit.opnfv.org/gerrit/#/c/21997/>`_ -- `Get rid of private key in repo <https://gerrit.opnfv.org/gerrit/#/c/21985>`_ -- `Handling file loads and tmp dirs differently <https://gerrit.opnfv.org/gerrit/#/c/21499>`_ -- `Remove `Debug = True when run Flask and add logger <https://gerrit.opnfv.org/gerrit/#/c/21799/>`_ +- :ref:`Removal of private keys <https://gerrit.opnfv.org/gerrit/#/c/21995/>` +- :ref:`Fix security issues of eval-s in testapi <https://gerrit.opnfv.org/gerrit/#/c/20751/>` +- :ref:`Implements use of yaml.safe_load <https://gerrit.opnfv.org/gerrit/#/c/20911/>` +- :ref:`Fix security issues reported by the security audit <https://gerrit.opnfv.org/gerrit/#/c/20693/>` +- :ref:`Fix issues found in security review <https://gerrit.opnfv.org/gerrit/#/c/21541/>` +- :ref:`Removing OpenSteak Project <https://gerrit.opnfv.org/gerrit/#/c/22139/>` +- :ref:`Remove unsed files in open-contrail role <https://gerrit.opnfv.org/gerrit/#/c/21997/>` +- :ref:`Get rid of private key in repo <https://gerrit.opnfv.org/gerrit/#/c/21985>` +- :ref:`Handling file loads and tmp dirs differently <https://gerrit.opnfv.org/gerrit/#/c/21499>` +- :ref:`Remove `Debug = True when run Flask and add logger <https://gerrit.opnfv.org/gerrit/#/c/21799/>` diff --git a/docs/release/overview.rst b/docs/release/overview.rst index cc0a30ded..4d2b611c6 100644 --- a/docs/release/overview.rst +++ b/docs/release/overview.rst @@ -10,20 +10,20 @@ Introduction ============ Network Functions Virtualization (NFV) is transforming the networking industry via -software-defined infrastructures and open source is the proven method for developing -software quickly for commercial products and services that can move markets. +software-defined infrastructures and open source is the proven method for quickly developing +software for commercial products and services that can move markets. Open Platform for NFV (OPNFV) facilitates the development and evolution of NFV components across various open source ecosystems. Through system level integration, deployment and testing, OPNFV constructs a reference NFV platform to accelerate the transformation of enterprise and service provider networks. As an open source project, OPNFV is uniquely positioned to bring together the work -of standards bodies, open source communities, and commercial suppliers to deliver a -de facto NFV platform for the industry. +of standards bodies, open source communities, service providers and commercial suppliers to deliver +a de facto NFV platform for the industry. By integrating components from upstream projects, the community is able to conduct performance and use case-based testing on a variety of solutions to ensure the platform’s suitability for -NFV use cases. OPNFV also works upstream with other open source communities to bring both contributions -and learnings from its work directly to those communities in the form of blueprints, patches, +NFV use cases. OPNFV also works upstream with other open source communities to bring contributions +and learnings from its work directly to those communities in the form of blueprints, patches, bugs, and new code. OPNFV initially focused on building NFV Infrastructure (NFVI) and Virtualised Infrastructure @@ -223,8 +223,7 @@ Functest Functest provides a functional testing framework incorporating a number of test suites and test cases that test and verify OPNFV platform functionality. -The scope of Functest and relevant test cases can be found in its -`user guide <http://artifacts.opnfv.org/functest/colorado/2.0/docs/userguide/index.html>`_. +The scope of Functest and relevant test cases can be found in its :ref:`user guide <Functest-UserGuide>`_ Functest provides both feature project and component test suite integration, leveraging OpenStack and SDN controllers testing frameworks to verify the key components of the OPNFV @@ -290,4 +289,4 @@ root cause isolation capabilities to facilitate system evaluation. .. _`OPNFV Configuration Guide`: http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/configguide .. _`OPNFV User Guide`: http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/userguide -.. _Dovetail project: https://wiki.opnfv.org/display/dovetail +.. _`Dovetail project`: https://wiki.opnfv.org/display/dovetail diff --git a/docs/release/userguide.introduction.rst b/docs/release/userguide.introduction.rst index ecbb75884..b4ebab25a 100644 --- a/docs/release/userguide.introduction.rst +++ b/docs/release/userguide.introduction.rst @@ -2,9 +2,9 @@ .. http://creativecommons.org/licenses/by/4.0 .. (c) Sofia Wallin (sofia.wallin@ericssion.com) -================ -OPNFV Userguide -================ +====================================== +OPNFV User Guide & Configuration Guide +====================================== Abstract ======== @@ -25,15 +25,15 @@ Introduction OPNFV provides a suite of scenarios, infrastructure depoyment options, which are able to be installed to host virtualized network functions (VNFs). -This guide intends to help users of the platform leverage the features and +This Guide intends to help Users of the platform leverage the features and capabilities delivered by the OPNFV project in support of these applications. OPNFV Continuous Integration builds, deploys and tests combinations of virtual infrastructure components in what are defined as scenarios. A scenario may include components such as OpenStack, OpenDaylight, OVS, KVM etc. where each -scenario will include different source components or configurations. Scenarios +scenario will include different source components or Configurations. Scenarios are designed to enable specific features and capabilities in the platform that -can be leveraged by the OPNFV user community. +can be leveraged by the OPNFV User community. Feature Overview @@ -42,47 +42,47 @@ Feature Overview The following links outline the feature deliveries from the participant OPNFV projects in the Colorado release. Each of the participating projects provides detailed descriptions about the delivered features. Including use cases, -implementation and configuration specifics on a per OPNFV project basis. +implementation and Configuration specifics on a per OPNFV project basis. The following are Configuration Guides and User Guides and assume that the reader has already some -information about a given projects specifics and deliverables. These guides +information about a given projects specifics and deliverables. These Guides are intended to be used following the installation of a given OPNFV installer to allow a user to deploy and implement feature delivered by OPNFV. If you are unsure about the specifics of a given project, please refer to the OPNFV projects home page, found on http://wiki.opnfv.org, for specific details. -You can find project specific usage and configuration information below: +You can find project specific usage and Configuration information below: Feature Configuration Guides ============================ -- `Armband configuration guide <http://artifacts.opnfv.org/armband/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Copper configuration guide <http://artifacts.opnfv.org/copper/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Doctor configuration guide <http://artifacts.opnfv.org/doctor/colorado/2.0/docs/installationprocedure/index.html>`_ -- `IPv6 configuration guide <http://artifacts.opnfv.org/ipv6/colorado/2.0/docs/installationprocedure/index.html>`_ -- `KVMforNFV configuration guide <http://artifacts.opnfv.org/kvmfornfv/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Moon configuration guide <http://artifacts.opnfv.org/moon/colorado/2.0/docs/installationprocedure/index.html>`_ -- `Multisite configuration guide <http://artifacts.opnfv.org/multisite/colorado/2.0/docs/installationprocedure/index.html>`_ -- `ONOSFW configuration guide <http://artifacts.opnfv.org/onosfw/colorado/2.0/installationprocedure/index.html>`_ -- `OVSNFV configuration guide <http://artifacts.opnfv.org/ovsnfv/colorado/2.0/docs/configguide/index.html>`_ -- `Promise configuration guide <https://git.opnfv.org/promise/tree/docs/release/configguide/feature.configuration.rst>`_ -- `SFC configuration guide <http://artifacts.opnfv.org/sfc/colorado/2.0/docs/installationprocedure/index.html>`_ +- :ref:`Armband Configuration Guide <armband-configguide>` +- :ref:`Copper Configuration Guide <copper-configguide>` +- :ref:`Doctor Configuration Guide <doctor-configguide>` +- :ref:`IPv6 Configuration Guide <ipv6-configguide>` +- :ref:`KVMforNFV Configuration Guide <kvmfornfv-configguide>` +- :ref:`Moon Configuration Guide <moon-configguide>` +- :ref:`Multisite Configuration Guide <multisite-configguide>` +- :ref:`ONOSFW Configuration Guide <onosfw-configguide>` +- :ref:`OVSNFV Configuration Guide <ovsnfv-configguide>` +- :ref:`Promise Configuration Guide <promise-configguide>` +- :ref:`SFC Configuration Guide <sfc-configguide>` Feature User Guides =================== -- `Copper user guide <http://artifacts.opnfv.org/copper/colorado/2.0/docs/userguide/index.html>`_ -- `Doctor user guide <http://artifacts.opnfv.org/doctor/colorado/2.0/docs/userguide/index.html>`_ -- `Domino user guide <http://artifacts.opnfv.org/domino/colorado/2.0/docs/userguide/index.html>`_ -- `IPv6 user guide <http://artifacts.opnfv.org/ipv6/colorado/2.0/docs/userguide/index.html>`_ -- `KVMforNFV user guide <http://artifacts.opnfv.org/kvmfornfv/colorado/2.0/docs/userguide/index.html>`_ -- `Moon user guide <http://artifacts.opnfv.org/moon/colorado/2.0/docs/userguide/index.html>`_ -- `Multisite user guide <http://artifacts.opnfv.org/multisite/colorado/2.0/docs/userguide/index.html>`_ -- `ONOSFW user guide <http://artifacts.opnfv.org/onosfw/colorado/2.0/docs/userguide/index.html>`_ -- `OVSNFV user guide <http://artifacts.opnfv.org/ovsnfv/colorado/2.0/docs/userguide/index.html>`_ -- `Parser user guide <http://artifacts.opnfv.org/parser/colorado/2.0/docs/userguide/index.html>`_ -- `Promise user guide <https://git.opnfv.org/promise/tree/docs/release/userguide/feature.userguide.rst>`_ -- `SDNVPN user guide <http://artifacts.opnfv.org/sdnvpn/colorado/2.0/docs/userguide/index.html>`_ -- `SFC user guide <http://artifacts.opnfv.org/sfc/colorado/2.0/docs/userguide/index.html>`_ +- :ref:`Copper User Guide <copper-userguide>` +- :ref:`Doctor User Guide <doctor-userguide>` +- :ref:`Domino User Guide <domino-userguide>` +- :ref:`IPv6 User Guide <ipv6-userguide>` +- :ref:`KVMforNFV User Guide <kvmfornfv-userguide>` +- :ref:`Moon User Guide <moon-userguide>` +- :ref:`Multisite User Guide <multisite-userguide>` +- :ref:`ONOSFW User Guide <onosfw-userguide>` +- :ref:`OVSNFV User Guide <ovsnfv-userguide>` +- :ref:`Parser User Guide <parser-userguide>` +- :ref:`Promise User Guide <promise-userguide>` +- :ref:`SDNVPN User Guide <sdnvpn-userguide>` +- :ref:`SFC User Guide <sfc-userguide>` |