Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
According to the use cases #1, #2, #3, #5, #6, #7, #8, #9 described in the [[http://www.etsi.org/deliver/etsi_gs/nfv/001_099/001/01.01.01_60/gs_nfv001v010101p.pdf|ETSI GS NFV 001]] and the architecture framework in [[http://www.etsi.org/deliver/etsi_gs/nfv/001_099/002/01.01.01_60/gs_nfv002v010101p.pdf|ETSI GS NFV 002]], the NFV cloud will be geographically distributed in multi-site, and multiple VIM instances may be deployed. And the NFV cloud will also co-exist with the non-virtualized traditional telecom network, as illustrated in the following picture. 

{{ :requirements_projects:multisite_vnf_pnf.png?700 |}}

In this project, we will focus on OpenStack as the VIM. The project is to identify the gaps and requirements for the OpenStack to support multi-site NFV cloud scenario, where VNFs deployed in multiple OpenStack instances and co-work with PNFs together. There are lots of issues need to be addressed:
  * What’s the requirement for Neutron to support VNF to VNF, VNF to PNF networking mode in multi-site, L2 or L3? Through flat network or project level isolated network? With or without tunneling?  etc.
  * Should OpenStack help to provide VNF cross site high availability / load balance / disaster recovery / backup / restoration / migration?
  * Should OpenStack to support VNF image replication in multi-site automatically.
  * Should quota control be implemented for one project spread into multi-site?
  * What’s the impact on OpenStack interface to support these required features?
  * …
Wiki

User Tools

Site Tools

Page Tools
