Re: workflow runner error

+1 On Thu, Jul 13, 2017 at 12:51 AM, Tal Liron wrote: > I wonder if we should provide a better upgrade path here. Perhaps we need > to add a file with some meta information about the version of the database. > We don't necessarily have to provide an automatic upgrade to a

Re: async execution/task management

The link is to CLI code, which I was aware of. Unlike the CLI, I don't want to sit and wait for the threads to complete. In a manner similar to Cloudify, I want to launch and execution in one call, and check on it's status at will in other calls. I would argue that if this sort of pattern is

[VOTE] publish ariatosca 0.1.1

The ariatosca community voted on and has approved a proposal to release ariatosca 0.1.1. Pursuant to the Releases section of the Incubation Policy and with the endorsement of our mentors, we would now like to request the permission of the Incubator PMC to publish the tarball on Apache's

[RESULT][VOTE] Apache ariatosca 0.1.1 (incubating)

The vote has passed with: - Three binding "+1" votes - no "0" votes - no "-1" votes The votes were: - +1, Suneel Marthi (binding) - +1, Maxim Orlov (binding) - +1, Ran Ziv (binding) Vote thread: https://lists.apache.org/thread.html/b0571ee44c5f5bb325cc7f49e475e3

Re: async execution/task management

I think I came up with a good enough solution for now. The caller is a long running process ( a web server essentially), so I added a module level dict that maps execution id to runner and thread. When a status or cancel comes it, it just looks the objects up in the map and gets busy. Of course

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

Hi ARIA TOSCA, You have a new direct message from the ASF team (https://the-asf.slack.com/x-185534614710-21366631/). --- @digestai View in the archives: https://the-asf.slack.com/x-185534614710-21366631/archives/D5E4SCANM/p158465405217 Digest.AI (8:01 AM, July 14th) Hi ARIA,

Re: workflow runner error

I wonder if we should provide a better upgrade path here. Perhaps we need to add a file with some meta information about the version of the database. We don't necessarily have to provide an automatic upgrade to a new database format, but least we can tell the user that the database is out of date

Re: async execution/task management

The execution id is indeed the linking factor between all execution related operations. ARIA doesn't provide asynchronous execution based operations. However, here you can see how ARIA runs executions

Re: workflow runner error

I think upgrade paths is not really a topic that should be discussed at the moment - we're at a 0.x.y release with no backward compatibility guarantees, plus, the version that was used prior to the current version in this case was an unreleased version, so an upgrade path wouldnt have been viable

Re: async execution/task management

However, note that since each process creates its own workflow_runner (and consequently a new engine), starting and ending the workflow_runner should be done from the same process. On Thu, Jul 13, 2017 at 11:39 AM Maxim Orlov wrote: > The execution id is indeed the linking

Re: Congrats on the First Release!

I've documented the release process on our Confluence: https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process This, together with the release automation script , should hopefully make things much simpler for the release manager of the