...
1) Is there an API within ONAP's VNF Manager component or Element Management that enables assignment/allocation to specific pieces of hardware within the NFVI/cloud infrastructure?
<Investigate OOF Placement & Slicing APIs> - API Specifications for OOF Applications
2) If the underlying VIM provides APIs for placement of virtual resources on specific pieces of physical hardware, then does ONAP provide corresponding APIs that the VNFs can use to leverage these VIM placement APIs to perform precise placements of the virtual resources they use onto specific nodes within the physical infrastructure? It also depends on what the VNF/CNF/PNF provide as information. To be checked with our A&AI PTL - William
...
Some information are currently available in the AAI component (Active Available Inventory)
Our model can also easily be adapted to store any information needed if our current model does not support it. APIs for inventory operations are auto generated once added to the model.
Can you please review our current model/relationships to see if it supports what you are looking for
Allowed relationships: https://gerrit.onap.org/r/gitweb?p=aai/schema-service.git;a=blob;f=aai-schema/src/main/resources/onap/dbedgerules/v24/DbEdgeRules_v24.json
A&AI API Documentation: https://wiki.onap.org/display/DW/AAI+REST+API+Documentation+-+Istanbul
Associations between virtual and physical resources is currently done in A&AI.
2) If the underlying VIM provides APIs for placement of virtual resources on specific pieces of physical hardware, then does ONAP provide corresponding APIs that the VNFs can use to leverage these VIM placement APIs to perform precise placements of the virtual resources they use onto specific nodes within the physical infrastructure? It also depends on what the VNF/CNF/PNF provide as information.
If the VIM is based on k8S then the new EMCO version (developed by Openness) will support a way to define the platform requirements on per workload basis as intents.
At the time of deployment, it can do match making between requirements and capabilities it discovered early on to select the right K8s cluster.
OpenNESS - EMCO API Documentation. Currently the latest EMCO version (V2) has not yet been integrated to ONAP.
3) Are there APIs between the Network Slice Instance layer and the Resource layer (resource management functions) that enable a network slice instance to gain information about the current mapping of network slice instances to physical resources? Likewise, are there APIs that enable the network slice instances to leverage specific resources available within the resource layer?
The current Network Slicing functionality (till Istanbul release) hasn't considered VNF placement, resource occupancy levels of a cloud instance, occupancy levels of a VNF, etc. due to a number of reasons (first focus on the basic functionality and key lifecycle phases, limited interest/contributions from community for core slicing (where VNF/CNF will be most relevant), etc.). Some of the aspects were being discussed for future releases beyond Istanbul.
In addition, , there is work done on VNF/VF module placement optimization done in OOF. The HAS functionality in OOF could be leveraged, a couple of references are given
o https://docs.onap.org/projects/onap-optf-has/en/latest/index.html#master-index
o https://wiki.onap.org/display/DW/OOF-HAS+Homing+Specification+Guide
There was also another functionality FGPS (Fine-Grained Placement Service) in OOF which I think is no longer maintained
- ONAP Service Assurance based on Magma Glacier Peak v1.6
- Magma/ONAP Integration - latest updates
...