Digest for ASF's Slack

Here’s your digest for today! #ariatosca undefined: [UPDATE] moved all of the topology related methods from the models into the instantiation module (which turned into a package). The reporting and exception handling mechanism is remain to be remodeled. undefined: <@U53P75YTD> <@U546PEP9S> can

RE: Openstack plugin

Hi Max, IF I understand correctly, we need to take the cloudify openstack plugin and replace the plugin.yaml with the one found in the repo. Install this updated plugin with ARIA Install the adapter found in this repo to make use of the plugin Am I right with my

Re: Unique identification of an instance element across services

I just don't see users having to deal much with node IDs outside of simple hello-world style tutorials, and I'd hate for the first impressions that users get out of ARIA is that it's just a playground for TOSCA. It should be ready out-of-the-box for the real world. On Wed, Jul 26, 2017 at 9:13

Re: Openstack plugin

you got most of it right :). You would need to follow these steps: 1. Install the adapter 2. Using ARIA, Install the wagon of the plugin. 3. Utilize the corresponding plugin.yaml found in the repo in your templates. The reason the adapter does not come with ARIA is it's an adapter for Cloudify

Re: Unique identification of an instance element across services

Such is their strength. I'm just advocating using them as a last resort because they are user unfriendly and gigantic. On Tue, Jul 25, 2017 at 12:55 PM, Tal Liron wrote: > Let's consider a mass deployment: thousands of service instances of the > same service template, created