Hi Ajay,
Apologies for hijacking this thread. I was wondering what is the request flow for VID's "browse SDC models". Will it contact openstack / mso/or any other component? I am assuming it will just contact SDC-BE. Is that assumption right? Regards Bharath T ________________________________ From: [email protected] <[email protected]> on behalf of [email protected] <[email protected]> Sent: Monday, June 5, 2017 6:45 PM To: [email protected]; [email protected] Cc: [email protected] Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain Hi Kanagaraj, Check error log. I have simulated same error, kindly check error “Failed to get shared context for usernull” on vid error.log [cid:[email protected]] If you are getting same check your underline openstack, is it working fine. And share the error.log of vm_vid. Regards, Ajay Priyadarshi From: Kanagaraj Manickam [mailto:[email protected]] Sent: 05 June 2017 17:25 To: Arun Arora (c); Ajay Priyadarshi Cc: [email protected] Subject: RE: [onap-discuss] VID VM , MariaDb docker does not remain Hi Arun, I have faced the similar issue and I referred your fix to solve it. Thank you. After this fix, VID started to run. But VID portal reports Error: Failed to get service models from ASDC, (I tried this after distributing a sample VSP) Regards Kanagaraj M *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! *************************************************************************************** From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Arun Arora (c) Sent: Thursday, June 01, 2017 3:24 PM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain Hi Ajay, For me, "1.1.0-SNAPSHOT uses vid_openecomp_ epsdk" is not true. I am using 1.1.0-SNAPSHOT but I had to rename the DB as vid_openecomp. On doing this change my issue was fixed and docker container didn’t stop after that. Thanks, Arun From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Thursday, June 01, 2017 12:51 PM To: Arun Arora (c) <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain Hi Arun, Share the following logs as stated. 1. execute command : docker logs vid-server 2. check for database name in file /opt/vid/lf_config/vid-pre-init.sql vid_openecomp or vid_openecomp_ epsdk 3. artifacts_version : 1.0.0-SNAPSHOT uses vid_openecomp database while artifacts_version: 1.1.0-SNAPSHOT uses vid_openecomp_ epsdk. so cat /opt/config/artifacts_version.txt /opt/config/docker_version.txt /opt/config/gerrit_branch.txt Output should match in line with database used in file /opt/vid/lf_config/vid-pre-init.sql 4. Share the error.log file output. Regards, Ajay Priyadarshi Date: Tue, 30 May 2017 17:57:47 +0200 From: "Josef Reisinger" <[email protected]<mailto:[email protected]>> To: "Arun Arora (c)" <[email protected]<mailto:[email protected]>> Cc: "\[onap-discuss\]" <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain running Message-ID: <ofb6a46ee4.34e290c3-onc1258130.0056c95e-c1258130.0057a...@notes.na.collabserv.com<mailto:ofb6a46ee4.34e290c3-onc1258130.0056c95e-c1258130.0057a...@notes.na.collabserv.com>> Content-Type: text/plain; charset="iso-8859-1" Arun, could your issue be related to the one described here: https://wiki.onap.org/questions/5736012/answers/6586792<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_questions_5736012_answers_6586792&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=8Giyn6_W22qZMzxxH1URjs-7ksqd8XPcszRywiw1XlM&e=>. If yes, could you find a solution there? If not would you mind to record your issue with the VID database in https://wiki.onap.org/questions<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_questions&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=6aLT42m8lQ-v4siCScIVvxMYGvb1JQ52-ohwe_HSQjY&e=> ? I am running two instances of ONAP right now on v. Openstack and ith helped in the first instance. I had some issues with exact the same database today in my second instance and in tried something different to what is provided as a solution in the above mentioned link (to give vidadmin rights to everything), I changed the script in /opt/vid_vm_init.sh and changed the DB name from vid_openecomp_epsdk to vid_openecomp. And VID worked too. Btw, if you want to attach to one of the docker container, vid-mariadb needs to be running. "docker start vid-mariadb " gives you the database container back and you can exec to vid-server or/and vid-mariadb Mit freundlichen Gr??en / Kind regards Josef Reisinger From: "Arun Arora (c)" <[email protected]<mailto:[email protected]>> To: Elhay Efrat <[email protected]<mailto:[email protected]>>, "Lefevre, Catherine" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: "Kapil Gupta \(c\)" <[email protected]<mailto:[email protected]>> Date: 30.05.2017 17:28 Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain running Sent by: [email protected]<mailto:[email protected]> FYI, some info regarding the VID VM and docker. It might be relevant if there is any fix done in the master branch which his not available in the release-1.0.0 branch. root@vm1-vid:/opt/config# cat artifacts_version.txt docker_version.txt gerrit_branch.txt 1.1.0-SNAPSHOT 1.0-STAGING-latest release-1.0.0 Thanks, Arun From: Arun Arora (c) Sent: Tuesday, May 30, 2017 8:48 PM To: Elhay Efrat <[email protected]<mailto:[email protected]>>; Lefevre, Catherine <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Cc: Kapil Gupta (c) <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] VID VM , MariaDb docker does not remain running HI Catherine, Efrat, I am not able to find /opt/app/vid/logs/vid or /usr/local/tomcat/logs/ directories. I am assuming these are in the VID VM and not in the docker container. Also, I am not able to log in the docker container as it is rendered unavailable even when I can see the vid-server container in docker ps list Pls let me know what else can be done to understand the issue symptoms. Thanks, Arun From: Elhay Efrat [mailto:[email protected]] Sent: Monday, May 29, 2017 11:36 PM To: Lefevre, Catherine <[email protected]<mailto:[email protected]>>; Arun Arora (c) < [email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Cc: Kapil Gupta (c) <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] VID VM , MariaDb docker does not remain running Please add also Docker logs {mariadb-docker-id} From: [email protected]<mailto:[email protected]> on behalf of Lefevre, Catherine Sent: Monday, May 29, 2017 5:59:59 PM To: Arun Arora (c); [email protected]<mailto:[email protected]> Cc: Kapil Gupta (c) Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain running Hi Arun, Could you please provide some logs, traces in order to better understand your current MariaDB issue? Logging/Diagnostic Information Application logs: /opt/app/vid/logs/vid audit.log for transaction details application.log for detailed application logs and debugging debug.log for debugging output error.log for exception debugging metrics.log for metrics on transactions Application server logs: /usr/local/tomcat/logs/ localhost_access_log.YYYY-mm-dd.txt contains access log info catalina.2017-02-28.log tomcat information Did you also check the following discussion? https://lists.onap.org/pipermail/onap-discuss/2017-May/000911.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_pipermail_onap-2Ddiscuss_2017-2DMay_000911.html&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=-_o5MkCc0jngHHEWHeWBHdIivw42EzTaDX5BYB45SgI&e=> Best regards Catherine From: [email protected]<mailto:[email protected]> [ mailto:[email protected]] On Behalf Of Arun Arora (c) Sent: Friday, May 26, 2017 2:16 PM To: [email protected]<mailto:[email protected]> Cc: Kapil Gupta (c) <[email protected]<mailto:[email protected]>> Subject: [onap-discuss] VID VM , MariaDb docker does not remain running Hi All, We have deployed ONAP on Vanilla OpenStack Mitaka (On top of CentOS 7). Using the following YAML and env files: https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=V23ql9egYjI-5AQYkeA1-x-J2AdolB0W7JS5rPZIwkE&e=> https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=V23ql9egYjI-5AQYkeA1-x-J2AdolB0W7JS5rPZIwkE&e=> After ONAP stack deployment, Mariadb docker inside VID VM starts but is exiting after sometime. Can anyone provide any pointers on why the mariadb docker stops, or is this the desired behavior? Thanks & Regards, Arun Arora 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=e7Dxd13X711iKpEkws8kh6s71rHRbLwqEDj4vhO2R3M&e=> _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=hqpY8fB9WF1i4qNbf1PTkt6uQLZLEJmDfcIoa0XsUm0&e=> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170530/03c5c646/attachment-0001.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.onap.org_pipermail_onap-2Ddiscuss_attachments_20170530_03c5c646_attachment-2D0001.html&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ&m=Z-TwiDmze5TWYD_jc3pXI7Ac05K3FGPd71ZxWWuOqVY&s=ihENL_-ASR-z9s6XXbebhcWYxBnP6OBNELeOO7fjO8E&e=>> ------------------------------ "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
