[openstack-dev] [Cinder] Request for J3 Feature Freeze Exception
Hello dear cinder stackers, Recently, the feature freeze was acted for J3, while I was frantically trying to tighten the feedback loop on the driver I was working on for my company, Scality, in hope of getting merged for J3. I felt I was really close, a lot of reviews coming in the last few days, and dealing with the timelag for the feedback, as I am under the impression that a lot of the cinder team is in the US (I am in west europe) So I asked Duncan what could be done, learned about the FFE, and I am now humbly asking you guys to give us a last chance to get in for Juno. I was told that if it was possible the last delay would be next week, and believe me, we're doing everything we can on our side to be able to meet that. I had a patch ready to go in answer to the recent reviews I got, but wanted to get driver cert log okay before I put if up for reviews. The situation being what it is, I put that up, and am working on the driver cert, solving last-minute issues. I'll understand if that is not possible, and I thank you for your understanding ! -- David Pineau, Developer at Scality IRC handle: joa Gerrit handle: Joachim ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
Well, I could make it test every patchset, but then I have to look into how to limit at one build per time + queue the other builds. (didn't try that yet) Anyways, I just got my new CI machine so I'll be able to finalize the CI system relatively soon. 2014-08-14 1:01 GMT+02:00 Jeremy Stanley : > On 2014-08-13 16:30:23 + (+), Asselin, Ramy wrote: >> I remember infra team objected to the nightly builds. They wanted >> reports on every patch set in order to report to gerrit. > [...] > > I can't imagine, nor do I recall, objecting to such an idea. The > question is merely where you expect to publish the results, and how > you deal with the fact that you're testing changes which have > already merged rather than getting in front of the reviewers on > proposed changes. I don't personally have any specific desire for > third-party CI systems to report on changes in Gerrit, but > individual projects supporting your drivers/features/whatever might. > -- > Jeremy Stanley > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- David Pineau, Developer R&D at Scality ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems
Hello, I have currently setup the Scality CI not to report (mostly because it isn't fully functionnal yet, as the machine it runs on turns out to be undersized and thus the tests fails on some timeout), partly because it's currently a nightly build. I have no way of testing multiple patchsets at the same time so it is easier this way. How do you plan to "Officialize" the different 3rd party CIs ? I remember that the cinder meeting about that in the Atlanta Summit concluded that a nightly build would be enough, but such build cannot really report on gerrit. David Pineau gerrit: Joachim IRC#freenode: joa 2014-08-13 2:28 GMT+02:00 Asselin, Ramy : > I forked jaypipe’s repos & working on extending it to support nodepool, log > server, etc. > > Still WIP but generally working. > > > > If you need help, ping me on IRC #openstack-cinder (asselin) > > > > Ramy > > > > From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] > Sent: Monday, August 11, 2014 11:33 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [OpenStack-Dev] [Cinder] 3'rd party CI systems > > > > On 12 August 2014 07:26, Amit Das wrote: > > I would like some guidance in this regards in form of some links, wiki pages > etc. > > > > I am currently gathering the "driver cert test results" i.e. tempest tests > from devstack in our environment & CI setup would be my next step. > > > > This should get you started: > > http://ci.openstack.org/third_party.html > > > > Then Jay Pipes' excellent two part series will help you with the details of > getting it done: > > http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/ > > http://www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/ > > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- David Pineau, Developer R&D at Scality ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
