Hi VF-C community, I wanted to get an overview of the code flow among the different services in VF-C. We can see that a number of endpoints are exposed as seen here: [1]. But it would be really helpful if we can get to understand the end to end workflow inside VF-C.
The following is what I have understood by looking at the code base: 1. gvnfm/vnflcm: Endpoints to create, instantiate, delete, terminate VNFs. It seems to be doing CRUD operations to a database from these endpoints. 2. gvnfm/vnfmgr: Endpoints to access, configure VNFs. Seems to be doing CRUD on database on what it receives from the endpoints. 3. gvnfm/vnfres: Endpoints to view VM, flavor, network resource information from database. 4. nfvo/catalog: Seems to be a consumer running in a HTTP server to receive info from message bus and has endpoints to do operations with CSAR packages? 5. nfvo/driver/ems: Collect FCAPS information from VNF. 6. nfvo/driver/sfc: Endpoints to create chains. 7. nfvo/driver/vnfm/gvnfm: Seems to have APIs similar to gvnfm, but I am not sure what the difference is between this and vnflcm/vnfmgr/vnfres. 8. nfvo/driver/vnfm/svnfm: Similar to 7. But for specific VNFs. 9. nfvo/lcm: Simiar to 1. But for NS? 10. nfvo/resmanagement: Similar to 3. But for NS? 11. nfvo/wfengine: Creates VNFs based on what is in database or what was received from message bus? Please let us know how the above components talk to each other so that we can understand the project much better. Thanks and Regards, Shashank. [1] - https://wiki.onap.org/display/DW/ONAP+Services+List#ONAPServicesList-VF-C
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
