I'm willing to help with this effort is someone can get it started.

What we really need is to spec this out -- can you start by documenting on
the wiki all the changes that ARIA would need to support 1.1? Once we have
that, we can turn it into JIRA tasks that individuals can handle.

On Wed, Mar 7, 2018 at 2:27 AM, Sudhakar Reddy <sudhakar.re...@amdocs.com>
wrote:

> Hi,
>
> I'm new to python and aria. So, it'll be difficult for me to
> design/implement this without getting some knowledge on how the YAML
> specification is been converted.
>
> I would like to be part of it if I can get inputs on how the approach
> should be.
>
> Thanks & Regards
> Sudhakar Reddy
> Contact No:8758383421
>
> -----Original Message-----
> From: D Jayachandran [mailto:d.jayachand...@ericsson.com]
> Sent: Tuesday, March 06, 2018 12:23 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: RE: Aria support for TOSCA-simple-1.1
>
> Hi Sudhakar,
>
> Am representing ericsson here and we would also like to have the support
> for simple YAML 1.1 with ARIA at the earliest.
> It would be great if you can even contribute in making ARIA compliant to
> simple YAML 1.1 so that the support would be available soon.
> Please share your thoughts over this.
>
> Regards,
> DJ
>
> -----Original Message-----
> From: Sudhakar Reddy [mailto:sudhakar.re...@amdocs.com]
> Sent: Thursday, March 01, 2018 10:46 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Aria support for TOSCA-simple-1.1
>
> Hi,
>
> I want to know whether we are in the process of giving the support for
> TOSCA definition: simple_yaml_1_1?
>
> As currently ONAP uses 1.1 version yaml to create the service model, the
> same won't be validated by aria. Let me know your inputs on this.
>
> Thanks & Regards
> Sudhakar Reddy
> Contact No:8758383421
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>
>

Reply via email to