diff options
| -rw-r--r-- | fuel/docs/src/installation-instructions.rst | 330 | ||||
| -rw-r--r-- | fuel/docs/src/release-notes.rst | 127 | ||||
| -rw-r--r-- | fuel/docs/src/tmp/INSTALL/README | 154 |
3 files changed, 283 insertions, 328 deletions
diff --git a/fuel/docs/src/installation-instructions.rst b/fuel/docs/src/installation-instructions.rst index 388907e..234dfc2 100644 --- a/fuel/docs/src/installation-instructions.rst +++ b/fuel/docs/src/installation-instructions.rst @@ -1,20 +1,20 @@ -:Authors: Jonas Bjurel (Ericsson) -:Version: 0.1 +:Authors: Jonas Bjurel (Ericsson AB) +:Version: 0.0.1 -================================================================ -OPNFV Installation instructions for - < Component denomination > -================================================================ +================================================ +OPNFV Installation instructions for - Fuel@OPNFV +================================================ Abstract ======== -This document describes how to install <Component>, it's dependencies and required system resources. +This document describes how to install Fuel@OPNFV, it's dependencies and required system resources. License ======= -<WORK'S NAME> (c) by <AUTHOR'S NAME> +Fuel@OPNFV DOCs (c) by Jonas Bjurel (Ericsson AB) -<WORK'S NAME> 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 <http://creativecommons.org/licenses/by/4.0/>. +Fuel@OPNFV DOCs are 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 <http://creativecommons.org/licenses/by/4.0/>. **Contents** @@ -44,54 +44,51 @@ License | **Date** | **Ver.** | **Author** | **Comment** | | | | | | +--------------------+--------------------+--------------------+--------------------+ -| 2015-04-14 | 0.1.0 | Jonas Bjurel | First draft | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 0.1.1 | | | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 1.0 | | | -| | | | | -| | | | | +| 2015-04-15 | 0.0.1 | Jonas Bjurel | First draft | +| | | (Ericsson AB) | | +--------------------+--------------------+--------------------+--------------------+ + 2 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. -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. +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 R1 (Arno) compliant. The audience of this document is assumed to have good knowledge in network and Unix/Linux administration. 3 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> +For more information on how to build, please see "OPNF Build instructions for - FUel@OPNFV <http://www.opnfv.org/xyz -Secondly, a number of deployment specific parameters must be collected, those are: +Next, familiarize yourself with the Fuel 6.0.1 version by reading the following documents: + +- Fuel planning guide <http://docs.mirantis.com/openstack/fuel/fuel-6.0/planning-guide.html#planning-guide> + +- Fuel user guide <http://docs.mirantis.com/openstack/fuel/fuel-6.0/user-guide.html#user-guide> + +- Fuel operations guide <http://docs.mirantis.com/openstack/fuel/fuel-6.0/operations.html#operations-guide> + + +A number of deployment specific parameters must be collected, those are: 1. Provider sub-net and gateway information @@ -105,49 +102,46 @@ This information will be needed for the configuration procedures provided in thi 4 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) | -| | | -+--------------------+----------------------------------------------------+ ++--------------------+------------------------------------------------------+ +| **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 ==================================================== -<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 switching infrastructure provides connectivity for the OPNFV infra-structure operations, tenant networks (East/West) and provider connectivity (North/South bound connectivity); it als provides needed connectivity for the strage Area Network (SAN). To avoid traffic congestion, it is strongly sugested that three physcally separated networks are used, that is: 1 physical network for administration and control, one physical network for tenant private and public networks, and one physical network for SAN. The switching connectivity can (but does not need to) be fully redundant, in such case it and comprises a redundant 10GE switch pair for each of the three physcally separated networks. -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. +The physical TOR 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. +The following sections guides through required black-box switch configurations. 5.1 VLAN considerations and blue-print -------------------------------------- @@ -157,30 +151,205 @@ This following sections guides through required black-box switch configurations. 6 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. 6.1 Install Fuel master ----------------------- +1. Mount the built .iso file (release/opnfv-<version>.iso) as a boot device to the fuel server. + +2. Reboot the fuel server. + + - The system now boots from the ISO image. + +3. Change the grub boot parameters + + - When the grub boot menu shows up - Press Tab to edit the kernel parameters + + - Change <showmenu=no> to <showmenu=yes>. + + - Change <netmask=255.255.255.0> to <netmask=255.255.0.0>. + + - Press [Enter]. + +4 Wait until screen Fuel setup is shown (Note: This can take up to 30 minutes). + +5. Select PXE Setup and change the following fields to appropriate values (example below): + + - Static Pool Start 10.20.0.3 + + - Static Pool End 10.20.0.254 + + - DHCP Pool Start 10.20.128.3 + + - DHCP Pool End 10.20.128.254 + +6. Select DNS & Hostname and change the following fields to appropriate values: + + - Hostname <CEE Region name>-fuel + + - Domain <Domain Name> + + - Search Domain <Search Domain Name> + + - Hostname to test DNS <Hostname to test DNS> + +7. Select Time Sync and change the following fields to appropriate values: + + - NTP Server 1 <Customer NTP server 1> + + - NTP Server 2 <Customer NTP server 2> + + - NTP Server 3<Customer NTP server 3> + + **Note: This step is only to pass the network sanity test, the actual ntp parameters will be set with the pre-deploy script.** + +8. Start the installation. + + - Select Quit Setup and press Save and Quit. + + - Installation starts, wait until a screen with logon credentials is shown. + + Note: This will take about 15 minutes. 6.2 Create an OPNV (Fuel Environment) ------------------------------------- +9. Connect to Fuel with a browser towards port 8000 + +10. Create and name a new OpenStack environment, to be installed. + +11. Select <Juno on Ubuntu> or <Juno on CentOS> as per your which in the "OpenStack Release" field. + +12. Select deployment mode. + + - Select the Multi-node with HA. + +13. Select compute node mode. + + - Select KVM as hypervisor (unless you're not deploying bare metal or nested KVM/ESXI). + +14. Select network mode. + + - Select Neutron with VLAN segmentation + + ** Note: This will later be overridden to VXLAN by OpenDaylight.** + +15. Select Storage Backends. + + - Select Ceph for Cinder and default for glance. + +16. Select additional services. + + - Check option <Install Celiometer (OpenStack Telemetry)>. + +17. Create the new environment. + 6.3 Configure the OPNFV environment ----------------------------------- +18. Enable PXE booting + + - For every controller- and compute server: enable PXE Booting as the first boot device in the BIOS boot order menu, and hard disk as the second boot device in the same menu. + +19. Reboot all the controller- and compute blades. + +20. Wait for the availability of nodes showing up in the Fuel GUI. + + - Wait until all nodes are displayed in top right corner of the Fuel GUI: <total number of server> TOTAL NODES and <total number of servers> UNALLOCATED NODES. + +21. Open the environment you previously created. + +22. Open the networks tab. + +23. Update the public network configuration. + + Change the following fields to appropriate values: + + - IP Range Start to <Public IP Address start> + + - IP Range End to <Public IP Address end> + + - CIDR to <CIDR for Public IP Addresses> + + - Gateway to <Gateway for Public IP Addresses> + + - Check VLAN tagging. + + - Set appropriate VLAN id. + +24. Update the management network configuration. + + - Set CIDR to 172.16.255.128/25 (or as per your which). + + - Check VLAN tagging. + + - Set appropriate VLAN id. + +25. Update the Neutron L2 configuration. + + - Set VLAN ID range. + +26. Update the Neutron L3 configuration. + + - Set Internal network CIDR to an appropriate value + + - Set Internal network gateway to an appropriate value + + - Set Floating IP ranges. + + - Set DNS Servers + +27. Save Settings. + +28. Click "verify network" to check the network set-up consistency and connectivity + +29. Update the storage configuration. + +30. Open the nodes tab. + +31. Assign roles. + + - Check <Controller and Telemetry MongoDB>. + + - Check the three servers you want to be installed as Controllesr in pane <Assign Role>. + + - Click <Apply Changes>. + + - Check <Compute>. + + - Check nodes to be installed as Compute nodes in pane Assign Role. + + - Click <Apply Changes>. + +32. Configure interfaces. + + - Check Select <All> to select all nodes with Control, Telemetry . MongoDB and Compute node roles. + + - Click <Configure Interfaces> + + - Screen Configure interfaces on number of <number of nodes> nodes is shown. + - Assign interfaces (bonded) for mgmt-, admin-, private-, public- and storage networks + 6.4 Deploy the OPNFV environment -------------------------------- +**NOTE: Before the deployment is performed, the OPNFV pre-deploy script must be ran** -7 Installation health-check -============================ -<DESCRIBE ANY MEANS TO DO VERIFY THE INTEGRITY AND HEALTHYNESS OF THE INSTALL> +35. Run the pre-deploy script. + Log on as root to the Fuel node. + Print Fuel environment Id (fuel env) + #> id | status | name | mode | release_id | changes <id>| new | <CEE Region name>| ha_compact | 2 | <ite specific information> -<EXAMPLE>: +36. Run the pre-deployment script (/opt/opnfv/pre-deploy.sh <id>) + As prompted for-, set the DNS servers to go into /etc/resolv.conf. + As prompted for-, set any Hosts file additions for controllers and compute nodes. You will be prompted for name, FQDN and IP for each entry. Press return when prompted for a name when you have completed your input. + As prompted for-, set NTP upstream configuration for controllers. You will be prompted for a NTP server each entry. Press return when prompted for a NTP server when you have completed your input. + +37. Deploy the environment. + In the Fuel GUI, click Deploy Changes. + +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: @@ -192,19 +361,10 @@ All test cases except the following should pass: 8 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...... +**-** 9 References ============= -<PROVIDE NEEDED/USEFUL REFERENCES> - -<EXAMPLES>: 9.1 OPNFV ------------- @@ -216,4 +376,4 @@ Change the Host OS password by...... -------------------- 9.4 Fuel -------------
\ No newline at end of file +------------ diff --git a/fuel/docs/src/release-notes.rst b/fuel/docs/src/release-notes.rst index d6b21cb..467de6e 100644 --- a/fuel/docs/src/release-notes.rst +++ b/fuel/docs/src/release-notes.rst @@ -1,20 +1,20 @@ :Authors: Jonas Bjurel (Ericsson) :Version: 0.1 -====================================================================== -OPNFV Release Note for "Arno-SRx release" - < Component denomination > -====================================================================== +================================================================ +OPNFV Release Note for "Arno-RC2 release candidate" - Fuel@OPNFV +================================================================ Abstract ======== -This document provides the release notes for <RELEASE> of <COMPONENT>. +This document provides the release notes for ARNO-RC2 release candidate of Fuel@OPNFV. License ======= -<WORK'S NAME> (c) by <AUTHOR'S NAME> +Fuel@OPNFV DOCs (c) by Jonas Bjurel (Ericsson AB) -<WORK'S NAME> 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 <http://creativecommons.org/licenses/by/4.0/>. +Fuel@OPNFV DOCs are 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 <http://creativecommons.org/licenses/by/4.0/>. **Contents** @@ -40,54 +40,48 @@ License | **Date** | **Ver.** | **Author** | **Comment** | | | | | | +--------------------+--------------------+--------------------+--------------------+ -| 2015-04-14 | 0.1.0 | Jonas Bjurel | First draft | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 0.1.1 | | | -| | | | | -+--------------------+--------------------+--------------------+--------------------+ -| | 1.0 | | | +| 2015-04-16 | 0.1.0 | Jonas Bjurel | First draft | | | | | | +--------------------+--------------------+--------------------+--------------------+ 2 Important notes =================== -<STATE IMPORTANT NOTES/DEVIATIONS SINCE PREVIOUS ITERATIVE RELEASE AND OTHER IMPORTANT NOTES FOR THIS RELEASE> +This is the first OPNFV Arno pre-release that implements the deploy stage of the OPNFV CI pipeline. -<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 +Carefully follow the installation-instructions and pay special attention to the pre-deploy script that needs to be ran befor deployment is started. 3 Summary =========== -<SUMMARIZE THE RELEASE - THE CONTENT - AND OTHER IMPORTANT HIGH LEVEL PROPERTIES> +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. + +This Arno pre-release of Fuel@OPNFV adds the deploy stage of the OPNFV CI pipeline -<EXAMPLE>: +- Documentation is built by Jenkins +- .iso image is built by Jenkins +- Jenkins deploy an Fuel@OPNFV stack instance on a nested hypervisor environment (KVM) -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...... +Automatic test of the deployed system is not part of this pre-release. 4 Release Data ================ -<STATE RELEVANT RELEASE DATA/RECORDS> - -<EXAMPLE>: +--------------------------------------+--------------------------------------+ -| **Project** | E.g. Arno/genesis/fuel@opnfv | +| **Project** | Arno/genesis/fuel | | | | +--------------------------------------+--------------------------------------+ -| **Repo/commit-ID** | E.g. genesis/adf634a0d4..... | +| **Repo/tag** | genesis/arno-rc2 | | | | +--------------------------------------+--------------------------------------+ -| **Release designation** | E.g. Arno RC2 | +| **Release designation** | Arno RC2 | | | | +--------------------------------------+--------------------------------------+ -| **Release date** | E.g. 2015-04-16 | +| **Release date** | 2015-04-16 | | | | +--------------------------------------+--------------------------------------+ -| **Purpose of the delivery** | E.g. OPNFV Internal quality assurance| +| **Purpose of the delivery** | OPNFV Internal quality assurance | +| | and CI Pipline dry-run | | | | +--------------------------------------+--------------------------------------+ @@ -96,40 +90,34 @@ Arno Fuel@OPNFV is based the OpenStack Fuel upstream project version 6.0.1, but 4.1.1 Module version changes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -<STATE WHAT UPSTREAM, - AS WELL AS OPNFV MODULE VERSIONS HAVE CHANGED> +This is the first tracked version of genesis/fuel. It is based on following upstream versions: -<EXAMPLE>: +- Fuel 6.0.1 (Juno release) -- Fuel have changed from 5.1 to 6.0.1 +- OpenDaylight Helium-SR2 -- OpenDaylight has changed from Helium-SR1 to Helium-SR2 +- Ubuntu 12.04.5 4.1.2 Document version changes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -<STATE WHAT RELATED DOCUMENTS THAT CHANGES WITH THIS RELEASE> - -<EXAMPLE>: +This is the first tracked version of genesis/fuel. It comes with the following documentation: -- The Fuel@OPNFV installation guide version has changed from version 0.1 to to 0.2 +- OPNFV Installation instructions for - Fuel@OPNFV - ver. 0.0.1 +- OPNFV Release Note for "Arno-RC2 release candidate" - Fuel@OPNFV - ver. 0.1 (this document) 4.2 Reason for version ---------------------- 4.2.1 Feature additions ~~~~~~~~~~~~~~~~~~~~~~~ -<STATE ADDED FEATURES BY REFERENCE TO JIRA> - -<EXAMPLE>: - -**JIRA BACK-LOG:** +--------------------------------------+--------------------------------------+ | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| BGS-123 | ADD OpenDaylight ml2 integration | +| JIRA: | Baselining Fuel 6.0.1 for OPNFV | | | | +--------------------------------------+--------------------------------------+ -| BGS-456 | Add auto-deployment of Fuel@OPNFV | +| JIRA: | Integration of OpenDaylight | | | | +--------------------------------------+--------------------------------------+ @@ -142,10 +130,7 @@ Arno Fuel@OPNFV is based the OpenStack Fuel upstream project version 6.0.1, but | **JIRA REFERENCE** | **SLOGAN** | | | | +--------------------------------------+--------------------------------------+ -| BGS-888 | Fuel doesn't deploy | | | | -+--------------------------------------+--------------------------------------+ -| BGS-999 | Floating IP doesn't work | | | | +--------------------------------------+--------------------------------------+ @@ -154,26 +139,18 @@ Arno Fuel@OPNFV is based the OpenStack Fuel upstream project version 6.0.1, but 4.3.1 Software deliverables ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -<STATE WHAT SOFTWARE DELIVERABLES THAT ARE RELATED TO THIS VERSION, AND WHERE THOSE CAN BE RETRIEVED> - -<EXAMPLE>: +Fuel@OPNFV .iso file 4.3.2 Documentation deliverables ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -<STATE WHAT DOCUMENTATION DELIVERABLES THAT ARE RELATED TO THIS VERSION, AND WHERE THOSE CAN BE RETRIEVED> - -<EXAMPLE>: +- OPNFV Installation instructions for - Fuel@OPNFV - ver. 0.0.1 +- OPNFV Release Note for "Arno-RC2 release candidate" - Fuel@OPNFV - ver. 0.1 (this document) 5 Known Limitations, Issues and Workarounds ============================================ 5.1 System Limitations ------------------------- -<STATE ALL RELEVANT SYSTEM LIMITATIONS> - -<EXAMPLE>: **Max number of blades:** 1 Fuel master, 3 Controllers, 20 Compute blades @@ -187,9 +164,6 @@ Arno Fuel@OPNFV is based the OpenStack Fuel upstream project version 6.0.1, but 5.2 Known issues ------------------- -<STATE ALL KNOWN ISSUES WITH JIRA REFERENCE> - -<EXAMPLE>: **JIRA TICKETS:** @@ -197,30 +171,17 @@ Arno Fuel@OPNFV is based the OpenStack Fuel upstream project version 6.0.1, but | **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" | +| JIRA: | CentOS is not supported | | | | +--------------------------------------+--------------------------------------+ 5.3 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 6 Test Result ============== -<STATE THE QA COVERAGE AND RESULTS> - -<EXAMPLE>: Fuel@OPNFV Arno RC2 has undergone QA test runs with the following results: @@ -228,24 +189,12 @@ 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....... | +| **-** | **-** | +--------------------------------------+--------------------------------------+ + 7 References ============= -<STATE RELEVANT REFERENCES FOR THIS RELEASE/VERSION> - -<EXAMPLE>: For more information on the OPNFV Arno release, please see: diff --git a/fuel/docs/src/tmp/INSTALL/README b/fuel/docs/src/tmp/INSTALL/README deleted file mode 100644 index 456e26d..0000000 --- a/fuel/docs/src/tmp/INSTALL/README +++ /dev/null @@ -1,154 +0,0 @@ -############################################################################## -# Copyright (c) 2015 Ericsson AB and others. -# stefan.k.berg@ericsson.com -# jonas.bjurel@ericsson.com -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Apache License, Version 2.0 -# which accompanies this distribution, and is available at -# http://www.apache.org/licenses/LICENSE-2.0 -############################################################################## - - -This README file describes how to install the OPNFV BGS Stack -============================================================= -1.1 Install Fuel Server ------------------------ -1. Mount the built .iso file (release/opnfv-<version>.iso) as a bootdevice to the fuel server. - -2. Reboot the fuel server. - The system now boots from the ISO image. - -3. Change the grub boot params - When Press Tab to edit . is shown press Tab. - Change showmenu=no to showmenu=yes. - Change netmask=255.255.255.0 to netmask=255.255.0.0. - Press Enter. - -4 Wait until screen Fuel setup . is shown. - Note: This takes about 30 minutes. - -5. Select PXE Setup and change the following fields to appropriate values (example below): - Static Pool Start 10.20.0.3 - Static Pool End 10.20.0.254 - DHCP Pool Start 10.20.128.3 - DHCP Pool End 10.20.128.254 - -6. Select DNS & Hostname and change the following fields to appropriate values: - Hostname <CEE Region name>-fuel - Domain <Domain Name> - Search Domain <Search Domain Name> - Hostname to test DNS <Hostname to test DNS> - -7. Select Time Sync and change the following fields to appropriate values: - NTP Server 1 <Customer NTP server 1> - NTP Server 2 <Customer NTP server 2> - NTP Server 3<Customer NTP server 3> - Note: This step is only to pass the network test, the actual ntp parameters will be set with the pre_deply script. - -8. Start the installation. - Select Quit Setup and press Save and Quit. - Installation starts, wait until a screen with logon credentials is shown. - Note: This takes about 15 minutes. - -10. Enable PXE Booting and put it first in the bios boot order menu. - -11. Reboot the controller- and compute blades. - -12. Connect to Fuel wit a browser towards port 8000 - -13. Create and name a new OpenStack environment, to be installed. - -14. Select Icehouse on Ubuntu . in field OpenStack Release. - -15. Select deployment mode. - Select the Multi-node with HA. - -16. Select compute node mode. - Select KVM as hypervisor. - -17. Select network mode. - Select Neutron with VLAN segmentation. - -18. Select Storage Backends. - Select Ceph for Cinder and default for glance. - - -19. Select additional services. - Check option Install Celiometer (OpenStack Telemetry). - -20. Create the new environment. - -21. Wait for availability nodes. - Wait until all nodes are displayed in top right in <total number of server> TOTAL NODES and <total number of servers> UNALLOCATED NODES. - -22. Open the created environment. - -23. Open the networks tab. - -24. Update the public configuration. - Change the following fields to appropriate values: - IP Range Start to <Public IP Address start> - IP Range End to <Public IP Address end> - CIDR to <CIDR for Public IP Addresses> - Gateway to <Gateway for Public IP Addresses> - Check VLAN tagging. - Set appropriate VLAN id. - -25. Update the management configuration. - Set CIDR to 172.16.255.128/25. - Check VLAN tagging. - Set appropriate VLAN id. - -26. Update the storage configuration. - Set CIDR to the appropriate value - Check VLAN tagging. - Set appropriate VLAN id. - -27. Update the Neutron L2 configuration. - Set VLAN ID range. - -28. Update the Neutron L3 configuration. - Set Internal network CIDR to an appropriate value - Set Internal network gateway to an appropriate value - Set Floating IP ranges. - Set DNS Servers - -29. Save Settings. - -30. Click "verify network" to check the network set-up - -31. Update storage configuration. - -32. Open the nodes tab. - -33. Assign roles. - Check Controller and Telemetry . MongoDB. - Check three nodes to be installed as Controller in pane Assign Role. - Click Apply Changes. - Check Compute. - Check nodes to be installed as Compute nodes in pane Assign Role. - Click Apply Changes. - -34. Configure interfaces. - Check Select All to select all nodes with Control, Telemetry . MongoDB and Compute node roles. - Click Configure Interfaces. - Screen Configure interfaces on number of <number of nodes> nodes is shown. - Assign interfaces (bonded) for mgmt-, admin-, private-, public- and storage networks - -35. Run the pre-deploy script. - Log on as root to the Fuel node. - Print Fuel environment Id (fuel env) - #> id | status | name | mode | release_id | changes <id>| new | <CEE Region name>| ha_compact | 2 | <ite specific information> - -36. Run the pre-deployment script (/opt/opnfv/pre-deploy.sh <id>) - As prompted for-, set the DNS servers to go into /etc/resolv.conf. - As prompted for-, set any Hosts file additions for controllers and compute nodes. You will be prompted for name, FQDN and IP for each entry. Press return when prompted for a name when you have completed your input. - As prompted for-, set NTP upstream configuration for controllers. You will be prompted for a NTP server each entry. Press return when prompted for a NTP server when you have completed your input. - -37. Deploy the environment. - In the Fuel GUI, click Deploy Changes. - -38 Verify the OpenStack Environment - Open the Health Check tab . - Select Select All. - Click Run tests. |