Correcting the namespace template for SO
IssueId : SO-300
Change-Id: Ifc45cdc7944d53097fc206e1d1fbb219228133c3
Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com>
diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 7c7c137..207d0be 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -6,43 +6,54 @@
Service Orchestrator Release Notes
==================================
-.. note::
- * This Release Notes must be updated each time the team decides to Release new artifacts.
- * The scope of this Release Notes is for this particular component. In other words, each ONAP component has its Release Notes.
- * This Release Notes is cumulative, the most recently Released artifact is made visible in the top of this Release Notes.
- * Except the date and the version number, all the other sections are optional but there must be at least one section describing the purpose of this new release.
- * This note must be removed after content has been added.
Version: 1.1.0
--------------
-:Release Date: yyyy-mm-dd
+:Release Date: 2017-11-16
**New Features**
- Initial release of Service Orchestrator (SO) for Open Network Automation Platform (ONAP)
-
+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**
- - ``_ and a sentence explaining what this defect is addressing.
+This is the initial release of ONAP SO.
+Issues of the Ecomp 1710 release are fixed in this release.
+
**Known Issues**
- - ``_ and two, three sentences.
- One sentences explaining what is the issue.
-
- Another sentence explaining the impact of the issue.
-
- And an optional sentence providing a workaround.
+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**
- You may want to include a reference to CVE (Common Vulnerabilities and Exposures) `CVE <https://cve.mitre.org>`_
-
+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.
**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.
+Deprecated SO projects in gerrit repo.
+mso
+mso/chef-repo
+mso/docker-config
+mso/libs
+mso/mso-config
**Other**