Merge "Add labels for scenario docs"
[joid.git] / labconfig / orange / pod2 / 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-orange
14         interfaces: ['bridge=brAdm,model=virtio', 'bridge=brData,model=virtio', 'bridge=brStorage,model=virtio']
15         memory: 4096
16         vcpus: 4
17         arch: amd64
18         pool: default
19         disk_size: 120G
20         release: trusty
21
22         # Apt http proxy setting(s)
23         apt_http_proxy:
24
25         apt_sources:
26           - ppa:maas/stable
27           - ppa:juju/stable
28
29         boot_source:
30             url: http://maas.ubuntu.com/images/ephemeral-v2/daily/
31             keyring_filename: /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg
32             exclusive: true
33             selections:
34                 1:
35                     release: trusty
36                     os: ubuntu
37                     arches: amd64
38                     subarches: "*"
39                     labels: daily
40                 2:
41                     release: xenial
42                     os: ubuntu
43                     arches: amd64
44                     subarches: "*"
45                     labels: daily
46
47         # Virsh power settings
48         # Specifies the uri and keys to use for virsh power control of the
49         # juju virtual machine. If the uri is omitted, the value for the
50         # --remote is used. If no power settings are desired, then do not
51         # supply the virsh block.
52         virsh:
53             rsa_priv_key: /home/ubuntu/.ssh/id_rsa
54             rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
55             uri: qemu+ssh://ubuntu@192.168.2.4/system
56
57         # Defines the IP Address that the configuration script will use to
58         # to access the MAAS controller via SSH.
59         ip_address: 192.168.2.5
60
61         # This section allows the user to set a series of options on the
62         # MAAS server itself. The list of config options can be found in
63         # the upstream MAAS documentation:
64         #  - http://maas.ubuntu.com/docs/api.html#maas-server
65         settings:
66             main_archive: http://fr.archive.ubuntu.com/ubuntu
67             upstream_dns: 192.168.2.1
68             maas_name: orangepod2
69             # kernel_opts: "console=tty0 console=ttyS1,115200n8"
70             # ntp_server: ntp.ubuntu.com
71
72         # This section is used to define the networking parameters for when
73         # the node first comes up. It is fed into the meta-data cloud-init
74         # configuration and is used to configure the networking piece of the
75         # service. The contents of this section are written directly to the
76         # /etc/network/interfaces file.
77         #
78         # Please note, this is slightly different than the
79         # node-group-interfaces section below. This will configure the
80         # machine's networking params, and the node-group-interfaces will
81         # configure the maas node-group interfaces which is used for
82         # controlling the dhcp, dns, etc.
83         network_config: |
84             auto lo
85             iface lo inet loopback
86
87             auto eth0
88             iface eth0 inet static
89             address 192.168.2.5
90             netmask 255.255.255.0
91             network 192.168.2.0
92             broadcast 192.168.2.255
93             gateway 192.168.2.1
94             dns-nameservers 192.168.2.1 127.0.0.1
95
96             auto eth1
97             iface eth1 inet static
98             address 192.168.12.5
99             netmask 255.255.255.0
100             network 192.168.12.0
101             broadcast 192.168.12.255
102
103             auto eth2
104             iface eth2 inet static
105             address 192.168.22.5
106             netmask 255.255.255.0
107             network 192.168.22.0
108             broadcast 192.168.22.255
109
110             #auto lo
111             #iface lo inet loopback
112
113             #auto eth0
114             #iface eth0 inet static
115             #  address 192.168.122.2
116             #  netmask 255.255.248.0
117             #  network 192.168.122.0
118             #  broadcast 192.168.122.255
119             #  gateway 192.168.122.1
120             #  dns-nameservers 192.168.122.1 127.0.0.1
121
122         # The node-group-interfaces section is used to configure the MAAS
123         # network interfaces. Basic configuration is supported, such as which
124         # device should be bound, the range of IP addresses, etc.
125         # Note: this may contain the special identifiers:
126         #   ${maas_net} - the first 3 octets of the ipv4 address
127         #   ${maas_ip} - the ip address of the MAAS controller
128         node_group_ifaces:
129             - device: eth0
130               ip: 192.168.2.5
131               subnet_mask: 255.255.255.0
132               broadcast_ip: 192.168.2.255
133               router_ip: 192.168.2.1
134               static_range:
135                   low: 192.168.2.50
136                   high: 192.168.2.80
137               dynamic_range:
138                   low: 192.168.2.81
139                   high: 192.168.2.254
140             - device: eth1
141               ip: 192.168.12.5
142               subnet_mask: 255.255.255.0
143               broadcast_ip: 192.168.12.255
144               management: 1
145               static_range:
146                   low: 192.168.12.50
147                   high: 192.168.12.80
148               dynamic_range:
149                   low: 192.168.12.81
150                   high: 192.168.12.254
151             - device: eth2
152               ip: 192.168.22.5
153               subnet_mask: 255.255.255.0
154               broadcast_ip: 192.168.22.255
155               management: 1
156               static_range:
157                   low: 192.168.22.50
158                   high: 192.168.22.80
159               dynamic_range:
160                   low: 192.168.22.81
161                   high: 192.168.22.254
162
163         # Defines the physical nodes which are added to the MAAS cluster
164         # controller upon startup of the node.
165         nodes:
166             - name: node1-compute
167               tags: compute
168               architecture: amd64/generic
169               mac_addresses:
170                   - "38:63:bb:3f:bc:c8"
171               power:
172                   type: ipmi
173                   address: 192.168.2.11
174                   user: Administrator
175                   pass: pod2Admin
176                   driver: LAN_2_0
177 #              sticky_ip_address:
178 #                  mac_address: "38:63:bb:43:b8:9c"
179 #                  requested_address: 192.168.122.5
180 #
181             - name: node2-compute
182               tags: compute
183               architecture: amd64/generic
184               mac_addresses:
185                   - "38:63:bb:44:34:84"
186               power:
187                   type: ipmi
188                   address: 192.168.2.12
189                   user: Administrator
190                   pass: pod2Admin
191                   driver: LAN_2_0
192
193             - name: node3-compute
194               tags: compute
195               architecture: amd64/generic
196               mac_addresses:
197                   - "38:63:bb:3f:1d:8c"
198               power:
199                   type: ipmi
200                   address: 192.168.2.13
201                   user: Administrator
202                   pass: pod2Admin
203                   driver: LAN_2_0
204
205             - name: node4-compute
206               tags: compute
207               architecture: amd64/generic
208               mac_addresses:
209                   - "38:63:bb:3f:2d:a8"
210               power:
211                   type: ipmi
212                   address: 192.168.2.14
213                   user: Administrator
214                   pass: pod2Admin
215                   driver: LAN_2_0
216
217             - name: node5-control
218               tags: control
219               architecture: amd64/generic
220               mac_addresses:
221                   - "94:57:a5:52:c9:48"
222               power:
223                   type: ipmi
224                   address: 192.168.2.15
225                   user: Administrator
226                   pass: pod2Admin
227                   driver: LAN_2_0
228
229             - name: node6-control
230               tags: control
231               architecture: amd64/generic
232               mac_addresses:
233                   - "94:57:a5:52:63:b0"
234               power:
235                   type: ipmi
236                   address: 192.168.2.16
237                   user: Administrator
238                   pass: pod2Admin
239                   driver: LAN_2_0
240
241             - name: node7-control
242               tags: control
243               architecture: amd64/generic
244               mac_addresses:
245                   - "94:57:a5:52:f1:80"
246               power:
247                   type: ipmi
248                   address: 192.168.2.17
249                   user: Administrator
250                   pass: pod2Admin
251                   driver: LAN_2_0
252
253     # Contains the virtual machine parameters for creating the Juju bootstrap
254     # node virtual machine
255     juju-bootstrap:
256         name: bootstrap
257         interfaces: ['bridge=brAdm,model=virtio']
258         memory: 8192
259         vcpus: 2
260         arch: amd64
261         pool: default
262         disk_size: 60G