Alex Schultz be274f1f49 Add tags to roles
Prior to Ocata, the Controller role was hardcoded for various lookups.
When we switched to having the primary role name being dynamically
pulled from the roles_data.yaml using the first role as the primary
role as part of I36df7fa86c2ff40026d59f02248af529a4a81861, it
introduced a regression for folks who had previously been using
a custom roles file without the Controller being listed first.

Instead of relying on the position of the role in the roles data, this
change adds the concepts of tags to the role data that can be used when
looking for specific functionality within the deployment process. If
no roles are specified with this the tags indicating a 'primary'
'controller', it will fall back to using  the first role listed in the
roles data as the primary role.

Change-Id: Id3377e7d7dcc88ba9a61ca9ef1fb669949714f65
Closes-Bug: #1677374
2017-04-12 06:55:29 -06:00
2017-04-07 11:03:50 +02:00
2017-04-12 06:55:29 -06:00
2017-04-12 06:55:29 -06:00
2017-02-14 17:39:35 +00:00
2017-01-13 14:35:27 -05:00
2017-02-14 17:39:35 +00:00
2013-10-22 17:49:35 +01:00
2017-03-13 12:11:46 -04:00
2014-01-20 11:58:20 +01:00
2013-10-22 17:49:35 +01:00
2017-04-12 06:55:29 -06:00
2017-04-07 11:03:50 +02:00
2017-04-12 06:55:29 -06:00
2017-04-12 06:55:29 -06:00
2017-03-28 13:03:01 +00:00

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

Description
RETIRED, Heat templates for deploying OpenStack
Readme 322 MiB