blob: 72b35793e08b9df36a70e457bd63d8fa91f212fd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
|
heat_template_version: 2014-10-16
description: >
OpenStack controller node post deployment for Puppet.
parameters:
servers:
type: json
resources:
# NOTE(dprince): this example uses a composition class
# on the puppet side (loadbalancer.pp). This seemed like the
# cleanest way to encapulate the puppet resources definitions
# for HAProxy and Keepalived.
ControllerLoadbalancerPuppetConfig:
type: OS::Heat::SoftwareConfig
properties:
group: puppet
options:
enable_hiera: True
enable_facter: False
inputs:
- name: tripleo::loadbalancer::keystone_admin
default: true
- name: tripleo::loadbalancer::keystone_public
default: true
- name: tripleo::loadbalancer::neutron
default: true
- name: tripleo::loadbalancer::cinder
default: true
- name: tripleo::loadbalancer::glance_api
default: true
- name: tripleo::loadbalancer::glance_registry
default: true
- name: tripleo::loadbalancer::nova_ec2
default: true
- name: tripleo::loadbalancer::nova_osapi
default: true
- name: tripleo::loadbalancer::nova_metadata
default: true
- name: tripleo::loadbalancer::nova_novncproxy
default: true
- name: tripleo::loadbalancer::mysql
default: true
- name: tripleo::loadbalancer::rabbitmq
default: true
- name: tripleo::loadbalancer::swift_proxy_server
default: true
- name: tripleo::loadbalancer::ceilometer
default: true
- name: tripleo::loadbalancer::heat_api
default: true
- name: tripleo::loadbalancer::heat_cloudwatch
default: true
- name: tripleo::loadbalancer::heat_cfn
default: true
outputs:
- name: result
config:
get_file: manifests/loadbalancer.pp
ControllerLoadbalancerPuppetDeployment:
type: OS::Heat::SoftwareDeployments
properties:
name: puppet_1
servers: {get_param: servers}
config: {get_resource: ControllerLoadbalancerPuppetConfig}
ControllerPuppetConfig:
type: OS::Heat::SoftwareConfig
properties:
group: puppet
options:
enable_hiera: True
enable_facter: False
inputs:
- name: step
outputs:
- name: result
config:
get_file: manifests/overcloud_controller.pp
# Step through a series of Puppet runs using the same manifest.
# NOTE(dprince): Heat breakpoints would make for a really cool way to step
# through breakpoints in a controlled manner across the entire cluster
ControllerPuppetDeploymentServicesBase:
type: OS::Heat::StructuredDeployments
properties:
name: puppet_2
servers: {get_param: servers}
config: {get_resource: ControllerPuppetConfig}
input_values:
step: 1
actions: ['CREATE'] # no need for two passes on an UPDATE
ControllerRingbuilderPuppetConfig:
type: OS::Heat::SoftwareConfig
properties:
group: puppet
options:
enable_hiera: True
enable_facter: False
inputs:
outputs:
- name: result
config:
get_file: manifests/ringbuilder.pp
ControllerRingbuilderPuppetDeployment:
type: OS::Heat::StructuredDeployments
properties:
name: puppet_3
servers: {get_param: servers}
config: {get_resource: ControllerRingbuilderPuppetConfig}
ControllerPuppetDeploymentOvercloudServices:
type: OS::Heat::StructuredDeployments
properties:
name: puppet_4
servers: {get_param: servers}
config: {get_resource: ControllerPuppetConfig}
input_values:
step: 2
|
