Veritas NetBackup™ CloudPoint Install and Upgrade Guide

To install the extension

1. Ensure that you have downloaded the extension script cp_extension_start.sh.

   See Downloading the CloudPoint extension.

   Note:

   Do not create the authentication token yet, as it is valid only for 180 seconds.

2. If the host from which you want to install the extension is not the same host where your CloudPoint is installed, load the CloudPoint container images on the extension host (flexsnap-cloudpoint, flexsnap-listener, flexsnap-workflow, flexsnap-fluentd, flexsnap-datamover)

   The image names are in the following format:

   Example: veritas/flexsnap-cloudpoint

3. Create image tags to map the source image with the target image, so that you can push the images to the Azure container registry you created earlier in the preparation steps.

   See Preparing to install the extension on a managed Kubernetes cluster.

   Gather the following parameters beforehand:

   Parameter	Description
   container_registry_path	To obtain the container registry path, go to your container registry in Azure and from the Overview pane, copy the 'Login server'. Example: mycontainer.azurecr.io
   tag	CloudPoint image version. Example: 9.0.1.0.9129

   • To tag the images, run the following command for each image, depending on the container platform running on your host:

     For Docker: # docker tag source_image:tag target_image:tag

     For Podman: # podman tag source_image:tag target_image:tag

     Where,

     • the source image tag is: veritas/flexsnap-cloudpoint:tag>

     • the target image tag is: <container_registry_path>/<source_image_name>:<CloudPoint_version_tag>

   Example:

   # docker tag veritas/flexsnap-cloudpoint:9.0.1.0.9129 mycontainer.azurecr.io/veritas/flexsnap-cloudpoint:9.0.1.0.9129
   # docker tag veritas/flexsnap-listener:9.0.1.0.9129 mycontainer.azurecr.io/veritas/flexsnap-listener:9.0.1.0.9129
   # docker tag veritas/flexsnap-fluentd:9.0.1.0.9129 mycontainer.azurecr.io/veritas/flexsnap-fluentd:9.0.1.0.9129
   # docker tag veritas/flexsnap-workflow:9.0.1.0.9129 mycontainer.azurecr.io/veritas/flexsnap-workflow:9.0.1.0.9129
   # docker tag veritas/flexsnap-datamover:9.0.1.0.9129 mycontainer.azurecr.io/veritas/flexsnap-datamover:9.0.1.0.9129

4. Then to push the images to the container registry, run the following command for each image, depending on the container platform running on your host:

   For Docker: # docker push target_image:tag

   For Podman: # podman push target_image:tag

   Example:

   # docker push mycontainer.azurecr.io/veritas/flexsnap-cloudpoint:9.0.1.0.9129
   # docker push mycontainer.azurecr.io/veritas/flexsnap-listener:9.0.1.0.9129
   # docker push mycontainer.azurecr.io/veritas/flexsnap-fluentd:9.0.1.0.9129
   # docker push mycontainer.azurecr.io/veritas/flexsnap-workflow:9.0.1.0.9129
   # docker push mycontainer.azurecr.io/veritas/flexsnap-datamover:9.0.1.0.9129
   

5. Once the images are pushed to the container registry, execute the extension script cp_extension_start.sh that was downloaded earlier, from the host where kubectl is installed. The script can be executed either by providing all the required input parameters in one command, or in an interactive way where you will be prompted for input.

   Gather the following parameters before running the script:

   Parameter	Description
   cloudpoint_ip	Provide IP address or FQDN of the main CloudPoint host.
   target_image:tag	Target image tag created for the flexsnap-cloudpoint image in step 3. Example: 'mycontainer.azurecr.io/veritas/flexsnap-cloudpoint:9.0.1.0.9129'
   namespace	CloudPoint namespace that was created earlier in the preparation steps.
   tag_key=tag_val	tag_key and tag_val can be retrieved by using these commands: Get the name of the node: # kubectl get nodes | grep <node_name> Get the tag key=value label: # kubectl describe node <node_name> -n <namespace> | grep -i labels Output example: agentpool=cpuserpool
   secret_name	Kubernetes secret that was created earlier in the preparation steps. Example: mysecret
   fileshare_name	You can find the name of your file share in your storage account in the Azure portal. It is recommended that your storage account and the Kubernetes cluster should be in the same region Example: mysharename
   workflow_token	Authentication token created from the NetBackup Web UI - Add extension dialog. See Downloading the CloudPoint extension.

   Run the script as an executable file:

   • Permit the script to run as an executable:

     # chmod +x cp_extension_start.sh

   • Run the installation command with all the input parameters described in the above table:

     # ./cp_extension_start.sh install -c <cloudpoint_ip> -i <target_image:tag> -n <namespace> -p <tag_key=tag_val> -s <secret_name> -f <fileshare_name> -t <workflow_token>

     Example:

     # ./cp_extension_start.sh install 
     -c 10.20.xx.xxx 
     -i mycontainer.azurecr.io/veritas/flexsnap-cloudpoint:9.0.1.0.9271 
     -n cloudpoint-system 
     -p agentpool=cpuserpool 
     -s mysecret 
     -f mysharename 
     -t workflow-3q3ou4jxiircp9tk0eer2g9jx7mwuypwz10k4i3sms2e7k4ee7-.....

   Run the script as an interactive file:

   • Run the following command:

     # ./cp_extension_start.sh install

   • When the script runs, provide the input parameters as described in the above table:

   CloudPoint IP or fully-qualified domain name: 10.20.xx.xxx
   Veritas CloudPoint image repository path. Format=<Login-server/image:tag>:
   mycontainer.azurecr.io/veritas/flexsnap-cloudpoint:9.0.1.0.9255
   CloudPoint extension namespace: cloudpoint-system
   Node pool with format key=value: agentpool=cpuserpool
   Azure Fileshare Secret: mysecret
   Azure Fileshare Name: mysharename
   CloudPoint extension token:
   
   Getting CloudPoint service file ...done
   Getting CloudPoint CRD file ...done
   Azure Fileshare Secret Validation ...done
   
   Starting CloudPoint service deployment
   
   namespace/cloudpoint-system configured
   
   deployment.apps/flexsnap-cloudpoint created
   
   serviceaccount/cloudpoint-acc created
   
   clusterrole.rbac.authorization.k8s.io/cloudpoint-cloudpoint-system unchanged
   
   clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-cloudpoint-system unchanged
   
   customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com created
   
   CloudPoint service deployment ...done
   
   customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met
   
   Generating CloudPoint Custom Resource Definition object
   
   cloudpointrule.veritas.com/cloudpoint-config-rule created
   
   CloudPoint extension installation ...done
   

   Note:

   The output examples have been formatted to fit the screen.