Go to file
Jiri Stransky a782462a1a Remove unused minor update code
Since Pike, minor updates are done via the composable services
framework. The old shell script approach hasn't been used/tested for 2
releases now, and should be dropped.

Also drop the UpdateWorkflow interface. Before we started doing
upgrades via Ansible, we used this pluggable resource interface to
perform oneshot operations like migrations to WSGI or AODH
services. Nowadays this interface is not referenced from anywhere and
we'd probably rather do similar operations via Ansible tasks.

Change-Id: I6c5eafe76eb53bc38d100a9ba132dd8fe6dd2d5f
2018-03-15 18:27:14 +01:00
2018-02-09 12:45:19 +00:00
2017-11-23 10:15:32 +01:00
2018-03-15 18:27:14 +01:00
2018-02-08 15:20:17 +08:00
2017-06-12 15:02:50 -05:00
2017-06-12 15:02:50 -05:00
2013-10-22 17:49:35 +01:00
2017-07-07 09:51:40 -06:00
2014-01-20 11:58:20 +01:00
2018-01-08 08:58:40 -08:00
2018-02-08 15:20:17 +08:00
2017-03-28 13:03:01 +00:00
2017-12-13 17:14:36 -06: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

  • roles: example roles that can be used with the tripleoclient to generate

    a roles_data.yaml for a deployment See the roles/README.rst for additional details.

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:

- scn001 scn002 scn003 scn004 scn006 scn007 scn009 non-ha ovh-ha
openshift

X

keystone

X

X

X

X

X

X

X

X

glance

rbd

swift

file

rgw

file

file

file

file

cinder

rbd

iscsi
heat

X

X

ironic

X

mysql

X

X

X

X

X

X

X

X

neutron

ovs

ovs

ovs

ovs

ovs

ovn

ovs

ovs

neutron-bgpvpn

wip

ovn

X

neutron-l2gw

wip

rabbitmq

X

X

X

X

X

X

X

X

mongodb
redis

X

X

haproxy

X

X

X

X

X

X

X

X

memcached

X

X

X

X

X

X

X

X

pacemaker

X

X

X

X

X

X

X

X

nova

qemu

qemu

qemu

qemu

ironic

qemu

qemu

qemu

ntp

X

X

X

X

X

X

X

X

X

snmp

X

X

X

X

X

X

X

X

X

timezone

X

X

X

X

X

X

X

X

X

sahara

X

mistral

X

swift

X

aodh

X

X

ceilometer

X

X

gnocchi

rbd

swift

panko

X

X

barbican

X

zaqar

X

ec2api

X

cephrgw

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