In the traditional Telco operator’s network, the service (software) is often bound with dedicated hardware and platform. It is easy to upgrade the whole system on demand. With the technical benefit of virtualization, NFV framework provides a scalable container for each VNF (service software), and de-couples them from the platform and hardware (NFVI).
OPNFV community must provide some kind of mechanism to assure the operators can perform smooth upgrade of the NFVI and VIM without service interruption when a new major(full set of components with new functions) is released, or a minor version (partial set of components with bug fixed) is required. Or, at least the service would be recovered within an expected short time.
This project is aiming to identify the user requirements on smooth upgrade the NFVI and VIM from one version to another. Such as:
This project will provide a requirement document on NFVI and VIM upgrading. And it will identify the gaps from the user requirements to the approved OPNFV projects and other upstream projects.
Based on the output of this project, we may propose another project (or extend this project) on the reference design and implementation on smooth upgrade of NFVI and VIM.
Blue Prints may be generated and send to upper stream projects from this project on behalf of the OPNFV community.