CUDB VNF Lifecycle Management

Contents

1Introduction
1.1Purpose and Scope
1.2Revision Information
1.3Target Groups
1.4Typographic Conventions
1.5Prerequisites
1.5.1Hardware and Software
1.5.2Configuration Files
1.5.3Other Requirements

2
Onboarding

3
Procedures
3.1Instantiate vCUDB System
3.1.1Preparation
3.1.2Instantiate vCUDB VNF
3.2Terminate vCUDB System
3.2.1Terminate vCUDB VNF

4
Troubleshooting

Glossary

Reference List

1   Introduction

This document describes system administration tasks performed in the Virtualized Network Function (VNF) Lifecycle Manager (VNF-LCM). The VNF-LCM provides a workflow execution environment and a web-based application for managing VNF lifecycle procedures.

The workflows are ordered sequences of steps for automating common use cases of the VNFs. A workflow provides a means to orchestrate simple and complex sequences of manual or automated tasks.

1.1   Purpose and Scope

This document covers the following workflow-based lifecycle management procedures:

All manual preparation steps that must be executed by Ericsson personnel are out of the scope of this document. See Section 1.5 for more information.

The Instantiate vCUDB system is not applicable for vCUDB system expansions.

Note:  
A Virtualized CUDB node is referred to as a vCUDB VNF instance throughout the document.

1.2   Revision Information


Rev. A
Rev. B
Rev. C

Other than editorial changes, this document has been updated as follows:

1.3   Target Groups

This document is intended for system administrators operating vCUDB systems.

1.4   Typographic Conventions

Typographic conventions can be found in the following document:

1.5   Prerequisites

This section describes the prerequisites that must be fulfilled before executing any of the workflows.

Ericsson personnel must execute all initial steps included in the manual procedures to provide system preparation and configuration files needed to run the workflow-based lifecycle management procedures.

1.5.1   Hardware and Software

The following virtual and physical hardware and software are required:

1.5.2   Configuration Files

1.5.2.1   Instantiate Configuration Files

Contact Ericsson personnel to obtain the following files, after all initial steps included in the installation instruction for vCUDB are executed:

1.5.3   Other Requirements

Contact Ericsson personnel regarding the following aspects:

2   Onboarding

This section describes how to prepare for workflow-based VNF operations using VNF-LCM. Performing this procedure is a prerequisite for lifecycle operations.

Execute the following commands on the VNF-LCM Services Virtual Machine (VM):

  1. Connect to VNF-LCM:

    ssh cloud-user@<VNFLAF-services_ip>

  2. Copy the CUDB Workflow pack CUDB_VNFLCM_WORKFLOWS-CXP9040847.tar file into /home/cloud-user directory.
  3. Decompress the CUDB Workflow pack CUDB_VNFLCM_WORKFLOWS-CXP9040847.tar

    [cloud-user@vnflaf-services ~]$ tar -xvf CUDB_VNFLCM_WORKFLOWS-CXP9040847.tar

  4. Install the CUDB Workflow pack:
    1. Switch to root user on vnflaf-services VM:

      [cloud-user@vnflaf-services ~]$ su – root

      [root@vnflaf-services ~]#

    2. Verify that the pack is not installed, by running the list command:

      rpm -qa |grep ERICvCUDB

    3. Uninstall the previous version, if there is one, and take the input data from the previous printout:

      # wfmgr bundle uninstall --package=<Name> --version=<Version>

    4. To install the Workflow pack, run the install command. The rpm file is located in the /home/cloud-user folder by default.

      # wfmgr bundle install --package=/home/cloud-user/<workflow_bundle_rpm_file>

      The expected output must be similar to the below example:

      -----------------------------------------------------------------------------------------------------------

package_name                         | pre_install   | install    | post_install    |             message |

------------------------------------------------------------------------------------------------------------

| ERICvCUDB_CXP9035445-1.9.20-1.noarch.rpm |   success   | success |   success    | package installation successful |

------------------------------------------------------------------------------------------------------------

      For more information on the output of the command, go to /var/log/wfmgr-cli-log/logfile.log.

For more information on installing workflows, refer to the Workflow Bundle Administration section of VNF-Lifecycle Manager System Administration Guide, Reference [5] document in the OSS-RC documentation.

3   Procedures

This section describes how to perform LCM operations. VNF-LCM procedures use workflow instances.

Launch VNF-LCM from web browser:

http://<vnflaf-services_ip>/index.html#workflows

Figure 1 shows the example of VNF Lifecycle Management, where the workflow is shown.

Figure 1   Workflow Overview

Note:  
If vCUDB was instantiated without using workflows, a tag must be defined manually in the stack, executing the following steps:
  • Select the appropriate stack for updating:
    source <openrc>
heat stack-list

  • Update the tag:
    heat stack-update -x --tags "vCUDB" <stack_name>


3.1   Instantiate vCUDB System

This section describes how to instantiate a VNF using VNF-LCM.

This workflow can be used to install a vCUDB node. To install a vCUDB system, this workflow must be executed several times, one for each VNF comprising the vCUDB system. Instantiations must be launched consecutively without waiting for one to finish before launching the next one.

Note:  
If a vCUDB system consists of more than 10 vCUDB VNFs, once the instantiations are finished, add multiple SITE_VIP IPs in a live CUDB node.

3.1.1   Preparation

The following configuration files for one vCUDB system must be available:

All the previous files must go under /vnflcm-ext/backups/workflows/cudbvnfd directory.

Note:  
Remember that all files must have permission to be executed by jboss at least. If it is not the case, change it as follows:

cd /vnflcm-ext/backups/workflows/cudbvnfd
chown -R jboss_user:jboss *


The final structure directory is created manually as shown in Figure 2.

Figure 2   Final Structure Directory

:

Note:  
Different vCUDB systems can be defined. Select one during instantiation of a VNF. Moreover, one vCUDB system consists of one or several VNFs, that is, CUDB nodes.

All configuration files must be placed manually in the corresponding directories.

3.1.2   Instantiate vCUDB VNF

3.1.2.1   Start a New Instance

  1. In the VNF-LCM Workflows screen, select Instantiate vCUDB VNF and click Start a New Instance.
  2. Instance Name field is filled out, click Submit.

  3. Select the newly-created workflow from the Instance with User Tasks panel, and click on the man icon.
  4. On the Workflow Instance screen, add VNF Name, select VNF descriptor ID to instantiate, and click Submit.

    The Select VNF descriptor ID field displays VNF configurations available for instantiation in the /vnflcm-ext/backups/workflows/cudbvnfd/ directory.

  5. On the Get Instance Configuration screen, select a VNF configuration to instantiate, and click Submit.

    The Select Configuration for the VNF instance field displays VNF configurations available for instantiation in the /vnflcmext/backups/workflows/cudbvnfd/vCUDB_1/configurations directory.

    Refresh the web page.

  6. On the Select VIM screen, select a VIM, and click Submit.

  7. On the Select Tenant screen, select a Tenant, and click Submit.

Result: On the Workflow Instance screen, click on Workflow Diagram and Workflow Log to see the progress.

Note:  
Refresh the web page from time to time.

3.1.2.2   Execute Steps

The workflow log shows the ongoing execution steps. The expected progress information output must be similar to the below example:

  1. Select VIM Info.
  2. Authenticate Cloud.
  3. Create Stack.
  4. Wait for LDE nodes.
  5. Wait for LDE nodes.
  6. Wait for CMW status OK.
  7. Regenerate cluster.conf.
  8. Execute PartTool.
  9. Copy runtime.
  10. CudbInstall, first step.
  11. Reconfigure Evip.
  12. CudbInstall, second step.
  13. Configure SnmpV3.
  14. Configure dscp.
  15. CudbInstall, third step.
  16. Configure SNMPV2.
  17. Restart services.
  18. Set environment variables.
  19. Check state.
  20. Get CudbSdpInfo.
  21. Initialize Database (DB).
  22. Order maintenance.
  23. PrepareStore in DB.
  24. Order ready in DB.
  25. Restart LdapFes.
  26. ApplyInitialConfig.
  27. ApplyInitialConfigC2L.
  28. Check status.
  29. Run CudbSwBackup.
  30. Wait for remote node installation.
  31. Run CudbRemoteTrust.
  32. Start DB replication.
  33. Add fixed entries.

3.2   Terminate vCUDB System

This section describes how to terminate a VNF using VNF-LCM.

This workflow can be used to decommission a vCUDB system and free the resources by executing it consecutively on each VNF comprising the vCUDB system.

3.2.1   Terminate vCUDB VNF

Continue with this procedure only if the VNF to be terminated is instantiated using the VNF-LCM:

  1. In the VNF-LCM Workflows screen, select Terminate vCUDB VNF, and click Start a New Instance.
  2. Instance Name field is filled out, click Submit.
  3. Select the newly-created workflow from the Active Instances panel and click on the man icon.

    Result: Traffic stops after VNF is terminated. On the Workflow Instances screen, click on Workflow Diagram and Workflow Log to see the progress.

    Note:  
    Refresh the web page.

  4. On the Select VIM screen, select a VIM, and click Submit.

  5. On the Select Tenant screen, select a Tenant, and click Submit.

  6. On the Workflow Instances screen, select the VNF to terminate, and click Submit.

    Forceful termination: If VNF is forcefully terminated, all ongoing traffic will be lost. This option must be confirmed on the next screen.

    Result: The VNF instance is terminated. On the Workflow Instances screen, click on Workflow Diagram and Workflow Log to see the progress.

    Note:  
    Refresh the web page.

4   Troubleshooting

If the workflow execution is unsuccessful, see the following options for more information on the cause of failure:


Glossary

For the terms, definitions, acronyms and abbreviations used in this document, refer to CUDB Glossary of Terms and Acronyms, Reference [1].


Reference List

CUDB Documents
[1] CUDB Glossary of Terms and Acronyms, 0033-HDA 104 03/10
ENM CPI Library References
[2] VNF-LCM Installation Instructions, 1/1531-CNA 403 3313
[3] ENM Configuration System Administration Guide, 1/1543-AOM 901 151-1
OSS-RC CPI Library References
[4] VNF-LCM CEE/Openstack Installation Instructions, 1/153 72-APR 901 0578
[5] VNF-Lifecycle Manager System Administration Guide, 1543-APR 901 0578


Copyright

© Ericsson AB 2016-2018. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    CUDB VNF Lifecycle Management