diff options
| author |   Stuart Mackie <wsmackie@juniper.net> | 2017-09-14 23:26:31 -0700 |
|---|---|---|
| committer | Stuart Mackie <wsmackie@juniper.net> | 2017-09-14 23:26:31 -0700 |
| commit | fd876b7dbc7d517a706b22e52bf6f0e8f79a0b4b (patch) | |
| tree | 996858dd4abe0221f8f9d54a2aeeb4ffb9971b8e /docs/templates | |
| parent | fce102283bab73ed08c292fce03e39c52f4a1fe2 (diff) | |
Docs
Change-Id: Iea3001f8414267f1535353f28d30d45daf9a3e66
Signed-off-by: Stuart Mackie <wsmackie@juniper.net>
Diffstat (limited to 'docs/templates')
22 files changed, 0 insertions, 940 deletions
diff --git a/docs/templates/development/design/index.rst b/docs/templates/development/design/index.rst deleted file mode 100644 index 392b39f..0000000 --- a/docs/templates/development/design/index.rst +++ /dev/null @@ -1 +0,0 @@ -.. To be decided diff --git a/docs/templates/development/overview/index.rst b/docs/templates/development/overview/index.rst deleted file mode 100644 index caf4dfc..0000000 --- a/docs/templates/development/overview/index.rst +++ /dev/null @@ -1,15 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International -.. License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) OPNFV, Ericsson AB and others. - -============================================= -OPNFV <Project Name> <Release Name> Overview -============================================= - -For example, the title might be "Qtip Danube Overview" - -.. toctree:: - :maxdepth: 1 - - overview diff --git a/docs/templates/development/overview/overview.rst b/docs/templates/development/overview/overview.rst deleted file mode 100644 index 498dc06..0000000 --- a/docs/templates/development/overview/overview.rst +++ /dev/null @@ -1,16 +0,0 @@ -============================================== -OPNFV <Release Name> <Project Name> Overview -============================================== - -.. contents:: - :depth: 3 - :local: - -Introduction ----------------- -Describing the components and behaviours in a manner that helps people understand the platform and how to work with it - -Upgrades from <Previous Release> ------------------------------------ -<optional, required if there's a previous release for the project> -Describe the new features diff --git a/docs/templates/development/requirements/index.rst b/docs/templates/development/requirements/index.rst deleted file mode 100644 index 392b39f..0000000 --- a/docs/templates/development/requirements/index.rst +++ /dev/null @@ -1 +0,0 @@ -.. To be decided diff --git a/docs/templates/release/configguide/feature.configuration.rst b/docs/templates/release/configguide/feature.configuration.rst deleted file mode 100644 index e2fcbbb..0000000 --- a/docs/templates/release/configguide/feature.configuration.rst +++ /dev/null @@ -1,256 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) Ferenc Cserepkei, Brady Allen Johnson, Manuel Buil and others - -Abstract -======== -This document provides information on how to install the OpenDayLigh SFC -features in OPNFV with the use of os_odl-l2_sfc-(no)ha scenario. - -SFC feature desciription -======================== -For details of the scenarios and their provided capabilities refer to -the scenario description documents: - -- http://artifacts.opnfv.org/sfc/colorado/docs/scenarios_os-odl_l2-sfc-ha/index.html - -- http://artifacts.opnfv.org/sfc/colorado/docs/scenarios_os-odl_l2-sfc-noha/index.html - - -The SFC feature enables creation of Service Fuction Chains - an ordered list -of chained network funcions (e.g. firewalls, NAT, QoS) - -The SFC feature in OPNFV is implemented by 3 major components: - -- OpenDayLight SDN controller - -- Tacker: Generic VNF Manager (VNFM) and a NFV Orchestrator (NFVO) - -- OpenvSwitch: The Service Function Forwarder(s) - -Hardware requirements -===================== - -The SFC scenarios can be deployed on a bare-metal OPNFV cluster or on a -virtual environment on a single host. - -Bare metal deployment on (OPNFV) Pharos lab -------------------------------------------- -Hardware requirements for bare-metal deployments of the OPNFV infrastructure -are given by the Pharos project. The Pharos project provides an OPNFV -hardware specification for configuring your hardware: -http://artifacts.opnfv.org/pharos/docs/pharos-spec.html - - -Virtual deployment ------------------- -To perform a virtual deployment of an OPNFV SFC scenario on a single host, -that host has to meet the following hardware requirements: - -- SandyBridge compatible CPU with virtualization support - -- capable to host 5 virtual cores (5 physical ones at least) - -- 8-12 GBytes RAM for virtual hosts (controller, compute), 48GByte at least - -- 128 GiBiBytes room on disk for each virtual host (controller, compute) + - 64GiBiBytes for fuel master, 576 GiBiBytes at least - -- Ubuntu Trusty Tahr - 14.04(.5) server operating system with at least ssh - service selected at installation. - -- Internet Connection (preferably http proxyless) - - -Pre-configuration activites - Preparing the host to install Fuel by script -========================================================================== -.. Not all of these options are relevant for all scenario's. I advise following the -.. instructions applicable to the deploy tool used in the scenario. - -Before starting the installation of the SFC scenarios some preparation of the -machine that will host the Colorado Fuel cluster must be done. - -Installation of required packages ---------------------------------- -To be able to run the installation of the basic OPNFV fuel installation the -Jumphost (or the host which serves the VMs for the virtual deployment) needs to -install the following packages: -:: - - sudo apt-get install -y git make curl libvirt-bin libpq-dev qemu-kvm \ - qemu-system tightvncserver virt-manager sshpass \ - fuseiso genisoimage blackbox xterm python-pip \ - python-git python-dev python-oslo.config \ - python-pip python-dev libffi-dev libxml2-dev \ - libxslt1-dev libffi-dev libxml2-dev libxslt1-dev \ - expect curl python-netaddr p7zip-full - - sudo pip install GitPython pyyaml netaddr paramiko lxml scp \ - scp pycrypto ecdsa debtcollector netifaces enum - -During libvirt install the user is added to the libvirtd group, so you have to -logout then login back again - - -Download the installer source code and artifact ------------------------------------------------ -To be able to install the scenario os_odl-l2_sfc-(no)ha one can follow the way -CI is deploying the scenario. -First of all the opnfv-fuel repository needs to be cloned: -:: - - git clone -b 'stable/colorado' ssh://<user>@gerrit.opnfv.org:29418/fuel - -This command copies the whole colorado branch of repository fuel. - -Now download the appropriate OPNFV Fuel ISO into an appropriate folder: -:: - - wget http://artifacts.opnfv.org/fuel/colorado/opnfv-colorado.1.0.iso - -The exact name of the ISO image may change. -Check https://www.opnfv.org/opnfv-colorado-fuel-users to get the latest ISO. - -Simplified scenario deployment procedure using Fuel -=================================================== - -This section describes the installation of the os-odl-l2_sfc or -os-odl-l2_sfc-noha OPNFV reference platform stack across a server cluster -or a single host as a virtual deployment. - -Scenario Preparation --------------------- -dea.yaml and dha.yaml need to be copied and changed according to the -lab-name/host where you deploy. -Copy the full lab config from: -:: - - cp -r <path-to-opnfv-fuel-repo>/deploy/config/labs/devel-pipeline/elx \ - <path-to-opnfv-fuel-repo>/deploy/config/labs/devel-pipeline/<your-lab-name> - -Add at the bottom of dha.yaml -:: - - disks: - fuel: 64G - controller: 128G - compute: 128G - - define_vms: - controller: - vcpu: - value: 2 - memory: - attribute_equlas: - unit: KiB - value: 12521472 - currentMemory: - attribute_equlas: - unit: KiB - value: 12521472 - compute: - vcpu: - value: 2 - memory: - attribute_equlas: - unit: KiB - value: 8388608 - currentMemory: - attribute_equlas: - unit: KiB - value: 8388608 - fuel: - vcpu: - value: 2 - memory: - attribute_equlas: - unit: KiB - value: 2097152 - currentMemory: - attribute_equlas: - unit: KiB - value: 2097152 - -Check if the default settings in dea.yaml are in line with your intentions -and make changes as required. - -Installation procedures ------------------------ - -We state here several alternatives. -First, we describe methods that are based on the use of the deploy.sh script, -what is used by the OPNFV CI system and can be found in the Fuel repository. - -In addition, the SFC feature can also be configured manually in the Fuel GUI -what we will show in the last subsection. - -Before starting any of the following procedures, go to -:: - - cd <opnfv-fuel-repo>/ci - -Full automatic virtual deployment, High Availablity mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -This example will deploy the high-availability flavor of SFC scenario -os_odl-l2_sfc-ha in a fully automatic way, i.e. all installation steps -(Fuel server installation, configuration, node discovery and platform -deployment) will take place without any further prompt for user input. -:: - - sudo bash ./deploy.sh -b file://<path-to-opnfv-fuel-repo>/config/ -l devel-pipeline -p <your-lab-name> - -s os_odl-l2_sfc-ha -i file://<path-to-fuel-iso> - -Full automatic virtual deployment, non HIGH Availablity mode -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -The following command will deploy the SFC scenario with non-high-availability -flavor (note the different scenario name for the -s switch). Otherwise it -does the same as described above. -:: - - sudo bash ./deploy.sh -b file://<path-to-opnfv-fuel-repo>/config/ -l devel-pipeline -p <your-lab-name> - -s os_odl-l2_sfc-noha -i file://<path-to-fuel-iso> - -Automatic Fuel installation and manual scenario deployment -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -A useful alternative to the full automatic procedure is to only deploy the Fuel host and to run host selection, role assignment and SFC scenario configuration manually. -:: - - sudo bash ./deploy.sh -b file://<path-to-opnfv-fuel-repo>/config/ -l devel-pipeline -p <your-lab-name> -s os_odl-l2_sfc-ha -i file://<path-to-fuel-iso> -e - -With -e option the installer will skip environment deployment, so an user -can do some modification before the scenario is really deployed. Another -useful option is the -f option which deploys the scenario using an existing -Fuel host. - -The result of this installation is a well configured Fuel sever. The use of -the deploy button on Fuel dashboard can initiate the deployment. A user may -perform manual post-configuration as well. - -Feature configuration on existing Fuel -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -If a Fuel server is already provisioned but the fuel plugins for Opendaylight, -Openvswitch are not provided install them by: -:: - - cd /opt/opnfv/ - fuel plugins --install fuel-plugin-ovs-*.noarch.rpm - fuel plugins --install opendaylight-*.noarch.rpm - -If plugins are installed and you want to update them use --force flag. - -Note that One may inject other - Colorado compatible - plugins to the Fuel -Master host using the command scp: - -scp <plugin>.rpm root@10.20.0.2:<plugin>.rpm - -Now the feature can be configured. Create a new environment with -Networking Setup:"OpenDayLight with tunneling segmentation". Then go to -settings/other and check "OpenDaylight plugin, SFC enabled", -"Install Openvswitch with NSH/DPDK, with NSH enabled". During node provision -remember assign the OpenDayLight role to the (primary)controller - -Now the deploy button on fuel dashboard can be used to deploy the environment. diff --git a/docs/templates/release/configguide/featureconfig.rst b/docs/templates/release/configguide/featureconfig.rst deleted file mode 100644 index 287715d..0000000 --- a/docs/templates/release/configguide/featureconfig.rst +++ /dev/null @@ -1,34 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -======== -Abstract -======== -Add a brief introduction to configure OPNFV with this specific feature including -dependancies on platform components, this description should be at a level that -will apply to any installer providing the pre-requisite components. - -.. contents:: - :depth: 3 - :local: - -Pre-configuration activities -============================ -Describe specific pre-configuration activities. This should include ensuring the -right components are installed by the installation tools as required for your -feature to function. Refer to the previous installer configuration chapters, -installations guide and release notes - - -Hardware configuration -====================== -Describe the hardware configuration needed for this specific feature - - -Feature configuration -===================== -Describe the procedures to configure your feature on the platform in order -that it is ready to use according to the feature instructions in the platform -user guide. Where applicable you should add content in the postinstall.rst -to validate the feature is configured for use. -(checking components are installed correctly etc...) diff --git a/docs/templates/release/configguide/index.rst b/docs/templates/release/configguide/index.rst deleted file mode 100644 index 1789179..0000000 --- a/docs/templates/release/configguide/index.rst +++ /dev/null @@ -1,12 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -********************************** -<Project Name> Configuration Guide -********************************** - -.. toctree:: - :maxdepth: 1 - - featureconfig - postinstall diff --git a/docs/templates/release/configguide/postinstall.rst b/docs/templates/release/configguide/postinstall.rst deleted file mode 100644 index 59a20c6..0000000 --- a/docs/templates/release/configguide/postinstall.rst +++ /dev/null @@ -1,38 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -************************************* -<Project> Post Installation Procedure -************************************* - -Add a brief introduction to the methods of validating the installation -according to this specific installer or feature. - -.. contents:: - :depth: 3 - :local: - - -Automated post installation activities -====================================== -Describe specific post installation activities performed by the OPNFV -deployment pipeline including testing activities and reports. Refer to -the relevant testing guides, results, and release notes. - -note: this section should be singular and derived from the test projects -once we have one test suite to run for all deploy tools. This is not the -case yet so each deploy tool will need to provide (hopefully very simillar) -documentation of this. - - -<Project> post configuration procedures -======================================= -Describe any deploy tool or feature specific scripts, tests or procedures -that should be carried out on the deployment post install and configuration -in this section. - - -Platform components validation -============================== -Describe any component specific validation procedures necessary for your -deployment tool in this section. diff --git a/docs/templates/release/installation/index.rst b/docs/templates/release/installation/index.rst deleted file mode 100644 index 3dbb7c5..0000000 --- a/docs/templates/release/installation/index.rst +++ /dev/null @@ -1,11 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -*************************************** -<Project Name> Installation Instruction -*************************************** - -.. toctree:: - :maxdepth: 1 - - installation.instruction diff --git a/docs/templates/release/installation/installation.instruction.rst b/docs/templates/release/installation/installation.instruction.rst deleted file mode 100644 index 449f25f..0000000 --- a/docs/templates/release/installation/installation.instruction.rst +++ /dev/null @@ -1,210 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -======== -Abstract -======== - -This document describes how to install <Component>, it's dependencies and required system resources. - -.. contents:: - :depth: 3 - :local: - -Version history ---------------------- - -+--------------------+--------------------+--------------------+--------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| 2015-04-14 | 0.1.0 | Jonas Bjurel | First draft | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 0.1.1 | | | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 1.0 | | | -| | | | | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ - - -Introduction -============ -<INTRODUCTION TO THE SCOPE AND INTENTION OF THIS DOCUMENT AS WELL AS TO THE SYSTEM TO BE INSTALLED> - -<EXAMPLE>: - -This document describes the supported software and hardware configurations for the -Fuel OPNFV reference platform as well as providing guidelines on how to install and -configure such reference system. - -Although the available installation options gives a high degree of freedom in how the system is set-up, -with what architecture, services and features, etc., not nearly all of those permutations provides -a OPNFV compliant reference architecture. Following the guidelines in this document ensures -a result that is OPNFV compliant. - -The audience of this document is assumed to have good knowledge in network and Unix/Linux administration. - - -Preface -======= -<DESCRIBE NEEDED PREREQUISITES, PLANNING, ETC.> - -<EXAMPLE>: - -Before starting the installation of Fuel@OPNFV, some planning must preceed. - -First of all, the Fuel@OPNFV .iso image needs to be retrieved, -the Latest stable Arno release of Fuel@OPNFV can be found here: <www.opnfv.org/abc/def> - -Alternatively, you may build the .iso from source by cloning the opnfv/genesis git repository: -<git clone https://<linux foundation uid>@gerrit.opnf.org/gerrit/genesis> -Check-out the Arno release: -<cd genesis; git checkout arno> -Goto the fuel directory and build the .iso -<cd fuel/build; make all> - -Familiarize yourself with the Fuel 6.0.1 version by reading the following documents: -- abc <http://wiki.openstack.org/abc> -- def <http://wiki.openstack.org/def> -- ghi <http://wiki.openstack.org/ghi> - -Secondly, a number of deployment specific parameters must be collected, those are: - -1. Provider sub-net and gateway information - -2. Provider VLAN information - -3. Provider DNS addresses - -4. Provider NTP addresses - -This information will be needed for the configuration procedures provided in this document. - - -Hardware requirements -===================== -<PROVIDE A LIST OF MINIMUM HARDWARE REQUIREMENTS NEEDED FOR THE INSTALL> - -<EXAMPLE>: - -Following minimum hardware requirements must be met for installation of Fuel@OPNFV: - -+--------------------+----------------------------------------------------+ -| **HW Aspect** | **Requirement** | -| | | -+--------------------+----------------------------------------------------+ -| **# of servers** | Minimum 5 (3 for non redundant deployment) | -| | 1 Fuel deployment master (may be virtualized) | -| | 3(1) Controllers | -| | 1 Compute | -+--------------------+----------------------------------------------------+ -| **CPU** | Minimum 1 socket x86_AMD64 Ivy bridge 1.6 GHz | -| | | -+--------------------+----------------------------------------------------+ -| **RAM** | Minimum 16GB/server (Depending on VNF work load) | -| | | -+--------------------+----------------------------------------------------+ -| **Disk** | Minimum 256GB 10kRPM spinning disks | -| | | -+--------------------+----------------------------------------------------+ -| **NICs** | 2(1)x10GE Niantec for Private/Public (Redundant) | -| | | -| | 2(1)x10GE Niantec for SAN (Redundant) | -| | | -| | 2(1)x1GE for admin (PXE) and control (RabitMQ,etc) | -| | | -+--------------------+----------------------------------------------------+ - - -Top of the rack (TOR) Configuration requirements -================================================ -<DESCRIBE NEEDED NETWORK TOPOLOGY SETUP IN THE TORs> - -<EXAMPLE>: - -The switching infrastructure provides connectivity for the OPNFV infra-structure operations as well as -for the tenant networks (East/West) and provider connectivity (North/South bound connectivity). -The switching connectivity can (but does not need to) be fully redundant, -in case it and comprises a redundant 10GE switch pair for "Traffic/Payload/SAN" purposes as well as -a 1GE switch pair for "infrastructure control-, management and administration" - -The switches are **not** automatically configured from the OPNFV reference platform. -All the networks involved in the OPNFV infra-structure as well as the provider networks -and the private tenant VLANs needs to be manually configured. - -This following sections guides through required black-box switch configurations. - -VLAN considerations and blue-print -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -IP Address plan considerations and blue-print -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -OPNFV Software installation and deployment -========================================== -<DESCRIBE THE FULL PROCEDURES FOR THE INSTALLATION OF THE OPNFV COMPONENT INSTALLATION AND DEPLOYMENT> - -<EXAMPLE>: - -This section describes the installation of the Fuel@OPNFV installation server (Fuel master) -as well as the deployment of the full OPNFV reference platform stack across a server cluster. -Etc. - -Install Fuel master -^^^^^^^^^^^^^^^^^^^^^ - -Create an OPNV (Fuel Environment) -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Configure the OPNFV environment -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Deploy the OPNFV environment -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - - -Installation health-check -========================= -<DESCRIBE ANY MEANS TO DO VERIFY THE INTEGRITY AND HEALTHYNESS OF THE INSTALL> - -<EXAMPLE>: - -Now that the OPNFV environment has been created, and before the post installation configurations is started, -perform a system health check from the Fuel GUI: - -- Select the "Health check" TAB. -- Select all test-cases -- And click "Run tests" - -All test cases except the following should pass: - -Post installation and deployment actions ------------------------------------------- -<DESCRIBE ANY POST INSTALLATION ACTIONS/CONFIGURATIONS NEEDED> - -<EXAMPLE>: -After the OPNFV deployment is completed, the following manual changes needs to be performed in order -for the system to work according OPNFV standards. - -**Change host OS password:** -Change the Host OS password by...... - - -References -========== -<PROVIDE NEEDED/USEFUL REFERENCES> - -<EXAMPLES>: - -OPNFV -^^^^^^^^^^ - -OpenStack -^^^^^^^^^^^ - -OpenDaylight -^^^^^^^^^^^^^^^ diff --git a/docs/templates/release/release-notes/index.rst b/docs/templates/release/release-notes/index.rst deleted file mode 100644 index e703944..0000000 --- a/docs/templates/release/release-notes/index.rst +++ /dev/null @@ -1,11 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - -**************************** -<Project Name> Release Notes -**************************** - -.. toctree:: - :maxdepth: 1 - - release-notes diff --git a/docs/templates/release/release-notes/release-notes.rst b/docs/templates/release/release-notes/release-notes.rst deleted file mode 100644 index ead095c..0000000 --- a/docs/templates/release/release-notes/release-notes.rst +++ /dev/null @@ -1,233 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 - - -This document provides the release notes for <RELEASE> of <COMPONENT>. - -.. contents:: - :depth: 3 - :local: - - -Version history ---------------- - -+--------------------+--------------------+--------------------+--------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| 2015-04-14 | 0.1.0 | Jonas Bjurel | First draft | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 0.1.1 | | | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 1.0 | | | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ - -Important notes -=============== - -<STATE IMPORTANT NOTES/DEVIATIONS SINCE PREVIOUS ITERATIVE RELEASE AND OTHER IMPORTANT NOTES FOR THIS RELEASE> - -<EXAMPLE>: - -**Attention:** Please be aware that since LSV3 a pre-deploy script must be ran on the Fuel master - -see the OPNFV@Fuel SW installation instructions - - -Summary -======= - -<SUMMARIZE THE RELEASE - THE CONTENT - AND OTHER IMPORTANT HIGH LEVEL PROPERTIES> - -<EXAMPLE>: - -Arno Fuel@OPNFV is based the OpenStack Fuel upstream project version 6.0.1, -but adds OPNFV unique components such as OpenDaylight version: Helium as well as other OPNFV unique configurations...... - - -Release Data -============ -<STATE RELEVANT RELEASE DATA/RECORDS> - -<EXAMPLE>: - -+--------------------------------------+--------------------------------------+ -| **Project** | E.g. Arno/genesis/fuel@opnfv | -| | | -+--------------------------------------+--------------------------------------+ -| **Repo/commit-ID** | E.g. genesis/adf634a0d4..... | -| | | -+--------------------------------------+--------------------------------------+ -| **Release designation** | E.g. Arno RC2 | -| | | -+--------------------------------------+--------------------------------------+ -| **Release date** | E.g. 2015-04-16 | -| | | -+--------------------------------------+--------------------------------------+ -| **Purpose of the delivery** | E.g. OPNFV Internal quality assurance| -| | | -+--------------------------------------+--------------------------------------+ - -Version change -^^^^^^^^^^^^^^^^ - -Module version changes -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -<STATE WHAT UPSTREAM, - AS WELL AS OPNFV MODULE VERSIONS HAVE CHANGED> - -<EXAMPLE>: - -- Fuel have changed from 5.1 to 6.0.1 - -- OpenDaylight has changed from Helium-SR1 to Helium-SR2 - -Document version changes -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -<STATE WHAT RELATED DOCUMENTS THAT CHANGES WITH THIS RELEASE> - -<EXAMPLE>: - -- The Fuel@OPNFV installation guide version has changed from version 0.1 to to 0.2 - -Reason for version -^^^^^^^^^^^^^^^^^^^^ -Feature additions -~~~~~~~~~~~~~~~~~~~~~~~ -<STATE ADDED FEATURES BY REFERENCE TO JIRA> - -<EXAMPLE>: - -**JIRA BACK-LOG:** - -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| BGS-123 | ADD OpenDaylight ml2 integration | -| | | -+--------------------------------------+--------------------------------------+ -| BGS-456 | Add auto-deployment of Fuel@OPNFV | -| | | -+--------------------------------------+--------------------------------------+ - -Bug corrections -~~~~~~~~~~~~~~~~~~~~~ - -**JIRA TICKETS:** - -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| BGS-888 | Fuel doesn't deploy | -| | | -+--------------------------------------+--------------------------------------+ -| BGS-999 | Floating IP doesn't work | -| | | -+--------------------------------------+--------------------------------------+ - -Deliverables ----------------- - -Software deliverables -^^^^^^^^^^^^^^^^^^^^^^^ - -<STATE WHAT SOFTWARE DELIVERABLES THAT ARE RELATED TO THIS VERSION, AND WHERE THOSE CAN BE RETRIEVED> - -<EXAMPLE>: - -Documentation deliverables -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -<STATE WHAT DOCUMENTATION DELIVERABLES THAT ARE RELATED TO THIS VERSION, AND WHERE THOSE CAN BE RETRIEVED> - -<EXAMPLE>: - - -Known Limitations, Issues and Workarounds -========================================= - -System Limitations -^^^^^^^^^^^^^^^^^^^^ -<STATE ALL RELEVANT SYSTEM LIMITATIONS> - -<EXAMPLE>: - -**Max number of blades:** 1 Fuel master, 3 Controllers, 20 Compute blades - -**Min number of blades:** 1 Fuel master, 1 Controller, 1 Compute blade - -**Storage:** Ceph is the only supported storage configuration. - -**Max number of networks:** 3800 (Needs special switch config.) - -**L3Agent:** L3 agent and floating IPs is not supported. - -Known issues -^^^^^^^^^^^^^^^ -<STATE ALL KNOWN ISSUES WITH JIRA REFERENCE> - -<EXAMPLE>: - -**JIRA TICKETS:** - -+--------------------------------------+--------------------------------------+ -| **JIRA REFERENCE** | **SLOGAN** | -| | | -+--------------------------------------+--------------------------------------+ -| BGS-987 | Nova-compute process does | -| | not re-spawn when killed | -| | | -+--------------------------------------+--------------------------------------+ -| BGS-654 | MOS 5.1 : neutron net-list returns | -| | "400 Bad request" | -| | | -+--------------------------------------+--------------------------------------+ - -Workarounds -^^^^^^^^^^^^^^^^^ - -<STATE ALL KNOWN WORKAROUNDS TO THE ISSUES STATED ABOVE> - -<EXAMPLE>: - -- In case the contact with a compute is lost - restart the compute host -- In case the disk is full on a controller - delete all files in /tmp - -Test Result -=========== -<STATE THE QA COVERAGE AND RESULTS> - -<EXAMPLE>: - -Fuel@OPNFV Arno RC2 has undergone QA test runs with the following results: - -+--------------------------------------+--------------------------------------+ -| **TEST-SUITE** | **Results:** | -| | | -+--------------------------------------+--------------------------------------+ -| Tempest test suite 123 | Following tests failed: | -| | | -| | 1. Image resizing.... | -| | | -| | 2. Heat deploy.... | -+--------------------------------------+--------------------------------------+ -| Robot test suite 456 | Following tests failed: | -| | | -| | 1....... | -| | | -| | 2....... | -+--------------------------------------+--------------------------------------+ - -References -========== -<STATE RELEVANT REFERENCES FOR THIS RELEASE/VERSION> - -<EXAMPLE>: - -For more information on the OPNFV Danube release, please see: - -http://opnfv.org/danube diff --git a/docs/templates/release/scenarios/scenario.name/index.rst b/docs/templates/release/scenarios/scenario.name/index.rst deleted file mode 100644 index 37aab84..0000000 --- a/docs/templates/release/scenarios/scenario.name/index.rst +++ /dev/null @@ -1,16 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) <optionally add copywriters name> - -**************************************** -<scenario name> overview and description -**************************************** -.. This document will be used to provide a description of the scenario for an end user. -.. You should explain the purpose of the scenario, the types of capabilities provided and -.. the unique components that make up the scenario including how they are used. - -.. toctree:: - :maxdepth: 1 - - scenario.description - diff --git a/docs/templates/release/scenarios/scenario.name/scenario.description.rst b/docs/templates/release/scenarios/scenario.name/scenario.description.rst deleted file mode 100644 index 8c2cbab..0000000 --- a/docs/templates/release/scenarios/scenario.name/scenario.description.rst +++ /dev/null @@ -1,39 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) <optionally add copywriters name> - -This document provides scenario level details for <RELEASE> of <COMPONENT>. - -.. contents:: - :depth: 3 - :local: - -============ -Introduction -============ -.. In this section explain the purpose of the scenario and the types of capabilities provided - -Scenario components and composition -=================================== -.. In this section describe the unique components that make up the scenario, -.. what each component provides and why it has been included in order -.. to communicate to the user the capabilities available in this scenario. - -Scenario usage overview -======================= -.. Provide a brief overview on how to use the scenario and the features available to the -.. user. This should be an "introduction" to the userguide document, and explicitly link to it, -.. where the specifics of the features are covered including examples and API's - -Limitations, Issues and Workarounds -=================================== -.. Explain scenario limitations here, this should be at a design level rather than discussing -.. faults or bugs. If the system design only provide some expected functionality then provide -.. some insight at this point. - -References -========== - -For more information on the OPNFV Danube release, please visit -http://www.opnfv.org/danube - diff --git a/docs/templates/release/userguide/feature.userguide.rst b/docs/templates/release/userguide/feature.userguide.rst deleted file mode 100644 index 1d54d0e..0000000 --- a/docs/templates/release/userguide/feature.userguide.rst +++ /dev/null @@ -1,23 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) <optionally add copywriters name> - -.. contents:: - :depth: 3 - :local: - -<Feature> description -===================== -.. Describe the specific features and how it is realised in the scenario in a brief manner -.. to ensure the user understand the context for the user guide instructions to follow. - -<Feature> capabilities and usage -================================ -.. Describe the specific capabilities and usage for <XYZ> feature. -.. Provide enough information that a user will be able to operate the feature on a deployed scenario. - -<Feature and API usage guidelines and example> -============================================== -.. Describe with examples how to use specific features, provide API examples and details required to -.. operate the feature on the platform. - diff --git a/docs/templates/release/userguide/index.rst b/docs/templates/release/userguide/index.rst deleted file mode 100644 index 5fec000..0000000 --- a/docs/templates/release/userguide/index.rst +++ /dev/null @@ -1,23 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. (c) <optionally add copywriters name> - -===================== -<Feature> User Guide -===================== - -.. The feature user guide should provide an OPNFV user with enough information to -.. use the features provided by the feature project in the supported scenarios. -.. This guide should walk a user through the usage of the features once a scenario -.. has been deployed and is active according to the installation guide provided -.. by the installer project. - -.. toctree:: - :maxdepth: 1 - - feature.userguide -.. The feature.userguide.rst file should contain the text for this document -.. additional documents can be added to this directory and added in the right order -.. to this file as a list below. - - diff --git a/docs/templates/testing/developer/devguide/index.rst b/docs/templates/testing/developer/devguide/index.rst deleted file mode 100644 index e69de29..0000000 --- a/docs/templates/testing/developer/devguide/index.rst +++ /dev/null diff --git a/docs/templates/testing/developer/internship/index.rst b/docs/templates/testing/developer/internship/index.rst deleted file mode 100644 index e69de29..0000000 --- a/docs/templates/testing/developer/internship/index.rst +++ /dev/null diff --git a/docs/templates/testing/index.rst b/docs/templates/testing/index.rst deleted file mode 100644 index 392b39f..0000000 --- a/docs/templates/testing/index.rst +++ /dev/null @@ -1 +0,0 @@ -.. To be decided diff --git a/docs/templates/testing/user/configguide/configguide.rst b/docs/templates/testing/user/configguide/configguide.rst deleted file mode 100644 index e69de29..0000000 --- a/docs/templates/testing/user/configguide/configguide.rst +++ /dev/null diff --git a/docs/templates/testing/user/configguide/index.rst b/docs/templates/testing/user/configguide/index.rst deleted file mode 100644 index e69de29..0000000 --- a/docs/templates/testing/user/configguide/index.rst +++ /dev/null diff --git a/docs/templates/testing/user/userguide/index.rst b/docs/templates/testing/user/userguide/index.rst deleted file mode 100644 index e69de29..0000000 --- a/docs/templates/testing/user/userguide/index.rst +++ /dev/null |