Page Comparison

In ONAP community, using ansible server to configure VNF is more popular now. As of Casablanca release, APPC has provided one single ansible server configuration functionality. In Dublin, APPC will allow multiple ansible server end points for routing life cycle command (see LCM API for more details). In order to support this new function. APPC will be enhancing in several adapators, database as well as CDT GUI. This page describes how to implement, how to use this feature, and some sample requests/response will be shown.

Design

Currently APPC directs Life Cycle commands to one and only one ansible server. This feature will enhance APPC to allow multiple ansible server end points to be defined within APPC. This will allow APPC to route life cycle commands to additional Ansible servers (active-active).

Database enhancement

A new table will be added for storing admin artifact:

...

{
  "fqdn-list": [
    {
      "vnf-management-server-fqdn": "fqdn-value1 url:port",
      "cloud-owner-list": [
        {
          "cloud-owner": "xxx3.0",
          "region-id-list": [
            {
              "region-id": "san4a",
              "tenant-id-list": [
                "tenantuuid1",
                "tenantuuid2"
              ]
            },
            {
              "region-id": "san4b",
              "tenant-id-list": [
                "tenantuuid1",
                "tenantuuid2"
              ]
            }
          ]
        },
        {
          "cloud-owner": "nc1.0",
          "region-id-list": [
            {
              "region-id": "san4a",
              "tenant-id-list": [
                "tenantuuid3",
                "tenantuuid4"
              ]
            }
          ]
        }
      ],
      "description": "fqdn for east zone vUSP Production",
      "username": "albino attuid",
      "create-date": "",
      "modify-username": "",
      "modify-date": ""
    },
    {
      "vnf-management-server-fqdn": "fqdn-value2 url:port",
      "cloud-owner-list": [
        {
          "cloud-owner": "xxx3.0",
          "region-id-list": [
            {
              "region-id": "san4a",
              "tenant-id-list": [
                "tenantuuid5",
                "tenantuuid6"
              ]
            },
            {
              "region-id": "san4b",
              "tenant-id-list": [
                "tenantuuid5",
                "tenantuuid6"
              ]
            }
          ]
        },
        {
          "cloud-owner": "nc1.0",
          "region-id-list": [
            {
              "region-id": "san4a",
              "tenant-id-list": [
                "tenantuuid7",
                "tenantuuid8"
              ]
            }
          ]
        }
      ],
      "description": "fqdn for east zone vUSP E2E",
      "username": "takacho",
      "create-date": "",
      "modify-username": "",
      "modify-date": ""
    }
  ]
}

CDT GUI enhancement

 The following table lists screen objects is for the CDT GUI. 

...

• new buttons under Admin tab:
  
  • Create New Server button – opens the Server Data screen for adding new server profile
    

    Clicking the CREATE NEW SERVER button on the default screen takes the user to this Server Data to enter data for a new server profiles.

    These fields are not user editable.

    -          Creator – the user ID when the server profile was first created.  Once it is set during initial server profile creation, this value will not be changed.

    -          Date Created – date the server profile was created.  Once it is set during initial server profile creation, this value will not be changed.

    -          Modifier – Empty during initial profile creation

    -          Modified Date – Empty during initial profile creation

  • View/Edit button – opens the Server Data screen for editing the existing server profile
    

    The Configuration Server screen allows user to edit existing Ansible profiles.  CDT retrieves the server profile data and display on in the appropriate fields.

    These fields are not user editable.

    -          Creator – the user ID when the server profile was first created.  Once it is set during initial server profile creation, this value will not be changed.

    -          Date Created – date the server profile was created.  Once it is set during initial server profile creation, this value will not be changed.

    -          Modifier – user ID of the server profile was last modified and saved to APPC database.

    -          Modified Date – date of the server profile was last modified and saved to APPC database.

  • Download All To PC button – saves the Admin artifact to an file on the local PC
  • Save All To APPC button – save Admin artifact to APPC database in JSON format
    Save Admin Artifact in APPC Database
  • Arrow symbols next to column heading – sort the data by the specific column

Runtime enhancement

• APPC will support saving of the Admin Artifact in the APPC Database – name the artifact as admin artifact.
  
  

• APPC will provide a script to support the environment specific data in the device authentication table

  APPC Runtime will provide enhancement to the authentication util tool for the VNFs with the Ansible protocols  to support the maintenance of the user name and password in the device authentication table:

  1. Server FQDN <url>
  2. Port <port number>
  3. User name <for ansible access>
  4. Password <for ansible access>
  5. VNF type
  6. Protocol
  7. Action

  Validation: For the Ansible Protocol, the Server FQDN/ URL & Port shall be required along with the VNF type, Action, Protocol, User Name and Password.

  For the VNF’s with the Ansible protocol, APPC shall allow to store multiple records of a VNF type with different action using 1 FQDN as well as multiple records for a VNF type and its actions using a different FQDN.

...

                                         ii.    If the matching Tenant-id is not found, then APP-C will error out – “vnf-management-server-fqdn not found for the <PROTOCOL> server for the given Tenant - <tenant-id> of the VNF instance <VNF instance name>”

Payload example

Ref link:

1. Ansible Playbook Examples in VNF Guide.

2. Ansible Adaptor in APPC