Re: ARIA-354 Verified

OH, indeed that's pro :D -- Miguel Jimenez, PhD student Department of Computer Science University of Victoria Engineering/Computer Science Building (ECS), Room 412 Victoria, BC V8W 3p6 Canada On Mon, Nov 27, 2017 at 6:51 PM, Tal Liron wrote: > In your case, I would replace

Re: ARIA-354 Verified

In your case, I would replace the "pip install" line with this one: make install-virtual This will install your checked-out git repo in development mode into the virtual environment, meaning that any code changes you make will immediately be reflected. This is how we pro devs work. :) On Mon,

Re: ARIA-354 Verified

I'm sorry if that was confusing. I checked out the 0.1.1 tag because the working blueprint is there. To install ARIA, I used pip. Just to make sure everything is clear, these are the steps I executed: sudo pip install virtualenv virtualenv tosca-environment source tosca-environment/bin/activate

Re: ARIA-354 Verified

I'm confused, Miguel. You checked out the git repository, but then installed ARIA from the PyPI (using pip). I would recommend not mixing the two methods, because indeed if the git repo is at master's tip, then it would not much what was last released to PyPI. You found a workaround here, using

Re: ARIA-354 Verified

Okay, it's working now. I needed to check out the tag 0.1.1. The complete list of commands is: sudo pip install --upgrade setuptools sudo pip install apache-ariatosca[ssh] ... aria --version v0.1.1 ... git clone https://github.com/apache/incubator-ariatosca; cd incubator-ariatosca git checkout

Re: simple validation error

thx On Nov 27, 2017 3:43 PM, "Tal Liron" wrote: It is a bug. I created this issue: https://issues.apache.org/jira/browse/ARIA-411 For now, the workaround is to add a "primary" key under "implementation". Also note that you must supply the "type" field for the interface

Re: simple validation error

It is a bug. I created this issue: https://issues.apache.org/jira/browse/ARIA-411 For now, the workaround is to add a "primary" key under "implementation". Also note that you must supply the "type" field for the interface definition. So: T1: derived_from: tosca.nodes.Root interfaces:

Re: ARIA-354 Verified

Ok, got it. Vish From: Tal Liron Sent: Monday, November 27, 2017 5:19 PM To: dev@ariatosca.incubator.apache.org Subject: Re: ARIA-354 Verified Vish, I'm pretty sure the version suffix is not required, because 0.1.1 is the highest version.

simple validation error

This should validate, no? tosca_definitions_version: tosca_simple_yaml_1_0 imports: - aria-1.0 node_types: T1: derived_from: tosca.nodes.Root interfaces: Standard: create: implementation: i1.sh T2: derived_from: T1 interfaces: Standard:

Re: ARIA-354 Verified

Vish, I'm pretty sure the version suffix is not required, because 0.1.1 is the highest version. On Mon, Nov 27, 2017 at 5:08 PM, Vishwanath Jayaraman < vishwana...@hotmail.com> wrote: > > You need to execute > > pip install apache-ariatosca[ssh]==0.1.1 > > Sent from my iPhone > > On Nov 27,

Re: ARIA-354 Verified

You need to execute pip install apache-ariatosca[ssh]==0.1.1 Sent from my iPhone On Nov 27, 2017, at 4:49 PM, Miguel Angel Jimenez Achinte > wrote: I executed: pip install apache-ariatosca[ssh] Should I use "pip install

Re: ARIA-354 Verified

Tom, these are the commands I executed to get "aria --version" working: sudo pip install --upgrade setuptools sudo pip install apache-ariatosca[ssh] ... aria --version v0.1.1 ... git clone https://github.com/apache/incubator-ariatosca; cd incubator-ariatosca aria service-templates store

Re: ARIA-354 Verified

Tom, the errors he is getting are not related to permissions. He has gone beyond the install phase and is having errors when trying to parse a TOSCA file. On Mon, Nov 27, 2017 at 4:53 PM, Thomas Nadeau wrote: > You need to do this as: > > % sudo -H pip install … > > Its a

Re: ARIA-354 Verified

The error you are seeing now is unrelated to the error that required the "--no-binary" workaround. It seems somehow your install is not seeing the extensions, and thus is not finding the TOSCA parser. Are you using a virtualenv? Or are you using "sudo -H" to install to your operating system? On

Re: ARIA-354 Verified

You need to do this as: % sudo -H pip install … Its a permissions problem. I literally started to modify the Installation Instructions earlier when I was reminded of this myself. Can’t get a good answer as to how to fix it either. Experienced it on CenOS, Fedora and Ubuntu. —Tom > On Nov

Re: ARIA-354 Verified

OH yes, I need to run the “hell world” example. I’ll do that first thing Tuesday... > On Nov 27, 2017, at 5:24 PM, Tal Liron wrote: > > Tom, the specific problems we had were not with installation, but rather in > running workflows. Have you tried to install the

Re: ARIA-354 Verified

Miguel, how did you install ARIA? On Mon, Nov 27, 2017 at 4:44 PM, Miguel Angel Jimenez Achinte < mig...@rigiresearch.com> wrote: > I just installed ARIA on Centos 7 and I get the same error: > > Storing service template my-service-template... > > *AttributeError*: 'NoneType' object has no

Re: ARIA-354 Verified

I just installed ARIA on Centos 7 and I get the same error: Storing service template my-service-template... *AttributeError*: 'NoneType' object has no attribute '_get_properties' File "/usr/lib/python2.7/site-packages/aria/parser/consumption/consumer.py", line 70, in consume

Re: ARIA-354 Verified

Tom, the specific problems we had were not with installation, but rather in running workflows. Have you tried to install the Hello World example? On Mon, Nov 27, 2017 at 2:54 PM, Thomas Nadeau wrote: > > I took an action during the grooming to verify the

ARIA-354 Verified

I took an action during the grooming to verify the installation of the latest PIP artifacts. I was able to install successfully on Ubuntu 16.04 LTS just now. —Tom

Re: ASF Slack Access and Write Permissions to the Wiki

Glad its working! And if there's anyone to thank, its our crack infra team. On Nov 27, 2017 2:57 PM, "Vishwanath Jayaraman" wrote: John, I am now able to see the edit button on the WIKI page and also able to change state of the JIRA item. That was fast, thanks a lot

Re: ASF Slack Access and Write Permissions to the Wiki

John, I am now able to see the edit button on the WIKI page and also able to change state of the JIRA item. That was fast, thanks a lot for all your help. Vish From: John D. Ament Sent: Monday, November 27, 2017 1:52 PM To:

Re: ASF Slack Access and Write Permissions to the Wiki

Im talking to Vish now. Looks like your fixes worked. Thx! > On Nov 27, 2017, at 2:52 PM, John D. Ament wrote: > > Vish can you try now? > > On Nov 27, 2017 2:28 PM, "Thomas Nadeau" wrote: > >> +1 >> >>> On Nov 27, 2017, at 1:44 PM, John D.

Re: ASF Slack Access and Write Permissions to the Wiki

Vish can you try now? On Nov 27, 2017 2:28 PM, "Thomas Nadeau" wrote: > +1 > > > On Nov 27, 2017, at 1:44 PM, John D. Ament > wrote: > > > > I think I see the issue. In the JIRA permission scheme, contributors can > > resolve and close issues, but

Re: ASF Slack Access and Write Permissions to the Wiki

+1 > On Nov 27, 2017, at 1:44 PM, John D. Ament wrote: > > I think I see the issue. In the JIRA permission scheme, contributors can > resolve and close issues, but not transition them. Are we in agreement > that contributors should be able to transition issues? > > On

Re: ASF Slack Access and Write Permissions to the Wiki

Requested -> https://issues.apache.org/jira/browse/INFRA-15566 On Mon, Nov 27, 2017 at 1:50 PM Tal Liron wrote: > I see no harm in giving them that permission. > > On Mon, Nov 27, 2017 at 12:44 PM, John D. Ament > wrote: > > > I think I see the issue.

Re: ASF Slack Access and Write Permissions to the Wiki

I see no harm in giving them that permission. On Mon, Nov 27, 2017 at 12:44 PM, John D. Ament wrote: > I think I see the issue. In the JIRA permission scheme, contributors can > resolve and close issues, but not transition them. Are we in agreement > that contributors

Re: ASF Slack Access and Write Permissions to the Wiki

I think I see the issue. In the JIRA permission scheme, contributors can resolve and close issues, but not transition them. Are we in agreement that contributors should be able to transition issues? On Mon, Nov 27, 2017 at 1:41 PM Thomas Nadeau wrote: > which issue? > >

Re: ASF Slack Access and Write Permissions to the Wiki

Aria -399, I want to be able to move it to In Progress from Open. Sent from my iPhone On Nov 27, 2017, at 12:41 PM, Thomas Nadeau > wrote: which issue? On Nov 27, 2017, at 1:33 PM, Vishwanath Jayaraman

Re: ASF Slack Access and Write Permissions to the Wiki

which issue? > On Nov 27, 2017, at 1:33 PM, Vishwanath Jayaraman > wrote: > > Thanks John. > Is there a reason why I am not able to edit the state of a Jira item assigned > to me? > > > Sent from my iPhone > > On Nov 27, 2017, at 12:25 PM, John D. Ament >

Re: ASF Slack Access and Write Permissions to the Wiki

thanks again for helping out on this. On today’s grooming someone suggested that we add this to the wiki’s “getting started” so that we have this straight for future contributors. Its on my list. —Tom > On Nov 27, 2017, at 1:13 PM, John D. Ament wrote: > > Miguel, >

Re: ASF Slack Access and Write Permissions to the Wiki

Thanks John. Is there a reason why I am not able to edit the state of a Jira item assigned to me? Sent from my iPhone On Nov 27, 2017, at 12:25 PM, John D. Ament > wrote: I've given you both access to confluence. I added MIguel as a

Re: ASF Slack Access and Write Permissions to the Wiki

Thank you for your help, John. Thomas, regarding the Slack channel, how should I proceed to get an invitation? Thanks in advance, Miguel -- Miguel Jimenez, PhD student Department of Computer Science University of Victoria Engineering/Computer Science Building (ECS), Room 412 Victoria, BC V8W

Re: ASF Slack Access and Write Permissions to the Wiki

I've given you both access to confluence. I added MIguel as a contributor in JIRA, Vish you were already listed as a contributor. On Mon, Nov 27, 2017 at 1:19 PM Vishwanath Jayaraman < vishwana...@hotmail.com> wrote: > John, > > My username is vishwanathj and associated email address is >

Re: ASF Slack Access and Write Permissions to the Wiki

John, My username is vishwanathj and associated email address is vishwana...@hotmail.com. I need edit access to confuence/wiki and permissions in JIRA to be able to change issue states from Open->Progress->resolved, etc. Thanks in advance for all your help. Vish

Re: ASF Slack Access and Write Permissions to the Wiki

Hi John, The username is the same I sent to general@incubator: username: jachinte email: mig...@uvic.ca for both Wiki and JIRA. Miguel -- Miguel Jimenez, PhD student Department of Computer Science University of Victoria Engineering/Computer Science Building (ECS), Room 412 Victoria, BC V8W 3p6

Re: ASF Slack Access and Write Permissions to the Wiki

Miguel, To get you set up on JIRA and Confluence, we'll need to know your username. John On Mon, Nov 27, 2017 at 12:23 PM Thomas Nadeau wrote: > > Sorry by “apache ID” I meant “jira login” below. I think Miguel > looking for wiki and Slack access > only. Vish

Re: ASF Slack Access and Write Permissions to the Wiki

Sorry by “apache ID” I meant “jira login” below. I think Miguel looking for wiki and Slack access only. Vish ran into the same issue earlier with wiki access, but in his case permissions vanished after he did have write access to the wiki. —Tom > On Nov 27, 2017, at 12:21

Re: ASF Slack Access and Write Permissions to the Wiki

Hi John, I want to get access to AriaTosca wiki/JIRA. -- Miguel Jimenez, PhD student Department of Computer Science University of Victoria Engineering/Computer Science Building (ECS), Room 412 Victoria, BC V8W 3p6 Canada On Mon, Nov 27, 2017 at 9:21 AM, John D. Ament

Re: ASF Slack Access and Write Permissions to the Wiki

Hi, I saw your email to general@incubator. I'm not sure what your goal is. Do you want access to the AriaTosca wiki/JIRA? Or the incubator wide wiki/JIRA? Note that apache.org emails are only given to committers. John On Mon, Nov 27, 2017 at 12:07 PM Miguel Angel Jimenez Achinte <

Grooming Meeting Minutes: November 27, 2017

November 27, 2017 Tal, Tom, Guy Offer, Vish, Arthur, Miguel Aria-394 - closed Aria-1 - Maxim/Avia proposed changes. Reponded to comments and pushed fixes. Avia reviewed. Should be finished today with one final review by tomorrow. Able to start release process after this. Aria-408 - closed .2

ASF Slack Access and Write Permissions to the Wiki

Miguel asked about getting access to ASF Slack at the grooming call this morning, so I thought I’d send this to the entire list. In order to gain access, please send email to gene...@incubator.apache.org asking for write permissions on your Apache ID for the wiki/jira as well

Re: upcoming podcasts

Suneel: This indeed is the case that Vish cannot edit. Can we adjust the Jira permissions so that anyone that is logged in can edit the Wiki? It appears that people not set with explicit write permissions can mod/edit the wiki. Is there any reason why people that don’t have apache accounts

Today's Grooming

We will be having our usual weekly grooming meeting at 11AM EST today. The Zoom coordinates can be found here: https://cloudify.zoom.us/j/5055197842 >

Re: upcoming podcasts

Sure, I can add to the wiki. Need edit permissions for username:vishwanathj with email address:vishwana...@hotmail.com Thanks Vish From: Thomas Nadeau Sent: Monday, November 27, 2017 9:09 AM To: dev@ariatosca.incubator.apache.org

Re: upcoming podcasts

These are cool ideas. Can you add them to the wiki? > On Nov 27, 2017, at 10:07 AM, Vishwanath Jayaraman > wrote: > > I was going through (and still going through) the > http://docs.oasis-open.org/tosca/TOSCA/v1.0/TOSCA-v1.0.pdf and >

Re: upcoming podcasts

I was going through (and still going through) the http://docs.oasis-open.org/tosca/TOSCA/v1.0/TOSCA-v1.0.pdf and http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/TOSCA-Simple-Profile-YAML-v1.1.html links and wished that there were multi part short videos that explained it. From

Re: upcoming podcasts

That is a great idea. I think having a guest on the show that is more involved in the ONAP work would be awesome. Tal? —Tom > On Nov 27, 2017, at 9:51 AM, Nati Shalom wrote: > > How about covering how Aria is being used in ONAP? > > On Mon, Nov 27, 2017

Re: upcoming podcasts

How about covering how Aria is being used in ONAP? On Mon, Nov 27, 2017 at 4:34 PM Thomas Nadeau wrote: > > Good morning, > > Just a heads up that I will be taking the baton on putting > together the podling report. Im going to get this done by the end of

upcoming podcasts

Good morning, Just a heads up that I will be taking the baton on putting together the podling report. Im going to get this done by the end of this week also, Tal and I will be doing the next podcast next week from Tel Aviv and might do a couple of extras while we are there

Re: First Podcast

Good idea to include the ep and title. Will look into the playlist. —Tom > On Nov 23, 2017, at 7:59 AM, Avia Efrat wrote: > > Maybe something like > ARIA and TOSCA Podcast - ep01 - Introduction > > In addition, create a Youtube playlist for the podcasts. >