Re: Service Composition / Substitution Mapping

Well, this is exactly what policies are for. :) Again, I think the rule of thumb should be that users put policies in place *only* if the defaults do not suffice. On Mon, Aug 7, 2017 at 6:42 PM, Ran Ziv wrote: > The sensible defaults Tal's mentioned sound indeed sensible to

Re: Openstack plugin

For future readers of this thread, you can find an example on how to use this plugin here: https://cwiki.apache.org/confluence/display/ARIATOSCA/OpenStack+Hello+World On Wed, Jul 26, 2017 at 6:25 PM, Maxim Orlov wrote: > you got most of it right :). You would need to follow

Re: Service Composition / Substitution Mapping

The sensible defaults Tal's mentioned sound indeed sensible to me. I'd also like users to have control over this, though I'm a bit worried about us getting too carried away with how arbitrarily we use policies for configuring, well, pretty much anything. It might not be a problem right now but I'm

Re: Contribution to aria

Sorry for the late reply, but one more important link to check out is the contribution guide, here: https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+to+ARIA It can also direct you to other Apache and general "how to get started with Open Source" guides. On Tue, Aug 1, 2017 at

Re: Version support for different TOSCA types

OK, you are referring to the "version" data type, and it is fully supported in ARIA, which includes: 1. Strict adherence to the (rather odd) specification and its regex 2. Proper support for TOSCA comparative constraints for versions (greater_than, lesser_than, etc.) 3. Comparisons also work