summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Blaisonneau <david.blaisonneau@orange.com>2016-04-28 16:10:53 +0200
committerDavid Blaisonneau <david.blaisonneau@orange.com>2016-04-29 16:50:32 +0200
commit2019d07fcf8aed6f456a25ba6d69bbfac93ffe18 (patch)
tree9622aa4478fbb0faf2f6e577793ed1324bf901f0
parentbc117148a167ee908ddc46f2c0cffdeac7484919 (diff)
Add orange pod1
-rwxr-xr-xci/01-deploybundle.sh10
-rwxr-xr-xci/02-maasdeploy.sh3
-rw-r--r--ci/maas/orange/pod1/deployment.yaml215
3 files changed, 228 insertions, 0 deletions
diff --git a/ci/01-deploybundle.sh b/ci/01-deploybundle.sh
index 79535efb..105477ad 100755
--- a/ci/01-deploybundle.sh
+++ b/ci/01-deploybundle.sh
@@ -20,6 +20,16 @@ case "$1" in
esac
case "$3" in
+ 'orangepod1' )
+ # As per your lab vip address list be deafult uses 10.4.1.11 - 10.4.1.20
+ sed -i -- 's/10.4.1.1/192.168.1.2/g' ./bundles.yaml
+ # choose the correct interface to use for data network
+ sed -i -- 's/#os-data-network: 10.4.8.0\/21/os-data-network: 192.168.11.0\/24/g' ./bundles.yaml
+ # Choose the external port to go out from gateway to use.
+ sed -i -- 's/#ext-port: "eth1"/ext-port: "eth1"/g' ./bundles.yaml
+ # Use host for public API for Orange pod2
+ # sed -i -- 's/#os-public-hostname: api.public-fqdn/os-public-hostname: api.pod2.opnfv.fr/g' ./bundles.yaml
+ ;;
'orangepod2' )
# As per your lab vip address list be deafult uses 10.4.1.11 - 10.4.1.20
sed -i -- 's/10.4.1.1/192.168.2.2/g' ./bundles.yaml
diff --git a/ci/02-maasdeploy.sh b/ci/02-maasdeploy.sh
index e1e4f978..cc41ecf1 100755
--- a/ci/02-maasdeploy.sh
+++ b/ci/02-maasdeploy.sh
@@ -11,6 +11,9 @@ case "$1" in
'intelpod6' )
cp maas/intel/pod6/deployment.yaml ./deployment.yaml
;;
+ 'orangepod1' )
+ cp maas/orange/pod1/deployment.yaml ./deployment.yaml
+ ;;
'orangepod2' )
cp maas/orange/pod2/deployment.yaml ./deployment.yaml
;;
diff --git a/ci/maas/orange/pod1/deployment.yaml b/ci/maas/orange/pod1/deployment.yaml
new file mode 100644
index 00000000..dcc8c447
--- /dev/null
+++ b/ci/maas/orange/pod1/deployment.yaml
@@ -0,0 +1,215 @@
+# 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-orange
+ interfaces: ['bridge=brAdm,model=virtio', 'bridge=brData,model=virtio', 'bridge=brStorage,model=virtio']
+ memory: 4096
+ vcpus: 4
+ arch: amd64
+ pool: default
+ disk_size: 120G
+
+ # 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@192.168.1.4/system
+
+ # Defines the IP Address that the configuration script will use to
+ # to access the MAAS controller via SSH.
+ ip_address: 192.168.1.5
+
+ # 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://fr.archive.ubuntu.com/ubuntu
+ upstream_dns: 192.168.1.1
+ maas_name: orangepod1
+ # 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 192.168.1.5
+ netmask 255.255.255.0
+ network 192.168.1.0
+ broadcast 192.168.1.255
+ gateway 192.168.1.1
+ dns-nameservers 192.168.1.1 127.0.0.1
+
+ auto eth1
+ iface eth1 inet static
+ address 192.168.11.5
+ netmask 255.255.255.0
+ network 192.168.11.0
+ broadcast 192.168.11.255
+
+ auto eth2
+ iface eth2 inet static
+ address 192.168.21.5
+ netmask 255.255.255.0
+ network 192.168.21.0
+ broadcast 192.168.21.255
+
+ #auto lo
+ #iface lo inet loopback
+
+ #auto eth0
+ #iface eth0 inet static
+ # address 192.168.122.2
+ # netmask 255.255.248.0
+ # network 192.168.122.0
+ # broadcast 192.168.122.255
+ # gateway 192.168.122.1
+ # dns-nameservers 192.168.122.1 127.0.0.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: 192.168.1.5
+ subnet_mask: 255.255.255.0
+ broadcast_ip: 192.168.1.255
+ router_ip: 192.168.1.1
+ static_range:
+ low: 192.168.1.50
+ high: 192.168.1.80
+ dynamic_range:
+ low: 192.168.1.81
+ high: 192.168.1.254
+ - device: eth1
+ ip: 192.168.11.5
+ subnet_mask: 255.255.255.0
+ broadcast_ip: 192.168.11.255
+ management: 1
+ static_range:
+ low: 192.168.11.50
+ high: 192.168.11.80
+ dynamic_range:
+ low: 192.168.11.81
+ high: 192.168.11.254
+ - device: eth2
+ ip: 192.168.21.5
+ subnet_mask: 255.255.255.0
+ broadcast_ip: 192.168.21.255
+ management: 1
+ static_range:
+ low: 192.168.21.50
+ high: 192.168.21.80
+ dynamic_range:
+ low: 192.168.21.81
+ high: 192.168.21.254
+
+ # Defines the physical nodes which are added to the MAAS cluster
+ # controller upon startup of the node.
+ nodes:
+ - name: node1-compute
+ tags: compute
+ architecture: amd64/generic
+ mac_addresses:
+ - "68:b5:99:74:e3:a8"
+ power:
+ type: ipmi
+ address: 192.168.1.11
+ user: Administrator
+ pass: pod1Admin
+ driver: LAN_2_0
+ - name: node2-compute
+ tags: compute
+ architecture: amd64/generic
+ mac_addresses:
+ - "68:b5:99:75:05:5e"
+ power:
+ type: ipmi
+ address: 192.168.1.12
+ user: Administrator
+ pass: pod1Admin
+ driver: LAN_2_0
+
+ - name: node3-control
+ tags: control
+ architecture: amd64/generic
+ mac_addresses:
+ - "94:57:a5:52:53:7c"
+ power:
+ type: ipmi
+ address: 192.168.1.13
+ user: Administrator
+ pass: pod1Admin
+ driver: LAN_2_0
+
+ - name: node4-control
+ tags: control
+ architecture: amd64/generic
+ mac_addresses:
+ - "94:57:a5:52:c1:54"
+ power:
+ type: ipmi
+ address: 192.168.1.14
+ user: Administrator
+ pass: pod1Admin
+ driver: LAN_2_0
+
+ - name: node5-control
+ tags: control
+ architecture: amd64/generic
+ mac_addresses:
+ - "94:57:a5:52:c1:d8"
+ power:
+ type: ipmi
+ address: 192.168.1.15
+ user: Administrator
+ pass: pod1Admin
+ 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']
+ memory: 4096
+ vcpus: 2
+ arch: amd64
+ pool: default
+ disk_size: 60G