Planning for the procedure
Background knowledge
This procedure assumes that:
-
you are installing into an existing VMware vSphere deployment which has pre-configured networks and VLANs; this procedure does not cover setting up a VMware vSphere deployment from scratch
-
you have deployed a SIMPL VM, unpacked the CSAR, and prepared an SDF.
Method of procedure
Refer to the SIMPL VM Documentation for details on the commands mentioned in the procedure. |
Step 1 - Upload SMO RVT configuration
Upload the configuration for the SMO nodes to the CDS. This will enable each SMO node to self-configure when they are deployed in the next step.
To upload configuration after creating and validating the yaml files as described in the above, run
rvtconfig upload-config -c <cds-mgmt-addresses> -t smo -i ~/yamls (--vm-version-source this-rvtconfig | --vm-version <version>)
on the SIMPL node from the resources
subdirectory of the SMO CSAR.
You can find the configuration examples here and how to do this on the configuration page.
An in-depth description of RVT YAML configuration can be found in the Rhino VoLTE TAS Configuration and Management Guide.
Deployments using SIMPL 6.7.3
Step 2 - Deploy the OVA
Run csar deploy --vnf smo --sdf <path to SDF>
.
This will validate the SDF, and generate the terraform template. After successful validation, this will upload the image, and deploy the number of SMO nodes specified in the SDF.
Only one node type should be deployed at the same time. I.e. when deploying these SMO nodes, don’t deploy other node types at the same time in parallel. |
Backout procedure
To delete the deployed VMs, run
csar delete --vnf smo --sdf <path to SDF>
.
You must also delete the MDM state for each VM.
To do this, you must first SSH into one of the MDM VMs.
Get the instance IDs by running: mdmhelper --deployment-id <deployment ID> instance list
.
Then for each SMO VM, run the following command:
curl -X DELETE -k \
--cert /etc/certs-agent/upload/mdm-cert.crt \
--cacert /etc/certs-agent/upload/mdm-cas.crt \
--key /etc/certs-agent/upload/mdm-key.key \
https://127.0.0.1:4000/api/v1/deployments/<deployment ID>/instances/<instance ID>
Verify that the deletion worked by running mdmhelper --deployment-id <deployment ID> instance list
again.
You may now log out of the MDM VM.
You must also delete state for this node type and version from the CDS prior to re-deploying the VMs.
To delete the state, run
rvtconfig delete-node-type --cassandra-contact-point <any CDS IP> --deployment-id <deployment ID>
.
--site-id <site ID> --node-type smo
(--vm-version-source [this-vm | this-rvtconfig] | --vm-version <vm_version>)
Deployments using SIMPL 6.6.x
Backout procedure
To delete the deployed VMs, run
csar deploy --vnf smo --delete
.
You must also delete the MDM state for each VM.
To do this, you must first SSH into one of the MDM VMs.
Get the instance IDs by running: mdmhelper --deployment-id <deployment ID> instance list
.
Then for each SMO VM, run the following command:
curl -X DELETE -k \
--cert /etc/certs-agent/upload/mdm-cert.crt \
--cacert /etc/certs-agent/upload/mdm-cas.crt \
--key /etc/certs-agent/upload/mdm-key.key \
https://127.0.0.1:4000/api/v1/deployments/<deployment ID>/instances/<instance ID>
Verify that the deletion worked by running mdmhelper --deployment-id <deployment ID> instance list
again.
You may now log out of the MDM VM.
You must also delete state for this node type and version from the CDS prior to re-deploying the VMs.
To delete the state, run
rvtconfig delete-node-type --cassandra-contact-point <any CDS IP> --deployment-id <deployment ID>
.
--site-id <site ID> --node-type smo
(--vm-version-source [this-vm | this-rvtconfig] | --vm-version <vm_version>)
Next Step
Follow the verification instructions here: Verify the state of the nodes and processes