Re: Property type 'null' validation issue

This does sound like a bug, and I am not familiar with a JIRA ticket for it. Feel free to create one. On Mon, Sep 18, 2017 at 8:13 AM, Vaishnavi K.R wrote: > Hi, > > > I tried using the 'null' property type as mentioned in the TOSCA simple > YAML 1.0 specification.

Re: Unique identification of an instance element across services

identified using the UUID. > > > So I see the uniqueness should prevail across the elements like service > templates, service instances and node instances. > > > Thanks, > > /Vaish > > > From: Ran Ziv <r...@cloudify.co> >

Re: Unique identification of an instance element across services

I can't seem to be able to access our JIRA at the moment, but generally speaking, the CLI currently supports "static completion" only, i.e. it auto-completes CLI commands but not object names. We tried implementing dynamic completion (e.g. tab on "-s" would auto-complete service names from the

Re: Use & impact of role/host attribute in ARIA

; > > > > The reason "role" exists is to avoid hardcoding functionality to type > > > names. Certain normative types play special roles in TOSCA: certain > > > relationships are special, as are certain capabilities, data types, > > > etc. In order to avoid havi

Re: Selecting and installing a specific stack

In your example, did you mean that the pairs A, B, C are supposedly of the same "abstract type" (e.g. C are both DBs, etc.)? If so, substitution mapping might be useful here as well. Otherwise, I'm not really sure why you'd see the two templates as "linked" or similar in any way. On Sat, Sep 9,

Re: operation dependencies

Avia's mentioned at one point that we might have misunderstood the spec at this section, and that in fact it can be possible to pass arbitrary inputs into operations regardless of the interface definition - which would mean this notion of "configuration" might be unnecessary. Also, note that the

Re: openstack plugin

et me ask a simple > question whos answer may clear things up: I want to use server "userdata" > using the Openstack plugin from ARIA. The question is "how can I make that > happen?" > > On Wed, Sep 6, 2017 at 1:39 AM, Ran Ziv <r...@cloudify.co> wrote: > &

Re: Use & impact of role/host attribute in ARIA

s not > aligned with TOSCA spec. > > Regards, > DJ > > -----Original Message- > From: Ran Ziv [mailto:r...@cloudify.co] > Sent: Wednesday, September 06, 2017 2:16 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Use & impact of role/host attribu

Re: Use & impact of role/host attribute in ARIA

This is where the execution plugin decides whether to run locally or remotely (ssh): https://github.com/apache/incubator-ariatosca/blob/0.1.1/aria/orchestrator/execution_plugin/instantiation.py#L42 This is indeed related to the "host" role definition. Here you can see the assignment of the

Re: openstack plugin

d: false > > I have my own copy of the plugin.yaml file that I'm making changes to so > things will work for me, so this is fine. I think the PR needs to go > beyond this, and ensure that all potential parameters are defined ( or at > least the parameters that the Openstack

Re: error after adding "userdata" or "user_data" to plugin.yaml

DeWayne, highlighting doesn't work too well with the mailing list - we only see simple text. The error doesn't ring a bell here. On Wed, Sep 6, 2017 at 8:43 AM, DeWayne Filppi wrote: > I have no idea if its a bug. Just seeing if it looked familiar to anyone. > Thought

Re: Service Composition / Substitution Mapping

gnizes this custom type. > > > Assuming the abstract node type would be substituted from a > > stored > > > substituting service template, we need to at least import the custom > node > > > types and have it part of the same CSAR package. > > >

Re: server create problem

> On Sat, Sep 2, 2017 at 2:41 AM, Ran Ziv <r...@cloudify.co> wrote: > > > You're right. The plugin itself does declare specific versions for the > > novaclient: > > https://github.com/cloudify-cosmo/cloudify-openstack- > > plugin/blob/2.0.1/setup.py

Re: openstack plugin

Could you link to the relevant place? Do you mean that in the original plugin.yaml you could set the userdata field (under properties? under the "server" property? args?) but only due to it not having had to be declared explicitly? There's a good chance that if this were possible than it simply

Re: server create problem

N: 'Client' > > object has no attribute 'images' > > > > Seems unrelated to ARIA. > > > > > > On Fri, Sep 1, 2017 at 2:28 AM, Ran Ziv <r...@cloudify.co> wrote: > > > >> Shouldn't the Nova client actually have an "images" attribute

Re: server create problem

be somebody who wrote this logic can help. Basically, the logic take the > 'image' property, makes it plural, and then tries to find it in the client > class. It doesn't find it and it blows up. Maybe I've got a bad version > of the openstack plugin: 2.2.0 > > > On Thu, Aug 31, 2017 a

Re: server create problem

tor-ariatosca/aria/orchestrator/ > workflows/executor/process.py", > line 342, in _main > |task_func(ctx=ctx, **operation_arguments) > | File > "/home/vagrant/venv/lib/python2.7/site-packages/ > adapters/context_adapter.py", > line 434, in wrapper > |ct

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

ria services create my-service -t my-service-template > > aria executions start install -s my-service > > > > I was also able to launch the url http://:9090 successfully. > > Thanks a lot for your patience and guidance. > > Vish > > > ___

Re: Podling Report Reminder - September 2017

I've updated the Podling report here: https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09 On Wed, Aug 30, 2017 at 6:54 AM, wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

p: > > type: WebApp > > properties: > > port: 9090 > > requirements: > > - host: web_server > > interfaces: > > Standard: > > configure: scripts/configure.sh > > start: scripts/star

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

File "/usr/local/lib/python2.7/dist-packages/aria/ > orchestrator/execution_plugin/ctx_proxy/client.py", line 101, in main > > |timeout=args.timeout) > > | File "/usr/local/lib/python2.7/dist-packages/aria/ > orchestrator/execution_plugin/ctx_proxy/client.py&q

Re: subnet connected to router

Can we re-state the problem at hand? It's been somewhat difficult to follow this thread. On Tue, Aug 29, 2017 at 3:45 AM, Tal Liron wrote: > Great! So, now let's think what makes your full Openstack example > different... I'm off for the day, will continue looking tomorrow. >

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

o the "entry_points". I'll create a JIRA for this. On Tue, Aug 29, 2017 at 11:42 AM, Ran Ziv <r...@cloudify.co> wrote: > Vishwanath, > Sorry for not having followed up this issue earlier. > I tried launching a 16.04 container earlier and following your steps, and >

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

> > > > > > > > > > > > > > > > > > > > Author: ARIA > > > > > > > > > > Author-email: dev@ariatosca.incubator.apache.org > > > > > > > > > > License: Apache License 2.0 >

Re: uninstall behavior

Not really. There's a JIRA ticket about this Have you tried resuming the workflow? On Thu, Aug 24, 2017 at 9:08 PM, DeWayne Filppi wrote: > Uninstall fails upon error. This has bad consequences for cleaning up > partial installs. Here's what I see: > > 1. Run install to

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

. Ran On Fri, Aug 25, 2017 at 12:43 PM, Ran Ziv <r...@cloudify.co> wrote: > Hi Vishwanath, > > Thanks for helping in updating the hello-world example readme. Sorry about > the lack of clarity there regarding the need to copy the template's > resources as well. > &

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

stall apache-ariatosca > > > > > > - sudo apt-get install -y python-dev gcc libffi-dev libssl-dev > > > > > > - sudo pip install apache-ariatosca[ssh] > > > > > > > > > After I execute > > > > > > 'aria service-templates store examp

Re: cli throwing PresenterNotFoundError

Hey DeWayne, Did you manage to resolve this problem? What was it? On Fri, Aug 18, 2017 at 7:18 AM, DeWayne Filppi wrote: > Thanks. Yeah I saw that. I didn't install with pip. Tried "make install" > and it didn't work. Tried "make install-virtual" and that didn't work.

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

e service_template/1/scripts/configure.sh > does not exist > > 20:50:18 | I | > aria.orchestrator.execution_plugin.operations.run_script_locally > | {u'process': {}, u'script_path': u'scripts/configure.sh'} > =END CONSOLE OUTPUT= > > > Vish > > > _

Re: cloudify openstack plugin example

I actually think it still might be related to the issue I mentioned above :) if the operation input isn't set with actual values, the node property should take hold - but because of the bug I mentioned the operation input receives empty yet still set values and therefore possibly overrides the

Re: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

dard.configure failed > web_app_1 Standard.configure started... > web_app_1 Standard.configure failed > console output end======== > > > Is the above you saw as well? > > Thanks > > Vish > > > >

Re: cloudify openstack plugin example

Might be related to this bug: https://issues.apache.org/jira/browse/ARIA-349 Which was recently fixed in this PR: https://github.com/apache/incubator-ariatosca/commit/8981791a10f91cb4f99ff8c01fd6b130b470ffae On Wed, Aug 23, 2017 at 9:15 PM, DeWayne Filppi wrote: > I see

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: Seeing error "Validation issues: unknown parent type "tosca:Root" in WebServer"

Hi Vishwanath, I just tried it myself and the service template parses fine. This is related to this change: https://github.com/apache/incubator-ariatosca/commit/c2b8e65b41c013bfd4ee14ea47268083f8b20822 The commit was introduced after 0.1.1 was released, so I think what might be the case here

Re: pip executable expected as part of plugin install.

Can you try to explain again what's the issue you're seeing with the way Wagon works right now? We could create a pull request for Wagon as well, but I'm not sure I understand the problem at the moment. On Wed, Aug 16, 2017 at 6:04 PM, D Jayachandran wrote: > Even

Re: JIRA: Assign button not available

It seems like you have to be added as a "contributor" role before you can be assigned to an issue at the moment. I can't change this permission scheme myself. I think it might actually be a single permissions scheme across Apache projects, but I'm not sure about that. In any case I added you as a

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

> 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

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

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

[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

[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

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

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

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

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

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

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

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

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

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

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

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

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

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

Re: ARIA dependencies License issues

I can provide 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. > > Joh

Re: A few questions about creating a release

Bumping this as well. On Mon, Jun 5, 2017 at 5:08 PM, Ran Ziv <r...@gigaspaces.com> 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.

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 <r...@gigaspaces.com> wrote: > Hi, > > I went over all of ARIA's dependencies (including recursive dependencies) > and validated them against the Apache allowed

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: How can I use aria CLI options correctly?

ble for IPv6 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 res

Re: How can I use aria CLI options correctly?

30:24 | I | web_app_1 Standard.configure started... > > > 10:30:24 | I | Executing: /tmp/tmpvwDbY0-configure.sh > > > 10:30:25 | I | Execution done (exit_code=1): > > > /tmp/tmpvwDbY0-configure.sh > > > 10:30:25 | E | web_app_1 Standard.configure failed" > &g

Re: How can I use aria CLI options correctly?

xit_code=1): /tmp/tmpvwDbY0-configure.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? > > > >

Re: Missing support for type qualified name

Liron [mailto:t...@gigaspaces.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... >

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

  1   2   3   4   5   6   7   >