-:Authors: Jonas Bjurel (Ericsson AB)
-:Version: 0.0.3
-
==================================================================================================
OPNFV Installation instructions for the Arno release of OPNFV when using Fuel as a deployment tool
==================================================================================================
+.. contents:: Table of Contents
+ :backlinks: none
+
+
Abstract
========
-This document describes how to install the Arno release of OPNFV when using Fuel as a deployment tool covering it's limitations, dependencies and required system resources.
+This document describes how to install the Arno SR1 release of OPNFV when using Fuel as a deployment tool covering it's limitations, dependencies and required system resources.
License
=======
-Arno release of OPNFV when using Fuel as a deployment tool Docs (c) by Jonas Bjurel (Ericsson AB)
-
-Arno release of OPNFV when using Fuel as a deployment tool Docs are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>.
-
-
-**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
+Arno SR1 release of OPNFV when using Fuel as a deployment tool Docs (c) by Jonas Bjurel (Ericsson AB)
-9 References
+Arno SR1 release of OPNFV when using Fuel as a deployment tool Docs are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>.
-1 Version history
-===================
+Version history
+===============
+--------------------+--------------------+--------------------+--------------------+
| **Date** | **Ver.** | **Author** | **Comment** |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
-| 2015-04-15 | 0.0.1 | Jonas Bjurel | First draft |
-| | | (Ericsson AB) | |
-+--------------------+--------------------+--------------------+--------------------+
-| 2015-04-23 | 0.0.2 | Jonas Bjurel | Minor changes |
-| | | (Ericsson AB) | |
-+--------------------+--------------------+--------------------+--------------------+
-| 2015-05-16 | 0.0.3 | Christopher Price | Minor changes |
-| | | (Ericsson AB) | |
+| 2015-06-03 | 1.0.0 | Jonas Bjurel | Installation |
+| | | (Ericsson AB) | instructions for |
+| | | | the Arno release |
+| | | | |
+| 2015-09-27 | 1.1.0 | Daniel Smith | ARNO SR1-RC1 |
+| | | (Ericsson AB) | update |
+| | | | |
+| | | | |
+--------------------+--------------------+--------------------+--------------------+
-2 Introduction
-================
+Introduction
+============
-This document describes the supported software and hardware configurations for the Arno release of OPNFV when using Fuel as a deployment tool as well as providing guidelines on how to install and configure such reference system.
+This document describes providing guidelines on how to install and configure the Arno SR1 release of OPNFV when using Fuel as a deployment tool including required software and hardware configurations.
-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.
+Although the available installation options gives a high degree of freedom in how the system is set-up including architecture, services and features, etc. said permutations may not provide an OPNFV compliant reference architecture. This instruction provides a step-by-step guide that results in an OPNFV Arno SR1 compliant deployment.
The audience of this document is assumed to have good knowledge in networking and Unix/Linux administration.
-3 Preface
-===========
+Preface
+=======
+
+Before starting the installation of the Arno SR1 release of OPNFV when using Fuel as a deployment tool, some planning must be done.
+
+Retrieving the ISO image
+------------------------
+
+First of all, the Fuel deployment ISO image needs to be retrieved, the .iso image of the Arno SR1 release of OPNFV when using Fuel as a deployment tool can be found at http://artifacts.opnfv.org/arno.2015.2.0/fuel/arno.2015.2.0.fuel.iso
+
-Before starting the installation of Arno release of OPNFV when using Fuel as a deployment tool, some planning must preceed.
+Building the ISO image
+----------------------
-First of all, the Fuel@OPNFV .iso image needs to be retrieved, the Latest stable Arno release of OPNFV when using Fuel as a deployment tool can be found here: <www.opnfv.org/abc/def>
-Alternatively, you may build the .iso from source by cloning the opnfv/genesis git repository:
+Alternatively, you may build the .iso from source by cloning the opnfv/genesis git repository. To retrieve the repository for the Arno release use the following command:
-<git clone https://<linux foundation uid>@gerrit.opnf.org/gerrit/genesis>
+- git clone https://<linux foundation uid>@gerrit.opnf.org/gerrit/genesis
-Check-out the Arno release:
+Check-out the Arno SR1 release tag to set the branch to the baseline required to replicate the Arno SR1 release:
-<cd genesis; git checkout arno>
+- cd genesis; git checkout stable/arno2015.2.0
-Goto the fuel directory and build the .iso
+Go to the fuel directory and build the .iso:
-<cd fuel/build; make all>
+- cd fuel/build; make all
-For more information on how to build, please see "OPNFV Build instructions for - Arno release of OPNFV when using Fuel as a deployment tool <http://www.opnfv.org/xyz>
+For more information on how to build, please see "OPNFV Build instructions for - Arno SR1 release of OPNFV when using Fuel as a deployment tool which you retrieved with the repository at </genesis/fuel/docs/src/build-instructions.rst>
-Next, familiarize yourself with the Fuel 6.0.1 version by reading the following documents:
+Next, familiarize yourself with the Fuel 6.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 planning guide <https://docs.mirantis.com/openstack/fuel/fuel-6.1/planning-guide.html>
-- Fuel user guide <http://docs.mirantis.com/openstack/fuel/fuel-6.0/user-guide.html#user-guide>
+- Fuel user guide <http://docs.mirantis.com/openstack/fuel/fuel-6.1/user-guide.html#user-guide>
-- Fuel operations guide <http://docs.mirantis.com/openstack/fuel/fuel-6.0/operations.html#operations-guide>
+- Fuel operations guide <http://docs.mirantis.com/openstack/fuel/fuel-6.1/operations.html#operations-guide>
+- Fuel Plugin Developers Guide <https://wiki.openstack.org/wiki/Fuel/Plugins>
A number of deployment specific parameters must be collected, those are:
4. Provider NTP addresses
+5. Network Topology you plan to Deploy (VLAN, GRE(VXLAN), FLAT)
+
+6. Linux Distro you intend to deploy.
+
+7. How many nodes and what roles you want to deploy (Controllers, Storage, Computes)
+
+8. Monitoring Options you want to deploy (Ceilometer, MongoDB).
+
+9. 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.
-4 Hardware requirements
-=========================
+Hardware requirements
+=====================
-Following minimum hardware requirements must be met for installation of Fuel@OPNFV:
+The following minimum hardware requirements must be met for the installation of Arno SR1 using Fuel:
+--------------------+------------------------------------------------------+
| **HW Aspect** | **Requirement** |
| | |
+--------------------+------------------------------------------------------+
-| **# of servers** | Minimum 5 (3 for non redundant deployment): |
+| **# of nodes** | Minimum 6 (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 |
| | |
+| | - 1 Ceilometer (VM option) |
++--------------------+------------------------------------------------------+
+| **CPU** | Minimum 1 socket x86_AMD64 with Virtualization |
+| | support |
+--------------------+------------------------------------------------------+
| **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) |
+| **Networks** | 4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) |
| | |
-| | - 2(1)x1GE for admin (PXE) and control (RabitMQ,etc) |
+| | 1 Un-Tagged VLAN for PXE Boot - ADMIN Network |
| | |
+| | note: These can be run on single NIC - or spread out |
+| | over other nics as your hardware supports |
+--------------------+------------------------------------------------------+
-5 Top of the rack (TOR) Configuration requirements
-====================================================
+Help with Hardware Requirements
+===============================
-The switching infrastructure provides connectivity for the OPNFV infra-structure operations, tenant networks (East/West) and provider connectivity (North/South bound connectivity); it also provides needed connectivity for the storage 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 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.
+Calculate hardware requirements:
-Manual configuration of the Arno hardware platform should be carried out according to the Pharos specification <link>.
+You can use the Fuel Hardware Calculator <https://www.mirantis.com/openstack-services/bom-calculator/> to calculate the hardware required for your OpenStack environment.
+When choosing the hardware on which you will deploy your OpenStack environment, you should think about:
-6 OPNFV Software installation and deployment
-==============================================
+ - CPU -- Consider the number of virtual machines that you plan to deploy in your cloud environment and the CPU per virtual machine.
+ - Memory -- Depends on the amount of RAM assigned per virtual machine and the controller node.
+ - Storage -- Depends on the local drive space per virtual machine, remote volumes that can be attached to a virtual machine, and object storage.
+ - Networking -- Depends on the Choose Network Topology, the network bandwidth per virtual machine, and network storage.
-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.
-6.1 Install Fuel master
------------------------
-1. Mount the built .iso file (release/opnfv-<version>.iso) as a boot device to the jump host server.
+Top of the rack (TOR) Configuration requirements
+================================================
-2. Reboot the jump host to establish the Fuel server.
+The switching infrastructure provides connectivity for the OPNFV infrastructure operations, tenant networks (East/West) and provider connectivity (North/South bound connectivity); it also provides needed connectivity for the storage Area Network (SAN). To avoid traffic congestion, it is strongly suggested that three physically 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 physically separated networks.
- - The system now boots from the ISO image.
+The physical TOR switches are **not** automatically configured from the OPNFV reference platform. All the networks involved in the OPNFV infrastructure as well as the provider networks and the private tenant VLANs needs to be manually configured.
-3. Change the grub boot parameters
+Manual configuration of the Arno SR1 hardware platform should be carried out according to the Pharos specification TODO-<insert link to Pharos ARNO SR1 Specification>
- - When the grub boot menu shows up - Press Tab to edit the kernel parameters
+OPNFV Software installation and deployment
+==========================================
- - Change <showmenu=no> to <showmenu=yes>.
+This section describes the installation of the OPNFV installation server (Fuel master) as well as the deployment of the full OPNFV reference platform stack across a server cluster.
- - Change <netmask=255.255.255.0> to <netmask=255.255.0.0>.
+Install Fuel master
+-------------------
+1. Mount the Arno SR1 ISO file as a boot device to the jump host server.
+
+2. Reboot the jump host to establish the Fuel server.
+
+ - The system now boots from the ISO image.
+
+ - Select 'DVD Fuel Install (Static IP)'
- Press [Enter].
-4 Wait until screen Fuel setup is shown (Note: This can take up to 30 minutes).
+3. 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):
+4. Configure DHCP/Static IP information for your FUEL node - For example, ETH0 is 10.20.0.2/24 for FUEL booting and ETH1 is DHCP in your corporate/lab network.
- - Static Pool Start 10.20.0.3
+ - Configure eth1 or other network interfaces here as well (if you have them present on your FUEL server).
- - Static Pool End 10.20.0.254
+5. Select PXE Setup and change the following fields to appropriate values (example below):
- - DHCP Pool Start 10.20.128.3
+ - DHCP Pool Start 10.20.0.3
- - DHCP Pool End 10.20.128.254
+ - DHCP Pool End 10.20.0.254
-6. Select DNS & Hostname and change the following fields to appropriate values:
+ - DHCP Pool Gateway 10.20.0.2 (ip of Fuel node)
- - Hostname <CEE Region name>-fuel
+ - Hostname <OPNFV Region name>-fuel
- Domain <Domain Name>
- Hostname to test DNS <Hostname to test DNS>
-7. Select Time Sync and change the following fields to appropriate values:
+6. 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>
+ - 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.
+7. 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)
--------------------------------------
+Boot the Node Servers
+---------------------
+
+After the Fuel Master node has rebooted from the above step and is at the login prompt, you should boot the Node Servers (Your Compute/Control/Storage blades (nested or real)) with a PXE Booting Scheme so that the FUEL
+Master can pick them up for control.
+
+8. 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.
+
+9. Reboot all the control and compute blades.
+
+10. 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.
+
+
+
+Install ODL Plugin on FUEL node
+-------------------------------
+
+11. SSH to your FUEL node (e.g. root@10.20.0.2 pwd: r00tme)
+
+12. Verify the plugin exists at /opt/opnfv/opendaylight-0.6-0.6.1-1.noarch.rpm
-9. Connect to Fuel with a browser towards port 8000
+13. Install the plugin with the command
-10. Create and name a new OpenStack environment, to be installed.
+ - "fuel plugins --install /opt/opnfv/opendaylight-0.6-0.6.1-1.noarch.rpm"
-11. Select <Juno on Ubuntu> or <Juno on CentOS> as per your which in the "OpenStack Release" field.
+ - Expected output: "Plugin opendaylight-0.6-0.6.1-1.noarch.rpm was successfully installed."
-12. Select deployment mode.
- - Select the Multi-node with HA.
+Create an OPNFV Environment
+---------------------------
-13. Select compute node mode.
+14. Connect to Fuel WEB UI with a browser towards port http://<ip of fuel server>:8000 (login admin/admin)
- - Select KVM as hypervisor (unless you're not deploying bare metal or nested KVM/ESXI).
+15. Create and name a new OpenStack environment, to be installed.
-14. Select network mode.
+16. Select <Juno on Ubuntu> or <Juno on CentOS> as per your which in the "OpenStack Release" field and press "Next"
- - Select Neutron with VLAN segmentation
+17. Select compute virtulization method.
- ** Note: This will later be overridden to VXLAN by OpenDaylight.**
+ - Select KVM as hypervisor (or one of your choosing) and press "Next"
-15. Select Storage Backends.
+18. Select network mode.
- - Select Ceph for Cinder and default for glance.
+ - Select Neutron with GRE segmentation and press "Next"
-16. Select additional services.
+ Note: this is the supportted method when using the ODL installation, other options will not work with the plugin and this Instruction Set.
- - Check option <Install Celiometer (OpenStack Telemetry)>.
+19. Select Storage Back-ends.
-17. Create the new environment.
+ - Select "Yes, use Ceph" if you intend to deploy Ceph Backends and press "Next"
-6.3 Configure the OPNFV environment
------------------------------------
-18. Enable PXE booting
+20. Select additional services you wish to install.
- - 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.
+ - Check option <Install Celiometer (OpenStack Telemetry)> and press "Next"
+ Note: If you use Ceilometer and you only have 5 nodes, you may have to run in a 3/1/1 (controller/ceilo-mongo/compute) configuration. Suggest adding more compute nodes
-19. Reboot all the controller- and compute blades.
+21. Create the new environment.
-20. Wait for the availability of nodes showing up in the Fuel GUI.
+ - Click "Create" Button
+
+Configure the OPNFV environment
+-------------------------------
+
+22. Enable PXE booting (if you haven't done this already)
+
+ - 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.
+
+23. 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.
+24. Open the environment you previously created.
-22. Open the networks tab.
+25. Open the networks tab.
-23. Update the public network configuration.
+26. Update the Public network configuration.
Change the following fields to appropriate values:
- CIDR to <CIDR for Public IP Addresses>
+ - Check VLAN tagging.
+
+ - Set appropriate VLAN id.
+
- Gateway to <Gateway for Public IP Addresses>
- - Check VLAN tagging.
+ - Set floating ip ranges
- - Set appropriate VLAN id.
-24. Update the management network configuration.
+27. Update the Storage Network Configuration
+
+ - Set CIDR to appropriate value (default 192.168.1.0/24)
+
+ - Set vlan to appropriate value (default 102)
- - Set CIDR to 172.16.255.128/25 (or as per your which).
+28. Update the Management network configuration.
+
+ - Set CIDR to appropriate value (default 192.168.0.0/24)
- Check VLAN tagging.
- - Set appropriate VLAN id.
+ - Set appropriate VLAN id. (default 101)
+
+29. Update the Private Network Information
-25. Update the Neutron L2 configuration.
+ - Set CIDR to appropriate value (default 192.168.2.0/24
- - Set VLAN ID range.
+ - Check and set VLAN tag appropriately (default 103)
-26. Update the Neutron L3 configuration.
+30. 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
+ - Set Guest OS DNS Server values appropriately
-27. Save Settings.
+31. Save Settings.
-28. Click "verify network" to check the network set-up consistency and connectivity
+32. Click on the "Nodes" Tab in the FUEL WEB UI.
-29. Update the storage configuration.
+33. Assign roles.
-30. Open the nodes tab.
+ - Click on "+Add Nodes" button
-31. Assign roles.
+ - Check "Controller" and the "Storage-Ceph OSD" in the Assign Roles Section
- - Check <Controller and Telemetry MongoDB>.
-
- - Check the three servers you want to be installed as Controllesr in pane <Assign Role>.
+ - Check the 3 Nodes you want to act as Controllers from the bottom half of the screen
- Click <Apply Changes>.
- - Check <Compute>.
+ - Click on "+Add Nodes" button
+
+ - Check "Compute" in the Assign Roles Section
- - Check nodes to be installed as Compute nodes in pane Assign Role.
+ - Check the Nodes that you want to act as Computes from the bottom half of the screen
- Click <Apply Changes>.
-32. Configure interfaces.
- - Check Select <All> to select all nodes with Control, Telemetry . MongoDB and Compute node roles.
+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
-6.4 Deploy the OPNFV environment
---------------------------------
-**NOTE: Before the deployment is performed, the OPNFV pre-deploy script must be ran**
+ - Note: Set MTU level to at least MTU=2090 (recommended MTU=2140 for SDN over VXLAN Usage) for each network
+
+ - Click Apply
+
+Enable ODL
+----------
+
+35. In the FUEL UI of your Enviornment, click the "Settings" Tab
+
+ - Enable OpenStack debug logging (in the Common Section) - optional
+
+ - Check the OpenDaylight Lithium Plugin Section
+
+ - Check to enable VXLAN
+
+ - Modify VNI and Port Range if desired
+
+ - Click "Save Settings" at the bottom to Save.
+
-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>
+OPTIONAL - Set Local Mirror Repos
+---------------------------------
-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.
+The following steps can be executed if you are in an environment with no connection to the internet. The Fuel server delivers a local repo that can be used for
+installation / deployment of openstack.
-37. Deploy the environment.
+36. In the Fuel UI of your Environment, click the Settings Tab and scroll to the Repositories Section.
+
+ - Replace the URI values for the "Name" values outlined below:
+
+ - "ubuntu" URI="deb http://<ip-of-fuel-server>:8080/ubuntu-part trusty main"
+ - "ubuntu-security" URI="deb http://<ip-of-fuel-server>:8080/ubuntu-part trusty main"
+ - "ubuntu-updates" URI="deb http://<ip-of-fuel-server>:8080/ubuntu-part trusty main"
+ - "mos-updates" URI="deb http://<ip-of-fuel-server>:8080/mos-ubuntu mos6.1-updates main restricted"
+ - "mos-security" URI="deb http://<ip-of-fuel-server>:8080/mos-ubuntu mos6.1-security main restricted"
+ - "mos-holdback" URI="deb http://<ip-of-fuel-server>:8080/mos-ubuntu mos6.1-holdback main restricted"
+
+ - Click "Save Settings" at the bottom to Save your changes
+
+Verify Networks
+---------------
+
+Its is important that Verify Networks be done as it will ensure that you can not only communicate on the networks you have setup, but can fetch the packages needed for a succesful
+deployment.
+
+37. From the FUEL UI in your Environment, Select the Networks Tab
+
+ - At the bottom of the page, Select "Verify Networks"
+
+ - Continue to fix your topology (physical switch, etc) until the "Verification Succeeded - Your network is configured correctly" message is shown
+
+Deploy Your Environment
+-----------------------
+
+38. Deploy the environment.
In the Fuel GUI, click Deploy Changes.
-7 Installation health-check
-=============================
+ - Wait until your Environment is deployed and the Horizon URI to connect is displayed in the FUEL GUI for your Environment
+
+Installation health-check
+=========================
+
+39. Perform system 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:
+ - Click the "Health Check" tab inside your Environment in the FUEL Web UI
-- Select the “Health check” TAB.
-- Select all test-cases
-- And click “Run tests”
+ - Check "Select All" and Click "Run Tests"
-All test cases except the following should pass:
+ Note: Live-Migraition test will fail (Bug in ODL currently), you can skip this test in the list if you choose to not see the error message, simply uncheck it in the list
-8 Post installation and deployment actions
-============================================
-**-**
+ - Allow tests to run and investigate results where appropriate
-9 References
-=============
+40. Verify that the OpenDaylight GUI is accessible
-9.1 OPNFV
--------------
+Point your browser to the following URL: http://{Controller-VIP}:8181/index.html> and login:
-9.2 OpenStack
------------------
+ - Username: admin
+ - Password: admin
-9.3 OpenDaylight
---------------------
+References
+==========
-9.4 Fuel
+OPNFV
+-----
+
+`OPNFV Home Page <www.opnfv.org>`_
+
+`OPNFV Genesis project page <https://wiki.opnfv.org/get_started>`_
+
+OpenStack
+---------
+
+`OpenStack Juno Release artifacts <http://www.openstack.org/software/juno>`_
+
+`OpenStack documentation <http://docs.openstack.org>`_
+
+OpenDaylight
------------
+
+`OpenDaylight artifacts <http://www.opendaylight.org/software/downloads>`_
+
+Fuel
+----
+
+`Fuel documentation <https://wiki.openstack.org/wiki/Fuel>`_
+
+:Authors: Daniel Smith (Ericsson AB)
+:Version: 1.1.0
+
+**Documentation tracking**
+
+Revision: _sha1_
+
+Build date: _date
Code Review / genesis.git / blobdiff