1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
3 .. Copyright 2018 Huawei Intellectual Property. All rights reserved.
6 Service Orchestrator Release Notes
7 ==================================
9 The SO provides the highest level of service orchestration in the ONAP architecture.
14 :Release Date: 2018-11-30
16 New release over master branch for Dublin development
21 :Release Date: 2018-11-30
23 This is the official release package that was tested against the 72 hour stability test in integration environment.
25 Casablanca Release branch
29 Features delivered in this release:
31 - Automatic scale out of VNFs.
32 - Extend the support of homing to vFW, vCPE usecases through HPA.
33 - Monitoring BPMN workflow capabilities through UI.
34 - SO internal architecture improvements.
35 - Support PNF resource type.
36 - Support to the CCVPN Usecase.
37 - Workflow Designer Integration.
41 Dockers released for SO:
43 - onap/so/api-handler-infra,1.3.3
44 - onap/so/bpmn-infra,1.3.3
45 - onap/so/catalog-db-adapter,1.3.3
46 - onap/so/openstack-adapter,1.3.3
47 - onap/so/request-db-adapter,1.3.3
48 - onap/so/sdc-controller,1.3.3
49 - onap/so/sdnc-adapter,1.3.3
50 - onap/so/so-monitoring,1.3.3
51 - onap/so/vfc-adapter,1.3.3
55 There are some issues around the HPA and CCVPN that have been resolved in the patch release of 1.3.5
57 - `SO-1249 <https://jira.onap.org/browse/SO-1249>`_
58 The workflow for resource processing use the wrong default value.
60 - `SO-1257 <https://jira.onap.org/browse/SO-1257>`_
61 Authorization header added to multicloud adapter breaks communication.
63 - `SO-1258 <https://jira.onap.org/browse/SO-1258>`_
64 OOF Directives are not passed through flows to Multicloud Adapter.
66 - `SO-1256 <https://jira.onap.org/browse/SO-1256>`_
67 Permission support for Vfcadapter is missing.
69 - `SO-1194 <https://jira.onap.org/browse/SO-1194>`_
70 Unable to find TOSCA CSAR location using ServiceModelUUID in DoCreateResource BPMN flow.
73 Below issues will be resolved in the next release:
75 - `SO-1248 <https://jira.onap.org/browse/SO-1248>`_
76 Csar needs to be manually placed into the bpmn corresponding directory.
78 - `SO-1184 <https://jira.onap.org/browse/SO-1184>`_
79 Database table is not populated for Generic NeutronNet resource.
84 SO code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The SO open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=43385708>`_.
88 - `SO project page <https://wiki.onap.org/display/DW/Service+Orchestrator+Project>`_
89 - `Passing Badge information for SO <https://bestpractices.coreinfrastructure.org/en/projects/1702>`_
90 - `Project Vulnerability Review Table for SO <https://wiki.onap.org/pages/viewpage.action?pageId=43385708>`_
95 :Release Date: 2018-10-24
97 Branch cut for Casablanca post M4 for integration test.
100 Below features are under test:
101 - Automatic scale out of VNFs.
102 - Extend the support of homing to vFW, vCPE usecases through HPA.
103 - Monitoring BPMN workflow capabilities through UI.
104 - SO internal architecture improvements.
105 - Support PNF resource type.
106 - Support to the CCVPN Usecase.
107 - Workflow Designer Integration.
113 :Release Date: 2018-08-22
115 New release over master branch for Casablanca development
120 :Release Date: 2018-06-07
122 The Beijing release is the second release of the Service Orchestrator (SO) project.
126 * Enhance Platform maturity by improving SO maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
127 * Manual scaling of network services and VNFs.
128 * Homing and placement capabilities through OOF interaction.
129 * Ability to perform change management.
136 The defects fixed in this release could be found `here <https://jira.onap.org/issues/?jql=project%20%3D%20SO%20AND%20affectedVersion%20%3D%20%22Beijing%20Release%22%20AND%20status%20%3D%20Closed%20>`_.
140 SO docker image is still on ecmop and not onap in the repository.
141 This will be addressed in the next release.
145 SO code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The SO open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=28377799>`_.
149 - `SO project page <https://wiki.onap.org/display/DW/Service+Orchestrator+Project>`_
150 - `Passing Badge information for SO <https://bestpractices.coreinfrastructure.org/en/projects/1702>`_
151 - `Project Vulnerability Review Table for SO <https://wiki.onap.org/pages/viewpage.action?pageId=28377799>`_
156 **Deprecation Notes**
162 :Release Date: 2018-01-18
166 The key defects fixed in this release :
168 - `SO-344 <https://jira.onap.org/browse/SO-344>`_
169 Only pass one VNF to DoCreateVnfAndModules.
171 - `SO-348 <https://jira.onap.org/browse/SO-348>`_
172 Json Analyze Exception in PreProcessRequest.
174 - `SO-352 <https://jira.onap.org/browse/SO-352>`_
175 SO failed to create VNF - with error message: Internal Error Occurred in CreateVnfInfra QueryCatalogDB Process.
177 - `SO-354 <https://jira.onap.org/browse/SO-354>`_
178 Change the Service Type And Service Role
184 :Release Date: 2017-11-16
189 The SO provides the highest level of service orchestration in the ONAP architecture.
190 It executes end-to-end service activities by processing workflows and business logic and coordinating other ONAP and external component activities.
192 The orchestration engine is a reusable service. Any component of the architecture can execute SO orchestration capabilities.
194 * Orchestration services will process workflows based on defined models and recipe.
195 * The service model maintains consistency and re-usability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
196 * Orchestration processes interact with other platform components or external systems via standard and well-defined APIs.
199 **Deprecation Notes**
201 There is a MSO 1.0.0 SO implementation existing in the pre-R1 ONAP Gerrit system.
202 The MSO1.0.0 is deprecated by the R1 release and the current release is built over this release.
203 The Gerrit repos of mso/* are voided and already locked as read-only.
204 Following are the deprecated SO projects in gerrit repo: