From e042f556c6c25858f328cb6287c164b2514a2561 Mon Sep 17 00:00:00 2001 From: Sofia Wallin Date: Mon, 15 Aug 2016 15:20:50 +0200 Subject: WIP: Created 2 introduction documents for user guide and installation Work on the contant in both installation and user guide Started to add artifacts in the installation instruction and user guide This is a first draft of the installation.introduction.rst and userguide.introduction.rst. Some of the information has been reused from the Brahmaputra docs with modifications. Please comment and add as needed/wanted. Change-Id: I0c6d79aac7d1152ec894986dda251ad2d3c7048e Signed-off-by: Sofia Wallin --- .../template-os-nosdn-nofeature-ha/preparation.rst | 101 --------------------- 1 file changed, 101 deletions(-) delete mode 100644 docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst (limited to 'docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst') diff --git a/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst b/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst deleted file mode 100644 index 450c8bf5e..000000000 --- a/docs/installationprocedure/template-os-nosdn-nofeature-ha/preparation.rst +++ /dev/null @@ -1,101 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International -.. License. .. http://creativecommons.org/licenses/by/4.0 .. -.. (c) Christopher Price (Ericsson AB) and others - -Preparation -=========== -.. 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 scenario some preparation must -be done. You may choose to install the scenario using an ISO image, or -executing the installation from a prepared jumphost. - -Preparing your jumphost to install by script --------------------------------------------- - -To deploy the scenario from a script you will need to prepare the jumphost -with a compatible operating system. Prepare your jumphost running CentOS 7 with libvirt -running on it. You may then install the RDO Release RPM: - -``sudo yum install -y https://www.rdoproject.org/repos/rdo-release.rpm opnfv-apex-{version}.rpm`` - -The RDO Project release repository is needed to install OpenVSwitch, which is a dependency of -opnfv-apex. If you do not have external connectivity to use this repository you need to download -the OpenVSwitch RPM from the RDO Project repositories and install it with the opnfv-apex RPM. - -Preparing your jumphost using an ISO image ------------------------------------------- - -An alternative to preparing your own jumphost id to use a ISO image as a boot image. -Download or build the ISO image according to the following instructions. - -Retrieving the ISO image -^^^^^^^^^^^^^^^^^^^^^^^^ - -If you choose to install the scenario from an ISO image you must first -retrieve the .iso image of the Colorado release. This can be -found can be found at . - -Building the ISO image -^^^^^^^^^^^^^^^^^^^^^^ - -Alternatively, you may choose to build the Fuel .iso from source by cloning the -opnfv/fuel git repository. To retrieve the repository for the Colorado release use the following command: - -$ git clone https://gerrit.opnfv.org/gerrit/fuel - -Check-out the Colorado release tag to set the HEAD to the -baseline required to replicate the Colorado release: - -$ git checkout colorado.1.0 - -Go to the fuel directory and build the .iso: - -$ cd fuel/build; make all - -For more information on how to build, please see *Reference: 14* - -Booting from the ISO image -^^^^^^^^^^^^^^^^^^^^^^^^^^ - -Mount the ISO file/media as a boot device on the jump host server. If all your hardware -preparation is complete at this time you should reboot the jumphost to establish the deployment server. - - -Additional preparations ------------------------ -.. Additional information should be provided here. it should be relatively short and informative -.. and not drag attention away from the hardware preparation section. - - -Additionally, familiarize yourself with Fuel by reading the following documents: - -- Fuel planning guide, please see *Reference: 8* - -- Fuel user guide, please see *Reference: 9* - -- Fuel operations guide, please see *Reference: 10* - -- Fuel Plugin Developers Guide, please see *Reference: 11* - -Prior to installation, a number of deployment specific parameters must be collected, those are: - -#. Provider sub-net and gateway information - -#. Provider VLAN information - -#. Provider DNS addresses - -#. Provider NTP addresses - -#. Network overlay you plan to deploy (VLAN, VXLAN, FLAT) - -#. How many nodes and what roles you want to deploy (Controllers, Storage, Computes) - -#. Monitoring options you want to deploy (Ceilometer, Syslog, etc.). - -#. Other options not covered in the document are available in the links above - -This information will be needed for the configuration procedures -provided in this document. -- cgit 1.2.3-korg