From 7e663b499dbb0ce1e9f1665bd51a7046c8a174bc Mon Sep 17 00:00:00 2001 From: Bin Yang Date: Wed, 21 Nov 2018 07:55:00 +0000 Subject: Add MultiCloud Architecture Documentation Change-Id: I99b6bd711f4aed106abc5071e082b43886e4d05a Issue-ID: MULTICLOUD-411 Signed-off-by: Bin Yang (cherry picked from commit ea58beb4e0b10c66086983644f7c2e420d78c08f) --- docs/MultiCloud-Administrator-Guide.rst | 6 -- docs/MultiCloud-Architecture.rst | 173 ++++++++++++++++++++++++++++++++ docs/images/mc-arch-workflow.png | Bin 0 -> 95980 bytes docs/index.rst | 7 ++ 4 files changed, 180 insertions(+), 6 deletions(-) create mode 100644 docs/MultiCloud-Architecture.rst create mode 100644 docs/images/mc-arch-workflow.png diff --git a/docs/MultiCloud-Administrator-Guide.rst b/docs/MultiCloud-Administrator-Guide.rst index 98e520b..ae4ff8c 100644 --- a/docs/MultiCloud-Administrator-Guide.rst +++ b/docs/MultiCloud-Administrator-Guide.rst @@ -8,12 +8,6 @@ ONAP MultiCloud Administrator Guide The guide for MultiCloud Administrator. -Architecture -============ - -Please refer to the link for more details: -https://wiki.onap.org/pages/viewpage.action?pageId=8227952 - Configuration ============= diff --git a/docs/MultiCloud-Architecture.rst b/docs/MultiCloud-Architecture.rst new file mode 100644 index 0000000..f1c5087 --- /dev/null +++ b/docs/MultiCloud-Architecture.rst @@ -0,0 +1,173 @@ +.. + This work is licensed under a Creative Commons Attribution 4.0 + International License. + Copyright (c) 2018 Wind River Systems, Inc. + +============================ +ONAP MultiCloud Architecture +============================ + +Value Proposition +----------------- + +ONAP MultiCloud project aims to mediate most interactions (if not all of them) +between ONAP and any underlying VIM or Cloud to: + +* enable ONAP to deploy and run on multiple infrastructure environments +* provide a Cloud Mediation Layer supporting multiple infrastructures and network backends so as to effectively prevents vendor lock-in +* decouples the evolution of ONAP platform from the evolution of underlying cloud infrastructure, and minimizes the impact on the deployed ONAP while upgrading the underlying cloud infrastructures independently + +Besides that, ONAP MultiCloud project enables + +* infrastructure providers exposing infrastructure's resources and features to ONAP for optimization of homing and placement of VNFs +* support the closed control loop remediation over infrastructure resources + +High Level Architecture and Workflows +------------------------------------- + +The following high level architecture and workflow diagram depicts how +ONAP MultiCloud is designed and integrated into ONAP end to end workflow + +.. image:: ./images/mc-arch-workflow.png + :alt: Multicloud icons in MSB + :width: 975 + :height: 293 + :align: center + +Components: +~~~~~~~~~~~ +**Broker:** + +A single broker deployed as micro-service exposes following functionalities: + +* Expose metadata list of supported plugins to ESR +* Route and forward API requests to appropriate plugin by looking up AAI cloud region with ID of the cloud region +* Dispatch capacity checking API to all related plugins + + +**Plugin(s):** + +Plugin adapts API requests to corresponding VIM/Cloud. + +There are multiple plugins deployed as micro-services available: + +* Plugin for Wind River: Adapt to Wind River Titanium Cloud R3, R4 or R5 +* Plugin for Ocata/Pike: Adapt to Vanilla OpenStack Releases: Ocata, Pike, and more to come +* Plugin for VIO: Adapt to VMware VIO +* Plugin for Azure: Adapt to Microsoft Azure Cloud. +* Plugin for kubernetes: Adapt to Kubernetes clusters + +Dependencies: +~~~~~~~~~~~~~ + +* MultiCloud micro-services exposed services via MSB +* MultiCloud relies on MSB for API forwarding between broker and plugin micro-services +* MultiCloud micro-services relies on AAI for any persistent data storage. e.g. AAI Cloud Region Object + + +Workflow elaboration: +~~~~~~~~~~~~~~~~~~~~~ + +0) OOM Deploys ONAP MultiCloud services +#) ONAP users on-boards underlying VIM or Cloud instances via ONAP ESR GUI Portal. + ESR creates AAI cloud region object and requests MultiCloud to update the cloud region with discovered infrastructure's resources and capabilities + +#) SDC distributes Service Model and VNF artifacts + +#) ONAP users deploy services, instantiate VNF + +#) ONAP SO consult OOF for VNF homing and placement hints, OOF matches the + VNF's requirement and cloud region's capabilities and resources to select + the best candidates for VNF homing.OOF also consult MultiCloud for checking + the capacity for VNF placement. + +#) The VNF instantiating + The VNF instantiating approach varies with different use case (or VNF artifacts type) + In case of VIM/Cloud specific artifact type, e.g. HEAT templates, SO invokes MultiCloud directly to instantiate the VNF. + In case of VNFD in TOSCA artifacts, SO invokes VF-C to decompose the TOSCA artifact to atomic resource level and VF-C invokes MultiCloud for atomic resource instantiating. + The interaction between SDN-C and MultiCloud is not yet designed. + +#) MultiCloud also supports close loop remediation by relaying FCAPS events and stream to DCAE VES collector. + +#) APP-C might request MultiCloud to perform resource level remediation + +API pattern: +~~~~~~~~~~~~ +MultiCloud broker exposes API exposed with namespace and version as below: + + api/multicloud/v1/ + +MultiCloud Plugins expose their API with namespace and version as below: + + api/multicloud-titaniumcloud/v1/ + + api/multicloud-ocata/v1/ + + api/multicloud-vio/v1/ + + api/multicloud-azure/v1/ + + api/multicloud-k8s/v1/ + + +For most APIs, the ID of a cloud region follows the API version, with which MultiCloud broker will forward the API to corresponding MultiCloud plugin for handling. + + api/multicloud/v1/{cloud-owner}/{cloud-region-id} + +MultiCloud services are registered into MSB so they can be discovered/reached via MSB API gateway. + + e.g. POST msb.onap.org:80/api/multicloud/v1/{cloud-owner}/{cloud-region-id}/infra_workload + + + +API catalogs +~~~~~~~~~~~~ + +The Northbound APIs can be cataloged as following + +1) Common MultiCloud functionalities + + **API swagger:** + API swagger is used for Health Check as well + +2) Infrastructure Provider registration + The infrastructure provider registration API is to trigger the discovery and registration of infrastructure capabilities (e.g. HPA capabilities) and resource. + +3) Template level APIs + Template level APIs are the integrating point between SO and MultiCloud which offloads the LCM of infrastructure workload from SO + +4) Atomic resource level APIs: + + This set of API falls into either catalog of following + + **Proxy of OpenStack services** + + The proxy of OpenStack services exposed all OpenStack services by replacing the endpoints. This is designed to smoothly integrate MultiCloud with existing ONAP projects which have been talking to OpenStack directly. e.g. APPC + + The API works the same way as native OpenStack API except the difference of endpionts [1]_. + + **Legacy Abstract APIs for VF-C** + + The legacy abstract APIs for VF-C are inherited from OPEN-O project which abstracted the OpenStack service APIs. + The API exposes openstack services with abstract + +5) Placement Optimization APIs: + Aggregate Resource Checking APIs help OOF to optimize the placement of + VNF over underlying VIM/Cloud + +6) FCAPS configuration APIs: + FCAPS Configuration APIs allow users to configure the MultiCloud FCAPS relaying services. + + +Terminology +----------- + +* ONAP MultiCloud, ONAP Multi-VIM/Cloud, ONAP MultiVIM refer to the same project in ONAP. + +* MultiCloud framework is the repo for source code, MultiCloud broker is the entity built from framework + + +References +---------- + +.. [1] https://wiki.onap.org/download/attachments/8227952/OANP_MultiCloud_R1_service_proxy_design.docx?version=1&modificationDate=1531281181000&api=v2 \ No newline at end of file diff --git a/docs/images/mc-arch-workflow.png b/docs/images/mc-arch-workflow.png new file mode 100644 index 0000000..ffa33c5 Binary files /dev/null and b/docs/images/mc-arch-workflow.png differ diff --git a/docs/index.rst b/docs/index.rst index 59aa8fb..c718b3d 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -4,6 +4,13 @@ .. _index-multicloud: +MultiCloud Architecture +----------------------------------- +.. toctree:: + :maxdepth: 2 + + MultiCloud-Architecture + MultiCloud API ----------------------------------- .. toctree:: -- cgit 1.2.3-korg From 2a1f9d70d78956236ef0ece57cb39c25398786ba Mon Sep 17 00:00:00 2001 From: Bin Yang Date: Fri, 16 Nov 2018 10:09:08 +0000 Subject: Update metadata example in API spec Change-Id: Ibdbc34d9aef340ef98316406a4a827badfc94fd5 Issue-ID: MULTICLOUD-405 Signed-off-by: Bin Yang (cherry picked from commit 0e8aea38a1154cdb4799b4f2e06a5b8170bfece8) --- docs/MultiCloud-APIv0-Specification.rst | 17 +++-------------- docs/MultiCloud-APIv1-Specification.rst | 16 +++------------- 2 files changed, 6 insertions(+), 27 deletions(-) diff --git a/docs/MultiCloud-APIv0-Specification.rst b/docs/MultiCloud-APIv0-Specification.rst index b89a51e..a5158c1 100644 --- a/docs/MultiCloud-APIv0-Specification.rst +++ b/docs/MultiCloud-APIv0-Specification.rst @@ -1370,15 +1370,6 @@ N/A | portId | M | 1 | String | Port Id | +-----------------+-----------------+-------------------+---------------+-------------------+ -**metadata** - -+-----------------+-----------------+-------------------+---------------+-------------------+ -| **Parameter** | **Qualifier** | **Cardinality** | **Content** | **Description** | -+=================+=================+===================+===============+===================+ -| keyName | M | 1 | String | Key name | -+-----------------+-----------------+-------------------+---------------+-------------------+ -| value | M | 1 | string | value | -+-----------------+-----------------+-------------------+---------------+-------------------+ :: @@ -1422,13 +1413,11 @@ N/A }], - "metada": [{ - - "keyName": "foo", + "metada": { - "value": "foo value" + "foo": "foo value" - }], + }, "userdata": "abcdedf" diff --git a/docs/MultiCloud-APIv1-Specification.rst b/docs/MultiCloud-APIv1-Specification.rst index b68fbe0..dc5c551 100644 --- a/docs/MultiCloud-APIv1-Specification.rst +++ b/docs/MultiCloud-APIv1-Specification.rst @@ -1152,14 +1152,6 @@ Parameter Qualifier Cardinality Content Description portId M 1 String Port Id ================ ========= ============ ======== ================================ -**metadata** - -================ ========= ============ ======== ================================ -Parameter Qualifier Cardinality Content Description -================ ========= ============ ======== ================================ - keyName M 1 String Key name - value M 1 string value -================ ========= ============ ======== ================================ :: @@ -1203,13 +1195,11 @@ Parameter Qualifier Cardinality Content Description }], - "metada": [{ - - "keyName": "foo", + "metada": { - "value": "foo value" + "foo": "foo value" - }], + }, "userdata": "abcdedf" -- cgit 1.2.3-korg From 3392b7218aeec34c3c63ecd8d53dd4fe9e9fa9fc Mon Sep 17 00:00:00 2001 From: Bin Yang Date: Wed, 21 Nov 2018 08:43:35 +0000 Subject: Wrap long lines Change-Id: I69e19da86592b293bd1e5bc51377583e7f3b6386 Issue-ID: MULTICLOUD-411 Signed-off-by: Bin Yang (cherry picked from commit 6237ee2f502f53b811630d069b26c9077e22e54a) --- docs/MultiCloud-Architecture.rst | 378 +++++++++++++++++++++------------------ 1 file changed, 205 insertions(+), 173 deletions(-) diff --git a/docs/MultiCloud-Architecture.rst b/docs/MultiCloud-Architecture.rst index f1c5087..56a3cc6 100644 --- a/docs/MultiCloud-Architecture.rst +++ b/docs/MultiCloud-Architecture.rst @@ -1,173 +1,205 @@ -.. - This work is licensed under a Creative Commons Attribution 4.0 - International License. - Copyright (c) 2018 Wind River Systems, Inc. - -============================ -ONAP MultiCloud Architecture -============================ - -Value Proposition ------------------ - -ONAP MultiCloud project aims to mediate most interactions (if not all of them) -between ONAP and any underlying VIM or Cloud to: - -* enable ONAP to deploy and run on multiple infrastructure environments -* provide a Cloud Mediation Layer supporting multiple infrastructures and network backends so as to effectively prevents vendor lock-in -* decouples the evolution of ONAP platform from the evolution of underlying cloud infrastructure, and minimizes the impact on the deployed ONAP while upgrading the underlying cloud infrastructures independently - -Besides that, ONAP MultiCloud project enables - -* infrastructure providers exposing infrastructure's resources and features to ONAP for optimization of homing and placement of VNFs -* support the closed control loop remediation over infrastructure resources - -High Level Architecture and Workflows -------------------------------------- - -The following high level architecture and workflow diagram depicts how -ONAP MultiCloud is designed and integrated into ONAP end to end workflow - -.. image:: ./images/mc-arch-workflow.png - :alt: Multicloud icons in MSB - :width: 975 - :height: 293 - :align: center - -Components: -~~~~~~~~~~~ -**Broker:** - -A single broker deployed as micro-service exposes following functionalities: - -* Expose metadata list of supported plugins to ESR -* Route and forward API requests to appropriate plugin by looking up AAI cloud region with ID of the cloud region -* Dispatch capacity checking API to all related plugins - - -**Plugin(s):** - -Plugin adapts API requests to corresponding VIM/Cloud. - -There are multiple plugins deployed as micro-services available: - -* Plugin for Wind River: Adapt to Wind River Titanium Cloud R3, R4 or R5 -* Plugin for Ocata/Pike: Adapt to Vanilla OpenStack Releases: Ocata, Pike, and more to come -* Plugin for VIO: Adapt to VMware VIO -* Plugin for Azure: Adapt to Microsoft Azure Cloud. -* Plugin for kubernetes: Adapt to Kubernetes clusters - -Dependencies: -~~~~~~~~~~~~~ - -* MultiCloud micro-services exposed services via MSB -* MultiCloud relies on MSB for API forwarding between broker and plugin micro-services -* MultiCloud micro-services relies on AAI for any persistent data storage. e.g. AAI Cloud Region Object - - -Workflow elaboration: -~~~~~~~~~~~~~~~~~~~~~ - -0) OOM Deploys ONAP MultiCloud services -#) ONAP users on-boards underlying VIM or Cloud instances via ONAP ESR GUI Portal. - ESR creates AAI cloud region object and requests MultiCloud to update the cloud region with discovered infrastructure's resources and capabilities - -#) SDC distributes Service Model and VNF artifacts - -#) ONAP users deploy services, instantiate VNF - -#) ONAP SO consult OOF for VNF homing and placement hints, OOF matches the - VNF's requirement and cloud region's capabilities and resources to select - the best candidates for VNF homing.OOF also consult MultiCloud for checking - the capacity for VNF placement. - -#) The VNF instantiating - The VNF instantiating approach varies with different use case (or VNF artifacts type) - In case of VIM/Cloud specific artifact type, e.g. HEAT templates, SO invokes MultiCloud directly to instantiate the VNF. - In case of VNFD in TOSCA artifacts, SO invokes VF-C to decompose the TOSCA artifact to atomic resource level and VF-C invokes MultiCloud for atomic resource instantiating. - The interaction between SDN-C and MultiCloud is not yet designed. - -#) MultiCloud also supports close loop remediation by relaying FCAPS events and stream to DCAE VES collector. - -#) APP-C might request MultiCloud to perform resource level remediation - -API pattern: -~~~~~~~~~~~~ -MultiCloud broker exposes API exposed with namespace and version as below: - - api/multicloud/v1/ - -MultiCloud Plugins expose their API with namespace and version as below: - - api/multicloud-titaniumcloud/v1/ - - api/multicloud-ocata/v1/ - - api/multicloud-vio/v1/ - - api/multicloud-azure/v1/ - - api/multicloud-k8s/v1/ - - -For most APIs, the ID of a cloud region follows the API version, with which MultiCloud broker will forward the API to corresponding MultiCloud plugin for handling. - - api/multicloud/v1/{cloud-owner}/{cloud-region-id} - -MultiCloud services are registered into MSB so they can be discovered/reached via MSB API gateway. - - e.g. POST msb.onap.org:80/api/multicloud/v1/{cloud-owner}/{cloud-region-id}/infra_workload - - - -API catalogs -~~~~~~~~~~~~ - -The Northbound APIs can be cataloged as following - -1) Common MultiCloud functionalities - - **API swagger:** - API swagger is used for Health Check as well - -2) Infrastructure Provider registration - The infrastructure provider registration API is to trigger the discovery and registration of infrastructure capabilities (e.g. HPA capabilities) and resource. - -3) Template level APIs - Template level APIs are the integrating point between SO and MultiCloud which offloads the LCM of infrastructure workload from SO - -4) Atomic resource level APIs: - - This set of API falls into either catalog of following - - **Proxy of OpenStack services** - - The proxy of OpenStack services exposed all OpenStack services by replacing the endpoints. This is designed to smoothly integrate MultiCloud with existing ONAP projects which have been talking to OpenStack directly. e.g. APPC - - The API works the same way as native OpenStack API except the difference of endpionts [1]_. - - **Legacy Abstract APIs for VF-C** - - The legacy abstract APIs for VF-C are inherited from OPEN-O project which abstracted the OpenStack service APIs. - The API exposes openstack services with abstract - -5) Placement Optimization APIs: - Aggregate Resource Checking APIs help OOF to optimize the placement of - VNF over underlying VIM/Cloud - -6) FCAPS configuration APIs: - FCAPS Configuration APIs allow users to configure the MultiCloud FCAPS relaying services. - - -Terminology ------------ - -* ONAP MultiCloud, ONAP Multi-VIM/Cloud, ONAP MultiVIM refer to the same project in ONAP. - -* MultiCloud framework is the repo for source code, MultiCloud broker is the entity built from framework - - -References ----------- - -.. [1] https://wiki.onap.org/download/attachments/8227952/OANP_MultiCloud_R1_service_proxy_design.docx?version=1&modificationDate=1531281181000&api=v2 \ No newline at end of file +.. + This work is licensed under a Creative Commons Attribution 4.0 + International License. + Copyright (c) 2018 Wind River Systems, Inc. + +============================ +ONAP MultiCloud Architecture +============================ + +Value Proposition +----------------- + +ONAP MultiCloud project aims to mediate most interactions (if not all of them) +between ONAP and any underlying VIM or Cloud to: + +* enable ONAP to deploy and run on multiple infrastructure environments +* provide a Cloud Mediation Layer supporting multiple infrastructures and + network backends so as to effectively prevents vendor lock-in +* decouples the evolution of ONAP platform from the evolution of underlying + cloud infrastructure, and minimizes the impact on the deployed ONAP while + upgrading the underlying cloud infrastructures independently + +Besides that, ONAP MultiCloud project enables + +* infrastructure providers exposing infrastructure's resources and features + to ONAP for optimization of homing and placement of VNFs +* support the closed control loop remediation over infrastructure resources + +High Level Architecture and Workflows +------------------------------------- + +The following high level architecture and workflow diagram depicts how +ONAP MultiCloud is designed and integrated into ONAP end to end workflow + +.. image:: ./images/mc-arch-workflow.png + :alt: Multicloud icons in MSB + :width: 975 + :height: 293 + :align: center + +Components: +~~~~~~~~~~~ +**Broker:** + +A single broker deployed as micro-service exposes following functionalities: + +* Expose metadata list of supported plugins to ESR +* Route and forward API requests to appropriate plugin by looking up AAI cloud + region with ID of the cloud region +* Dispatch capacity checking API to all related plugins + + +**Plugin(s):** + +Plugin adapts API requests to corresponding VIM/Cloud. + +There are multiple plugins deployed as micro-services available: + +* Plugin for Wind River: Adapt to Wind River Titanium Cloud R3, R4 or R5 +* Plugin for Ocata/Pike: Adapt to Vanilla OpenStack Releases: Ocata, Pike +* Plugin for VIO: Adapt to VMware VIO +* Plugin for Azure: Adapt to Microsoft Azure Cloud. +* Plugin for kubernetes: Adapt to Kubernetes clusters + +Dependencies: +~~~~~~~~~~~~~ + +* MultiCloud micro-services exposed services via MSB +* MultiCloud relies on MSB for API forwarding between broker and plugin + micro-services +* MultiCloud micro-services relies on AAI for any persistent data storage. + e.g. AAI Cloud Region Object + + +Workflow elaboration: +~~~~~~~~~~~~~~~~~~~~~ + +0) OOM Deploys ONAP MultiCloud services +#) ONAP users on-boards underlying VIM or Cloud instances via ONAP ESR GUI. + ESR creates AAI cloud region object and requests MultiCloud to update the + cloud region with discovered infrastructure's resources and capabilities + +#) SDC distributes Service Model and VNF artifacts + +#) ONAP users deploy services, instantiate VNF + +#) ONAP SO consult OOF for VNF homing and placement hints, OOF matches the + VNF's requirement and cloud region's capabilities and resources to select + the best candidates for VNF homing.OOF also consult MultiCloud for checking + the capacity for VNF placement. + +#) The VNF instantiating + The VNF instantiating approach varies with different use case (or VNF + artifacts type): + + In case of VIM/Cloud specific artifact type, e.g. HEAT templates, SO + invokes MultiCloud directly to instantiate the VNF. + + In case of VNFD in TOSCA artifacts, SO invokes VF-C to decompose the + TOSCA artifact to atomic resource level and VF-C invokes MultiCloud for + atomic resource instantiating. + + The interaction between SDN-C and MultiCloud is not yet designed. + +#) MultiCloud also supports close loop remediation by relaying FCAPS events + and stream to DCAE VES collector. + +#) APP-C might request MultiCloud to perform resource level remediation + +API pattern: +~~~~~~~~~~~~ +MultiCloud broker exposes API exposed with namespace and version as below: + +:: + + api/multicloud/v1/ + +MultiCloud Plugins expose their API with namespace and version as below: + +:: + + api/multicloud-titaniumcloud/v1/ + api/multicloud-ocata/v1/ + api/multicloud-vio/v1/ + api/multicloud-azure/v1/ + api/multicloud-k8s/v1/ + + +For most APIs, the ID of a cloud region follows the API version, with which +MultiCloud broker will forward the API to corresponding MultiCloud plugin for +handling. + +:: + + api/multicloud/v1/{cloud-owner}/{cloud-region-id} + +MultiCloud services are registered into MSB so they can be discovered/reached +via MSB API gateway. + +:: + + e.g. POST msb.onap.org:80/api/multicloud/v1/{cloud-owner}/{cloud-region-id}/infra_workload + + +API catalogs +~~~~~~~~~~~~ + +The Northbound APIs can be cataloged as following + +1) Common MultiCloud functionalities + + **API swagger:** + API swagger is used for Health Check as well + +2) Infrastructure Provider registration + The infrastructure provider registration API is to trigger the discovery + and registration of infrastructure capabilities (e.g. HPA capabilities) + and resource. + +3) Template level APIs + Template level APIs are the integrating point between SO and MultiCloud + which offloads the LCM of infrastructure workload from SO + +4) Atomic resource level APIs: + + This set of API falls into either catalog of following + + **Proxy of OpenStack services** + + The proxy of OpenStack services exposed all OpenStack services by replacing + the endpoints. This is designed to smoothly integrate MultiCloud with + existing ONAP projects which have been talking to OpenStack directly. + e.g. APPC + + The API works the same way as native OpenStack API except the difference of + endpionts [1]_. + + **Legacy Abstract APIs for VF-C** + + The legacy abstract APIs for VF-C are inherited from OPEN-O project which + abstracted the OpenStack service APIs. + +5) Placement Optimization APIs: + Aggregate Resource Checking APIs help OOF to optimize the placement of + VNF over underlying VIM/Cloud + +6) FCAPS configuration APIs: + FCAPS Configuration APIs allow users to configure the MultiCloud FCAPS + relaying services. + + +Terminology +----------- + +* ONAP MultiCloud, ONAP Multi-VIM/Cloud, ONAP MultiVIM refer to the same + project in ONAP. + +* MultiCloud framework is the repo for source code, MultiCloud broker is the + entity built from framework + + +References +---------- + +.. [1] https://wiki.onap.org/download/attachments/8227952/OANP_MultiCloud_R1_service_proxy_design.docx?version=1&modificationDate=1531281181000&api=v2 -- cgit 1.2.3-korg From 253e8458ebe6d64d73f2ec45736ec38e3c234b84 Mon Sep 17 00:00:00 2001 From: Xiaohua Zhang Date: Tue, 27 Nov 2018 09:55:38 +0000 Subject: bump version to 1.2.3 Change-Id: I5a3725a9deeac3e9e8bd3d01305ba87f2db90e49 Issue-ID: MULTICLOUD-419 Signed-off-by: Xiaohua Zhang (cherry picked from commit 36035e27f91e4d77f80fc806cbfffc2fa5110b32) --- multivimbroker/docker/Dockerfile | 2 +- multivimbroker/docker/build_image.sh | 4 ++-- multivimbroker/pom.xml | 4 ++-- pom.xml | 2 +- version.properties | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/multivimbroker/docker/Dockerfile b/multivimbroker/docker/Dockerfile index 6167e9b..bc72323 100644 --- a/multivimbroker/docker/Dockerfile +++ b/multivimbroker/docker/Dockerfile @@ -14,7 +14,7 @@ EXPOSE 9001 RUN apt-get update && \ apt-get install -y unzip && \ cd /opt/ && \ - wget -O multicloud-framework.zip "https://nexus.onap.org/service/local/artifact/maven/redirect?r=snapshots&g=org.onap.multicloud.framework.broker&a=multicloud-framework-broker&e=zip&v=1.2.2-SNAPSHOT" && \ + wget -O multicloud-framework.zip "https://nexus.onap.org/service/local/artifact/maven/redirect?r=snapshots&g=org.onap.multicloud.framework.broker&a=multicloud-framework-broker&e=zip&v=1.2.3-SNAPSHOT" && \ unzip -q -o -B multicloud-framework.zip && \ rm -f multicloud-framework.zip && \ pip install -r /opt/multivimbroker/requirements.txt diff --git a/multivimbroker/docker/build_image.sh b/multivimbroker/docker/build_image.sh index f196590..11a46da 100644 --- a/multivimbroker/docker/build_image.sh +++ b/multivimbroker/docker/build_image.sh @@ -17,8 +17,8 @@ cd ${DOCKER_BUILD_DIR} BUILD_ARGS="--no-cache" ORG="onap" -VERSION="1.2.2-SNAPSHOT" -STAGING_VERSION="1.2.2-STAGING" +VERSION="1.2.3-SNAPSHOT" +STAGING_VERSION="1.2.3-STAGING" PROJECT="multicloud" IMAGE="framework" DOCKER_REPOSITORY="nexus3.onap.org:10003" diff --git a/multivimbroker/pom.xml b/multivimbroker/pom.xml index f87db2c..fbaa183 100644 --- a/multivimbroker/pom.xml +++ b/multivimbroker/pom.xml @@ -18,12 +18,12 @@ org.onap.multicloud.framework multicloud-framework - 1.2.2-SNAPSHOT + 1.2.3-SNAPSHOT 4.0.0 org.onap.multicloud.framework.broker multicloud-framework-broker - 1.2.2-SNAPSHOT + 1.2.3-SNAPSHOT pom multicloud-framework-broker multivim broker diff --git a/pom.xml b/pom.xml index 1764a59..a4b00f8 100644 --- a/pom.xml +++ b/pom.xml @@ -24,7 +24,7 @@ 4.0.0 org.onap.multicloud.framework multicloud-framework - 1.2.2-SNAPSHOT + 1.2.3-SNAPSHOT pom multicloud-framework multivim broker diff --git a/version.properties b/version.properties index c9206e9..cd12874 100644 --- a/version.properties +++ b/version.properties @@ -19,7 +19,7 @@ major=1 minor=2 -patch=2 +patch=3 base_version=${major}.${minor}.${patch} -- cgit 1.2.3-korg From f6334a804d974a0cea267cba327e64571e0f0616 Mon Sep 17 00:00:00 2001 From: Bin Yang Date: Thu, 29 Nov 2018 02:24:59 +0000 Subject: Refine Release note 3.0.0 Align to ONAP release versions And specify the components with versions Change-Id: Idd2e131ca25a91df4a75d41008e6283dfd37c10e Issue-ID: MULTICLOUD-422 Signed-off-by: Bin Yang --- docs/Release Notes.rst | 124 +++++++++++++++++++++++++++++++++---------------- 1 file changed, 83 insertions(+), 41 deletions(-) diff --git a/docs/Release Notes.rst b/docs/Release Notes.rst index 47d075b..f183082 100644 --- a/docs/Release Notes.rst +++ b/docs/Release Notes.rst @@ -6,15 +6,19 @@ Release Notes ============= -Version: 1.2.1 --------------- -:Release Date: 2018-11-12 +Version: 3.0.0 (Casablanca Release) +----------------------------------- + +:Release Date: 2018-11-30 **New Features** -* Upgraded Northbound API to v1 which support `Consistent ID of a Cloud Region` -* Added new Generic API to offload Infrastructure's workload LCM from SO to MutliCloud +* Enriched the documentaton with Architecture descriptions +* Verified the supports to end to end vCPE TOSCA VNF use case +* Upgraded to Northbound API v1 to support `Consistent ID of a Cloud Region` +* Added new Generic API to offload Infrastructure's workload LCM from SO to + MutliCloud * Updated the plugin for Wind River to support Titanium Cloud R5 * Updated the plugin for VIO to support VIO 5.0 * Added a plugin to support OpenStack Pike @@ -22,70 +26,96 @@ Version: 1.2.1 * Released Kubernetes' plugin seed code -**MultiCloud Plugin for Wind River Titanium Cloud** +**The MultiCloud services consists of following components:** + +**MultiCloud Broker (version: 1.2.2)** + +* Added plugin type for azure and pike +* Added API v1 to align to `Consistent ID of a Cloud Region` +* Added API infra_workload to enable SO and MultiCloud Integration + +**MultiCloud Plugin for Wind River Titanium Cloud (version: 1.2.2)** * Expanded the HPA discovery and registration to cover SR-IOV NICs. * Decoupled AAI's cloud-region-id from OpenStack Region ID -* Automated the on-boarding multiple OpenStack instances leveraging OpenStack multi-region feature. -* Enabled the on-boarding of subclouds of Titanium Cloud in Distributed Cloud Mode +* Automated the on-boarding multiple OpenStack instances leveraging OpenStack + multi-region feature. +* Enabled the on-boarding of subclouds of Titanium Cloud in Distributed Cloud + Mode * Automated the decommission of a Cloud Region * Automated the updating AAI with heat stack resources * Enabled Server Operations API for Auto-Healing +* Cached the AAI cloud region data to improve the API handling performance +* Passed the vCPE TOSCA VNF use case with several critical issues fixed +* Fixed the keystone v2.0 endpoint issue - -**MultiCloud Plugin for OpenStack** +**MultiCloud Plugin for OpenStack (version: 1.2.2)** * Expanded the HPA discovery and registration to cover SR-IOV NICs. * Decoupled AAI's cloud-region-id from OpenStack Region ID * Enabled Server Operations API for Auto-Healing +* Cached the AAI cloud region data to improve the API handling performance +* Passed the vCPE TOSCA VNF use case with several critical issues fixed +* Fixed the keystone v2.0 endpoint issue -**MultiCloud Plugin for VIO** +**MultiCloud Plugin for VIO (version 1.2.2)** * Expanded the HPA discovery and registration to cover SR-IOV NICs. * Decoupled AAI's cloud-region-id from OpenStack Region ID -* Automated the on-boarding multiple OpenStack instances leveraging OpenStack multi-region feature. +* Automated the on-boarding multiple OpenStack instances leveraging OpenStack + multi-region feature. * Automated the decommission of a Cloud Region * Supported Cloud Agnostic Placement Policies in VIO plugin * Enabled Server Operations API for Auto-Healing * Enabled marker support on logging -**MultiCloud Plugin for Azure** +**MultiCloud Plugin for Azure (version 1.2.2)** + * Released inital seed code * Enabled flavor discovery during on-boarding of azure cloud * Supported for OOB vFW and vDNS use cases using the plugin -**MultiCloud Plugin for Kubernetes** +**MultiCloud Plugin for Kubernetes (version: N/A)** + * Released initial seed code -* Supported Service, Deployment and Namespace Kubernetes objects for this initial phase -* Provided functional tests for ensuring its correct operation using an emulated ONAP interaction +* Supported Service, Deployment and Namespace Kubernetes objects for this + initial phase +* Provided functional tests for ensuring its correct operation using an + emulated ONAP interaction * Included a vagrant project for provisioning a Kubernetes deployment -**Bug Fixes** - -**Known Issues** +**Bug Fixes** - `MULTICLOUD-253 `_ OPENO servers API: meta_data is generated in wrong type -- `MULTICLOUD-359 `_ - OPENO images API: image creating API cannot handle large image file - - `MULTICLOUD-386 `_ OPENO identity API: identity API cannot work with keystone endpoint v2.0 -- `MULTICLOUD-389 `_ - OPENO servers API: keypair cannot be passed for nova instance creation - - `MULTICLOUD-390 `_ OPENO servers API: pass userdata without contextArray, then "user_data" is not being passed to nova instance API. +**Known Issues** + +- `MULTICLOUD-359 `_ + OPENO images API: image creating API cannot handle large image file + +- `MULTICLOUD-389 `_ + OPENO servers API: keypair cannot be passed for nova instance creation + +- `MULTICLOUD-421 `_ + API request to multicloud with authorization header will be rejected + + + **Security Notes** -MULTICLOUD code has been formally scanned during build time using NexusIQ and no Critical vulnerability were found. +MULTICLOUD code has been formally scanned during build time using NexusIQ and +no Critical vulnerability were found. Quick Links: - `MULTICLOUD project page `_ @@ -98,15 +128,16 @@ None **Deprecation Notes** -* The maintainance with regarding to MultiCloud plugin for OpenStack Newton has been stopped from Casablanca Release. +* The maintainance with regarding to MultiCloud plugin for OpenStack Newton + has been stopped from Casablanca Release. **Other** None -Version: 1.1.2 --------------- +Version: 2.0.0 (Beijing Release) +-------------------------------- :Release Date: 2018-06-07 @@ -115,12 +146,16 @@ Version: 1.1.2 * Allow to check capacity capability for smart VNF placement across VIMs. * Declarative template driven framework to generate API dynamically. -* Federate the events of VIM layer with ONAP message bus which provide direct help to HA fencing and improve the +* Federate the events of VIM layer with ONAP message bus which provide direct + help to HA fencing and improve the efficiency of VM recover with performance verification. * Enable basic HPA discovery and representing at Multi VIM/Cloud when registry. -* Enable distributed log collection mechanism to a centralized logging analysis system. -* Improve parallelism of Multi VIM/Cloud service framework with performance verification. -* Upload and download images based on Cloud storage capabilities to support remote image distribution requirement. +* Enable distributed log collection mechanism to a centralized logging + analysis system. +* Improve parallelism of Multi VIM/Cloud service framework with performance + verification. +* Upload and download images based on Cloud storage capabilities to support + remote image distribution requirement. **Bug Fixes** @@ -137,12 +172,15 @@ Version: 1.1.2 **Known Issues** - `MULTICLOUD-242 `_ - One known issue is that the Ocata image is not put into the consistent place as R1 and please attention to the - download path when you choose manual installation of Ocata plugin from the image pool. + One known issue is that the Ocata image is not put into the consistent place + as R1 and please attention to the + download path when you choose manual installation of Ocata plugin from the + image pool. **Security Notes** -MULTICLOUD code has been formally scanned during build time using NexusIQ and no Critical vulnerability were found. +MULTICLOUD code has been formally scanned during build time using NexusIQ and +no Critical vulnerability were found. Quick Links: - `MULTICLOUD project page `_ @@ -161,23 +199,27 @@ None None -Version: 1.0.0 --------------- +Version: 1.0.0 (Amsterdam Release) +---------------------------------- :Release Date: 2017-11-16 **New Features** -* Keystone proxy for convenient integration with modules which depend on original OpenStack functions +* Keystone proxy for convenient integration with modules which depend on + original OpenStack functions * Multiple VIM registry and unregister * Resources LCM functions * Auto-deployment support to both K8s and heat * Hierarchical binding based integration with the third party SDN controller -* Basic Fcaps alert collection support, VM abnormal status is thrown out as an example +* Basic Fcaps alert collection support, VM abnormal status is thrown out as + an example * Fake cloud based Unit and system test framework * Complete code coverage detection, CSIT, and document framework -* Provide several plugins of different backbends, including: Vanilla OpenStack (based on Ocata) and commercial Clouds including OpenStack (including Titanium - Mitaka from Wind River and VIO - Ocata from VMware) +* Provide several plugins of different backbends, including: Vanilla OpenStack + (based on Ocata) and commercial Clouds including OpenStack (including + Titanium - Mitaka from Wind River and VIO - Ocata from VMware) **Bug Fixes** -- cgit 1.2.3-korg From db453dd45bacb0cb3caf63a20d5ac3bd4254fe10 Mon Sep 17 00:00:00 2001 From: Bin Yang Date: Wed, 28 Nov 2018 07:23:15 +0000 Subject: Refactor the rst Specify release version which support vCPE TOSCA VNF use case Change-Id: I8663fcb8e8fd1c943fc8254e9a30bca91fdccead Issue-ID: MULTICLOUD-422 Signed-off-by: Bin Yang (cherry picked from commit e455c741c34660dacaa1643ef0a660e7b3efac90) --- ...serGuide-MultiCloud-WindRiver-TitaniumCloud.rst | 325 +++++++++++---------- 1 file changed, 173 insertions(+), 152 deletions(-) diff --git a/docs/multicloud-plugin-windriver/UserGuide-MultiCloud-WindRiver-TitaniumCloud.rst b/docs/multicloud-plugin-windriver/UserGuide-MultiCloud-WindRiver-TitaniumCloud.rst index 8e3b851..17200c7 100644 --- a/docs/multicloud-plugin-windriver/UserGuide-MultiCloud-WindRiver-TitaniumCloud.rst +++ b/docs/multicloud-plugin-windriver/UserGuide-MultiCloud-WindRiver-TitaniumCloud.rst @@ -1,152 +1,173 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 -.. International License. http://creativecommons.org/licenses/by/4.0 -.. Copyright (c) 2017-2018 Wind River Systems, Inc. - -=============================================== -MultiCloud Plugin for Wind River Titanium Cloud -=============================================== - -The following guides are provided to describe tasks that a user of -ONAP may need to perform when operating ONAP to orchestrate VNF onto -an instance of Wind River Titanium Cloud - - -Supported Features -`````````````````` - -**Proxy endpoints for OpenStack services** - - MultiCloud plugin for Wind River Titanium Cloud supports the proxy of OpenStack services - The catalog of proxied services is exactly the catalog of OpenStack services - -**VFC specific Northbound API** - - MultiCloud plugin for Wind River Titanium Cloud supports VFC with the legacy APIs - which was inherited from OPEN-O MultiVIM project. - -**Support enhanced SO/OOF workflow** - - MultiCloud plugin for Wind River Titanium Cloud supports infra_workload APIs from Casablanca Release. - - These APIs enhances the workflow of Heat based VNF orchestration by: - offloading Heat template/parameter updating from SO to MultiCloud plugins - - Enabling the "Centralized Representation of Cloud Regions" - - Automate the heatbridge action by updating the AAI with deployed Heat stack resources - -**Support OOF** - - MultiCloud plugin for Wind River Titanium Cloud supports capacity check from Beijing Release. - -**Conform to Consistent ID of a Cloud Region** - - Northbound API v1 supports the composite keys {cloud-owner}/{cloud-region-id} as - the ID of a cloud region - -**Decoupling between cloud-region-id and OpenStack Region ID** - - {cloud-region-id} should be populated by users while on-boarding a cloud region, - With ONAP A and B release, it must be the same as the "OpenStack Region ID" of the - represented OpenStack instance. From ONAP C release, this restriction has been removed. - - The backward compatibility is maintained so that user can still populate the {cloud-reigon-id} by - "OpenStack Region ID". - - Users could also specify the "OpenStack Region ID" while onboarding a cloud region - out of multi-region instances. - - Note: There are still restrictions to populate {cloud-owner} and {cloud-region-id}, please - refer to section "On-board a Cloud Region" - -**Support on-boarding of Multi-Region instances** - - Multiple OpenStack instances federated with the "multi-region" feature - can be on-boarded into ONAP with a single click. ONAP user needs to - register only the primary region into ONAP, and the multicloud plugin for Wind River - - Titanium Cloud will discover and on-board all other secondary regions automatically. - - This feature supports Titanium Cloud feature "Distributed Cloud" to on-board all subclouds with a single click. - - This feature can be controlled by user with configuration options while on-boarding a cloud region - -**HPA discovery** - - MultiCloud plugin for Wind River Titanium Cloud supports discover and - registration into AAI with regarding to following HPA capability: - CPU Pinning, HugePage, ... - -**Cloud Region decommission** - - MultiCloud plugin for Wind River Titanium Cloud support the decommission of a cloud region with a single API requests. - This API is not yet integrated with ESR GUI portal. - -**VESagent** - - MultiCloud plugin for Wind River Titanium Cloud supports VESagent - which can be configured to monitor the VM status and assert or abate - fault event to VES collector for close loop control over - infrastructure resources. - -**LOGGING** - MultiCloud plugin for Wind River Titanium Cloud supports centralized logging with OOM deployed ONAP - - -Supported Use Cases -``````````````````` - -**vFW/vDNS** - - The vFW/vDNS are the VNFs modeled with HEAT templates - MultiCloud plugin for Wind River Titanium Cloud has been tested with vFW/vDNS use cases from Amsterdam Release. - -**vCPE** - - **vCPE without HPA orchestration** - vCPE is the VNF modeled with HEAT templates, basic Use case from Amsterdam Release - does not include any HPA orchestration. - - **vCPE with HPA orchestration** - From Beijing Release,a variation of vCPE use case include HPA orchestration - - MultiCloud plugin for Wind River Titanium Cloud has been tested with both cases. - -**vVoLTE** - - MultiCloud plugin for Wind River Titanium Cloud has been tested with vVoLTE use case. - - -Known Issues: -`````````````````` - -1, MULTICLOUD-359 : The image uploading API from VFC specific NBI does not work with large image file. - - - -.. include:: Tutorial-Onboard-WindRiver-TitaniumCloud.rst - - -Tutorial: Cloud Region Decommission: -```````````````````````````````````` - -ESR GUI Portal cannot decommission a cloud region which has been updated by -MultiCloud Plugin for Wind River Titanium Cloud, and it does not request MultiCloud -to help on that yet. So it is required to issue a rest API request to MultiCloud with -a single curl commands: - - -.. code-block:: console - - curl -X DELETE \ - 'http://$ONAP_MSB_IP:$ONAP_MSB_PORT/api/multicloud-titaniumcloud/v0/CloudOwner_RegionOne' \ - -H 'Accept: application/json' \ - -H 'Cache-Control: no-cache' \ - -H 'Content-Type: application/json' \ - -H 'Postman-Token: 8577e1cc-1038-471d-8b3b-d36fe44ae023' - - -.. include:: Tutorial-HPA-Provision-Discovery-WindRiver-TitaniumCloud.rst - - -.. include:: Tutorial-VESagent-MultiCloud-WindRiver-TitaniumCloud.rst +.. This work is licensed under a Creative Commons Attribution 4.0 +.. International License. http://creativecommons.org/licenses/by/4.0 +.. Copyright (c) 2017-2018 Wind River Systems, Inc. + +=============================================== +MultiCloud Plugin for Wind River Titanium Cloud +=============================================== + +The following guides are provided to describe tasks that a user of +ONAP may need to perform when operating ONAP to orchestrate VNF onto +an instance of Wind River Titanium Cloud + + +Supported Features +`````````````````` + +**Proxy endpoints for OpenStack services** + + MultiCloud plugin for Wind River Titanium Cloud supports the proxy of + OpenStack services. The catalog of proxied services is exactly same as + the catalog of OpenStack services + +**VFC specific Northbound API** + + MultiCloud plugin for Wind River Titanium Cloud supports VFC with the + legacy APIs which was inherited from OPEN-O MultiVIM project. + +**Support enhanced SO/OOF workflow** + + MultiCloud plugin for Wind River Titanium Cloud supports infra_workload + APIs from Casablanca Release. + + These APIs enhances the workflow of Heat based VNF orchestration by: + + - offloading Heat template/parameter updating from SO to MultiCloud + plugins + - Enabling the "Centralized Representation of Cloud Regions" + - Automate the heatbridge action by updating the AAI with deployed Heat + stack resources + +**Support OOF** + + MultiCloud plugin for Wind River Titanium Cloud supports capacity check + from Beijing Release. + +**Conform to Consistent ID of a Cloud Region** + + Northbound API v1 supports the composite keys + {cloud-owner}/{cloud-region-id} as the ID of a cloud region + +**Decoupling between cloud-region-id and OpenStack Region ID** + + {cloud-region-id} should be populated by users while on-boarding a cloud + region. With ONAP A and B release, it must be the same as the "OpenStack + Region ID" of the represented OpenStack instance. From ONAP C release, + this restriction has been removed. + + The backward compatibility is maintained so that user can still populate + the {cloud-reigon-id} by "OpenStack Region ID". + + Users could also specify the "OpenStack Region ID" while onboarding a + cloud region out of multi-region instances. + +.. Note:: There are still restrictions to populate {cloud-owner} and + {cloud-region-id}, please refer to section "On-board a Cloud Region" + +**Support on-boarding of Multi-Region instances** + + Multiple OpenStack instances federated with the "multi-region" feature + can be on-boarded into ONAP with a single click. ONAP user needs to + register only the primary region into ONAP, and the multicloud plugin for + Wind River Titanium Cloud + + Titanium Cloud will discover and on-board all other secondary regions + automatically. + + This feature supports Titanium Cloud feature "Distributed Cloud" to + on-board all subclouds with a single click. + + This feature can be controlled by user with configuration options while + on-boarding a cloud region + +**HPA discovery** + + MultiCloud plugin for Wind River Titanium Cloud supports discover and + registration into AAI with regarding to following HPA capability: + CPU Pinning, HugePage, ... + +**Cloud Region decommission** + + MultiCloud plugin for Wind River Titanium Cloud support the decommission + of a cloud region with a single API requests. + + This API is not yet integrated with ESR GUI portal. + +**VESagent** + + MultiCloud plugin for Wind River Titanium Cloud supports VESagent + which can be configured to monitor the VM status and assert or abate + fault event to VES collector for close loop control over + infrastructure resources. + +**LOGGING** + MultiCloud plugin for Wind River Titanium Cloud supports centralized + logging with OOM deployed ONAP + + +Supported Use Cases +``````````````````` + +**vFW/vDNS** + + The vFW/vDNS are the VNFs modeled with HEAT templates + MultiCloud plugin for Wind River Titanium Cloud has been tested with + vFW/vDNS use cases from Amsterdam Release. + +**vCPE** + + **vCPE (HEAT VNF) without HPA orchestration** + vCPE is the VNF modeled with HEAT templates, basic Use case from + Amsterdam Release does not include any HPA orchestration. + + **vCPE (HEAT VNF) with HPA orchestration** + From Beijing Release,a variation of vCPE use case include HPA + orchestration + + **vCPE (TOSCA VNF) with HPA orchestration** + From Casablanca Release (With MultiCloud Release Version 1.2.2), vCPE + use case expands to support TOSCA VNF and include HPA orchestration + + MultiCloud plugin for Wind River Titanium Cloud has been tested with both + cases. + +**vVoLTE** + + MultiCloud plugin for Wind River Titanium Cloud has been tested with vVoLTE + use case. + + +Known Issues: +`````````````````` + +1. MULTICLOUD-359 : The image uploading API from VFC specific NBI does not +work with large image file. + + + +.. include:: Tutorial-Onboard-WindRiver-TitaniumCloud.rst + + +Tutorial: Cloud Region Decommission: +```````````````````````````````````` + +ESR GUI Portal cannot decommission a cloud region which has been updated by +MultiCloud Plugin for Wind River Titanium Cloud, and it does not request +MultiCloud to help on that yet. So it is required to issue a rest API request +to MultiCloud with a single curl commands: + + +.. code-block:: console + + curl -X DELETE \ + 'http://$ONAP_MSB_IP:$ONAP_MSB_PORT/api/multicloud-titaniumcloud/v0/CloudOwner_RegionOne' \ + -H 'Accept: application/json' \ + -H 'Cache-Control: no-cache' \ + -H 'Content-Type: application/json' \ + -H 'Postman-Token: 8577e1cc-1038-471d-8b3b-d36fe44ae023' + + +.. include:: Tutorial-HPA-Provision-Discovery-WindRiver-TitaniumCloud.rst + + +.. include:: Tutorial-VESagent-MultiCloud-WindRiver-TitaniumCloud.rst -- cgit 1.2.3-korg From cc926e357bef56529a381457c631208f2f5cf09c Mon Sep 17 00:00:00 2001 From: Gildas Lanilis Date: Wed, 28 Nov 2018 16:33:39 -0800 Subject: Add links to Security Vulnerability Update RN by adding links to Security Vulnerability Change-Id: If91b6c4ec80f9bbe0fb032e10025e99082940ab9 Issue-ID: DOC-333 Signed-off-by: Gildas Lanilis Signed-off-by: Bin Yang --- docs/Release Notes.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/Release Notes.rst b/docs/Release Notes.rst index f183082..e9da04f 100644 --- a/docs/Release Notes.rst +++ b/docs/Release Notes.rst @@ -115,12 +115,20 @@ Version: 3.0.0 (Casablanca Release) **Security Notes** MULTICLOUD code has been formally scanned during build time using NexusIQ and -no Critical vulnerability were found. +all Critical vulnerabilities have been addressed, items that remain open have +been assessed for risk and determined to be false positive. + +The MULTICLOUD open Critical security vulnerabilities and their risk +assessment have been documented as part of the +`project `_. + Quick Links: - `MULTICLOUD project page `_ - `Passing Badge information for MULTICLOUD `_ + + - `Project Vulnerability Review Table for Multicloud `_ **Upgrade Notes** -- cgit 1.2.3-korg