Add Functional Capabilities and Infrastructural Capabilities dynamic exportation

[gabrielecastellano]

The new branch of the frog4-orchestrator (global orchestrator) takes decisions about where VNFs should be instantiated basing on the exported capabilities. So domain orchestrators should be extended to support the dynamic exportation of these capabilities.

The data structure that describes the domain should follow the data model defined on the frog4-domain-data-model repository (the python parser is available on the frog4-sdn-do but should be separated in a new library repository).

Moreover, the domain-orchestrator should export an additional API that allows the global orchestrator to know if a specific VNF could be implemented trough an infrastructural capability. request: GET /vnf/{name} response:

• 200: the vnf can be implemented.
• 404: vnf not found. this could not be always true, it depends by the VNFs that the domain orchestrator is able to fetch from the vnf-repository.

At this moment, the only domain-orchestrator that has been extended in this way is the frog4-sdn-do.

[ivanocerrato]

There is an issue similar here https://github.com/netgroup-polito/frog4-openstack-do/issues/19 . For now, I will keep both of them since, if I understand correctly, they are a little bit different.

[rbrtbnfgl]

https://github.com/netgroup-polito/frog4-openstack-do/commit/568db94ad4cccb80d7ed9e7f48372df611868d38 done functional capabilities discover.