The VM for AutoVNF is deployed using boot_uas.py script provided with the UAS bundle. The script is located in the following directory:
/opt/cisco/usp/bundles/uas-bundle/tools
This script includes a number of deployment parameters for the VM. These parameters are described in the help information
pertaining to the script which can be accessed by executing the following command:
./boot_uas.py –h
The help information is provided as an appendix in this document. Refer to .
Important |
These instructions assume you are already logged on to the Onboarding Server.
|
To deploy the AutoVNF VM:
-
Navigate to the directory containing the boot_uas.py file.
cd /opt/cisco/usp/bundles/uas-bundle/tools
-
Deploy the AutoVNF VM.
./boot_uas.py --autovnf --openstack --image <image_name> --flavor <flavor_name> --net <network_name>
There are additional arguments that can be executed with this script based on your deployment scenario. Refer to for details.
Important |
Both version 2 and 3 of OpenStack Keystone APIs are supported. You can specify the desired version using the --os_identity_api_version argument with this script. For example to specify the use of version 3, add the argument --os_identity_api_version 3. The default is version 2.
|
Upon executing the script, you are prompted to enter user crendentials for performing operations within the AutoVNF VM.
-
Provide the requested information.
-
AutoVNF VM Login Password: The password for the default user account, which is named ubuntu.
-
AutoVNF API Access password for "admin": The password for the ConfD administrator user, which is named admin.
-
AutoVNF API Access password for "oper": The password for the ConfD operator user, which is named oper.
-
AutoVNF API Access password for "security": The password for the ConfD security administrator user, which is named security-admin.
-
Log on to the AutoVNF VM as ubuntu. Use the password that was created earlier for this user.
-
Become the root user.
sudo -i
-
Prepare the system.cfg file. This will serve as the Day-0 config for the VNF. Refer to Sample system.cfg File for an example configuration file.
Important |
Though administrative user credentials can be specified in clear text in the system.cfg file, it is not recommended. For security
purposes, it is recommended that you configure a secure token for the user account in the VNF configuration file and reference
that file as part of the VDU catalog pertaining to the CF using the login-credential parameter. In the system.cfg file, use the $CF_LOGIN_USER and $CF_LOGIN_PASSWORD variables as follows to call the values configured for the secure token:
configure
context local
administrator $CF_LOGIN_USER password $CF_LOGIN_PASSWORD ftp
|
-
Upload the system.cfg to the /opt/cisco/usp/uploads/ directory on the AutoVNF VM.
-
Copy the ESC scripts from the /opt/cisco/usp/uas/autovnf/vnfms/esc-scripts directory on the AutoVNF VM to the VNFM (ESC) VMs.
These are custom scripts which aid in the VNF instantiation.
-
Connect to the master VNFM (ESC) VM and copy the scripts.
cd /opt/cisco/usp/uas/autovnf/vnfms/esc-scripts
scp esc-vpc-di-internal-keys.sh <esc_user>@<master_esc_vm_address>: opt/cisco/esc/esc-scripts/esc-vpc-di-internal-keys.sh
scp esc_vpc_chassis_id.py<esc_user>@<master_esc_vm_address>: opt/cisco/esc/esc-scripts/esc_vpc_chassis_id.py
scp esc_volume_em_staging.sh <esc_user>@<master_esc_vm_address>: /opt/cisco/esc/esc-scripts/esc_volume_em_staging.sh
-
Connect to the standby VNFM (ESC) VM and copy the scripts.
scp esc-vpc-di-internal-keys.sh <esc_user>@<standby_esc_vm_address>: opt/cisco/esc/esc-scripts/esc-vpc-di-internal-keys.sh
scp esc_vpc_chassis_id.py<esc_user>@<standby_esc_vm_address>: opt/cisco/esc/esc-scripts/esc_vpc_chassis_id.py
scp esc_volume_em_staging.sh <esc_user>@<standby_esc_vm_address>: /opt/cisco/esc/esc-scripts/esc_volume_em_staging.sh
-
Confirm that the VNFM has been configured with the VIM connectors for the VNF tenants. A connector is needed for each tenant.
Refer to Sample ESC VIM Connector Configuration for an example configuration.
-
Connect to the master VNFM (ESC) VM.
-
Log on to the ConfD command line.
/opt/cisco/esc/confd/bin/confd_cli –C
-
Confirm the VIM connector configuration.
show running-config esc_system_config vim_connectors vim_connector <vim_connector_name>
If the connectors have not been configured, refer to the documentation for the appropriate version of ESC software. ESC product
documentation is available here: https://www.cisco.com/c/en/us/support/cloud-systems-management/elastic-services-controller-esc/tsd-products-support-series-home.html
Important |
The OpenStack Keystone configuration version specified for the authentication URL in the connector must match the version
used when deploying AutoVNF and the version specified in the AutoVNF configuration file.
|
-
Repeat step 9.c for each VIM connector.
Important |
If the ESC VMs are upgraded or redeployed at any time, ensure that you reload the VIM connectors on the new or upgraded ESC
VM deployment.
|
-
Prepare the AutoVNF VNFM configuration file.
This file provides the information necessary to allow AutoVNF to communicate with the VNFM (ESC).
A sample configuration file is provided for reference in Sample AutoVNF VNFM Configuration File.
Important |
The OpenStack Keystone configuration version specified in the VNFM configuration file used by AutoVNF must match the version
used when deploying AutoVNF and the version specified in the ESC VIM connector(s). Set the api-version parameter to the appropriate version type.
|
Important |
If the ESC VMs are upgraded or redeployed at any time after the AutoVNF is deployed, you may need to change the ESC endpoint
details in the AutoVNF VNFM configuration file and reload it.
|
-
Save the AutoVNF VNFM configuration file to your home directory on the AutoVNF VM.
-
Prepare the AutoVNF VNF configuration file.
This file provides the VNF configuration information used by AutoVNF during the deployment process. A sample configuration
file is provided for reference in Sample AutoVNF VNF Configuration File.
Caution |
Ensure that the network service descriptor (NSD) identified in the AutoVNF VNF configuration file is identical to the one
specified in the AutoVNF VNFM configuration file.
|
-
Save the AutoVNF VNF configuration file to your home directory on the AutoVNF VM.
-
Proceed to Activate the AutoVNF Configuration Files.