forked from cloudify-cosmo/cloudify-nodecellar-example
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathaws-ec2-blueprint.yaml
228 lines (192 loc) · 7.46 KB
/
aws-ec2-blueprint.yaml
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
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
###########################################################
# This Blueprint installs the nodecellar application
# on an amazon ec2 cloud environment.
###########################################################
tosca_definitions_version: cloudify_dsl_1_1
imports:
- http://www.getcloudify.org/spec/cloudify/3.3m3/types.yaml
- http://www.getcloudify.org/spec/aws-plugin/1.3m3/plugin.yaml
- http://www.getcloudify.org/spec/diamond-plugin/1.3m3/plugin.yaml
- types/nodecellar.yaml
#####################################################################################
# inputs section allows the user to use same
# blueprint for creating different deployments, each one
# with its own parameters.
# to specify deployment inputs run:
# - cfy deployments create -b <blueprint_id> -d <deployment_id> -i inputs.json
#####################################################################################
inputs:
image:
description: >
Image to be used when launching agent VM's
size:
description: >
Flavor of the agent VM's
agent_user:
description: >
User for connecting to agent VM's
node_types:
###########################################################
# We define a type that inherits ec2's default
# server, and adds monitoring capabillities on top of it.
###########################################################
nodecellar.nodes.MonitoredServer:
derived_from: cloudify.aws.nodes.Instance
properties:
cloudify_agent:
default:
user: { get_input: agent_user }
interfaces:
###########################################################
# We are infact telling cloudify to install a diamond
# monitoring agent on the server.
#
# (see https://github.com/BrightcoveOS/Diamond)
###########################################################
cloudify.interfaces.monitoring_agent:
install:
implementation: diamond.diamond_agent.tasks.install
inputs:
diamond_config:
default:
interval: 1
start: diamond.diamond_agent.tasks.start
stop: diamond.diamond_agent.tasks.stop
uninstall: diamond.diamond_agent.tasks.uninstall
###########################################################
# Adding some collectors. These collectors are necessary
# for the Cloudify UI to display the deafult metrics.
###########################################################
cloudify.interfaces.monitoring:
start:
implementation: diamond.diamond_agent.tasks.add_collectors
inputs:
collectors_config:
default:
CPUCollector: {}
MemoryCollector: {}
LoadAverageCollector: {}
DiskUsageCollector:
config:
devices: x?vd[a-z]+[0-9]*$
NetworkCollector: {}
node_templates:
mongod_host:
type: nodecellar.nodes.MonitoredServer
properties:
image_id: { get_input: image }
instance_type: { get_input: size }
relationships:
- type: cloudify.aws.relationships.instance_connected_to_security_group
target: mongod_security_group
nodejs_host:
type: nodecellar.nodes.MonitoredServer
properties:
image_id: { get_input: image }
instance_type: { get_input: size }
relationships:
- type: cloudify.aws.relationships.instance_connected_to_security_group
target: nodecellar_security_group
- type: cloudify.aws.relationships.instance_connected_to_elastic_ip
target: nodecellar_elasticip
mongod:
type: nodecellar.nodes.MongoDatabase
properties:
port: 27017
interfaces:
cloudify.interfaces.lifecycle:
###########################################################
# The MongoDBCollector depends on a python library called
# pymongo. We install this library in the 'configure'
# lifecycle hook of this node.
###########################################################
configure: scripts/mongo/install-pymongo.sh
###########################################################
# Notice that this node defines an additional collector
# to collect data on the MongoDB.
###########################################################
cloudify.interfaces.monitoring:
start:
implementation: diamond.diamond_agent.tasks.add_collectors
inputs:
collectors_config:
MongoDBCollector:
config:
hosts: "localhost:27017"
relationships:
- type: cloudify.relationships.contained_in
target: mongod_host
nodejs:
type: nodecellar.nodes.NodeJSServer
relationships:
- type: cloudify.relationships.contained_in
target: nodejs_host
nodecellar:
type: nodecellar.nodes.NodecellarApplicationModule
properties:
port: 8080
relationships:
################################
# Setting the mongo connection
################################
- type: node_connected_to_mongo
target: mongod
################################
# Setting the nodejs connection
################################
- type: node_contained_in_nodejs
target: nodejs
###########################################################
# A security group to enable access to the nodejs host
# using the port of the nodecellar application.
#
# This security group will be attached to the nodejs_host
###########################################################
nodecellar_security_group:
type: cloudify.aws.nodes.SecurityGroup
properties:
description: Security Group for Nodecellar VMs
rules:
- ip_protocol: tcp
from_port: { get_property: [ nodecellar, port ] }
to_port: { get_property: [ nodecellar, port ] }
cidr_ip: 0.0.0.0/0
###########################################################
# A security group to enable access to the mongo host
# using the port of the mongo node.
#
# We need this so that the nodecellar application can
# comminicate with MongoDB, since they are running on
# different hosts.
###########################################################
mongod_security_group:
type: cloudify.aws.nodes.SecurityGroup
properties:
description: Security Group for Mongo VMs
rules:
- ip_protocol: tcp
from_port: { get_property: [ mongod, port ] }
to_port: { get_property: [ mongod, port ] }
cidr_ip: 0.0.0.0/0
- ip_protocol: tcp
from_port: 28017
to_port: 28017
cidr_ip: 0.0.0.0/0
###########################################################
# A floating ip to be attached to the nodejs host, since
# eventually we want to be able to access it
# from any machine, on any network.
###########################################################
nodecellar_elasticip:
type: cloudify.aws.nodes.ElasticIP
###########################################################
# This outputs section exposes the application endpoint.
# You can access it by running:
# - cfy deployments -d <deployment_id> outputs
###########################################################
outputs:
endpoint:
description: Web application endpoint
value:
ip_address: { get_attribute: [ nodecellar_elasticip, floating_ip_address ] }
port: { get_property: [ nodecellar, port ] }