Update docs structure according to new guidelines in https://wiki.opnfv.org/display/DOC 49/28349/4
authorGerald Kunzmann <kunzmann@docomolab-euro.com>
Thu, 9 Feb 2017 09:36:29 +0000 (09:36 +0000)
committerGerald Kunzmann <kunzmann@docomolab-euro.com>
Wed, 15 Feb 2017 15:30:08 +0000 (15:30 +0000)
Change-Id: I69e6536d9044dd9db2ed3cd698059aa3a800c318
Signed-off-by: Gerald Kunzmann <kunzmann@docomolab-euro.com>
32 files changed:
docs/development/requirements/NB_interface.rst [moved from docs/requirements/NB_interface.rst with 100% similarity]
docs/development/requirements/annex1.rst [moved from docs/requirements/annex1.rst with 100% similarity]
docs/development/requirements/architecture.rst [moved from docs/requirements/architecture.rst with 100% similarity]
docs/development/requirements/gap_analysis.rst [moved from docs/requirements/gap_analysis.rst with 100% similarity]
docs/development/requirements/glossary.rst [moved from docs/requirements/glossary.rst with 100% similarity]
docs/development/requirements/images/LICENSE [moved from docs/requirements/images/LICENSE with 100% similarity]
docs/development/requirements/images/computeflavor.png [moved from docs/requirements/images/computeflavor.png with 100% similarity]
docs/development/requirements/images/figure1.png [moved from docs/requirements/images/figure1.png with 100% similarity]
docs/development/requirements/images/figure2.png [moved from docs/requirements/images/figure2.png with 100% similarity]
docs/development/requirements/images/figure3.png [moved from docs/requirements/images/figure3.png with 100% similarity]
docs/development/requirements/images/figure4.png [moved from docs/requirements/images/figure4.png with 100% similarity]
docs/development/requirements/images/figure5.png [moved from docs/requirements/images/figure5.png with 100% similarity]
docs/development/requirements/images/figure5_new.png [moved from docs/requirements/images/figure5_new.png with 100% similarity]
docs/development/requirements/images/figure6.png [moved from docs/requirements/images/figure6.png with 100% similarity]
docs/development/requirements/images/figure6_new.png [moved from docs/requirements/images/figure6_new.png with 100% similarity]
docs/development/requirements/images/figure7_new.png [moved from docs/requirements/images/figure7_new.png with 100% similarity]
docs/development/requirements/impl_architecture.rst [moved from docs/requirements/impl_architecture.rst with 100% similarity]
docs/development/requirements/index.rst [moved from docs/requirements/index.rst with 100% similarity]
docs/development/requirements/intro.rst [moved from docs/requirements/intro.rst with 100% similarity]
docs/development/requirements/references.rst [moved from docs/requirements/references.rst with 100% similarity]
docs/development/requirements/revision.rst [moved from docs/requirements/revision.rst with 100% similarity]
docs/development/requirements/schemas.rst [moved from docs/requirements/schemas.rst with 100% similarity]
docs/development/requirements/summary.rst [moved from docs/requirements/summary.rst with 100% similarity]
docs/development/requirements/supported_apis.rst [moved from docs/requirements/supported_apis.rst with 100% similarity]
docs/development/requirements/usecase.rst [moved from docs/requirements/usecase.rst with 100% similarity]
docs/release/configguide/feature.configuration.rst [moved from docs/installationprocedure/feature.configuration.rst with 100% similarity]
docs/release/configguide/images/LICENSE [moved from docs/installationprocedure/images/LICENSE with 100% similarity]
docs/release/configguide/images/screenshot_promise.png [moved from docs/installationprocedure/images/screenshot_promise.png with 100% similarity]
docs/release/configguide/images/screenshot_promise_install.png [moved from docs/installationprocedure/images/screenshot_promise_install.png with 100% similarity]
docs/release/configguide/index.rst [moved from docs/installationprocedure/index.rst with 100% similarity]
docs/release/userguide/feature.userguide.rst [moved from docs/userguide/feature.userguide.rst with 97% similarity]
docs/release/userguide/index.rst [moved from docs/userguide/index.rst with 100% similarity]

similarity index 97%
rename from docs/userguide/feature.userguide.rst
rename to docs/release/userguide/feature.userguide.rst
index 5fcae54..0a32270 100644 (file)
@@ -6,7 +6,7 @@ Abstract
 This user guide document provides the users with:
 
 1. Short description of Promise project and key features implemented in
-Colorado.
+Danube.
 
 Promise description
 ===================
@@ -22,7 +22,7 @@ The following are the key features provided by this module:
 
 Promise capabilities and usage
 ==============================
-The Colorado implementation of Promise is built with the YangForge data modeling
+The Danube implementation of Promise is built with the YangForge data modeling
 framework [#f2]_ , using a shim-layer on top of OpenStack to provide
 the Promise features. This approach requires communication between
 Consumers/Administrators and OpenStack to pass through the shim-layer. The
@@ -41,7 +41,7 @@ in the Promise requirement document [#f1]_ .
 
 Promise features and API usage guidelines and examples
 ------------------------------------------------------
-This section lists the Promise features and API implemented in OPNFV Colorado.
+This section lists the Promise features and API implemented in OPNFV Danube.
 
 Note: The listed parameters are optional unless explicitly marked as "mandatory".
 
@@ -156,7 +156,7 @@ The operation takes the following input parameters:
 * provider-id: identifier of the provider where the instance shall be created
 * reservation-id: identifier of a resource reservation the *create-instance*
 
-The Colorado implementation of Promise has the following limitations:
+The Danube implementation of Promise has the following limitations:
 
 * All create server instance requests shall pass through the Promise
   shim-layer such that Promise can keep track of all allocation requests. This
@@ -263,7 +263,7 @@ The current implementation supports the following filter criteria:
 
 This API  towards OpenStack allows a Consumer/Administrator to add and remove
 resource providers to Promise. Note, Promise supports a multi-provider
-configuration, however, for Colorado, multi-provider support is not yet
+configuration, however, for Danube, multi-provider support is not yet
 fully supported.
 
 *add-provider*
@@ -272,7 +272,7 @@ fully supported.
 This operation is used to register a new resource provider into the Promise
 reservation system.
 
-Note, for Colorado, the add-provider operation should only be used to
+Note, for Danube, the add-provider operation should only be used to
 register one provider with the Promise shim-layer. Further note that currently
 only OpenStack is supported as a provider.