diff options
| -rw-r--r-- | docs/release-notes.rst | 55 |
1 files changed, 19 insertions, 36 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index c0a2984c65..03824a826e 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -3,59 +3,42 @@ .. Copyright 2017 Huawei Intellectual Property. All rights reserved. -SO Release Notes -================ +Service Orchestrator Release Notes +================================== - +The SO provides the highest level of service orchestration in the ONAP architecture. Version: 1.1.0 -------------- - :Release Date: 2017-11-16 - **New Features** + The SO provides the highest level of service orchestration in the ONAP architecture. -SO is implemented via BPMN flows that operate on Models distributed from SDC that describe the Services and associated VNFs and other Resource components. -Cloud orchestration currently based on HEAT and TOSCA templates. -The orchestration engine is a reusable service. Any component of the architecture can execute process workflows. -Orchestration services can consume a process workflow and execute it. -The service model maintains consistency and reusability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment. -Orchestration processes interact with other platform components or external systems via standard and well-defined APIs. - -**Bug Fixes** -This is the initial release of ONAP SO. -Issues of the Ecomp 1710 release are fixed in this release. - -**Known Issues** -1. The articatfs of SO are under the openecomp/mso folder in nexus. - This is not impacting the release but is good to be moved to the ONAP -2. Current SO release does not support PNF orchestration. - The usecases demonstrated in ONAP Amsterdam release does not include PNF. -3. ARIA Plugin is not in full fledged in the current release. - The VNFs provided in the vCPE and vFW usecase are heat based and dont require ARIA. - -**Security Issues** -This is the initial release of ONAP SO. -Security aspects are not included in the current release. - -**Upgrade Notes** -This is the initial release of ONAP SO. +It executes end-to-end service activities by processing workflows and business logic and coordinating other ONAP and external component activities. + +The orchestration engine is a reusable service. Any component of the architecture can execute SO orchestration capabilities. + +* Orchestration services will process workflows based on defined models and recipe. +* The service model maintains consistency and reusability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment. +* Orchestration processes interact with other platform components or external systems via standard and well-defined APIs. + **Deprecation Notes** + There is a MSO 1.0.0 SO implementation existing in the pre-R1 ONAP Gerrit system. The MSO1.0.0 is deprecated by the R1 release and the current release is built over this release. The Gerrit repos of mso/* are voided and already locked as read-only. Following are the deprecated SO projects in gerrit repo: -mso -mso/chef-repo -mso/docker-config -mso/libs -mso/mso-config - +- mso +- mso/chef-repo +- mso/docker-config +- mso/libs +- mso/mso-config + **Other** =========== |