1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
2 .. http://creativecommons.org/licenses/by/4.0
9 VF-C includes two main components, NFV-O and GVNFM, to implement life cycle
10 management and FCAPS of VNF and NS. VF-C takes part in end to end service
11 orchestration and close loop automation by working with SO, DCAE and Policy.
12 VF-C also provides standard southbound interface to VNFMs and can integrate
13 with multi vendor VNFMs via drivers.
19 :Release Date: 2020-10-29
23 - Functional Enhancement:
25 1. Improve instance storage function
26 2. Remove components which are no longer used or maintained.
28 - Maturity Enhancement:
31 2. Optimize docker image
32 3. Update dependency lib
33 4. Increase code coverage
40 - vfc-nfvo-driver-gvnfm-gvnfmadapter 1.4.0
41 - vfc-nfvo-driver-svnfm-ztedriver 1.3.8
42 - vfc-nfvo-driver-svnfm-huawei 1.3.8
46 - vfc-gvnfm-vnflcm 1.4.0
47 - vfc-gvnfm-vnfmgr 1.3.9
48 - vfc-gvnfm-vnfres 1.3.8
52 Though VFC itself has migrated to python 3, however, the deployment of VFC still has python 2.7 pods since it uses public mariadb image. Please refer to: https://jira.onap.org/browse/VFC-1740 for details.
60 - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
61 - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
68 The following components are not in the scope of the Guilin release since they are no longer used or maintained.
71 - vfc/nfvo/multivimproxy
72 - vfc/nfvo/driver/vnfm/gvnfm/juju
73 - vfc/nfvo/driver/vnfm/svnfm/nokia
84 :Release Date: 2020-03-17
88 - Functional Enhancement:
90 1. Migrate VF-C catalog to Modeling etsicatalog
91 2. Using the common database (MariaDB) and encrypting the database password.
92 3. Remove the root permission and change the user of VFC project to ONAP.
93 4. Add the function of auto register MSB switch for startup project.
94 5. Increase the communication access form between components through the HTTPS encrypted access form of MSB.
95 6. SOL005 compliance NS instantiation, query and termination commands have been added to cli.
98 - Maturity Enhancement:
100 1. Enhance the security of database access
101 2. Enhance the stability of instantiation process and improve efficiency and productivity.
102 3. Improve the stability of instance termination process and deletion process, and improve the success rate of subscription record deletion.
103 4. Adapt to MSB https for microservice service registration and access.
110 - vfc-nfvo-resmanagement 1.3.1
111 - vfc-nfvo-driver-gvnfm-gvnfmadapter 1.3.9
112 - vfc-nfvo-driver-gvnfm-juju 1.3.9
113 - vfc-nfvo-driver-svnfm-ztedriver 1.3.6
114 - vfc-nfvo-driver-svnfm-huawei 1.3.6
115 - vfc-nfvo-driver-svnfm-Nokia2 1.3.6
119 - vfc-nfvo-multivimproxy 1.3.1
120 - vfc-nfvo-wfengine-mgrservice 1.3.3
121 - vfc-nfvo-wfengine-activiti 1.3.3
124 - vfc-gvnfm-vnflcm 1.3.9
125 - vfc-gvnfm-vnfmgr 1.3.8
126 - vfc-gvnfm-vnfres 1.3.7
130 - Fix bug for duplication query and delete vserver and network in AAI resource during terminating ns.
131 - Fix terminate ns API is unstable.
132 - Fix bug for fail to delete subscription for vnfm during terminating ns.
133 - Fix the bug for fail parse contextArray, initial it to [].
134 - Fix the deduplication AAI resource issues.
135 - Fix the bug of vim_id data type error when creating vnfs.
136 - Fix the failure of parsing the acquired data format during SFC creation.
137 - Fix the failure of blocking due to multithreading during instantiation.
147 - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
148 - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
149 - `CLI command about VFC operation <https://onap.readthedocs.io/en/latest/submodules/vfc/nfvo/lcm.git/docs/platform/cli-userguide/index.html#vfc-part>`_
154 **Deprecation Notes**
166 :Release Date: 2019-08-20
170 - Functional Enhancement:
172 1. Upgrade component environments from Python 2 to Python 3 and upgrade package dependencies to stable versions
173 2. Good connectivity and stability of information transmission between nslcm drivers and vnflcm
174 3. Solving Layer_protocol Protocol Protocol Supporting Uniformity and Increasing Compatibility
176 - Standard Alignment-SOL005 Alignment
178 - Maturity Enhancement:
180 1. Increase read and write stability of AAI interaction
181 2. Enhance the stability of vnflcm and nslcm message subscription notification function
182 3. Enhance the reliability of MSB registration information and message reading
190 - vfc-nfvo-catalog 1.3.4
191 - vfc-nfvo-driver-gvnfm-gvnfmadapter 1.3.5
192 - vfc-nfvo-driver-svnfm-ztedriver 1.3.3
195 - vfc-gvnfm-vnflcm 1.3.4
196 - vfc-gvnfm-vnfmgr 1.3.4
197 - vfc-gvnfm-vnfres 1.3.4
201 - Fix bug for failure in creating subscriptions for vnfm
202 - Fix network name conflict problem when creating network writing to AAI
203 - Fix bug for failure in creating ns vl to aai
204 - Fix the bug for table NFVO_NSINST field status update incorrect
211 VFC code has been formally scanned during build time using NexusIQ and all Critical
212 vulnerabilities have been addressed, items that remain open have been assessed
213 for risk and determined to be false positive. The VFC open Critical security
214 vulnerabilities and their risk assessment have been documented as part
215 of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=68542814>`_.
219 - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
220 - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
221 - `Project Vulnerability Review Table for VFC <https://wiki.onap.org/pages/viewpage.action?pageId=68542814>`_
226 **Deprecation Notes**
238 :Release Date: 2019-06-06
242 - Functional Enhancement:
244 1. Upgrade Multicloud API to support consistent identification of cloud region functional requirement
245 2. OOF Integration Optimization.Optimize the methodology for VNF(vdu) placement, add the process for placement with selected candidates(VIM)
246 3. Align VNFD SOL2.5.1 and model multi-version support
248 - Standard Alignment-SOL005 Alignment
250 - Maturity Enhancement:
252 1. Mysql DB migrate to OOM shared MariaDB Galera Cluster
253 2. Configuration inject automatically
254 3. Add data persistent storage to avoid data loss due to pod restart
262 - vfc-nfvo-catalog 1.3.2
263 - vfc-nfvo-resmgr 1.3.0
264 - vfc-nfvo-driver-emsdriver 1.3.0
265 - vfc-nfvo-driver-gvnfm-gvnfmadapter 1.3.3
266 - vfc-nfvo-driver-gvnfm-jujudriver 1.3.1
267 - vfc-nfvo-driver-svnfm-ztedriver 1.3.1
268 - vfc-nfvo-driver-svnfm-huaweidriver 1.3.0
269 - vfc-nfvo-driver-svnfm-nokiav2driver 1.3.1
270 - vfc-nfvo-driver-sfc-ztesfcdriver 1.3.1
271 - vfc-nfvo-multivimproxy 1.3.0
274 - vfc-gvnfm-vnflcm 1.3.2
275 - vfc-gvnfm-vnfmgr 1.3.2
276 - vfc-gvnfm-vnfres 1.3.2
278 - workflow-engine-mgr-service 1.3.0
279 - activiti-extension 1.3.0
285 - `VFC-1402 <https://jira.onap.org/browse/VFC-1402>`_ Lost connection to Mariadb server during query in vnflcm.
286 - `VFC-1411 <https://jira.onap.org/browse/VFC-1411>`_ The network can not be deleted in ns terminate.
290 VFC code has been formally scanned during build time using NexusIQ and all Critical
291 vulnerabilities have been addressed, items that remain open have been assessed
292 for risk and determined to be false positive. The VFC open Critical security
293 vulnerabilities and their risk assessment have been documented as part
294 of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=51282550>`_.
298 - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
299 - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
300 - `Project Vulnerability Review Table for VFC <https://wiki.onap.org/pages/viewpage.action?pageId=51282550>`_
305 **Deprecation Notes**
314 :Release Date: 2018-11-30
318 - NS Orchestration supports PNF:1.NSLCM supports NSD, composed of VNF, PNF, and VL;2.Catalog supports PNFD and updates NSD DM
319 - Hardware Platform Awareness (HPA) Support:1.integrate with OOF;2.VF-C can parse R2+ TOSCA MODEL which includes HPA feature
320 - Standard Alignment:SOL003 Alignment in GVNFM and Catalog
321 - Standalone DB Microservice
327 - vfc-nfvo-catalog 1.2.2
328 - vfc-nfvo-resmgr 1.2.1
329 - vfc-nfvo-driver-emsdriver 1.2.1
330 - vfc-nfvo-driver-gvnfm-gvnfmadapter 1.2.2
331 - vfc-nfvo-driver-gvnfm-jujudriver 1.2.1
332 - vfc-nfvo-driver-svnfm-ztedriver 1.2.1
333 - vfc-nfvo-driver-svnfm-huaweidriver 1.2.1
334 - vfc-nfvo-driver-svnfm-nokiav2driver 1.2.1
335 - vfc-nfvo-driver-sfc-ztesfcdriver 1.2.0
336 - vfc-nfvo-multivimproxy 1.2.1
339 - vfc-gvnfm-vnflcm 1.2.2
340 - vfc-gvnfm-vnfmgr 1.2.1
341 - vfc-gvnfm-vnfres 1.2.1
343 - workflow-engine-mgr-service
350 - `VFC-896 <https://jira.onap.org/browse/VFC-896>`_ vim-id in AAI is handled as a mandatory parameter
351 - `VFC-890 <https://jira.onap.org/browse/VFC-890>`_ The hard coded SDC user and password in catalog & LCM is not present in SDC
352 - `VFC-891 <https://jira.onap.org/browse/VFC-891>`_ The AAI credentials is hard coded in LCM
353 - SDC-1897 - Parser exported CSAR with error OPEN (Will be fixed at Dublin),VFC could ignore that error. To ignore that error, we need either apply the patch at https://jira.opnfv.org/browse/PARSER-187 locally in nfv-toscaparser which VFC uses or wait for nfv-toscaparser got that fixed.
357 VFC code has been formally scanned during build time using NexusIQ and all Critical
358 vulnerabilities have been addressed, items that remain open have been assessed
359 for risk and determined to be false positive. The VFC open Critical security
360 vulnerabilities and their risk assessment have been documented as part
361 of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=45298878>`_.
365 - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
366 - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
367 - `Project Vulnerability Review Table for VFC <https://wiki.onap.org/pages/viewpage.action?pageId=45298878>`_
372 **Deprecation Notes**
381 :Release Date: 2018-06-07
385 - NS/VNF manual scaling supporting for VoLTE use case
386 - VNF Integration, integration with VNF via GVNFM
395 - vfc-nfvo-driver-emsdriver
396 - vfc-nfvo-driver-gvnfm-gvnfmadapter
397 - vfc-nfvo-driver-gvnfm-jujudriver
398 - vfc-nfvo-driver-svnfm-ztedriver
399 - vfc-nfvo-driver-svnfm-huaweidriver
400 - vfc-nfvo-driver-svnfm-nokiadriver
401 - vfc-nfvo-driver-svnfm-nokiav2driver
402 - vfc-nfvo-driver-sfc-ztesfcdriver
403 - vfc-nfvo-multivimproxy
409 - workflow-engine-mgr-service
414 This is the initial release
418 - `VFC-896 <https://jira.onap.org/browse/VFC-896>`_ vim-id in AAI is handled as a mandatory parameter
419 - `VFC-890 <https://jira.onap.org/browse/VFC-890>`_ The hard coded SDC user and password in catalog & LCM is not present in SDC
420 - `VFC-891 <https://jira.onap.org/browse/VFC-891>`_ The AAI credentials is hard coded in LCM
424 VFC code has been formally scanned during build time using NexusIQ and all Critical
425 vulnerabilities have been addressed, items that remain open have been assessed
426 for risk and determined to be false positive. The VFC open Critical security
427 vulnerabilities and their risk assessment have been documented as part
428 of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=25437810>`_.
432 - `VFC project page <https://wiki.onap.org/display/DW/Virtual+Function+Controller+Project>`_
433 - `Passing Badge information for VFC <https://bestpractices.coreinfrastructure.org/en/projects/1608>`_
434 - `Project Vulnerability Review Table for VFC <https://wiki.onap.org/pages/viewpage.action?pageId=25437810>`_
439 **Deprecation Notes**
448 :Release Date: 2017-11-16
452 - NS lifecycle management, including NS instance creation, termination and healing
453 - VNF lifecycle management, including VNF instance creation, termination and healing
454 - VNF FCAPS, collecting FCAPS data from vendor EMS
455 - VNFM Integration, integration with specific VNFMs of vendors to deploy commercial VNFs
456 - VNF Integration, integration with VNF via GVNFM
464 - vfc-nfvo-driver-emsdriver
465 - vfc-nfvo-driver-gvnfm-gvnfmadapter
466 - vfc-nfvo-driver-gvnfm-jujudriver
467 - vfc-nfvo-driver-svnfm-ztedriver
468 - vfc-nfvo-driver-svnfm-huaweidriver
469 - vfc-nfvo-driver-svnfm-nokiadriver
470 - vfc-nfvo-driver-sfc-ztesfcdriver
476 - workflow-engine-mgr-service
481 This is the initial release
493 This is the initial release
495 **Deprecation Notes**
497 This is the initial release