led explanation. Finally we have better clarity and
> are in the same page.
>
> Regards,
> DJ
>
> -Original Message-
> From: Avia Efrat [mailto:a...@gigaspaces.com]
> Sent: Tuesday, July 11, 2017 3:42 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Query o
gt; d.jayachand...@ericsson.com>
> > > wrote:
> > >
> > > > Hi Tal,
> > > >
> > > > Have you got a chance to look into this below issue ?
> > > >
> > > > Regards,
> > > > DJ
> > > > -Original Message-
; > operation input that has required: false in its corresponding node type
> > operation input.
> >
> >
> >
> >
> > On Mon, Jul 3, 2017 at 10:17 PM, Tal Liron <t...@gigaspaces.com> wrote:
> >
> > > Oops, it seems your email from before was
missed it. I will get to it after the US holiday!
> >
> > On Mon, Jul 3, 2017 at 4:21 AM, D Jayachandran <
> > d.jayachand...@ericsson.com>
> > wrote:
> >
> > > Hi Tal,
> > >
> > > Have you got a chance to look into this below issue ?
> > &g
elow issue ?
> >
> > Regards,
> > DJ
> > -Original Message-
> > From: D Jayachandran [mailto:d.jayachand...@ericsson.com]
> > Sent: Monday, June 05, 2017 3:44 PM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: RE: Query on
ow issue ?
>>
>> Regards,
>> DJ
>> -Original Message-
>> From: D Jayachandran [mailto:d.jayachand...@ericsson.com]
>> Sent: Monday, June 05, 2017 3:44 PM
>> To: dev@ariatosca.incubator.apache.org
>> Subject: RE: Query on operation inputs
>>
e ?
>
> Regards,
> DJ
> -Original Message-
> From: D Jayachandran [mailto:d.jayachand...@ericsson.com]
> Sent: Monday, June 05, 2017 3:44 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: RE: Query on operation inputs
>
> Hi Tal,
>
> Please find below
> exists
> >
> > [root@DJ-DEV tal-test]# python /root/tal-test/incubator-
> ariatosca/aria/cli/main.py
> > executions start install -s s2
> > Declared parameters "labels" have not been provided values
> >
> > Regards,
> > DJ
> >
>
root@DJ-DEV tal-test]# python /root/tal-test/incubator-
> ariatosca/aria/cli/main.py
> > executions start install -s s2
> > Declared parameters "labels" have not been provided values
> >
> > Regards,
> > DJ
> >
> > -Original Message-
> &
"labels" have not been provided values
Regards,
DJ
-Original Message-
From: Ran Ziv [mailto:r...@gigaspaces.com]
Sent: Thursday, June 01, 2017 5:24 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Query on operation inputs
Again, there's a difference between the
A-149-functions-in-operation-configuration
> and it seems to have the fix for operation/interface inputs.
>
> Regards,
> DJ
> -Original Message-
> From: D Jayachandran
> Sent: Thursday, June 01, 2017 4:40 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: RE: Query on opera
To: dev@ariatosca.incubator.apache.org
Subject: RE: Query on operation inputs
Hi Ran,
The validation of operation inputs is also done during instantiation. Please
find below.
[root@DJ-DEV tal-test]# python
/root/tal-test/incubator-ariatosca/aria/cli/main.py service-templates store
/root
must either have a default value in the type
> definition or be supplied with a value in the actual operation
> definition)
>
>
> Regards,
> DJ
>
> -Original Message-
> From: Ran Ziv [mailto:r...@gigaspaces.com]
> Sent: Sunday, May 28, 2017 6:14 PM
> To: dev@ariatos
d with a value in the actual operation definition)
>
>
> Regards,
> DJ
>
> -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
>
>
, 2017 6:14 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Query on operation inputs
I've reviewed your example, and I think either I'm missing something or my
original explanation still applies:
1. The validation at orchestration time for whether required inputs have been
specified
Thanks Tal.
I will try to use your branch and let you know the results.
Regards,
DJ
-Original Message-
From: Tal Liron [mailto:t...@gigaspaces.com]
Sent: Friday, May 26, 2017 9:57 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Query on operation inputs
OK, I see now
t; and "isService" have the required definition as "false". Hence
> I
> > may or may not specify them in my NODE-TEMPLATE input section.
> > Except "labels" I have metioned all my optional outputs. I expect my
> > service to be started without any issue but
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
sca/aria/cli/main.py executions start -s
demo-sr-1 install
Required inputs [u'labels'] have not been specified - expected inputs:
[u'isService', u'name', u'exposed_port', u'image', u'labels', u'target_port',
u'target_host']
Regards,
DJ
-Original Message-----
From: Tal Liron [mailto:t...@gigasp
ration. Could you please help me with that reference in TOSCA spec ?
>
>
> Regards,
> DJ
>
> -Original Message-
> From: Ran Ziv [mailto:r...@gigaspaces.com]
> Sent: Thursday, May 25, 2017 5:16 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Query on oper
2017 5:16 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Query on operation inputs
Yes, I understand the confusion here. The issue is that, despite its name, the
"required" field isn't what defines whether an input is optional or not
- it is only relevant during the parsing phase (This is a
rty: [ web_app, image] }
> exposed_port: { get_property: [ web_app, port]
> }
> target_host: { get_property: [ database, name]
> }
> target_port: { get_property: [ database, port]
> }
>
dev@ariatosca.incubator.apache.org
Subject: Re: Query on operation inputs
Hi,
Weird, I remember responding to this mail before, but it doesn't seem like I
have.
In any case, it is indeed our intention that no inputs may be passed into
operations unless they have been clearly declared in the service-template.
ARIA o
Hi,
Weird, I remember responding to this mail before, but it doesn't seem like
I have.
In any case, it is indeed our intention that no inputs may be passed into
operations unless they have been clearly declared in the service-template.
ARIA opts to be a strict implementation of TOSCA wherever
Hi,
The latest Apache-aria is throwing a validation error during the execution of a
service.
It demands all the operation inputs defined in a node type be declared in the
service template though they are optional inputs.
Could you please let us know if this change was intentional ?
Regards,
Hi,
The latest Apache-aria is throwing a validation error during the execution of a
service.
It demands all the operation inputs defined in a node type be declared in the
service template though they are optional inputs.
Could you please let us know if this change was intentional ?
Regards,
26 matches
Mail list logo
