Hey Eduard,

We posted our driver cert result by creating a new bugzilla ticket &
tagging that as driver-cert.

https://bugs.launchpad.net/cinder/+bug/1380126



Regards,
Amit
*CloudByte Inc.* <http://www.cloudbyte.com/>

On Thu, Oct 30, 2014 at 5:55 PM, Eduard Matei <
eduard.ma...@cloudfounders.com> wrote:

> Hi Mike,
> I saw your comment on my review, but i need some more info regarding
> "Your driver passes the cert test and the results are posted."
> I assume you mean running cinder_driver_cert.sh - this is already passing
> - but how do i get the results posted, and where?
> I've been looking through some documentation and couldn't find a
> definitive answer.
>
> Thanks
> Eduard
>
>
> On Thu, Oct 30, 2014 at 9:03 AM, Mike Perez <thin...@gmail.com> wrote:
>
>> On 19:41 Thu 04 Sep     , Duncan Thomas wrote:
>> > Hi
>> >
>> > during this week's cinder weekly meeting [1], we discussed plans for
>> > Kilo, a discussion that started at the mid-cycle meetup [2]. The
>> > outcome is that we (the cinder core team and extended community) want
>> > to focus on stability and code clean-up in the Kilo release, and
>> > paying off some of the technical debt we've built up over the past
>> > couple of years [3]. In order to facilitate this, for the Kilo cycle:
>> >
>> > 1. New drivers must be submitted before K1 in order to be considered.
>> > Any driver submitted after this date will be deferred until the L
>> > cycle. We encourage submitters to get in early, even if you make K1
>> > there is no guarantee of getting enough reviewer attention to get
>> > merged.
>> >
>> > 2. New features are limited and ideally merged by K2.
>> >
>> > 3. K3 is dedicated to stability and bug fixing. (Much of this work
>> > will happen before K3, but K3 is dedicated to testing and reviewing of
>> > it, in preference to anything else. Any driver enhancements required
>> > to support pre-existing features will also be considered, but please
>> > get them in as early as possible).
>> >
>> > 4. PoC required before the summit, for any summit session related to
>> > new features.
>> >
>> > 5. There will be a continuing drive for 3rd party CI of every driver
>> > in cinder during the Kilo cycle.
>> >
>> >
>> > I'll repost these guidelines and any follow-up clarifications shortly
>> > before the summit. Comments / feedback welcome.
>> >
>> > [1]
>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-09-03-16.01.log.html
>> >
>> > [2] https://etherpad.openstack.org/p/cinder-meetup-summer-2014
>> >
>> > [3] https://etherpad.openstack.org/p/cinder-kilo-stabilisation-work
>>
>>
>> Just reiterating points here. From the September 23rd Cinder meeting [1],
>> and
>> verified in the Oct 29th Cinder meeting [2], the community has agreed
>> that new
>> drivers must be submitted *before* K-1 ends.
>>
>> K-1 is expected to end on 12/18, according to the launchpad page [3].
>>
>> Submitted and qualified for merge means:
>> * Your blueprint for your driver was submitted and approved before 11/15.
>> * Your driver code is posted to gerrit.
>> * Your driver passes the cert test and the results are posted. [4]
>> * Your driver fulfills minimum features. [5]
>> * You have spoken to Duncan (DuncanT- on #openstack-cinder) about your
>> third
>>   party ci. [6]
>>
>> To be clear:
>> * Your driver submission must meet *all* the items before the end of k-1.
>> * If your driver is submitted *LATE* in k-1, and meets *all* the items
>> above,
>>   but isn't merged, it will be still be considered for merge in k-2 or
>> k-3.
>>   However, expect low priority in reviews and not guaranteed for merge in
>> Kilo.
>> * If your driver is submitted after k-1, expect me to reference this
>> email and
>>   will request the driver to be submitted in the L release.
>> * This does not include backup drivers.
>>
>> And yes, the Cinder wiki will be updated with this information.
>>
>> [1] -
>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-09-03-16.01.log.html
>> [2] -
>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-29-16.00.log.html
>> [3] - https://launchpad.net/cinder/+milestone/kilo-1
>> [4] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
>> [5] -
>> http://docs.openstack.org/developer/cinder/devref/drivers.html#minimum-features
>> [6] -
>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond
>>
>> --
>> Mike Perez
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
>
> *Eduard Biceri Matei, Senior Software Developer*
> www.cloudfounders.com
>  | eduard.ma...@cloudfounders.com
>
>
>
> *CloudFounders, The Private Cloud Software Company*
>
> Disclaimer:
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to whom they are addressed.
> If you are not the named addressee or an employee or agent responsible for 
> delivering this message to the named addressee, you are hereby notified that 
> you are not authorized to read, print, retain, copy or disseminate this 
> message or any part of it. If you have received this email in error we 
> request you to notify us by reply e-mail and to delete all electronic files 
> of the message. If you are not the intended recipient you are notified that 
> disclosing, copying, distributing or taking any action in reliance on the 
> contents of this information is strictly prohibited.
> E-mail transmission cannot be guaranteed to be secure or error free as 
> information could be intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete, or contain viruses. The sender therefore does not accept 
> liability for any errors or omissions in the content of this message, and 
> shall have no liability for any loss or damage suffered by the user, which 
> arise as a result of e-mail transmission.
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to