|
Post by adrianecardozo on Jun 1, 2018 2:37:28 GMT
Hi,
I have some questions related to the Capabilities object.
When creating a composed resource, is it possible to specify the number of resource blocks expected and the type of each one?
For example, suppose that in the Resouce Zone there are:
- 10 resource blocks of "Storage" (200GB SAS)
- 20 resource blocks of "Storage" (300GB HDD)
- 5 resource blocks of "Compute"
and I can only compose 1 "Compute" with 2 "Storage" (disk drives of 200GB SAS) and 2 "Storage" (disk drives of 300GB HDD).
Checking the specification, it seems I can't make this restriction. Am I missing something? How could I specify that in the Capabilities?
Thanks in advance, Adriane
|
|
|
Post by mraineri on Jun 5, 2018 14:01:21 GMT
You're correct; the capabilities object currently does not convey that sort of information. The intent of the capabilities object is to describe the structure of the POST request; it wasn't intended to show implementation specific restrictions on how things can be composed. Currently this would require the client to try a composition request, see it fail, and modify the request as the service indicates. I'll bring this up for discussion within the group to see if there's a better solution.
|
|
|
Post by rafiqahamed on Jun 7, 2018 6:31:23 GMT
Within a ResourceZone you can use any ResourceBlock any number of times based on below steps. 1. If CompositionState=Unused or 2. If CompositionState=Composed, then look for SharingEnabled=true && NumberOfCompositions <= MaxCompositions.
That gives user an indirect control on how many RB's to include in his Composition request. Note even if Capabilities define how many Storage RB's you can include, the client would still have to work through the above Attributes to identify if its free and shared.
|
|
|
Post by adrianecardozo on Jul 10, 2018 17:26:13 GMT
|
|