From: Jonas Bjurel Date: Mon, 29 Aug 2016 12:49:02 +0000 (+0000) Subject: Merge "deploy.sh: accept a timeout flag (-T)" X-Git-Tag: danube.1.RC1~161 X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=commitdiff_plain;h=a0f0fb312899a44e80ec0339a44497b6e1c94bff;hp=bb2a6188ff55e61390841694cac786d4e758d67b;p=fuel.git Merge "deploy.sh: accept a timeout flag (-T)" --- diff --git a/build/Makefile b/build/Makefile index c4775a3da..b3905e364 100644 --- a/build/Makefile +++ b/build/Makefile @@ -57,7 +57,7 @@ export MIRROR_UBUNTU_ROOT := $(shell echo -n '/' ; echo "$(MIRROR_UBUNTU_URL)" | export LATEST_MIRROR_ID_URL := http://$(shell ./select_closest_fuel_mirror.py) -export MIRROR_MOS_UBUNTU := $(shell echo "$(LATEST_MIRROR_ID_URL)" | cut -d'/' -f3) +export MIRROR_MOS_UBUNTU ?= $(shell echo "$(LATEST_MIRROR_ID_URL)" | cut -d'/' -f3) export LATEST_TARGET_UBUNTU := $(shell curl -sSf "$(MIRROR_MOS_UBUNTU)/mos-repos/ubuntu/$(MOSVERSION).target.txt" | head -1) export MIRROR_MOS_UBUNTU_ROOT := /mos-repos/ubuntu/$(LATEST_TARGET_UBUNTU) diff --git a/build/f_isoroot/Makefile b/build/f_isoroot/Makefile index 4df7bcb0c..448f4158c 100644 --- a/build/f_isoroot/Makefile +++ b/build/f_isoroot/Makefile @@ -11,7 +11,7 @@ # Add Fuel plugin build targets here # Plugins disabled for the Fuel Mitaka uplift. Please re-enable your plugin as you have # verified it! -PLUGINS = f_odlpluginbuild f_onosfwpluginbuild f_vsperfpluginbuild f_ovs-nsh-dpdk-pluginbuild f_yardstick-pluginbuild f_kvm-pluginbuild f_bgpvpn-pluginbuild f_collectd-ceilometer-pluginbuild +PLUGINS ?= f_odlpluginbuild f_onosfwpluginbuild f_vsperfpluginbuild f_ovs-nsh-dpdk-pluginbuild f_yardstick-pluginbuild f_kvm-pluginbuild f_bgpvpn-pluginbuild f_collectd-ceilometer-pluginbuild #PLUGINS = f_odlpluginbuild f_onosfwpluginbuild f_ovsnfv-dpdk-pluginbuild f_vsperfpluginbuild f_ovs-nsh-dpdk-pluginbuild f_bgpvpn-pluginbuild export PLUGINS #NON_8-0_REBASED_PLUGINS = f_bgpvpn-pluginbuild diff --git a/build/f_isoroot/f_odlpluginbuild/config.mk b/build/f_isoroot/f_odlpluginbuild/config.mk index d600e54ef..48e7f78fd 100644 --- a/build/f_isoroot/f_odlpluginbuild/config.mk +++ b/build/f_isoroot/f_odlpluginbuild/config.mk @@ -8,7 +8,7 @@ ############################################################################## FUEL_PLUGIN_ODL_BRANCH ?= master -FUEL_PLUGIN_ODL_CHANGE ?= 8cc22c4717d2da338135d854e1d13aac3ef75314 +FUEL_PLUGIN_ODL_CHANGE ?= 0ff4ebdbfe5f681f0b44eea14c9c2b3dbb10b1d5 FUEL_PLUGIN_ODL_REPO ?= https://github.com/openstack/fuel-plugin-opendaylight.git export ODL_TARBALL_LOCATION?=https://nexus.opendaylight.org/content/repositories/public/org/opendaylight/integration/distribution-karaf/0.4.3-Beryllium-SR3/distribution-karaf-0.4.3-Beryllium-SR3.tar.gz diff --git a/ci/build.sh b/ci/build.sh index 62abba173..82049cdcd 100755 --- a/ci/build.sh +++ b/ci/build.sh @@ -111,7 +111,7 @@ SCRIPT_DIR=$(readlink -f $(dirname ${BASH_SOURCE[0]})) BUILD_BASE=$(readlink -e ${SCRIPT_DIR}/../build/) RESULT_DIR="${BUILD_BASE}/release" BUILD_SPEC="${BUILD_BASE}/config.mk" -LOCAL_CACHE_ARCH_NAME="fuel-cache" +LOCAL_CACHE_ARCH_NAME="${LOCAL_CACHE_ARCH_NAME:-fuel-cache}" # # END of variables to customize diff --git a/docs/buildprocedure/build.instruction.rst b/docs/buildprocedure/build.instruction.rst index 7e381500b..dd7aab51a 100644 --- a/docs/buildprocedure/build.instruction.rst +++ b/docs/buildprocedure/build.instruction.rst @@ -308,8 +308,8 @@ The artifacts produced are: References ========== -1) `OPNFV Installation instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_ +1) `OPNFV Installation instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/installationprocedure/index.html -2) `OPNFV Build instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_ +2) `OPNFV Build instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/buildprocedure/index.html -3) `OPNFV Release Note for the Colorado release of OPNFV when using Fuel as a deployment tool `_ +3) `OPNFV Release Note for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/releasenotes/index.html diff --git a/docs/buildprocedure/index.rst b/docs/buildprocedure/index.rst index 99dc3ab27..d2a7512af 100644 --- a/docs/buildprocedure/index.rst +++ b/docs/buildprocedure/index.rst @@ -4,9 +4,9 @@ .. You should have received a copy of the license along with this work. .. If not, see . -***************************** -Fuel@OPNFV build instructions -***************************** +****************************** +Fuel\@OPNFV build instructions +****************************** .. toctree:: :numbered: diff --git a/docs/installationprocedure/img/addnodes.png b/docs/installationprocedure/img/addnodes.png index 15730db90..b62405692 100644 Binary files a/docs/installationprocedure/img/addnodes.png and b/docs/installationprocedure/img/addnodes.png differ diff --git a/docs/installationprocedure/img/compute.png b/docs/installationprocedure/img/compute.png index fd7811f37..fc1cf0f22 100644 Binary files a/docs/installationprocedure/img/compute.png and b/docs/installationprocedure/img/compute.png differ diff --git a/docs/installationprocedure/img/computelist.png b/docs/installationprocedure/img/computelist.png index a4453d958..474196536 100644 Binary files a/docs/installationprocedure/img/computelist.png and b/docs/installationprocedure/img/computelist.png differ diff --git a/docs/installationprocedure/img/fuelmenu1.png b/docs/installationprocedure/img/fuelmenu1.png index 15fccc434..ee7a0edb2 100644 Binary files a/docs/installationprocedure/img/fuelmenu1.png and b/docs/installationprocedure/img/fuelmenu1.png differ diff --git a/docs/installationprocedure/img/fuelmenu2.png b/docs/installationprocedure/img/fuelmenu2.png index 1f87c53e5..4dcbb6e68 100644 Binary files a/docs/installationprocedure/img/fuelmenu2.png and b/docs/installationprocedure/img/fuelmenu2.png differ diff --git a/docs/installationprocedure/img/fuelmenu3.png b/docs/installationprocedure/img/fuelmenu3.png index c9fa27959..23e61975b 100644 Binary files a/docs/installationprocedure/img/fuelmenu3.png and b/docs/installationprocedure/img/fuelmenu3.png differ diff --git a/docs/installationprocedure/img/fuelmenu4.png b/docs/installationprocedure/img/fuelmenu4.png index 1bc9c0410..3be29cd66 100644 Binary files a/docs/installationprocedure/img/fuelmenu4.png and b/docs/installationprocedure/img/fuelmenu4.png differ diff --git a/docs/installationprocedure/img/fuelmenu5.png b/docs/installationprocedure/img/fuelmenu5.png index 11247986b..e3d215459 100644 Binary files a/docs/installationprocedure/img/fuelmenu5.png and b/docs/installationprocedure/img/fuelmenu5.png differ diff --git a/docs/installationprocedure/img/fuelmenu6.png b/docs/installationprocedure/img/fuelmenu6.png index 9ff62c798..cafbcddfc 100644 Binary files a/docs/installationprocedure/img/fuelmenu6.png and b/docs/installationprocedure/img/fuelmenu6.png differ diff --git a/docs/installationprocedure/img/grub-1.png b/docs/installationprocedure/img/grub-1.png index 7488503af..e64b79373 100644 Binary files a/docs/installationprocedure/img/grub-1.png and b/docs/installationprocedure/img/grub-1.png differ diff --git a/docs/installationprocedure/img/health.png b/docs/installationprocedure/img/health.png index 71675069e..57bd8cf70 100644 Binary files a/docs/installationprocedure/img/health.png and b/docs/installationprocedure/img/health.png differ diff --git a/docs/installationprocedure/img/interfaceconf.png b/docs/installationprocedure/img/interfaceconf.png index e8b45578c..e00b03f03 100644 Binary files a/docs/installationprocedure/img/interfaceconf.png and b/docs/installationprocedure/img/interfaceconf.png differ diff --git a/docs/installationprocedure/img/network.png b/docs/installationprocedure/img/network.png index 04c67d38e..7bef05064 100644 Binary files a/docs/installationprocedure/img/network.png and b/docs/installationprocedure/img/network.png differ diff --git a/docs/installationprocedure/img/neutronl3.png b/docs/installationprocedure/img/neutronl3.png index dd8d7954b..36291ef87 100644 Binary files a/docs/installationprocedure/img/neutronl3.png and b/docs/installationprocedure/img/neutronl3.png differ diff --git a/docs/installationprocedure/img/other.png b/docs/installationprocedure/img/other.png index 4e740eb06..c088488dc 100644 Binary files a/docs/installationprocedure/img/other.png and b/docs/installationprocedure/img/other.png differ diff --git a/docs/installationprocedure/img/plugins.png b/docs/installationprocedure/img/plugins.png index bfe8781e8..8f7ea596f 100644 Binary files a/docs/installationprocedure/img/plugins.png and b/docs/installationprocedure/img/plugins.png differ diff --git a/docs/installationprocedure/img/verifynet.png b/docs/installationprocedure/img/verifynet.png index 5932bc223..e675562c0 100644 Binary files a/docs/installationprocedure/img/verifynet.png and b/docs/installationprocedure/img/verifynet.png differ diff --git a/docs/installationprocedure/index.rst b/docs/installationprocedure/index.rst index 0dd7a881b..171647188 100644 --- a/docs/installationprocedure/index.rst +++ b/docs/installationprocedure/index.rst @@ -4,9 +4,9 @@ .. You should have received a copy of the license along with this work. .. If not, see . -*********************************** -Fuel@OPNFV Installation Instruction -*********************************** +************************************ +Fuel\@OPNFV Installation Instruction +************************************ .. toctree:: :numbered: diff --git a/docs/installationprocedure/installation.instruction.rst b/docs/installationprocedure/installation.instruction.rst index fea90af0d..bb56a53cf 100644 --- a/docs/installationprocedure/installation.instruction.rst +++ b/docs/installationprocedure/installation.instruction.rst @@ -13,7 +13,7 @@ Abstract ======== This document describes how to install the Colorado release of -OPNFV when using Fuel as a deployment tool, covering it's usage, +OPNFV when using Fuel as a deployment tool, covering it's usage, limitations, dependencies and required system resources. Introduction @@ -35,6 +35,7 @@ networking and Unix/Linux administration. Preface ======= + Before starting the installation of the Colorado release of OPNFV, using Fuel as a deployment tool, some planning must be done. @@ -49,7 +50,8 @@ Building the ISO image ---------------------- Alternatively, you may build the Fuel .iso from source by cloning the -opnfv/fuel git repository. To retrieve the repository for the Colorado release use the following command: +opnfv/fuel git repository. To retrieve the repository for the Colorado +release use the following command: .. code-block:: bash @@ -97,7 +99,7 @@ Prior to installation, a number of deployment specific parameters must be collec #. How many nodes and what roles you want to deploy (Controllers, Storage, Computes) -#. Monitoring options you want to deploy (Ceilometer, Syslog, erc.). +#. Monitoring options you want to deploy (Ceilometer, Syslog, etc.). #. Other options not covered in the document are available in the links above @@ -207,7 +209,7 @@ Install Fuel master .. figure:: img/grub-1.png -#. Wait until screen Fuel setup is shown (Note: This can take up to 30 minutes). +#. Wait until the Fuel setup screen is shown (Note: This can take up to 30 minutes). #. In the "Fuel User" section - Confirm/change the default password (See figure below) @@ -274,7 +276,7 @@ Install Fuel master - Select Quit Setup and press Save and Quit. - - Installation starts, wait until the login screen is shown. + - The installation will now start, wait until the login screen is shown. Boot the Node Servers @@ -282,12 +284,12 @@ Boot the Node Servers After the Fuel Master node has rebooted from the above steps and is at the login prompt, you should boot the Node Servers (Your -Compute/Control/Storage blades (nested or real) with a PXE booting +Compute/Control/Storage blades, nested or real) with a PXE booting scheme so that the FUEL Master can pick them up for control. #. 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. + - 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. #. Reboot all the control and compute blades. @@ -324,7 +326,7 @@ Install additional Plugins/Features on the FUEL node Create an OpenStack Environment ------------------------------- -#. Connect to Fuel WEB UI with a browser (default: https://10.20.0.2:8443) (login admin/admin) +#. Connect to Fuel WEB UI with a browser (default: https://10.20.0.2:8443) (login: admin/admin) #. Create and name a new OpenStack environment, to be installed. @@ -350,7 +352,7 @@ Create an OpenStack Environment #. Select "additional services" you wish to install. - - Check option "Install Ceilometer (OpenStack Telemetry)" and press + - Check option "Install Ceilometer and Aodh" and press #. Create the new environment. @@ -361,7 +363,7 @@ Configure the network environment #. Open the environment you previously created. -#. Open the networks tab and select the "default Node Networks group to" on the left pane (see figure below). +#. Open the networks tab and select the "default" Node Networks group to on the left pane (see figure below). .. figure:: img/network.png @@ -413,7 +415,7 @@ Configure the network environment - Set appropriate VLAN tag (default 103) -#. Select the "Neutron L3 Node Networks group" on the left pane. +#. Select the "Neutron L3" Node Networks group on the left pane. .. figure:: img/neutronl3.png @@ -439,7 +441,7 @@ Configure the network environment #. Save Settings. -#. Select the "Other Node Networks group" on the left pane(see figure below). +#. Select the "Other" Node Networks group on the left pane (see figure below). .. figure:: img/other.png @@ -460,7 +462,7 @@ Select Hypervisor type #. In the FUEL UI of your Environment, click the "Settings" Tab -#. Select Compute on the left side pane (see figure below) +#. Select "Compute" on the left side pane (see figure below) - Check the KVM box and press "Save settings" @@ -488,7 +490,7 @@ Allocate nodes to environment and assign functional roles - Click on the <+Add Nodes> button - - Check , and optionally an SDN Controller role (OpenDaylight controller/ONOS) in the Assign Roles Section. + - Check , and optionally an SDN Controller role (OpenDaylight controller/ONOS) in the "Assign Roles" Section. - Check one node which you want to act as a Controller from the bottom half of the screen @@ -518,8 +520,7 @@ Allocate nodes to environment and assign functional roles - Click - - Assign interfaces (bonded) for mgmt-, admin-, private-, public- - and storage networks + - Assign interfaces (bonded) for mgmt-, admin-, private-, public- and storage networks - Click @@ -529,7 +530,7 @@ Allocate nodes to environment and assign functional roles OPTIONAL - Set Local Mirror Repos --------------------------------- -The following steps can be executed if you are in an environment with +The following steps must 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. @@ -543,7 +544,7 @@ that can be used for installation / deployment of openstack. - "ubuntu-updates" URI="deb http://:8080/mirrors/ubuntu/ trusty-updates main" - - "mos" URI="deb http://::8080/mitaka-9.0/ubuntu/x86_64 mos8.0 main restricted" + - "mos" URI="deb http://::8080/mitaka-9.0/ubuntu/x86_64 mos9.0 main restricted" - "Auxiliary" URI="deb http://:8080/mitaka-9.0/ubuntu/auxiliary auxiliary main restricted" @@ -617,7 +618,7 @@ packages needed for a successful deployment can be fetched. Deploy Your Environment ----------------------- -38. Deploy the environment. +#. Deploy the environment. - In the Fuel GUI, click on the "Dashboard" Tab. @@ -647,43 +648,43 @@ References OPNFV ----- -1) `OPNFV Home Page `_ +1) `OPNFV Home Page `_: http://www.opnfv.org -2) `OPNFV documentation- and software downloads `_ +2) `OPNFV documentation- and software downloads `_: https://www.opnfv.org/software/download OpenStack --------- -3) `OpenStack Mitaka Release artifacts `_ +3) `OpenStack Mitaka Release artifacts `_: http://www.openstack.org/software/mitaka -4) `OpenStack documentation `_ +4) `OpenStack documentation `_: http://docs.openstack.org OpenDaylight ------------ -5) `OpenDaylight artifacts `_ +5) `OpenDaylight artifacts `_: http://www.opendaylight.org/software/downloads Fuel ---- -6) `The Fuel OpenStack project `_ +6) `The Fuel OpenStack project `_: https://wiki.openstack.org/wiki/Fuel -7) `Fuel documentation overview `_ +7) `Fuel documentation overview `_: http://docs.openstack.org/developer/fuel-docs -8) `Fuel Installation Guide `_ +8) `Fuel Installation Guide `_: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html -9) `Fuel User Guide `_ +9) `Fuel User Guide `_: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html -10) `Fuel Developer Guide `_ +10) `Fuel Developer Guide `_: http://docs.openstack.org/developer/fuel-docs/devdocs/develop.html -11) `Fuel Plugin Developers Guide `_ +11) `Fuel Plugin Developers Guide `_: http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html -12) `Fuel OpenStack Hardware Compatibility List `_ +12) `Fuel OpenStack Hardware Compatibility List `_: https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list Fuel in OPNFV ------------- -13) `OPNFV Installation instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_ +13) `OPNFV Installation instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/installationprocedure/index.html -14) `OPNFV Build instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_ +14) `OPNFV Build instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/buildprocedure/index.html -15) `OPNFV Release Note for the Colorado release of OPNFV when using Fuel as a deployment tool `_ +15) `OPNFV Release Note for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/releasenotes/index.html diff --git a/docs/releasenotes/index.rst b/docs/releasenotes/index.rst index edce08908..8fb1fef78 100644 --- a/docs/releasenotes/index.rst +++ b/docs/releasenotes/index.rst @@ -4,9 +4,9 @@ .. You should have received a copy of the license along with this work. .. If not, see . -************************ -Fuel@OPNFV release notes -************************ +************************* +Fuel\@OPNFV release notes +************************* .. toctree:: :numbered: diff --git a/prototypes/sfc_tacker/poc.tacker-up.sh b/prototypes/sfc_tacker/poc.tacker-up.sh index fc45c7643..caad3f86a 100755 --- a/prototypes/sfc_tacker/poc.tacker-up.sh +++ b/prototypes/sfc_tacker/poc.tacker-up.sh @@ -58,6 +58,7 @@ ____EOF # Function setting up the build/deploy environment function envSetup () { + apt-key adv --keyserver keyserver.ubuntu.com --recv-keys BCE5CC461FA22B08 apt-get update apt-get install -y git python-pip python-all debhelper chkPPkg stdeb @@ -136,13 +137,13 @@ function blessPackage () { dpkg-deb --control "$DEBFILE" "${TMPDIR}/DEBIAN" cd "$TMPDIR" patch -p 1 < - Installed-Size: 1565 + Installed-Size: 1566 -Depends: python (>= 2.7), python (<< 2.8), python:any (>= 2.7.1-0ubuntu2), python-pbr, python-paste, python-pastedeploy, python-routes, python-anyjson, python-babel, python-eventlet, python-greenlet, python-httplib2, python-requests, python-iso8601, python-jsonrpclib, python-jinja2, python-kombu, python-netaddr, python-sqlalchemy (>= 1.0~), python-sqlalchemy (<< 1.1), python-webob, python-heatclient, python-keystoneclient, alembic, python-six, python-stevedore, python-oslo.config, python-oslo.messaging-, python-oslo.rootwrap, python-novaclient +Depends: python (>= 2.7), python (<< 2.8), python:any (>= 2.7.1-0ubuntu2), python-pbr, python-paste, python-pastedeploy, python-routes, python-anyjson, python-babel, python-eventlet, python-greenlet, python-httplib2, python-requests, python-iso8601, python-jsonrpclib, python-jinja2, python-kombu, python-netaddr, python-sqlalchemy (>= 1.0~), python-sqlalchemy (<< 1.1), python-webob, python-heatclient, python-keystoneclient, alembic, python-six, python-stevedore, python-oslo.config, python-oslo.messaging, python-oslo.rootwrap, python-novaclient Section: python @@ -250,7 +251,7 @@ function populate_client() { } # Function orchestrate the Tacker service -function orchestarte () { +function orchestrate () { rm -rf /etc/puppet/modules/tacker pushd /etc/puppet/modules git clone https://github.com/trozet/puppet-tacker.git tacker @@ -266,6 +267,7 @@ function orchestarte () { auth_uri=$(crudini --get '/etc/heat/heat.conf' 'keystone_authtoken' 'auth_uri') identity_uri=$(crudini --get '/etc/heat/heat.conf' 'keystone_authtoken' 'identity_uri') int_addr=$(ifconfig br-mesh | sed -n '/inet addr/s/.*addr.\([^ ]*\) .*/\1/p') + odl_addr=$(hiera management_vip) mgmt_addr=$(ifconfig br-mgmt | sed -n '/inet addr/s/.*addr.\([^ ]*\) .*/\1/p') pub_addr=$(ifconfig br-ex-lnx | sed -n '/inet addr/s/.*addr.\([^ ]*\) .*/\1/p') rabbit_host=$(crudini --get '/etc/heat/heat.conf' 'oslo_messaging_rabbit' 'rabbit_hosts'| cut -d ':' -f 1) @@ -301,7 +303,7 @@ function orchestarte () { rabbit_host => '${rabbit_host}', rabbit_password => '${rabbit_password}', heat_uri => '${heat_uri}', - opendaylight_host => '${mgmt_addr}', + opendaylight_host => '${odl_addr}', opendaylight_port => '${odl_port}', } @@ -360,6 +362,7 @@ function populate_rc() { done } + envSetup deployTackerClient deployJsonrpclib @@ -367,9 +370,11 @@ buildTackerServer blessPackage deployTackerServer populate_client -orchestarte +orchestrate populate_rc +git clone https://github.com/trozet/sfc-random.git + remove_repo "$MYREPO" remove_repo "$DEPREPO" remove_repo "$CLIREPO"