Installation Instructions 5/1531-AXB 901 33/7 Uen A

SAPC VNF Decommissioning Instruction for OpenStack
Ericsson Service-Aware Policy Controller

Contents


1 SAPC VNF Decommissioning Instruction for OpenStack Introduction

The purpose of this document is to describe how to decommission the SAPC when is deployed on top of an OpenStack based NFVI..

2 How to Decommission the SAPC using ECM

2.1 Prerequisites

  • Access to the Ericsson Cloud Manager (ECM).

  • The tenant and the Virtual Data Center (VDC), below this tenant, where the SAPC is deployed are known.

2.2 Procedure

The whole procedure consists of two phases. The first one is related to the SAPC virtual application (vApp) deletion from the cloud manager. The second phase is optional, related to the virtual networks used by the vApp deleted, which can be also removed from the system.

2.2.1 Delete the SAPC Virtual Application

Steps

  1. From the preparation server (see SAPC VNF Descriptor Generator Tool for details), a tool to delete automatically vApps in ECM, delivered as part of the Virtual Delivery Package (VDP), must be executed. Before the execution, the following information must be provided in the "ecm" and "scaling" sections of the configuration file SAPC.cfg:
    Note: Detailed description of the parameters contained on the scaling section of SAPC.cfg can be also found on the SAPC VNF Descriptor Generator Tool.
    • The name of the SAPC vApp.

      Note: In case, more than one SAPC vApps are deployed on the same VDC, a prefix is added to the name of the additional instances. This prefix must be also provided as part of the name of the vApp to delete.
    • VDC where the vApp is deployed.

    • Tenant of the VDC where the vApp is deployed.

    • ECM server hostname or IP Address.

    • User to connect with the ECM server. Password is optional, in case it is not provided in the configuration file, the user is prompted.

    The rest of the parameters of the configuration file SAPC.cfg can be ignored.
  2. The SAPC_orchestrator, located in the bin/ directory of the VDP, is the tool which deletes vApps in ECM. To execute it, the following arguments are available:
    Note: For the execution of the script from the bin directory of the VDP, only the presence of the configuration file SAPC.cfg and the --option argument with the operation to perform is needed.
    • --help or -h: if this argument is present, an explanation for every argument is shown and the execution finishes.

    • --version: if this argument is present, the version is shown and the execution finishes.

    • --option: mandatory argument. It indicates the operation to perform. Possible values are: onboarding, instantiation, scaleout, scalein, termination.

    • --cfg <CFG> or -c <CFG> : mandatory argument. It indicates where the SAPC.cfg configuration file is. The default SAPC.cfg configuration file is placed in the root directory of the VDP explained in SAPC VNF Descriptor Generator Tool.

    • --debug: optional argument for debugging and troubleshooting purposes.

    • --log <LOG> : optional argument to log the messages to a file instead of showing them into the standard output.

    Then, an example of the SAPC_orchestrator execution is:
    <PreparationServer># SAPC_orchestrator --option termination --cfg SAPC.cfg
  3. Once the ECM has received the order from the previous script, the selected vApp starts to be deleted.
  4. After some minutes, the vApp is deleted from the system and it does not appear in ECM.

2.2.2 Delete the SAPC Virtual Networks (optional)

Steps

  1. Click the Virtual Networks tab under the appropriate VDC to display a list of all the virtual networks in the VDC.
  2. Select every virtual network belonging to the SAPC and Click Delete.
    Note: The virtual networks could be left to be reused for a later SAPC deployment. Check the vnets_exist field described in the SAPC VNF Descriptor Generator Tool.

3 How to Decommission the SAPC using Atlas/Director

3.1 Prerequisites

In case of deployment based on Heat, different inputs are needed.

  • Access to the machine running Atlas/Director.

  • The tenant (project) and the credentials of a user with deletion capabilities below this tenant, where the SAPC is deployed, are known.

  • The name assigned to the stack used for the SAPC deployment is known.

3.2 Procedure

Steps

The steps to be executed using the Command Line Interface (CLI) are:

  1. Connect via SSH to the machine running Atlas/Director using the provided credentials.
  2. Execute the following command in order to delete the desired stack:
    Note: If not included in the command to be executed, it is needed to set up the following environment variables:
    • OS_AUTH_URL should point to Keystone service.

    • OS_CACERT for the verification of the server certificate.

    • OS_TENANT_NAME shall contain the name of the tenant where the stack was created.

    • OS_USERNAME: user with delete rights.

    • OS_PASSWORD: password for OS_USERNAME.

    heat stack-delete <stack_name>
  3. Run the command "heat stack-list"; the status for the stack to be removed shall be DELETE_IN_PROGRESS, until delete operation is finished and the stack does not appear any longer.