4 VNFM OpenStack Prerequisites

Following are the prerequisites for using the VNFM:

• An OpenStack instance, TRAIN version. This OpenStack must be stable for cloud-init completion and proper network connectivity.
• Fixed IP's used for stack creation must be reachable.
• Security ports must be opened from the cloud infrastructure even if the VNFM template opens the port while deployment. However, it should not be blocked from cloud.
• Network used for stack deployment must be proper and "GATEWAY IP" should be present for each network.
• One OpenStack tenant per DSR signaling VNF. The DSR network OAM VNF may share a tenant with one of the signaling VNFs, if allowed.

  Note:

  The openstack instance must have admin privileges for multi-tenant deployments.
• A DSR VM image must be in VMDK format as per GA release, named as: DSR-9.0.2.0.0-*.vmdk

  Use sections to add and organize related content if another section heading is needed. Where DSR-9.0.2.0.0-*.ova is the name of the OVA image delivered with the DSR build. This image must be accessible from every tenant where VMs are deployed.

• VNFM assumes that the following flavors are defined on each OpenStack tenant on which the VMs are deployed.

For information about VNFM installation on OpenStack, see Install and Configure the DSR VNFM.

Table 4-1 DSR Specific Flavors and Respective VNFM Types

VNFC Type	Image Name	Flavor Name	Minimum vCPUs	Minimum RAM (GB)	Minimum Disk (GB)
NOAM, DSR-DBSERVER, DSR-DR-NOAM	DSR-9.0.2.0.0.vmdk	dsr.noam (Regular Profile)	4	14	120
		dsr.noam (Large Profile)	8	14	120
SOAM		dsr.soam (Regular Profile)	4	14	120
		dsr.soam (Large Profile)	8	14	120
DA-MP		dsr.da dsr.da(Large Profile)	12	16	120
IPFE		dsr.ipfe	18	24	120
STP-MP		dsr.vstp Note: Only if using vSTP function	6	16	120
SERVICE-MP		dsr.ServiceMp Note: Only if using vSTP function	8	12	120
SBR		dsr.sbr	12	25	120
SDS-NOAM, SDS-QS, SDS-DR-NOAM, SDS-DR-QS	SDS-9.0.2.0.0.vmdk	sds.noam	4	32	350
SDS-SOAM		sds.dpsoam	4	12	175
SDS-DP		sds.dp	6	10	175
DSR-IDIHAPP	apps-9.0.2.0.0.vmdk	appl-idih	4	8	64
DSR-IDIHMEDIATION	mediation-9.0.2.0.0.vmdk	med-idih	4	8	70
DSR-IDIHDB	oracle-9.0.2.0.0.vmdk	db-idih	4	8	220
UDR	UDR-14.0.2.0.0.vmdk	EIR	18	70	400
		vMNP	32	120	800
ATS Master	ats-9.0.2.0.0.	ats.master	4	16	1024

For more information about flavor, see section DSR VM Configurations of DSR Benchmarking guide for the minimum resource requirement with respect to each VNF flavor.

Note:

To deploy a larger profile, the VM user needs to create the respective flavor in OpenStack.

Table 4-2 OpenStack VIM Connection Information

Parameter	Definition	Example
vimId	The identifier of the VIM instance. This identifier is managed by the NFVO.	"vimid"
vimType	The value of this attribute determines the structure of the "interfaceInfo" and "accessInfo" attributes, based on the type of the VIM.	"ETSINFV.OPENSTACK_KEYSTONE.V_3"
endpoint	VIM controller Identity API URI . The url representing the interface endpoint.	"https://mvl-dev1.us.oracle.com:5000/v3"
username	The username to use for access.	"******"
password	Password to verified credentials for openstack controller	"******"
userDomain	The OpenStack user domain to use for the VIM connection.	"default"
projectDomain	The OpenStack project domain to use for the VIM connection.	"******"
project	The OpenStack project to use for the VIM connection.	"*****"
region	The OpenStack region to use for the VIM connection.	"RegionOne"

VNFM adds a list of generic ports as a part of Openstack Security Groups. If traffic needs to be allowed through any other specific port, then that port must be added in Openstack Security Groups. For details about Adding a port in Openstack Security Groups, see Adding a Port in Openstack Security Groups.