-:Authors: Christopher Price (christopher.price@ericsson.com)
-:Version: 0.0.1
-
=====================================
OPNFV User Guide for the Arno release
=====================================
License
=======
+
OPNFV User Guide for the Arno release (c) by Christopher Price (christopher.price@ericsson.com)
OPNFV User Guide for the Arno release is 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/>.
| 2015-05-28 | 0.0.1 | Christopher Price | Initial version |
| | | (Ericsson AB) | |
+--------------------+--------------------+--------------------+--------------------+
+| 2015-06-02 | 0.0.2 | Christopher Price | Minor Updates |
+| | | (Ericsson AB) | |
++--------------------+--------------------+--------------------+--------------------+
.. contents:: Table of Contents
In order to deploy the Arno release on a Pharos compliant lab using the Fuel deployment toolchain you should follow in the Fuel installation guide: http://artifacts.opnfv.org/genesis/fuel/docs/installation-instructions.html
+Enabling or disabling OpenDaylight and the native Neutron driver
+----------------------------------------------------------------
+
+You may find that you wish to adjust the system by enabling or disabling the native OpenStack Neutron driver depending on the tasks you are trying to achieve with the platform. Each of the deployment tools has the option to deploy with or without OpenDaylight enabled. Details of the available delpoyment options can be found in the associated installation-instructions, please note the platform validation procedures expect a fully deployed platform and results may vary depending on the options selected.
+
Deployment Validation
---------------------
The Arno release provides a platform for deploying software on virtual infrastructure. The majority of operations to be executed on the platform revolve around deploying, managing and removing software (applications) on the platform itself. Application deployment is covered in the following sections, however some platform operations you may want to perform include setting up a tenant, in OpenStack tenants are also known as projects in this document we will refer to them as tenants, and associated users for that tenant.
OpenStack provides a good overview of how to create your first tenant for deploying your applications. You should create a tenant for your applications, associate users with the tenant and assign quota's.
- - Open the OpenStack console (Horizon) you should find this by logging into your control node, for POD1 of the OPNFV lab this would be <172.30.9.70:80>
+- Open the OpenStack console (Horizon) you should find this by logging into your control node; for example to access the console of POD1 of the OPNFV lab you would browse to <172.30.9.70:80>
- Create your tenant and users by following the instructions at: http://docs.openstack.org/openstack-ops/content/projects_users.html
Further actions and activities for checking logs and status can be found in other areas of the operations document: http://docs.openstack.org/openstack-ops/content/openstack-ops_preface.html
Frequently Asked Questions
==========================
+Does OPNFV provide support for the Arno release?
+------------------------------------------------
+
+The Arno release of OPNFV is intended to be a developmental release and is not considered suitable for production deployment or at scale testing activities. As a developmental release, and in the spirit of collaborative development, we want as much feedback from the community as possible on your experiences with the platform and how the release can be improved.
+
+Support for Arno is provided in two ways:
+
+You can engage with the community to help us improve and further develop the OPNFV platform by raising Jira Bugs or Tasks, and pushing correction patches to our repositories.
+
+ - To access Jira for issue reporting or improvement proposals head to: https://jira.opnfv.org/
+ - To get started helping out developing the platform head to: https://wiki.opnfv.org/developer
+
+Alternatively if you are intending to invest your time as a user of the platform you can request support and help from our mailing list at: mailto://support@opnfv.org
+
License
=======
Foreman
-------
+
+:Authors: Christopher Price (christopher.price@ericsson.com)
+:Version: 0.0.2
+
+**Documentation tracking**
+
+Revision: _sha1_
+
+Build date: _date_
+
#Now lets got and fetch the ODL distribution
RUN echo "Fetching ODL"
-RUN wget https://nexus.opendaylight.org/content/groups/public/org/opendaylight/integration/distribution-karaf/0.2.2-Helium-SR2/distribution-karaf-0.2.2-Helium-SR2.tar.gz -O /opt/odl_source/distribution-karaf-0.2.2-Helium-SR2.tar.gz
+RUN wget https://nexus.opendaylight.org/content/groups/public/org/opendaylight/integration/distribution-karaf/0.2.3-Helium-SR3/distribution-karaf-0.2.3-Helium-SR3.tar.gz -O /opt/odl_source/distribution-karaf-0.2.3-Helium-SR3.tar.gz
RUN echo "Untarring ODL inplace"
RUN mkdir -p /opt/odl
-RUN tar zxvf /opt/odl_source/distribution-karaf-0.2.2-Helium-SR2.tar.gz -C /opt/odl
+RUN tar zxvf /opt/odl_source/distribution-karaf-0.2.3-Helium-SR3.tar.gz -C /opt/odl
RUN echo "Installing DLUX and other features into ODL"
#COPY dockerfile/container_scripts/start_odl_docker.sh /etc/init.d/start_odl_docker.sh
-:Authors: Tim Rozet (trozet@redhat.com)
-:Version: 0.0.2
-
=======================================================================================================
OPNFV Installation instructions for the Arno release of OPNFV when using Foreman as a deployment tool
=======================================================================================================
+
+.. contents:: Table of Contents
+ :backlinks: none
+
+
Abstract
========
| 2015-05-27 | 0.0.2 | Christopher Price | Minor changes & |
| | | (Ericsson AB) | formatting |
+--------------------+--------------------+--------------------+--------------------+
-
-
-.. contents:: Table of Contents
- :backlinks: none
+| 2015-06-02 | 0.0.3 | Christopher Price | Minor changes & |
+| | | (Ericsson AB) | formatting |
++--------------------+--------------------+--------------------+--------------------+
Introduction
Foreman
-------
+
+:Authors: Tim Rozet (trozet@redhat.com)
+:Version: 0.0.3
+
+**Documentation tracking**
+
+Revision: _sha1_
+
+Build date: _date_
+
-:Authors: Tim Rozet (trozet@redhat.com)
-:Version: 0.1
-
===========================================================================================
OPNFV Release Note for the Arno release of OPNFV when using Foreman as a deployment tool
===========================================================================================
+
+.. contents:: Table of Contents
+ :backlinks: none
+
+
Abstract
========
-This document provides the release notes for ARNO-RC2 release candidate of Foreman/QuickStack@OPNFV.
+This document provides the release notes for Arno release with the Foreman/QuickStack deployment toolchain.
License
=======
-All Foreman/QuickStack and "common" entities are protected by the Apache License ( http://www.apache.org/licenses/ )
-
-**Contents**
-
-1 Version History
-2 Important notes
-
-3 Summary
-
-4 Delivery Data
-
-5 Known Limitations, Issues and Workarounds
-
-6 Test Result
+All Foreman/QuickStack and "common" entities are protected by the Apache License ( http://www.apache.org/licenses/ )
-7 References
-1 Version history
-===================
+Version history
+===============
+--------------------+--------------------+--------------------+--------------------+
| **Date** | **Ver.** | **Author** | **Comment** |
| 2015-04-16 | 0.1.0 | Tim Rozet | First draft |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
+| 2015-06-02 | 0.1.1 | Chris Price | Minor Edits |
+| | | | |
++--------------------+--------------------+--------------------+--------------------+
-2 Important notes
-===================
+Important notes
+===============
-This is the first OPNFV Arno pre-release that implements the deploy stage of the OPNFV CI pipeline.
+This is the initial OPNFV Arno release that implements the deploy stage of the OPNFV CI pipeline.
Carefully follow the installation-instructions which guide a user on how to deploy OPNFV using Foreman/QuickStack installer.
-3 Summary
-===========
-
-Arno Foreman/QuickStack@OPNFV is an installer capable of setting up an OPNFV target system. The current definition of an OPNFV target system is OpenStack Juno upstream project versioncombined with OpenDaylight version: Helium. The system is deployed with OpenStack High Availability (HA) for most OpenStack services. OpenDaylight is deployed in non-HA form as HA is not availble for Arno release. Ceph storage is used as Cinder backend, and is the only supported storage for Arno. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller node.
+Summary
+=======
-This Arno pre-release of Foreman/QuickStack@OPNFV adds the deploy stage of the OPNFV CI pipeline
+Arno release with the Foreman/QuickStack deployment toolchain will establish an OPNFV target system on a Pharos compliant lab infrastructure. The current definition of an OPNFV target system is and OpenStack Juno version combined with OpenDaylight version: Helium. The system is deployed with OpenStack High Availability (HA) for most OpenStack services. OpenDaylight is deployed in non-HA form as HA is not availble for Arno release. Ceph storage is used as Cinder backend, and is the only supported storage for Arno. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller node.
- Documentation is built by Jenkins
- .iso image is built by Jenkins
-- Jenkins deploys an Foreman/QuickStack@OPNFV stack to baremetal, which includes 3 control+network nodes, and 2 compute nodes.
+- Jenkins deploys an Arno release with the Foreman/QuickStack deployment toolchain baremetal, which includes 3 control+network nodes, and 2 compute nodes.
-Automatic test of the deployed system is not part of this pre-release.
-
-4 Release Data
-================
+Release Data
+============
+--------------------------------------+--------------------------------------+
-| **Project** | Arno/genesis/bgs |
+| **Project** | genesis/bgs |
| | |
+--------------------------------------+--------------------------------------+
-| **Repo/tag** | genesis/arno-rc2 |
+| **Repo/tag** | genesis/arno_1.0.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Arno RC2 |
+| **Release designation** | Arno 1.0.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | 2015-04-23 |
+| **Release date** | 2015-06-04 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | OPNFV Internal quality assurance |
-| | and CI Pipline dry-run |
+| **Purpose of the delivery** | OPNFV Arno release |
| | |
+--------------------------------------+--------------------------------------+
-4.1 Version change
-------------------
+Version change
+--------------
-4.1.1 Module version changes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-This is the first tracked version of genesis-Foreman/QuickStack. It is based on following upstream versions:
+Module version changes
+~~~~~~~~~~~~~~~~~~~~~~
+This is the first tracked version of the Arno release with the Foreman/QuickStack deployment toolchain. It is based on following upstream versions:
- OpenStack (Juno release)
- CentOS 7
-4.1.2 Document version changes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-This is the first tracked version of genesis-Foreman/QuickStack. It comes with the following documentation:
+Document version changes
+~~~~~~~~~~~~~~~~~~~~~~~~
-- OPNFV Installation instructions for - Foreman/QuickStack@OPNFV - ver. 0.0.1
-- OPNFV Release Note for "Arno-RC2 release candidate" - Foreman/QuickStack@OPNFV - ver. 0.1 (this document)
+This is the first tracked version of Arno release with the Foreman/QuickStack deployment toolchain. The following documentation is provided with this release:
-4.2 Reason for version
-----------------------
-4.2.1 Feature additions
-~~~~~~~~~~~~~~~~~~~~~~~
+- OPNFV Installation instructions for the Arno release with the Foreman/QuickStack deployment toolchain - ver. 1.0.0
+- OPNFV Release Notes for the Arno release with the Foreman/QuickStack deployment toolchain - ver. 1.0.0 (this document)
+
+Feature additions
+~~~~~~~~~~~~~~~~~
+--------------------------------------+--------------------------------------+
| **JIRA REFERENCE** | **SLOGAN** |
| | using Foreman/Quickstack. |
+--------------------------------------+--------------------------------------+
-4.2.2 Bug corrections
-~~~~~~~~~~~~~~~~~~~~~
+Bug corrections
+~~~~~~~~~~~~~~~
**JIRA TICKETS:**
| | |
+--------------------------------------+--------------------------------------+
-4.3 Deliverables
-----------------
+Deliverables
+------------
-4.3.1 Software deliverables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Software deliverables
+~~~~~~~~~~~~~~~~~~~~~
Foreman/QuickStack@OPNFV .iso file
deploy.sh - Automatically deploys Target OPNFV System to Bare Metal
-4.3.2 Documentation deliverables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- OPNFV Installation instructions for - Foreman/QuickStack@OPNFV - ver. 0.0.1
-- OPNFV Release Note for "Arno-RC2 release candidate" - Foreman/QuickStack@OPNFV - ver. 0.1 (this document)
+Documentation deliverables
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+- OPNFV Installation instructions for the Arno release with the Foreman/QuickStack deployment toolchain - ver. 1.0.0
+- OPNFV Release Notes for the Arno release with the Foreman/QuickStack deployment toolchain - ver. 1.0.0 (this document)
-5 Known Limitations, Issues and Workarounds
-============================================
+Known Limitations, Issues and Workarounds
+=========================================
-5.1 System Limitations
--------------------------
+System Limitations
+------------------
**Max number of blades:** 1 Foreman/QuickStack master, 3 Controllers, 20 Compute blades
**Min master requirements:** At least 2048 MB of RAM
-5.2 Known issues
--------------------
+Known issues
+------------
**JIRA TICKETS:**
| | by puppet |
+--------------------------------------+--------------------------------------+
-5.3 Workarounds
-------------------
+Workarounds
+-----------
**-**
-6 Test Result
-==============
+Test Result
+===========
-Foreman/QuickStack@OPNFV Arno RC2 has undergone QA test runs with the following results:
+The Arno release with the Foreman/QuickStack deployment toolchain has undergone QA test runs with the following results:
+--------------------------------------+--------------------------------------+
| **TEST-SUITE** | **Results:** |
+--------------------------------------+--------------------------------------+
-7 References
-=============
+References
+==========
For more information on the OPNFV Arno release, please see:
http://wiki.opnfv.org/release/arno
+
+:Authors: Tim Rozet (trozet@redhat.com)
+:Version: 0.2
+
+**Documentation tracking**
+
+Revision: _sha1_
+
+Build date: _date_
+
source => '/etc/puppet/modules/opnfv/scripts/config_net_odl.sh',
mode => 750,
}
+ file { '/opt/opnfv/odl/change.sh':
+ ensure => present,
+ source => '/etc/puppet/modules/opnfv/scripts/change.sh',
+ mode => 750,
+ }
# fix failed to find the cgroup root issue
--- /dev/null
+#!/bin/bash
+# script to remove bridges and reset networking for ODL
+
+
+#VARS
+MODE=0
+DNS=8.8.8.8
+
+#ENV
+source ~/openrc
+
+# GET IPS for that node
+function get_ips {
+ BR_MGMT=`grep address /etc/network/ifcfg_backup/ifcfg-br-mgmt | awk -F" " '{print $2}'`
+ BR_STORAGE=`grep address /etc/network/ifcfg_backup/ifcfg-br-storage | awk -F" " '{print $2}'`
+ BR_FW_ADMIN=`grep address /etc/network/ifcfg_backup/ifcfg-br-fw-admin | awk -F" " '{print $2}'`
+ BR_EX=`grep address /etc/network/ifcfg_backup/ifcfg-br-ex | awk -F" " '{print $2}'`
+ DEF_NETMASK=255.255.255.0
+ DEF_GW=172.30.9.1
+}
+
+function backup_ifcfg {
+ echo " backing up "
+ mkdir -p /etc/network/ifcfg_backup
+ mv /etc/network/interfaces.d/ifcfg-br-ex /etc/network/ifcfg_backup/.
+ mv /etc/network/interfaces.d/ifcfg-br-fw-admin /etc/network/ifcfg_backup/.
+ mv /etc/network/interfaces.d/ifcfg-br-mgmt /etc/network/ifcfg_backup/.
+ mv /etc/network/interfaces.d/ifcfg-br-storage /etc/network/ifcfg_backup/.
+ mv /etc/network/interfaces.d/ifcfg-br-prv /etc/network/ifcfg_backup/.
+ mv /etc/network/interfaces.d/ifcfg-eth0 /etc/network/ifcfg_backup/.
+ mv /etc/network/interfaces.d/ifcfg-eth1 /etc/network/ifcfg_backup/.
+ rm -rf /etc/network/interfaces.d/ifcfg-eth1.300
+ rm -rf /etc/network/interfaces.d/ifcfg-eth1.301
+ rm -rf /etc/network/interfaces.d/ifcfg-eth1
+ rm -rf /etc/network/interfaces.d/ifcfg-eth0
+
+}
+
+
+function create_ifcfg_br_mgmt {
+ echo "migrating br_mgmt"
+ echo "auto eth1.300" >> /etc/network/interfaces.d/ifcfg-eth1.300
+ echo "iface eth1.300 inet static" >> /etc/network/interfaces.d/ifcfg-eth1.300
+ echo " address $BR_MGMT" >> /etc/network/interfaces.d/ifcfg-eth1.300
+ echo " netmask $DEF_NETMASK" >> /etc/network/interfaces.d/ifcfg-eth1.300
+}
+
+function create_ifcfg_br_storage {
+ echo "migration br_storage"
+ echo "auto eth1.301" >> /etc/network/interfaces.d/ifcfg-eth1.301
+ echo "iface eth1.301 inet static" >> /etc/network/interfaces.d/ifcfg-eth1.301
+ echo " address $BR_STORAGE" >> /etc/network/interfaces.d/ifcfg-eth1.301
+ echo " netmask $DEF_NETMASK" >> /etc/network/interfaces.d/ifcfg-eth1.301
+}
+
+function create_ifcfg_br_fw_admin {
+ echo " migratinng br_fw_admin"
+ echo "auto eth1" >> /etc/network/interfaces.d/ifcfg-eth1
+ echo "iface eth1 inet static" >> /etc/network/interfaces.d/ifcfg-eth1
+ echo " address $BR_FW_ADMIN" >> /etc/network/interfaces.d/ifcfg-eth1
+ echo " netmask $DEF_NETMASK" >> /etc/network/interfaces.d/ifcfg-eth1
+}
+
+function create_ifcfg_eth0 {
+ echo "migratinng br-ex to eth0 - temporarily"
+ echo "auto eth0" >> /etc/network/interfaces.d/ifcfg-eth0
+ echo "iface eth0 inet static" >> /etc/network/interfaces.d/ifcfg-eth0
+ echo " address $BR_EX" >> /etc/network/interfaces.d/ifcfg-eth0
+ echo " netmask $DEF_NETMASK" >> /etc/network/interfaces.d/ifcfg-eth0
+ echo " gateway $DEF_GW" >> /etc/network/interfaces.d/ifcfg-eth0
+}
+
+function set_mode {
+ if [ -d "/var/lib/glance/images" ]
+ then
+ echo " controller "
+ MODE=0
+ else
+ echo " compute "
+ MODE=1
+ fi
+}
+
+
+function stop_ovs {
+ echo "Stopping OpenVSwitch"
+ service openvswitch-switch stop
+
+}
+
+function start_ovs {
+ echo "Starting OVS"
+ service openvswitch-switch start
+ ovs-vsctl show
+}
+
+
+function clean_ovs {
+ echo "cleaning OVS DB"
+ stop_ovs
+ rm -rf /var/log/openvswitch/*
+ mkdir -p /opt/opnfv/odl/ovs_back
+ cp -pr /etc/openvswitch/* /opt/opnfv/odl/ovs_back/.
+ rm -rf /etc/openvswitch/conf.db
+ echo "restarting OVS - you should see Nothing there"
+ start_ovs
+}
+
+
+
+function reboot_me {
+ reboot
+}
+
+function allow_challenge {
+ sed -i -e 's/ChallengeResponseAuthentication no/ChallengeResponseAuthentication yes/g' /etc/ssh/sshd_config
+ service ssh restart
+}
+
+function clean_neutron {
+ subnets=( `neutron subnet-list | awk -F" " '{print $2}' | grep -v id | sed '/^$/d'` )
+ networks=( `neutron net-list | awk -F" " '{print $2}' | grep -v id | sed '/^$/d'` )
+ ports=( `neutron port-list | awk -F" " '{print $2}' | grep -v id | sed '/^$/d'` )
+ routers=( `neutron router-list | awk -F" " '{print $2}' | grep -v id | sed '/^$/d'` )
+
+ #display all elements
+ echo "SUBNETS: ${subnets[@]} "
+ echo "NETWORKS: ${networks[@]} "
+ echo "PORTS: ${ports[@]} "
+ echo "ROUTERS: ${routers[@]} "
+
+
+ # get port and subnet for each router
+ for i in "${routers[@]}"
+ do
+ routerport=( `neutron router-port-list $i | awk -F" " '{print $2}' | grep -v id | sed '/^$/d' `)
+ routersnet=( `neutron router-port-list $i | awk -F" " '{print $8}' | grep -v fixed | sed '/^$/d' | sed 's/,$//' | sed -e 's/^"//' -e 's/"$//' `)
+ done
+
+ echo "ROUTER PORTS: ${routerport[@]} "
+ echo "ROUTER SUBNET: ${routersnet[@]} "
+
+ #remove router subnets
+ echo "router-interface-delete"
+ for i in "${routersnet[@]}"
+ do
+ neutron router-interface-delete ${routers[0]} $i
+ done
+
+ #remove subnets
+ echo "subnet-delete"
+ for i in "${subnets[@]}"
+ do
+ neutron subnet-delete $i
+ done
+
+ #remove nets
+ echo "net-delete"
+ for i in "${networks[@]}"
+ do
+ neutron net-delete $i
+ done
+
+ #remove routers
+ echo "router-delete"
+ for i in "${routers[@]}"
+ do
+ neutron router-delete $i
+ done
+
+ #remove ports
+ echo "port-delete"
+ for i in "${ports[@]}"
+ do
+ neutron port-delete $i
+ done
+
+ #remove subnets
+ echo "subnet-delete second pass"
+ for i in "${subnets[@]}"
+ do
+ neutron subnet-delete $i
+ done
+
+}
+
+function set_dns {
+ sed -i -e 's/nameserver 10.20.0.2/nameserver $DNS/g' /etc/resolv.conf
+}
+
+
+#OUTPUT
+
+function check {
+ echo $BR_MGMT
+ echo $BR_STORAGE
+ echo $BR_FW_ADMIN
+ echo $BR_EX
+}
+
+### MAIN
+
+
+set_mode
+backup_ifcfg
+get_ips
+create_ifcfg_br_mgmt
+create_ifcfg_br_storage
+create_ifcfg_br_fw_admin
+if [ $MODE == "0" ]
+then
+ create_ifcfg_eth0
+fi
+allow_challenge
+clean_ovs
+check
+reboot_me
+
+
-:Authors: Jonas Bjurel (Ericsson AB)
-:Version: 0.0.4
-
==================================================================================================
OPNFV Installation instructions for the Arno release of OPNFV when using Fuel as a deployment tool
==================================================================================================
+.. contents:: Table of Contents
+ :backlinks: none
+
+
Abstract
========
| 2015-05-27 | 0.0.4 | Christopher Price | Minor changes |
| | | (Ericsson AB) | |
+--------------------+--------------------+--------------------+--------------------+
-
-
-.. contents:: Table of Contents
- :backlinks: none
+| 2015-06-02 | 0.0.5 | Christopher Price | Minor changes |
+| | | (Ericsson AB) | |
++--------------------+--------------------+--------------------+--------------------+
Introduction
Before starting the installation of the Arno release of OPNFV when using Fuel as a deployment tool, some planning must be done.
-First of all, the Fuel deployment .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>
+Retrieving the ISO image
+------------------------
+
+First of all, the Fuel deployment arnofuel.iso image needs to be retrieved, the .iso image of the Arno release of OPNFV when using Fuel as a deployment tool can be found here at http://artifacts.opnfv.org/arno.2015.1.0/fuel/arno.2015.1.0.fuel.iso
+
+Building the ISO image
+----------------------
-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>
-Check-out the Arno release:
+Check-out the Arno release tag to set the branch to the baseline required to replicate the Arno release.
-<cd genesis; git checkout arno>
+<cd genesis; git checkout arno.2015.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 "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 release of OPNFV when using Fuel as a deployment tool which you retrieves 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:
- 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
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.
-Manual configuration of the Arno hardware platform should be carried out according to the Pharos specification <link>.
+Manual configuration of the Arno hardware platform should be carried out according to the Pharos specification http://artifacts.opnfv.org/arno.2015.1.0/docs/pharos-spec.arno.2015.1.0.pdf
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.
+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.
Install Fuel master
-------------------
-1. Mount the built .iso file (release/opnfv-<version>.iso) as a boot device to the jump host server.
+1. Mount the built fuel.arno.2015.1.0.iso file as a boot device to the jump host server.
2. Reboot the jump host to establish the Fuel server.
Fuel
----
+
+:Authors: Jonas Bjurel (Ericsson AB)
+:Version: 0.0.5
+
+**Documentation tracking**
+
+Revision: _sha1_
+
+Build date: _date_
+
-:Authors: Jonas Bjurel (Ericsson)
-:Version: 0.3
-
=====================================================================================
OPNFV Release Note for the Arno release of OPNFV when using Fuel as a deployment tool
=====================================================================================
+
+.. contents:: Table of Contents
+ :backlinks: none
+
+
Abstract
========
-This document compiles the release notes for the ARNO release, when using Fuel as a deployment tool.
+This document compiles the release notes for the Arno release of OPNFV when using Fuel as a deployment tool.
License
=======
-Arno release with th Fuel deployment tool Docs (c) by Jonas Bjurel (Ericsson AB)
-
-Arno release with the Fuel 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
+Arno release with the Fuel deployment tool Docs (c) by Jonas Bjurel (Ericsson AB)
-2 Important notes
-
-3 Summary
-
-4 Delivery Data
-
-5 Known Limitations, Issues and Workarounds
-
-6 Test Result
-
-7 References
+Arno release with the Fuel 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-05-12 | 0.3 | Chris Price | Minor edits |
| | | | |
+--------------------+--------------------+--------------------+--------------------+
+| 2015-06-02 | 0.4 | Chris Price | Minor edits |
+| | | | |
++--------------------+--------------------+--------------------+--------------------+
-2 Important notes
-===================
+Important notes
+===============
For the first OPNFV release (Arno), these notes introduce use of `OpenStack Fuel <https://wiki.openstack.org/wiki/Fuel>`_ for the deployment stage of the OPNFV continuous integration (CI) pipeline. The goal of the Arno release and this Fuel-based deployment process is to establish a foundational platform accelerating further development of the OPNFV infrastructure.
Carefully follow the installation-instructions and pay special attention to the pre-deploy script that needs to be run before deployment is started.
-3 Summary
-===========
+Summary
+=======
For Arno, the typical use of Fuel as an OpenStack installer is supplemented with OPNFV unique components such as `OpenDaylight <http://www.opendaylight.org/software>`_ version Helium as well as OPNFV-unique configurations.
- Automated validation of the Arno deployment
-4 Release Data
-================
+Release Data
+============
+--------------------------------------+--------------------------------------+
-| **Project** | Arno/genesis/fuel |
+| **Project** | genesis/bgs |
| | |
+--------------------------------------+--------------------------------------+
-| **Repo/tag** | genesis/arno |
+| **Repo/tag** | genesis/arno_1.0.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Arno |
+| **Release designation** | Arno 1.0.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | 2015-Spring |
+| **Release date** | 2015-06-04 |
+| | |
++--------------------------------------+--------------------------------------+
+| **Purpose of the delivery** | OPNFV Arno release |
| | |
+--------------------------------------+--------------------------------------+
-4.1 Version change
-------------------
+Version change
+--------------
-4.1.1 Module version changes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Module version changes
+~~~~~~~~~~~~~~~~~~~~~~
This is the first tracked release of genesis/fuel. It is based on following upstream versions:
-- Fuel 6.0.1 (Juno release)
+- Fuel 6.0.1
+- OpenStack Juno release
- OpenDaylight Helium-SR2
-4.1.2 Document version changes
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Document version changes
+~~~~~~~~~~~~~~~~~~~~~~~~
This is the first tracked version of genesis/fuel. It comes with the following documentation:
- OPNFV Installation instructions for Arno with Fuel as deployment tool
- OPNFV Build instructions for Arno with Fuel as deployment tool
-4.2 Reason for version
-----------------------
-4.2.1 Feature additions
-~~~~~~~~~~~~~~~~~~~~~~~
+Reason for version
+------------------
+Feature additions
+~~~~~~~~~~~~~~~~~
+--------------------------------------+--------------------------------------+
| **JIRA REFERENCE** | **SLOGAN** |
| | |
+--------------------------------------+--------------------------------------+
-4.2.2 Bug corrections
-~~~~~~~~~~~~~~~~~~~~~
+Bug corrections
+~~~~~~~~~~~~~~~
**JIRA TICKETS:**
| | |
+--------------------------------------+--------------------------------------+
-4.3 Deliverables
-----------------
+Deliverables
+------------
-4.3.1 Software deliverables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Software deliverables
+~~~~~~~~~~~~~~~~~~~~~
Fuel-based installer iso (opnfv.iso) file
-4.3.2 Documentation deliverables
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- OPNFV Installation instructions for Arno release with the Fuel deployment tool - ver. 0.0.1
-- OPNFV Release Note for Arno release with the Fuel deployment tool - ver. 0.1 (this document)
+Documentation deliverables
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+- OPNFV Installation instructions for Arno release with the Fuel deployment tool - ver. 1.0.0
+- OPNFV Release Note for Arno release with the Fuel deployment tool - ver. 1.0.0 (this document)
-5 Known Limitations, Issues and Workarounds
-============================================
+Known Limitations, Issues and Workarounds
+=========================================
-5.1 System Limitations
--------------------------
+System Limitations
+------------------
**Max number of blades:** 1 Fuel master, 3 Controllers, 20 Compute blades
**L3Agent:** L3 agent and floating IPs is not supported.
-5.2 Known issues
--------------------
+Known issues
+------------
**JIRA TICKETS:**
| | |
+--------------------------------------+--------------------------------------+
-5.3 Workarounds
-------------------
+Workarounds
+-----------
**-**
-6 Test Result
-==============
+Test Result
+===========
Arno release with the Fuel deployment tool has undergone QA test runs with the following results:
+--------------------------------------+--------------------------------------+
-7 References
-=============
+References
+==========
For more information on the OPNFV Arno release, please see http://wiki.opnfv.org/releases/arno.
+
+:Authors: Jonas Bjurel (Ericsson)
+:Version: 0.4
+
+**Documentation tracking**
+
+Revision: _sha1_
+
+Build date: _date_
+
Code Review / genesis.git / commitdiff