Adding VNF Managers
Procedure
Resource Designer allows a service provider to add a
new VNF manager, including third-party VNF manager plug-in information,
from the Designs page.
To clone a VNF package design:
- Click Home > Requests. You see
the Requests page and can view the number of open requests that you
created to design a VNF package.
- Select Begin from the appropriate open VNF
request wizard.
The Basic VNF Information page appears.
- Click Add VNF Manager.
The New VNF Manager wizard appears.
- Complete the configuration according to the guidelines
provided in Table 15.
- Click Save. If you want to discard your changes,
click Cancel instead.
Table 15: Add VNF Manager
Field | Description |
|---|
VNF Manager Name | Select the VNF configuration manager. A VNF manager represents
plug-in information, which includes plug-in type and name. Example: JunosSpace |
Username | Specify the username that you configured for the VNF
manager. |
Password | Specify the password that you configured for the VNF
manager. You can choose a password that is at least eight characters
long and contains characters from at least three of the following
four character classes: uppercase letters, lowercase letters, numbers
(0 through 9), and special characters. |
Plug In | Select the plug-in type. |
Built-In | PlugIn Name—Specify the built-in plug-in
name. Example: viptables |
External Plugin | PlugIn Name—Specify the python VNF manager
plug-in name, which is used to provide additional features on top
of the existing built-in VNF manager. The naming convention of the
package name is <Vendor><VNFM Name><Version>, and this can
be installed through the PIP tool. Display Name—Specify the display name
for the VNF manager. Description—Enter a description for your
VNF manager. Make this description as clear and useful as possible
for all administrators. Vendor—Specify the vendor name that you
want the external plug-in to support. EMS Name—Specify an EMS name for the
EMS instance that manages the VNF instances instantiated from the
VNF package. Each POP is associated with an EMS instance to manage
instances instantiated in the POP. The same EMS instance is shared
by multiple POPs or dedicated EMS instances for each POP, and the
EMS name is used to find the right EMS instance to manage the VNF
instances in a specific POP. Example: Junos Space 15.1 and Versa Director 1.1.
|
Related Documentation
Help us to improve. Rate this article.
Feedback Received. Thank You!