Page Comparison

...

                                         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>”

• Sequence in which the FQDN is sourced from Device authentication vs. from the Admin Artifact

APPC will apply sequence in which the FQDN is sourced from Device authentication vs. from the Admin Artifact.

APPC will verify if the device authentication table has only 1 entry for the given VNF type, Protocol, Action.

If yes, then APPC will not invoke the Admin Artifact to retrieve the FQDN for the Ansible server.

...

• South bound Ansible Adaptor to read the Ansible FQDN info and connect to the corresponding Ansible server cluster to send the POST request to the Ansible Rest API

APPC will enhance the South bound Ansible Adaptor to read the vnf-management-server-fqdn info and connect to the corresponding Ansible server cluster to send the POST request to the Ansible Rest API.

For all the LCM actions of the VNF’s with the Ansible Protocol, APPC will apply the following steps:

1. 1. 1. South bound Ansible Adaptor to read the vnf-management-server-fqdn info and connect to the corresponding Ansible server cluster to send the POST requests to the Ansible Rest API.
      2. For the given POST request on a VNF, if an IP address is returned by the Ansible Rest API then the Adaptor shall record the IP address and send the get results requests to the given IP address directly.
      3. For the given POST request on a VNF, if an IP address is not returned by the Ansible Rest API then the Adaptor shall send the get results requests as current BAU using the FQDN that was used for the POST request.
      4. All the steps between POST request/ response from APPC to Ansible Rest APIs shall be recorded in the logs.
      5. All the steps between Get Results request/ response from APPC to Ansible Rest APIs shall be recorded in the logs
         
         

• Sequence in which the FQDN is sourced from Device authentication vs. from the Admin Artifact

APPC will apply sequence in which the FQDN is sourced from Device authentication vs. from the Admin Artifact.

APPC will verify if the device authentication table has only 1 entry for the given VNF type, Protocol, Action.

If yes, then APPC will not invoke the Admin Artifact to retrieve the FQDN for the Ansible server.

If there are multiple records in the device authentication table then APPC will invoke the Admin Artifact to retrieve the FQDN, Cloud Owner, Cloud Region ID, and Tenant Id.

• Precedence factor on the condition for the tenant id and other attributes present in the payload

APPC will support the precedence factor on the condition for the tenant id and other attributes present in the payload.

APPC will verify If the cloud owner, cloud region id, tenant id, VNF management server FQDN (Ansible server cluster FQDN) is sent in the payload.

If yes then APPC will use the values received in the payload in order to find the appropriate VNF management server to connect for the given VNF request.

If not then APPC will use credentials as described above in "Ansible DG enhancement" and "Ansbile adaptor enhancement"

Payload example

Ref link:

1. Ansible Playbook Examples in VNF Guide.

2. Ansible Adaptor in APPC