James Slagle 62a84e777b Use custom role names in deployed-server roles
Custom role names need to be used in the deployed server role files,
otherwise the new customized roles are not generated by jinja since the
default roles are excluded from templating in j2_excludes.yaml.

This patch also removes the OS::TripleO::Services::Core service that was
recently removed from the default Controller role as well in
I48cd2b6a4593d673d5883b45feae088392e7e713

Partially-implements: blueprint split-stack-software-configuration
Change-Id: I60cb60382d472cd093f07e134245f666029f3b16
2017-01-16 10:48:00 -05:00
2017-01-13 14:35:27 -05:00
2017-01-13 14:35:27 -05:00
2016-05-09 20:22:52 -04:00
2017-01-13 14:35:27 -05:00
2013-10-22 17:49:35 +01:00
2014-01-20 11:58:20 +01:00
2013-10-22 17:49:35 +01:00
2017-01-09 15:23:22 -05:00
2017-01-10 09:44:01 +00:00
2017-01-13 14:35:27 -05: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

file

swift

file

file

swift

cinder

rbd

iscsi

iscsi

heat

X

X

X

X

X

mysql

X

X

X

X

X

neutron

ovs

ovs

ovs

ovs

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

cephrgw

X

X

Description
RETIRED, Heat templates for deploying OpenStack
Readme 322 MiB