You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ariatosca.apache.org by Steve Baillargeon <st...@ericsson.com> on 2017/11/02 21:29:35 UTC

Multiple local storages for Compute Node Template

Hi
Is this a valid set of requirement assignments for a node template of type Compute?
All have the same requirement assignment name (as per Compute Node Type definition) but pointing to different node template names.

requirements:
  - local_storage: my_storage_1
  - local_storage: my_storage_2
  - local_storage: my_storage_3

When must I have to use the extended notation?
When using topology substitution?

Regards
Steve


Re: Multiple local storages for Compute Node Template

Posted by Tal Liron <ta...@cloudify.co>.
This is (probably) correct usage.

You'll see that in "tosca.nodes.Compute" the local_storage requirement is
declared with "occurrences" of [ 0, UNBOUNDED ], meaning that it can have
any number of specifications. However, you'll also see that "node" is
declared there as "tosca.nodes.BlockStorage", so you need to be sure that
your "my_storage_" node templates are of that or a derived type.



On Thu, Nov 2, 2017 at 4:29 PM, Steve Baillargeon <
steve.baillargeon@ericsson.com> wrote:

> Hi
> Is this a valid set of requirement assignments for a node template of type
> Compute?
> All have the same requirement assignment name (as per Compute Node Type
> definition) but pointing to different node template names.
>
> requirements:
>   - local_storage: my_storage_1
>   - local_storage: my_storage_2
>   - local_storage: my_storage_3
>
> When must I have to use the extended notation?
> When using topology substitution?
>
> Regards
> Steve
>
>