diff options
author | Yan Yang <yangyanyj@chinamobile.com> | 2017-11-01 05:24:19 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@onap.org> | 2017-11-01 05:24:19 +0000 |
commit | 1963d5088a1937c3308104a90bbe86dcdc12330a (patch) | |
tree | 7c704933aabb751fc0c0a0cd93925495298dad2b /docs/release-notes.rst | |
parent | 635886dfc12300038ef096d08f8eb4c09ce075a4 (diff) | |
parent | ad8793f9b4a4de8fe8aa37c80d6746403631528f (diff) |
Merge "Update VF-C doc"
Diffstat (limited to 'docs/release-notes.rst')
-rw-r--r-- | docs/release-notes.rst | 54 |
1 files changed, 54 insertions, 0 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst new file mode 100644 index 00000000..f06fbc90 --- /dev/null +++ b/docs/release-notes.rst @@ -0,0 +1,54 @@ +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 + + +VF-C 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. + +VF-C includes two main component:NFV-O and GVNFM, can implement life cycle management and FCAPS of VNF and NS. VF-C takes part in end2end service orchestration and close loop automatiion by working with SO,DCAE and Policy. +VF-C also provides standard south bound interface to VNFMs and can integration with multi vendor VNFMs via drivers. + + + +Version: x.y.z +-------------- + + +:Release Date: yyyy-mm-dd + + + +**New Features** + + - + - NS lifecycle management, including NS instance creation,termination and healing + - VNF lifecycle management, including VNF nstance creation,termination and healing + - VNF FCAPS, collecting FCAPS data from vendor EMS + - VNFM Integration, Integration with specific VNFMs of vendors to deploy commercial VNFs + - VNF Integration, Integration with VNF via GVNFM + + +**Bug Fixes** + + +**Known Issues** + +**Security Issues** + + +**Upgrade Notes** + +**Deprecation Notes** + +**Other** + +=========== + +End of Release Notes |