Re: Unique identification of an instance element across services

[Tal Liron]

So, we actually don't have this working yet. The code is in there, but it
is not yet configurable. I've added a comment to ARIA-229 about
specifically handling this. Until ARIA-229 is resolved, this issue is still
open:

https://issues.apache.org/jira/browse/ARIA-229

Also, regarding service names, I've added a comment to ARIA-221. In my
opinion, service name auto-generation should follow the same rules as node
name auto-generation. That would be most coherent:

https://issues.apache.org/jira/browse/ARIA-221


On Fri, Oct 6, 2017 at 3:32 PM, Steve Baillargeon <
steve.baillarg...@ericsson.com> wrote:

> Hi
> About the UUID.
> As far as I know and mentioned a number of times, ARIA already support
> different kinds of ID generation.
> I have nothing to add on this topic.
>
> I would like to focus on the service-template name and the 'already exist'
> error generated by ARIA when the user submits a service-template with a
> name that is "already-in-use".
> When will this problem be resolved? Do we have a Jira for it?
> As previously indicated, ARIA must allow for duplicate service-template
> names.
>
> Here are the best practices for API regarding individual resource names
> and resource IDs.
>
> 1) The resource name is generated by the API consumer. It is optional. The
> resource name does *not* need to be globally unique. The resource name is
> usually human-readable.
> 2) If resource name is not generated by the API consumer, the API producer
> does not need to (automatically) generate a resource name.
> 3) The resource identifier is generated by the API producer. The resource
> identifier must be "globally unique". The resource ID does not need to be
> human-readable.
> 4) The API producer must use the resource identifier to uniquely identify
> the resource. It shall not use the resource name for identification
> purpose. The resource name (if provided) is metadata associated with the
> resource.
> 5) The API consumer must provide the resource ID when performing an
> operation on an existing resource.
>
> Regarding CLI and the existing Jira.
> https://issues.apache.org/jira/browse/ARIA-221
> I don't think it is a good idea.
> In fact, I think the API guidelines should apply to CLI as well.
> The main difference will be on 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 algorithm can be
> system-wide or per interface (?)
>
> -Steve B
>
>
>
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Monday, October 02, 2017 11:52 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Unique identification of an instance element across services
>
> I suggest that this discussion isn't too important now.
>
> What's important is that we have support for user configuration in ARIA,
> and that it is possible to easily switch between different kinds of ID
> generation.
>
> Once we have that working, we can go back to discussing what the default
> should be. As users gain some experience playing with different IDs we
> could get feedback.
>
> On Thu, Sep 28, 2017 at 9:29 AM, Vaishnavi K.R  >
> wrote:
>
> > Thanks Tal.
> >
> >
> > I think many of us are not convinced with the inclusion of the UUID
> > for element identification.
> >
> > As of now, we have ID for the unique identification. So why should we
> > restrict the users from giving duplicate names for the service templates.
> >
> >
> > I wish to confirm if anyone has a second opinion in allowing duplicate
> > names.
> >
> > If not, I can raise a JIRA issue and fix it.
> >
> > Looking forward to your comments.
> >
> >
> > Thanks,
> >
> > /Vaish
> >
> > 
> > From: Tal Liron 
> > Sent: Tuesday, September 26, 2017 2:04:50 AM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: Unique identification of an instance element across
> > services
> >
> > DeWayne, I think you missed parts of this discussion where we answered
> > some these issues:
> >
> > 1) ARIA *does* allow you configure you choice of ID generation, and I
> > agree it can be an integration requirement. (We have a JIRA open to
> > give this configuration a CLI.)
> > 2) ARIA has a choice of UUID formats beyond the very long 36-character
> hex.
> > Base57 is 22 characters and designed for human readability.
> > 3) All the costs you mention seem very negligible to me. ARIA's
> > database storage is tiny. UUID generation happens only when new nodes
> > are created, and is many orders of magnitude faster than storing
> anything in a database.
> >
> > It doesn't easy to resolve this issue, as there are two camps here.
> > But I'm very convinced that Vaish and I are correct here. :) Node (and
> > service) names in the real world are used for other systems beyond
> > ARIA once the 

Re: Node Template Substitution

[Avia Efrat]

Currently the design is finished, and it is on a small hold for now.
The plan is to support the 1.0/1.1 profile.

On Wed, Oct 4, 2017 at 7:50 PM, Steve Baillargeon <
steve.baillarg...@ericsson.com> wrote:

> Hi
> Can we have a status update on the availability of the Node Template
> Substitution feature (aka substitution mappings)?
> Will it support the "capabilities" defined in YAML Profile 1.0 or YAML
> Profile 1.2?
>
> Regards
> Steve B
>
>

Re: list of maps

[Tal Liron]

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:
  MyNode:
properties:
  my_property:
type: list
entry_schema: Element

topology_template:
  node_templates:
my_node:
  type: MyNode
  properties:
my_property:
  - {data: {a: b}}
  - {data: {c: d}}
  - {data: {e: f, g: h, i: j}}


On Fri, Oct 6, 2017 at 5:50 PM, DeWayne Filppi  wrote:

> How would one define a property that was a list of maps, e.g.
>
> prop:
>   -  a: b
>   -  c: d
>
>
> -- DeWayne
>

Re: Working towards Release 1

[Thomas Nadeau]

I asked for suggestions for dates/times. Please propose some. I want 
to try to make this as convent for everyone to attend as possible.  For
those that cannot, we will make every attempt to publish an agenda ahead
of the grooming as well as post facto meeting minutes on our wiki.

—Tom


> On Oct 6, 2017, at 7:34 PM, John D. Ament  wrote:
> 
> What's weekly grooming? Does it happen on list? If I don't work at
> Cloudify, how do I participate in weekly grooming?
> 
> John
> 
> On Thu, Oct 5, 2017 at 12:09 PM Thomas Nadeau 
> wrote:
> 
>> 
>>Agreed. We can update the Jira on the weekly grooming.
>> 
>>—Tom
>> 
>> 
>>> On Oct 5, 2017, at 11:24 AM, Tal Liron  wrote:
>>> 
>>> 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 expecting the comments(if any) in the JIRA itself,
 right?
 
 Vish
 
 
 
 From: Thomas Nadeau 
 Sent: Wednesday, October 4, 2017 3:38 PM
 To: dev@ariatosca.incubator.apache.org
 Subject: Working towards Release 1
 
 
   Tal and I sat down yesterday and started with a new epic (
 https://issues.apache.org/jira/browse/ARIA-386)
 in order to begin to capture what we think as a project, is needed to
>> get
 Aria to a stable release 1.0.  I like to do
 releases in “themes” so for this one it is simple: TOSCA 1.0
>> “compliance”
 as we see it.  There are related issues to
 releasing things, but this is a start. Please take a look and comment
>> here.
 
   —Tom
 
 
>> 
>> 

Re: Working towards Release 1

[Tal Liron]

We have a lot of timezones represented here, so we need to be considerate.
I'm in UTC-5.

On Mon, Oct 9, 2017 at 8:23 AM, Thomas Nadeau  wrote:

>
> I asked for suggestions for dates/times. Please propose some. I
> want
> to try to make this as convent for everyone to attend as possible.  For
> those that cannot, we will make every attempt to publish an agenda ahead
> of the grooming as well as post facto meeting minutes on our wiki.
>
> —Tom
>
>
> > On Oct 6, 2017, at 7:34 PM, John D. Ament  wrote:
> >
> > What's weekly grooming? Does it happen on list? If I don't work at
> > Cloudify, how do I participate in weekly grooming?
> >
> > John
> >
> > On Thu, Oct 5, 2017 at 12:09 PM Thomas Nadeau 
> > wrote:
> >
> >>
> >>Agreed. We can update the Jira on the weekly grooming.
> >>
> >>—Tom
> >>
> >>
> >>> On Oct 5, 2017, at 11:24 AM, Tal Liron  wrote:
> >>>
> >>> 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 expecting the comments(if any) in the JIRA
> itself,
>  right?
> 
>  Vish
> 
> 
>  
>  From: Thomas Nadeau 
>  Sent: Wednesday, October 4, 2017 3:38 PM
>  To: dev@ariatosca.incubator.apache.org
>  Subject: Working towards Release 1
> 
> 
>    Tal and I sat down yesterday and started with a new epic (
>  https://issues.apache.org/jira/browse/ARIA-386)
>  in order to begin to capture what we think as a project, is needed to
> >> get
>  Aria to a stable release 1.0.  I like to do
>  releases in “themes” so for this one it is simple: TOSCA 1.0
> >> “compliance”
>  as we see it.  There are related issues to
>  releasing things, but this is a start. Please take a look and comment
> >> here.
> 
>    —Tom
> 
> 
> >>
> >>
>
>

Re: Working towards Release 1

[Thomas Nadeau]

How does 12 noon EST on Mondays sound? We could go to 11AM EST which 
would be 8
for those in PST, 5 for CET and 6PM for IST.

—Tom


> On Oct 9, 2017, at 9:53 AM, Tal Liron  wrote:
> 
> We have a lot of timezones represented here, so we need to be considerate.
> I'm in UTC-5.
> 
> On Mon, Oct 9, 2017 at 8:23 AM, Thomas Nadeau  wrote:
> 
>> 
>>I asked for suggestions for dates/times. Please propose some. I
>> want
>> to try to make this as convent for everyone to attend as possible.  For
>> those that cannot, we will make every attempt to publish an agenda ahead
>> of the grooming as well as post facto meeting minutes on our wiki.
>> 
>>—Tom
>> 
>> 
>>> On Oct 6, 2017, at 7:34 PM, John D. Ament  wrote:
>>> 
>>> What's weekly grooming? Does it happen on list? If I don't work at
>>> Cloudify, how do I participate in weekly grooming?
>>> 
>>> John
>>> 
>>> On Thu, Oct 5, 2017 at 12:09 PM Thomas Nadeau 
>>> wrote:
>>> 
 
   Agreed. We can update the Jira on the weekly grooming.
 
   —Tom
 
 
> On Oct 5, 2017, at 11:24 AM, Tal Liron  wrote:
> 
> 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 expecting the comments(if any) in the JIRA
>> itself,
>> right?
>> 
>> Vish
>> 
>> 
>> 
>> From: Thomas Nadeau 
>> Sent: Wednesday, October 4, 2017 3:38 PM
>> To: dev@ariatosca.incubator.apache.org
>> Subject: Working towards Release 1
>> 
>> 
>>  Tal and I sat down yesterday and started with a new epic (
>> https://issues.apache.org/jira/browse/ARIA-386)
>> in order to begin to capture what we think as a project, is needed to
 get
>> Aria to a stable release 1.0.  I like to do
>> releases in “themes” so for this one it is simple: TOSCA 1.0
 “compliance”
>> as we see it.  There are related issues to
>> releasing things, but this is a start. Please take a look and comment
 here.
>> 
>>  —Tom
>> 
>> 
 
 
>> 
>> 

Re: Working towards Release 1

[Arthur Berezin]

+1 for Monday 11AM EST


On Mon, Oct 9, 2017 at 9:23 PM Thomas Nadeau  wrote:

>
> How does 12 noon EST on Mondays sound? We could go to 11AM EST
> which would be 8
> for those in PST, 5 for CET and 6PM for IST.
>
> —Tom
>
>
> > On Oct 9, 2017, at 9:53 AM, Tal Liron  wrote:
> >
> > We have a lot of timezones represented here, so we need to be
> considerate.
> > I'm in UTC-5.
> >
> > On Mon, Oct 9, 2017 at 8:23 AM, Thomas Nadeau 
> wrote:
> >
> >>
> >>I asked for suggestions for dates/times. Please propose some. I
> >> want
> >> to try to make this as convent for everyone to attend as possible.  For
> >> those that cannot, we will make every attempt to publish an agenda ahead
> >> of the grooming as well as post facto meeting minutes on our wiki.
> >>
> >>—Tom
> >>
> >>
> >>> On Oct 6, 2017, at 7:34 PM, John D. Ament 
> wrote:
> >>>
> >>> What's weekly grooming? Does it happen on list? If I don't work at
> >>> Cloudify, how do I participate in weekly grooming?
> >>>
> >>> John
> >>>
> >>> On Thu, Oct 5, 2017 at 12:09 PM Thomas Nadeau  >
> >>> wrote:
> >>>
> 
>    Agreed. We can update the Jira on the weekly grooming.
> 
>    —Tom
> 
> 
> > On Oct 5, 2017, at 11:24 AM, Tal Liron  wrote:
> >
> > 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 expecting the comments(if any) in the JIRA
> >> itself,
> >> right?
> >>
> >> Vish
> >>
> >>
> >> 
> >> From: Thomas Nadeau 
> >> Sent: Wednesday, October 4, 2017 3:38 PM
> >> To: dev@ariatosca.incubator.apache.org
> >> Subject: Working towards Release 1
> >>
> >>
> >>  Tal and I sat down yesterday and started with a new epic (
> >> https://issues.apache.org/jira/browse/ARIA-386)
> >> in order to begin to capture what we think as a project, is needed
> to
>  get
> >> Aria to a stable release 1.0.  I like to do
> >> releases in “themes” so for this one it is simple: TOSCA 1.0
>  “compliance”
> >> as we see it.  There are related issues to
> >> releasing things, but this is a start. Please take a look and
> comment
>  here.
> >>
> >>  —Tom
> >>
> >>
> 
> 
> >>
> >>
>
>

Re: Working towards Release 1

[Tal Liron]

Either works for me.

On Mon, Oct 9, 2017 at 7:06 PM, Arthur Berezin  wrote:

> +1 for Monday 11AM EST
>
>
> On Mon, Oct 9, 2017 at 9:23 PM Thomas Nadeau 
> wrote:
>
> >
> > How does 12 noon EST on Mondays sound? We could go to 11AM EST
> > which would be 8
> > for those in PST, 5 for CET and 6PM for IST.
> >
> > —Tom
> >
> >
> > > On Oct 9, 2017, at 9:53 AM, Tal Liron  wrote:
> > >
> > > We have a lot of timezones represented here, so we need to be
> > considerate.
> > > I'm in UTC-5.
> > >
> > > On Mon, Oct 9, 2017 at 8:23 AM, Thomas Nadeau 
> > wrote:
> > >
> > >>
> > >>I asked for suggestions for dates/times. Please propose some. I
> > >> want
> > >> to try to make this as convent for everyone to attend as possible.
> For
> > >> those that cannot, we will make every attempt to publish an agenda
> ahead
> > >> of the grooming as well as post facto meeting minutes on our wiki.
> > >>
> > >>—Tom
> > >>
> > >>
> > >>> On Oct 6, 2017, at 7:34 PM, John D. Ament 
> > wrote:
> > >>>
> > >>> What's weekly grooming? Does it happen on list? If I don't work at
> > >>> Cloudify, how do I participate in weekly grooming?
> > >>>
> > >>> John
> > >>>
> > >>> On Thu, Oct 5, 2017 at 12:09 PM Thomas Nadeau <
> tnad...@lucidvision.com
> > >
> > >>> wrote:
> > >>>
> > 
> >    Agreed. We can update the Jira on the weekly grooming.
> > 
> >    —Tom
> > 
> > 
> > > On Oct 5, 2017, at 11:24 AM, Tal Liron  wrote:
> > >
> > > 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 expecting the comments(if any) in the JIRA
> > >> itself,
> > >> right?
> > >>
> > >> Vish
> > >>
> > >>
> > >> 
> > >> From: Thomas Nadeau 
> > >> Sent: Wednesday, October 4, 2017 3:38 PM
> > >> To: dev@ariatosca.incubator.apache.org
> > >> Subject: Working towards Release 1
> > >>
> > >>
> > >>  Tal and I sat down yesterday and started with a new epic (
> > >> https://issues.apache.org/jira/browse/ARIA-386)
> > >> in order to begin to capture what we think as a project, is needed
> > to
> >  get
> > >> Aria to a stable release 1.0.  I like to do
> > >> releases in “themes” so for this one it is simple: TOSCA 1.0
> >  “compliance”
> > >> as we see it.  There are related issues to
> > >> releasing things, but this is a start. Please take a look and
> > comment
> >  here.
> > >>
> > >>  —Tom
> > >>
> > >>
> > 
> > 
> > >>
> > >>
> >
> >
>