Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Switch to using sphinx-build, fix doc warnings
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Remove install_command from tox.ini, the default is fine
Change-Id: I23a2d62a8853f01e8574ef37b5ee1ac2ee09acd0
Add new Rocky specification for installing OpenStack services using the
distribution packages.
Implements blueprint: openstack-distribution-packages
Change-Id: Id5b991c6982609931a7befb1a2a3e74363a3024c
Added specs to create masakari role that consist of three components:
1) masakari-api
2) masakari-engine
3) masakari-monitor
Change-Id: I40b98c825af59208bb30985fe8a4a4806d0ba76e
We should as much as possible simplify the deploy guide, and
if possible, reduce the amount of duplicate documentation.
I think this spec shows a few areas of improvements we could set
in place to streamline the user experience.
Change-Id: If884c7a56f9bc97a89973ae98840b5783fb88b88
Blazar is the resource reservation project for OpenStack.
This blueprint describe the steps required to make
it available as a service for OpenStack Ansible.
Change-Id: Ibe345ce18b7b4f28886ef5333478e1d3d043ac4a
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
When fully running on bare metal, the current process of
deployment highlights some inefficiencies. This explains the
problem and a proposition on how to fix it.
Change-Id: Ia0ca51f8d18297bd1726429795af648f125d56c5
This blueprint describes the work needed to deploy Openvswitch
with NSH support by using openstack-ansible.
This document covers the installation steps and the
specific configuration which is necessary for the addition of
NSH support to Openvswitch
Several references are provided for further information.
Change-Id: I39760056645d650d19686aef3ce6ee5a6ec4aaf8
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
The current python wheel/venv build process is not easily
understood, and the install process has become complicated.
This aims to work towards making it simpler to deploy,
simpler to understand and to make many of the current
features which are forced on deployers to be opt-in.
Change-Id: Ideee1ba496173590558b29ba6fcac719ba4e162e
In order to improve ease of use, optimise execution and provide
the ability to make use of pre-built artifacts in deployments
this spec proposes the implementation of deployment stages.
Change-Id: Ic7dc8cd3da425f365c1114366983d344a49ae9f1
Congress is the policy framework for OpenStack.
This blueprint describe the steps required to make
it available as a service for OpenStack Ansible.
Change-Id: I9cd0c71ace611e2ebca63dee9f04d77e75e6f0ee
Signed-off-by: Taseer Ahmed <taseer94@gmail.com>
This blueprint describes the work needed to deploy the OpenDaylight
SDN controller as a neutron backend by using openstack-ansible.
The document covers the implications of installing OpenDaylight, its
configuration, and the connection between OpenDaylight and OpenvSwitch.
Several references are provided for further information.
Change-Id: I8b2c85c2a6b06d9a4ddcc568ee80ac2a0800fe7c
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
The specs job hasn't been published in a while and I wondered if
warnings could be causing it. This patch clears up those warnings.
Change-Id: I5e888782d2e62781f44862f2821069fa5b34bec4
This spec proposes the development of monitoring plugins for OpenStack
and system services as well as an opinionated monitoring stack
deployment.
Change-Id: I8c807248f531ead255eda571cba9eea5a29c5ed2
This depends on a spec for storage plugins, but that is only for the
pike sphinx infrastructure parts, not a dependency between the specs
themselves.
Change-Id: Ie5156b577337dc26855cb670f44e6956c0d8356b
This spec is meant to be a high level overview for working towards
pluggable support for storage backends in the current inventory system.
Change-Id: Ie8d6368d264351d9dcc40957a01b3775b14d54eb
James Gibson