Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Base Candidate Class 

AttributeRequiredContent
inventory_providerYString
inventory_typeY

String

candidate_idYString
candidate_typeYString
uniquenessYBoolean
costYString

Inventory Types

 1) Cloud

 2) Service

 3) Vfmodule

 4) Transport

All the candidate for every inventory types extend from the candidate base class.

Following are the AAI objects from which the respective candidates takes the required data:

Cloud object

EXAMPLE : https://docs.onap.org/projects/onap-optf-has/en/latest/sections/homingspecification.html

MODEL

AttributeRequiredContent
cloud-regionYdict
complexY

dict

flavorsYdict
sriov_automation*Nboolean

Service object

EXAMPLE : https://docs.onap.org/projects/onap-optf-has/en/latest/sections/homingspecification.html

MODEL

AttributeRequiredContent
generic-vnfYdict
vlan_info*Y

dict

cloud-regionYdict
service-instanceYdict
complexYdict
sriov_automation*Nboolean

Vfmodule object

EXAMPLE : https://docs.onap.org/projects/onap-optf-has/en/latest/sections/homingspecification.html

MODEL

AttributeRequiredContent
generic-vnfYdict
cloud-regionY

dict

vlan_info*Ydict
vserverYdict
service-instanceYdict
vf-moduleYdict
complexYdict
l-interfacesYdict
sriov_automation*Nboolean

Transport object

EXAMPLE : https://docs.onap.org/projects/onap-optf-has/en/latest/sections/homingspecification.html

MODEL

AttributeRequiredContent
service-instanceYdict
complexY

dict

zoneYdict

Design

In the data module, after fetching the data from AAI the candidate gets populated like this 

While returning to solver;



  • No labels