Attached. Note that I include a modified version of the plugin.yaml for
openstack that Aria uses by default (in the imports dir). The change of
interest is in the aria.openstack.datatypes.Server data type.
On Wed, Sep 6, 2017 at 4:03 PM, Tal Liron wrote:
> You are allowed
You are allowed to add extra inputs at the node type, beyond what is
defined in the interface type. You just can't do it at the node template.
The error you get is odd. If you could share your complete work, perhaps we
can run it and assist you. For me, at least, it's impossible to asses the
I was afraid you were going to say that. I added a generic map as the
"server" property. This passes the parse on template load. When I
actually then try to use userdata, the install workflow dies in the aria
extension registration process, claiming : RuntimeError: Re-definition of
yaml-1.1 in
In TOSCA, properties must have a well-defined schema, and as such it means
that the "server" property's datatype must be defined to have the
"userdata" field for users to be able to use it through there.
This is also true for operation inputs at this time, although AFAIK the
spec does in fact
Rather than opening a potentially misguided PR, let 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 wrote:
>
First of all, "role" is an extension and is only used internally. It is
indeed not defined by TOSCA and you shouldn't be using it yourself.
The reason "role" exists is to avoid hardcoding functionality to type
names. Certain normative types play special roles in TOSCA: certain
relationships are
"directives" is just a list of strings. Moreover, it seems like a
placeholder for something in the future. Also note that "directives" exist
only for node templates, not node type, so this means that in order to use
substitution we would have to have a node template marked as being
abstract. If we
(I'll let Tal take this one :P)
On Wed, Sep 6, 2017 at 2:26 PM, D Jayachandran
wrote:
> Yes, I can see that Ran. So that was my question , why was role being
> added to the types ?
> TOSCA spec does not say about a parameter called role. I feel this is not
> aligned
Yes, I can see that Ran. So that was my question , why was role being added to
the types ?
TOSCA spec does not say about a parameter called role. I feel this is not
aligned with TOSCA spec.
Regards,
DJ
-Original Message-
From: Ran Ziv [mailto:r...@cloudify.co]
Sent: Wednesday,
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
On Tue, Sep 5, 2017 at 6:09 PM, Tal Liron wrote:
>
> Just like you can specify a specific node template for a requirement, I
> believe it can be useful and often necessary to specify a substituted
> service template.
>
Even if it is needed, the question is how to do that.
Well then, feel free to create an issue, and either submit the smaller fix,
or create a PR which goes beyond this as you say :)
On Tue, Sep 5, 2017 at 6:52 PM, DeWayne Filppi wrote:
> Yes, I believe you've got the idea. The original "server" arg is defined
> as a
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
Thanks Tal. I agree this needs to taken up with OASIS.
Having said that ,there is statement in TOSCA Spec 2.9
" In TOSCA templates, nodes are either:
· Concrete: meaning that they have a deployment and/or one or more
implementation artifacts that are declared on the “create” operation
Hi,
I just noticed the "role" attribute is added for different "capability" and
"node" types in ARIA profiles. There is no such role with the TOSCA spec.
Why is this been added in the profiles ? What is the use of them ?
I faced an issue when I run a local script as part of the Interface
15 matches
Mail list logo