Re: [Engine-devel] Changes in DB scripts that need your attension
- Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 9:43:00 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:58:26 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:53:11 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:44:06 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:26:44 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension Hi, - Original Message - From: Eli Mesika emes...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:19:43 PM Subject: [Engine-devel] Changes in DB scripts that need your attension Hi As part of solving https://bugzilla.redhat.com/show_bug.cgi?id=947344 I am doing the following changes: 1) Create all *.md5 files in /tmp/db Please use mkstemp or equivalent to create unique temp directory. OK, will use mktemp -d for that 2) Create db log files by default under /var/log/ovirt-engine/db Please allow to override log location and/or output logs to stdout. This will make it easier to run it within installer so that the log will be available at installer log. All scripts supports the -l LOGFILE flag 3) Do not automatically create a *.schema file that represent the up-to-date schema (after all upgrades took place) A new utility script exportDbSchema.sh will be available for that (manual only, no auto-generation schema) In order that DB scripts in development environment will keep working, please do sudo mkdir -p /var/log/ovirt-engine/db sudo chmod 777 /var/log/ovirt-engine/db 777 access permission is not something that should exist in system anywhere, well apart of /tmp and /tmp is marked using 't' attribute. Missed that in my prev reply anyway , do whatever is needed so that the user that access the scripts in dbscripts has r/w/ permisssions on /var/log/ovirt-engine/db since this is only for development, each developer will decide how to do that OK... I will check this with the new development environment[1] [1] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer Hi, Where can I find the patch? I cannot see this in gerrit nor reference in bug#947344 This was pushed only today :http://gerrit.ovirt.org/#/c/14090/ Alon ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] Changes in DB scripts that need your attension
Hi As part of solving https://bugzilla.redhat.com/show_bug.cgi?id=947344 I am doing the following changes: 1) Create all *.md5 files in /tmp/db 2) Create db log files by default under /var/log/ovirt-engine/db 3) Do not automatically create a *.schema file that represent the up-to-date schema (after all upgrades took place) A new utility script exportDbSchema.sh will be available for that (manual only, no auto-generation schema) In order that DB scripts in development environment will keep working, please do sudo mkdir -p /var/log/ovirt-engine/db sudo chmod 777 /var/log/ovirt-engine/db If you are getting Permission Denied errors while running the scripts it means that you didn't run the 2 commands above. If you have any comments/suggestions to this solution, please respond before this patch is merged, I will wait with this change to next SUN , APR 21 2013 Best Regards Eli ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Changes in DB scripts that need your attension
- Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:26:44 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension Hi, - Original Message - From: Eli Mesika emes...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:19:43 PM Subject: [Engine-devel] Changes in DB scripts that need your attension Hi As part of solving https://bugzilla.redhat.com/show_bug.cgi?id=947344 I am doing the following changes: 1) Create all *.md5 files in /tmp/db Please use mkstemp or equivalent to create unique temp directory. OK, will use mktemp -d for that 2) Create db log files by default under /var/log/ovirt-engine/db Please allow to override log location and/or output logs to stdout. This will make it easier to run it within installer so that the log will be available at installer log. All scripts supports the -l LOGFILE flag 3) Do not automatically create a *.schema file that represent the up-to-date schema (after all upgrades took place) A new utility script exportDbSchema.sh will be available for that (manual only, no auto-generation schema) In order that DB scripts in development environment will keep working, please do sudo mkdir -p /var/log/ovirt-engine/db sudo chmod 777 /var/log/ovirt-engine/db 777 access permission is not something that should exist in system anywhere, well apart of /tmp and /tmp is marked using 't' attribute. Regards, Alon ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Changes in DB scripts that need your attension
- Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:44:06 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:26:44 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension Hi, - Original Message - From: Eli Mesika emes...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:19:43 PM Subject: [Engine-devel] Changes in DB scripts that need your attension Hi As part of solving https://bugzilla.redhat.com/show_bug.cgi?id=947344 I am doing the following changes: 1) Create all *.md5 files in /tmp/db Please use mkstemp or equivalent to create unique temp directory. OK, will use mktemp -d for that 2) Create db log files by default under /var/log/ovirt-engine/db Please allow to override log location and/or output logs to stdout. This will make it easier to run it within installer so that the log will be available at installer log. All scripts supports the -l LOGFILE flag 3) Do not automatically create a *.schema file that represent the up-to-date schema (after all upgrades took place) A new utility script exportDbSchema.sh will be available for that (manual only, no auto-generation schema) In order that DB scripts in development environment will keep working, please do sudo mkdir -p /var/log/ovirt-engine/db sudo chmod 777 /var/log/ovirt-engine/db 777 access permission is not something that should exist in system anywhere, well apart of /tmp and /tmp is marked using 't' attribute. Missed that in my prev reply anyway , do whatever is needed so that the user that access the scripts in dbscripts has r/w/ permisssions on /var/log/ovirt-engine/db since this is only for development, each developer will decide how to do that Regards, Alon ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Changes in DB scripts that need your attension
- Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:53:11 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:44:06 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:26:44 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension Hi, - Original Message - From: Eli Mesika emes...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:19:43 PM Subject: [Engine-devel] Changes in DB scripts that need your attension Hi As part of solving https://bugzilla.redhat.com/show_bug.cgi?id=947344 I am doing the following changes: 1) Create all *.md5 files in /tmp/db Please use mkstemp or equivalent to create unique temp directory. OK, will use mktemp -d for that 2) Create db log files by default under /var/log/ovirt-engine/db Please allow to override log location and/or output logs to stdout. This will make it easier to run it within installer so that the log will be available at installer log. All scripts supports the -l LOGFILE flag 3) Do not automatically create a *.schema file that represent the up-to-date schema (after all upgrades took place) A new utility script exportDbSchema.sh will be available for that (manual only, no auto-generation schema) In order that DB scripts in development environment will keep working, please do sudo mkdir -p /var/log/ovirt-engine/db sudo chmod 777 /var/log/ovirt-engine/db 777 access permission is not something that should exist in system anywhere, well apart of /tmp and /tmp is marked using 't' attribute. Missed that in my prev reply anyway , do whatever is needed so that the user that access the scripts in dbscripts has r/w/ permisssions on /var/log/ovirt-engine/db since this is only for development, each developer will decide how to do that OK... I will check this with the new development environment[1] [1] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer Regards, Alon ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Changes in DB scripts that need your attension
- Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:58:26 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:53:11 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Eli Mesika emes...@redhat.com To: Alon Bar-Lev alo...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:44:06 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension - Original Message - From: Alon Bar-Lev alo...@redhat.com To: Eli Mesika emes...@redhat.com Cc: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:26:44 PM Subject: Re: [Engine-devel] Changes in DB scripts that need your attension Hi, - Original Message - From: Eli Mesika emes...@redhat.com To: engine-devel engine-devel@ovirt.org Sent: Thursday, April 18, 2013 12:19:43 PM Subject: [Engine-devel] Changes in DB scripts that need your attension Hi As part of solving https://bugzilla.redhat.com/show_bug.cgi?id=947344 I am doing the following changes: 1) Create all *.md5 files in /tmp/db Please use mkstemp or equivalent to create unique temp directory. OK, will use mktemp -d for that 2) Create db log files by default under /var/log/ovirt-engine/db Please allow to override log location and/or output logs to stdout. This will make it easier to run it within installer so that the log will be available at installer log. All scripts supports the -l LOGFILE flag 3) Do not automatically create a *.schema file that represent the up-to-date schema (after all upgrades took place) A new utility script exportDbSchema.sh will be available for that (manual only, no auto-generation schema) In order that DB scripts in development environment will keep working, please do sudo mkdir -p /var/log/ovirt-engine/db sudo chmod 777 /var/log/ovirt-engine/db 777 access permission is not something that should exist in system anywhere, well apart of /tmp and /tmp is marked using 't' attribute. Missed that in my prev reply anyway , do whatever is needed so that the user that access the scripts in dbscripts has r/w/ permisssions on /var/log/ovirt-engine/db since this is only for development, each developer will decide how to do that OK... I will check this with the new development environment[1] [1] https://github.com/alonbl/ovirt-engine/blob/otopi/README.developer Hi, Where can I find the patch? I cannot see this in gerrit nor reference in bug#947344 Alon ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
