I mean the pre-load db is part of deployment not a manual process…

Good to hear :) we’ll look at logs as maybe this part failed for us. Thanks

The default value for VNF_DG_MAPPING should be pre-loaded when doing deployment…

Alexis, I remember I had to make a few manual changes to work with OpenStack actions. I’m copying parts of an email that I sent to APPC Team a few months ago. This was tested with Casablanca.

Also, I don’t know if it’s normal, but we had to add this in the sdnctl DB of appc to make it work. MariaDB [sdnctl]> select * from

Yes, setup as follow in the screenshot. The payload is the following, which seems similar as yours: { "input": { "common-header": { "timestamp": "2019-05-16T14:47:55.449Z",

Alexis, Are you using CDT? What is your setup? I ran this fine in the past from Postman: { "input": { "common-header": { "timestamp": "{{serverDate}}", "api-ver":

No that is for Dublin release. 1.5.0-SNAPSHOT Taka

Hi Taka, These tests in APPC was it on Casablanca release? Regards, Steve

Yes, agreed. Using Casablanca 3.0.1-ONAP version of APPC

Alexis, Agree you shouldnt have to tweak the DG. Seems like the decoding before calling the DG isnt firing quite right for some reason in your Casablanca instance. Brian

It sounds like indentity-url is required… need to check the “secret” code☹ Taka

Taka, I understand you ran testing, I would need to look into that. Also, note, I’m using Casablanca. It looks like `input.payload`, which is a JSON, isn’t converted to SLI ctx. `vm-id` that is

Hi Seshu and SO team, It has come to our attention that even though SO has released version 1.4.1 of docker images, the dublin staging builds are continuing to build 1.4.1-STAGING-latest which is

Sorry, folks. I have been focusing on the bugs fix these days… Alexis, We ran 72 hours performance testing for APPC that contains “start” lcm in Windriver labs APPC tenant. Here is the

It looks like its the encoding that is not quite right. 2019-05-16 14:00:45,830 | INFO | ppc-dispatcher-6 | ProviderOperation | 503 - appc-iaas-adapter - 1.4.4 | APPC0057I APPC

Hi, Referring to our discussion on this Wednesday’s control loop subcommittee meeting, it felt that we have quite a different view on what is actually included in current vFWCL case. To get some

Brian, Team, We are following this example. Here is our payload { "input": { "common-header": { "timestamp": {{timestamp}}, "api-ver": "2.00",

Pairwise complete – updated, a couple components either don’t ship logs, need a filebeat refactor or need more advanced use cases on my

Hi Liu, We were unable to do much with Scaling in the Dublin Release because of resource issues. The only thing we did is make auto-scale out a little easier to use. It looks like El Alto will be a