In your docker capable machine, create a directory where you will store everything you will use during the installation.

Download the installer bundle (.tar.gz file) and the OVA file from cisco.com to the directory you created previously. For the purpose of these instructions, we will use the file names as "cw-na-platform-4.1.0-38-installer-pkg.tar.gz" and "cw-na-platform-4.1.0-38-release-211108.ova" respectively.

Use the following command to unzip the installer bundle:

tar -xvf cw-na-platform-4.1.0-38-installer-pkg.tar.gz

Navigate to the directory created in the previous step and use the following command to verify the signature of the installer image:

python cisco_x509_verify_release.py -e <.cer file> -i <.tar.gz file> -s <.tar.gz.signature file> -v dgst -sha512

python cisco_x509_verify_release.py3 -e <.cer file> -i <.tar.gz file> -s <.tar.gz.signature file> -v dgst -sha512

Use the following command to load the installer image file into your Docker environment.

docker load -i <.tar.gz file>

docker load -i cw-na-platform-installer-4.1.0-38-release-211108.tar.gz

Loaded image ID: sha256:4a55858a7dd9a5fed7d0d46716e4c9525333525419e5517a4904093f01b3f165

Launch the Docker container using the following command:

docker run --rm -it -v `pwd`:/data 4a55858a7dd9a5fed7d0d46716e4c9525333525419e5517a4904093f01b3f165

My Machine% docker images
REPOSITORY                                           TAG       IMAGE ID       CREATED        SIZE
cw-na-platform-installer-4.1.0-38-release-211108    <none>    4a55858a7dd9   7 days ago     276MB

Navigate to the directory with the VMware template.

Copy the template file found under /opt/installer/deployments/4.1.0/vcenter/deployment_template_tfvars to the /data folder using a different name.

Edit the template file located in the /data directory, in a text editor, adding the necessary parameters:

• Crosswork cluster information such as VM size: Use "Small" for lab deployments, otherwise enter "Large". For more information, see the storage profiles in VM Host Requirements.
• Unique Crosswork VM entries, including names, their IP addresses and node type settings.

  Note	Use a strong VM Password (8 character long, including upper & lower case letters, numbers and one special character). The VM setup will fail if a weak password is used.

• vCenter access details and credentials, along with the assignment of the named Crosswork VMs to the Data Center resources.

From the terminal window, determine the container id and copy the OVA file to the /data directory in your container.

docker ps
CONTAINER ID     IMAGE            COMMAND       CREATED         STATUS         PORTS NAMES
1bda806bbd82     4a55858a7dd9     "/bin/sh"     3 hours ago     Up 3 hours     <port-name>

docker cp {image file name} {container id} :/data

Run the installer.

./cw-installer.sh install -p -m /data/<template file name> -o /data/<.ova file>

./cw-installer.sh install -p -m /data/deployment.tfvars -o /data/cw-na-platform-4.1.0-38-release-211108.ova

Enter "yes" when prompted to accept the End User License Agreement (EULA).

Enter "yes" when prompted to confirm the operation.

Warning: Line 119: No space left for device '8' on parent controller '3'.
Warning: Line 114: Unable to parse 'enableMPTSupport' for attribute 'key' on element 'Config'.

cw_cluster_vms = <sensitive>
INFO: Copying day 0 state inventory to CW
INFO: Waiting for deployment status server to startup on 10.90.147.66. Elapsed time 0s, retrying in 30s
Crosswork deployment status available at http://{VIP}:30602/grafana.monitoring 
Once deployment is complete login to Crosswork via: https://{VIP}:30603/#/logincontroller 
INFO: Cw Installer operation complete.

In your docker capable machine, create a directory where you will store everything you will use during the installation.

Download the installer bundle (.tar.gz file) and the QCOW2 bundle (.tar.gz file) from cisco.com to the directory you created previously. For the purpose of these instructions, we will use the file names as "cw-na-platform-4.1.0-38-installer-pkg.tar.gz" and "cw-na-platform-4.1.0-38-release-211108-qcow2-pkg.tar.gz" respectively.

Use the following command to unzip the installer bundle:

tar -xvf cw-na-platform-4.1.0-38-installer-pkg.tar.gz

Navigate to the directory created in the previous step and use the following command to verify the signature of the installer image:

python cisco_x509_verify_release.py -e <.cer file> -i <.tar.gz file> -s <.tar.gz.signature file> -v dgst -sha512

python cisco_x509_verify_release.py3 -e <.cer file> -i <.tar.gz file> -s <.tar.gz.signature file> -v dgst -sha512

Use the following command to load the installer image file into your Docker environment.

docker load -i <.tar.gz file>

docker load -i cw-na-platform-installer-4.1.0-38-release-211108.tar.gz

Loaded image ID: sha256:4a55858a7dd9a5fed7d0d46716e4c9525333525419e5517a4904093f01b3f165

Launch the Docker container using the following command:

docker run --rm -it -v `pwd`:/data 4a55858a7dd9a5fed7d0d46716e4c9525333525419e5517a4904093f01b3f165

My Machine% docker images
REPOSITORY                                           TAG       IMAGE ID       CREATED        SIZE
cw-na-platform-installer-4.1.0-38-release-211108    <none>    4a55858a7dd9   7 days ago     276MB

Navigate to the directory with the CSP template.

Copy the template file found under /opt/installer/deployments/4.1.0/csp/deployment_template_tfvars to the /data folder using a different name.

Edit the template file located in the /data directory, in a text editor, adding the necessary parameters:

• Crosswork cluster information such as VM size: Use "Small" for lab deployments, otherwise enter "Large".
• Unique Crosswork VM entries, including names, their IP addresses and node type settings.

  Note	Use a strong VM Password (8 character long, including upper & lower case letters, numbers and one special character). The VM setup will fail if a weak password is used.

• Cisco CSP access details and credentials, along with the assignment of the named Crosswork VMs to the Cisco CSP host resources.

From the terminal window, unzip the QCOW2 bundle (.tar.gz file):

tar -xvf cw-na-platform-4.1.0-38-release-211108-qcow2-pkg.tar.gz

Navigate to the directory created in the previous step, and use the following command to verify the signature of the QCOW2 image:

python cisco_x509_verify_release.py -e <.cer file> -i <.tar.gz file> -s <.tar.gz.signature file> -v dgst -sha512

Run the installer.

./cw-installer.sh install -t csp -m /data/<template file name> -o /data/<qcow2.tar.gz file> -p

./cw-installer.sh install -t csp m /data/deployment.tfvars -o /data/cw-na-platform-4.1.0-38-release-211108-qcow2.tar.gz -p

Enter "yes" when prompted to accept the End User License Agreement (EULA).

Enter "yes" when prompted to confirm the operation.

Download the latest available Cisco Crosswork image file (*.ova) to your system.

With VMware ESXi running, log into the VMware vSphere Web Client. On the left navigation pane, choose the ESXi host on which you want to deploy the VM.

Choose Actions > Deploy OVF Template.

The VMware Deploy OVF Template window appears, with the first step, 1 - Select an OVF template, highlighted. Click Choose Files to navigate to the location where you downloaded the OVA image file and select it. Once selected, the file name is displayed in the window.

Click Next. The Deploy OVF Template window is refreshed, with 2 - Select a name and folder now highlighted. Enter a name and select the respective Datacenter for the Cisco Crosswork VM you are creating.

Click Next. The Deploy OVF Template window is refreshed, with 3 - Select a compute resource highlighted. Select the host for your Cisco Crosswork VM.

Click Next. The VMware vCenter Server validates the OVA. Network speed will determine how long validation takes. After the validation is complete, the Deploy OVF Template window is refreshed, with 4 - Review details highlighted.

Review the OVF template that you are deploying. Note that this information is gathered from the OVF, and cannot be modified.

Click Next. The Deploy OVF Template window is refreshed, with 5 - License agreements highlighted. Review the End User License Agreement and click the I accept all license agreements checkbox.

Click Next The Deploy OVF Template window is refreshed, with 6 - Configuration highlighted. Choose the desired deployment configuration.

Note	If Cisco Crosswork is deployed using a single interface, then Cisco Crosswork Data Gateway must be deployed using a single interface as well (only required for lab deployments).

Click Next. The Deploy OVF Template window is refreshed, with 7 - Select Storage highlighted. Choose the relevant option from the Select virtual disk format drop-down list. From the table, choose the datastore you want to use, and review its properties to ensure there is enough available storage.

Note	For production deployment, choose the Thick provision eager zeroed option because this will preallocate disk space and provide the best performance. For lab purposes, we recommend the Thin provision option because it saves disk space.

Click Next. The Deploy OVF Template window is refreshed, with 8 - Select networks highlighted. From the Data Network and Management Network drop-down lists, choose an appropriate destination network.

Click Next. The Deploy OVF Template window is refreshed, with 9 - Customize template highlighted.

1. Expand the Management Network settings. Provide information for the IPv4 or IPv6 deployment (as per your selection).

2. Expand the Data Network settings. Provide information for the IPv4 or IPv6 deployment (as per your selection).

   

   Note	Data Network settings are not displayed if you have selected the IPv4 on a Single Interface or IPv6 on a Single Interface configuration.

3. Expand the Deployment Credentials settings. Enter relevant values for the VM Username and Password.

4. Expand the DNS and NTP Servers settings. According to your deployment configuration (IPv4 or IPv6), the fields that are displayed are different. Provide information in the following three fields:

   • DNS IP Address: The IP addresses of the DNS servers you want the Cisco Crosswork server to use. Separate multiple IP addresses with spaces.

   • DNS Search Domain: The name of the DNS search domain.

   • NTP Servers: The IP addresses or host names of the NTP servers you want to use. Separate multiple IPs or host names with spaces.

   

   Note	The DNS and NTP servers must be reachable using the network interfaces you have mapped on the host. Otherwise, the configuration of the VM will fail.

5. The default Disk Configuration settings should work for most environments. Change the settings only if you are instructed to by the Cisco Customer Experience team.

6. Expand Crosswork Configuration and enter your legal disclaimer text (users will see this text if they log into the CLI).

7. Expand Crosswork Cluster Configuration. Provide relevant values for the following fields:

   • VM Type:

     • Choose Hybrid if this is one of the 3 hybrid nodes.

     • Choose Worker if this is a worker node.

   • Cluster Seed node:

     • Choose True if this is the first VM being built in a new cluster.

     • Choose False for all other VMs, or when rebuilding a failed VM.

   • Crosswork Management Cluster Virtual IP: Enter the Management Virtual IP address and Management Virtual IP DNS name.

   • Crosswork Data Cluster Virtual IP: Enter the Data Virtual IP address. and the Data Virtual IP DNS name.

   • Initial node count: Default value is 3.

   • Initial leader node count: Default value is 3.

   • Location of VM: Enter the location of VM.

   • Installation type:

     • For new cluster installation: Do not select the checkbox.

     • Replacing a failed VM: Select the checkbox if this VM is being installed to replace a failed VM.

   

Click Next. The Deploy OVF Template window is refreshed, with 10 - Ready to Complete highlighted.

Review your settings and then click Finish if you are ready to begin deployment. Wait for the deployment to finish before continuing. To check the deployment status:

1. Open a VMware vCenter client.

2. In the Recent Tasks tab of the host VM, view the status of the Deploy OVF template and Import OVF package jobs.

To finalize the template creation, select the host and right-click on the newly installed VM and select Template > Convert to Template. A prompt confirming the action is displayed. Click Yes to confirm. The template is created under the VMs and Templates tab in the vSphere Client UI.

To build the VM, right-click on the newly created template and select New VM from This Template.

The VMware Deploy From Template window appears, with the first step, 1 - Select a name and folder, highlighted. Enter a name and select the respective Datacenter for the VM.

Click Next. The Deploy From Template window is refreshed, with 2 - Select a compute resource highlighted. Select the host for your Cisco Crosswork VM.

Click Next. The Deploy From Template window is refreshed, with 3 - Select Storage highlighted. Choose Same format as source option as the virtual disk format (recommended).

If you are using a single data store: Select the data store you wish to use, and click Next.

If you are using two data stores (regular and high speed):

• Enable Configure per disk option.

• Select regular data store as the Storage setting for all the disks except disk 6.

• Select high speed (ssd) data store as the Storage setting for disk 6.

  Note	This disk must have 50 GB of free storage space.

  

• Click Next.

The Deploy From Template window is refreshed, with 4 - Select clone options highlighted. You can choose further clone options here.

Click Next. The Deploy From Template window is refreshed, with 5 - Customize vApp properties highlighted. The vApp properties from the template is already populated in this window. You need to check the following fields:

Click Next. The Deploy From Template window is refreshed, with 6 - Ready to complete highlighted. Review your settings and then click Finish if you are ready to begin deployment.

Repeat from Step 17 to Step 23 to deploy the remaining VMs in the cluster.

You can now power on Cisco Crosswork VMs to complete the deployment process. The VM selected as the cluster seed node must be powered on first, followed by the remaining VMs (after a delay of few minutes). To power on, expand the host’s entry, click the Cisco Crosswork VM, and then choose Actions > Power > Power On.

Prepare the Cisco Crosswork service image for upload to Cisco CSP:

1. Download and extract the Cisco Crosswork qcow2 build from cisco.com to your local machine or a location on your local network that is accessible to your Cisco CSP.

   The build is a tarball of the qcow2 file and the template file (.tpl).

   Note	The procedure requires ovf-env.xml file. You must create it using the template file found in the build.

2. Open the ovf-env.xml file and modify the parameters as per your installation requirements.

   Below is an example of how the ovf-env.xml file looks like:

   <?xml version="1.0" encoding="UTF-8"?>
   <Environment>
        xmlns="http://schemas.dmtf.org/ovf/environment/1"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:oe="http://schemas.dmtf.org/ovf/environment/1"
        xmlns:ve="http://www.cisco.com/schema/ovfenv"
        oe:id=""
      <PlatformSection>
         <Kind>Cisco CSP</Kind>
         <Version>2.8</Version>
         <Vendor>Cisco</Vendor>
         <Locale>en</Locale>
      </PlatformSection>
      <PropertySection>
            <Property oe:key="CWIPv4Address" oe:value="0.0.0.0"/>
            <Property oe:key="CWIPv6Address" oe:value="::0"/>
            <Property oe:key="CWPassword" oe:value="{{.CWPassword}}"/>
            <Property oe:key="CWUsername" oe:value="{{.CWUsername}}"/>
            <Property oe:key="ClusterName" oe:value="{{.ClusterName}}"/>
            <Property oe:key="CwInstaller" oe:value="True"/>
            <Property oe:key="DNSv4" oe:value="{{.DNSv4}}"/>
            <Property oe:key="DNSv6" oe:value="{{.DNSv6}}"/>
            <Property oe:key="DataIPv4Address" oe:value="{{.DataIPv4Address}}"/>
            <Property oe:key="DataIPv4Gateway" oe:value="{{.DataIPv4Gateway}}"/>
            <Property oe:key="DataIPv4Netmask" oe:value="{{.DataIPv4Netmask}}"/>
            <Property oe:key="DataIPv6Address" oe:value="{{.DataIPv6Address}}"/>
            <Property oe:key="DataIPv6Gateway" oe:value="{{.DataIPv6Gateway}}"/>
            <Property oe:key="DataIPv6Netmask" oe:value="{{.DataIPv6Netmask}}"/>
            <Property oe:key="DataVIP" oe:value="{{.DataVIP}}"/>
            <Property oe:key="Deployment" oe:value="{{.Deployment}}"/>
            <Property oe:key="Disclaimer" oe:value="{{.Disclaimer}}"/>
            <Property oe:key="Domain" oe:value="{{.Domain}}"/>
            <Property oe:key="InitMasterCount" oe:value="{{.InitMasterCount}}"/>
            <Property oe:key="InitNodeCount" oe:value="{{.InitNodeCount}}"/>
            <Property oe:key="IsSeed" oe:value="{{.IsSeed}}"/>
            <Property oe:key="K8Orch" oe:value=""/>
            <Property oe:key="ManagementIPv4Address" oe:value="{{.ManagementIPv4Address}}"/>
            <Property oe:key="ManagementIPv4Gateway" oe:value="{{.ManagementIPv4Gateway}}"/>
            <Property oe:key="ManagementIPv4Netmask" oe:value="{{.ManagementIPv4Netmask}}"/>
            <Property oe:key="ManagementIPv6Address" oe:value="{{.ManagementIPv6Address}}"/>
            <Property oe:key="ManagementIPv6Gateway" oe:value="{{.ManagementIPv6Gateway}}"/>
            <Property oe:key="ManagementIPv6Netmask" oe:value="{{.ManagementIPv6Netmask}}"/>
            <Property oe:key="ManagementVIP" oe:value="{{.ManagementVIP}}"/>
            <Property oe:key="NSOProvider" oe:value="False"/>
            <Property oe:key="NTP" oe:value="{{.NTP}}"/>
            <Property oe:key="VMType" oe:value="{{.VMType}}"/>
            <Property oe:key="corefs" oe:value="20"/>
            <Property oe:key="ddatafs" oe:value="200"/>
            <Property oe:key="logfs" oe:value="10"/>
            <Property oe:key="ramdisk" oe:value="{{.RamDiskSize}}"/>
      </PropertySection>
   </Environment>

   Note	Only one node in the cluster must have IsSeed set to True.

Upload Cisco Crosswork service image to Cisco CSP:

1. Log into the Cisco CSP.

2. Go to Configuration > Repository.

3. On the Repository Files page, Click button.

   
   

   

   
   

4. Select an Upload Destination.

5. Click Browse, navigate to the qcow2 file, click Open and then Upload.

   Repeat this step to upload ovf-env.xml file.

   
   

   

   
   

   After the file is uploaded, the file name and other relevant information are displayed in the Repository Files table.

Create Cisco Crosswork VM:

1. Go to Configuration > Services.

2. On the Service page, click button.

3. Check Create Service option.

   The Create Service Template page is displayed.

4. Enter the values for the following fields:

   Field	Description
   Name	Name of the VM.
   Target Host Name	Choose the target host on which you want to deploy the VM.
   Image Name	Select the qcow2 image.

5. Click Day Zero Config.

   
   

   

   
   

   In the Day Zero Config dialog box, do the following:

   1. From the Source File Name drop-down list, select a day0 configuration file i.e., the ovf-env.xml file that you modifed and uploaded earlier.

   2. In the Destination File Name field, specify the name of the day0 destination text file. This must always be "ovf-env.xml".

   3. Click Submit.

6. Enter the values for the following fields:

   Field	Description
   Number of CPU Cores	Small: 8 Large: 12
   RAM (MB)	Small: 49152 Large: 98304

7. Click VNIC.

   
   

   

   
   

   In the VNIC Configuration dialog box, perform the following:

   Note	The VNIC Name is set by default.

   1. Select the Interface Type as Access.

   2. Select the Model as Virtio.

   3. Select the Network Type as External.

   4. Select Network Name:

      For VNIC...	Select...
      vnic0	Eth0-1
      vnic1	Eth1-1

   5. Select Admin Status as UP.

   6. Click Submit.

   7. Repeat Steps i to vi for vNIC1 and vNIC2.

   After you have added all three vNICs, the VNIC table will look like this:

   
   

   

   
   

8. Expand the Service Advance Configuration and for Firmware, select uefi from the drop-down.

   Check the Secure Boot checkbox.

   
   

   

   
   

9. Click Storage. In the Storage Configuration dialog box, fill the following fields:

   Field	Description
   Name	Name of the storage. This is specified by default.
   Device Type	Select Disk.
   Location	Select local.
   Disk Type	Select VIRTIO.
   Format	Select QCOW2.
   Mount image file as disk?	Leave this unchecked.
   Size (GB)	Enter the disk size (5 for Standard and 500 for Extended.)

   
   

   

   
   

   Note	You have to configure 3 disks of different sizes: Disk 0: 10 GB Disk 1: 400 GB Disk 2: 50 GB

   When you have completed the storage configuration, click Submit.

10. Click Deploy.

    
    

    

    
    

    You will see a similar message once the service has successfully deployed. Click Close.

Repeat Step 1 to Step 3 for each VM in the cluster.

Deploy Cisco Crosswork VM:

1. Go to Configuration > Services.

2. In the Services table, click the console icon under Console column for the Cisco Crosswork VM you created above.