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 This is the official release package that was tested against the 72 hour stability test in integration environment.
18 Casablanca Release branch
22 Features delivered in this release:
24 - Automatic scale out of VNFs.
25 - Extend the support of homing to vFW, vCPE usecases through HPA.
26 - Monitoring BPMN workflow capabilities through UI.
27 - SO internal architecture improvements.
28 - Support PNF resource type.
29 - Support to the CCVPN Usecase.
30 - Workflow Designer Integration.
34 Dockers released for SO:
36 - onap/so/api-handler-infra,1.3.3
37 - onap/so/bpmn-infra,1.3.3
38 - onap/so/catalog-db-adapter,1.3.3
39 - onap/so/openstack-adapter,1.3.3
40 - onap/so/request-db-adapter,1.3.3
41 - onap/so/sdc-controller,1.3.3
42 - onap/so/sdnc-adapter,1.3.3
43 - onap/so/so-monitoring,1.3.3
44 - onap/so/vfc-adapter,1.3.3
48 There are some issues around the HPA and CCVPN that have been resolved in the patch release of 1.3.4
49 - `SO-1249 <https://jira.onap.org/browse/SO-1249>`_
51 Below issues will be resolved in the next release:
53 - `SO-1258 <https://jira.onap.org/browse/SO-1258>`_
54 - `SO-1257 <https://jira.onap.org/browse/SO-1257>`_
55 - `SO-1256 <https://jira.onap.org/browse/SO-1256>`_
56 - `SO-1248 <https://jira.onap.org/browse/SO-1248>`_
61 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>`_.
65 - `SO project page <https://wiki.onap.org/display/DW/Service+Orchestrator+Project>`_
66 - `Passing Badge information for SO <https://bestpractices.coreinfrastructure.org/en/projects/1702>`_
67 - `Project Vulnerability Review Table for SO <https://wiki.onap.org/pages/viewpage.action?pageId=43385708>`_
72 :Release Date: 2018-10-24
74 Branch cut for Casablanca post M4 for integration test.
77 Below features are under test:
78 * Support PNF resource type.
79 * Extend the support of homing to vFW, VDNS usecases.
80 * Workflow Designer Integration.
81 * Monitoring BPMN worflow capabilities through UI.
82 * Support to the CCVPN Usecase.
83 * SO internal architecture improvements
88 :Release Date: 2018-08-22
90 New release over master branch for Casablanca development
95 :Release Date: 2018-06-07
97 The Beijing release is the second release of the Service Orchestrator (SO) project.
101 * Enhance Platform maturity by improving SO maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
102 * Manual scaling of network services and VNFs.
103 * Homing and placement capabilities through OOF interaction.
104 * Ability to perform change management.
111 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>`_.
115 SO docker image is still on ecmop and not onap in the repository.
116 This will be addressed in the next release.
120 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>`_.
124 - `SO project page <https://wiki.onap.org/display/DW/Service+Orchestrator+Project>`_
125 - `Passing Badge information for SO <https://bestpractices.coreinfrastructure.org/en/projects/1702>`_
126 - `Project Vulnerability Review Table for SO <https://wiki.onap.org/pages/viewpage.action?pageId=28377799>`_
131 **Deprecation Notes**
137 :Release Date: 2018-01-18
141 The key defects fixed in this release :
143 - `SO-344 <https://jira.onap.org/browse/SO-344>`_
144 Only pass one VNF to DoCreateVnfAndModules.
146 - `SO-348 <https://jira.onap.org/browse/SO-348>`_
147 Json Analyze Exception in PreProcessRequest.
149 - `SO-352 <https://jira.onap.org/browse/SO-352>`_
150 SO failed to create VNF - with error message: Internal Error Occurred in CreateVnfInfra QueryCatalogDB Process.
152 - `SO-354 <https://jira.onap.org/browse/SO-354>`_
153 Change the Service Type And Service Role
159 :Release Date: 2017-11-16
164 The SO provides the highest level of service orchestration in the ONAP architecture.
165 It executes end-to-end service activities by processing workflows and business logic and coordinating other ONAP and external component activities.
167 The orchestration engine is a reusable service. Any component of the architecture can execute SO orchestration capabilities.
169 * Orchestration services will process workflows based on defined models and recipe.
170 * The service model maintains consistency and re-usability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
171 * Orchestration processes interact with other platform components or external systems via standard and well-defined APIs.
174 **Deprecation Notes**
176 There is a MSO 1.0.0 SO implementation existing in the pre-R1 ONAP Gerrit system.
177 The MSO1.0.0 is deprecated by the R1 release and the current release is built over this release.
178 The Gerrit repos of mso/* are voided and already locked as read-only.
179 Following are the deprecated SO projects in gerrit repo: