Subject: Re: TOSCA spec compliance on finding target node
I think you are talking about requirements? Some of the combinations you
mention are for requirement declarations (at the node type) and some for
requirement assignments (at the node template).
Generally speaking, ARIA intends to support
> >
> > As per the TOSCA specification, the above are valid combinations.
> >
> > Will ARIA support all the above ?? If so, we wish to contribute.
> >
> > Looking forward to your comment.
> >
> >
> >
> > Thanks,
> >
> > /Vaish
>
wish to contribute.
>
> Looking forward to your comment.
>
>
>
> Thanks,
>
> /Vaish
>
>
> From: Tal Liron
> Sent: Tuesday, July 25, 2017 10:03:18 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: TOSCA spec compliance on
forward to your comment.
Thanks,
/Vaish
From: Tal Liron
Sent: Tuesday, July 25, 2017 10:03:18 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: TOSCA spec compliance on finding target node
It indeed should *not* be required. I just verified that it you
It indeed should *not* be required. I just verified that it you are
correct, and a match is not made if only the capability is specified
without a node type/template.
This is a regression, because it used to work correctly.
There is currently work in progress to refactor that mechanism, so I will
Hi ARIA folks,
I had a look at the source code of ARIA on how the target node is identified
based on the requirement and capability information furnished in the node
template and its corresponding node type. But I find that only few of the
combinations are supported i.e., as per the TOSCA spec