1 # This file defines the deployment for the MAAS environment which is to be
2 # deployed and automated.
5 # Defines the general setup for the MAAS environment, including the
6 # username and password for the host as well as the MAAS server.
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 # TODO interfaces: ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']
15 interfaces: ['bridge=brAdm,model=virtio','bridge=brPublic,model=virtio']
22 # Apt http proxy setting(s)
29 # Virsh power settings
30 # Specifies the uri and keys to use for virsh power control of the
31 # juju virtual machine. If the uri is omitted, the value for the
32 # --remote is used. If no power settings are desired, then do not
33 # supply the virsh block.
35 rsa_priv_key: /home/ubuntu/.ssh/id_rsa
36 rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
37 uri: qemu+ssh://ubuntu@10.120.0.2/system
39 # Defines the IP Address that the configuration script will use to
40 # to access the MAAS controller via SSH.
41 ip_address: 10.120.0.3
43 # This section allows the user to set a series of options on the
44 # MAAS server itself. The list of config options can be found in
45 # the upstream MAAS documentation:
46 # - http://maas.ubuntu.com/docs/api.html#maas-server
48 upstream_dns: 192.168.60.1
49 maas_name: cengnlynxpod1
50 # kernel_opts: "console=tty0 console=ttyS1,115200n8"
51 # ntp_server: ntp.ubuntu.com
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.
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.
66 iface lo inet loopback
69 iface eth0 inet static
73 broadcast 10.120.0.255
75 dns-nameservers 192.168.60.1 8.8.8.8 127.0.0.1
78 iface eth1 inet static
83 iface eth2 inet static
88 # The node-group-interfaces section is used to configure the MAAS
89 # network interfaces. Basic configuration is supported, such as which
90 # device should be bound, the range of IP addresses, etc.
91 # Note: this may contain the special identifiers:
92 # ${maas_net} - the first 3 octets of the ipv4 address
93 # ${maas_ip} - the ip address of the MAAS controller
97 subnet_mask: 255.255.255.0
98 broadcast_ip: 10.120.0.255
99 router_ip: 10.120.0.254
108 subnet_mask: 255.255.255.0
109 broadcast_ip: 172.16.121.255
119 subnet_mask: 255.255.255.0
120 broadcast_ip: 172.16.122.255
129 # Defines the physical nodes which are added to the MAAS cluster
130 # controller upon startup of the node.
132 - name: node1-compute
134 architecture: amd64/generic
136 - "0c:c4:7a:3a:c5:b6"
139 address: 192.168.42.72
144 - name: node2-compute
146 architecture: amd64/generic
148 - "0c:c4:7a:3a:b2:ae"
151 address: 192.168.42.40
156 - name: node3-control
158 architecture: amd64/generic
160 - "0c:c4:7a:1f:6f:c0"
163 address: 192.168.42.33
168 - name: node4-control
170 architecture: amd64/generic
172 - "0c:c4:7a:31:9d:bc"
175 address: 192.168.42.6
180 - name: node5-control
182 architecture: amd64/generic
184 - "00:25:90:fd:2e:48"
187 address: 192.168.42.35
193 # - name: jenkins-slave
194 # tags: jenkins-slave
195 # architecture: amd64/generic
197 # - "52:54:00:f0:5c:53"
200 # address: qemu+ssh://ubuntu@10.4.1.1/system
202 # Contains the virtual machine parameters for creating the Juju bootstrap
203 # node virtual machine
206 interfaces: ['bridge=brAdm,model=virtio','bridge=brPublic,model=virtio']