Installing the CloudPoint extension on Azure (AKS)
Before you install the CloudPoint extension:
To install the extension
- Download the extension script
nbu_cloudpoint_extension.tar.See Downloading the CloudPoint extension.
Note:
Do not create the authentication token yet, as it is valid only for 180 seconds.
- 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 - Create image tags to map the source image with the target image, so that you can push the images to the Azure container registry.
See Preparing to install the extension on a managed Kubernetes cluster (AKS) in Azure.
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.iotag
CloudPoint image version.
Example:
9.0.1.0.9129To 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
- 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
- Once the images are pushed to the container registry, execute the extension script
cp_extension.shthat 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_keyandtag_valcan 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=cpuserpoolstorage_class
Kubernetes storage class that was created earlier in the preparation steps.
Example:
cloudpoint-scSize in GB
Volume size to be provisioned as per your scaling requirements.
workflow_token
Authentication token created from the NetBackup Web UI - Add extension dialog.
Note:
While deploying CloudPoint Kubernetes extension, create a storage class and provide it as an input to the CloudPoint extension installation script. By default file properties are open, hence it is recommended to create storage class by providing custom attributes in order to maintain the file/folder permissions created on extension under
/cloudpointdirectory. For more information, see Create a storage class section of the Azure product documentation.Run the script as an executable file:
Permit the script to run as an executable:
# chmod +x cp_extension.sh
Run the installation command with all the input parameters described in the above table:
# ./cp_extension.sh install -c <cloudpoint_ip> -i <target_image:tag> -n <namespace> -p <tag_key=tag_val> -f <storage_class> -t <workflow_token>
Example:
root@access-vm2-dnd:/home/cpuser/cp_ext# ./cp_extension.sh install Veritas CloudPoint image repository path. Format=<Login-server/image:tag>: cpscale1.azurecr.io/veritas/flexsnap-cloudpoint:10.0.0.0.9808 CloudPoint extension namespace: ext CloudPoint IP or fully-qualified domain name: 10.244.63.154 Node group/pool label with format key=value: agentpool=extpool1 Storage class name: nbux-sc Size in GB : 100 CloudPoint extension token: This is a fresh NetBackup CloudPoint Extension Installation Starting CloudPoint service deployment customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com unchanged serviceaccount/cloudpoint-acc unchanged clusterrole.rbac.authorization.k8s.io/cloudpoint-ext unchanged clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-ext unchanged deployment.apps/flexsnap-cloudpoint created CloudPoint service deployment ...done customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met Generating CloudPoint Custom Resource Definition object Waiting for deployment "flexsnap-cloudpoint" rollout to finish: 0 of 1 updated replicas are available... deployment "flexsnap-cloudpoint" successfully rolled out cloudpointrule.veritas.com/cloudpoint-config-rule created CloudPoint extension installation ...done root@access-vm2-dnd:/home/cpuser/cp_ext# kubectl get pods -n ext NAME READY STATUS RESTARTS AGE flexsnap-cloudpoint-d8fb97c49-swp7v 1/1 Running 0 5m53s flexsnap-fluentd-b6vxz 1/1 Running 0 5m40s flexsnap-fluentd-collector-867c9cf776-q58bw 1/1 Running 0 5m40s flexsnap-listener-6f9f5cf7fd-9bsm4 1/1 Running 0 5m40s
Run the script as an interactive file:
Run the following command:
# ./cp_extension.sh install
When the script runs, provide the input parameters as described in the above table:
Veritas CloudPoint image repository path. Format=<Login-server/image:tag>: cpscale1.azurecr.io/veritas/flexsnap-cloudpoint:10.0.0.0.9808 CloudPoint extension namespace: ext CloudPoint IP or fully-qualified domain name: 10.244.63.154 Node group/pool label with format key=value: agentpool=extpool1 Storage class name: nbux-sc Size in GB : 100 CloudPoint extension token: This is a fresh NetBackup CloudPoint Extension Installation Starting CloudPoint service deployment customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com unchanged serviceaccount/cloudpoint-acc unchanged clusterrole.rbac.authorization.k8s.io/cloudpoint-ext unchanged clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-ext unchanged deployment.apps/flexsnap-cloudpoint created CloudPoint service deployment ...done customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met Generating CloudPoint Custom Resource Definition object Waiting for deployment "flexsnap-cloudpoint" rollout to finish: 0 of 1 updated replicas are available... deployment "flexsnap-cloudpoint" successfully rolled out cloudpointrule.veritas.com/cloudpoint-config-rule created CloudPoint extension installation ...done
Note:
The output examples have been formatted to fit the screen.
This concludes the CloudPoint extension installation on a managed Kubernetes cluster (in Azure cloud).
To verify that the extension is installed successfully:
Verify that the success message is displayed at the command prompt.
Verify that the extension is listed on the NetBackup Web UI.
Go to Cloud > CloudPoint Servers tab > click Advanced settings > go to CloudPoint extensions tab and verify.
Run the following command and verify that there are four pods, namely,
flexsnap-cloudpoint-xxx, flexsnap-fluentd-xxx, flexsnap-listener-xxx, flexsnap-fluentd-collector-xxx, flexsnap-datamover-xxxxin Running state:# kubectl get pods -n <namespace>
Example: # kubectl get pods -n cloudpoint-system