Contrail Cloud Deployment Guide

Transcription

1 Contrail Cloud Deployment Guide Release 10.0 Modified:

2 Juniper Networks, Inc Innovation Way Sunnyvale, California USA Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and/or its affiliates in the United States and other countries. All other trademarks may be property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Contrail Cloud Deployment Guide Release 10.0 Copyright 2018 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year However, the NTP application is known to have some difficulty in the year END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ( EULA ) posted at By downloading, installing or using such software, you agree to the terms and conditions of that EULA. ii

3 Table of Contents Chapter 1 Contrail Cloud Deployment Guide Deploying Contrail Cloud Prerequisites for Deploying Contrail Cloud Deployment Sequence for Deploying Contrail Cloud Install Contrail Cloud Installer on the Contrail Cloud Manager Host Prepare the Deployment Templates Provision Contrail Cloud jumphost Adding Nodes to the Inventory Assign Control Host Roles to the Inventory Create VMs for all Control Roles Assign Compute Hosts Assign Storage Hosts Deploy the OpenStack Cluster Deploy the AppFormix Cluster Install VNF images and Templates Adding New Storage Nodes Appendix: Sample Configuration Files Sample all.yml Sample inventory.yml Sample control-hosts.yml Sample compute-nodes.yml Sample storage-nodes.yml Sample appformix-nodes.yml iii

4 Contrail Cloud Deployment Guide iv

5 CHAPTER 1 Contrail Cloud Deployment Guide Deploying Contrail Cloud Deploying Contrail Cloud on page 5 Appendix: Sample Configuration Files on page 15 Prerequisites for Deploying Contrail Cloud on page 5 Deployment Sequence for Deploying Contrail Cloud on page 6 Adding New Storage Nodes on page 15 Prerequisites for Deploying Contrail Cloud Before you deploy Contrail Cloud 10.0, ensure that your system meets the following prerequisites: Infrastructure Networking Every system must have access to the Contrail Cloud repository satellite. The satellite is used to distribute packages and control software versioning. The undercloud host must have access to the Intelligent Platform Management Interface (IPMI) of every managed server. The undercloud host must be in the same broadcast domain as each managed server s management interface to allow PXE booting. When you use multiple networks that use different switching per rack, this could be accomplished by stretching a VLAN across the interfaces. Currently BOOTP forwarding in the network fabric is not supported. The undercloud is the only DHCP server in this network. Additional networks are created for control plane, tenant traffic, storage access, and storage backend as described in Red Hat OpenStack Platform director (OSPd) installation and usage. Undercloud Host Setup The undercloud is deployed as a virtual machine on a Linux kernel-based virtual machine (KVM) host. You must ensure the KVM host: Runs Red Hat Enterprise Linux (RHEL) 7.4 with only base packages installed. Does not run other virtual machines. 5

6 Contrail Cloud Deployment Guide Has a network connection that can reach the Contrail Cloud Satellite and has IPMI access to physical hardware. Has a network connection that can be used for provisioning other infrastructure resources. Has at least 500 GB space in the /var directory to host virtual machines, packages, and images. Has at least 32 GB RAM and 8 vcpus. Supports users such as a root user who has password-free sudo abilities. Provides password-free SSH access in loopback for the user with sudo capabilities. Resolves Internet and satellite sites with DNS. Has time synchronized with an NTP source. Deployment Sequence for Deploying Contrail Cloud The following sections describe the Contrail Cloud deployment sequence in detail: Install Contrail Cloud Installer on the Contrail Cloud Manager Host on page 6 Prepare the Deployment Templates on page 8 Provision Contrail Cloud jumphost on page 12 Adding Nodes to the Inventory on page 13 Assign Control Host Roles to the Inventory on page 13 Create VMs for all Control Roles on page 13 Assign Compute Hosts on page 14 Assign Storage Hosts on page 14 Deploy the OpenStack Cluster on page 14 Deploy the AppFormix Cluster on page 15 Install VNF images and Templates on page 15 Install Contrail Cloud Installer on the Contrail Cloud Manager Host Download the Contrail Cloud installer in the.sh format. You can then configure site settings to use the Juniper Satellite as the repository to access packages such as Red Hat OpenStack, Ceph Storage, Contrail Networking, and AppFormix packages to install Contrail Cloud. Complete the following steps to perform the installation: 1. Download the Contrail Cloud Installer script from the Contrail Cloud Download Software page and host the script on the Contrail Cloud Manager. 2. Specify the Contrail Cloud activation key by setting the environment variables as shown in the following example: SATELLITE= contrail_cloud_satellite.juniper.net 6

7 Chapter 1: Contrail Cloud Deployment Guide SATELLITE_KEY= ak-dev-rhel-osp SATELLITE_ORG= Contrail NOTE: You can request for Contrail Cloud activation keys by sending an to You will then receive an containing a unique satellite activation key, satellite host, and satellite organization information. 3. Ensure that the Contrail Cloud Installer script has the required permissions to run the following command to install the Contrail Cloud packages:./contrail_cloud_installer.sh \ --satellite_host ${SATELLITE} \ --satellite_key ${SATELLITE_KEY} \ --satellite_org ${SATELLITE_ORG} The Contrail Cloud packages are installed in the /var/lib/contrail_cloud directory. 4. Define site specific information in the Ansible variables: Change directory to /var/lib/contrail_cloud. Copy the sample /var/lib/contrail_cloud/samples/all.yml variables file to the /var/lib/contrail_cloud/ansible/playbooks/inventory/group_vars/all.yml file. Customize the /var/lib/contrail_cloud/ansible/playbooks/inventory/group_vars/all.yml file with site specific settings to reflect the environment. Ensure that the following fields are changed for each site: Field Description SATELLITE_FQDN Satellite host SATELLITE_KEY Satellite Activation Key SATELLITE_ORG Satellite Organization ccd_host_ip Host IP for the Contrail Cloud jumphost cluster_domain Unique DNS domain name for Contrail Cloud ntp_servers NTP time sources ExternalNetCidr A routable subnet to be used for external access to overcloud infrastructure ExternalInterfaceDefaultRoute Route for the External network ExternalAllocationPoolsStart DHCP range start 7

8 Contrail Cloud Deployment Guide Field Description ExternalAllocationPoolsEnd DHCP range end ExternalNetworkVlanID VLAN ID for external network InternalApiNetworkVlanID VLAN ID for internal_api network TenantNetworkVlanID VLAN ID for tenant network StorageNetworkVlanID VLAN ID for storage network StorageMgmtNetworkVlanID VLAN ID for storage management network ManagementNetworkVlanID VLAN ID for management network PublicVirtualFixedIPs External VIP 5. Run the Contrail Cloud Ansible provisioning: Verify that you can establish an SSH connection without specifying a password. sudo ssh localhost true cd /var/lib/contrail_cloud/ansible/playbooks/ Run the following command with sudo using the root user account. sudo ansible-playbook -i inventory/ -u root install_contrail_cloud_manager.yml A new user with the user name contrail is created. The default password is c0ntrail123. Use this user name to run all subsequent operations in Contrail Cloud from the /var/lib/contrail_cloud/ansible/playbooks directory. Prepare the Deployment Templates Inventory Settings The inventory defines all the servers that are used by Contrail Cloud. The ~contrail/inventory.yml file contains the description of all the inventory. You can copy a sample inventory file from /var/lib/contrail_cloud/samples/. Sample inventory file nodes: - name: "csgsnc050" pm_addr: " " pm_type: "pxe_ipmitool" pm_user: "ADMIN" pm_password: "ADMIN" mac: - "0c:c4:7a:81:ad:12" status: "creating 8

9 Chapter 1: Contrail Cloud Deployment Guide The parameter status is optional. When status is not defined or is set to creating, the nodes are imported into the ironic inventory and used for overcloud roles. When status is set to deleting, the node is removed from the ironic inventory. Control Hosts Settings The control hosts run virtual machines for all Contrail Cloud control functions. The following are the various Contrail Cloud control hosts: OpenStack Controller Contrail Controller Contrail Analytics Contrail Analytics Database AppFormix Controller The ~contrail/control-hosts.yml file defines the server and network properties for each control host. To ensure high availability of the control functions, three control hosts are defined Hosts must also be defined in the inventory.yml file. You can copy a sample control-hosts.yml file from the /var/lib/contrail_cloud/samples/ directory. Sample control hosts file hosts: - name: csgsnc066 ip_address: " " interface: eno1: device: "eno1" bridge: "br-eno1" eno2: device: "eno2" bridge: "br-eno2" br-eno1: bootproto: "dhcp" device: "br-eno1" type: "Bridge" delay: "0" br-eno2: device: "br-eno2" type: "Bridge" delay: "0" 9

10 Contrail Cloud Deployment Guide ipaddr: " " netmask: " " br-bond0: device: "br-bond0" type: "Bridge" delay: "0" ens7f0: device: "ens7f0" master: "bond0" slave: "yes" ens7f1: device: "ens7f1" master: "bond0" slave: "yes" bond0: device: "bond0" type: "Bond" bridge: "br-bond0" bondingmaster: "yes" bonding_opts: "mode=802.3ad lacp_rate=fast updelay=1000 miimon=100" Storage Node Settings The ~contrail/storage-nodes.yml file defines the storage nodes that run Ceph storage services. You need to define a minimum of three storage hosts to ensure high availability of the storage functions. Nodes must also be defined in the inventory.yml file. You can copy a sample storage-nodes.yml file from /var/lib/contrail_cloud/samples/. Sample storage node file storage_nodes: - name: csgsnc064 ip_address: " " - name: csgsnc065 ip_address: " " - name: csgsnc066 ip_address: " " Compute Node Settings 10

11 Chapter 1: Contrail Cloud Deployment Guide The compute nodes are used for Nova compute resources. The ~contrail/compute-nodes.yml file defines the compute resources. Hosts defined in the ~contrail/compute-nodes.yml file must also be defined in the inventory file. Sample compute nodes file compute_nodes_kernel: - name: csgsnc061 ip_address: " " - name: csgsnc062 ip_address: " " - name: csgsnc063 ip_address: " " compute_nodes_dpdk: - name: csgsnc064 ip_address: " " - name: csgsnc065 ip_address: " " - name: csgsnc066 ip_address: " " AppFormix Hosts Settings AppFormix hosts are used for AppFormix controllers. The ~contrail/appformix-hosts.yml file defines the AppFormix controller resources. Sample appformix-hosts file hosts: - name: appformix-controller ip_address: " " interface: eth0: device: "eth0" ipaddr: " " netmask: " " eth1: device: "eth1" ipaddr: " " netmask: " " eth2: device: "eth2" ipaddr: " " netmask: " " eth0.3001: device: "eth0.3001" 11

12 Contrail Cloud Deployment Guide vlan: "yes" ipaddr: " " netmask: " " eth0.3002: device: "eth0.3002" vlan: "yes" ipaddr: " " netmask: " " eth0.3003: device: "eth0.3003" vlan: "yes" ipaddr: " " netmask: " " Provision Contrail Cloud jumphost The following example describes jumphost disk partitioning: ~]$ sudo vgscan Reading volume groups from cache. Found volume group "csgsnc049-vg00" using metadata type lvm2 ~]$ sudo lvscan ACTIVE '/dev/csgsnc049-vg00/lv_home' [46.52 GiB] inherit ACTIVE '/dev/csgsnc049-vg00/lv_tmp' [93.05 GiB] inherit ACTIVE '/dev/csgsnc049-vg00/lv_root' [< GiB] inherit ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8: G 0 disk sda1 8:1 0 1G 0 part /boot sda2 8: G 0 part csgsnc049--vg00-lv_root 253: G 0 lvm / csgsnc049--vg00-lv_home 253: G 0 lvm /home csgsnc049--vg00-lv_tmp 253: G 0 lvm /tmp sdb 8: G 0 disk sdb1 8: G 0 part md0 9: G 0 raid1 sdb2 8: G 0 part md1 9: G 0 raid1 sdb3 8: G 0 part md3 9: G 0 raid1 sdb4 8:20 0 1K 0 part sdb5 8: G 0 part md2 9: G 0 raid1 sdb6 8: G 0 part md4 9: G 0 raid1 sdc 8: G 0 disk sdd 8: G 0 disk sde 8: G 0 disk sdf 8: G 0 disk sdf1 8:81 0 4G 0 part [SWAP] 12

13 Chapter 1: Contrail Cloud Deployment Guide ~]$ ~]$ df -kh Filesystem Size Used Avail Use% Mounted on /dev/mapper/csgsnc049--vg00-lv_root 733G 74G 623G 11% / devtmpfs 63G 0 63G 0% /dev tmpfs 63G 0 63G 0% /dev/shm tmpfs 63G 18M 63G 1% /run tmpfs 63G 0 63G 0% /sys/fs/cgroup /dev/sda1 976M 114M 795M 13% /boot /dev/mapper/csgsnc049--vg00-lv_tmp 92G 69M 87G 1% /tmp /dev/mapper/csgsnc049--vg00-lv_home 46G 1.7G 42G 4% /home tmpfs 13G 0 13G 0% /run/user/0 tmpfs 13G 0 13G 0% /run/user/1003 Adding Nodes to the Inventory The inventory-assign.yml playbook adds all nodes defined in the ~contrail/inventory.yml file to the ironic inventory. The nodes added to the ironic inventory are managed by Contrail Cloud. To add nodes to the ironic inventory: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail Run playbook inventory-assign.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ inventory-assign.yml Assign Control Host Roles to the Inventory The control-hosts-deploy.yml playbook assigns all nodes defined in the ~contrail/control-hosts.yml file as control hosts. The hosts are then imaged and booted. To assign control host roles to the inventory: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail Run playbook control-hosts-deploy.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ control-hosts-deploy.yml Create VMs for all Control Roles The control-vms-deploy.yml playbook creates virtual machines for every overcloud control role and imports the virtual machine details into the ironic inventory. To create VMs for control roles: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail

14 Contrail Cloud Deployment Guide 2. Run playbook control-vms-deploy.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ control-vms-deploy.yml Assign Compute Hosts The compute-nodes-assign.yml playbook assigns the Nova compute role for all nodes defined in the ~contrail/compute-nodes.yml file. To assign compute hosts: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail Run playbook compute-nodes-assign.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ compute-nodes-assign.yml Assign Storage Hosts The storage-nodes-assign.yml playbook assigns the Ceph storage role for all nodes defined in the ~contrail/storage-nodes.yml file. To assign storage hosts: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail Run playbook storage-nodes-assign.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ storage-nodes-assign.yml Deploy the OpenStack Cluster The openstack-deploy.yml playbook deploys the OpenStack overcloud with all control functions and all compute and storage resources that have been defined in the previous playbooks. To deploy the OpenStack cluster: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail Run playbook openstack-deploy.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ openstack-deploy.yml 14

15 Chapter 1: Contrail Cloud Deployment Guide Deploy the AppFormix Cluster The appformix-deploy.yml playbook deploys the AppFormix controllers based on the servers defined in the appformix-nodes.yml file. Copy the AppFormix license file to a specific location on the undercloud host and update ansible_variable appformix_license with the license file location in /var/lib/contrail_cloud/ansible/playbooks/group_vars/all.yaml. To deploy the AppFormix cluster: 1. Log in to the Contrail Cloud host with the user name contrail and password c0ntrail Run playbook appformix-deploy.yml. cd /var/lib/contrail_cloud/ansible/playbooks ansible-playbook -i inventory/ appformix-deploy.yml Install VNF images and Templates You can use Horizon or OpenStack command line clients to install Glance images and Heat templates for the VNF services. Adding New Storage Nodes To add new storage nodes: 1. Update inventory.yml. 2. Run the inventory-assign.yml playbook. 3. Update compute-nodes.yml with the new nodes, and run compute-nodes-assign.yml. 4. Update storage-nodes.yml with the new nodes, and run storage-nodes-assign.yml. 5. Finally, rerun openstack-deploy.yml. Related Documentation Appendix: Sample Configuration Files on page 15 Appendix: Sample Configuration Files This appendix includes the following sample files: Sample all.yml on page 16 Sample inventory.yml on page 20 Sample control-hosts.yml on page 20 Sample compute-nodes.yml on page 24 Sample storage-nodes.yml on page 24 Sample appformix-nodes.yml on page 24 15

16 Contrail Cloud Deployment Guide Sample all.yml ################################################### # Ansible specific vars # ansible connection details ansible_connection: ssh host_key_checking: false deprecation_warnings: false dpdk_support: true ceph_support: true jws_enabled: false ################################################### ################################################### # Jumphost ccd_user: contrail ccd_user_password: dt4hdji/4vaty ccd_host_ip: ccd_host_root_password: c0ntrail123 provision_nic_name: "eno2" provision_bridge_name: "br-provision" provision_bridge_ip: provision_bridge_prefix: 0 provision_net_name: "provision" ################################################### # Undercloud ccd_ospd_vm_ip: ccd_ospd_vm_netmask: ccd_ospd_vm_root_password: contrail123 ccd_ospd_vm_user_name: stack ccd_ospd_vm_user_password: '{{ccd_ospd_vm_root_password}}' undercloud_ip: undercloud_prefix: undercloud_prefix_length: 24 undercloud_gateway: undercloud_dhcp_start: undercloud_dhcp_end: undercloud_inspection_ip_range: , ################################################### # Control Hosts control_host_user: cloud-user controlplane_vm_cpu: 8 controlplane_vm_mem: # VM networks # ORDER MATTERS! vm_networks: - br-eno1 - br-eno2 - br-bond0 vm_mgmt_network: br-eno1 deploy_roles: - "control" - "contrail-controller" 16

17 Chapter 1: Contrail Cloud Deployment Guide - "contrail-analytics" - "contrail-analytics-database" bonding_options: "mode=mode=802.3ad lacp_rate=fast updelay=1000 miimon=100" ################################################### # Compute Hosts contrail_dpdk_profile: contrail-dpdk dpdk_node_properties: - "cpu_hugepages:true" - "cpu_txt:true" - "boot_option:local" - "cpu_aes:true" - "cpu_vt:true" - "cpu_hugepages_1g:true" ################################################### # Storage Hosts storage_node_profile: ceph-storage ################################################### # Overcloud #based on contrail-net-bond-vlan.yaml ExternalNetCidr: " /24" ExternalAllocationPoolsStart: " " ExternalAllocationPoolsEnd: " " ExternalNetworkMtu: "1500" # based on contrail-nic-config-compute-bond-vlan.yaml ExternalNetworkVlanID: "10" InternalApiNetworkVlanID: "20" TenantNetworkVlanID: "50" StorageNetworkVlanID: "3002" StorageMgmtNetworkVlanID: "3003" ManagementNetworkVlanID: "3001" ExternalInterfaceDefaultRoute: " " # based on ips-from-pool-all.yaml PublicVirtualFixedIPs: [ ' ' ] ################################################### # Common Properties dns_nameservers: - ' ' - ' ' ntp_servers: - 'ntp2.juniper.net' timezone: 'America/Los_Angeles' # Contrail Cloud Package Satellite SATELLITE_FQDN: ec us-west-2.compute.amazonaws.com SATELLITE_KEY: ak-dev-rhel-osp SATELLITE_ORG: Contrail cluster_domain: "scale.juniper.net" primary_domain_name: '{{ cluster_domain }}' cloud_domain_name: '{{ cluster_domain }}' 17

18 Contrail Cloud Deployment Guide neutron_provision_network: "ctlplane" rh_image_user: '{{ ccd_ospd_vm_user_name }}' # disk size for undercloud and overcloud vms in GBytes vm_disk_size: "100" ################################################### # Host Nic Layouts controller_nic_layout: - nic1: Network: ControlPlane Routes: - ip_netmask: /24 next_hop: EC2MetadataIp - default: true next_hop: ControlPlaneDefaultRoute DnsServer: true - vlan2001: Network: Management VlanParent: nic1 - vlan2002: Network: Storage VlanParent: nic1 - vlan2003: Network: StorageMgmt VlanParent: nic1 - nic2: Network: External Routes: - next_hop: ExternalInterfaceDefaultRoute - nic3: Network: InternalApi Routes: - next_hop: InternalApiDefaultRoute compute_nic_layout: - nic1: Network: ControlPlane Routes: - ip_netmask: /24 next_hop: EC2MetadataIp - default: true next_hop: ControlPlaneDefaultRoute DnsServer: true - vlan2001: Network: Management VlanParent: nic1 - vlan2002: Network: Storage VlanParent: nic1 - vlan2003: Network: StorageMgmt VlanParent: nic1 - nic2: Network: External - bond0: Network: None BondingOptions: "{{ bonding_options }}" Members: 18

19 Chapter 1: Contrail Cloud Deployment Guide - name: ens7f0 primary: true - name: ens7f1 - vhost0: Network: InternalApi compute_dpdk_nic_layout: - nic1: Network: ControlPlane Routes: - ip_netmask: /24 next_hop: EC2MetadataIp - default: true next_hop: ControlPlaneDefaultRoute DnsServer: true - vlan2001: Network: Management VlanParent: nic1 - vlan2002: Network: Storage VlanParent: nic1 - vlan2003: Network: StorageMgmt VlanParent: nic1 - nic2: Network: External - bond0: Network: None BondingOptions: "{{ bonding_options }}" - vhost0: Network: InternalApi storage_nic_layout: - nic1: Network: ControlPlane Routes: - ip_netmask: /24 next_hop: EC2MetadataIp - next_hop: ControlPlaneDefaultRoute DnsServer: true - vlan2001: Network: Management VlanParent: nic1 - vlan2002: Network: Storage VlanParent: nic1 - vlan2003: Network: StorageMgmt VlanParent: nic1 - nic2: Network: External Routes: - default: true next_hop: ExternalInterfaceDefaultRoute - bond0: Network: InternalApi BondingOptions: "{{ bonding_options }}" Members: - name: ens7f0 primary: true - name: ens7f1 19

20 Contrail Cloud Deployment Guide Sample inventory.yml nodes: - name: "csgsnc050" pm_addr: " " pm_type: "pxe_ipmitool" pm_user: "ADMIN" pm_password: "ADMIN" mac: - "0c:c4:7a:81:ad:12" status: "creating" - name: "csgsnc051" pm_addr: " " pm_type: "pxe_ipmitool" pm_user: "ADMIN" pm_password: "ADMIN" mac: - "0c:c4:7a:81:a4:d6" status: "creating" - name: "csgsnc052" pm_addr: " " pm_type: "pxe_ipmitool" pm_user: "ADMIN" pm_password: "ADMIN" mac: - "0c:c4:7a:81:aa:e0" status: "creating" - name: "csgsnc053" pm_addr: " " pm_type: "pxe_ipmitool" pm_user: "ADMIN" pm_password: "ADMIN" mac: - "0c:c4:7a:81:aa:e3" status: "creating" Sample control-hosts.yml hosts: - name: "csgsnc050" ip_address: " " interface: eno1: device: "eno1" bridge: "br-eno1" br-eno1: device: "br-eno1" bootproto: "dhcp" type: "Bridge" delay: "0" br-bond0: device: "br-bond0" 20

21 Chapter 1: Contrail Cloud Deployment Guide type: "Bridge" delay: "0" br-eno2: device: "br-eno2" netmask: " " ipaddr: " " type: "Bridge" delay: "0" eno2: device: "eno2" bridge: "br-eno2" bond0: device: "bond0" type: "Bond" bridge: "br-bond0" bondingmaster: "yes" bondingopts: "mode=mode=802.3ad lacp_rate=fast updelay=1000 miimon=100" ens7f0: device: "ens7f0" slave: "yes" master: "bond0" ens7f1: device: "ens7f1" slave: "yes" master: "bond0" - name: "csgsnc051" ip_address: " " interface: eno1: device: "eno1" bridge: "br-eno1" br-eno1: 21

22 Contrail Cloud Deployment Guide device: "br-eno1" bootproto: "dhcp" type: "Bridge" delay: "0" br-bond0: device: "br-bond0" type: "Bridge" delay: "0" br-eno2: device: "br-eno2" netmask: " " ipaddr: " " type: "Bridge" delay: "0" eno2: device: "eno2" bridge: "br-eno2" bond0: device: "bond0" type: "Bond" bridge: "br-bond0" bondingmaster: "yes" bondingopts: "mode=mode=802.3ad lacp_rate=fast updelay=1000 miimon=100" ens7f0: device: "ens7f0" slave: "yes" master: "bond0" ens7f1: device: "ens7f1" slave: "yes" master: "bond0" - name: "csgsnc052" ip_address: " " interface: eno1: 22

23 Chapter 1: Contrail Cloud Deployment Guide device: "eno1" bridge: "br-eno1" br-eno1: device: "br-eno1" bootproto: "dhcp" type: "Bridge" delay: "0" br-bond0: device: "br-bond0" type: "Bridge" delay: "0" br-eno2: device: "br-eno2" netmask: " " ipaddr: " " type: "Bridge" delay: "0" eno2: device: "eno2" bridge: "br-eno2" bond0: device: "bond0" type: "Bond" bridge: "br-bond0" bondingmaster: "yes" bondingopts: "mode=mode=802.3ad lacp_rate=fast updelay=1000 miimon=100" ens7f0: device: "ens7f0" slave: "yes" master: "bond0" ens7f1: device: "ens7f1" 23

24 Contrail Cloud Deployment Guide slave: "yes" master: "bond0" Sample compute-nodes.yml compute_nodes_kernel: - name: csgsnc055 ip_address: " " compute_nodes_dpdk: - name: csgsnc054 ip_address: " " - name: csgsnc053 ip_address: " " - name: csgsnc048 ip_address: " " Sample storage-nodes.yml storage_nodes: - name: csgsnc064 ip_address: " " - name: csgsnc065 ip_address: " " - name: csgsnc066 ip_address: " " Sample appformix-nodes.yml hosts: - name: appformix-controller ip_address: " " interface: eth0: device: "eth0" ipaddr: " " netmask: " " eth1: device: "eth1" ipaddr: " " netmask: " " eth2: device: "eth2" ipaddr: " " netmask: " " 24

25 Chapter 1: Contrail Cloud Deployment Guide eth0.3001: device: "eth0.3001" vlan: "yes" ipaddr: " " netmask: " " eth0.3002: device: "eth0.3002" vlan: "yes" ipaddr: " " netmask: " " eth0.3003: device: "eth0.3003" vlan: "yes" ipaddr: " " netmask: " " 25

26 Contrail Cloud Deployment Guide 26