From f24247660e9f6539737d460c59ab66ec2068333b Mon Sep 17 00:00:00 2001 From: zhang-jun3g Date: Mon, 9 Nov 2015 16:31:16 +0800 Subject: Move files from doc to docs Move files to docs for automation html release. JIRA:ESCALATOR-27 Change-Id: I3654b18ad6c7fc94614fd55afe5e3140bf467752 Signed-off-by: zhang-jun3g --- docs/01-Scope.rst | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 docs/01-Scope.rst (limited to 'docs/01-Scope.rst') diff --git a/docs/01-Scope.rst b/docs/01-Scope.rst new file mode 100644 index 0000000..5247e40 --- /dev/null +++ b/docs/01-Scope.rst @@ -0,0 +1,28 @@ +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. + +.. 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. + +.. 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 -- cgit 1.2.3-korg