Hi Yan, I would like to follow up on this thread and gather feedback from the discussion here.
The main request that comes up from the requirements document is to bring back support for a REST API to ARIA, exactly as it was previously exposed to Open-O NFVO, is this correct? We are working on creating a native REST API to ARIA, and the work-in-progress is expected to land soon. ARIA is a Python TOSCA SDK so it natively supports using Python objects, To get a complete Python reference documentation for ARIA you can just clone the upstream project and build the Spinx docs # git clone https://github.com/apache/incubator-ariatosca.git # make docs # firefox docs/html/index.html The cool part is that it's that ARIA can execute the TOSCA Template based workflows. Here is a basic hello world example of this works: First, provide ARIA with the ARIA "hello world" service-template and name it (e.g. my-service-template): aria service-templates store examples/hello-world/helloworld.yaml my-service-template Now create a service based on this service-template and name it (e.g. my-service): aria services create my-service -t my-service-template Finally, start a install workflow execution on my-service like so: aria executions start install -s my-service You should now have a simple web server running on your local machine. You can try visiting http://localhost:9090 to view our deployed application. ----- Additionally, we want to have the ability to consume ARIA as a Java in-process library and handle in-memory TOSCA objects, to traverse and extract information natively in Java. Currently, ARIA supports a complete CLI that can, among other things, emit JSON based on the parsed graph. ARIA also allows accessing its storage layer which is based on SQL, the SQL tier is another option for in-process Java integration as this allows native access to all the TOSCA related objects and artifacts, traversing thru the graph and others. # aria service-templates show --json helloworld I'm happy to provide reference examples for Java. Arthur On Mon, Jul 17, 2017 at 1:01 PM Kapeluto, Zahi <[email protected]> wrote: > Hi Yan, > > My feedback: > > * Most of the ONAP components, some of them already consume our TOSCA > parser (MSO, SDN-C, VID, SDN-GC), are Java-based hence require Java > language invoke. > * The common use-case we found is that components would like to > consume the parser in-process, i.e. get it as a library rather than a > service. > * Our parser creates an in-memory JAVA representation of the model. > The consuming component can then traverse over it and extract the > information it needs. Can you explain why you would need JSON output? > > Here are the repos of out TOSCA parser: > https://gerrit.onap.org/r/#/admin/projects/sdc/jtosca; > https://gerrit.onap.org/r/#/admin/projects/sdc/sdc-tosca. We can discuss > further if you’re interested in design concepts and architecture. > > Thanks, > Zahi Kapeluto > Lead Architect, Network Communications LOB > AT&T Network Applications Development · SD&E > Tel Aviv | Tampa | Atlanta | New Jersey | Chicago > ················································· > Mobile: +972 (54) 6636831 <+972%2054-663-6831> > Office: +972 (3) 9280064 <+972%203-928-0064> > > From: <[email protected]> on behalf of 杨艳 < > [email protected]> > Date: Friday, 14 July 2017 at 3:15 > To: 'Thomas Nadeau' <[email protected]>, "'denghui \\(L\\)'" < > [email protected]>, 'onap-discuss' <[email protected]> > Subject: [onap-discuss] 答复: [Modeling][vfc] TOSCA Parser API Requirements > > Hi Tom, > > Thanks for your suggestion, I have uploaded the document to the wiki > https://wiki.onap.org/display/DW/VF-C+R1+Deliverables< > https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_VF-2DC-2BR1-2BDeliverables&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Tb4B9h_-wR6nA2dMKyowUg&m=5Bw4qKyovq7EervinsZZT6r_C95YpsK1FjWB9Gbig8Q&s=DUEr4Tfnyhij1etU9TdUQu7-q9nZZpl9IpSmsbMeNWI&e=>, > If there is any feedback that need to update the document, I will update to > the wiki page. > > Best Regards, > Yan > 发件人: Thomas Nadeau [mailto:[email protected]] > 发送时间: 2017年7月13日 19:14 > 收件人: 杨艳; 'denghui \\(L\\)'; onap-discuss > 主题: RE: [onap-discuss] [Modeling][vfc] TOSCA Parser API Requirements > > Can you please post the document onto Jira somewhere rather than mailing > it around? That will allow everyone to look at the same version until its > changed. > > --Tom > > > From: [email protected] [mailto: > [email protected]] On Behalf Of ?? > Sent: Thursday, July 13, 2017 6:53 AM > To: 'denghui \\(L\\)' <[email protected]>; onap-discuss < > [email protected]> > Subject: Re: [onap-discuss] [Modeling][vfc] TOSCA Parser API Requirements > > > > > Very sorry,I forgot to add the attachment in last email. > > > > Best Regards, > > Yan > > ----邮件原文---- > 发件人："杨艳" <[email protected]<mailto:[email protected]>> > 收件人："'denghui \\(L\\)<file:///(L/)>'" <[email protected]<mailto: > [email protected]>>,onap-discuss <[email protected]<mailto: > [email protected]>> > 抄 送: (无) > 发送时间：2017-07-13 17:53:28 > 主题：[onap-discuss] [Modeling][vfc] TOSCA Parser API Requirements > Dear Modeling Project PTL, > > Please check the attachment about the API requirements of TOSCA Parser in > VF-C for R1, which has been discussed within the VF-C project team. And now > we want to submit it to the modeling project for evaluation and hope the > modeling project recommends appropriate Parser that can meet these > requirements. > > Best Regards, > Yan > 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Tb4B9h_-wR6nA2dMKyowUg&m=5Bw4qKyovq7EervinsZZT6r_C95YpsK1FjWB9Gbig8Q&s=g54dDgAe8HofmbM-e5sNFkOTC4JkYo_ieded3J3QTSM&e= > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-discuss >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
