VMware Integrated OpenStack supports ISO, VMDK, and OVA formats natively. Non-native formats such as RAW, QCOW2, VDI, and VHD are also supported after automatic conversion by the import process. The initial format of the VNF is considered for onboarding, as is the format of any additional components the VNF requires to function. Images are either able to be directly imported, or they can be converted. These formats can also be imported using the command- line.

The VMware Ready for NFV is a program where VMware and VNF vendors collaborate to ensure that the VNF is interoperable with VMware Telco Cloud Infrastructure OpenStack edition. Based on experience, VMware provides best practices guidelines to help VNF vendors in preparing their VNFs for consumption by VMware Integrated OpenStack.

CSPs expect their VNF supplier to deliver a package that is ready to be consumed by VMware Integrated OpenStack. The package must support:

  1. Autonomous VNF Life Cycle Operations. CSPs must be able to install, upgrade, and manage the VNF themselves.

  2. Compact. All components that are required to operate the VNF are packaged together. VNF Components (VNF-Cs) are clearly defined, use unique and specific names, and are included in the package.

  3. Authorized. The package provided to the customer must be verifiable. For example, an md5 hash can be used to verify that the package provided by the vendor is the same package that is installed by the CSP.

  4. Holistic. The packaged VNF must include all configuration that is required to deploy a healthy VNF. For example, if the VNF is data plane intensive, all performance-related configuration such as CPU and NUMA affinity, CPU and memory reservations must be included in the package.