Re: pip executable expected as part of plugin install.

Hi, There is no change with regards to this in the latest code base. The following is the error that we get when the pip executable is not found. Validating plugin /root/testplugin-1.0-py27-none-any.wgn... Plugin validated successfully Installing plugin

Re: Loading Custom Workflows from CSAR

Hi Tal, The loading of the python modules with python functions for workflows happens when the module is in PYTHONPATH. But I could also see that, the absolute path of the resource storage with the service template ID is added to sys.path to make it available for python. This facilitates the

RE: install_aria_extensions called twice

Hi, Thanks for the information. Will this item be prioritized and fixed? Regards, Srinidhi. -Original Message- From: Maxim Orlov [mailto:ma...@cloudify.co] Sent: Wednesday, December 06, 2017 5:59 PM To: dev@ariatosca.incubator.apache.org Subject: Re: install_aria_extensions called twice

RE: Node Template Substitution

Hi Avia I don't access to the design doc. Am I missing something? Will 0.2.0 support YAML Profile 1.0 or 1.2 topology substitution? Or is it postponed to later? -Steve -Original Message- From: Avia Efrat [mailto:a...@cloudify.co] Sent: Tuesday, October 17, 2017 4:44 AM To:

Re: Website Build + Release

Cool. Lets work together on this, so that more than 1 person learns how this works. 8) —Tom > On Dec 7, 2017, at 6:51 PM, Arthur Berezin wrote: > > I can pick this one up. > > Arthur > > On Thu, Dec 7, 2017, 17:13 John D. Ament

Re: Website Build + Release

I can pick this one up. Arthur On Thu, Dec 7, 2017, 17:13 John D. Ament wrote: > Tom, > > I don't know how to do this, so I'd recommend someone else jump in to take > care of it. I would recommend as an immediate step to update the website > with the 0.1.1 release docs

starting .3 release delayed

I just wanted to let folks know that I wasn't able to get the release script kicked off today and I need to split for the airport for a super long ride home, so I'll likely only get back to this next Monday first thing EST. Committers: if you merge any PRs between now and then, please ensure that

Re: Time for a new release

Question about the instructions. It says: If this is your first time creating a release for ARIA, make sure to update the KEYS file with your key I went ahead and generated a new key, and amended it to the KEYS file that I found

Re: Time for a new release

Got it. Thanks. Ill follow those instructions and get this kicked off. --Tom On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament wrote: > Thomas, > > I believe the release process was documented on confluence by prior release > manager. >

Re: Time for a new release

I added the report to the confluence wiki here: https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12 On Thu, Dec 7, 2017 at 5:14 PM, John D. Ament wrote: > Thomas, > > I believe the release process was documented on confluence by prior

Re: Time for a new release

The doc is done. Can you please take a look [see link below]? Also, is there a final resting place for the document other than the Confluence Wiki? —Tom > On Dec 7, 2017, at 5:14 PM, John D. Ament wrote: > > Thomas, > > I believe the release

Re: Loading custom workflows

We had some good discussions are are just about ready to make them public for soliciting feedback. I will handle it next week and let the mailing list know! On Thu, Dec 7, 2017 at 2:31 PM, Thomas Nadeau wrote: > Do you think it is a good idea to start a document and/or wiki

Re: Loading Custom Workflows from CSAR

Actually, the current implementation does not use the CSAR: it expects that the Python function (decorated by @workflow) would be somewhere in the Python path, and we are currently missing a CSAR code-loading mechanism. We do not expect the @workflow function structure to change in any way, so I

Re: AriaTosca December Podling Report

Thomas, The report was due yesterday. John On Thu, Dec 7, 2017 at 2:50 AM Thomas Nadeau wrote: > Just to give a little more info than the original sharing link message. > The mentors > asked me to share the document with the community that I am using to create > the

Re: Website Build + Release

Tom, I don't know how to do this, so I'd recommend someone else jump in to take care of it. I would recommend as an immediate step to update the website with the 0.1.1 release docs to avoid downloading the release on each build. John On Thu, Dec 7, 2017 at 5:06 AM Thomas Nadeau

Time for a new release

Community, At last week's grooming we agreed that I would invoke the next release of Aria (.3) after certain critical PRs were merged. We are at that time now, so I wanted to begin the process. That leads me to my next question... Mentors: is there a document describing the steps to take?

Re: Loading custom workflows

Our current idea is to support multiple ways of installing extensions. One of them will, of course, be by including them in the CSAR file (which can be done in various ways: Python source code, wheels, wagons, etc.). We want to standardize all extensions with a single well-defined entry point. On

Re: Website Build + Release

John, Can I help you with this or is this something you can do quickly? --Tom On Wed, Dec 6, 2017 at 10:01 PM, Arthur Berezin wrote: > John, +1. > > Let's update the aria's release process to push sphynx update on Aria > releases. > > The reason the website is currently