Hi Michael, Installed Beijing as you suggest. I found one problem with robot when I am running "./demok8s.sh onap init_robot" it is failing and saying "/etc/.../authorization" is read-only file system and not able to update credential there.
I think seem some issue with permission setting up during deployment or something I am missing. Thanks, Vijendra From: Vijendra Singh Rajput Sent: Friday, 15 June 2018 12:58 PM To: Michael O'Brien <[email protected]> Cc: [email protected] Subject: Re: need your help Hi Michael, Thanks for clarification. Thanks, Vijendra Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Michael O'Brien <[email protected]<mailto:[email protected]>> Sent: Thursday, June 14, 2018 10:33:13 PM To: Vijendra Singh Rajput Cc: [email protected]<mailto:[email protected]> Subject: RE: need your help Hi, the Amsterdam release is essentially deprecated for several reasons - it is a hybrid kubernetes/heat deployment and it uses an old version of docker 1.12 - If you don't specifically need Amsterdam I recommend moving to Beijing or master (Casablanca). I personally did not have any issues with AWS - I mostly stuck to R4 instances - but only ones with EBS. For Beijing I use an EFS/NFS wrapper for the shared drive. There is a small chance you are compromised. If you are on public cloud - either run in a private VPC, set your SG to block 10249-10255 from outside the subnet - or set the oauth admin security to your github account. Check your df that the drive is not saturated as well. I would not be able to triage your docker specific issue without more details on which pod is causing this - however right now we are primarily focused on only working out issues with the latest releases - switch to a later release and post to this list and any number of ONAP enthusiasts will assist. Thank you /michael From: Vijendra Singh Rajput [mailto:[email protected]] Sent: Thursday, June 14, 2018 2:53 AM To: Michael O'Brien <[email protected]<mailto:[email protected]>> Subject: need your help Hello Michael, I deployed ONAP Amsterdam release on r4-4xlarge EC2 instance. All pods are in running state. health test is passed except DCAE and at this moment I don't bother about DCAE. I am facing one issue, starting all pods successfully, after 3-4 hrs I can see one process "/tmp/docker -c /tmp/k.conf" started and using 100% CPU with no resource left, which trigger cluster to panic state and all pods goes into different state (either pending or init) even tiller deploy pod goes in restart mode and not allowing to clean dead pods using oom scripts. sometime after killing that process goes away and cluster comes to healthy state but again this process will trigger automatically. could you please help me understand what is that process and why it is starting again and again even after killing. Your help really appreciated. Thanks, Vijendra 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://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fabout%2Femail-disclaimer&data=01%7C01%7CVijendra_Rajput%40infosys.com%7Cecf1da76b6d046e02b4508d5d1f31a08%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1&sdata=PChbiC27EhycBG4F0SkTSSP7Ss7VFshzE8wsibH0SC8%3D&reserved=0>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
