1
# This file defines the deployment for the MAAS environment which is to be
2
# deployed and automated.
4
# Contains the virtual machine parameters for creating the Juju bootstrap
8
interfaces: ['bridge=virbr0,model=virtio']
15
# requested_address: 192.168.122.25
18
# Defines the general setup for the MAAS environment, including the
19
# username and password for the host as well as the MAAS server.
23
# Contains the virtual machine parameters for creating the MAAS virtual
24
# server. Here you can configure the name of the virsh domain, the
25
# parameters for how the network is attached.
27
interfaces: ['bridge=virbr0,model=virtio']
35
# Apt http proxy setting(s)
43
url: http://maas.ubuntu.com/images/ephemeral-v2/daily/
44
keyring_filename: /usr/share/keyrings/ubuntu-cloudimage-keyring.gpg
60
# Virsh power settings
61
# Specifies the uri and keys to use for virsh power control of the
62
# juju virtual machine. If the uri is omitted, the value for the
63
# --remote is used. If no power settings are desired, then do not
64
# supply the virsh block.
66
rsa_priv_key: /home/ubuntu/.ssh/id_rsa
67
rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
68
uri: qemu+ssh://ubuntu@192.168.122.1/system
70
# Defines the IP Address that the configuration script will use to
71
# to access the MAAS controller via SSH.
72
ip_address: 192.168.122.2
74
# This section allows the user to set a series of options on the
75
# MAAS server itself. The list of config options can be found in
76
# the upstream MAAS documentation:
77
# - http://maas.ubuntu.com/docs/api.html#maas-server
79
main_archive: http://us.archive.ubuntu.com/ubuntu
80
upstream_dns: 192.168.122.1
82
# kernel_opts: "console=tty0 console=ttyS1,115200n8"
83
ntp_server: ntp.ubuntu.com
85
# This section is used to define the networking parameters for when
86
# the node first comes up. It is fed into the meta-data cloud-init
87
# configuration and is used to configure the networking piece of the
88
# service. The contents of this section are written directly to the
89
# /etc/network/interfaces file.
91
# Please note, this is slightly different than the
92
# node-group-interfaces section below. This will configure the
93
# machine's networking params, and the node-group-interfaces will
94
# configure the maas node-group interfaces which is used for
95
# controlling the dhcp, dns, etc.
98
iface lo inet loopback
101
iface eth0 inet static
102
address 192.168.122.2
103
netmask 255.255.255.0
104
network 192.168.122.0
105
broadcast 192.168.122.255
106
gateway 192.168.122.1
107
dns-nameservers 192.168.122.1 127.0.0.1
109
# See https://maas.ubuntu.com/docs/maascli.html#node-groups for
110
# description and full list of supported options.
111
# NOTE: interfaces are added using the node_group_interfaces section
112
# and only one node_group can be created by this bundle.
113
# Additional node groups can be added post deployment.
115
# # This is the cluster DNS name.
118
# The node-group-interfaces section is used to configure the MAAS
119
# network interfaces. Basic configuration is supported, such as which
120
# device should be bound, the range of IP addresses, etc.
121
# Note: this may contain the special identifiers:
122
# ${maas_net} - the first 3 octets of the ipv4 address
123
# ${maas_ip} - the ip address of the MAAS controller
127
subnet_mask: 255.255.255.0
128
broadcast_ip: 192.168.122.255
129
router_ip: 192.168.122.1
132
high: 192.168.122.200
135
high: 192.168.122.100
137
# Physical nodes to be added to the MAAS cluster. Nodes will be
138
# configured, commissioned and put into the Ready state so
139
# they are ready to be deployed to.
143
# architecture: amd64/generic
145
# - "38:63:bb:43:b8:9c"
153
# mac_address: "38:63:bb:43:b8:9c"
154
# requested_address: 192.168.122.6