Hi Michael, The guides you mention assume that the compute infrastructure has been already setup and concentrate on ONAP itself. The Cloud Setup Guide<https://onap.readthedocs.io/en/beijing/submodules/oom.git/docs/oom_cloud_setup_guide.html#cloud-setup-guide-label> will eventually describe many environments (as found in the wiki) but currently only describes a Rancher on OpenStack environment and contain the NFS setup required for a multi-node cluster.
OOM currently does use Persistent Volumes and Persistent Volume Claims (there is some documentation on this here<https://onap.readthedocs.io/en/beijing/submodules/oom.git/docs/oom_developer_guide.html#persistent-volumes>). Here is a randomly chosen example of the config from the oom/kubernetes/policy/charts/drools/charts/nexus/values.yaml<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing>: 70<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l70> ## Persist data to a persitent volume 71<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l71> persistence: 72<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l72> enabled: true 73<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l73> volumeReclaimPolicy: Retain 74<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l74> accessMode: ReadWriteMany 75<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l75> size: 2Gi 76<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l76> mountPath: /dockerdata-nfs 77<https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/policy/charts/drools/charts/nexus/values.yaml;h=03a03cc1985a7e1ed580c9dc2aa3d98c86d32747;hb=refs/heads/beijing#l77> mountSubPath: nexus/data During the Casablanca release the OOM team plans to support a wider variety of K8s Storage Classes so allow more flexibility in deployment. Cheers, Roger From: <[email protected]> on behalf of Michael Still <[email protected]> Date: Tuesday, June 19, 2018 at 4:13 AM To: "[email protected]" <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [onap-discuss] AAF kubernetes pods failing Thanks for this. You're totally right, I didn't have a shared NFS mount across the kubelets. Interestingly I can't see this mentioned in the getting started guide or the install guide. I concede its in the kube setup guide though. Is there are good reason that OOM isn't using more traditional persistent volume claims via kubernetes storage providers? Thanks, Michael On Tue, Jun 19, 2018 at 5:24 PM Michal Ptacek <[email protected]<mailto:[email protected]>> wrote: Hi, I believe that this problem might be caused by missing mountpoint /opt/app/osaaf this might pop-up when nfs share is not established across computes see "Setting up an NFS share for Multinode Kubernetes Clusters" in http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html#onap-on-kubernetes-with-rancher br, Michal --------- Original Message --------- Sender : Michael Still <[email protected]<mailto:[email protected]>> Date : 2018-06-19 04:57 (GMT+1) Title : Re: [onap-discuss] AAF kubernetes pods failing To : [email protected]<mailto:[email protected]> CC : [email protected]<mailto:[email protected]> Hi, I am seeing exactly this problem today with an attempted Beijing install using OOM. The aaf-locate container is logging: /bin/bash: /opt/app/osaaf/logs/locate/stdout`date -I`: No such file or directory Has anyone found a work-around for this? Thanks, Michael On Sat, May 12, 2018 at 6:48 AM William Kurkian <[email protected]<mailto:[email protected]>> wrote: Hello, On my onap install, most of the AAF pods are not starting. It seems to be largely because of one pod that has an error sending it into CrashLoopBackoff. It is the aaf-locate pod and it gets this error: /bin/bash: /opt/app/osaaf/logs/locate/stdout`date -I`: No such file or directory Is this known and expected? or is it some issue on my machine? Thanks, William Kurkian _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss -- Did this email leave you hoping to cause me pain? Good news! Sponsor me in city2surf 2018 and I promise to suffer greatly. http://www.madebymikal.com/city2surf-2018/ _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss [cid:[email protected]] [http://ext.w1.samsung.net/mail/ext/v1/external/status/update?userid=m.ptacek&do=bWFpbElEPTIwMTgwNjE5MDcyNDEyZXVjbXMxcDNjMTRlZWUyMGZiOWViNDAzMWI3MTJlNGI2ZjU3N2FhNCZyZWNpcGllbnRBZGRyZXNzPW1pa2FsQHN0aWxsaHEuY29t] -- Did this email leave you hoping to cause me pain? Good news! Sponsor me in city2surf 2018 and I promise to suffer greatly. http://www.madebymikal.com/city2surf-2018/ This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
