1. Escalator
Project Proposal
20 April 2015
Jie Hu, ZTE

2. Project Name, Repo and Categories
Proposed name for the project: escalator
Proposed name for the repository: escalator
Project Categories: Requirements

3. Background
In the traditional Telco operator’s network, the service (software) is often bound with dedicated hardware and platform.
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 (or with an unnoticeable) service interruption.

4. Overview of Escalator
Identify the user requirements on smooth upgrade the NFVI and VIM from one version to another. 
Identify the gaps from the user requirements to the approved OPNFV projects and other upstream projects.
Provide a requirement document on NFVI and VIM upgrading.
Based on the output of this project, we may propose another project on the reference design and implementation on smooth upgrade of NFVI and VIM. (or extend this project ? )

5. Scope Describe the problem being solved by project
In Telco network, a planned network/service interruption for upgrade should be recovered in a short time. This has not been considered by the upstream projects yet.
Upgrade platform need a lot of efforts on preparation works.
Specify any interface/API specification proposed,
Controlling the upgrade procedure
Sending notifications of the upgrade procedure
Interacting with the Orchestrate or OSS

6. Scope
Validation, Notification, Monitor & Control on Upgrade / Rollback
Develop an use cases section for upgrade related operations to clarify the scope. (Joint work with HA, Multisite, etc.)
High level requirements on the compatibility of OPNFV platform.
BUT NOT: VNF upgrade and update
Architecture, Codes / Automaton scripts, BPs (Future extensible)

7. Dependencies
Identify similar projects is underway or being proposed in OPNFV or upstream project
TBD
Identify any open source upstream projects and release timeline.
Openstack
ODL
Identify any specific development be staged with respect to the upstream project and releases.
Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.
None

8. Committers and Contributors:
Names and affiliations of the committers
Jie Hu
Qiao Fu
Ulrich Kleber
Names and affiliations of any other contributors
Maria Toeroe
Sama, Malla Reddy
Zhong Chao
Julien Zhang
Yuri Yuan
Zhipeng Huang

9. Planned deliverables User Requirement of OPNFV Escalator
Gap Analysis on OPNFV Escalator with open source upstream projects (OpenStack, OpenDaylight, etc.)

10. Proposed Release Schedule
User Requirement of OPNFV Escalator (June 2015)
Gap Analysis on OPNFV Escalator with open source upstream projects (October 2015)
It will align with the 2nd or 3rd release of OPNFV
User Requirement Jun, 2015
Gap Analysis Oct, 2015
Architecture, Codes / Scripts , Blue Prints, …

11. Thanks!