Hi, Kindly clarify following queries for dcae_cli tool a) Is dcae_cli postgress database for catalog a separate database, can we use existing database from other ONAP components (i.e.

Hi all, It’s come to our attention that some entries in the docker manifest do not actually exist in nexus3. Since we’re now past RC1, I’m turning on a validation to ensure that all the

Just to update; upgrading helm indeed did fix the issue. Below are the steps incase someone else stumbles on similar issue. wget

Hi, Currently we have the SDN-C and APP-C and VFC in the architecture. There has been proposals in the directional architecture to bring this down to SDN-C and A Generic NF controller. In this

SO sets that field in A&AI, at distribution time. Thanks -Steve From: <onap-discuss-bounces@...> on behalf of Andrew Fenner <andrew.fenner@...> Date: Thursday, May 3, 2018 at 12:51 PM To:

Hi, Looking at the latest (todays) images for VID and AAI I think I see a mismatch. VID is doing a query into AAI looking for {"start" : "service-design-and-creation/models/","query" :

Greetings Jaroslav, Nexus 2 is still required by our environment. The reason being that Nexus 3 still does not provide any staging capabilities for Maven artifacts. Additionally, we heavily leverage

Finally I have the answer. Thank you for the clarification. Now I understand. BR, AT&T Network Application Development · NetCom Tel Aviv | Tampa |

Since the Jenkins jobs are actually run by an external Jenkins instance, the timestamps on jenkins.onap.org for the external jobs only reflect the times when the resulting logs are retrieved. For the

Hi Michael (and Josef) Thank you for the update! I will try switching to newer helm and check. The other warning reported was indeed noticed before (that dint really interfere with the

Vijaj, Hi, I was worried about this. There was a change put in for APPC where a helm upgrade to 2.8.2 was required. We already were prototyping the 2.7.2 to 2.8.2 was beneficial for onap

Then I am missing something from the flow…. What I see in the Jenkins is that from start to the end it runs from just a couple of minutes. But you say it retries for 2.5? are this retries

Mandeep, Hi, forwarding to community. Welcome – Accenture is an excellent and very efficient organization from my experience. From the pod names and namespace below – it looks like a

It currently retries health checks for about 2.5 hours. Do we need more than that? Thanks, Gary

Gary if possible since you are making modifications to the external deploy can you provide more time to the system to start before the heath checks kick in? Or add more retries.

They are normally once a day, around midnight PDT for Wind River and around noon PDT for TLAB. I just made some major changes to the OOM deployment recently so I may manually kick off some more OOM

It’s part of an automated process that Gary manages. ONAP builds are kicked via Jenkins job periodically. There should probably be another deployment this afternoon if I’m not wrong. Gary can

Great thank you for the info, Are you planning to re-run the job today? BR, AT&T Network Application Development · NetCom Tel Aviv | Tampa | Atlanta | New

Are we looking at the same job? https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/338/console when I look here I see only failures? And from what I saw the

Andrej, I suppose there are a variety of ways this could be implemented, as all three derive from CC-SDK. SDN-R = CC-SDK + Mobility Wireless “artifacts” Tracy