Re: CI for Aria Tosca?

Hi John, We're in the process of moving code to the Apache git repository, after which we'll set up a build to run our unit tests etc. Most of the people involved in the project are on holiday for most of this month, so this might take some more time. Ran On Sun, Oct 16, 2016 at 6:15 PM, John D.

Re: GIT/JIRA Integration

browse/INFRA-13431?page= > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel> > ? > > John > > On Sun, Feb 19, 2017 at 8:05 AM Ran Ziv wrote: > > > Yes, I see it now, although when I click any of these (e.g. "commits") > I'm > > asked to

Re: Query on interface inputs

Could you please explain what you mean exactly by "optional inputs"? For an input to be "optional" it should have a default value at its definition. (Note that there is also the "required" flag for parameters but that is only respected at parse time) We would probably be better to provide better

Re: GIT/JIRA Integration

@John, Bumping this again, as the bot is still spamming on our JIRA issues. Thanks! On Thu, May 11, 2017 at 10:03 AM, Ran Ziv wrote: > Hi John, > > It took some time, but I finally have the Fisheye extension working on > JIRA. > It'd be great if you could turn off the

Re: GIT/JIRA Integration

that you want the fisheye > > integration still on. > > > > John > > > > On Thu, May 18, 2017 at 6:00 PM Ran Ziv wrote: > > > > > @John, > > > > > > Bumping this again, as the bot is still spamming on our JIRA issues. > > >

Re: Moving to 100% GitHub

I don't think moving the project to Github and the issue of lack of discussions on the mailing list are related - we need to solve the latter regardless of the former. Tal, I'm not sure how exactly it would increase visibility - The mirror is as visible as the new repository would be..? It could h

Re: New mailing lists

Matej, John etc. - The issue we keep coming back to, and the reason we try to avoid emails, is that discussions on emails are simply much slower than ones on Slack. John, regarding summarizing slack conversations on the mailing list manually - that's possible, but then I feel like we might be gett

Re: [UPDATE] Work on ARIA-149: Support intrinsic functions in "dependencies" operation configuration

+1 for examples, or perhaps a link to specific code sections. >From what I did understand though, before we talk about additional changes, I'm not at all sure I'm in favor of the current ones. First, the many-to-many relationship sounds in contrast to what Avia is currently working on with (chang

Re: Renaming Old ARIA Repos

I'd think simply a huge note on the top of the README would suffice. On Sun, May 21, 2017 at 4:28 PM, Arthur Berezin wrote: > Hi All, > > > It seems that the old ARIA organization on GitHub from before we moved to > ASF(https://github.com/aria-tosca-old) are still creating confusion. > I added t

Re: Moving to 100% GitHub

ache.org/confluence/display/ARIATOSCA/ > > Contributing+to+ARIA > > > > > > On Sun, May 21, 2017 at 2:38 PM, John D. Ament > > > wrote: > > > > > > > On Sun, May 21, 2017 at 7:51 AM Ran Ziv wrote: > > > > > > > > > I don&#

Re: [UPDATE] Work on ARIA-149: Support intrinsic functions in "dependencies" operation configuration

spec. They >are preserved and never change. >2. "configuration" is an extra optional ARIA extension dict allowing >users to configure how the plugin will execute the operation. >3. "function" and "arguments" are internal implementation detail

Re: Query on operation inputs

Hi, Weird, I remember responding to this mail before, but it doesn't seem like I have. In any case, it is indeed our intention that no inputs may be passed into operations unless they have been clearly declared in the service-template. ARIA opts to be a strict implementation of TOSCA wherever poss

Re: Query on operation inputs

name: { get_input: web_app_name } > image: { get_property: [ web_app, image] } > exposed_port: { get_property: [ web_app, port] > } > target_host: { get_property: [ database, name] > } > target_port: {

Re: New mailing lists

am quite fine with having digests or transcripts from > Slack appear in the mailing list. > > As far as I understand, Slack is reserved to people with Apache ID, so > getting the conversation onto the mailing list would be good. > > Best regards, > Matej > > > Ran Ziv j

Re: Query on operation inputs

orter and > > complete example would help demonstrate what you mean. > > > > > > On Thu, May 25, 2017 at 9:56 AM, D Jayachandran < > > d.jayachand...@ericsson.com > > > wrote: > > > > > Hi Ran, > > > > > > When I refer the TOSCA spec, it

Re: Query on operation inputs

the actual operation definition) > > > Regards, > DJ > > -Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Sunday, May 28, 2017 6:14 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Query on operation inputs > > I've reviewed you

Re: Query on operation inputs

t;:64:25 > Failed to parse service template > > > I think the branch Tal provided https://github.com/apache/ > incubator-ariatosca/tree/ARIA-149-functions-in-operation-configuration > has fixed the issue on operation inputs. > > Regards, > DJ > > -Original Messa

Re: Query on operation inputs

executions start install -s s2 > Declared parameters "labels" have not been provided values > > Regards, > DJ > > -Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Thursday, June 01, 2017 5:24 PM > To: dev@ariatosca.incubator.apac

Re: Query related to substitution mapping

i agree for the most part, although I don't see it as part of the instantiation phase refactoring, but rather as a completely separate feature which I'd like us to work on in the near future. On Thu, Jun 1, 2017 at 7:27 PM, Tal Liron wrote: > Your expectations are reasonable: that ARIA would loo

Re: Query related to substitution mapping

y have this as > part of your backlog. > We just need to know if you have plans to include this in your upcoming > release ? > > > Regards, > DJ > -----Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Thursday, June 01, 2017 10:01 PM > To: d

ARIA dependencies License issues

Hi, I went over all of ARIA's dependencies (including recursive dependencies) and validated them against the Apache allowed licenses . We've done this before and found no issues, but this time two libraries came up as a possible problem. I hav

Re: Let's talk about scaling (ARIA-254)

Controlling node scaling via policy makes sense, but I do have a few concerns: 1) As you've mentioned, this would impose some overhead, for example when users would want to create multiple instances of a simple node-template. The scaling policies are definitely needed e.g. for group, but it'd have

A few questions about creating a release

Hi Suneel, John, I have a few quick questions about creating a release for an incubator project: 1) According to these links: 1 2 Incubating p

Re: Plugin structure and specifications

? Do we have any specifications on the structure of plugin ? --> A plugin should simply be a standard Python package really; There are no special constraints on its structure. If the plugin has dependencies, they do need to be compatible with ARIA's, as the plugin's code will be loaded in the same

Re: How can I use aria CLI options correctly?

Hi Dave, Unfortunately, the README is currently much outddated. That is why the "aria parse" command raises an invalid command error. We're working on updating the quick start guide, and hopefully it'll be up to date early next week, although that too isn't going to provide a full documentation a

Re: Let's talk about scaling (ARIA-254)

1. Got it. 2. Ok, makes sense. I might have been wrong thinking this policy should be special then. About storing in policy information in nodes/templates that the policy is associated with in general - sounds interesting, I'm not sure I'd implement this right away, I think it'd be better to hold

Re: Plugin structure and specifications

the plugin > specific types. > Could you point me to some documentation involving these or any example of > plugin.yaml > > > Regards, > DJ > > -Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Tuesday, June 06, 2017 6:41 PM > To: dev@ariato

Re: Missing support for type qualified name

Hi DJ, Sounds good. Feel free to create a new JIRA yourself! And thanks for posting on the dev list before creating this issue. One small note, I'd personally think of this as a "story" rather than a "bug" - We don't yet claim to be 100% TOSCA complaint, and we're familiar with several other miss

Re: Let's talk about scaling (ARIA-254)

Oh, I might have misunderstood then. But looks like we reached at the same conclusion at the end, so I guess we're good :) On Wed, Jun 7, 2017 at 6:51 PM, Tal Liron wrote: > > About storing in policy information in nodes/templates that the policy is > > associated with in general - sounds intere

Re: How can I use aria CLI options correctly?

(I've replied on this same mail two days ago, so I guess there's been some sort of a mistake. In any case, I've copy-pasted my reply here as well.) Hi Dave, Unfortunately, the README is currently much outddated. That is why the "aria parse" command raises an invalid command error. We're working

Re: Missing support for type qualified name

ces.com] > Sent: Thursday, June 08, 2017 11:47 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Missing support for type qualified name > > Thanks, DJ. This was on the list of things to do but we indeed forgot to > create a JIRA for it... > > On Thu, Jun 8, 2017 at 8

Re: How can I use aria CLI options correctly?

figure.sh > > 10:30:25 | E | web_app_1 Standard.configure failed" > > > > I have no idea why the configuration is failed, any way to trouble > > shooting the issue or where can I find more detailed error message? > > > > > -Original Message- > &g

Re: How can I use aria CLI options correctly?

gt; > > 10:29:51 | I | Executing: /tmp/tmpeuRKHt-configure.sh > > > 10:29:52 | I | Execution done (exit_code=1): > > > /tmp/tmpeuRKHt-configure.sh > > > 10:29:52 | E | web_app_1 Standard.configure failed > > > 10:30:24 | I | web_app_1 Standar

Re: How can I use aria CLI options correctly?

Pv6 capable hosts > > ::1 localhost ip6-localhost ip6-loopback > > ff02::1 ip6-allnodes > > ff02::2 ip6-allrouters > > #shldeOTCopen005 10.239.48.67 > > 10.239.48.159 ceph-dev.intel.com ceph-dev > > > > Will the demo application download any resource from ext

Re: Let's talk about scaling (ARIA-254)

I think that's a very good solution. The semantics of capability being first in precedence makes sense - basically if you'd like to scale a compute node, do it the "TOSCA way" - Otherwise, use the policy. I also agree that despite the quirkiness, the policy should have identical properties/default

Re: Let's talk about scaling (ARIA-254)

uity between the values. What do you think? > > On Tue, Jun 13, 2017 at 4:25 AM, Ran Ziv wrote: > > > I think that's a very good solution. The semantics of capability being > > first in precedence makes sense - basically if you'd like to scale a > > compute nod

Re: ARIA dependencies License issues

Bumping this again, still waiting for answers on these issues. On Sun, Jun 4, 2017 at 3:02 PM, Ran Ziv wrote: > Hi, > > I went over all of ARIA's dependencies (including recursive dependencies) > and validated them against the Apache allowed licenses > <https

Re: A few questions about creating a release

Bumping this as well. On Mon, Jun 5, 2017 at 5:08 PM, Ran Ziv wrote: > Hi Suneel, John, > > I have a few quick questions about creating a release for an incubator > project: > > > 1) According to these links: 1 > <http://incubator.apache.org/guides/releasemanageme

Re: ARIA dependencies License issues

some insight, but ultimately you > need to get some legal input (from legal-discuss) > > - Code formatting shouldn't be an issue, since its not required for the > execution of the code. > - Paramiko would be an issue. I would not include it as a dependency. > > John >

Re: aria install from source error

Hi DeWayne, The readme doesn't specify anything about a centos installation by the way - there should definitely be some system dependencies that might be required, so if you run into those please let us know so we'll update the readme accordingly. Your specific error, however, is caused by an ol

Re: A few questions about creating a release

Bumping this one more time, and also copying this to the legal mailing list. I'm not 100% sure that's the place for it, but perhaps someone there might be able to help. Thanks On Wed, Jun 14, 2017 at 6:17 PM, Ran Ziv wrote: > Bumping this as well. > > On Mon, Jun 5, 2017

Re: Creating a Source Release

Thanks John. Before we can follow these steps though, we'll need to find answers for some release-related questions I asked on a separate thread. I reposted these questions on the legal mailing list today, so hopefully we'll be getting answers soon. Ran On Tue, Jun 20, 2017 at 3:46 PM, John D. Am

Re: aria install from source error

other modules were easy to identity, unlike setuptools. Thanks. > > > > DeWayne > > > > On Fri, Jun 16, 2017 at 2:34 PM, Ran Ziv wrote: > > > > > Hi DeWayne, > > > > > > The readme doesn't specify anything about a centos installation b

Re: aria install from source error

Filppi > > wrote: > > > > > Ran, > > > > > > FYI, that worked, in addition to a ton of other modules I had to add. > > The > > > other modules were easy to identity, unlike setuptools. Thanks. > > > > > > DeWayne > > &g

Re: A few questions about creating a release

ackages available on Pypi to avoid confusion. > > > > > > On Thu, Jun 22, 2017 at 5:22 PM Arthur Berezin > > wrote: > > > > > On Tue, Jun 20, 2017 at 12:26 PM Ran Ziv wrote: > > > > > >> Bumping this one more time, and also co

Re: Website ready for builds?

Great, thanks! On Jun 22, 2017 19:10, "John D. Ament" wrote: > Ok, the website is up. http://ariatosca.incubator.apache.org/ > > Can you please add the incubator logo + disclaimer on it? > > John > > On Thu, Jun 22, 2017 at 10:41 AM John D. Ament > wrote: > > > That should start working after

Re: aria install from source error

18:39, "DeWayne Filppi" wrote: > Regarding six etc... I installed them based on specific errors I saw. > > On Thu, Jun 22, 2017 at 2:43 AM, Ran Ziv wrote: > > > I've updated the instructions on the readme. It now also separates ARIA > > installation from ARIA[

Re: Website Improvements

(1) + (2) - Arthur will update those on the website. (3) - The pip links will become valid as soon as we make a release as we'll have it on there as well. (4) - Oh that's indeed much better, I wasn't familiar with it. Thanks! I'll update the readme accordingly. Ran On Mon, Jun 26, 2017 at 5:19 PM

[VOTE] publish ariatosca 0.1.0

I created a tarball candidate for the 0.1.0 release and placed it in ARIA's /dist/dev folder: https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ The file is signed (.asc) and its MD5 / SHA512 checksums may be found in that folder as well. The list of issues Resolved for this release are

Re: [VOTE] publish ariatosca 0.1.0

ote that happens on general@incubator before actually > moving it to /dist/release > > John > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv wrote: > > > I created a tarball candidate for the 0.1.0 release and placed it in > ARIA's > > /dist/dev folder: > > http

Re: [VOTE] publish ariatosca 0.1.0

ching distribution found for apache-ariatosca > > - There is no DISCLAIMER file > - No instructions on how to run RAT > - I'm not sure this is a source release, many files don't match whats in > the repo (files added/missing?) > > Other things look fine: > - cont

Re: [VOTE] publish ariatosca 0.1.0

D. Ament wrote: > On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv wrote: > > > Suneel, re mentioning 72 hours - note that I simply used the recommended > > template for these messages from here: > > > > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx- > dev/20

Re: [VOTE] publish ariatosca 0.1.0

The vote is cancelled in light of a "-1" vote. I'll fix the mentioned issues next week and raise another vote. I could still use some clarification with regards to what constitutes a "source distribution" for this matter. Thanks, Ran On Thu, Jun 29, 2017 at 7:08 PM,

[VOTE] publish ariatosca 0.1.0 (#2)

This is a vote to release Apache AriaTosca (Incubating) 0.1.0. If the vote passes, another vote for approving the release will take place on the Apache Incubator's PMC. I created a tarball candidate for the 0.1.0 release and placed it in ARIA's /dist/dev folder: *https://dist.apache.org/repos/dis

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

nclude the root URL. Or you can just dump everything directly into > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ . > > For the contents in sdist and bdist, please include the md5 and sha files. > > John > > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv wrote: > > &g

Re: Inputs to a life cycle operation

Hi DJ, You're definitely correct - this issue is in fact already in a pull request , and will hopefully be merged soon. Ran On Mon, Jul 3, 2017 at 1:04 PM, D Jayachandran wrote: > Hi, > > With the current ARIA implementation, > > > *

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

1) Validated signature & checksums 2) Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name 3) Ran RAT check 4) Made a clean install using "pip install ." 5) Ran tests using "make tests" +1 On Sun, Jul 2, 2017 at 4:18 PM, Ran Ziv wrote: >

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

Thanks John. I took a note of adding the relevant instructions to the readme. I'll make sure it's added soon. On Mon, Jul 3, 2017 at 2:13 PM, John D. Ament wrote: > On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv wrote: > > > Okay. I didn't have anything to go by since

Re: imperative workflows (1.1)

Yup. We have given some thought as to how to implement 1.1 workflows including conditional tasks ("on_success"/"on_failure") and it maps well into the workflow engine, but generally speaking supporting TOSCA 1.1 is not currently a top item. On Tue, Jul 4, 2017 at 8:12 AM, Tal Liron wrote: > Not

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

bdist, source} * {sha, md5} hashes and sigs > > 2. Built project from {source} with "pip install" > > 3. Ran tests > > 4. Verified -incubating in artifacts names. > > > > > > On Mon, Jul 3, 2017 at 7:13 AM, John D. Ament > > wrote: > >

Re: Missing support for type qualified name

ng to debug or figure out these issues :) Ran On Sun, Jun 11, 2017 at 11:36 AM, Ran Ziv wrote: > Thanks DJ. > > Note that in order for the project to be able to accept your pull request, > you'd first have to sign up Apache's ICLA agreement. > See more here <https://ww

Re: create_template

Hi DeWayne, The error probably means that the ARIA TOSCA extension isn't properly installed, and therefore the parser can't find a valid reader. The error message could probably have been somewhat clearer.. Feel free to create a JIRA issue over this (or I'll create one if you don't :)). Note that

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

. Ament (binding) - +1, Suneel Marthi (binding) - +1, Justin Mclean (binding) - +1, Ran Ziv (non-binding) - +1, Avia Efrat (non-binding) - +1, Tal Liron (non-binding) Thank you for your support! We'll continue with the release now. Ran, on behalf of Apache ariatosca PPMC

Re: create_template

't > present when I used 'pip install .', so I switch to the makefile. This > completed and appeared to put everything in it's right place, but the error > is unchanged. To be specific I see: > > Validation issues: > 0: presenter not found > Presenter

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

I'm all for it, though I don't really like "entry-level" for the name of the label :) Any other suggestions? On Mon, Jul 10, 2017 at 5:09 AM, John D. Ament wrote: > I think it's a good idea. Lots of other projects do something similar. We > could link to a query with this from the proposed co

[ANNOUNCE] Apache AriaTosca 0.1.0-incubating released

The Apache AriaTosca (incubating) team is pleased to announce the release of AriaTosca 0.1.0. AriaTosca offers an easily consumable SDK and a CLI to implement TOSCA (Topology and Orchestration Specification of Cloud Applications) based solutions. The release is available at: https://www.apache.or

Re: Congrats on the First Release!

Thanks :) 1) Documenting the release process - I have it on my list and will get it on our Confluence soon. I also wrote some scripts to ease this process, we'll probably merge them onto the repo one way or another soon. 2) The sdist comes with generated HTML pages; We should probably have these o

Installation issue in 0.1.0 release

I've found the following issue with the 0.1.0 release: https://issues.apache.org/jira/browse/ARIA-304 A fix for this has already been merged into master; PR can be seen here: https://github.com/apache/incubator-ariatosca/pull/178 I'm proposing the possibility of creating a quick 0.1.1 release f

Re: Congrats on the First Release!

you want to create JIRAs for these? > > John > > On Mon, Jul 10, 2017 at 8:13 AM Ran Ziv wrote: > > > Thanks :) > > > > 1) Documenting the release process - I have it on my list and will get it > > on our Confluence soon. I also wrote some scripts to ease this

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

tore the quick introduction to TOSCA and theoretical > overview for everyone to see? > Thanks > > Steve B > > > > > -Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Monday, July 10, 2017 4:39 AM > To: dev@ariatosca.incubator.apache.org &

[VOTE] publish ariatosca 0.1.1

This is a vote to release Apache AriaTosca (Incubating) 0.1.1. If the vote passes, another vote for approving the release will take place on the Apache Incubator's PMC. I created a tarball candidate for the 0.1.1 release and placed it in ARIA's /dist/dev folder: *https://dist.apache.org/repos/dis

Re: Query on operation inputs

t; Hi Tal, > > > > > > Please find below the git repo of my example. > > > > > > https://github.com/djay8887/Aria-operationInputs > > > > > > regards, > > > DJ > > > > > > -Original Message- > > > From

Re: Installation issue in 0.1.0 release

frequently. Gets in the habit > of > > how to do it. So if you or someone else has the cycles to cut the > release > > I say do it. > > > > I personally don't care what version it is, its just a number. > > > > John > > > > On Mon, Jul 10,

Re: Inputs to a life cycle operation

The issue was indeed merged a few days ago. Note however that it's not a part of the 0.1.0 release (nor will it be a part of the 0.1.1 one, as it wasn't categorized as a bug fix but as a new feature). It will be a part of a future 0.2.0 release. On Mon, Jul 3, 2017 at 1:39 PM, Ran

Re: Missing support for type qualified name

nges , am not sure if > I have to make another PR ? > Could you please advice me here ? > > > Regards, > DJ > > -Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Friday, July 07, 2017 3:28 PM > To: dev@ariatosca.incubator.apache.org > S

Re: [VOTE] publish ariatosca 0.1.1

On Tue, Jul 11, 2017 at 2:27 AM, Suneel Marthi wrote: > > > +1 binding > > > > 1. Checked Sigs and Hashes > > 2. Verified RAT check > > > > > > On Mon, Jul 10, 2017 at 1:04 PM, Ran Ziv wrote: > > > > > This is a vote to release Ap

Re: workflow list API

There's actually a JIRA issue for it: https://issues.apache.org/jira/browse/ARIA-246 Although, as Tal's mentioned, we've never been 100% certain yet about what should be the behavior here. On Wed, Jul 12, 2017 at 8:33 AM, Tal Liron wrote: > Do you mean the CLI command? > > We actually have tal

Re: Missing support for type qualified name

are successful. Kindly check and let me > know if its fine. > > Regards, > DJ > -Original Message- > From: Ran Ziv [mailto:r...@gigaspaces.com] > Sent: Tuesday, July 11, 2017 2:07 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Missing support for type q

Re: Plugin validation

Indeed, service-templates would *not* have to be modified when a newer version of plugin is installed. At the moment, the plugin matching mechanism is rather simplified, but we plan on extending it (and it should actually be pretty simple to do so). See related JIRA issue here: https://issues.apac

Re: workflow runner error

Could it be that you first used an older, non-release version of ARIA, and then used 0.1.0 without first resetting your ARIA working directory (e.g. "aria reset -f")? The task table should indeed have the said column, as can be seen here: https://github.com/apache/incubator-ariatosca/blob/0.1.0/ar

Re: workflow runner error

:40 AM, DeWayne Filppi > wrote: > > > Yes, that absolutely could be the case. I'll try a reset. > > > > On Wed, Jul 12, 2017 at 3:40 PM, Ran Ziv wrote: > > > > > Could it be that you first used an older, non-release version of ARIA, > > and

Re: Congrats on the First Release!

ager of the next release. Please let me know if you have any comments on the document or if you think I might have missed something. On Mon, Jul 10, 2017 at 4:11 PM, Ran Ziv wrote: > Done: > https://issues.apache.org/jira/browse/ARIA-306 ( with sub-tasks > https://issues.apache.org/

[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/b0571ee44c5f5bb325cc7f49e47

[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 /dist/relea

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

e votes were ( https://lists.apache.org/thread.html/0c5fe55ddeb138bc318242f96d529ce7c2be4c222c0d758562f5ea45@%3Cgeneral.incubator.apache.org%3E ): - +1, John D. Ament (binding) - +1, Suneel Marthi (binding) - +1, sblack...@apache.org (binding) - +1, Ran Ziv (non-binding) - +1, Maxim Orlov (non-bind

Re: Congrats on the First Release!

release should be deleted. > > John > > On Thu, Jul 13, 2017 at 6:58 AM Ran Ziv wrote: > > > I've documented the release process on our Confluence: > > https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process > > > > This, together with the rel

[ANNOUNCE] Apache AriaTosca 0.1.1-incubating released

The Apache AriaTosca (incubating) team is pleased to announce the release of AriaTosca 0.1.1. AriaTosca offers an easily consumable SDK and a CLI to implement TOSCA (Topology and Orchestration Specification of Cloud Applications) based solutions. The release is available at: https://www.apache.or

Re: Contribution to aria

Sorry for the late reply, but one more important link to check out is the contribution guide, here: https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+to+ARIA It can also direct you to other Apache and general "how to get started with Open Source" guides. On Tue, Aug 1, 2017 at 5:4

Re: Service Composition / Substitution Mapping

The sensible defaults Tal's mentioned sound indeed sensible to me. I'd also like users to have control over this, though I'm a bit worried about us getting too carried away with how arbitrarily we use policies for configuring, well, pretty much anything. It might not be a problem right now but I'm

Re: Openstack plugin

For future readers of this thread, you can find an example on how to use this plugin here: https://cwiki.apache.org/confluence/display/ARIATOSCA/OpenStack+Hello+World On Wed, Jul 26, 2017 at 6:25 PM, Maxim Orlov wrote: > you got most of it right :). You would need to follow these steps: > 1. Ins

Re: ARIA install on MAC

Hi Steve, It does sound like an issue related to the setuptools version. What made you unable to upgrade it? Also, these links might be helpful: https://bitbucket.org/ruamel/yaml/issues/86/osx-cannot-install https://bitbucket.org/ruamel/yaml/issues/32/cannot-run-setup-script-on-python-2710 https:

Re: ARIA install on PC

Hi Steve, It seems like your aria\exceptions.py file is of a wrong version somehow. If you take a look at its 0.1.1 revision, you'll see the import line in line 20 (the last line in your stack trace) is a different one than the one mentioned in the error: https://github.com/apache/incubator-ariato

Re: ARIA install on PC

l version 0.2.0. > I have the same error when I run aria --version. > Line 20 from version 0.2.0 on my PC has the following line: > from ..exceptions import AriaError > I have attached the doc. > > Should I give up :) ? > > -Steve > > -Original Message- > From

Re: Service Composition / Substitution Mapping

I'd say right now we're looking at "static service composition" which is only about "substituting service templates", not "substituting service". If a service is already running, it will not be used. I think what Tal meant was that each service template - whether the top level one or one of the su

Re: Service Composition / Substitution Mapping

I'd say right now we're looking at "static service composition" which is only about "substituting service templates", not "substituting service". If a service is already running, it will not be used. I think what Tal meant was that each service template - whether the top level one or one of the su

Re: ARIA install on MAC

ry/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", > line 131, in copy2 > > copystat(src, dst) > > File > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py", > line 103, in copystat > > os.chflags(dst, st.st_f

Re: Service Composition / Substitution Mapping

- Is it okay to delete(dissolve) the substituting service after it > is used to create the composed service. ? > > Starting with it might be a good idea to only have "substituting service > templates" approach. > > Regards, > DJ > -Original Message- >

Re: subscribe

Hi Vishwanath, In order to subscribe to the lists, you need to send your subscription request to "user-subscr...@ariatosca.incubator.apache.org" and " dev-subscr...@ariatosca.incubator.apache.org", rather than to the actual lists. Ran On Fri, Aug 18, 2017 at 5:30 AM, Vishwanath Jayaraman < vis

Re: Running into issue when installing aria[ssh] on Ubuntu 16.04

This seems like a simple mistake, the package's name was changed when ARIA became an Apache incubator project. Please try to install "apache-ariatosca[ssh]" instead of "aria[ssh]". On Fri, Aug 18, 2017 at 5:14 PM, Vishwanath Jayaraman < vishwana...@hotmail.com> wrote: > Hi, > > I am new to ARIA

Re: Running into issue when installing aria[ssh] on Ubuntu 16.04

e past. > > Thanks > > Vish > > > > From: Ran Ziv > Sent: Friday, August 18, 2017 9:31 AM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Running into issue when installing aria[ssh] on Ubuntu 16.04 > > This seems like a simple mi

  1   2   3   4   5   6   7   8   >