Update relesae notes 51/72151/1
authoryangyan <yangyanyj@chinamobile.com>
Thu, 8 Nov 2018 02:23:38 +0000 (10:23 +0800)
committeryangyan <yangyanyj@chinamobile.com>
Thu, 8 Nov 2018 02:24:40 +0000 (10:24 +0800)
Change-Id: Id38e919a312e935facc9bd579e0a83a47ccb348b
Issue-ID: VFC-1181
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
docs/release-notes.rst

index 75cde29..9bd38d9 100644 (file)
@@ -11,6 +11,72 @@ orchestration and close loop automation by working with SO, DCAE and Policy.
 VF-C also provides standard southbound interface to VNFMs and can integrate
 with multi vendor VNFMs via drivers.
 
+Version: 1.2.0
+--------------
+
+:Release Date: 2018-11-15
+
+**New Features**
+
+- NS Orchestration supports PNF:1.NSLCM supports NSD, composed of VNF, PNF, and VL;2.Catalog supports PNFD and updates NSD DM
+- Hardware Platform Awareness (HPA) Support:1.integrate with OOF;2.VF-C can parse R2+ TOSCA MODEL which includes HPA feature
+- Standard Alignment:SOL003 Alignment in GVNFM and Catalog
+- Standalone DB Microservice
+
+Released components:
+
+NFVO
+ - vfc-nfvo-lcm
+ - vfc-nfvo-catalog
+ - vfc-nfvo-resmgr
+ - vfc-nfvo-driver-emsdriver
+ - vfc-nfvo-driver-gvnfm-gvnfmadapter
+ - vfc-nfvo-driver-gvnfm-jujudriver
+ - vfc-nfvo-driver-svnfm-ztedriver
+ - vfc-nfvo-driver-svnfm-huaweidriver
+ - vfc-nfvo-driver-svnfm-nokiav2driver
+ - vfc-nfvo-driver-sfc-ztesfcdriver
+ - vfc-nfvo-multivimproxy
+ - vfc-nfvo-db 
+GVNFM
+ - vfc-gvnfm-vnflcm
+ - vfc-gvnfm-vnfmgr
+ - vfc-gvnfm-vnfres
+Workflow
+ - workflow-engine-mgr-service
+ - activiti-extension
+
+**Bug Fixes**
+
+**Known Issues**
+
+ - `VFC-896 <https://jira.onap.org/browse/VFC-896>`_  vim-id in AAI is handled as a mandatory parameter
+ - `VFC-890 <https://jira.onap.org/browse/VFC-890>`_  The hard coded SDC user and password in catalog & LCM is not present in SDC
+ - `VFC-891 <https://jira.onap.org/browse/VFC-891>`_  The AAI credentials is hard coded in LCM
+
+**Security Notes**
+
+VFC 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 VFC open Critical security
+vulnerabilities and their risk assessment have been documented as part
+of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=45298878>`_.
+
+Quick Links:
+
+- `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
+- `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
+- `Project Vulnerability Review Table for VFC <https://wiki.onap.org/pages/viewpage.action?pageId=45298878>`_
+
+**Upgrade Notes**
+       NA
+
+**Deprecation Notes**
+       NA
+
+**Other**
+       NA
+
 Version: 1.1.0
 --------------