Using Contrail Command to Install Contrail Networking 1911 and AppFormix 3.1.9


Hello! In this video, we’ll show you how to use
the Contrail Command graphical user interface to install Contrail Networking 1911 with AppFormix
3.1.9. First, let’s get familiar with the devices
included in the installation. In a typical data center fabric, you’ll
deploy several spine and leaf devices as shown on the screen. However, for this video, we’ll represent
each of the major fabric device types with a single device: one server leaf, one border
leaf, and one lean spine. Now, the reason for this is that we want to
focus on the key servers that manage the fabric: The Contrail Networking All-In-One server,
or AIO for short, the AppFormix server, and the Contrail Command server. As I mentioned, Contrail Command is a GUI
that you use with the Contrail Cloud solution and the Contrail Enterprise Multicloud solution. It is a single point of management for the
fabric underlay, the overlay networks, and the virtual endpoints. The AIO cluster consists of several virtual
machines that run the components of Contrail Networking, such as a controller, an orchestrator,
and the compute nodes. Just so you know, we’re using OpenStack
for this installation, but we do support other orchestrators. AppFormix provides end-to-end visibility into
your multicloud environment so that you can spot potential issues and improve the operations
of your network. So, we’ve learned about the fabric devices
and the servers that control them. Now, let’s focus on installing the Contrail
Command server, and then use the Contrail Command GUI to deploy the AIO cluster and
AppFormix. Here are the hardware and software requirements
for the three servers. Make sure you setup these three servers and
connect them to your local network before continuing. A link to the server requirements, in the
TechLibrary, is available in the description below. Another helpful resource, also linked below,
is the Server Requirements and Supported Platforms page. To find the correct versions of CentOS, kernel,
and Docker software, see the Contrail Networking Supported Platforms List. On that page, look for details about the OpenStack
Queens deployment for Contrail Networking 1911. Additionally, you need access to the Contrail
Networking installation packages. For details, you can find the README Access
PDF file, and the container tag you need as part of the installation procedure. Contrail Command deploys as a pair of Docker
containers. You install Contrail Command by downloading
and running the contrail-command-deployer image, which runs in its own container and
exits when the Contrail Command installation is complete. To install the Contrail Command server, first,
log in as a root user to the server. Install and start the Docker Engine. This adds the Docker repository, and installs
and starts the Docker Community Edition version 18.06. Log in to the hub.juniper.net registry with
the credentials sent to you by the Juniper Contrail-Registry team. Use the docker pull command to retrieve the
docker image, which contains the installation package. In this case, the container tag is 1911.31. The next step is to create the command_servers.yml
file. This YAML file contains information required
by the Contrail Command server for deployments. The file is placed in the root directory on
the Contrail Command server. You’ll need to create your own configuration file for your specific deployment. Also, keep the username and password handy. They’re shown here at the end of the YAML
file and are the same ones you’ll need to login to the Contrail Command GUI. You can find the complete command servers
YAML file in the links below. Issue a docker run command to activate the
contrail-command-deployer and install Contrail Command. Use the docker logs command to track the progress
of the Contrail Command installation. At this point, you should have a successful
installation of Contrail Command. Download the AppFormix 3.1.9 Application Packages
from the Juniper Networks Download page. Copy the files to the opt/software/appformix
directory on the Contrail Command server. Also, put a copy of the AppFormix license
signature file in this same directory. Now, let’s use the Contrail Command GUI
to deploy the AIO Cluster and AppFormix. First, use a web browser to log in to the
Contrail Command GUI. Enter https://:9091. Use the username and password that you specified
earlier in the command_servers.yml file. In Step 1, Inventory, let’s add the Contrail
AIO Cluster and the AppFormix server. Navigate to Servers, click Add, and select
Detailed. For this example, let’s call the Contrail
Hostname aio-cluster. You’ll notice that the Management IP address
of 10.1.1.2 is the fabric-facing interface so Contrail can manage the fabric devices. As such, we’re using interface ens224 for
this purpose. Next, use the default credentials from the
pull-down menu. Then, click Add, in Network Interfaces to
configure each interface. Ens192 connects to your out-of-band management
network, ens224 is the fabric management interface, and ens256 is a direct link to the server
leaf. Click Create. Now, let’s use similar steps to add an AppFormix
server and configure it’s interfaces. The Hostname is appformix, and the fabric
management address is again the ens224 interface. Use the default credentials from the pull-down
menu. Then, add your Network Interfaces. Ens192 connects to your out-of-band management
network and ens224 is the fabric management interface. Click Create. We’re done configuring servers and interfaces,
so click Next. In Step 2, Provisioning Options, we’ll create
a cluster of VMs to run Contrail services. Select Contrail Enterprise Multicloud as the
Provisioning Manager, then enter the following required information. Give it a Cluster Name. Add the Container Registry information, such
as the path to the Container Registry, your Container Registry Username and Password,
and the Contrail Version found in the README file. Enter the IP address of your NTP Server.
Also, keep the username and password handy.
They’92re shown here at the end of the YAML file and are the same ones you’92ll need
to login to the Contrail Command GUI.
You can find the complete command servers YAML file in the links below.
Issue a docker run command to activate the
contrail-command-deployer and install Contrail Command.
Use the docker logs command to track the progress
of the Contrail Command installation.
At this point, you should have a successful installation of Contrail Command.
pardpardeftab720partightenfactor0
cf4 Download the AppFormix 3.1.9 Application Packages from the Juniper Networks Download
page.
Copy the files to the opt/software/cf5 appformixcf4 directory on the Contrail Command server.
Also, put a copy of the AppFormix license
signature file in this same directory.
pardpardeftab720partightenfactor0 cf2 Now, let’92s use the Contrail Command
GUI to deploy the AIO Cluster and AppFormix.
First, use a web browser to log in to the Contrail Command GUI.
Enter https://:9091.
Use the username and password that you specified
earlier in the command_servers.yml file.
In Step 1, Inventory, let’92s add the Contrail AIO Cluster and the AppFormix server.
Navigate to Servers, click Add, and select
Detailed.
For this example, let’92s call the Contrail Hostname aio-cluster.
You’92ll notice that the Management IP address
of 10.1.1.2 is the fabric-facing interface so Contrail can manage the fabric devices.
As such, we’92re using interface ens224 for
this purpose.’a0
Next, use the default credentials from the pull-down menu.’a0
Then, click Add, in Network Interfaces to
configure each interface.
Ens192 connects to your out-of-band management network, ens224 is the fabric management interface,
and ens256 is a direct link to the server leaf.’a0
Click Create.
Now, let’92s use similar steps to add an
AppFormix server and configure it’92s interfaces.
The Hostname is appformix, and the fabric management address is again the ens224 interface.’a0’a0
Use the default credentials from the pull-down
menu.’a0
Then, add your Network Interfaces.
Ens192 connects to your out-of-band management network and ens224 is the fabric management
interface.’a0
Click Create.
We’92re done configuring servers and interfaces, so click Next.
In Step 2, Provisioning Options, we’92ll
create a cluster of VMs to run Contrail services.
Select Contrail Enterprise Multicloud as the Provisioning Manager, then enter the following
required information.
Give it a Cluster Name.
Add the Container Registry information, such as the path to the Container Registry, your
Container Registry Username and Password, and the Contrail Version found in the README
file.
Enter the IP address of your NTP Server.’a0
The IP address for your Default vRouter Gateway provides the direct link from the AIO Cluster
to the server leaf in your fabric.
For Encapsulation Priority, use the pulldown menu to select VXLAN, MPLSoUDP, MPLSoGRE.
Click the Fabric Management checkbox, then
click the arrow to open Contrail Configuration.
Click Add, and enter Key Value pairs for CONTROL_NODES, PHYSICAL_INTERFACE, and TSN_NODES.
Notice these all belong to the AIO Cluster.
When you’92re done, click Next.
Steps 3 through 6 are optional, so we’92ll
jump to step 7 and assign Control Nodes.
Click on the aio-cluster arrow under Available servers to move it to Assigned Control nodes.
Notice the roles have been automatically provided
for you.
Click Next.
Now we’92ll assign the Orchestrator Nodes.
Check the Show Advanced box to customize your deployment.
Click Add under Kolla Globals and enter standard
Key Value pairs for OpenStack components.
Here, you’92ll disable haproxy and ironic, enable swift, and set a disk partition size
of 20 Gigabytes.’a0’a0
Click the aio cluster arrow to move it from Available servers to Assigned Openstack nodes
and click Next.
Let’92s assign the’a0Compute Nodes.
Once again, click the aio-cluster arrow to move it from Available servers to Assigned
Compute nodes.
Enter the server leaf Default vRouter Gateway that we’92ve used before, 10.1.11.2, and
click Next.
Now we’92ll assign the Contrail Service Nodes.
Click on the aio-cluster arrow to move it from Available servers to’a0Assigned Service
nodes.
Notice that the Default vRouter Gateway address is filled in for you automatically.
Click Next.
In Step 11, we’92ll assign AppFormix Nodes.
pardpardeftab720partightenfactor0
cf4 Add in the name of your AppFormix license.cf2
cf4 Then click the arrow of the appformix
server to move it to the Assigned Appformix Nodes.
The appFormix_platform_node role is assigned
by default.cf2
cf4 Click Next.
We’92ll skip configuring AppFormix Flows, so click Next.
pardpardeftab720partightenfactor0
cf2 So finally, we’92ve arrived at the’a0cf4 Summary screen where you can verify your entries
before starting the deployment.
The cluster entries appear at the top of the screen, and right below you can click on the
various tabs to view node entries.
If everything looks good, click Provision.
cf2 The provisioning process can take roughly an hour and a half, so be patient.
While you’92re waiting, ycf4 ou can monitor
the progress by running the docker exec CLI command on the Contrail Command server.cf2
pardpardeftab720partightenfactor0
cf4 Once the provisioning processcf2 cf4 completes,
click Proceed to Login.
The updated login screen now contains a pull-down menu that includes the Contrail cluster we
just created.
Select the cluster and log in.
At this point, Contrail Command, Contrail Networking, and AppFormix are all up and running.
Thanks for watching this video.
pardpardeftab720partightenfactor0 cf2
pardpardeftab720partightenfactor0 cf4 For further details, check out the links
below, and the Contrail Networking portion of the Juniper Networks TechLibrary.cf2

}

Leave a Reply

Your email address will not be published. Required fields are marked *