diff options
author | Jie Hu <hu.jie@zte.com.cn> | 2015-09-17 19:43:22 +0800 |
---|---|---|
committer | Jie Hu <hu.jie@zte.com.cn> | 2015-09-17 19:43:22 +0800 |
commit | 81eeba7607f9453ef18ba0917024fe0476cc9178 (patch) | |
tree | 1af43bb3f6200ac354d27fa3a3280f94652ee8ce /doc/01-Scope.rst | |
parent | 4c56dfd4b3434d217a13f14808f4a41184e1d3bd (diff) |
JIRA ESCALATOR-3
Change-Id: I6044ea74eca6ad6337cbc19f35cbfb437f8d1386
Signed-off-by: Jie Hu <hu.jie@zte.com.cn>
Diffstat (limited to 'doc/01-Scope.rst')
-rw-r--r-- | doc/01-Scope.rst | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/01-Scope.rst b/doc/01-Scope.rst new file mode 100644 index 0000000..2f791eb --- /dev/null +++ b/doc/01-Scope.rst @@ -0,0 +1,26 @@ +Scope +----- + +| This document describes the user requirements on the smooth upgrade + function of the NFVI and VIM with respect to the upgrades of the OPNFV + platform from one version to another. Smooth upgrade means that the + upgrade results in no service outage for the end-users. This requires + that the process of the upgrade is automatically carried out by a tool + (code name: Escalator) with pre-configured data. The upgrade process + includes preparation, validation, execution, monitoring and + conclusion. +| ==[MT] While it is good to have a tool for the entire upgrade process, + but it is a challenging task, so maybe we shouldn't require automation + for the entire process right away. Automation is essential at + execution.== +| ==[hujie] Maybe we can analysis information flows of the upgrade tool, + abstract the basic / essential actions from the tool (or tools), and + map them to a command set of NFVI / VIM's interfaces.== + +The requirements are defined in a stepwise approach, i.e. in the first +phase focusing on the upgrade of the VIM then widening the scope to the +NFVI. + +The requirements may apply to different NFV functions (NFVI, or VIM, or +both of them) . They will be classified in the Appendix of this +document.
\ No newline at end of file |