Hi all, I am using ONAP Frankfurt release. I see that all of databases are deployed using statefulset and without any operators. Is that OK for a production environment? If no, how can I fix this? Tha

#kubernetes #oom

Hi, If all nodes( master and worker node) goes out of network, What should be the outcome? We have deployed frankfurt release. In our case due to the network failure, kubernetes cluster gets reformed

#kubernetes

Hi, I'm trying to run CNF deployment by following the pages: https://wiki.onap.org/display/DW/Deploying+vFw+and+EdgeXFoundry+Services+on+Kubernets+Cluster+with+ONAP . I took the vfw helm chart from ge

#5G #k8s #multicloud #kubernetes

actually it's a "AWX" issue: https://github.com/ansible/awx/issues/5473 De : onap-discuss@... [onap-discuss@...] de la part de jas.dhillon@... [jas.dhillon@...

#kubernetes #elalto #nodeport

Hello, I took a look on a master: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied) 2020-04-16 05:37:44,301 INFO exited: nginx (exit status 1; not expected) 2020-04-16 05:37:45,303 IN

#kubernetes #elalto #nodeport

Hello, The `awx-service` (running at port 30478) results in connection-refused. It seems like the actual `awx_task` process is running on port 8050, but the k8s-service is created on port 8052: --- ap

#kubernetes #elalto #nodeport

Hi, removing old configmaps versions and limiting the helm history to 5-10 versions did the trick for me. > https://github.com/helm/helm/issues/2332#issuecomment-336565784 Regards David -- David Pérez

#oom #helm #casablanca #lfn #kubernetes

Hi, I am starting to get errors like the one below when deploying/undeploying with helm, branch Casablanca, running for ~70 days. # helm undeploy dev-sniro-emulator --purge Error: trying to send messa

#oom #helm #casablanca #lfn #kubernetes

Hi Marco, Thanks again for your support and guidance. I have successfully uploaded the policies for vFW_PKG following your approach, and I can view them as well in Policy UI. The Drools rules artifact

#casablanca #oom #kubernetes #policy

Kamel, I’m not sure whether the update-policy script has been tested recently, so I propose another approach in case that script doesn’t work for you: Login to PAP Policy container from Rancher VM Cop

#casablanca #oom #kubernetes #policy

For ONAP Casablanca release, the update-vfw-op-policy.sh script is under /oom/kubernetes/policy/charts/drools/resources/scripts folder as shown below ubuntu@onap-1:~/oom/kubernetes/policy/charts/drool

#casablanca #oom #kubernetes #policy

Hi Alexis de Talhouet, I have instantiated vFWCL with ONAP Casablanca release and while configuring the closed-loop part, I'm not able to find the update-vfw-op-policy.sh script under oom/kubernetes/p

#casablanca #oom #kubernetes #policy

Team, There is at least one team that is not reserving nodeports – this has caused several instances of nodeport conflicts during a full helm deploy – this has occurred regularly over the past 6 month

#oom #kubernetes #nodeport

Hey there, Maybe this can help with this topic, I found that Kured[1] helps to drain the workers before they’re restarted. Its installation is thru a Kubernetes objects and it supports several K8s ver

#beijing #kubernetes #oom

Jobs are used in ONAP primarily to perform one-time database initialization. A limitation in using a Job is that it runs to completion and will not be restarted. If there are Pods that depend on the c

#beijing #kubernetes #oom

Hi, This is a kubernetes undercloud issue – not specific to onap I regularly restart my VMware VM’s – especially when duplicating VMs across laptops – in that case there are 3 scenarios – I would like

#beijing #kubernetes #oom

I have faced the same issue. But haven’t found a solution so far except for reinstalling ONAP. Regards, Atif

#beijing #kubernetes #oom

After a power outage about 75% of the pods come back. And for the most part the functionality is not working. Seeing a bunch of errors for pods that look like this: container "portal-db-job" in pod "o

#beijing #kubernetes #oom

Hello, According to your output, readiness checks are failing, make sure that policydb and nexus container dependencies come up ok. Best regards, Jorge

#install #usecaseui #kubernetes #policy #drools

Hello, In Beijing installation the drools pod status is init and doesn't run. It's waiting on init status even deleted the pod several times, although there is no error in the logs. It can't create th

#install #usecaseui #kubernetes #policy #drools