...
It is assumed that a parallel cluster with updated VM images is deployed by the NFV-O and VNF-M, data is replicated from the old cluster, and then traffic is cut over. For most use cases rolling upgrades are possible. The exact procedure is use case dependent, in particular on persistent state management and data loss tolerance for the particular use case, and must be determined per individual deployment.
VNF Migration
It is assumed that VNF migration is handled much like a VNF upgrade. For some cases VIM tools may be used instead, e.g. vMotion on VMware VIMs if SR-IOV is not used.
VNF Decommissioning
It is assumed this is no more complicated than performing a graceful VNF shutdown and then deleting the VNF from the NFV-O catalogues.
Google Cloud Platform Deployment
MediationZone is not verified on Google Cloud Platform, though by deploying on Linux, treating VMs like physical servers, and using external orchestrators as outlined for a physical hardware deployment, a successful deployment with HA could be achieved.
If you are interested in using MediationZone in a Google Cloud Platform environment, contact us to discuss your particular circumstances.
Microsoft Azure Deployment
MediationZone is not verified on Microsoft Azure, though by deploying on Linux, treating VMs like physical servers, and using external orchestrators as outlined for a physical hardware deployment, a successful deployment with HA could be achieved.
If you are interested in using MediationZone in a Microsoft Azure environment, contact us to discuss your particular circumstances.
Other Public Clouds
MediationZone is not verified on other public clouds like e.g. RackSpace, though by deploying on Linux, treating VMs like physical servers, and using external orchestrators as outlined for a physical hardware deployment, a successful deployment with HA could be achieved.
Docker Deployment
MediationZone 8.0 and higher can be run on Docker, but this deployment option is considered as Limited Availability in 8.0. We are using Docker a great deal and if you are interested in using MediationZone in Docker for production use, contact us to discuss your particular circumstances.
Kubernetes/Mesos
<picture> <ref to PE>
Cloud Foundry Deployment
MediationZone can be exposed as a Service in Cloud Foundry using the Service Broker mechanism. It is not suited to running as a Cloud Foundry Application, since these can only communicate via HTTPS and WebSockets, while one of MZ’s main usages is to integrate systems using a wide range of different protocols. If you are interested in exposing MediationZone on Cloud Foundry, contact DigitalRoute to discuss your particular circumstances.