.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. _vfc_index:
+VF-C(Virtual Function Controller)
+---------------------------------
-ONAP VF-C
-=========
+As part of the integration between OpenECOMP and OPEN-O, this proposed project VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements full life cycle management and FCAPS of VNF and NS.
-As part of the integration between OpenECOMP and OPEN-O, VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements life cycle management and FCAPS of VNF and NS.
-
-* support NS and VNF lifecycle management based on the ONAP tosca and yang data model and workflow
-* support integration with multi VNFMs via drivers, which include vendors VNFM and generic VNFM
-* support integration with multi VNFs via generic VNFM, which does not provide VNFM function
-* support integration with multi VIMS via Multi-VIM, which include the opensource and commercial VIMs
-* support microservice architecture and model driven resource orchestration and management
+This document is aimed to give the users some brief introductions on VF-C from different aspects. The users could find useful information, e.g. the architecuture, the APIs and the installation steps, etc. as well as the release notes of VF-C in this document.
.. toctree::
:maxdepth: 1
+
+ platform/index.rst
+ release-notes.rst
- architecture.rst
- delivery.rst
- APIs/index
- installation.rst
--- /dev/null
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+.. _vfc_index:
+
+ONAP VF-C
+=========
+
+As part of the integration between OpenECOMP and OPEN-O, VF-C leverages ETSI NFV MANO architecture and information model as a reference, and implements life cycle management and FCAPS of VNF and NS.
+
+* support NS and VNF lifecycle management based on the ONAP tosca and yang data model and workflow
+* support integration with multi VNFMs via drivers, which include vendors VNFM and generic VNFM
+* support integration with multi VNFs via generic VNFM, which does not provide VNFM function
+* support integration with multi VIMS via Multi-VIM, which include the opensource and commercial VIMs
+* support microservice architecture and model driven resource orchestration and management
+
+
+.. toctree::
+ :maxdepth: 1
+
+ architecture.rst
+ delivery.rst
+ APIs/index
+ installation.rst
::
- docker run -d --name vfc-resmanagement -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/resmanagement
-
-For testing, we can use curl command to access the swagger api.
-
-::
-
- curl http://${MSB_IP}:80/api/resmgr/v1/swagger.json
-
-- Install vfc-nfvo-resmanagement component.
-
-::
-
- docker run -d --name vfc-resmanagement -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/resmanagement
+ docker run -d --name vfc-resmanagement -p 8480:8480 -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/resmanagement
For testing, we can use curl command to access the swagger api.
::
- docker run -d --name vfc-emsdriver -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/emsdriver
+ docker run -d --name vfc-emsdriver -p 8206:8206 -e MSB_ADDR=${MSB_IP}:80 -e VES_ADDR=${VES_COLLECTOR_IP}:8080 -e VES_AUTHINFO="":"" nexus3.onap.org:10001/onap/vfc/emsdriver
For testing, we can use curl command to access the swagger api.
::
docker run -d --name vfc-gvnfmdriver -p 8484:8484 -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/gvnfmdriver
- docker run -d --name vfc-jujudriver -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/jujudriver
+ docker run -d --name vfc-jujudriver -p 8483:8483 -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/jujudriver
For testing, we can use curl command to access the swagger api.
::
curl http://${MSB_IP}:80/api/gvnfmdriver/v1/swagger.json
- curl http://${MSB_IP}:80/openoapi/jujuvnfm/v1/swagger.json
+ curl http://${MSB_IP}:80/api/jujuvnfmdriver/v1/swagger.json
- Install vfc-svnfmdriver components.
::
docker run -d --name vfc-ztevmanagerdriver -p 8410:8410 -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/ztevmanagerdriver
- docker run -d --name vfc-svnfm-huawei -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/nfvo/svnfm/huawei
- docker run -d --name vfc-svnfm-nokia -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/nfvo/svnfm/nokia
+ docker run -d --name vfc-svnfm-huawei -p 8482:8482 -p 8443:8443 -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/nfvo/svnfm/huawei
+ docker run -d --name vfc-svnfm-nokia -p 8486:8486 -e MSB_ADDR=${MSB_IP}:80 nexus3.onap.org:10001/onap/vfc/nfvo/svnfm/nokia
For testing, we can use curl command to access the swagger api.
::
curl http://${MSB_IP}:80/api/ztevmanagerdriver/v1/swagger.json
- curl http://${MSB_IP}:80/api/hwvnfm/v1/swagger.json
+ curl http://${MSB_IP}:80/api/huaweivnfmdriver/v1/swagger.json
curl http://${MSB_IP}:80/api/nokiavnfmdriver/v1/swagger.json
--- /dev/null
+.. 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
"description": "vim",
"domain": "",
"type": ignore_case_get(esr_system_info[0], "type"),
- "createTime": "2016-07-18 12:22:53"
+ "createTime": "2016-07-18 12:22:53",
+ "sslCacert": ignore_case_get(esr_system_info[0], "ssl-cacert"),
+ "sslInsecure": ignore_case_get(esr_system_info[0], "ssl-insecure"),
+ "status": ignore_case_get(esr_system_info[0], "system-status")
}
return vim_info
},
"name": {
"type": "string",
- "description": "vnfm name"
+ "description": "vim name"
},
"type": {
"type": "string",
- "description": "vnfm type"
+ "description": "vim type"
},
"url": {
"type": "string",
- "description": "vnfm url"
+ "description": "vim url"
},
"userName": {
"type": "string",
- "description": "vnfm login username"
+ "description": "vim login username"
},
"password": {
"type": "string",
- "description": "vnfm login password"
+ "description": "vim login password"
},
"vendor": {
"type": "string",
},
"version": {
"type": "string",
- "description": "vnfm version"
+ "description": "vim version"
},
"description": {
"type": "string",
- "description": "vnfm description"
+ "description": "vim description"
},
"createTime": {
"type": "string",
- "description": "vnfm info createTime"
+ "description": "vim info createTime"
+ },
+ "sslCacert": {
+ "type": "string",
+ "description": "CA file content if enabled ssl on auth-url"
+ },
+ "sslInsecure": {
+ "type": "string",
+ "description": "Whether to verify VIM's certificate"
+ },
+ "status": {
+ "type": "string",
+ "description": "The status of external system"
}
}
}
Code Review / vfc / nfvo / lcm.git / commitdiff
