added ubuntu charm for local deployment charm to configure the
[joid.git] / ci / maas / intel / pod6 / deployment.yaml
1 # This file defines the deployment for the MAAS environment which is to be
2 # deployed and automated.
3 demo-maas:
4     maas:
5         # Defines the general setup for the MAAS environment, including the
6         # username and password for the host as well as the MAAS server.
7         user: ubuntu
8         password: ubuntu
9
10         # Contains the virtual machine parameters for creating the MAAS virtual
11         # server. Here you can configure the name of the virsh domain, the
12         # parameters for how the network is attached.
13         name: opnfv-maas-intel
14         interfaces: ['bridge=brAdm,model=virtio', 'bridge=brData,model=virtio', 'bridge=brPublic,model=virtio']
15         memory: 4096
16         vcpus: 4
17         arch: amd64
18         pool: default
19         disk_size: 160G
20
21         # Apt http proxy setting(s)
22         apt_http_proxy:
23
24         apt_sources:
25           - ppa:maas/stable
26           - ppa:juju/stable
27
28         # Virsh power settings
29         # Specifies the uri and keys to use for virsh power control of the 
30         # juju virtual machine. If the uri is omitted, the value for the
31         # --remote is used. If no power settings are desired, then do not
32         # supply the virsh block.
33         virsh:
34             rsa_priv_key: /home/ubuntu/.ssh/id_rsa
35             rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
36             uri: qemu+ssh://ubuntu@10.4.1.1/system
37
38         # Defines the IP Address that the configuration script will use to
39         # to access the MAAS controller via SSH.
40         ip_address: 10.4.1.2
41
42         # This section allows the user to set a series of options on the
43         # MAAS server itself. The list of config options can be found in
44         # the upstream MAAS documentation:
45         #  - http://maas.ubuntu.com/docs/api.html#maas-server
46         settings:
47             main_archive: http://us.archive.ubuntu.com/ubuntu
48             upstream_dns: 10.4.0.2
49             maas_name: intelpod6
50             # kernel_opts: "console=tty0 console=ttyS1,115200n8"
51             # ntp_server: ntp.ubuntu.com
52
53         # This section is used to define the networking parameters for when
54         # the node first comes up. It is fed into the meta-data cloud-init
55         # configuration and is used to configure the networking piece of the
56         # service. The contents of this section are written directly to the
57         # /etc/network/interfaces file.
58         #
59         # Please note, this is slightly different than the
60         # node-group-interfaces section below. This will configure the
61         # machine's networking params, and the node-group-interfaces will
62         # configure the maas node-group interfaces which is used for
63         # controlling the dhcp, dns, etc.
64         network_config: |
65             auto lo
66             iface lo inet loopback
67
68             auto eth0
69             iface eth0 inet static
70             address 10.4.1.2
71             netmask 255.255.248.0
72             network 10.4.0.0
73             broadcast 10.4.7.255
74             gateway 10.4.0.1
75             dns-nameservers 10.4.0.2 127.0.0.1
76
77             auto eth1
78             iface eth1 inet static
79             address 10.4.9.2
80             netmask 255.255.248.0
81
82             auto eth2
83             iface eth2 inet static
84             address 10.2.66.3
85             netmask 255.255.255.0
86
87             #auto lo
88             #iface lo inet loopback
89
90             #auto eth0
91             #iface eth0 inet static
92             #  address 192.168.122.2
93             #  netmask 255.255.248.0
94             #  network 192.168.122.0
95             #  broadcast 192.168.122.255
96             #  gateway 192.168.122.1
97             #  dns-nameservers 192.168.122.1 127.0.0.1
98
99         # The node-group-interfaces section is used to configure the MAAS
100         # network interfaces. Basic configuration is supported, such as which
101         # device should be bound, the range of IP addresses, etc.
102         # Note: this may contain the special identifiers:
103         #   ${maas_net} - the first 3 octets of the ipv4 address
104         #   ${maas_ip} - the ip address of the MAAS controller 
105         node_group_ifaces:
106             - device: eth0
107               ip: 10.4.1.2
108               subnet_mask: 255.255.248.0
109               broadcast_ip: 10.4.7.255
110               router_ip: 10.4.0.1
111               static_range:
112                   low: 10.4.2.20
113                   high: 10.4.2.254
114               dynamic_range:
115                   low: 10.4.1.50
116                   high: 10.4.1.254
117             - device: eth1
118               ip: 10.4.9.2
119               subnet_mask: 255.255.255.0
120               broadcast_ip: 10.4.9.255
121               management: 1
122               static_range:
123                   low: 10.4.9.20
124                   high: 10.4.9.150
125               dynamic_range:
126                   low: 10.4.9.151
127                   high: 10.4.9.200
128             - device: eth2
129               ip: 10.2.66.3
130               subnet_mask: 255.255.255.0
131               broadcast_ip: 10.2.66.255
132               management: 1
133               static_range:
134                   low: 10.2.66.20
135                   high: 10.2.66.150
136               dynamic_range:
137                   low: 10.2.66.151
138                   high: 10.2.66.200
139
140         # Defines the physical nodes which are added to the MAAS cluster
141         # controller upon startup of the node.
142         nodes:
143             - name: node2-control
144               tags: control
145               architecture: amd64/generic
146               mac_addresses:
147                   - "00:1e:67:e0:0b:71"
148                   - "00:1e:67:e0:0b:72"
149                   - "00:1e:67:d0:9a:8c"
150                   - "00:1e:67:d0:9a:8d"
151               power:
152                   type: ipmi
153                   address: 10.4.7.2
154                   user: root
155                   pass: root
156                   driver: LAN_2_0
157 #              sticky_ip_address:
158 #                  mac_address: "38:63:bb:43:b8:9c"
159 #                  requested_address: 192.168.122.5
160                 
161 #            - name: node1
162 #              tags: physical
163 #              architecture: amd64/generic
164 #              mac_addresses:
165 #                  - "00:1e:67:e0:08:b0"
166 #                  - "00:1e:67:e0:08:b1"
167 #                  - "00:1e:67:d0:99:ee"
168 #                  - "00:1e:67:d0:99:ef"
169 #              power:
170 #                  type: ipmi
171 #                  address: 10.4.2.9
172 #                  user: root
173 #                  pass: root
174 #                  driver: LAN_2_0
175 #              sticky_ip_address:
176 #                  mac_address: "38:63:bb:43:b8:9c"
177 #                  requested_address: 192.168.122.5
178
179             - name: node3-control
180               tags: control
181               architecture: amd64/generic
182               mac_addresses:
183                   - "00:1e:67:e0:09:32"
184                   - "00:1e:67:e0:09:33"
185                   - "00:1e:67:d0:9b:92"
186                   - "00:1e:67:d0:9b:93"
187               power:
188                   type: ipmi
189                   address: 10.4.7.3
190                   user: root
191                   pass: root
192                   driver: LAN_2_0
193 #              sticky_ip_address:
194 #                  mac_address: "38:63:bb:43:b8:9c"
195 #                  requested_address: 192.168.122.5
196
197             - name: node4-control
198               tags: control
199               architecture: amd64/generic
200               mac_addresses:
201                   - "00:1e:67:e0:09:fa"
202                   - "00:1e:67:e0:09:fb"
203                   - "00:1e:67:d0:9c:9c"
204                   - "00:1e:67:d0:9c:9d"
205               power:
206                   type: ipmi
207                   address: 10.4.7.4
208                   user: root
209                   pass: root
210                   driver: LAN_2_0
211 #              sticky_ip_address:
212 #                  mac_address: "38:63:bb:43:b8:9c"
213 #                  requested_address: 192.168.122.5
214
215             - name: node5-compute
216               tags: compute
217               architecture: amd64/generic
218               mac_addresses:
219                   - "00:1e:67:cf:bc:f7"
220                   - "00:1e:67:cf:bc:f8"
221                   - "00:1e:67:d0:9c:26"
222                   - "00:1e:67:d0:9c:27"
223               power:
224                   type: ipmi
225                   address: 10.4.7.5
226                   user: root
227                   pass: root
228                   driver: LAN_2_0
229 #              sticky_ip_address:
230 #                  mac_address: "38:63:bb:43:b8:9c"
231 #                  requested_address: 192.168.122.5
232
233 #            - name: jenkins-slave
234 #              tags: jenkins-slave
235 #              architecture: amd64/generic
236 #              mac_addresses:
237 #                  - "52:54:00:f0:5c:53"
238 #              power:
239 #                  type: virsh
240 #                  address: qemu+ssh://ubuntu@10.4.1.1/system
241
242     # Contains the virtual machine parameters for creating the Juju bootstrap
243     # node virtual machine
244     juju-bootstrap:
245         name: bootstrap
246         interfaces: ['bridge=brAdm,model=virtio', 'bridge=brData,model=virtio', 'bridge=brPublic,model=virtio']
247         memory: 4096
248         vcpus: 4
249         arch: amd64
250         pool: default
251         disk_size: 120G