Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-10-31 Thread Tal Liron
1) Does ARIA actually support namespace_uri and namespace_prefix for each import definition as defined in YAML 1.1 spec. See multi-line grammar below: > imports: > - file: > repository: > namespace_uri: > namespace_prefix: > This is in TOSCA 1.0, too. Repositories are

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-10-31 Thread Steve Baillargeon
From: Tal Liron [mailto:t...@cloudify.co] > Sent: Tuesday, September 26, 2017 11:56 AM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Contribution for https://issues.apache.org/ > jira/browse/ARIA-118 > > That's how ARIA implements it right now. I consider the TOSCA 1.0 spec >

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-10-20 Thread Tal Liron
Sent: Tuesday, September 26, 2017 11:56 AM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Contribution for https://issues.apache.org/ > jira/browse/ARIA-118 > > That's how ARIA implements it right now. I consider the TOSCA 1.0 spec on > "imports" to

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-10-20 Thread D Jayachandran
loudify.co] Sent: Tuesday, September 26, 2017 11:56 AM To: dev@ariatosca.incubator.apache.org Subject: Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118 That's how ARIA implements it right now. I consider the TOSCA 1.0 spec on "imports" to be an error because it

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-25 Thread Steve Baillargeon
To: dev@ariatosca.incubator.apache.org Subject: Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118 So, this is one of the cases where the spec seems to be wrong: the is probably a mistake. None of the other examples in the spec have it, nor do we see it in other TOSCA examples. Note

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-25 Thread Tal Liron
efix: > > > With your example can we have multiple repositories ? > > > Regards, > DJ > > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Thursday, September 21, 2017 9:31 PM > To: dev@ariatosca.incubator.apache.org > Subjec

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-25 Thread D Jayachandran
Message- From: Tal Liron [mailto:t...@cloudify.co] Sent: Thursday, September 21, 2017 9:31 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118 I do suggest the repository, because it seems like the more TOSCA way to do

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-21 Thread Tal Liron
repository conventions ? > > Regards, > DJ > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Wednesday, September 20, 2017 9:38 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Contribution for https://issues.apache.org/ > jira/browse

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-21 Thread D Jayachandran
...@cloudify.co] Sent: Wednesday, September 20, 2017 9:38 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118 I think the format you suggest is awkward in YAML. Because ":" is reserved, you would have to wrap the string

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-20 Thread Tal Liron
.yaml", I would like to suggest the following > "plugins: openstack-" > Please let me know if this fine with you. > > > Regards, > DJ > > -Original Message- > From: Tal Liron [mailto:t...@gigaspaces.com] > Sent: Thursday, July 20, 2017 6:24

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-09-20 Thread D Jayachandran
s fine with you. Regards, DJ -Original Message- From: Tal Liron [mailto:t...@gigaspaces.com] Sent: Thursday, July 20, 2017 6:24 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118 It's unassigned, so I don't see why not! On T

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-07-20 Thread D Jayachandran
will be working on this. > > Regards, > DJ > -Original Message- > From: Tal Liron [mailto:t...@gigaspaces.com] > Sent: Thursday, July 20, 2017 6:24 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Contribution for > https://issues.apache.org/jira/browse/ARIA-1

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-07-20 Thread John D. Ament
> -Original Message- > From: Tal Liron [mailto:t...@gigaspaces.com] > Sent: Thursday, July 20, 2017 6:24 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Contribution for > https://issues.apache.org/jira/browse/ARIA-118 > > It's unassigned, so I don't see

RE: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-07-20 Thread D Jayachandran
Thanks Tal, I will be working on this. Regards, DJ -Original Message- From: Tal Liron [mailto:t...@gigaspaces.com] Sent: Thursday, July 20, 2017 6:24 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118 It's unassigned

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-07-20 Thread Tal Liron
It's unassigned, so I don't see why not! On Thu, Jul 20, 2017 at 7:41 AM, D Jayachandran wrote: > Hi, > > Do you have any plans on working on this JIRA issue ? > https://issues.apache.org/jira/browse/ARIA-118 > Can we contribute on this ? > > > Regards, > DJ >

Contribution for https://issues.apache.org/jira/browse/ARIA-118

2017-07-20 Thread D Jayachandran
Hi, Do you have any plans on working on this JIRA issue ? https://issues.apache.org/jira/browse/ARIA-118 Can we contribute on this ? Regards, DJ