...
- 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
- Create New Server button – opens the Server Data screen for adding new server profile
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:
- Server FQDN <url>
- Port <port number>
- User name <for ansible access>
- Password <for ansible access>
- VNF type
- Protocol
- 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.
Payload example
Ref link:
- Ansible Playbook Examples in VNF Guide.
- Ansible Adaptor in APPC