Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI
On Fri, Aug 28, 2015 at 6:29 PM, Peter Penchevwrote: > On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev > wrote: >> On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy wrote: >>> Hi Peter, >>> >>> Your log files require downloads. Please fix it such that they can be >>> viewed directly [1] >> >> Hi, and thanks for the fast reply! Yes, I'll try to change the >> webserver's configuration, although the snippet in the FAQ won''t help >> a lot, since it's a lighttpd server, not Apache. I'll get back to you >> when I've figured something out. > > OK, it took some twiddling with the lighttpd config, but it's done - > now files with a .gz extension are served uncompressed in a way that > makes the browser display them and not save them to disk. > > About the rebasing over our local patches: I made the script display > the subject lines and the file lists of the commits on our local > branch (the ones that the source is being rebased onto). Pay no > attention to the several commits to "devstack"; they are mostly > artifacts of our own infrastructure and the setup of the machines, and > in most cases they are no-ops. > > About your question about 3129 and 217802/1 - well, to be fair, this > is not a Cinder patch, so it's kind of expected that you won't find it > in the Cinder commits :) It's a Brick patch and it is indeed listed a > couple of lines down in the os-brick section :) > > So, a couple of examples of our shiny new log setup (well, pretty much > the same as the old boring log setup, but oh well): > > http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3166/ > http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3167/ > http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3168/ Hi, Yesterday I realized that Mike Perez was on vacation; well, is there anybody else who could take a look at our CI's logs and drop a line to the third-party CI team to reenable our Gerrit account? As an additional step of making our CI's patches public, I just submitted https://review.openstack.org/220155/ - "Reintroduce the StorPool driver", and updated https://review.openstack.org/#/c/192639/ - add the os-brick StorPool connector (just for informational purposes). And, yes, I do realize that the Liberty feature freeze is pretty much upon us, but, well, it's been three weeks since the message to third-party-announce that our CI was ready to be reenabled... so would there be any chance for our Cinder driver to be reintroduced? Thanks in advance for any assistance! G'luck, Peter __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI
On 09/03/2015 10:17 AM, Peter Penchev wrote: > On Fri, Aug 28, 2015 at 6:29 PM, Peter Penchev >wrote: >> On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev >> wrote: >>> On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy wrote: Hi Peter, Your log files require downloads. Please fix it such that they can be viewed directly [1] >>> >>> Hi, and thanks for the fast reply! Yes, I'll try to change the >>> webserver's configuration, although the snippet in the FAQ won''t help >>> a lot, since it's a lighttpd server, not Apache. I'll get back to you >>> when I've figured something out. >> >> OK, it took some twiddling with the lighttpd config, but it's done - >> now files with a .gz extension are served uncompressed in a way that >> makes the browser display them and not save them to disk. >> >> About the rebasing over our local patches: I made the script display >> the subject lines and the file lists of the commits on our local >> branch (the ones that the source is being rebased onto). Pay no >> attention to the several commits to "devstack"; they are mostly >> artifacts of our own infrastructure and the setup of the machines, and >> in most cases they are no-ops. >> >> About your question about 3129 and 217802/1 - well, to be fair, this >> is not a Cinder patch, so it's kind of expected that you won't find it >> in the Cinder commits :) It's a Brick patch and it is indeed listed a >> couple of lines down in the os-brick section :) >> >> So, a couple of examples of our shiny new log setup (well, pretty much >> the same as the old boring log setup, but oh well): >> >> http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3166/ >> http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3167/ >> http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3168/ > > Hi, > > Yesterday I realized that Mike Perez was on vacation; well, is there > anybody else who could take a look at our CI's logs and drop a line to > the third-party CI team to reenable our Gerrit account? There is no third party CI team. Disabling and re-enabling CI accounts is the responsibility of the infra team. But you are correct, we are waiting to hear from one of Mike Perez or a designate. And while I'm here a big thank you to Ramy Asselin for all his hard work helping you. Thank you, Anita. > > As an additional step of making our CI's patches public, I just > submitted https://review.openstack.org/220155/ - "Reintroduce the > StorPool driver", and updated https://review.openstack.org/#/c/192639/ > - add the os-brick StorPool connector (just for informational > purposes). And, yes, I do realize that the Liberty feature freeze is > pretty much upon us, but, well, it's been three weeks since the > message to third-party-announce that our CI was ready to be > reenabled... so would there be any chance for our Cinder driver to be > reintroduced? > > Thanks in advance for any assistance! > > G'luck, > Peter > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI
On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev openstack-...@storpool.com wrote: On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy ramy.asse...@hp.com wrote: Hi Peter, Your log files require downloads. Please fix it such that they can be viewed directly [1] Hi, and thanks for the fast reply! Yes, I'll try to change the webserver's configuration, although the snippet in the FAQ won''t help a lot, since it's a lighttpd server, not Apache. I'll get back to you when I've figured something out. OK, it took some twiddling with the lighttpd config, but it's done - now files with a .gz extension are served uncompressed in a way that makes the browser display them and not save them to disk. About the rebasing over our local patches: I made the script display the subject lines and the file lists of the commits on our local branch (the ones that the source is being rebased onto). Pay no attention to the several commits to devstack; they are mostly artifacts of our own infrastructure and the setup of the machines, and in most cases they are no-ops. About your question about 3129 and 217802/1 - well, to be fair, this is not a Cinder patch, so it's kind of expected that you won't find it in the Cinder commits :) It's a Brick patch and it is indeed listed a couple of lines down in the os-brick section :) So, a couple of examples of our shiny new log setup (well, pretty much the same as the old boring log setup, but oh well): http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3166/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3167/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3168/ G'luck, Peter __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [cinder][third-party] StorPool Cinder CI
Hi, Some time ago I sent http://lists.openstack.org/pipermail/third-party-announce/2015-August/000261.html to the third-party-announce list as a reply to a message about the StorPool Cinder third-party CI being disabled. Well, as I wrote in my reply there, I think that we have done what Mike Perez asked us to - reconfigured our CI to run in silent mode and keep it running for a while, updating our local patches to deal with the changes in Cinder, Nova and Brick, and put out the logs so that they're available for public perusal. That message contains links to some CI runs as of the time of its sending, but here are some new ones as of today: http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3129/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3128/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3127/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3126/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3125/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3124/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3123/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3122/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3121/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3120/ So, would that be enough to get our CI system's Gerrit account reenabled, as a first step towards putting the StorPool Cinder driver back in? Of course, if there's anyhing else we should do, just let us know. Once again, thanks to all of you for your work on OpenStack, and thanks to Anita Kuno, Mike Perez, and everyone else for keeping an eye on the third-party CI systems! G'luck, Peter __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI
On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy ramy.asse...@hp.com wrote: Hi Peter, Your log files require downloads. Please fix it such that they can be viewed directly [1] Hi, and thanks for the fast reply! Yes, I'll try to change the webserver's configuration, although the snippet in the FAQ won''t help a lot, since it's a lighttpd server, not Apache. I'll get back to you when I've figured something out. Also, it's not clear where in your scripts you actually pull down the cinder patch. It's in the pre_test_hook, the for loop that rebases cinder, nova, os-brick, etc. onto the storpool-osci branch of our local repo: 2015-08-27 20:18:15.857 | + echo '=== Fetch the StorPool modifications:' 2015-08-27 20:18:15.858 | === Fetch the StorPool modifications: 2015-08-27 20:18:15.859 | + for i in cinder devstack devstack-gate nova os-brick tempest 2015-08-27 20:18:15.860 | + echo '=== - cinder' 2015-08-27 20:18:15.861 | === - cinder 2015-08-27 20:18:15.862 | + cd /opt/stack/new/cinder 2015-08-27 20:18:15.863 | + git remote add osci git+ssh://logarchive@osci-jenkins-master/var/lib/osci/git/cinder/ 2015-08-27 20:18:15.864 | + git fetch osci 2015-08-27 20:18:16.033 | From git+ssh://osci-jenkins-master/var/lib/osci/git/cinder 2015-08-27 20:18:16.034 | * [new branch] master - osci/master 2015-08-27 20:18:16.036 | * [new branch] storpool-osci - osci/storpool-osci [snip] 2015-08-27 20:18:16.046 | + git rebase osci/storpool-osci 2015-08-27 20:18:16.090 | First, rewinding head to replay your work on top of it... 2015-08-27 20:18:16.155 | Applying: Port test_nfs to Python 3 2015-08-27 20:18:16.185 | Applying: Implement function to manage/unmanage snapshots ...and then proceeds to do the same for the rest of the OpenStack projects listed on the third line. G'luck, Peter __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [cinder][third-party] StorPool Cinder CI
Hi Peter, Your log files require downloads. Please fix it such that they can be viewed directly [1] Also, it's not clear where in your scripts you actually pull down the cinder patch. Ramy [1] http://docs.openstack.org/infra/system-config/third_party.html#faq-frequently-asked-questions -Original Message- From: Peter Penchev [mailto:openstack-...@storpool.com] Sent: Thursday, August 27, 2015 1:43 PM To: OpenStack openstack-dev@lists.openstack.org Subject: [openstack-dev] [cinder][third-party] StorPool Cinder CI Hi, Some time ago I sent http://lists.openstack.org/pipermail/third-party-announce/2015-August/000261.html to the third-party-announce list as a reply to a message about the StorPool Cinder third-party CI being disabled. Well, as I wrote in my reply there, I think that we have done what Mike Perez asked us to - reconfigured our CI to run in silent mode and keep it running for a while, updating our local patches to deal with the changes in Cinder, Nova and Brick, and put out the logs so that they're available for public perusal. That message contains links to some CI runs as of the time of its sending, but here are some new ones as of today: http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3129/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3128/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3127/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3126/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3125/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3124/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3123/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3122/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3121/ http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3120/ So, would that be enough to get our CI system's Gerrit account reenabled, as a first step towards putting the StorPool Cinder driver back in? Of course, if there's anyhing else we should do, just let us know. Once again, thanks to all of you for your work on OpenStack, and thanks to Anita Kuno, Mike Perez, and everyone else for keeping an eye on the third-party CI systems! G'luck, Peter __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev