tosca.nodes.Compute offering questions

[Luca Gioppo <luca.gioppo@csi.it>]

Some questions on the Compute node definition.

From a model point of view the definition is logical, from the Cloud API available is less usefull.

 

On CloudStack for example I create a new virtual machine by sending the templateId the offeringId and the zoneId.

To get those information my orchestrator has to match the generic request of CPU, Memory, disk, operating system etc with the existing offerings.

Is this the way that the standard has to be used?

So to create a compute resource the orchestrator must "guess" the correct combination?

Is there a good practice to adopt for giving back results or is a free decision of the orchestrator implementor?

I could find a combination of offering that match the node description or not in case not I should return error to end user or try to go to the nearest good offering?

Maybe this problem could araise the need of some new attribute in the standard for forcing a proper behaviour?

 

Thanks

Luca