
For a standalone all-in-one, we need to create a basic role that has some of the services, a network config for a single node and an environment file that has all the services defined but disabled so that we can enable just the services we will need. In the future, we will likely make the service list more dynamic but for now it contains a minimal set of services for a keystone/openshift/kubernetes deployment. Change-Id: Ieb7c94563bd0132393b5fa268d743981f6e0b6f2 Related-Blueprint: all-in-one
Team and repository tags
tripleo-heat-templates
Heat templates to deploy OpenStack using OpenStack.
- Free software: Apache License (2.0)
- Documentation: https://docs.openstack.org/tripleo-docs/latest/
- Source: http://git.openstack.org/cgit/openstack/tripleo-heat-templates
- Bugs: https://bugs.launchpad.net/tripleo
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 | non-ha | ovh-ha |
---|---|---|---|---|---|---|---|---|---|---|
openshift |
|
|||||||||
keystone |
|
|
|
|
|
|
|
|
|
|
glance |
|
swift |
|
|
|
|
|
|
||
cinder |
|
iscsi | ||||||||
heat |
|
|
||||||||
ironic |
|
|||||||||
mysql |
|
|
|
|
|
|
|
|
|
|
neutron |
|
|
|
|
|
|
|
|
||
neutron-bgpvpn |
|
|||||||||
ovn |
|
|||||||||
neutron-l2gw |
|
|||||||||
rabbitmq |
|
|
|
|
|
|
|
|
||
mongodb | ||||||||||
redis |
|
|
||||||||
haproxy |
|
|
|
|
|
|
|
|
||
memcached |
|
|
|
|
|
|
|
|
||
pacemaker |
|
|
|
|
|
|
|
|
||
nova |
|
|
|
|
ironic |
|
|
|
||
ntp |
|
|
|
|
|
|
|
|
|
|
snmp |
|
|
|
|
|
|
|
|
|
|
timezone |
|
|
|
|
|
|
|
|
|
|
sahara |
|
|||||||||
mistral |
|
|||||||||
swift |
|
|||||||||
aodh |
|
|
||||||||
ceilometer |
|
|
||||||||
gnocchi |
|
|
||||||||
panko |
|
|
||||||||
barbican |
|
|||||||||
zaqar |
|
|||||||||
ec2api |
|
|||||||||
cephrgw |
|
|||||||||
tacker |
|
|||||||||
congress |
|
|||||||||
cephmds |
|
|||||||||
manila |
|
|||||||||
collectd |
|
|||||||||
fluentd |
|
|||||||||
sensu-client |
|
|||||||||
designate |
|