2941972574133468f521af4f108f6d5ca8d94512
[joid.git] / ci / maas / cengn_lynx / pod1 / deployment.yaml
1 # This file defines the deployment for the MAAS environment which is to be
2 # deployed and automated.
3 cengn-lynx-pod1:
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-cengn-lynx
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.120.0.2/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.120.0.3
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             upstream_dns: 192.168.60.1
48             maas_name: cengnlynxpod1
49             # kernel_opts: "console=tty0 console=ttyS1,115200n8"
50             # ntp_server: ntp.ubuntu.com
51
52         # This section is used to define the networking parameters for when
53         # the node first comes up. It is fed into the meta-data cloud-init
54         # configuration and is used to configure the networking piece of the
55         # service. The contents of this section are written directly to the
56         # /etc/network/interfaces file.
57         #
58         # Please note, this is slightly different than the
59         # node-group-interfaces section below. This will configure the
60         # machine's networking params, and the node-group-interfaces will
61         # configure the maas node-group interfaces which is used for
62         # controlling the dhcp, dns, etc.
63         network_config: |
64             auto lo
65             iface lo inet loopback
66
67             auto eth0
68             iface eth0 inet static
69             address 10.120.0.3
70             netmask 255.255.255.0
71             network 10.120.0.0
72             broadcast 10.120.0.255
73             gateway 10.120.0.254
74             dns-nameservers 192.168.60.1 8.8.8.8 127.0.0.1
75
76             auto eth1
77             iface eth1 inet static
78             address 172.16.121.3
79             netmask 255.255.255.0
80             
81             auto eth2
82             iface eth2 inet static
83             address 172.16.122.3
84             netmask 255.255.255.0
85             
86
87         # The node-group-interfaces section is used to configure the MAAS
88         # network interfaces. Basic configuration is supported, such as which
89         # device should be bound, the range of IP addresses, etc.
90         # Note: this may contain the special identifiers:
91         #   ${maas_net} - the first 3 octets of the ipv4 address
92         #   ${maas_ip} - the ip address of the MAAS controller 
93         node_group_ifaces:
94             - device: eth0
95               ip: 10.120.0.3
96               subnet_mask: 255.255.255.0
97               broadcast_ip: 10.120.0.255
98               router_ip: 10.120.0.254
99               static_range:
100                   low: 10.120.0.20
101                   high: 10.120.0.100
102               dynamic_range:
103                   low: 10.120.0.101
104                   high: 10.120.0.200
105             - device: eth1
106               ip: 172.16.121.3
107               subnet_mask: 255.255.255.0
108               broadcast_ip: 172.16.121.255
109               management: 1
110               static_range:
111                 low: 172.16.121.20
112                 high: 172.16.121.100
113               dynamic_range:
114                 low: 172.16.121.101
115                 high: 172.16.121.200
116             - device: eth2
117               ip: 172.16.122.3
118               subnet_mask: 255.255.255.0
119               broadcast_ip: 172.16.122.255
120               management: 1
121               static_range:
122                 low: 172.16.122.20
123                 high: 172.16.122.100
124               dynamic_range:
125                 low: 172.16.122.101
126                 high: 172.16.122.200
127             
128         # Defines the physical nodes which are added to the MAAS cluster
129         # controller upon startup of the node.
130         nodes:
131           - name: node1-compute
132             tags: compute
133             architecture: amd64/generic
134             mac_addresses:
135               - "0c:c4:7a:3a:c5:b6"
136             power:
137                 type: ipmi
138                 address: 192.168.42.72
139                 user: root
140                 pass: root
141                 driver: LAN_2_0
142
143           - name: node2-compute
144             tags: compute
145             architecture: amd64/generic
146             mac_addresses:
147               - "0c:c4:7a:3a:b2:ae"
148             power:
149                 type: ipmi
150                 address: 192.168.42.40
151                 user: root
152                 pass: root
153                 driver: LAN_2_0
154
155           - name: node3-control
156             tags: control
157             architecture: amd64/generic
158             mac_addresses:
159               - "0c:c4:7a:1f:6f:c0"
160             power:
161                 type: ipmi
162                 address: 192.168.42.33
163                 user: root
164                 pass: root
165                 driver: LAN_2_0
166
167           - name: node4-control
168             tags: control
169             architecture: amd64/generic
170             mac_addresses:
171               - "0c:c4:7a:31:9d:bc"
172             power:
173                 type: ipmi
174                 address: 192.168.42.6
175                 user: root
176                 pass: root
177                 driver: LAN_2_0
178
179           - name: node5-control
180             tags: control
181             architecture: amd64/generic
182             mac_addresses:
183                - "00:25:90:fd:2e:48"
184             power:
185                  type: ipmi
186                  address: 192.168.42.35
187                  user: root
188                  pass: root
189                  driver: LAN_2_0
190
191
192 #            - name: jenkins-slave
193 #              tags: jenkins-slave
194 #              architecture: amd64/generic
195 #              mac_addresses:
196 #                  - "52:54:00:f0:5c:53"
197 #              power:
198 #                  type: virsh
199 #                  address: qemu+ssh://ubuntu@10.4.1.1/system
200
201     # Contains the virtual machine parameters for creating the Juju bootstrap
202     # node virtual machine
203     juju-bootstrap:
204         name: bootstrap
205         interfaces: ['bridge=brAdm,model=virtio','bridge=brPublic,model=virtio']
206         memory: 4096
207         vcpus: 4
208         arch: amd64
209         pool: default
210         disk_size: 120G