RE: Inputs and Node object context for python and shell scripts

Hi Max, Thanks for the info. So with this decorator we get only the attributes and properties wrapped as dictionary. All other node objects like relationships, capabilities and interfaces are as wrapped mapped collections. Regards, DJ -Original Message- From: Maxim Orlov [mailto:ma...

Re: Service Composition / Substitution Mapping

I agree! Luckily metadata exists in the 1.0 spec. :) http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/cos01/TOSCA-Simple-Profile-YAML-v1.0-cos01.html#_Toc379455044 On Tue, Aug 1, 2017 at 7:16 PM, DeWayne Filppi wrote: > It occurs that it might be useful to be able to tag service

Re: Service Composition / Substitution Mapping

It occurs that it might be useful to be able to tag service templates with arbitrary meta-data. Perhaps at one level carried forward from a CSAR manifest, but also user definable. This would allow inter-service references to be definitive, if desired. This could be implicitly defined as a capabi

Re: Service Composition / Substitution Mapping

Thanks for the kudos. :) This topic was discussed on this list a while ago. It's indeed tricky to get right, because TOSCA leaves a lot of room for the orchestrator to implement. I'm thinking of it working something like this: 1. The reqs-and-caps engine by default will always look for satisfiab

Service Composition / Substitution Mapping

Hello all, I'm starting to work on a full implementation of substitution_mapping, which will lead to the ability of service composition. For those unacquainted with substitution mapping, here are some quick resources: *From the spec

Re: Aria Backlog

Fantastic. Thanks! > On Aug 1, 2017:2:59 PM, at 2:59 PM, Avia Efrat wrote: > > In the view you linked to, the issues are listed in a numerical order (only > issues that are not resolved/closed are shown there). > You can see their priority by the small icon to the right of the issue name. > > P

Re: Aria Backlog

In the view you linked to, the issues are listed in a numerical order (only issues that are not resolved/closed are shown there). You can see their priority by the small icon to the right of the issue name. Personally, I don't use this view. I use: https://issues.apache.org/jira/issues/?jql=projec

Aria Backlog

Forgive me for asking a dumb question here, but is the backlog as listed here groomed? That is, are the stories/epics listed in priority order or just numerically? https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=150&projectKey=ARIA&view=planning.nodetail

Re: Query on operation inputs

Quick update on this issue: We merged the relevant pull request: https://github.com/apache/incubator-ariatosca/pull/187 Now inputs behave as expected. On Tue, Jul 11, 2017 at 5:39 AM, D Jayachandran wrote: > Hi Avia, > > Thanks for the detailed explanation. Finally we have better clarity and >

Re: Contribution to aria

Hi Yuval, I went over the backlog to find issues that fit the description you asked for. Here are some suggestions: *Incredibly trivial, and could be finished very quickly:* https://issues.apache.org/jira/browse/ARIA-200 (Even if it seems trivial, it could serve as a starting point on the process

Re: Contribution to aria

I think people here are pretty welcoming with contributions or figuring things out. At least the ones I’ve spoken with have been. 8) As for what to work on, you can look here at the backlog for unassigned issues here: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapi

Contribution to aria

Hi, I was participating on your two days tosca/cloudify course at AT&T in israel. You have talked about aria and i was wondering if and how i can contribute some code. Im not really a python developer (have almost 6 years java experience) and one of my goals is to improve my python skills by contri

Re: Inputs and Node object context for python and shell scripts

Sorry for the broken email, it seems my markup translator has some funky behavior. The code block is: from aria import operation @operation def samplemethod(ctx=None, **inputs): print "ctx -->",ctx print "inputs -->",inputs ctx.node.attributes['test'] = "abc" On Tue, Aug 1, 2017 at 1:48 P

Re: Inputs and Node object context for python and shell scripts

Oh, i see. For each method which represents an operation, you should use the @operation decorator. Thus samplemethod would look like this: from aria import operation @operationdef samplemethod(ctx=None, **inputs): print "ctx -->",ctx print "inputs -->",inputs ctx.node.attributes['test'

RE: Inputs and Node object context for python and shell scripts

Hi Max, I have a service template with just node templates web_app and database with a depends on Relationship. Both use the same custom node type derived from "tosca:Root". I just have the create operation defined where the implementation points to a plugin module. Am trying to set the attribu