https://www.ejbca.org/ part of contrib Von: onap-discuss@... <onap-discuss@...> Im Auftrag von minsang.yoon@... Gesendet: Freitag, 16. April 2021 15:22 An: ale

#sdnc #guilin #oom #deployment

What is the ejbca pods? It comes with which component?

#sdnc #guilin #oom #deployment

I don't see the issue with actual helm charts in guilin. at least two successful deployments. Out of your error messges I would investigate further all potential components in the chain: certcervice,

#sdnc #guilin #oom #deployment

I am facing the exact same problem. I know there was no this issue before maintenance release. I still have helm chart before maintenance release so I could deploy SDNC successfully with old chart. Bu

#sdnc #guilin #oom #deployment

Hi All, While deploying ONAP guilin release using oom, SDNC pods are not coming up: onapit-sdnc-0 0/2 Init:Error 6 29m onapit-sdnc-ansible-server-668576f5b4-pf76j 0/1 Init:1/2 2 29m onapit-sdnc-db-0 1

#sdnc #guilin #oom #deployment

CDS team, In the Honolulu release build, the CDS py-executor node is no longer starting. I have created a Highest severity Jira for this issue: https://jira.onap.org/browse/CCSDK-3200 This is a BLOCKI

#ccsdk #sdnc

Hi Kamel/Brian, We tried to register ransim with the sdnc with schemaless as true and device is getting connected but when we try schemaless as false we are getting error as "RemoteDevice{ncserver3}:

#sdnc

All, Next week’s CCSDK/SDNC meeting (2/3/21) is cancelled due to conflict with the LFN Developer and Test Forum. We’ll meet next in 2 weeks (2/10/2021). Thanks, Dan

#ccsdk #sdnc

CCSDK/SDNC teams: In preparation for the Honolulu M2 milestone (scheduled for 1/21), I have completed the release planning templates for CCSDK and SDNC. They can be found at the following links: CCSDK

#ccsdk #sdnc

I’m working with SDNC in an environment that requires a proxy and a certificate to access a DMaaP message router. I’d appreciate it if you could give me pointers on how to configure SDNC to use them?

#ccsdk #sdnc

I don’t believe DCAE not being deployed would cause that error. I suspect more that SDNC might not have processed the TOSCA distribution correctly – either maybe due to a timing issue (if say it was p

#sdnc #frankfurt

Thank you Pavel and Dan. I will check them. Just one small thing. I have not deployed DCAE in our cluster (we currently do not have enough resources for all components) because it did not seem useful

#sdnc #frankfurt

Aliakbar, That error is indicating that you’re trying to instantiate a vf-module that SDNC doesn’t recognize. SDNC gets a feed from SDC of TOSCA models. So, what seems to be happening here is that for

#sdnc #frankfurt

Hi, Aliakbar Try change "sdnc_artifact_name" to just: vnf in your test service model (Properties Assignment -> sdnc filter). And sdnc_model_name should be equal CBA name. You can see CBA name here: se

#sdnc #frankfurt

Hi ONAP community, I am using ONAP Frankfurt and trying to instantiate a service on Openstack. Everything goes on well until I instantiate vf module. The SO returns this error message to me: ""STATUS:

#sdnc #frankfurt

Hi ONAP team, I got a problem when instantiating a service. the SDNC error says: " Received error from SDN-C: No preload data found to match vnf-name " when I checked the logs of SDNC components, I se

#sdnc #aai

CCSDK team: The code for the SLI is currently contained in 4 separate git repositories: ccsdk/sli/core : the core components of the service logic interpreter ccsdk/sli/adaptors : resource adaptors sup

#ccsdk #sdnc

CCSDK / SDNC team: As discussed on our call this morning, we need to create an initial release of our CCSDK and SDNC teams to facilitate early testing of some features in our next release. I’m in the

#sdnc #ccsdk

Hi All, I using the latest OOM chart. The cert-init container of dev-sdnc-0 pod is not coming up. PFB the events of dev-sdnc-0 pod: Events: Type Reason Age From Message ---- ------ ---- ---- ------- N

#sdnc

CCSDK/SDNC team, I need to cancel our call tomorrow due to a schedule conflict. See you next Wednesday! Dan

#ccsdk #sdnc