From 0f416cdda6a27f8d3dabd84dfe6bf09e9b681cf3 Mon Sep 17 00:00:00 2001 From: Jonas Bjurel Date: Tue, 14 Apr 2015 23:30:26 +0200 Subject: Initial rearrangements for the OPNFV/opnfvdoc documentation structure including LOW level READMEs, LICENCEs, and TODOs. JIRA: Change-Id: Ifd2baa5b1db3ae0fb354e39548eb7f9547639581 Signed-off-by: Jonas Bjurel --- fuel/docs/src/installation-instructions.rst | 219 ++++++++++++++++++++++++++++ 1 file changed, 219 insertions(+) create mode 100644 fuel/docs/src/installation-instructions.rst (limited to 'fuel/docs/src/installation-instructions.rst') diff --git a/fuel/docs/src/installation-instructions.rst b/fuel/docs/src/installation-instructions.rst new file mode 100644 index 0000000..388907e --- /dev/null +++ b/fuel/docs/src/installation-instructions.rst @@ -0,0 +1,219 @@ +:Authors: Jonas Bjurel (Ericsson) +:Version: 0.1 + +================================================================ +OPNFV Installation instructions for - < Component denomination > +================================================================ + +Abstract +======== + +This document describes how to install , it's dependencies and required system resources. + +License +======= + (c) by + + is licensed under a Creative Commons Attribution 4.0 Unported License. You should have received a copy of the license along with this. If not, see . + + +**Contents** + +1 Version history + +2 Introduction + +3 Preface + +4 Hardware requirements + +5 Top of the rack (TOR) Configuration requirements + +6 OPNFV Software installation and deployment + +7 Installation health-check + +8 Post installation and deployment actions + +9 References + +1 Version history +=================== + ++--------------------+--------------------+--------------------+--------------------+ +| **Date** | **Ver.** | **Author** | **Comment** | +| | | | | ++--------------------+--------------------+--------------------+--------------------+ +| 2015-04-14 | 0.1.0 | Jonas Bjurel | First draft | +| | | | | ++--------------------+--------------------+--------------------+--------------------+ +| | 0.1.1 | | | +| | | | | ++--------------------+--------------------+--------------------+--------------------+ +| | 1.0 | | | +| | | | | +| | | | | ++--------------------+--------------------+--------------------+--------------------+ + +2 Introduction +================ + + +: + +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. + +3 Preface +=========== + + +: + +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: + +Alternatively, you may build the .iso from source by cloning the opnfv/genesis git repository: +@gerrit.opnf.org/gerrit/genesis> +Check-out the Arno release: + +Goto the fuel directory and build the .iso + + +Familiarize yourself with the Fuel 6.0.1 version by reading the following documents: +- abc +- def +- 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. + +4 Hardware requirements +========================= + + +: + +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) | +| | | ++--------------------+----------------------------------------------------+ + +5 Top of the rack (TOR) Configuration requirements +==================================================== + + +: + +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. + +5.1 VLAN considerations and blue-print +-------------------------------------- + +5.2 IP Address plan considerations and blue-print +------------------------------------------------- + +6 OPNFV Software installation and deployment +============================================== + + +: + +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. + +6.1 Install Fuel master +----------------------- + +6.2 Create an OPNV (Fuel Environment) +------------------------------------- + +6.3 Configure the OPNFV environment +----------------------------------- + +6.4 Deploy the OPNFV environment +-------------------------------- + +7 Installation health-check +============================ + + +: + +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: + +8 Post installation and deployment actions +============================================ + + +: +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...... + +9 References +============= + + +: + +9.1 OPNFV +------------- + +9.2 OpenStack +----------------- + +9.3 OpenDaylight +-------------------- + +9.4 Fuel +------------ \ No newline at end of file -- cgit 1.2.3-korg