ariatosca-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Orlov <ma...@cloudify.co>
Subject Re: Unique identification of an instance element across services
Date Tue, 25 Jul 2017 18:28:43 GMT
Actually the refactoring was made so the id would be more user readable.
The index is determined according to the used indices (it's not just a
running number). If indeed this poses an issue (or if 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 <tal@cloudify.co> wrote:

> 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, Jul 25, 2017 at 3:42 AM, Vaishnavi K.R <vaishnavi.k.r@ericsson.com
> >
> wrote:
>
> > Hi,
> >
> >
> > With my understanding in current ARIA, the node instances are made unique
> > by prefixing the node name with the 'id of the service' (i.e. the primary
> > key of the service table) as the instances are specific to the service.
> >
> >
> > What will be the name of the node instances if the default instances for
> > the node template is '3' and how this will hold good during scale in and
> > out?
> >
> >
> > Could UUID be of great help in handling such cases by including that as a
> > column in the database tables of the service and the node?
> >
> > This will wipe out the naming confusions and querying can be made easy
> > with the UUIDs.
> >
> >
> > Looking forward to your suggestion.
> >
> >
> > Thanks,
> >
> > /Vaish
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message