else:
cmd = "{} \"{}\" {}".format(driver, driver, ds_cfg)
if driver == 'nova':
- cmd += '--config api_version="2.34"'
+ cmd += ' --config api_version="2.34"'
logging.debug("Congress command created: {}".format(cmd))
cmds.append(cmd)
return cmds
@ln $(RPMUDR) $(BUILD_DIR)/centos/Packages
@ln $(RPMODL) $(BUILD_DIR)/centos/Packages
# add packages to the centos packages
- cd $(BUILD_DIR)/centos/Packages && yumdownloader openvswitch jq python34 python34-libs python34-PyYAML python34-setuptools ipxe-roms-qemu python34-jinja2 python34-markupsafe ansible python34-six python34-cffi python34-idna python34-pycparser python-crypto python-httplib2 python-jinja2 python-keyczar python-paramiko sshpass python-ecdsa python34-ply
+ cd $(BUILD_DIR)/centos/Packages && yumdownloader openvswitch jq python34 python34-libs python34-PyYAML python34-setuptools
+ cd $(BUILD_DIR)/centos/Packages && yumdownloader python34-jinja2 python34-markupsafe ansible python34-six python34-cffi
+ cd $(BUILD_DIR)/centos/Packages && yumdownloader ipxe-roms-qemu python34-idna python34-pycparser python-crypto python-httplib2
+ cd $(BUILD_DIR)/centos/Packages && yumdownloader python-jinja2 python-keyczar python-paramiko sshpass python-ecdsa python34-ply
+ cd $(BUILD_DIR)/centos/Packages && yumdownloader libvirt-python python-lxml
cd $(BUILD_DIR)/centos/Packages && curl -O http://artifacts.opnfv.org/apex/dependencies/python3-ipmi-0.3.0-1.noarch.rpm
cd $(BUILD_DIR)/centos/Packages && curl -O http://artifacts.opnfv.org/apex/dependencies/python34-asn1crypto-0.22.0-1.el7.centos.noarch.rpm
cd $(BUILD_DIR)/centos/Packages && curl -O http://artifacts.opnfv.org/apex/dependencies/python34-cryptography-2.0.3-1.el7.centos.x86_64.rpm
-========================================================================
-OPNFV Release Notes for the Danube release of OPNFV Apex deployment tool
-========================================================================
+===========================================================================
+OPNFV Release Notes for the Euphrates release of OPNFV Apex deployment tool
+===========================================================================
.. contents:: Table of Contents
Abstract
========
-This document provides the release notes for Danube release with the Apex
+This document provides the release notes for Euphrates release with the Apex
deployment toolchain.
License
| **Date** | **Ver.** | **Authors** | **Comment** |
| | | | |
+-------------+-----------+-----------------+----------------------+
+| 2017-08-28 | 5.0 | Tim Rozet | Updates for Euphrates|
++-------------+-----------+-----------------+----------------------+
| 2017-03-30 | 4.0 | Tim Rozet | Updates for Danube |
+-------------+-----------+-----------------+----------------------+
| 2016-09-20 | 2.1.0 | Tim Rozet | More updates for |
Important Notes
===============
-This is the OPNFV Danube release that implements the deploy stage of the
+This is the OPNFV Euphrates release that implements the deploy stage of the
OPNFV CI pipeline via Apex.
Apex is based on RDO's Triple-O installation tool chain.
Summary
=======
-Danube release with the Apex deployment toolchain will establish an OPNFV
+Euphrates release with the Apex deployment toolchain will establish an OPNFV
target system on a Pharos compliant lab infrastructure. The current definition
of an OPNFV target system is OpenStack Newton combined with an SDN
controller, such as OpenDaylight. The system is deployed with OpenStack High
Availability (HA) for most OpenStack services. SDN controllers are deployed
on every controller unless deploying with one the HA FD.IO scenarios. Ceph
storage is used as Cinder backend, and is the only supported storage for
-Danube. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller
+Euphrates. Ceph is setup as 3 OSDs and 3 Monitors, one OSD+Mon per Controller
node in an HA setup. Apex also supports non-HA deployments, which deploys a
single controller and n number of compute nodes. Furthermore, Apex is
capable of deploying scenarios in a bare metal or virtual fashion. Virtual
- Documentation is built by Jenkins
- .iso image is built by Jenkins
- .rpm packages are built by Jenkins
-- Jenkins deploys a Danube release with the Apex deployment toolchain
+- Jenkins deploys a Euphrates release with the Apex deployment toolchain
bare metal, which includes 3 control+network nodes, and 2 compute nodes.
Release Data
| **Project** | apex |
| | |
+--------------------------------------+--------------------------------------+
-| **Repo/tag** | apex/danube.1.0 |
+| **Repo/tag** | apex/euphrates.1.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release designation** | danube.1.0 |
+| **Release designation** | 5.0.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | 2017-03-31 |
+| **Release date** | 2017-09-17 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | OPNFV Danube release |
+| **Purpose of the delivery** | OPNFV Euphrates release |
| | |
+--------------------------------------+--------------------------------------+
Module version changes
~~~~~~~~~~~~~~~~~~~~~~
-This is the first tracked version of the Danube release with the Apex
+This is the first tracked version of the Euphrates release with the Apex
deployment toolchain. It is based on following upstream versions:
- OpenStack (Newton release)
Document Version Changes
~~~~~~~~~~~~~~~~~~~~~~~~
-This is the first tracked version of Danube release with the Apex
+This is the first tracked version of Euphrates release with the Apex
deployment toolchain.
The following documentation is provided with this release:
-- OPNFV Installation instructions for the Danube release with the Apex
+- OPNFV Installation instructions for the Euphrates release with the Apex
deployment toolchain - ver. 1.0.0
-- OPNFV Release Notes for the Danube release with the Apex deployment
+- OPNFV Release Notes for the Euphrates release with the Apex deployment
toolchain - ver. 1.0.0 (this document)
Feature Additions
Documentation Deliverables
~~~~~~~~~~~~~~~~~~~~~~~~~~
-- OPNFV Installation instructions for the Danube release with the Apex
- deployment toolchain - ver. 4.0
-- OPNFV Release Notes for the Danube release with the Apex deployment
- toolchain - ver. 4.0 (this document)
+- OPNFV Installation instructions for the Euphrates release with the Apex
+ deployment toolchain - ver. 5.0
+- OPNFV Release Notes for the Euphrates release with the Apex deployment
+ toolchain - ver. 5.0 (this document)
Known Limitations, Issues and Workarounds
=========================================
References
==========
-For more information on the OPNFV Danube release, please see:
+For more information on the OPNFV Euphrates release, please see:
-http://wiki.opnfv.org/releases/Danube
+http://wiki.opnfv.org/releases/Euphrates
:Authors: Tim Rozet (trozet@redhat.com)
:Authors: Dan Radez (dradez@redhat.com)
-:Version: 4.0
+:Version: 5.0
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with no SDN controller and no extra features enabled.
.. contents::
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with no SDN controller and no extra features enabled.
.. contents::
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with no SDN controller and performance options enabled.
.. contents::
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
-.. _os-odl_l3-nofeature-ha:
+.. _os-odl-csit-noha:
.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-===============================================
-os-odl_l3-nofeature-ha overview and description
-===============================================
+=========================================
+os-odl-csit-noha overview and description
+=========================================
.. toctree::
:numbered:
:maxdepth: 4
- os-odl_l3-nofeature-ha.rst
+ os-odl-csit-noha.rst
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with the OpenDaylight SDN controller and only CSIT relevant
features enabled.
Scenario usage overview
=======================
-Simply deploy this scenario by using the os-odl_l3-csit-noha.yaml deploy
+Simply deploy this scenario by using the os-odl-csit-noha.yaml deploy
settings file.
Limitations, Issues and Workarounds
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
-.. _os-odl_l3-csit-noha:
+.. _os-odl-nofeature-ha:
.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
============================================
-os-odl_l3-csit-noha overview and description
+os-odl-nofeature-ha overview and description
============================================
.. toctree::
:numbered:
:maxdepth: 4
- os-odl_l3-csit-noha.rst
+ os-odl-nofeature-ha.rst
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with the OpenDaylight SDN controller and no extra features enabled.
.. contents::
OpenDaylight is also enabled in HA, and forms a cluster. Neutron
communicates with a Virtual IP Address for OpenDaylight which is load
-balanced acrosss the OpenDaylight cluster. Every Open vSwitch node is
+balanced across the OpenDaylight cluster. Every Open vSwitch node is
connected to every OpenDaylight for High Availability.
Scenario usage overview
=======================
-Simply deploy this scenario by using the os-odl_l3-nofeature-ha.yaml deploy
+Simply deploy this scenario by using the os-odl-nofeature-ha.yaml deploy
settings file.
Limitations, Issues and Workarounds
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
-.. _os-odl_l3-nofeature-noha:
+.. _os-odl-nofeature-noha:
.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-=================================================
-os-odl_l3-nofeature-noha overview and description
-=================================================
+==============================================
+os-odl-nofeature-noha overview and description
+==============================================
.. toctree::
:numbered:
:maxdepth: 4
- os-odl_l3-nofeature-noha.rst
+ os-odl-nofeature-noha.rst
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with the OpenDaylight SDN controller and no extra features enabled.
.. contents::
Scenario usage overview
=======================
-Simply deploy this scenario by using the os-odl_l3-nofeature-noha.yaml deploy
+Simply deploy this scenario by using the os-odl-nofeature-noha.yaml deploy
settings file.
Limitations, Issues and Workarounds
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
.. http://creativecommons.org/licenses/by/4.0
.. (c) <optionally add copywriters name>
-This document provides scenario level details for Danube 1.0 of
+This document provides scenario level details for Euphrates 1.0 of
deployment with the OVN SDN controller and no extra features enabled.
.. contents::
References
==========
-For more information on the OPNFV Danube release, please visit
-http://www.opnfv.org/danube
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
---
- hosts: localhost
tasks:
+ - yum:
+ name: "{{ item }}"
+ state: present
+ with_items:
+ - python-lxml
+ - libvirt-python
- sysctl:
name: net.ipv4.ip_forward
state: present
state: present
with_items: '{{ virsh_enabled_networks }}'
- virt_net:
- command: define
+ state: present
name: '{{ item }}'
xml: '{{ lookup("template", "virsh_network_ovs.xml.j2") }}'
- autostart: yes
with_items: '{{ virsh_enabled_networks }}'
- virt_net:
- command: create
+ state: active
name: '{{ item }}'
+ autostart: yes
with_items: '{{ virsh_enabled_networks }}'
- virt_pool:
name: default
- command: define
autostart: yes
- state: active
+ state: present
xml: '{{ lookup("template", "virsh_pool.xml.j2") }}'
+ - virt_pool:
+ name: default
+ autostart: yes
+ state: active
- lineinfile:
path: /etc/modprobe.d/kvm_intel.conf
line: 'options kvm-intel nested=1'
become_user: stack
when: congress
with_items: "{{ congress_datasources }}"
- ignore_errors: yes
Code Review / apex.git / commitdiff