Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Provision VMs on Contrail Service Orchestration Servers

 

Virtual machines (VMs) on the Contrail Service Orchestration (CSO) servers host the infrastructure services and some components.

Note

If you use a KVM hypervisor while installing a distributed CPE (Hybrid WAN) or an SD-WAN solution, you must create a bridge interface on the physical server. The bridge interface should map the primary network interface (Ethernet management interface) on each CSO server to a virtual interface before you create VMs. This bridge interface enables the VMs to communicate with the network.

Assumptions/Prerequisites:

  • Network devices (routers) must be configured with the required configurations.

  • All the physical servers where KVM VMs are provisioned must have Ubuntu 16.04.5 LTS installed.

  • All the VMs where CSO components are deployed must have Ubuntu 16.04.5 LTS OS installed.

  • Ensure that the VMs and associated resources meet the requirements as given at Minimum Requirements for Servers and VMs.

  • You must have a DNS server with high availability for the on-premise Kubernetes cluster.

  • Verify the DNS server configuration on the servers.

  • All the VMs must have SSH enabled.

  • All the VMs must be on the same subnet.

  • All the VMs can reach one another.

  • All the operations and installations must be run as root user.

  • Verify that all the VMs have the correct Fully Qualified Domain Name (FQDN).

Before You Begin

Before you begin, you must:

  • Configure the physical servers.

  • Ensure that the VMs meet the server requirements listed in Minimum Requirements for Servers and VMs.

    Each type of the CSO VM must be distributed across different servers in different racks to avoid server or top-of-rack switch failure. We recommend that you use three servers.

  • Install Ubuntu 16.04.5 LTS as the operating system for the physical servers.

Note

CSO Release 5.1.0 only supports KVM hypervisors. CSO Release 5.1.1 and later support KVM hypervisors and ESXi version 6.7 hypervisors.

Create a Bridge Interface for KVM Hypervisors

If you use a KVM hypervisor, you must create a bridge interface on the physical server that maps the primary network interface (Ethernet management interface) on each CSO server to a virtual interface before you create the VMs. The bridge interface enables the VMs to communicate with the network.

To create a bridge interface:

  1. Log in as root user on the CSO server.
  2. View the network interfaces configured on the server to obtain the name of the primary interface on the server.
    root@host:~/# ifconfig
  3. Set up the KVM host.
    * apt-get update
    * apt-get install libvirt-bin
  4. Modify the /etc/network/interfaces file to map the primary network interface to the virtual interface (br0). Note

    You must perform this step on all the servers. Address of eno2 must be changed.

    For example, use the following configuration to map the primary interface eno2 to the virtual interface br0:

  5. Navigate to the directory where the CSO .tar file has been downloaded on each of the servers and run the following scripts:
    root@host:~/Contrail_Service_Orchestration_5.1.2/ci_cd# ls -ltr setup_bms.sh

    -rwxr-xr-x 1 root root 716 Oct 10 01:57 setup_bms.sh

    root@host:~/Contrail_Service_Orchestration_5.1.2/ci_cd# ./setup_bms.sh

    You must run these scripts on all the servers.

Download the Installer for KVM Hypervisor

To download the installer for KVM hypervisors and then provision the VMs:

  1. Log in as root user to the CSO server.
  2. Download the appropriate installer package from the CSO Downloads page.

    Use the Contrail Service Orchestration installer package if you have purchased Network Service Orchestrator and Network Service Controller licenses for a distributed deployment.

  3. Expand the installer package.
    root@host:~/# tar –xvzf cso<version>.tar.gz

    The expanded package is a directory that has the same name as the installer package and contains the installation files.

  4. Run the deploy.sh command. Use the interactive script to create configuration files for the environment specific topology.

    Example output for CSO deployment on KVM hypervisor—

    root@host:~/Contrail_Service_Orchestration_5.1.2./ deploy.sh
    Note

    You must note the automatically generated password that is displayed on the console because the password is not saved in the system.

Download the Installer for ESXi Hypervisor

To download the installer for ESXi hypervisors and then provision the VMs:

  1. Download the appropriate installer package from the CSO Downloads page on any of the servers.

    Use the Contrail Service Orchestration installer package if you have purchased Network Service Orchestrator and Network Service Controller licenses for a distributed deployment.

  2. Expand the installer package.
    root@host:~/# tar –xvzf cso<version>.tar.gz

    The expanded package contains ESXi-5.1.2.tgz under /Artifacts folder.

    Extract ESXi-5.1.2.tgz package.

    The ESXi-5.1.2.tgz package contains the ubuntu-16.04-server-cloudimg-amd64.ova file and the junos-vrr-x86-64-15.1F6-S7.2.ova file.

  3. Provision the VMs (except the VRR VMs) using the ubuntu-16.04-server-cloudimg-amd64.ova file.

    The VMs must match the server requirements specified in Minimum Requirements for Servers and VMs.

    The default username is root.

  4. Provision the VRR VMs using the junos-vrr-x86-64-15.1F6-S7.2.ova file.

    Enable NETCONF for the VRR VMs.

After you provision the VMs:

  1. Assign an IP address to the logical interface(ens192) associated with the VM.

    For example:

  2. Configure a valid hostname for the VMs. and update the /etc/hostname file.

    Note

    The hostnames must start and end with an alphanumeric character. The hostnames can contain only the following special characters—hyphen (-) and period (.). The hostnames cannot contain uppercase letters.

  3. Update the /etc/hosts file.

    For example:127.0.1.1 <hostname>.example.net <hostname>

  4. Reboot the VMs.

Verify Connectivity of the VMs

From each VM, verify that you can ping the IP addresses and hostnames of all the other servers, and VMs in the CSO deployment.

Caution

If the VMs cannot communicate with all the other hosts in the deployment, the installation will fail.

Related Documentation