Hi Thomas, My email Id is : sudhakarreddy...@gmail.com Let me know once u add me. I'll update the findings in Confluence.
Thanks & Regards Sudhakar Reddy Contact No:8758383421 -----Original Message----- From: Thomas Nadeau [mailto:tnad...@lucidvision.com] Sent: Wednesday, March 07, 2018 10:15 PM To: dev@ariatosca.incubator.apache.org Subject: Re: Aria support for TOSCA-simple-1.1 What is your ID on confluence? I can add contributor permissions. > On Mar 7, 2018, at 11:29 AM, Sudhakar Reddy <sudhakar.re...@amdocs.com> wrote: > > Yeah. I'll check for the changes that are being made in 1.1 version. Btw, I > don’t have any rights to create a page in Confluence. > > Probably I'll share the document after initial investigation. > > > Thanks & Regards > Sudhakar Reddy > Contact No:8758383421 > > > -----Original Message----- > From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] > Sent: Wednesday, March 07, 2018 5:55 PM > To: dev@ariatosca.incubator.apache.org > Subject: Re: Aria support for TOSCA-simple-1.1 > > I agree. This is specifically why I created the area on the wiki yesterday. > Sudhakar, there is no need to start with python code changes. If you can > start by documenting what you think are the diffs in the specs and any other > requirements for changes, that is a great place to start. > > Tal, welcome back to the party! 8) > > --Tom > > > > On Wed, Mar 7, 2018 at 3:43 AM, Tal Liron <tal.li...@gmail.com> wrote: > >> 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> >>> >>> >> > 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>