Re: First Podcast

gt; > On Nov 23, 2017, at 3:33 AM, Avia Efrat wrote: > > > > And maybe make the video name a little bit more descriptive and > appealing =) > > > > On Nov 21, 2017 13:46, "Thomas Nadeau" wrote: > > > >> Thanks for the correction! >

Re: operation dependencies

; node types to have extensible contracts, or allow them to have breakable > contracts. It doesn't make sense to me to be somewhere in between: > strictness should be all the way. > > Finally, I don't understand this question: > > On Wed, Nov 22, 2017 at 7:21 AM, Avia

Re: First Podcast

And maybe make the video name a little bit more descriptive and appealing =) On Nov 21, 2017 13:46, "Thomas Nadeau" wrote: > Thanks for the correction! > > > On Nov 20, 2017, at 4:52 PM, Miguel Angel Jimenez Achinte < > mig...@rigiresearch.com> wrote: > > > > Hi Tom, > > The correct link is: htt

Re: operation dependencies

ve no choice at present. But, to do this properly, I think we need to > also find a way to preserve the type in intrinsic functions, as mentioned > in this discussion. It would still leave cases where it's possible to have > type-less inputs, but I guess that's just how it is righ

Re: Official Project Vote: Moving to Gitbox

+1 On Nov 8, 2017 18:19, "Thomas Nadeau" wrote: > > We need to take a formal vote on whether or not to move forward > with gitbox. Can the project committers please post their > votes. > > I will tally the votes and post the conclusion by the close of > business > today. > >

Re: ariatosca.org sync with git repo: ARIA-400

I prefer option 1. But we should take into consideration different README/getting-started for different ARIA versions. Although if we plan to stabilize the API after the 1.0 release, this is less of an issue. On Fri, Oct 27, 2017 at 1:14 AM, Vishwanath Jayaraman < vishwana...@hotmail.com> wrote:

Re: operation dependencies

returning to: these kinds of parameters we add here -- SSH user, password, > etc. -- are meant as *directives to our execution plugin*, conceptually > very different from operation inputs. Mixing them together is confusing > (what do you do with name overlaps?) as well as a major security concer

Re: Node Template Substitution

Original Message- > From: Arthur Berezin [mailto:art...@cloudify.co] > Sent: Tuesday, October 10, 2017 12:20 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Node Template Substitution > > Avia, can you please post a link to the design? thanks > > On Mon, Oct 9, 2017 at 5:14 PM Avia Ef

Re: Node Template Substitution

Currently the design is finished, and it is on a small hold for now. The plan is to support the 1.0/1.1 profile. On Wed, Oct 4, 2017 at 7:50 PM, Steve Baillargeon < steve.baillarg...@ericsson.com> wrote: > Hi > Can we have a status update on the availability of the Node Template > Substitution fe

Re: operation dependencies

In contrary to most of the TOSCA entities, TOSCA does not differentiate between 'definition' and 'assignment' in the context of operations. There are only "operation definitions" [3.5.13]. Logically, there is a partial differentiation [3.5.13.1], where inputs in node type operations are expected to

Substitution Mappings Property Mappings in TOSCA v1.2

I'm not sure I see a use case of the new properties field that is newly defined under substitution_mappings in v1.2. The description is: "A property mapping allows to map the property of a substituted node type to a property definition or value (mapped as a constant value property definition) wit

Re: Support for TOSCA Simple Profile NFV 1.0

achedTo ( Relantionship > required for virtual storage with compute node) > > > > > > How to address the missing parts from the spec ? > > > > Regards, > > DJ > > > > -Original Message- > From: Avia Efrat [mailto:a...@gigaspaces.com] >

Re: Service Composition / Substitution Mapping

On Tue, Sep 5, 2017 at 6:09 PM, Tal Liron wrote: > > Just like you can specify a specific node template for a requirement, I > believe it can be useful and often necessary to specify a substituted > service template. > ​Even​ if it is needed, the question is how to do that. Using a policy seems

Re: Service Composition / Substitution Mapping

1) Substitutable nodes (abstract nodes) are defined by their type. And a node type should represent specific node/subsystem characteristics. Having two node types ( with the same name) that represent different logical entities seems odd, and indicates a possible bug in the design. That is another r

Re: cli throwing PresenterNotFoundError

A quick late night thought - try this: https://issues.apache.org/jira/browse/ARIA-110 Another solution, try installing via 'make install' only. On Fri, Aug 18, 2017 at 3:47 AM, DeWayne Filppi wrote: > I'm running 'aria service-template validate' against a CSAR, and getting a > 'PresenterNotFoun

Re: Version support for different TOSCA types

eed do nothing in ARIA core. > > I’d agree with that. Its tempting to do an ARIA-specificly > supported > extension to support this and then offer that as an update to TOSCA, but > we should think through that carefully if that is indeed what we want to > do. > >

Re: Service Composition / Substitution Mapping

gt; > > > very detailed validation error here saying that the > > > > > > > requirement > > > > cannot > > > > > be > > > > > > > satisfied, HOWEVER there exist service templates A, B, and C &g

Re: Version support for different TOSCA types

Actually, I can see the version field used as a backwards-compatibility mechanism that will enable to keep the same node type, while adding functionality. (maybe even modifying functionality, but that is more complex). In general, I agree that the 1.0 spec is not clear about using this version fie

Re: pip executable expected as part of plugin install.

Hi DJ, It seems you are correct, I don't see a reason for not using the pip library. Maybe it was that way since we didn't want to add pip as a dependency explicitly (this code is from the beginning of ARIA). Feel free to open an issue about that =) On Wed, Aug 2, 2017 at 10:19 AM, D Jayachandran

Service Composition / Substitution Mapping

Hello all, I'm starting to work on a full implementation of substitution_mapping, which will lead to the ability of service composition. For those unacquainted with substitution mapping, here are some quick resources: *From the spec

Re: Aria Backlog

In the view you linked to, the issues are listed in a numerical order (only issues that are not resolved/closed are shown there). You can see their priority by the small icon to the right of the issue name. Personally, I don't use this view. I use: https://issues.apache.org/jira/issues/?jql=projec

Re: Query on operation inputs

arity and > are in the same page. > > Regards, > DJ > > -Original Message- > From: Avia Efrat [mailto:a...@gigaspaces.com] > Sent: Tuesday, July 11, 2017 3:42 AM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Query on operation inputs > > Here i

Re: Contribution to aria

Hi Yuval, I went over the backlog to find issues that fit the description you asked for. Here are some suggestions: *Incredibly trivial, and could be finished very quickly:* https://issues.apache.org/jira/browse/ARIA-200 (Even if it seems trivial, it could serve as a starting point on the process

Re: Unique identification of an instance element across services

First, good arguments from both 'sides'. I am for at least adding a uuid as an option, as ARIA is intended to be used at scale as well. But currently, I am for the simple ids to be used as default (and not uuids). Like it or not, right now ARIA is more at a 'TOSCA playground' stage, and I think th

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

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 the session

Re: Query on operation inputs

Here is the Jira issue: https://issues.apache.org/jira/browse/ARIA-313 On Tue, Jul 11, 2017 at 12:44 AM, Ran Ziv wrote: > Avia, could you please create a JIRA issue for this? > > > On Mon, Jul 10, 2017 at 5:12 PM, Avia Efrat wrote: > > > Hello DJ, > > > > I ra

Re: Query on operation inputs

a value when the actual > > > > > > > > > execution > > > takes > > > > place. > > > > > > > > > > > > > > > > > > I hope this helps clearing this confusing issue.. > > > > > > &

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

osed > > contributing guide I emailed about earlier. If we put the > > contributing guide on confluence, I believe we can even embed a report. > > > > John > > > > On Sun, Jul 9, 2017 at 9:34 PM Avia Efrat wrote: > > > > > Today Tal (t...@gigaspaces.

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

uch a label, as I'm not sure I'm pleased with 'entry-level'. (Some other suggestions were 'first-time-contributor' and 'trivial', but feel free to suggest your own) -- Avia Efrat SW Engineer a...@gigaspaces.com | +972546204553 Cloudify | http://getcloudify.or

Re: [VOTE] publish ariatosca 0.1.0 (#2)

> > > Source distribution: > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ > 0.1.0-sdist/ > > > > > Binary distribution: > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator

Re: Support for TOSCA Simple Profile NFV 1.0

via. > > Regards, > DJ > > -Original Message- > From: Avia Efrat [mailto:a...@gigaspaces.com] > Sent: Wednesday, June 07, 2017 3:03 AM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Support for TOSCA Simple Profile NFV 1.0 > > Hi DJ, > > I'v

Re: Support for TOSCA Simple Profile NFV 1.0

/github.com/cloudify-cosmo> > [image: Azure Webinar] > <http://getcloudify.org/webinars/Azure-plugin-for- > cloudify-webinar.html?utm_source=signaturesatori&utm_ > medium=email&utm_campaign=general_signature> > -- Avia Efrat SW Engineer a...@gigaspaces.com | +9725462

[jira] [Assigned] (ARIA-180) Convert many-to-many for parameter models to one-to-many

[ https://issues.apache.org/jira/browse/ARIA-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat reassigned ARIA-180: --- Assignee: Avia Efrat > Convert many-to-many for parameter models to one-to-m

[jira] [Created] (ARIA-250) Sporadic Appveyor failures even if all tests pass

Avia Efrat created ARIA-250: --- Summary: Sporadic Appveyor failures even if all tests pass Key: ARIA-250 URL: https://issues.apache.org/jira/browse/ARIA-250 Project: AriaTosca Issue Type: Bug

[jira] [Resolved] (ARIA-157) CLI unit tests for storing service-templates fail on appveyor

[ https://issues.apache.org/jira/browse/ARIA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat resolved ARIA-157. - Resolution: Fixed Fix Version/s: 0.1.0 > CLI unit tests for storing service-templates fail

[jira] [Assigned] (ARIA-157) CLI unit tests for storing service-templates fail on appveyor

[ https://issues.apache.org/jira/browse/ARIA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat reassigned ARIA-157: --- Assignee: Avia Efrat > CLI unit tests for storing service-templates fail on appve

[jira] [Resolved] (ARIA-210) Relative paths may cause issues in `aria service-templates` commands

[ https://issues.apache.org/jira/browse/ARIA-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat resolved ARIA-210. - Resolution: Fixed Fix Version/s: 0.1.0 > Relative paths may cause issues in `aria service-templa

[jira] [Assigned] (ARIA-210) Relative paths may cause issues in `aria service-templates` commands

[ https://issues.apache.org/jira/browse/ARIA-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat reassigned ARIA-210: --- Assignee: Avia Efrat > Relative paths may cause issues in `aria service-templates` comma

[jira] [Assigned] (ARIA-156) Workflow runner continues to run when exception is raised on task_started event

[ https://issues.apache.org/jira/browse/ARIA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat reassigned ARIA-156: --- Assignee: Avia Efrat > Workflow runner continues to run when exception is raised on task_star

[jira] [Created] (ARIA-157) CLI service-template store tests fail on appveyor

Avia Efrat created ARIA-157: --- Summary: CLI service-template store tests fail on appveyor Key: ARIA-157 URL: https://issues.apache.org/jira/browse/ARIA-157 Project: AriaTosca Issue Type: Bug

[jira] [Created] (ARIA-156) Workflow runner continues to run when exception is raised in _task_started

Avia Efrat created ARIA-156: --- Summary: Workflow runner continues to run when exception is raised in _task_started Key: ARIA-156 URL: https://issues.apache.org/jira/browse/ARIA-156 Project: AriaTosca

[jira] [Updated] (ARIA-143) Cancelling of workflow execution

[ https://issues.apache.org/jira/browse/ARIA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-143: Description: Make the process of cancelling execution more robust: - Identify possible pitfalls and corner

[jira] [Resolved] (ARIA-143) Cancelling of workflow execution

[ https://issues.apache.org/jira/browse/ARIA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat resolved ARIA-143. - Resolution: Fixed > Cancelling of workflow execut

[jira] [Closed] (ARIA-143) Cancelling of workflow execution

[ https://issues.apache.org/jira/browse/ARIA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat closed ARIA-143. --- > Cancelling of workflow execution > > > K

[jira] [Updated] (ARIA-143) Improve cancelling of workflow execution

[ https://issues.apache.org/jira/browse/ARIA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-143: Summary: Improve cancelling of workflow execution (was: Improve cancelling workflow execution) > Impr

[jira] [Created] (ARIA-143) Improve cancelling workflow execution

Avia Efrat created ARIA-143: --- Summary: Improve cancelling workflow execution Key: ARIA-143 URL: https://issues.apache.org/jira/browse/ARIA-143 Project: AriaTosca Issue Type: Story Affects

[jira] [Resolved] (ARIA-133) Add status-related properties to Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat resolved ARIA-133. - Resolution: Fixed Fix Version/s: 0.1.0 > Add status-related properties to Execution, Task and N

[jira] [Closed] (ARIA-133) Add status-related properties to Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat closed ARIA-133. --- > Add status-related properties to Execution, Task and Node mod

[jira] [Updated] (ARIA-133) Add status-related properties to Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Summary: Add status-related properties to Execution, Task and Node models (was: Add status-related methods

[jira] [Updated] (ARIA-133) Add status-related methods to Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Description: We are adding those properties so it will be easier to filter these models from storage

[jira] [Updated] (ARIA-133) Add status-related methods to Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Summary: Add status-related methods to Execution, Task and Node models (was: Add status-related methods to

[jira] [Updated] (ARIA-133) Add status-related methods to the Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Description: We are adding those methods so it will be easier to filter these models from storage according

[jira] [Updated] (ARIA-133) Add status-related methods to the Execution, Task and Node models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Summary: Add status-related methods to the Execution, Task and Node models (was: Add status-related methods

[jira] [Updated] (ARIA-133) Add status-related methods to the Execution and Task models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Description: We are adding these methods so it will be easier to filter these models from storage according

[jira] [Updated] (ARIA-133) Add status-related methods to the Execution and Task models

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Summary: Add status-related methods to the Execution and Task models (was: Add is_active and is_ended

[jira] [Updated] (ARIA-133) Add is_active and is_ended methods to the Execution model

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Description: We are adding these methods so it will be easier to filter executions and tasks from the storage

[jira] [Updated] (ARIA-133) Add is_active and is_ended methods to the Execution and Task model

[ https://issues.apache.org/jira/browse/ARIA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-133: Summary: Add is_active and is_ended methods to the Execution and Task model (was: Add is_active and is_ended

[jira] [Created] (ARIA-133) Add is_active and is_ended methods to the Execution model

Avia Efrat created ARIA-133: --- Summary: Add is_active and is_ended methods to the Execution model Key: ARIA-133 URL: https://issues.apache.org/jira/browse/ARIA-133 Project: AriaTosca Issue Type

[jira] [Created] (ARIA-124) The 'simple topologies' of the tests are not tosca complient

Avia Efrat created ARIA-124: --- Summary: The 'simple topologies' of the tests are not tosca complient Key: ARIA-124 URL: https://issues.apache.org/jira/browse/ARIA-124 Project: AriaTosca

[jira] [Updated] (ARIA-96) Dependency versions strictness / conflicts

[ https://issues.apache.org/jira/browse/ARIA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avia Efrat updated ARIA-96: --- Description: When ARIA is used by another project, it might lead to dependency versions conflicts. Dependency

Re: Docstrings in ARIA

I too am for sticking with reST, mostly for its native compatibility with Sphinx. But I must say that I find the Google style to be much more readable as is in comparison with reST. On Mon, Nov 21, 2016 at 4:31 PM, Tal Liron wrote: > Another thing for ReST -- it's very strict, so we get instant

Re: JIRA configuration changes

Overall, Ran's suggestions go well with my vision of the development process. I just want to further emphasize, the less options and fields in a Jira issue screen (as long as it suits our general needs), the better. On Mon, Nov 14, 2016 at 10:04 PM, Ran Ziv wrote: > 1) AFAIK in JIRA this is only