Open Stack

On Fri, Aug 28, 2015 at 6:29 PM, Peter Penchev
<openstack-dev at storpool.com> wrote:
> On Fri, Aug 28, 2015 at 1:03 AM, Peter Penchev
> <openstack-dev at storpool.com> wrote:
>> On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy <ramy.asselin at 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/

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