Re: GIT/JIRA Integration

Bumping this again. On Sun, Jan 22, 2017 at 11:49 AM, Ran Ziv <r...@gigaspaces.com> wrote: > Any news about this perhaps? > > On Wed, Jan 4, 2017 at 5:17 PM, Ran Ziv <r...@gigaspaces.com> wrote: > >> Sounds good. Any idea when it's supposed to happen so I'll know

Re: Plan for first AriaTosca release ?

I don't think we're there quite yet, but we're getting closer. We're making many changes to the data model at the moment, so it's probably a good idea to wait until those are complete and we can fully run TOSCA workflows before we make the first release. On Tue, Jan 24, 2017 at 5:00 PM, Suneel

Re: GIT/JIRA Integration

..@apache.org> wrote: > Take a look now. Just checked a few tickets > > - Branches are shown > - Commits are shown > - everything is under the dev tag > > Assuming that's good, I'll shut off the commit edits inline. > > John > > On Thu, Feb 16, 2017 at 9:38 AM Ran

Re: GIT/JIRA Integration

How about now? :) On Tue, Jan 31, 2017 at 5:21 AM, John D. Ament <johndam...@apache.org> wrote: > I just pinged them again. > > On Mon, Jan 30, 2017 at 7:41 PM Ran Ziv <r...@gigaspaces.com> wrote: > > > Bumping this again. > > > > On Sun, Jan 22, 2017

ARIA update

Hi all, We've been thinking it'd possibly be a good idea to update about current progress once a week or two. This should usually be pretty short, but might help some follow ARIA on a high level without having to delve into the JIRA issues etc. On this week's news: - The main story is the

Questions regarding CI, PR and documentation

Hi, I have some questions for our mentors: 1) CI - we've noticed some Apache projects use online services rather than the infra tools offered by Apache. We're leaning towards using TravisCI, however we're somewhat worried that since all apache projects are under a

Re: JIRA configuration changes

her emphasize, the less options and fields in a Jira > > issue screen (as long as it suits our general needs), the better. > > > > On Mon, Nov 14, 2016 at 10:04 PM, Ran Ziv <r...@gigaspaces.com> wrote: > > > > > 1) AFAIK in JIRA this is only possible using cus

JIRA configuration changes

Hi everyone, So over a month ago I created this JIRA ticket for the Apache infra team, asking them to make several adjustments in our JIRA configuration. It still hasn't been taken care of, but in any case John has brought it to my attention

Re: JIRA configuration changes

letely understand your concern, and indeed I mean for this data to be public knowledge, and for outside contributers to be allowed in the "sprint" if/when necessary (and only if they'd be interested in it). Ran On Mon, Nov 14, 2016 at 9:19 PM, John D. Ament <johndam...@apache.org> wro

Re: JIRA configuration changes

board, but the issue type scheme is not part of that. On Mon, Nov 14, 2016 at 9:53 PM, John D. Ament <johndam...@apache.org> wrote: > On Mon, Nov 14, 2016 at 2:29 PM Ran Ziv <r...@gigaspaces.com> wrote: > > > John - > > > > 1) You can see the fields that are on the

Re: Podling Report Reminder - November 2016

Done, please let me know if you have any additional comments. On Fri, Nov 4, 2016 at 3:36 PM, Ran Ziv <r...@gigaspaces.com> wrote: > im updating it now > > On Fri, Nov 4, 2016 at 3:36 PM, Arthur Berezin <art...@gigaspaces.com> > wrote: > >> Thanks Ran! >

Re: Podling Report Reminder - November 2016

26 PM John D. Ament <johndam...@apache.org> > wrote: > > > Ok, thanks for clarifying. Can you update the report? > > > > John > > > > On Fri, Nov 4, 2016 at 9:23 AM Ran Ziv <r...@gigaspaces.com> wrote: > > > > Suneel - it's not completely

Re: Podling Report Reminder - November 2016

Suneel - it's not completely like that - ARIA is a new project in most senses, so there isn't many to migrate to the mailing lists. JIRA is a different case though, and in a while we'll probably have others create issues on there as well. John - Arthur's meaning is that additional developers

Re: JIRA Issue Scheme

L. > > John > > On Sun, Oct 30, 2016 at 6:30 PM Ran Ziv <r...@gigaspaces.com> wrote: > > > The reason we asked for this is because we wanted to simplify some of the > > JIRA mechanisms (screens, issues) but with only requiring minimal changes > > from

Re: [DISCUSS] Move Aria Tosca to Reporting Group 1

No objections here. On Wed, Nov 2, 2016 at 5:09 AM, Suneel Marthi wrote: > +1 for the move. But we still do file the November report correct? and the > next report would be due Jan 2017. > > > > On Tue, Nov 1, 2016 at 10:36 PM, John D. Ament >

Re: Dec 16 Podling Report

Thanks John. Sorry again about that last part :) On Thu, Dec 8, 2016 at 4:50 AM, John D. Ament wrote: > I added the following mentor comment to the report: > > johndament: The podling is still getting its feet wet. Discussions are > starting to happen on the mailing

Re: [DISCUSS] Rename ARIATOSCA to ARIA

The intention was not at all to rename the project - when the proposal had been made, the name "ARIA" was considered as well, and ARIATOSCA was the one chosen, for various reasons, and we should probably stick with it. This is actually a much smaller issue, not even about renaming the JIRA project

Re: GIT/JIRA Integration

. I don't have an account on that > JIRA. Are you talking about the "Development" section on the far right? > > That's a feature in newer JIRA versions. We're on 6.3. I'd have to see if > that's an option first. > > John > > On Tue, Jan 3, 2017 at 8:31 AM Ran Ziv <

Re: GIT/JIRA Integration

Thanks John, I see that basically all git traffic now appears on JIRA as comments - that indeed seems too noisy IMO. Is it possible to configure it so that the git-jira integration will simply present commits/branches/PRs related to a specific JIRA on a separate section rather than in comments

Re: GIT/JIRA Integration

lic offering. Assuming no qualms > with enabling fisheye for ARIAs repos, this will happen automatically. Any > concerns with that? Once its up, we can turn off the other format. > > John > > On Wed, Jan 4, 2017 at 7:05 AM Ran Ziv <r...@gigaspaces.com> wrote: > > > Yes,

Re: [DISCUSS] Website

do we? (want to use jek) On Mon, Jan 9, 2017 at 2:50 PM, Arthur Berezin wrote: > John, Suneel, We would like to migrate the website to Jekyll, where can I > find more information on what servers the web pages from the ASF repos? Is > there anyone that could help with the

Re: ARIA install on PC

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: Ran

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

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

Re: ARIA install on MAC

> os.chflags(dst, st.st_flags) > > OSError: [Errno 1] Operation not permitted: '/var/folders/73/sq1jnvgx0l7_ > 18h9kc7v09_rgp/T/pip-w_p4Ck-uninstall/System/Library/ > Frameworks/Python.framework/Versions/2.7/Extras/lib/ > python/six-1.4.1-py2.7.egg-info' > > > > >

Re: Service Composition / Substitution Mapping

ce. ? > - 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 > -

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

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:

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? >

Re: Missing support for type qualified name

> Now the CI tests and build jobs 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 > Subj

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

[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: Missing support for type qualified name

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 > Subject: Re

Re: [VOTE] publish ariatosca 0.1.1

uot; > > +1 > > On Tue, Jul 11, 2017 at 2:27 AM, Suneel Marthi <smar...@apache.org> wrote: > > > +1 binding > > > > 1. Checked Sigs and Hashes > > 2. Verified RAT check > > > > > > On Mon, Jul 10, 2017 at 1:04 PM, Ran Ziv <r...@gigas

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 Ziv &l

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

[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:

Re: Installation issue in 0.1.0 release

podlings should try to cut releases 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. > > > > Jo

Re: Query on operation inputs

n operation inputs > > > > > > Hi Tal, > > > > > > Please find below the git repo of my example. > > > > > > https://github.com/djay8887/Aria-operationInputs > > > > > > regards, > > > DJ > > > > > > -O

Re: Missing support for type qualified name

out these issues :) Ran On Sun, Jun 11, 2017 at 11:36 AM, Ran Ziv <r...@gigaspaces.com> 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:

[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

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

Re: workflow runner error

hu, Jul 13, 2017 at 3:40 AM, DeWayne Filppi <dewa...@gigaspaces.com> > wrote: > > > Yes, that absolutely could be the case. I'll try a reset. > > > > On Wed, Jul 12, 2017 at 3:40 PM, Ran Ziv <r...@gigaspaces.com> wrote: > > > > > Could it be that you f

Re: Congrats on the First Release!

anager 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 <r...@gigaspaces.com> wrote: > Done: > https://issues.apache.org/jira/browse/ARIA-306 ( with sub-tasks > http

[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:

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

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

Re: Congrats on the First Release!

wrote: > Ran, > > Do you want to create JIRAs for these? > > John > > On Mon, Jul 10, 2017 at 8:13 AM Ran Ziv <r...@gigaspaces.com> wrote: > > > Thanks :) > > > > 1) Documenting the release process - I have it on my list and will get it > &g

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

ore 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 > S

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:

Re: [VOTE] publish ariatosca 0.1.0

No matching 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: > - contains incubati

Re: [VOTE] publish ariatosca 0.1.0

wrote: > On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv <r...@gigaspaces.com> 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/

Re: [VOTE] publish ariatosca 0.1.0

re's a second vote that happens on general@incubator before actually > moving it to /dist/release > > John > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv <r...@gigaspaces.com> wrote: > > > I created a tarball candidate for the 0.1.0 release and placed it in > ARIA's > >

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, Ran Ziv

[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 (#2)

only need to > include 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 <r...@gigas

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

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

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 <johndam...@apache.org> wrote: > On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv <r...@gigaspaces.com> wrote: > > > Okay

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

binding > > > > 1. Verified {sdist, 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

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

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

Re: aria install plugin openstack

Please see Wagon's README here: https://github.com/cloudify-cosmo/wagon The archive's format has been changed from tar.gz to zip - This means that you're either using a .wgn file which is too old, or if you built the wagon file yourself - wagon code that is not up to date. ARIA only supports

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 <

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

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

e past. > > Thanks > > Vish > > > > From: Ran Ziv <r...@cloudify.co> > 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 > > Th

Re: GIT/JIRA Integration

//issues.apache.org/jira/browse/INFRA-13431?page= > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel> > ? > > John > > On Sun, Feb 19, 2017 at 8:05 AM Ran Ziv <r...@gigaspaces.com> wrote: > > > Yes, I see it now, although when I click any of these (e.g. &q

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

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: 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 <r...@gigaspaces.com> wrote: > Bumping this as well. > > On M

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.

Re: aria install from source error

Fri, Jun 16, 2017 at 7:21 PM, DeWayne Filppi <dewa...@gigaspaces.com> > > 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 setu

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

Re: aria install from source error

, "DeWayne Filppi" <dewa...@gigaspaces.com> wrote: > Regarding six etc... I installed them based on specific errors I saw. > > On Thu, Jun 22, 2017 at 2:43 AM, Ran Ziv <r...@gigaspaces.com> wrote: > > > I've updated the instructions on the readme. It now also separ

Re: aria install from source error

n of other modules I had to add. > The > > other modules were easy to identity, unlike setuptools. Thanks. > > > > DeWayne > > > > On Fri, Jun 16, 2017 at 2:34 PM, Ran Ziv <r...@gigaspaces.com> wrote: > > > > > Hi DeWayne, > > > >

Re: A few questions about creating a release

ckages so that we only have new > ASF > > packages available on Pypi to avoid confusion. > > > > > > On Thu, Jun 22, 2017 at 5:22 PM Arthur Berezin <art...@gigaspaces.com> > > wrote: > > > > > On Tue, Jun 20, 2017 at 12:26 PM Ran Ziv <r...@gigasp

Re: GIT/JIRA Integration

ration. Just make sure its clear that you want the fisheye > > integration still on. > > > > John > > > > On Thu, May 18, 2017 at 6:00 PM Ran Ziv <r...@gigaspaces.com> wrote: > > > > > @John, > > > > > > Bumping this again, as the

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

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

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

Re: Query on operation inputs

andran < > > d.jayachand...@ericsson.com > > > wrote: > > > > > Hi Ran, > > > > > > When I refer the TOSCA spec, it says > > > > > > " An optional key that declares a property as required (true) or not > > &

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

Re: Query on operation inputs

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

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 <r...@gigaspaces.com> wrote: > Hi John, > > It took some time, but I finally have the Fisheye extension working on > JIRA. > It'd be great

Re: Query related to substitution mapping

tion. It's good to know you already 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] > Sen

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

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

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

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

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@ariatosca.incubator.apache.org &

Re: Query on operation inputs

d with a value in 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 > >

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

Re: Query on operation inputs

ubernetes-deployment.yaml":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 &g

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

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

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

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

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

  1   2   3   4   5   6   7   >