blob: 4ca1a01953ee76bb9f62751a3a9bffb404f87c73 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. Copyright 2018 Huawei Intellectual Property. All rights reserved.
Service Orchestrator Release Notes
==================================
The SO provides the highest level of service orchestration in the ONAP architecture.
Version: 1.3.1
--------------
:Release Date: 2018-10-24
Branch cut for Casablanca post M4 for integration test.
**New Features**
Below features are under test:
* Support PNF resource type.
* Extend the support of homing to vFW, VDNS usecases.
* Workflow Designer Integration.
* Monitoring BPMN worflow capabilities through UI.
* Support to the CCVPN Usecase.
* SO internal architecture improvements
Version: 1.3.0
--------------
:Release Date: 2018-08-22
New release over master branch for Casablanca development
Version: 1.2.2
--------------
:Release Date: 2018-06-07
The Beijing release is the second release of the Service Orchestrator (SO) project.
**New Features**
* Enhance Platform maturity by improving SO maturity matrix see `Wiki <https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity>`_.
* Manual scaling of network services and VNFs.
* Homing and placement capabilities through OOF interaction.
* Ability to perform change management.
* Integrated to APPC
* Integrated to OOF
* Integrated to OOM
**Bug Fixes**
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>`_.
**Known Issues**
SO docker image is still on ecmop and not onap in the repository.
This will be addressed in the next release.
**Security Notes**
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>`_.
Quick Links:
- `SO project page <https://wiki.onap.org/display/DW/Service+Orchestrator+Project>`_
- `Passing Badge information for SO <https://bestpractices.coreinfrastructure.org/en/projects/1702>`_
- `Project Vulnerability Review Table for SO <https://wiki.onap.org/pages/viewpage.action?pageId=28377799>`_
**Upgrade Notes**
NA
**Deprecation Notes**
NA
Version: 1.1.2
--------------
:Release Date: 2018-01-18
Bug Fixes
---------
The key defects fixed in this release :
- `SO-344 <https://jira.onap.org/browse/SO-344>`_
Only pass one VNF to DoCreateVnfAndModules.
- `SO-348 <https://jira.onap.org/browse/SO-348>`_
Json Analyze Exception in PreProcessRequest.
- `SO-352 <https://jira.onap.org/browse/SO-352>`_
SO failed to create VNF - with error message: Internal Error Occurred in CreateVnfInfra QueryCatalogDB Process.
- `SO-354 <https://jira.onap.org/browse/SO-354>`_
Change the Service Type And Service Role
Version: 1.1.1
--------------
:Release Date: 2017-11-16
**New Features**
The SO provides the highest level of service orchestration in the ONAP architecture.
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 re-usability 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
**Other**
NA
===========
End of Release Notes
|
