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