;> It is important to provide a reliable, normative means to represent
> a
> > >>>> version string which enables the comparison and management of types
> > and
> > >>>> templates over time.
> > >>>> Therefore, the TOSCA TC intends to p
omparison and management of types
> and
> >>>> templates over time.
> >>>> Therefore, the TOSCA TC intends to provide a normative version type
> >>>> (string) for this purpose in future Working Drafts of this
> >> specification.
> >>>>
> >>>> I al
ification.
>>>>
>>>> I also see text about TOSCA version comparison.
>>>>
>>>> It seems like TOSCA version can be used by the parser to show
>>> differences
>>>> between 2 templates or to highlight types with differe
; > between 2 templates or to highlight types with different versions in
> the
> > > same template.
> > > I think this is a useful feature to add to ARIA. What do you think?
> > >
> > > In general, what is the process to request an enhancement to ARIA?
>
to highlight types with different versions in the
> > same template.
> > I think this is a useful feature to add to ARIA. What do you think?
> >
> > In general, what is the process to request an enhancement to ARIA?
> >
> >
> > Cheers
> > St
think?
>
> In general, what is the process to request an enhancement to ARIA?
>
>
> Cheers
> Steve B
>
>
>
>
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Tuesday, August 08, 2017 9:07 AM
> To: dev@ariatosca.incubator.ap
rs
Steve B
-Original Message-
From: Tal Liron [mailto:t...@cloudify.co]
Sent: Tuesday, August 08, 2017 9:07 AM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Version support for different TOSCA types
My understanding has been that this is simply internal metadata, like the
"des
> version in my service template ?
> In that case how can the node template choose a particular version
> of the custom node type ?
> Or Is the version only for the template author to track changes
> about custom types over time ?
>
>
> Regards,
> DJ
>
> --
author to track changes about
custom types over time ?
Regards,
DJ
-Original Message-
From: Tal Liron [mailto:t...@cloudify.co]
Sent: Tuesday, August 08, 2017 12:11 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Version support for different TOSCA types
There is no special
ions, as well as template definitions which could be
> version and change over time. "
>
>
> Regards,
> DJ
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Monday, August 07, 2017 9:04 PM
> To: dev@ariatosca.incubator.apache.org
>
2017 9:04 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Version support for different TOSCA types
OK, you are referring to the "version" data type, and it is fully supported in
ARIA, which includes:
1. Strict adherence to the (rather odd) specification and its regex 2. Proper
support for TOS
TOSCA-Simple-Profile-
> YAML/v1.0/os/TOSCA-Simple-Profile-YAML-v1.0-os.pdf
>
> Regards,
> DJ
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Friday, August 04, 2017 9:39 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Versio
...@cloudify.co]
Sent: Friday, August 04, 2017 9:39 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Version support for different TOSCA types
I think you are referring to TOSCA 1.1, which is on the roadmap but not
supported yet.
You can of course create your own "version" p
I think you are referring to TOSCA 1.1, which is on the roadmap but not
supported yet.
You can of course create your own "version" property or attribute for node
types in TOSCA 1.0.
On Fri, Aug 4, 2017 at 7:05 AM, D Jayachandran
wrote:
> Hi,
>
> The TOSCA spec mentions about the version as a ke
Hi,
The TOSCA spec mentions about the version as a keyname for different type
definitions(Node, Group, Interface, Artifacts, Data .. .)
As mentioned in spec this is for the re-use of different types . Does ARIA
support the version at this stage ? What is the scope of orchestrator when it
comes
15 matches
Mail list logo
