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
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
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
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
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:
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=ARIA=planning.nodetail
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.
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:
Hi,
I was participating on your two days tosca/cloudify course at AT 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
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
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
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
12 matches
Mail list logo