Hi, There are several documentations for APPC that describe for the architecture and the response code from APPC request. https://docs.onap.org/en/latest/submodules/appc.git/docs/APPC%20User%20Guide/A

#appc #ccsdk

Hi guys, I try to integrate APP-C with our current LCM system. There are some uncertainties. Hope I would get some leads here. 1. Northbound Ability Please consider an architecture with three layers.

#appc #ccsdk

Hi guys, I try to integrate APP-C with our current LCM system. There are some uncertainties. Hope I would get some leads here. 1. Northbound Ability Please consider an architecture with three layers.

#appc #ccsdk

Can you send trace level karaf log ? Taka Pardon any typos from iPhone

#appc

You are using the generic execute-graph, can you try using restconf/operations/appc-provider-lcm:stop API from swagger? Taka, Can you please chime in if you see something wrong? From: Vikas Kumar <vku

#appc

Thanks for the replay Marco, The URL does exist as I am able to do the stop operation with the same URL using APPC swagger and it works. The escape chars which I mentioned are not the one in the paylo

#appc

The request is correct. See below generic structure for LCM stop operation: { "input": { "common-header": { "timestamp": "{{serverDate}}", "api-ver": "2.00", "originator-id": "{{orginatorId}}", "reque

#appc

Hi Marco, Taka, I am facing an issue while doing LCM Stop operation. In karaf.log it says VM URL is invalid (please see the log snippet below). I noticed that in my request additional escape chars are

#appc

Dear Taka, Thank you for your advice. Previously I git pull by 'git clone -b 5.0.1-ONAP http://gerrit.onap.org/r/oom --recurse-submodules'. I pull the head of master this time. And it works, thank you

#appc #helm

I saw your failure was on common/etcd. Did you git pull to the head of master for the all OOM repo? Taka APPC PTL

#appc #helm

Hi, I want to deploy APP-C for testing its capability, and I follow oom_quickstart_guide And I use Helm 2.16.1, macOS Catalina version 10.15.1 However, after I modified 'appc enable: true' and run 'ma

#appc #helm

Beejal, The Frankfurt design in its full implementation will allow the designer to selector the actor in SDC at resource level. Once selected, no other manual touch point shall be required by the user

#appc #cds #ccsdk

Hi Yuriy, Is it only SDC work that’s needed or SO too? Can I manually update the catalogdb and trigger the call to CDS? Thanks, Beejal

#appc #cds #ccsdk

You would have various of choices for scaling use case in Frankfurt. In APPC, we would use ansible as the specific protocol and also we would adopt with CDS during the runtime for scaling use case. Pl

#appc #cds #ccsdk

Well, this goes against what I just wrote 😊 To clarify, CDS can be used as actor in Frankfurt, not in Dublin. Marco From: <onap-discuss@...> on behalf of "MALAKOV, YURIY" <ym9479@...> R

#appc #cds #ccsdk

No, it’s not, as APPC is the current action executor. CDS is only used for instantiation and post-instantiation (El Alto) configuration. Marco From: <onap-discuss@...> on behalf of Beejal S

#appc #cds #ccsdk

++ Scott Beejal, Yes, it’s possible. In Frankfurt , ONAP is planning to add in SDC the controller_actor field with ENUM of SDNC, APPC, and CDS, within a context of a VF/PNF RESOURCE. This will allow t

#appc #cds #ccsdk

I am looking at the scale out use case: https://onap.readthedocs.io/en/latest/submodules/integration.git/docs/docs_scaleout.html The above link mentions "Users need to specify which controller to use

#appc #cds #ccsdk

Hi, It has been some time sinc I was playing around Casablanca, that issue below seems to be related of problem with setting-up APPC mount point (w/o it CL will not happen) I would check APPC karaf.lo

#appc

Hello, I have created a vFW closed service by following the guide https://docs.onap.org/en/casablanca/submodules/oom/offline-installer.git/docs/vFWCL-notes.html. After appc mount step, I verify that n

#appc