-# This file defines the deployment for the MAAS environment which is to be\r
-# deployed and automated.\r
-demo-maas:\r
- maas:\r
- # Defines the general setup for the MAAS environment, including the\r
- # username and password for the host as well as the MAAS server.\r
- user: ubuntu\r
- password: ubuntu\r
-\r
- # Contains the virtual machine parameters for creating the MAAS virtual\r
- # server. Here you can configure the name of the virsh domain, the\r
- # parameters for how the network is attached.\r
- name: opnfv-maas-juniper\r
- interfaces: ['bridge=brAdm,model=virtio','bridge=brPublic,model=virtio']\r
- #interfaces: ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']\r
- memory: 4096\r
- vcpus: 1\r
- arch: amd64\r
- pool: default\r
- disk_size: 160G\r
-\r
- # Apt http proxy setting(s)\r
- apt_http_proxy:\r
-\r
- apt_sources:\r
- - ppa:maas/stable\r
- - ppa:juju/stable\r
-\r
- # Virsh power settings\r
- # Specifies the uri and keys to use for virsh power control of the \r
- # juju virtual machine. If the uri is omitted, the value for the\r
- # --remote is used. If no power settings are desired, then do not\r
- # supply the virsh block.\r
- virsh:\r
- rsa_priv_key: /home/ubuntu/.ssh/id_rsa\r
- rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub\r
- uri: qemu+ssh://ubuntu@172.16.50.51/system\r
-\r
- # Defines the IP Address that the configuration script will use to\r
- # to access the MAAS controller via SSH.\r
- ip_address: 172.16.50.50\r
-\r
- # This section allows the user to set a series of options on the\r
- # MAAS server itself. The list of config options can be found in\r
- # the upstream MAAS documentation:\r
- # - http://maas.ubuntu.com/docs/api.html#maas-server\r
- settings:\r
- main_archive: http://us.archive.ubuntu.com/ubuntu\r
- upstream_dns: 8.8.8.8\r
- maas_name: juniperpod1\r
- # kernel_opts: "console=tty0 console=ttyS1,115200n8"\r
- # ntp_server: ntp.ubuntu.com\r
-\r
- # This section is used to define the networking parameters for when\r
- # the node first comes up. It is fed into the meta-data cloud-init\r
- # configuration and is used to configure the networking piece of the\r
- # service. The contents of this section are written directly to the\r
- # /etc/network/interfaces file.\r
- #\r
- # Please note, this is slightly different than the\r
- # node-group-interfaces section below. This will configure the\r
- # machine's networking params, and the node-group-interfaces will\r
- # configure the maas node-group interfaces which is used for\r
- # controlling the dhcp, dns, etc.\r
- network_config: |\r
- auto lo\r
- iface lo inet loopback\r
-\r
- auto eth0\r
- iface eth0 inet static\r
- address 172.16.50.50\r
- netmask 255.255.255.0\r
- network 172.16.50.0\r
- broadcast 172.16.50.255\r
- #gateway x.x.x.x\r
- dns-nameservers 8.8.8.8 127.0.0.1\r
-\r
- auto eth1\r
- iface eth1 inet static\r
- address 10.10.15.50\r
- netmask 255.255.240.0\r
- network 10.10.0.0\r
- broadcast 10.10.15.255\r
- gateway 10.10.10.1\r
-\r
- #auto eth2\r
- #iface eth2 inet static\r
- #address 10.2.65.3\r
- #netmask 255.255.255.0\r
- #network 10.2.65.0\r
- #broadcast 10.2.65.255\r
-\r
- # The node-group-interfaces section is used to configure the MAAS\r
- # network interfaces. Basic configuration is supported, such as which\r
- # device should be bound, the range of IP addresses, etc.\r
- # Note: this may contain the special identifiers:\r
- # ${maas_net} - the first 3 octets of the ipv4 address\r
- # ${maas_ip} - the ip address of the MAAS controller \r
- node_group_ifaces:\r
- - device: eth0\r
- ip: 172.16.50.50\r
- subnet_mask: 255.255.255.0\r
- broadcast_ip: 172.16.50.255\r
- router_ip: 172.16.50.50\r
- static_range:\r
- low: 172.16.50.60\r
- high: 172.16.50.129\r
- dynamic_range:\r
- low: 172.16.50.130\r
- high: 172.16.50.200\r
- #- device: eth1\r
- # ip: 10.10.15.50\r
- # subnet_mask: 255.255.240.0\r
- # broadcast_ip: 10.10.15.255\r
- # router_ip: 10.10.10.1\r
- #management: 1\r
- # static_range:\r
- # low: 10.10.15.60\r
- # high: 10.10.15.129\r
- # dynamic_range:\r
- # low: 10.10.15.130\r
- # high: 10.10.15.200\r
- #- device: eth2\r
- # ip: 10.2.65.3\r
- # subnet_mask: 255.255.255.0\r
- # broadcast_ip: 10.2.65.255\r
- # management: 1\r
- # static_range:\r
- # low: 10.2.65.20\r
- # high: 10.2.65.100\r
- # dynamic_range:\r
- # low: 10.2.65.101\r
- # high: 10.2.65.200\r
- # Defines the physical nodes which are added to the MAAS cluster\r
- # controller upon startup of the node.\r
- \r
- # Juniper pod1: server 2, 4 and 6 have 32GB RAM and 4 cores. server 3 \r
- # and 5 have 64GB RAM and 12 cores. Make server 2, 4 and 6 as control\r
- # nodes and 3 and 5 as compute nodes.\r
- nodes:\r
- - name: 2-R4N4B2-control\r
- tags: control\r
- architecture: amd64/generic\r
- mac_addresses:\r
- - "0c:c4:7a:16:2a:70"\r
- power:\r
- type: ipmi\r
- address: 10.10.7.92\r
- user: ADMIN\r
- pass: ADMIN\r
- driver: LAN_2_0\r
-# sticky_ip_address:\r
-# mac_address: "38:63:bb:43:b8:9c"\r
-# requested_address: 192.168.122.5\r
- \r
- - name: 3-R4N3B1-compute\r
- tags: compute\r
- architecture: amd64/generic\r
- mac_addresses:\r
- - "0c:c4:7a:53:57:c2"\r
- power:\r
- type: ipmi\r
- address: 10.10.7.84\r
- user: ADMIN\r
- pass: ADMIN\r
- driver: LAN_2_0\r
-# sticky_ip_address:\r
-# mac_address: "38:63:bb:43:b8:9c"\r
-# requested_address: 192.168.122.5\r
-\r
- - name: 4-R4N4B4-control\r
- tags: control\r
- architecture: amd64/generic\r
- mac_addresses:\r
- - "0c:c4:7a:16:22:9c"\r
- power:\r
- type: ipmi\r
- address: 10.10.7.95\r
- user: ADMIN\r
- pass: ADMIN\r
- driver: LAN_2_0\r
-# sticky_ip_address:\r
-# mac_address: "38:63:bb:43:b8:9c"\r
-# requested_address: 192.168.122.5\r
-\r
- - name: 5-R4N3B2-compute\r
- tags: compute\r
- architecture: amd64/generic\r
- mac_addresses:\r
- - "0c:c4:7a:53:57:16"\r
- power:\r
- type: ipmi\r
- address: 10.10.7.85\r
- user: ADMIN\r
- pass: ADMIN\r
- driver: LAN_2_0\r
-# sticky_ip_address:\r
-# mac_address: "38:63:bb:43:b8:9c"\r
-# requested_address: 192.168.122.5\r
-\r
- - name: 6-R4N4B3-control\r
- tags: control\r
- architecture: amd64/generic\r
- mac_addresses:\r
- - "0c:c4:7a:16:2a:0a"\r
- power:\r
- type: ipmi\r
- address: 10.10.7.93\r
- user: ADMIN\r
- pass: ADMIN\r
- driver: LAN_2_0\r
-# sticky_ip_address:\r
-# mac_address: "38:63:bb:43:b8:9c"\r
-# requested_address: 192.168.122.5\r
-\r
-# - name: jenkins-slave\r
-# tags: jenkins-slave\r
-# architecture: amd64/generic\r
-# mac_addresses:\r
-# - "52:54:00:f0:5c:53"\r
-# power:\r
-# type: virsh\r
-# address: qemu+ssh://ubuntu@10.4.1.1/system\r
-\r
- # Contains the virtual machine parameters for creating the Juju bootstrap\r
- # node virtual machine\r
- juju-bootstrap:\r
- name: bootstrap\r
- interfaces: ['bridge=brAdm,model=virtio','bridge=brPublic,model=virtio']\r
- #interfaces: ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']\r
- memory: 4096\r
- vcpus: 2\r
- arch: amd64\r
- pool: default\r
- disk_size: 120G\r
+# This file defines the deployment for the MAAS environment which is to be
+# deployed and automated.
+demo-maas:
+ maas:
+ # Defines the general setup for the MAAS environment, including the
+ # username and password for the host as well as the MAAS server.
+ user: ubuntu
+ password: ubuntu
+
+ # Contains the virtual machine parameters for creating the MAAS virtual
+ # server. Here you can configure the name of the virsh domain, the
+ # parameters for how the network is attached.
+ name: opnfv-maas-juniper
+ interfaces: ['bridge=brAdm,model=virtio', 'bridge=brPublic,model=virtio']
+ memory: 4096
+ vcpus: 1
+ arch: amd64
+ pool: default
+ disk_size: 160G
+
+ # Apt http proxy setting(s)
+ apt_http_proxy:
+
+ apt_sources:
+ - ppa:maas/stable
+ - ppa:juju/stable
+
+ # Virsh power settings
+ # Specifies the uri and keys to use for virsh power control of the
+ # juju virtual machine. If the uri is omitted, the value for the
+ # --remote is used. If no power settings are desired, then do not
+ # supply the virsh block.
+ virsh:
+ rsa_priv_key: /home/ubuntu/.ssh/id_rsa
+ rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
+ uri: qemu+ssh://ubuntu@172.16.50.51/system
+
+ # Defines the IP Address that the configuration script will use to
+ # to access the MAAS controller via SSH.
+ ip_address: 172.16.50.50
+
+ # This section allows the user to set a series of options on the
+ # MAAS server itself. The list of config options can be found in
+ # the upstream MAAS documentation:
+ # - http://maas.ubuntu.com/docs/api.html#maas-server
+ settings:
+ main_archive: http://us.archive.ubuntu.com/ubuntu
+ upstream_dns: 8.8.8.8
+ maas_name: juniperpod1
+ # kernel_opts: "console=tty0 console=ttyS1,115200n8"
+ # ntp_server: ntp.ubuntu.com
+
+ # This section is used to define the networking parameters for when
+ # the node first comes up. It is fed into the meta-data cloud-init
+ # configuration and is used to configure the networking piece of the
+ # service. The contents of this section are written directly to the
+ # /etc/network/interfaces file.
+ #
+ # Please note, this is slightly different than the
+ # node-group-interfaces section below. This will configure the
+ # machine's networking params, and the node-group-interfaces will
+ # configure the maas node-group interfaces which is used for
+ # controlling the dhcp, dns, etc.
+ network_config: |
+ auto lo
+ iface lo inet loopback
+
+ auto eth0
+ iface eth0 inet static
+ address 172.16.50.50
+ netmask 255.255.255.0
+ network 172.16.50.0
+ broadcast 172.16.50.255
+ dns-nameservers 8.8.8.8 127.0.0.1
+
+ auto eth1
+ iface eth1 inet static
+ address 10.10.15.50
+ netmask 255.255.240.0
+ network 10.10.0.0
+ broadcast 10.10.15.255
+ gateway 10.10.10.1
+
+ # The node-group-interfaces section is used to configure the MAAS
+ # network interfaces. Basic configuration is supported, such as which
+ # device should be bound, the range of IP addresses, etc.
+ # Note: this may contain the special identifiers:
+ # ${maas_net} - the first 3 octets of the ipv4 address
+ # ${maas_ip} - the ip address of the MAAS controller
+ node_group_ifaces:
+ - device: eth0
+ ip: 172.16.50.50
+ subnet_mask: 255.255.255.0
+ broadcast_ip: 172.16.50.255
+ router_ip: 172.16.50.50
+ static_range:
+ low: 172.16.50.60
+ high: 172.16.50.90
+ dynamic_range:
+ low: 172.16.50.91
+ high: 172.16.50.254
+
+ # Defines the physical nodes which are added to the MAAS cluster
+ # controller upon startup of the node.
+ nodes:
+ - name: 2-R4N4B2-control
+ tags: control
+ architecture: amd64/generic
+ mac_addresses:
+ - "0c:c4:7a:16:2a:70"
+ power:
+ type: ipmi
+ address: 10.10.7.92
+ user: ADMIN
+ pass: ADMIN
+ driver: LAN_2_0
+
+ - name: 3-R4N3B1-compute
+ tags: compute
+ architecture: amd64/generic
+ mac_addresses:
+ - "0c:c4:7a:53:57:c2"
+ power:
+ type: ipmi
+ address: 10.10.7.84
+ user: ADMIN
+ pass: ADMIN
+ driver: LAN_2_0
+
+ - name: 4-R4N4B4-control
+ tags: control
+ architecture: amd64/generic
+ mac_addresses:
+ - "0c:c4:7a:16:22:9c"
+ power:
+ type: ipmi
+ address: 10.10.7.95
+ user: ADMIN
+ pass: ADMIN
+ driver: LAN_2_0
+
+ - name: 5-R4N3B2-compute
+ tags: compute
+ architecture: amd64/generic
+ mac_addresses:
+ - "0c:c4:7a:53:57:16"
+ power:
+ type: ipmi
+ address: 10.10.7.85
+ user: ADMIN
+ pass: ADMIN
+ driver: LAN_2_0
+
+ - name: 6-R4N4B3-control
+ tags: control
+ architecture: amd64/generic
+ mac_addresses:
+ - "0c:c4:7a:16:2a:0a"
+ power:
+ type: ipmi
+ address: 10.10.7.93
+ user: ADMIN
+ pass: ADMIN
+ driver: LAN_2_0
+
+ # Contains the virtual machine parameters for creating the Juju bootstrap
+ # node virtual machine
+ juju-bootstrap:
+ name: bootstrap
+ interfaces: ['bridge=brAdm,model=virtio', 'bridge=brPublic,model=virtio']
+ memory: 4096
+ vcpus: 2
+ arch: amd64
+ pool: default
+ disk_size: 120G
-default: demo-maas\r
-\r
-environments:\r
-\r
- # https://juju.ubuntu.com/docs/config-maas.html\r
- demo-maas:\r
- type: maas\r
-\r
- # maas-server specifies the location of the MAAS server. It must\r
- # specify the base path.\r
- #\r
- maas-server: 'http://10.4.1.2/MAAS'\r
-\r
- # maas-oauth holds the OAuth credentials from MAAS.\r
- #\r
- maas-oauth: 'HyacKVwxBVE9xwmJW7:CVwUpERLN3fDUbkUra:ETW88KVJxDHQA3kqmZgghUQnzanSFwH4'\r
-\r
- # maas-server bootstrap ssh connection options\r
- #\r
-\r
- # bootstrap-timeout time to wait contacting a state server, in seconds.\r
- bootstrap-timeout: 1800\r
-\r
- # Whether or not to refresh the list of available updates for an\r
- # OS. The default option of true is recommended for use in\r
- # production systems, but disabling this can speed up local\r
- # deployments for development or testing.\r
- #\r
- enable-os-refresh-update: false\r
-\r
- # Whether or not to perform OS upgrades when machines are\r
- # provisioned. The default option of true is recommended for use\r
- # in production systems, but disabling this can speed up local\r
- # deployments for development or testing.\r
- #\r
- enable-os-upgrade: false \r
- \r
- \r
- admin-secret: admin\r
- default-series: trusty\r
+default: demo-maas
+
+environments:
+
+ # https://juju.ubuntu.com/docs/config-maas.html
+ demo-maas:
+ type: maas
+
+ # maas-server specifies the location of the MAAS server. It must
+ # specify the base path.
+ #
+ maas-server: 'http://10.4.1.2/MAAS'
+
+ # maas-oauth holds the OAuth credentials from MAAS.
+ #
+ maas-oauth: 'HyacKVwxBVE9xwmJW7:CVwUpERLN3fDUbkUra:ETW88KVJxDHQA3kqmZgghUQnzanSFwH4'
+
+ # maas-server bootstrap ssh connection options
+ #
+
+ # bootstrap-timeout time to wait contacting a state server, in seconds.
+ bootstrap-timeout: 1800
+
+ # Whether or not to refresh the list of available updates for an
+ # OS. The default option of true is recommended for use in
+ # production systems, but disabling this can speed up local
+ # deployments for development or testing.
+ #
+ enable-os-refresh-update: false
+
+ # Whether or not to perform OS upgrades when machines are
+ # provisioned. The default option of true is recommended for use
+ # in production systems, but disabling this can speed up local
+ # deployments for development or testing.
+ #
+ enable-os-upgrade: false
+
+
+ admin-secret: admin
+ default-series: trusty
Code Review / joid.git / commitdiff