tripleo-heat-templates/README.rst
Carlos Camacho 4b4425dfb5 Add BGPVPN services to scenario004
This submission will enable the BGPVPN API
on scenario004.

This addition to scenario004 does not
provide any sanity check for the Neutron API
extension. At this stage is meant to
install the required packages and prerequisites,
configure the extension and
having the services started correctly.

In the README.rst file, this is displayed as
neutron-bgpvpn, so for further integrations
should be added as neutron-<extension_name>
for an easier reading.

Depends-On: I4d0617b0d7801426ea6827e70f5f31f10bbcc038
Depends-On: I2be0fab671ec1a804d029afc6dc27d19a193b064
Change-Id: I6c257417a9231c44e13535bc408d67d2a3cacbf8
2017-04-07 11:03:50 +02:00

8.8 KiB

Team and repository tags

image

tripleo-heat-templates

Heat templates to deploy OpenStack using OpenStack.

Features

The ability to deploy a multi-node, role based OpenStack deployment using OpenStack Heat. Notable features include:

  • Choice of deployment/configuration tooling: puppet, (soon) docker
  • Role based deployment: roles for the controller, compute, ceph, swift, and cinder storage
  • physical network configuration: support for isolated networks, bonding, and standard ctlplane networking

Directories

A description of the directory layout in TripleO Heat Templates.

  • environments: contains heat environment files that can be used with -e

    on the command like to enable features, etc.

  • extraconfig: templates used to enable 'extra' functionality. Includes

    functionality for distro specific registration and upgrades.

  • firstboot: example first_boot scripts that can be used when initially

    creating instances.

  • network: heat templates to help create isolated networks and ports
  • puppet: templates mostly driven by configuration with puppet. To use these

    templates you can use the overcloud-resource-registry-puppet.yaml.

  • validation-scripts: validation scripts useful to all deployment

    configurations

Service testing matrix

The configuration for the CI scenarios will be defined in tripleo-heat-templates/ci/ and should be executed according to the following table:

- scenario001 scenario002 scenario003 scenario004 multinode-nonha
keystone

X

X

X

X

X

glance

rbd

swift

file

swift + rbd

swift

cinder

rbd

iscsi

iscsi

heat

X

X

X

X

X

mysql

X

X

X

X

X

neutron

ovs

ovs

ovs

ovs

X

neutron-bgpvpn

X

rabbitmq

X

X

X

X

X

mongodb

X

X

redis

X

haproxy

X

X

X

X

X

keepalived

X

X

X

X

X

memcached

X

X

X

X

X

pacemaker

X

X

X

X

X

nova

qemu

qemu

qemu

qemu

X

ntp

X

X

X

X

X

snmp

X

X

X

X

X

timezone

X

X

X

X

X

sahara

X

mistral

X

swift

X

X

aodh

X

ceilometer

X

gnocchi

X

panko

X

barbican

X

zaqar

X

ec2api

X

cephrgw

X

X

tacker

X

congress

X

cephmds

X

manila

X

collectd

X

fluentd

X

sensu-client

X