Re: workflow list API

2017-07-11 Thread Tal Liron
Do you mean the CLI command? We actually have talked about this in the past, and the question was just how much the "built-in" (normative lifecycle) workflows should be considered as equivalent to any arbitrary workflow. Can you think of arguments for or against this thinking? On Wed, Jul 12,

[Slack] Notifications from the ASF team for July 12th, 2017 at 8:17 AM

2017-07-11 Thread Slack
Hi ARIA TOSCA, You have a new direct message from the ASF team (https://the-asf.slack.com/x-185534614710-211600170693/). --- @digestai View in the archives: https://the-asf.slack.com/x-185534614710-211600170693/archives/D5E4SCANM/p1499835684891910 Digest.AI (8:01 AM, July 12th) Hi ARIA,

workflow list API

2017-07-11 Thread DeWayne Filppi
The workflow list API call doesn't return "normative" workflows (like "install"). Intentional? -- DeWayne

Re: [VOTE] publish ariatosca 0.1.1

2017-07-11 Thread Ran Ziv
1) Validated signature & checksums 2) Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name 3) Ran RAT check 4) Made a clean install using "pip install ." 5) Ran tests using "make test" +1 binding On Tue, Jul 11, 2017 at 12:08 PM, Maxim Orlov wrote: >1.

Re: [VOTE] Add an 'entry-level' label to some of our Jira issues

2017-07-11 Thread Avia Efrat
Seeing that the overall reaction was good, I created a Jira issue: https://issues.apache.org/jira/browse/ARIA-316 On Mon, Jul 10, 2017 at 4:13 PM, Avia Efrat wrote: > These presentationa are not stand-alone, as they consist of bulletins that > were more broadly explained in

Re: Plugin validation

2017-07-11 Thread Tal Liron
That's a good question. :) Actually, in the service template you do not pin down the plugin, but rather specify the plugin and a minimum version that you need. During instantiation there might be a higher version of the plugin that would be matched. Once instantiated the plugin version is

Re: Missing support for type qualified name

2017-07-11 Thread Ran Ziv
Hi DJ, You shouldn't create another PR - the current should simply update when you push your changes into the relevant branch in your fork (in this case, the master branch). At the moment I see 4 commits on the PR, and it seems to still be broken. If it hasn't updated yet, please update it. If

Re: [VOTE] publish ariatosca 0.1.1

2017-07-11 Thread Maxim Orlov
1. Validated signature & checksums 2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name 3. Ran RAT check 4. Made a clean install using "pip install ." 5. Ran tests using "make test" +1 On Tue, Jul 11, 2017 at 2:27 AM, Suneel Marthi wrote: > +1

Plugin validation

2017-07-11 Thread D Jayachandran
Hi, With current implementation, the plugin validation in a service template happens during the service creation (instantiation of service model). Will it be appropriate if we have this plugin validation happening during the service-template creation itself ? Regards, DJ

RE: Missing support for type qualified name

2017-07-11 Thread D Jayachandran
Hi Ran, I fixed those issues. I have commited those with changes , am not sure if I have to make another PR ? Could you please advice me here ? Regards, DJ -Original Message- From: Ran Ziv [mailto:r...@gigaspaces.com] Sent: Friday, July 07, 2017 3:28 PM To: