Add me as contributor

Could someone please give me write access to the git repo? My Apache username is "emblemparade".

Re: JIRA configuration changes

+1 Regarding sprints -- seems to me that this field can be used by whomever is assigned the JIRA for their own purposes, whether they are in GigaSpaces or not. As Ran pointed out, our own work is public. On Mon, Nov 14, 2016 at 1:53 PM, John D. Ament wrote: > On Mon, Nov

Re: Service Composition / Substitution Mapping

y by the orchestrator, but some kind of special requirement > type(s) would be needed to utilize it. This way, external repos could be > used safely and directly without the separate load step. > > On Tue, Aug 1, 2017 at 12:43 PM, Tal Liron <t...@cloudify.co> wrote: > >

Re: Workflow graph, Juju charm and node states

> > 1) Is it possible to send me an example of a custom workflow graph? > There is a rather simple one here: https://github.com/apache/incubator-ariatosca/tree/master/tests/resources/service-templates/tosca-simple-1.0/node-cellar On the YAML side, you'll see how we use the aria.Workflow policy

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

axim Orlov [mailto:ma...@cloudify.co] > > >> Sent: Monday, July 31, 2017 10:22 PM > > >> To: dev@ariatosca.incubator.apache.org > > >> Subject: Re: Inputs and Node object context for python and shell > > >> scripts > > >> > > &g

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

Re: Node types

> Q1 > I see normative node types in the YAML spec. Here it makes sense to call > them normative node types :) > I see non-normative node types in the YAML spec. Here it makes sense to > call them normative node types :) > I also know the template author can create its own node types. Should I >

Re: TOSCA simple YAML 1.1 support

We're still in the investigation phase. Is there a specific 1.1 feature you would want to prioritize? On Tue, Aug 15, 2017 at 3:03 AM, David Haja wrote: > Hi, > > > Do you have any timelines to support TOSCA simple YAML 1.1? > > > Regards, > > David >

Re: Service Composition / Substitution Mapping

re, but > it's not really a "substitution map", rather more of a "service proxy" (as > implemented as a plugin in Cloudify). Just trying to clarify. Maybe the > community thinks that "substitution map" as something that occurs beyond > parsetime, o

Re: Service Composition / Substitution Mapping

Well, DJ, it's all just opinion at this stage and feedback is welcome! Option 1: > To look at satisfying nodes present in a substituting service, > Have these nodes part of the newly created service and remove the > substituting service(nodes with different ID's. Also we are very much in

Re: Is it possible to inspect a model?

The "-f" flag ("--full") for "aria service-template show" and "aria service show" will do just that. You can also output the same in --json and --yaml. Currently the "-f" flag doesn't work on individual nodes, but there is an open ticket to add that. On Thu, Aug 10, 2017 at 3:38 AM, chbndrhnns

Re: Service Composition / Substitution Mapping

Thanks for the feedback, DJ. What I wrote was just ideas for now, we're still in the investigation phase and haven't implemented anything yet. 1. The reqs-and-caps engine by default will always look for satisfiable > capabilities within the currently instantiated service. HOWEVER, if such a >

Re: Import definition for top-level service template

I do not think you need to import the substituting template: the whole point is that it should be left to the orchestrator to "stitch" things together. However, I do think you at least need the substituted node type to be known, so that the parser can validate the mappings. So it might make sense

Re: Service Composition / Substitution Mapping

d to be triggered > due to operations that they connect to lifecycle methods, and there is no > "materialize_capabilities" interface that I noticed, some other kind of > magic must be performed. Maybe this is an orchestrator-specific detail > outside of TOSCA. > > DeWayn

Re: Service Composition / Substitution Mapping

eems to not really care, which is fine and > perhaps a good idea. But ARIA has to care. > > DeWayne > > On Fri, Aug 11, 2017 at 12:34 PM, Tal Liron <t...@cloudify.co> wrote: > > > In my opinion, the new composite service should indeed be a single > service, > > so t

Podcast about the state of NFV in TOSCA

With Michael Brenner, Luc Boutier, and yours truly. I specifically delve into some of the challenges we face in ARIA. The podcast can be found here: http://cloudify.co/2017/08/03/open-source-podcast-episode-3-an-honest-discussion-on-tosca.html https://www.youtube.com/watch?v=gj6CUt2IF-I

Re: Service Composition / Substitution Mapping

interface for it, then > orchestrators or just plugins could determine how tricky they wanted to > be. IOW, let not the perfect be the enemy of the good. > > DeWayne > > > On Fri, Aug 11, 2017 at 1:26 PM, Tal Liron <t...@cloudify.co> wrote: > > > OK, that's a whole d

Re: workflow list API

Do you mean the CLI command? We actually have talked about this in the past, and the question was just how much the "built-in" (normative lifecycle) workflows should be considered as equivalent to any arbitrary workflow. Can you think of arguments for or against this thinking? On Wed, Jul 12,

Re: Plugin validation

That's a good question. :) Actually, in the service template you do not pin down the plugin, but rather specify the plugin and a minimum version that you need. During instantiation there might be a higher version of the plugin that would be matched. Once instantiated the plugin version is

Re: workflow runner error

I wonder if we should provide a better upgrade path here. Perhaps we need to add a file with some meta information about the version of the database. We don't necessarily have to provide an automatic upgrade to a new database format, but least we can tell the user that the database is out of date

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

It's unassigned, so I don't see why not! On Thu, Jul 20, 2017 at 7:41 AM, D Jayachandran wrote: > Hi, > > Do you have any plans on working on this JIRA issue ? > https://issues.apache.org/jira/browse/ARIA-118 > Can we contribute on this ? > > > Regards, > DJ >

Re: Openstack plugin

ARIA has an adapter that can use Cloudify plugins, and it has been tested successfully with both OpenStack and AWS so far. Unfortunately there are no instructions on how to use it. I know just the right person to write it and will ask him to do so. :) On Fri, Jul 21, 2017 at 3:29 AM, D

Re: Unique identification of an instance element across services

We used to use UUIDs but at some point this was refactored. I tend to agree with you. Actually, I would prefer it to be configurable. We have code in place for ID generation of various types: UUIDs, short UUIDs, and sequentials. All of them would seem useful to me for various scenarios. On Tue,

Re: TOSCA spec compliance on finding target node

It indeed should *not* be required. I just verified that it you are correct, and a match is not made if only the capability is specified without a node type/template. This is a regression, because it used to work correctly. There is currently work in progress to refactor that mechanism, so I

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

d Node object context for python and shell scripts > > > > I'm not entirely sure to which inputs you are referring to, but any ctx > > attribute or method accessible from a python script is accessible form > any > > shell script. For example: > > > >- "ctx.node.attr

Re: Unique identification of an instance element across services

f indeed a uuid is > easier to recognize, or even use in a query), let's discuss it further... > > On Tue, Jul 25, 2017 at 7:35 PM, Tal Liron <t...@cloudify.co> wrote: > > > We used to use UUIDs but at some point this was refactored. I tend to > agree > > with you. > &

Re: Unique identification of an instance element across services

locking scheme. > > - DeWayne > > On Jul 25, 2017 12:11 PM, "Tal Liron" <t...@cloudify.co> wrote: > > > It's not an issue of thread safety -- it could be entirely different > > processes, on different machines, accessing the same db. It can be solved > >

Re: Unique identification of an instance element across services

r than the uuid based ID in my opionion. > > On Jul 25, 2017 9:49 PM, "Tal Liron" <t...@cloudify.co> wrote: > > Our code for determining the next index is not concurrently safe (no atomic > transaction) so I can see it breaking in concurrent use cases (running two &g

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

I'm pretty sure you can access the inputs via the ctx call. Can anyone confirm how to do this? We really need to document ctx usage... On Mon, Jul 24, 2017 at 5:57 AM, D Jayachandran wrote: > Hi, > > With current ARIA implementation, the python and shell scripts

Re: Unique identification of an instance element across services

, DeWayne Filppi <dewa...@cloudify.co> wrote: > Such is their strength. I'm just advocating using them as a last resort > because they are user unfriendly and gigantic. > > On Tue, Jul 25, 2017 at 12:55 PM, Tal Liron <t...@cloudify.co> wrote: > > > Let's cons

Re: [VOTE] publish ariatosca 0.1.0

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 folde

Re: inputs

wrote: > Are template inputs always scalar? The spec seems vague, but all examples > I see are scalar. > > --DeWayne > -- Tal Liron, Senior Solutions Architect <http://cloudify.co> -- M: +1-312-375-8299 http://cloudify.co @cloudifysource <https://twit

Re: imperative workflows (1.1)

ine: we do not support TOSCA 1.1 right now, but have a very powerful workaround. On Mon, Jul 3, 2017 at 3:01 PM, DeWayne Filppi <dewa...@gigaspaces.com> wrote: > Is there any current support for imperative workflows (ala 1.1)? If not, > is it a priority roadmap item? > > --DeWayn

Re: Query on operation inputs

the git repo of my example. > > https://github.com/djay8887/Aria-operationInputs > > regards, > DJ > > -Original Message- > From: Tal Liron [mailto:t...@gigaspaces.com] > Sent: Thursday, June 01, 2017 9:59 PM > To: dev@ariatosca.incubator.apache.org > Subjec

Re: Query on operation inputs

DJ, I'm sorry, I'm still not sure what to look at here. The example seems to run fine. By the way, you can import ARIA's types (such as aria.Plugin) like so: imports: - aria-1.0 On Mon, Jul 3, 2017 at 2:17 PM, Tal Liron <t...@gigaspaces.com> wrote: > Oops, it seems your email fr

Re: Service Composition / Substitution Mapping

se in the future when the > number of them grows.. > > > On Wed, Aug 2, 2017 at 7:14 PM, Tal Liron <t...@cloudify.co> wrote: > > > Our goal with adding new "conventions" to ARIA, such as policies, is to > > always make them optional. The idea is that a

Re: Service Composition / Substitution Mapping

ost completely wide open from > the orchestrator side, IOW few predefined keys. Too few IMHO, but if > everyone uses ARIA conventions it could work. > > On Tue, Aug 1, 2017 at 11:49 PM, Tal Liron <t...@cloudify.co> wrote: > > > I agree! Luckily metadata exists in the 1.0 spec. :) >

Re: Version support for different TOSCA types

tom node types with different > version in my service template ? > In that case how can the node template choose a particular version > of the custom node type ? > Or Is the version only for the template author to track changes > about custom types over time ? > >

Re: Version support for different TOSCA types

t; In general, what is the process to request an enhancement to ARIA? > > > Cheers > Steve B > > > > > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Tuesday, August 08, 2017 9:07 AM > To: dev@ariatosca.incubator.apache.org &g

Re: Version support for different TOSCA types

xdb.v2), but I think using > a different version field better describes the differences between the > version 1 database and version 2 database. > > > > On Wed, Aug 9, 2017 at 4:21 PM, Thomas Nadeau <tnad...@lucidvision.com> > wrote: > > > > > >

Re: Version support for different TOSCA types

the version field in the 1.0 spec, I agree. > > On Tue, Aug 8, 2017 at 8:40 PM, Tal Liron <t...@cloudify.co> wrote: > > > The process is simply to open a JIRA ticket. However, it may be better to > > first discuss it on this mailing list. > > > > For this enhanc

Re: Version support for different TOSCA types

I think you are referring to TOSCA 1.1, which is on the roadmap but not supported yet. You can of course create your own "version" property or attribute for node types in TOSCA 1.0. On Fri, Aug 4, 2017 at 7:05 AM, D Jayachandran wrote: > Hi, > > The TOSCA spec

Re: Version support for different TOSCA types

t; > http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile- > YAML/v1.0/os/TOSCA-Simple-Profile-YAML-v1.0-os.pdf > > Regards, > DJ > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Friday, August 04, 2017 9:39 PM > To: dev@ariatosca.incubator.apa

Re: cloudify plugin relationship mapping

Yes. The HostedOn relationship is used in requirements for a Container capability, e.g.: node_types: tosca.nodes.SoftwareComponent: ... requirements: - host: capability: tosca.capabilities.Container node: tosca.nodes.Compute relationship:

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

Let's talk about scaling some more. :) Earlier, I complete missed the definition of tosca.capabilities.Scalable: http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.0/cos01/TOSCA-Simple-Profile-YAML-v1.0-cos01.html#DEFN_TYPE_CAPABILITIES_SCALABLE The reason I missed it is that it's

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

now I'm leaving them as is, but I think it would be even cleaner if they followed the new naming convention in modeling. I continue being unhappy about how the Task API treats both arguments and inputs as the same thing and squashing them all together... :( However, for now I would be happ

Moving to 100% GitHub

you think? Pros and cons? -- Tal Liron Solution Architect t...@gigaspaces.com | +13123758299 Cloudify | http://getcloudify.org <http://getcloudify.org?utm_source=signaturesatori_medium=email_campaign=general_signature> <https://twitter.com/CloudifySource> <https://www.linkedin.com

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

mentation" is called "user_implementation" (vs "actual > implementation") , or rather "template_implementation" - which again hints > it should sit over at the template models..? > > > > > > On Mon, May 22, 2017 at 7:07 PM, Tal Liron <t.

Re: Query on operation inputs

ept "labels" I have metioned all my optional outputs. I expect my > service to be started without any issue but it fails with the error "label" > is not specified. This is why I find ARIA is having a problem. > > > # python /root/incubator-ariatosca/aria/cli/main.py executions

Re: Query related to substitution mapping

titution mapping. > The db.yaml is the substituting template which is imported to web.yaml. > The web.yaml has an abstract node template "database" which would be > substituted with db.yaml. > > We want to understand is it mandatory to have templates imported for > substitu

Re: GIT/JIRA Integration

> > > >>> > > > >> > > > > > >>> > Ran > > >> > > > > > >>> > > > >> > > > > > >>> > On Wed, Jan 4, 2017 at 2:02 PM, John D. Ament < > > >> > > > > johndam...@apache.org > > >> > > > > > > > > >> > > > > > >>> > wrote: > > >> > > > > > >>> > > > >> > > > > > >>>

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

m both not convinced the original values are needed at that stage (can we > have an actual use case?), but even if they are, do we really need to keep > all four on the same model? > How about having the original values on the OperationTemplate, and the > "coerced values" (for lack of

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

> > > The scaling policies are definitely needed e.g. for group, but it'd have > been nice to have some simplified manner for defining multiple instances of > a given node without having to go through actual scaling policies > definitions (e.g. a special property on the node to define this etc). >

Re: Support for TOSCA Simple Profile NFV 1.0

r NFV > profiles and do you have any timelines to support draft 04 ? > > > Regards, > DJ > -- Tal Liron Senior Engineer t...@gigaspaces.com | +1 (773) 828-9339 Cloudify | http://getcloudify.org <http://getcloudify.org?utm_source=signaturesatori_medium=email_campaign=general

Re: Query related to substitution mapping

Your expectations are reasonable: that ARIA would look at all of its current service instances and try to match reqs-and-caps with substitutions. However, we are a bit far from implementing this. Currently, ARIA only knows how to match reqs-and-caps within the service. Also, this feature has to

Re: Query on operation inputs

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

Let's talk about scaling (ARIA-254)

The TOSCA spec says nothing about how multiple nodes per template would be created, leaving it the orchestrator to decide. The provided scaling policy in the Simple Profile is empty, just providing a base type for users to extend. What I'm proposing is to support basic policy-based scaling to

Re: aria install from source error

clude=['aria*']) + > > > > > > TypeError: find_packages() got an unexpected keyword argument 'include' > > > > > > Is this familiar? > > > > > > Also note that I installed pip via bootstrap.pypa and running "pip > > install > > &g

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

> is still not properly defined in TOSCA, perhaps this means that the > policy's values should override the capability's if both exist? I'd rather > it didn't, as it could make things confusing, and because it's still an > ARIA-specific definition. Just thought I'd bring it up though. > &

Re: Query on operation inputs

ards, > > DJ > > > > -Original Message- > > From: Ran Ziv [mailto:r...@gigaspaces.com] > > Sent: Thursday, May 25, 2017 4:07 PM > > To: dev@ariatosca.incubator.apache.org > > Subject: Re: Query on operation inputs > > > > Hi, &g

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

lot of different possible inputs to an > operation: (1) interface inputs, (2) operation inputs (3) task inputs. I > feel that the "implementation" should have a special place under the > operation inputs, but not a field on its own... > > On Thu, May 25, 2017 at 1:22 AM,

Re: Query related to substitution mapping

ou have any feedback on this and if our understanding is correct ? > > > Regards, > DJ > > > > -- Tal Liron Senior Engineer t...@gigaspaces.com | +1 (773) 828-9339 Cloudify | http://getcloudify.org <http://getcloudify.org?utm_source=signaturesatori_medium=email_campaign=genera

Re: Moving to 100% GitHub

tosca.org to > http://ariatosca.incubator.apache.org > > > > On Sun, May 21, 2017 at 4:15 PM, Tal Liron <t...@gigaspaces.com> wrote: > > > We have both a website and a contribution guide. How should we improve > > them? > > > > http://ariatosca.org/

Re: Moving to 100% GitHub

p github usage, but want to make sure that > > projects are communicating well, so that the source code being maintained > > on github is more of a convenience. Until I see more action from > AriaTosca > > on this list I would be hesitant to say yes for the project. > > >

Re: Unique identification of an instance element across services

; default, it will work with the name based identification > > Also I need clarification on the UUID generation. Currently ARIA supports > four variants. Do we have any standard on how this UUID should be and also > on what aspect these four variants are concluded on? > > >

Re: Unique identification of an instance element across services

I get the feeling that you are more gifted typist than most. Or are you > saying nobody will ever be required to type in one those IDs? > > On Fri, Sep 15, 2017 at 9:27 AM, Tal Liron <t...@cloudify.co> wrote: > > > Before we allow users to configure this, we have another JIR

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

Feel free to take over the JIRA issue. :) On Mon, Sep 18, 2017 at 10:50 PM, D Jayachandran < d.jayachand...@ericsson.com> wrote: > Hi Tal, > > This seems to be a better option and we can contribute for it. > > > Regards, > DJ > > -----Original Message

Re: get_artifact function usage

Sorry, I forgot to answer this. The answer is not good: sadly, there is no solid support for artifacts in ARIA right now beyond parsing. This function is currently a no-op. Rather than just implement this function, I think it should be tackled as part of comprehensive support for artifacts:

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

.yaml", I would like to suggest the following > "plugins: openstack-" > Please let me know if this fine with you. > > > Regards, > DJ > > -Original Message- > From: Tal Liron [mailto:t...@gigaspaces.com] > Sent: Thursday, July 20, 2017 6:24

Re: get_artifact function usage

> Hi Tal, > > Thanks for the clarification. When we say download, does the artifact can > be at remote location or part of the CSAR ? > > > Regards, > DJ > > -----Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Tue

Re: Contribution for https://issues.apache.org/jira/browse/ARIA-118

repository conventions ? > > Regards, > DJ > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Wednesday, September 20, 2017 9:38 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Contribution for https://issues.apache.org/ > jira/browse

Re: get_attribute not evaluating

the result of a translation effort > from a Cloudify DSL blueprint (which apparently tolerates it). If I move > the macro definition up into "dsl_definitions", all appears to be well. > > -- DeWayne > > On Thu, Oct 5, 2017 at 5:01 PM, Tal Liron <t...@cloudify.co> wrot

Re: get_attribute not evaluating

ot;val": {"get_attribute": > ["node1", "att1"]}}. > > This seems odd. On the other hand, if you replace the "macro: *macro" line > with just '*macro', then the "val" environment variable contains "a val" as > you

Re: get_attribute not evaluating

ot;val": {"get_attribute": ["node1", "att1"]}} to the > operation. So basically, "get_attribute" is only evaluated if it's not > nested. > > -- DeWayne > > > On Fri, Oct 6, 2017 at 10:02 AM, Tal Liron <t...@cloudify.co> w

Slack

Hi, devs! As you have probably surmised from reading the digests sent to this list, there is a Slack channel where ARIA devs can chat. I thought it was for committers only, but in fact any contributor can join and talk to others in a more real-time fashion. It's critical to understand that Slack

Re: TOSCA state

ARIA does support node "state" and changes it dynamically as part of the normative workflow cycle (install, uininstall, start, stop). It does not otherwise respond to the actually condition at the IaaS -- that would require some kind of monitoring service, which is beyond the scope of ARIA. A

Re: Unique identification of an instance element across services

n the choice of the resource identifier > algorithm. > If CLI user wants a "human-readable" ID, then selects one that is > appropriate for it. > If API user wants a true UUID, the selects a version 1 UUID for instance. > I suspect the choice of the resource identifier algorith

Re: list of maps

It's an interesting problem, and the solution is clumsy due to the odd way TOSCA defines entry schema. I see no choice but to add an extra nesting property. Something like this: data_types: Element: properties: data: type: map entry_schema: string node_types:

Re: Working towards Release 1

ote: > > > >> > >> Agreed. We can update the Jira on the weekly grooming. > >> > >>—Tom > >> > >> > >>> On Oct 5, 2017, at 11:24 AM, Tal Liron <t...@cloudify.co> wrote: > >>> > >>>

Re: list of maps

t; Really? Two layers of properties? > > On Tue, Oct 10, 2017 at 11:10 AM, Tal Liron <t...@cloudify.co> wrote: > > > You did not mention any error in this thread. > > > > The only other option I can think of is to define all the keys explicitly > > as not re

Re: Fortigate VNF template

Great! Is there anything stopping you from contributing this to the ARIA project when done? On Tue, Oct 10, 2017 at 10:37 AM, DeWayne Filppi wrote: > For those interested, I'm in the process of implementing a TOSCA template > for the initial deployment and configuration of

Re: list of maps

r I recently mentioned. > > I'm looking for: > > prop: > - a: b > - c: d > > *not* > > prop: > - {data: {a:b}} > - {data { c:d)) > > The Cloudify plugin I'm trying to reuse requires the first form. > > DeWayne > > On Mon, Oct 9, 2017 at 9:00

Re: stuck executions

That's a good point. I would say there is a bug in "service delete -f". Could you open a bug in JIRA? On Tue, Oct 10, 2017 at 11:35 AM, DeWayne Filppi wrote: > I started an execution and then canceled it. Now when I try to delete the > service (with -f) it fails to delete

Re: strange yaml-1.1 error

All I can say is that this has nothing to do with YAML, but with Python paths (code loading) in the workflow execution sub-process. On Tue, Oct 10, 2017 at 10:29 AM, DeWayne Filppi wrote: > In the absence of any context (because reproducing this is very involved), > does

Re: Fortigate VNF template

les > > > > Arthur > > > > On Tue, Oct 10, 2017 at 6:52 PM DeWayne Filppi <dewa...@cloudify.co> > wrote: > > > >> Nope. > >> > >> On Oct 10, 2017 10:50 AM, "Tal Liron" <t...@cloudify.co> wrote: > >> > >

Re: Renaming the install and uninstall normative workflows

7 at 8:45 PM Thomas Nadeau <tnad...@lucidvision.com> > wrote: > >> +1 >> >> >> > On Oct 3, 2017, at 1:17 PM, Tal Liron <t...@cloudify.co> wrote: >> > >> > +1 >> > >> > I don't see any reason why not to. Anybody have another op

Re: stuck executions

You can delete everything in the "execution" and related tables. On Tue, Oct 10, 2017 at 11:39 AM, DeWayne Filppi <dewa...@cloudify.co> wrote: > Sure. Can I update a table in the database or something to fix it? > > On Tue, Oct 10, 2017 at 11:38 AM, Tal Liron

Re: Fortigate VNF template

Any help in debugging would be appreciated! On Tue, Oct 10, 2017 at 2:02 PM, DeWayne Filppi wrote: > For reasons that somewhat mystify me, the template is installing with no > errors now. I fixed it by removing the inputs definition I had in the > terminal.yaml file, which

Re: Fortigate VNF template

efinition of the > inputs? > > On Tue, Oct 10, 2017 at 2:17 PM, Tal Liron <t...@cloudify.co> wrote: > > > Any help in debugging would be appreciated! > > > > On Tue, Oct 10, 2017 at 2:02 PM, DeWayne Filppi <dewa...@cloudify.co> > > wrote: > > > &g

Re: Fortigate VNF template

10, 2017, at 4:09 PM, DeWayne Filppi <dewa...@cloudify.co> wrote: > > > > Ok. The interesting thing is that not only does it allow you to have > > ad-hoc inputs, it also blows a gasket when you try to define them. > > > > On Tue, Oct 10, 2017 at 3:02 PM, Tal Liron &l

Re: Working towards Release 1

I think we can discuss the epic in general here, and leave implementation details on JIRA. On Thu, Oct 5, 2017 at 9:52 AM, Vishwanath Jayaraman < vishwana...@hotmail.com> wrote: > Tal/Tom, > > Very glad to see an epic and its associated stories/tasks for Release 1.0. > > I am assuming you are

Re: get_attribute not evaluating

DeWayne, as usual it's very hard for me to follow up on your questions. Please provide more information. At the very least, what is the full error you see? (I don't understand what "not evaluating" means.) Also, we need to reproduce this in order the help. Either provide us with a complete

Re: High level design documentation or class/sequence diagrams?

com> wrote: > > > Sounds good > > > > Sent from my iPhone > > > > On Oct 12, 2017, at 1:14 PM, Tal Liron <t...@cloudify.co > t...@cloudify.co>> wrote: > > > > There is none. However, I am planning to do a live video session where we >

Re: Free PyCharm license for ARIA work?

e http://python.org/dev/peps/pep-0263/ for > details > > Are you aware of this ? > > > Regards, > DJ > > -Original Message- > From: Tal Liron [mailto:t...@cloudify.co] > Sent: Thursday, October 12, 2017 12:05 AM > To: dev@ariatosca.incubator.apache.org > Subject:

Re: Service-template name

What is a "plugin service template"? On Fri, Oct 13, 2017 at 2:40 PM, Steve Baillargeon < steve.baillarg...@ericsson.com> wrote: > Hi > When we say service-templates must have unique names, can someone clarify > it is applicable for all service-templates including plugin > service-templates? > >

Re: High level design documentation or class/sequence diagrams?

There is none. However, I am planning to do a live video session where we do an overview of the codebase. On Thu, Oct 12, 2017 at 12:59 PM, Vishwanath Jayaraman < vishwana...@hotmail.com> wrote: > Was wondering if there are any high level design documentation or > class/sequence diagrams that

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

Are you reporting a bug here? It would really help to get a complete example with instructions to reproduce. On Tue, Sep 5, 2017 at 7:07 PM, DeWayne Filppi wrote: > After adding the highlighted content to the ARIA openstack plugin.yaml, > >

Re: operation dependencies

Yes: https://cwiki.apache.org/confluence/display/ARIATOSCA/Execution+Configuration On Fri, Sep 8, 2017 at 4:45 PM, DeWayne Filppi wrote: > I see in the examples a list of dependencies for scripts in operations, for > example: > > implementation: >

Re: Selecting and installing a specific stack

The only thing you can configure in pure TOSCA is the inputs, so it's not so easy a problem to solve. If we have node templates for all the nodes, we could configure their requirements for each using intrinsic functions that rely on the inputs, so that the final topology could change. Let me try

Re: subnet connected to router

OK! DeWayne provided me with the complete service template offline and I managed to reproduce the problem and also create a more minimal way to reproduce it. To follow it, see this JIRA: https://issues.apache.org/jira/browse/ARIA-356

  1   2   3   4   >