...
This deployment means that MediationZone is deployed as a VNF in an NFV Infrastructure, provided by an NFV-I vendor.<picture>
...
NFV deployments can be just as varied as non-NFV deployments, and it is not simple to capture every possible MediationZone product in a single diagram. The main difference from MediationZone’s perspective compared to the previously mentioned virtual deployment options is integration with the NFV MANO layer. MediationZone Common O&M APIs are used by the VNF Manager to collect, deploy, instantiate, scale and shutdown metrics.
...
MediationZone is assumed to be delivered as a VM image in QCOW2 format. DigitalRoute assumes that a basic Linux image is provided by the customer, complying with customer environment-specific OS storage, networking, hardening and configuration policies, on which DigitalRoute then installs MediationZone, creating a new image which is the deliverable from DigitalRoute. A deployment descriptor containing topology information is also part of the VNF delivery.<picture>
...
MediationZone normally comes with two common images, one for CZ (Platform) and one for EZ (EC/ECSA/SC) VNFC types. However, when circumstances merit it multiple image types can be delivered – e.g. for deployments where CouchBase is part of DZ, or GlusterFS is used. These images do not contain any site-specific information, but must be configured during image bootstrapping using the NFV Infrastructure’s bootstrapping mechanisms. These are environment-specific and must be clarified during an implementation project.
...