Mailing-List: contact dev-help@ariatosca.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ariatosca.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <VI1PR07MB10223AB18726DE7549956051EDFF0@VI1PR07MB1022.eurprd07.prod.outlook.com>
References: <VI1PR07MB1022CE030313B72092246C7AEDED0@VI1PR07MB1022.eurprd07.prod.outlook.com>
 <VI1PR07MB1022EAC82B9277AD82FB497FEDFF0@VI1PR07MB1022.eurprd07.prod.outlook.com>
 <CAAduSmPH6v3WSZ+FYkJWsfPD0XRuneUR8_p3WnS+P-Kx9JektQ@mail.gmail.com>
 <VI1PR07MB1022D015D673346A0D9D22D8EDFF0@VI1PR07MB1022.eurprd07.prod.outlook.com>
 <CAAduSmOTGZk9vgz5kXAAwU8xjH-oVbg+A2dPD3Jh2y5TpoHPaQ@mail.gmail.com> <VI1PR07MB10223AB18726DE7549956051EDFF0@VI1PR07MB1022.eurprd07.prod.outlook.com>
From: Tal Liron <tal@gigaspaces.com>
Date: Thu, 25 May 2017 12:48:41 -0500
Message-ID: <CAMeryBcJJU+Zqnk+UJpr+OP000Z+kEsaEsouoHiv3P3BwGHb0w@mail.gmail.com>
Subject: Re: Query on operation inputs
To: dev@ariatosca.incubator.apache.org
Content-Type: multipart/alternative; boundary="001a113ece4a056e5a05505cd60b"
archived-at: Thu, 25 May 2017 17:49:14 -0000

--001a113ece4a056e5a05505cd60b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi DJ, let's try to look at these issues one at a time.

I got your YAML to parse OK, but had to change it around a bit... it would
help if you used a complete example here, and also if it would be much
shorter to demonstrate the specific issue you are asking about. There's a
lot going on in this example and you are asking a few different questions.

The error message you are getting is not about operation inputs, but about
topology template inputs. I can't help much here unless I see those input
definitions: they do not appear in your YAML fragment. In general, see
section 3.8.2.1 in the TOSCA spec. Values for topology template inputs must
come from an external source, and indeed in this case you are providing
them via the CLI. ARIA makes sure that all required topology template
inputs have a value, and that it is a valid value for the type. So, that's
the error you are seeing.

The inputs we *do* see in your YAML fragment are input definitions at the
node type and input assignments at the node template. These work
differently from topology template inputs, because their values do not come
from an external source directly (though this can be indirect via get_input
and other intrinsic functions).

According to the spec you quote (3.5.8.2) , the key "required" is optional
in YAML, meaning that you do not have to specify it. Its default value is
"true". So, unless you specify "required: false", that property is
required. So actually all your "required" true" lines are redundant
(informative, but don't change functionality).

So, let's look at your "isService" input. At the node type, it is defined
as required: false. And indeed, if at the node template I don't assign a
value to it, ARIA has no problem. However, if you do not assign a value to
a required input, say "image", then ARIA would be unhappy.

I hope this is clear, though I have a feeling you are asking about
something else which I'm not quite understanding. Again, a shorter and
complete example would help demonstrate what you mean.


On Thu, May 25, 2017 at 9:56 AM, D Jayachandran <d.jayachandran@ericsson.co=
m
> wrote:

> Hi Ran,
>
> When I refer the TOSCA spec, it says
>
> " An optional key that declares a property as required (true) or not
> (false)."
> property_required: represents an optional boolean value (true or false)
> indicating whether or not the property is required.  If this keyname is n=
ot
> present on a property definition, then the property SHALL be considered
> required (i.e., true) by default.
>
> It is not clear to whom this property is required or not ?
>
> With your argument, it seems we always need to provide a default value to
> an input, when we don=E2=80=99t declare in my service template. Is my und=
erstanding
> correct here ?
> But the TOSCA spec says the default value is always an optional one. Also
> since the parser validates the service template inputs according to the
> "required" field am not sure why we need another validation during the
> execution ?
>
> I also don=E2=80=99t find any reference in TOSCA spec which says, all inp=
uts
> defined in node type be declared in node template to be used by any
> operation. Could you please help me with that reference in TOSCA spec ?
>
>
> Regards,
> DJ
>
> -----Original Message-----
> From: Ran Ziv [mailto:ran@gigaspaces.com]
> Sent: Thursday, May 25, 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 n=
ot
> - it is only relevant during the parsing phase (This is according to our
> understanding of the TOSCA spec. Tal could probably expand more on this).
> What's relevant for deciding whether an input is required or not for
> actual execution is whether it has a default value - so all inputs would
> have a value when the actual execution takes place.
>
> I hope this helps clearing this confusing issue..
>
> Ran
>
> On Thu, May 25, 2017 at 2:08 PM, D Jayachandran <
> d.jayachandran@ericsson.com
> > wrote:
>
> > Hi Ran,
> >
> > Thanks for your response.
> >
> > In my case, I have defined the inputs as optional under the create
> > operation of my custom node type.
> > Since it is an optional input, I haven't declared it in my node-templat=
e.
> > I assume optional input may or may not be declared in a service templat=
e
> ?
> > Am I missing something here ?
> >
> > Please find below the node type and node template in my case.
> >
> > # python /root/incubator-ariatosca/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']
> >
> > Node-type
> >
> > node_types:
> >     test.nodes.Container.Application:
> >         derived_from: tosca.nodes.Root
> >         properties:
> >             name:
> >               type: string
> >               required: true
> >             image:
> >               type: string
> >               required: true
> >             port:
> >               type: integer
> >               required: false
> >         interfaces:
> >             Standard:
> >                 type: tosca.interfaces.node.lifecycle.Standard
> >                 create:
> >                         inputs:
> >                             name:
> >                                 type: string
> >                                 required: true
> >                             image:
> >                                 type: string
> >                                 required: true
> >                             exposed_port:
> >                                 type: integer
> >                                 required: false
> >                             target_port:
> >                                 type: integer
> >                                 required: false
> >                             target_host:
> >                                 type: integer
> >                                 required: false
> >                             labels:
> >                                 type: string
> >                                 required: false
> >                             isService:
> >                                 type: boolean
> >                                 required: false
> >                         implementation:
> >                             primary: sample > sample.samplemethod
> >
> > Node template:
> >
> >         web_app:
> >             type: test.nodes.Container.Application
> >             properties:
> >                 name: { get_input: web_app_name }
> >                 image: { get_input: web_app_image }
> >                 port: { get_input: web_app_port }
> >             requirements:
> >                 - dependency:
> >                       node: database
> >                       relationship:
> >                           type: tosca.relationships.DependsOn
> >             interfaces:
> >                 Standard:
> >                      create:
> >                         inputs:
> >                             name: { get_input: web_app_name }
> >                             image: { get_property: [ web_app, image] }
> >                             exposed_port: { get_property: [ web_app,
> > port] }
> >                             target_host: { get_property: [ database,
> > name] }
> >                             target_port: { get_property: [ database,
> > port] }
> >                             isService: true
> >
> > Regards,
> > DJ
> >
> > -----Original Message-----
> > From: Ran Ziv [mailto:ran@gigaspaces.com]
> > Sent: Thursday, May 25, 2017 4:07 PM
> > To: 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 opts to be a strict implementation of TOSCA wherever possible.
> >
> > Ran
> >
> > On Thu, May 25, 2017 at 1:22 PM, D Jayachandran <
> > d.jayachandran@ericsson.com
> > > wrote:
> >
> > > 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,
> > > DJ(D Jayachandran)
> > >
> >
>


--=20
Tal Liron
Senior Engineer
tal@gigaspaces.com | +1 (773) 828-9339
Cloudify | http://getcloudify.org
<http://getcloudify.org?utm_source=3Dsignaturesatori&utm_medium=3Demail&utm=
_campaign=3Dgeneral_signature>

<https://twitter.com/CloudifySource>
<https://www.linkedin.com/groups/8467478>
<https://github.com/cloudify-cosmo>   <https://github.com/cloudify-cosmo>
[image: Azure Webinar]
<http://getcloudify.org/webinars/Azure-plugin-for-cloudify-webinar.html?utm=
_source=3Dsignaturesatori&utm_medium=3Demail&utm_campaign=3Dgeneral_signatu=
re>

--001a113ece4a056e5a05505cd60b--