Automated CNF Rollback via Script in TCA 3.2

Products

• VMware Telco Cloud Automation

Issue/Introduction

Manually performing a rollback for Cloud Native Network Functions (CNFs) in VMware Telco Cloud Automation (TCA) 3.2 is a complex task that requires calculating repository details, configuring Helm chart metadata, and preparing specific API payloads. The cnf-rollback.sh script simplifies this by automating authentication and payload preparation.

Environment

3.2

Cause

Standard LCM operations (Upgrade, Scale, Reconfigure) may require reversion to a previous state. Manual execution is difficult because it requires extracting operation parameters and handling manual repository credentials when an extensionId is missing.

Resolution

1. Verify Prerequisites:

   • Ensure bash, curl, and jq are installed.

   • For Ubuntu/Debian: sudo apt-get install curl jq.

   • For RHEL/CentOS: sudo yum install curl jq.

2. Locate CNF Instance ID:

   • Log in to the TCA UI and navigate to Network Functions.

   • Locate the target CNF and expand the row.

   • Copy the UUID from the Id field; do not use the Descriptor ID.

3. Run the Rollback Script:

   • Make the script executable: chmod +x cnf-rollback.sh.

   • Execute the script interactively: ./cnf-rollback.sh.

   • Follow the prompts to enter the TCA Host, Instance ID, and credentials.

4. Select Rollback Operation:

   • Select from the numbered list of supported operations: Reconfigure, SCALE, Upgrade, or INSTANTIATE.

5. Repository Authentication:

   • If the script detects an empty extensionId, enter the passwords for the unique repository credentials when prompted.

Additional Information

Please refer to the attached CNF Rollback Script - User Guide.pdf for detailed step-by-step examples and troubleshooting.

This will be solved in the TCA UI 3.4.0.1