Emilien Macchi d24874c7b2 Disable systemd-networkd & systemd-resolved
Latest commits in puppet-systemd enabled by default systemd-networkd and
systemd-resolved but we don't want to manage them for now in TripleO.
MySQL and MongoDB services were managing some systemd resources so now
we ensure that these 2 systemd services are disabled. In the future, we
might want and activate these services and revert that patch but for now
we want to disable them.

Change-Id: I42c6c9b643a71a0fbb1768bbae91e8bfa916ea00
Closes-Bug: #1704145
2017-07-14 04:10:55 +00:00
2017-07-07 09:51:40 -06: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
2013-10-22 17:49:35 +01:00
2017-07-07 09:51:40 -06:00
2017-07-07 09:51:40 -06:00
2017-03-28 13:03:01 +00:00
2017-07-07 09:51:40 -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:

- 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

neutron-l2gw

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