Raj, Just out of curiosity, does ONAP Guilin release work with Helm3?
Thanks, Xin Miao Solution Engineering Fujitsu Network Communication (W)972-479-2263 (M)469-268-5226 2811 Telecom Drive Richardson, TX 75081, USA From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Rajendra Prasad Mishra Sent: Wednesday, May 12, 2021 12:08 AM To: onap-discuss@lists.onap.org; Rajendra Prasad Mishra <rpmis...@aarnanetworks.com> Cc: Bhagyalakshmi R <rbhagy...@gmail.com>; vishal.official1...@gmail.com; Vamshi Namilikonda <vn00480...@techmahindra.com> Subject: Re: [onap-discuss] #vid Hi Bhagyalakshmi, Vishal, I believe you are now successfully able to deploy ONAP on OpenShift. I am also trying the same stuff and require some help. We are able to do the basic changes (around security context, anyuid etc.) on OpenShift and are able to get multiple components up on OpenShift. However, we are facing issues with AAF component, specifically around configmap in aaf-sms. The log says that the " /opt/app/osaaf/local/org.onap.aaf-sms.key" file is not found. This file is provided using configMap by certInitilizer component in ONAP. The same chart works well on other K8 clusters. So the question is, did you guys do anything specific on OpenShift specially around ConfigMap ? If possible can you share the helm chart diff for common/CertInitlizer and AAF/aaf-sms components. For the record, we are using Guilin release with helm 3 based deployment. I would also like to know how you dealt with NFS server issue (the /dockerdata-nfs mounts) Here is the error log of aaf-sms pod. ---------- INFO: 2021/05/10 08:53:48 vault.go:521: Vault is already Initialized WARNING: 2021/05/10 08:53:48 vault.go:389: Unable to find RoleID. Generating... ERROR: 2021/05/10 08:53:48 auth.go:226: Read from file: open auth/role: no such file or directory ERROR: 2021/05/10 08:53:48 vault.go:405: Creating Policy: Error making API request.URL: PUT http://aaf-sms-db:8200/v1/sys/policy/smsvaultpolicy Code: 503. Errors:* Vault is sealed ERROR: 2021/05/10 08:53:48 vault.go:85: InitRole First Attempt: Unable to create policy for approle creation INFO: 2021/05/10 08:53:48 vault.go:86: InitRole will try again later ERROR: 2021/05/10 08:53:48 auth.go:79: Read PEM File: open /opt/app/osaaf/local/org.onap.aaf-sms.key: no such file or directory ERROR: 2021/05/10 08:53:48 auth.go:61: Read Key File: open /opt/app/osaaf/local/org.onap.aaf-sms.key: no such file or directory ERROR: 2021/05/10 08:53:48 sms.go:73: Get TLS Configuration: open /opt/app/osaaf/local/org.onap.aaf-sms.key: no such file or directory 2021/05/10 08:53:48 open /opt/app/osaaf/local/org.onap.aaf-sms.key: no such file or directory ------- thanks, -RP Mishra On Thu, May 6, 2021 at 4:31 PM Rajendra Prasad Mishra via lists.onap.org<http://lists.onap.org> <rpmishra=aarnanetworks....@lists.onap.org<mailto:aarnanetworks....@lists.onap.org>> wrote: Hi Bhagyalakshmi, I hope I understood your question correctly. I just checked, and it looks like VID is not sharing the DB in guilin. VID uses its own private DB in Guilin. So we should have no issues with that. Now if you want to deploy version 8 of VID on Guilin, just change the image version to 8 and try that. If you copy the VID helm charts from master to guilin it will fail as master has shared DB. As far as "lower_case_table_names" is concerned, it is a DB property and should not impact VID or SO. As per the link on mariadb doc (https://mariadb.com/docs/reference/mdb/system-variables/lower_case_table_names/) "The lower_case_table_names system variable determines whether table names, table aliases, and database names are compared in a case-sensitive manner, and whether tablespace files are stored on disk in a case-sensitive manner.: · When set to 0 (the default on Unix-based systems), table names, table aliases, and database names are compared in a case-sensitive manner. · When set to 1 (the default on Windows), table names and database names are stored in lowercase and compared in a case-insensitive manner." As we see above setting it to 1 will make the comparison "case-insensitive" which means SO or any other utility can pass the name in CAPITAL or small letters. So if I understand correctly, there should be no change in behaviour of SO or VID. Unless of course, SO or other components use two different table/db names differentiated only by their case (e.g. TABLE1 and table1 are two different tables). thanks, -RP On Thu, May 6, 2021 at 3:41 PM Bhagyalakshmi R <rbhagy...@gmail.com<mailto:rbhagy...@gmail.com>> wrote: Hi Rajendra, We are using VID version 8 and other components including mariadb with version 7. When we set this flag "lower_case_table_names=1" in mariadb version 7, all the tables are created in upper case. Now the other pods like SO referring to lower case tablename fails to recognize the tables with upper case. I believe some components being version 7 and other being version 8 will not work. Please let us know if any alternative solution for this issue. Regards, Bhagyalakshmi .R On Fri, Apr 30, 2021 at 7:13 PM Vishal Sharma <vishal.official1...@gmail.com<mailto:vishal.official1...@gmail.com>> wrote: Hi Rajendra, Thanks for the update, we are looking into it now. In master branch this lower case value is coming while not present in Guilin release. Will update you shortly after the changes are made. BR// Vishal Sharma On Fri, 30 Apr 2021, 18:12 Rajendra P Mishra (RP), <rpmis...@aarnanetworks.com<mailto:rpmis...@aarnanetworks.com>> wrote: Hi Vishal, I used to face a similar issue in VID when moving it to common DB. "Table 'vid_openecomp_epsdk.VID_JOB' doesn't exist" The above error is due to VID expecting "case-insensitiveness" in the DB. More info here (https://mariadb.com/docs/reference/mdb/system-variables/lower_case_table_names/) As a part of the change, I moved mariadb to use "lower_case_table_names=1" in the mariadb-galera/values.yaml <https://gerrit.onap.org/r/c/oom/+/113597/15/kubernetes/common/mariadb-galera/values.yaml> This option can be set only at init time of the DB and not at runtime. Can you check if this is set in your DB instance running. Without it VID will not work. The above link has details on how to check it in a running DB (by logging into one of the DB instance pod) In case it is not set, then you need to set it to "1" and re-deploy ONAP. thanks, -RP On Fri, Apr 30, 2021 at 1:48 PM <vishal.official1...@gmail.com<mailto:vishal.official1...@gmail.com>> wrote: We are facing issue when deploying VID component in Guilin release also from Master branch but facing issues, due to this we are totally stuck to run vFW demo. Below the background given: Background: We are setting up the ONAP components (from the Guilin release) on the OKD cluster and able to setup all the components except VID. We tried with various VID releases, but none of them is working for one or another reason. Option1: Tried to setup the VID from the Guilin release 7.0.0, but the vid pod is crashing with below error. Localizing the VID quartz configuration ERROR: Could not process template file /usr/local/tomcat/webapps/vid/WEB-INF/conf/quartz_template.properties into /usr/local/tomcat/webapps/vid/WEB-INF/conf/quartz.properties sed: -e expression #5, char 27: unknown option to `s' [t974240@chdcovh01 /appl/codebase/testrepo/oom/kubernetes]$ Option2: Installed VID from the master branch. Though, Pods are up and running but seeing DB errors in the vid pod logs and VID UI is not coming up due to these errors (Details are available in the ticket). Raised ticket https://jira.onap.org/browse/VID-983<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FVID-983&data=04%7C01%7CVishal.Sharma%40spark.co.nz%7Cc90b499a86ab427ea8d208d90b16b75f%7Cf6b3cec6a8624a409ab400d6e11e6f0f%7C0%7C0%7C637553014520805602%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=r0vpc9o8ejI%2FvcOfUJtiAmekbQsuoxib37M0ffjMETE%3D&reserved=0> but not getting any response. -- [https://docs.google.com/uc?export=download&id=1aZs2CQGQI0WnAobumqXPiXg7bcYvmO9q&revid=0B4K_71eDDWrCcUw1YkxuY1c5cm1sa254M0pqL0hzaXcyK1BZPQ] CRN Top 10 Coolest Edge Computing Startups of 2020<https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-startups-of-2020/2> -- [https://docs.google.com/uc?export=download&id=1aZs2CQGQI0WnAobumqXPiXg7bcYvmO9q&revid=0B4K_71eDDWrCcUw1YkxuY1c5cm1sa254M0pqL0hzaXcyK1BZPQ] CRN Top 10 Coolest Edge Computing Startups of 2020<https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-startups-of-2020/2> -- [https://docs.google.com/uc?export=download&id=1aZs2CQGQI0WnAobumqXPiXg7bcYvmO9q&revid=0B4K_71eDDWrCcUw1YkxuY1c5cm1sa254M0pqL0hzaXcyK1BZPQ] CRN Top 10 Coolest Edge Computing Startups of 2020<https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-startups-of-2020/2> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23210): https://lists.onap.org/g/onap-discuss/message/23210 Mute This Topic: https://lists.onap.org/mt/82476408/21656 Mute #vid:https://lists.onap.org/g/onap-discuss/mutehashtag/vid Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
