Martin André a17b245049 Do not modify imagestreams
The `openshift_examples_modify_imagestreams` ansible variable controls
whether openshift-ansible changes the imagestream registry hosts to be
the same as where the openshift images are pulled. In our case this
points to the container image registry on the undercloud by default.

However, due to how this feature was implemented in openshift-ansible
[1], the imagestreams are only modified when the original value is
registry.redhat.com, i.e. when deploying openshift-enterprise,
explaining why this issue remained unnoticed until now.

[1] 95bc2d2e61/roles/openshift_examples/tasks/main.yml (L52-L55)

Change-Id: I4949f53e966872f775833b8d36d96ef72cf13845
2018-10-12 16:36:20 +02:00
2018-10-01 13:59:59 -04:00
2018-10-12 16:36:20 +02:00
2018-05-09 08:28:42 +02:00
2018-10-05 10:55:31 -06: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-09-15 18:05:52 +02:00
2017-03-28 13:03:01 +00:00
2018-09-19 05:14:47 +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

  • 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:

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

X

keystone

X

X

X

X

X

X

X

X

X

X

glance

rbd

swift

file

rgw

file

file

rbd

file

file

cinder

rbd

iscsi
heat

X

X

ironic

X

mysql

X

X

X

X

X

X

X

X

X

X

neutron

ovs

ovs

ovs

ovs

ovs

ovn

ovs

ovs

ovs

neutron-bgpvpn

wip

ovn

X

neutron-l2gw

wip

om-rpc rabbit rabbit

amqp1

rabbit rabbit rabbit rabbit rabbit rabbit
om-notify rabbit rabbit rabbit rabbit rabbit rabbit rabbit rabbit rabbit
mongodb
redis

X

X

haproxy

X

X

X

X

X

X

X

X

X

memcached

X

X

X

X

X

X

X

X

X

pacemaker

X

X

X

X

X

X

X

X

X

nova

qemu

qemu

qemu

qemu

ironic

qemu

qemu

qemu

qemu

ntp

X

X

X

X

X

X

X

X

X

X

X

snmp

X

X

X

X

X

X

X

X

X

X

X

timezone

X

X

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

designate

X

octavia

X

Description
RETIRED, Heat templates for deploying OpenStack
Readme 322 MiB