• Manage Accounts
  • Add a Resource Orchestrator Account
  • Add a VIM Account
  • Add an SDN Account
  • Add a VNFM Account
  • Add a Config Agent Account
  • Update or Remove an Account

Add a VNFM Account

The topics in this section describe how to instantiate RIFT.ware on an existing Or-VNFMSoftware defined networking is a computer networking approach that lets network administrators manage network services through abstraction of lower-level functionality. SDN addresses the challenge that the static architecture of traditional networks does not support the scalable, dynamic computing and storage needs of data center environments. SDN decouples the control plane (system that decides where traffic is sent) from the data plane (underlying systems that forward traffic to the selected destination). account.

1. Sign in to the Launchpad Dashboard and click ACCOUNTS.

   

2. Under ACCOUNT TYPE, choose VNFM and click CREATE ACCOUNT.

3. Add the unique VNFM Account Name*.

4. Under SELECT ACCOUNT TYPE, click Or Vnfm.

   

5. Under Account Details, provide the following information (fields with * are required):

   • SNVFM TYPE* – Type of the Or-Vnfm complaint sVNFM.

   • HOST* – Hostname or IP address of the sVNFM.

   • PORT* – Port of the sVNFM.

   • API ROOT* – Root that is used to configure the sVNFM for communication to NFVO.

   • TOKEN – Optional token field that allows a user to configure API access tokens.

   • TOKEN URI – Complete URI for obtaining the OAuth2.0 token.

   • REVOKE URI – URI where the revoke token request will be sent.

   • CLIENT ID – OAuth2.0 client-id for RIFT. The sVNFM server should be configured with this ID to authenticate RIFT as a client for obtaining the token.

   • CLIENT SECRET – OAuth2.0 client-secret for RIFT. This acts as the client for the sVNFM.

   CUSTOMIZATION – Choose yes or no for the below customization options to determine if the sVNFM supports external cp creation, notifications and async grant response.

   • HTTPS SUPPORT

   • SSL VERIFY CERTIFICATE – If HTTPS SUPPORT is set to Yes and CA certified SSL certificates are installed then select Yes. Otherwise, select No.

   • EXT CP CREATION SUPPORT – Select Yes if the VNFM account supports the creation of external connection points.

   • NOTIFICATION SUPPORT

   • PER VNF NOTIFICATION

   • ASYNC GRANT RESPONSE SUPPORT

     Note: The default wait time is 120 seconds.

   NFVO CONFIG

   • USER* – Name of the user that the sVNFM uses to send requests to the NFVO.

   • PASSWORD* – Password for the above user.

     Note: The above user must be pre-configured in RIFT.ware with the minimum access rw-project-mano:vnfm-admin role.

6. Carefully check your entiries and click SAVE.

   

   

At the time of instantiation, the sVNFM account needs to be selected to manage an associated VNF. See the Configuration parameters section in the Create and Instantiate a Network Service section to configure the descriptor details.