Re: [openstack-dev] [Cinder] Cutoff deadlines for cinder drivers

[Jay Bryant]

Mike,

Thanks for the diligent efforts to get the word out!

Jay
On Jan 20, 2015 12:30 PM, "Mike Perez"  wrote:

> On 13:53 Tue 20 Jan , Erlon Cruz wrote:
> > Thanks Deepak!
> >
> >
> > Mike is also sending the announce to the vendors in the mail accounts
> > listed in the CI Status page[1].
> >
> > [1] https://wiki.openstack.org/wiki/Cinder/third-party-ci-status
>
> I've actually gone through each volume driver file and emailed whoever
> mostly
> appeared in git blame, as well as whoever appeared recently in commits with
> an obvious company email address. This has been cross checked with the
> proposed
> maintainers file [1].
>
> --
> Mike Perez
>
> [1] - https://review.openstack.org/#/c/116887/
>
> __
> 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] Cutoff deadlines for cinder drivers

[Mike Perez]

On 13:53 Tue 20 Jan , Erlon Cruz wrote:
> Thanks Deepak!
> 
> 
> Mike is also sending the announce to the vendors in the mail accounts
> listed in the CI Status page[1].
> 
> [1] https://wiki.openstack.org/wiki/Cinder/third-party-ci-status

I've actually gone through each volume driver file and emailed whoever mostly
appeared in git blame, as well as whoever appeared recently in commits with
an obvious company email address. This has been cross checked with the proposed
maintainers file [1].

-- 
Mike Perez

[1] - https://review.openstack.org/#/c/116887/

__
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] Cutoff deadlines for cinder drivers

[Erlon Cruz]

Thanks Deepak!


Mike is also sending the announce to the vendors in the mail accounts
listed in the CI Status page[1].

[1] https://wiki.openstack.org/wiki/Cinder/third-party-ci-status

On Tue, Jan 20, 2015 at 6:47 AM, Deepak Shetty  wrote:

> Yuck ! its Mar. 19, 2015 (bad copy paste before)
>
> On Tue, Jan 20, 2015 at 12:16 PM, Deepak Shetty 
> wrote:
>
>> Just so that people following this thread know about the final decision,
>> Per
>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
>> the deadline for CI is extended to Mar. 3, 2015 for all volume drivers.
>>
>> 
>> Deadlines
>>
>> All volume drivers
>> 
>> need to have a CI by end of* K-3, March 19th 2015*.* Failure will result
>> in removal in the Kilo release.* Discussion regarding this was in the
>> #openstack-meeting IRC room during the Cinder meeting. Read discussion
>> logs
>> 
>>
>> 
>>
>> On Tue, Jan 13, 2015 at 3:55 AM, Mike Perez  wrote:
>>
>>> On 09:03 Mon 12 Jan , Erlon Cruz wrote:
>>> > Hi guys,
>>> >
>>> > Thanks for answering my questions. I have 2 points:
>>> >
>>> > 1 - This (remove drivers without CI) is a way impacting change to be
>>> > implemented without exhausting notification and discussion on the
>>> mailing
>>> > list. I myself was in the meeting but this decision wasn't crystal
>>> clear.
>>> > There must be other driver maintainers completely unaware of this.
>>>
>>> I agree that the mailing list has not been exhausted, however, just
>>> reaching
>>> out to the mailing list is not good enough. My instructions back in
>>> November
>>> 19th [1][2] were that we need to email individual maintainers and the
>>> openstack-dev list. That was not done. As far as I'm concerned, we can't
>>> stick
>>> to the current deadline for existing drivers. I will bring this up in
>>> the next
>>> Cinder meeting.
>>>
>>> > 2 - Build a CI infrastructure and have people to maintain a the CI for
>>> a
>>> > new driver in a 5 weeks frame. Not all companies has the knowledge and
>>> > resources necessary to this in such sort period. We should consider a
>>> grace
>>> > release period, i.e. drivers entering on K, have until L to implement
>>> > theirs CIs.
>>>
>>> New driver maintainers have until March 19th. [3] That's around 17 weeks
>>> since
>>> we discussed this in November [2]. This is part the documentation for
>>> how to
>>> contribute a driver [4], which links to the third party requirement
>>> deadline
>>> [3].
>>>
>>> [1] -
>>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
>>> [2] -
>>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34
>>> [3] -
>>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
>>> [4] - https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
>>>
>>> --
>>> Mike Perez
>>>
>>>
>>> __
>>> 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
>
>
__
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] Cutoff deadlines for cinder drivers

[Deepak Shetty]

Yuck ! its Mar. 19, 2015 (bad copy paste before)

On Tue, Jan 20, 2015 at 12:16 PM, Deepak Shetty  wrote:

> Just so that people following this thread know about the final decision,
> Per
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
> the deadline for CI is extended to Mar. 3, 2015 for all volume drivers.
>
> 
> Deadlines
>
> All volume drivers
> 
> need to have a CI by end of* K-3, March 19th 2015*.* Failure will result
> in removal in the Kilo release.* Discussion regarding this was in the
> #openstack-meeting IRC room during the Cinder meeting. Read discussion
> logs
> 
>
> 
>
> On Tue, Jan 13, 2015 at 3:55 AM, Mike Perez  wrote:
>
>> On 09:03 Mon 12 Jan , Erlon Cruz wrote:
>> > Hi guys,
>> >
>> > Thanks for answering my questions. I have 2 points:
>> >
>> > 1 - This (remove drivers without CI) is a way impacting change to be
>> > implemented without exhausting notification and discussion on the
>> mailing
>> > list. I myself was in the meeting but this decision wasn't crystal
>> clear.
>> > There must be other driver maintainers completely unaware of this.
>>
>> I agree that the mailing list has not been exhausted, however, just
>> reaching
>> out to the mailing list is not good enough. My instructions back in
>> November
>> 19th [1][2] were that we need to email individual maintainers and the
>> openstack-dev list. That was not done. As far as I'm concerned, we can't
>> stick
>> to the current deadline for existing drivers. I will bring this up in the
>> next
>> Cinder meeting.
>>
>> > 2 - Build a CI infrastructure and have people to maintain a the CI for a
>> > new driver in a 5 weeks frame. Not all companies has the knowledge and
>> > resources necessary to this in such sort period. We should consider a
>> grace
>> > release period, i.e. drivers entering on K, have until L to implement
>> > theirs CIs.
>>
>> New driver maintainers have until March 19th. [3] That's around 17 weeks
>> since
>> we discussed this in November [2]. This is part the documentation for how
>> to
>> contribute a driver [4], which links to the third party requirement
>> deadline
>> [3].
>>
>> [1] -
>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
>> [2] -
>> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34
>> [3] -
>> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
>> [4] - https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
>>
>> --
>> Mike Perez
>>
>> __
>> 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] Cutoff deadlines for cinder drivers

[Deepak Shetty]

Just so that people following this thread know about the final decision,
Per https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
the deadline for CI is extended to Mar. 3, 2015 for all volume drivers.


Deadlines

All volume drivers

need to have a CI by end of* K-3, March 19th 2015*.* Failure will result in
removal in the Kilo release.* Discussion regarding this was in the
#openstack-meeting IRC room during the Cinder meeting. Read discussion logs




On Tue, Jan 13, 2015 at 3:55 AM, Mike Perez  wrote:

> On 09:03 Mon 12 Jan , Erlon Cruz wrote:
> > Hi guys,
> >
> > Thanks for answering my questions. I have 2 points:
> >
> > 1 - This (remove drivers without CI) is a way impacting change to be
> > implemented without exhausting notification and discussion on the mailing
> > list. I myself was in the meeting but this decision wasn't crystal clear.
> > There must be other driver maintainers completely unaware of this.
>
> I agree that the mailing list has not been exhausted, however, just
> reaching
> out to the mailing list is not good enough. My instructions back in
> November
> 19th [1][2] were that we need to email individual maintainers and the
> openstack-dev list. That was not done. As far as I'm concerned, we can't
> stick
> to the current deadline for existing drivers. I will bring this up in the
> next
> Cinder meeting.
>
> > 2 - Build a CI infrastructure and have people to maintain a the CI for a
> > new driver in a 5 weeks frame. Not all companies has the knowledge and
> > resources necessary to this in such sort period. We should consider a
> grace
> > release period, i.e. drivers entering on K, have until L to implement
> > theirs CIs.
>
> New driver maintainers have until March 19th. [3] That's around 17 weeks
> since
> we discussed this in November [2]. This is part the documentation for how
> to
> contribute a driver [4], which links to the third party requirement
> deadline
> [3].
>
> [1] -
> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
> [2] -
> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34
> [3] -
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
> [4] - https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
>
> --
> Mike Perez
>
> __
> 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] Cutoff deadlines for cinder drivers

[Mike Perez]

On 09:03 Mon 12 Jan , Erlon Cruz wrote:
> Hi guys,
> 
> Thanks for answering my questions. I have 2 points:
> 
> 1 - This (remove drivers without CI) is a way impacting change to be
> implemented without exhausting notification and discussion on the mailing
> list. I myself was in the meeting but this decision wasn't crystal clear.
> There must be other driver maintainers completely unaware of this.

I agree that the mailing list has not been exhausted, however, just reaching
out to the mailing list is not good enough. My instructions back in November
19th [1][2] were that we need to email individual maintainers and the
openstack-dev list. That was not done. As far as I'm concerned, we can't stick
to the current deadline for existing drivers. I will bring this up in the next
Cinder meeting.

> 2 - Build a CI infrastructure and have people to maintain a the CI for a
> new driver in a 5 weeks frame. Not all companies has the knowledge and
> resources necessary to this in such sort period. We should consider a grace
> release period, i.e. drivers entering on K, have until L to implement
> theirs CIs.

New driver maintainers have until March 19th. [3] That's around 17 weeks since
we discussed this in November [2]. This is part the documentation for how to
contribute a driver [4], which links to the third party requirement deadline
[3].

[1] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
[2] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34
[3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
[4] - https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver

-- 
Mike Perez

__
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] Cutoff deadlines for cinder drivers

[Erlon Cruz]

Hi guys,

Thanks for answering my questions. I have 2 points:

1 - This (remove drivers without CI) is a way impacting change to be
implemented without exhausting notification and discussion on the mailing
list. I myself was in the meeting but this decision wasn't crystal clear.
There must be other driver maintainers completely unaware of this.

2 - Build a CI infrastructure and have people to maintain a the CI for a
new driver in a 5 weeks frame. Not all companies has the knowledge and
resources necessary to this in such sort period. We should consider a grace
release period, i.e. drivers entering on K, have until L to implement
theirs CIs.

On Mon, Jan 12, 2015 at 4:07 AM, Asselin, Ramy  wrote:

> Feel free to join any of the 3rd party 'mentoring' meetings on IRC
> Freenode #openstack-meeting to help get started, work through issues, etc.
>
> "Third Party meeting for all aspects of Third Party needs: Mondays at 1500
> UTC and Tuesdays at 0800 UTC. Everyone interested in any aspect Third Party
> process is encouraged to attend." [1]
>
> [1] https://wiki.openstack.org/wiki/Meetings/ThirdParty
>
> Ramy
>
> -Original Message-
> From: Mike Perez [mailto:thin...@gmail.com]
> Sent: Sunday, January 11, 2015 6:53 PM
> To: jsbry...@electronicjungle.net; OpenStack Development Mailing List
> (not for usage questions)
> Subject: Re: [openstack-dev] [Cinder] Cutoff deadlines for cinder drivers
>
> On 21:00 Sat 10 Jan , Jay S. Bryant wrote:
> > I think what we discussed was that existing drivers were supposed to
> > have something working by the end of k-2, or at least have something
> > close to working.
> >
> > For new drivers they had to have 3rd party CI working by the end of Kilo.
> >
> > Duncan, correct me if I am wrong.
> >
> > Jay
> > On 01/10/2015 04:52 PM, Mike Perez wrote:
> > >On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:
> > >>Hi Erlon,
> > >>
> > >>We've got a thread mailing-list [1] for it and some details in wiki
> [2].
> > >>Anyway, need to get confirmation from our core devs and/or Mike.
> > >>
> > >>[1]
> > >>http://lists.openstack.org/pipermail/openstack-dev/2014-October/0495
> > >>12.html
> > >>[2]
> > >>https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testi
> > >>ng_requirements_for_Kilo_release_and_beyond
> > >>
> > >>Regards,
> > >>Ivan Kolodyazhny
> > >>
> > >>On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz 
> wrote:
> > >>
> > >>>Hi all, hi cinder core devs,
> > >>>
> > >>>I have read on IRC discussions about a deadline for drivers vendors
> > >>>to have their CI running and voting until kilo-2, but I didn't find
> > >>>any post on this list to confirm this. Can anyone confirm this?
> > >>>
> > >>>Thanks,
> > >>>Erlon
> > >We did discuss and agree in the Cinder meeting that the deadline
> > >would be k-2, but I don't think anyone reached out to the driver
> > >maintainers about the deadline. Duncan had this action item [1],
> perhaps he can speak more about it.
> > >
> > >[1] -
> > >http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19
> > >-16.00.html
> > >
>
> That is correct [1]. However, I don't think there was any warning given to
> existing drivers [2]. If Duncan can confirm this is the case, I would
> recommend fair warning go out for the end of Kilo for existing drivers as
> well.
>
> [1] -
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
> [2] -
> http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
>
> --
> Mike Perez
>
> __
> 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
>
__
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] Cutoff deadlines for cinder drivers

[Asselin, Ramy]

Feel free to join any of the 3rd party 'mentoring' meetings on IRC Freenode 
#openstack-meeting to help get started, work through issues, etc. 

"Third Party meeting for all aspects of Third Party needs: Mondays at 1500 UTC 
and Tuesdays at 0800 UTC. Everyone interested in any aspect Third Party process 
is encouraged to attend." [1]

[1] https://wiki.openstack.org/wiki/Meetings/ThirdParty

Ramy

-Original Message-
From: Mike Perez [mailto:thin...@gmail.com] 
Sent: Sunday, January 11, 2015 6:53 PM
To: jsbry...@electronicjungle.net; OpenStack Development Mailing List (not for 
usage questions)
Subject: Re: [openstack-dev] [Cinder] Cutoff deadlines for cinder drivers

On 21:00 Sat 10 Jan , Jay S. Bryant wrote:
> I think what we discussed was that existing drivers were supposed to 
> have something working by the end of k-2, or at least have something 
> close to working.
> 
> For new drivers they had to have 3rd party CI working by the end of Kilo.
> 
> Duncan, correct me if I am wrong.
> 
> Jay
> On 01/10/2015 04:52 PM, Mike Perez wrote:
> >On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:
> >>Hi Erlon,
> >>
> >>We've got a thread mailing-list [1] for it and some details in wiki [2].
> >>Anyway, need to get confirmation from our core devs and/or Mike.
> >>
> >>[1]
> >>http://lists.openstack.org/pipermail/openstack-dev/2014-October/0495
> >>12.html
> >>[2]
> >>https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testi
> >>ng_requirements_for_Kilo_release_and_beyond
> >>
> >>Regards,
> >>Ivan Kolodyazhny
> >>
> >>On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz  wrote:
> >>
> >>>Hi all, hi cinder core devs,
> >>>
> >>>I have read on IRC discussions about a deadline for drivers vendors 
> >>>to have their CI running and voting until kilo-2, but I didn't find 
> >>>any post on this list to confirm this. Can anyone confirm this?
> >>>
> >>>Thanks,
> >>>Erlon
> >We did discuss and agree in the Cinder meeting that the deadline 
> >would be k-2, but I don't think anyone reached out to the driver 
> >maintainers about the deadline. Duncan had this action item [1], perhaps he 
> >can speak more about it.
> >
> >[1] - 
> >http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19
> >-16.00.html
> >

That is correct [1]. However, I don't think there was any warning given to 
existing drivers [2]. If Duncan can confirm this is the case, I would recommend 
fair warning go out for the end of Kilo for existing drivers as well.

[1] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
[2] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html

--
Mike Perez

__
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] Cutoff deadlines for cinder drivers

[Mike Perez]

On 21:00 Sat 10 Jan , Jay S. Bryant wrote:
> I think what we discussed was that existing drivers were supposed to
> have something working by the end of k-2, or at least have something
> close to working.
> 
> For new drivers they had to have 3rd party CI working by the end of Kilo.
> 
> Duncan, correct me if I am wrong.
> 
> Jay
> On 01/10/2015 04:52 PM, Mike Perez wrote:
> >On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:
> >>Hi Erlon,
> >>
> >>We've got a thread mailing-list [1] for it and some details in wiki [2].
> >>Anyway, need to get confirmation from our core devs and/or Mike.
> >>
> >>[1]
> >>http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
> >>[2]
> >>https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond
> >>
> >>Regards,
> >>Ivan Kolodyazhny
> >>
> >>On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz  wrote:
> >>
> >>>Hi all, hi cinder core devs,
> >>>
> >>>I have read on IRC discussions about a deadline for drivers vendors to
> >>>have their CI running and voting until kilo-2, but I didn't find any post
> >>>on this list to confirm this. Can anyone confirm this?
> >>>
> >>>Thanks,
> >>>Erlon
> >We did discuss and agree in the Cinder meeting that the deadline would be 
> >k-2,
> >but I don't think anyone reached out to the driver maintainers about the
> >deadline. Duncan had this action item [1], perhaps he can speak more about 
> >it.
> >
> >[1] - 
> >http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html
> >

That is correct [1]. However, I don't think there was any warning given to
existing drivers [2]. If Duncan can confirm this is the case, I would recommend
fair warning go out for the end of Kilo for existing drivers as well.

[1] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
[2] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html

-- 
Mike Perez

__
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] Cutoff deadlines for cinder drivers

[Jay S. Bryant]

I think what we discussed was that existing drivers were supposed to 
have something working by the end of k-2, or at least have something 
close to working.


For new drivers they had to have 3rd party CI working by the end of Kilo.

Duncan, correct me if I am wrong.

Jay
On 01/10/2015 04:52 PM, Mike Perez wrote:

On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:

Hi Erlon,

We've got a thread mailing-list [1] for it and some details in wiki [2].
Anyway, need to get confirmation from our core devs and/or Mike.

[1]
http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
[2]
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond

Regards,
Ivan Kolodyazhny

On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz  wrote:


Hi all, hi cinder core devs,

I have read on IRC discussions about a deadline for drivers vendors to
have their CI running and voting until kilo-2, but I didn't find any post
on this list to confirm this. Can anyone confirm this?

Thanks,
Erlon

We did discuss and agree in the Cinder meeting that the deadline would be k-2,
but I don't think anyone reached out to the driver maintainers about the
deadline. Duncan had this action item [1], perhaps he can speak more about it.

[1] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html




__
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] Cutoff deadlines for cinder drivers

[Mike Perez]

On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:
> Hi Erlon,
> 
> We've got a thread mailing-list [1] for it and some details in wiki [2].
> Anyway, need to get confirmation from our core devs and/or Mike.
> 
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
> [2]
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond
> 
> Regards,
> Ivan Kolodyazhny
> 
> On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz  wrote:
> 
> > Hi all, hi cinder core devs,
> >
> > I have read on IRC discussions about a deadline for drivers vendors to
> > have their CI running and voting until kilo-2, but I didn't find any post
> > on this list to confirm this. Can anyone confirm this?
> >
> > Thanks,
> > Erlon

We did discuss and agree in the Cinder meeting that the deadline would be k-2,
but I don't think anyone reached out to the driver maintainers about the
deadline. Duncan had this action item [1], perhaps he can speak more about it.

[1] - 
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.html

-- 
Mike Perez

__
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] Cutoff deadlines for cinder drivers

[Erlon Cruz]

Hi Ivan, thanks !!

On Fri, Jan 9, 2015 at 10:42 AM, Ivan Kolodyazhny  wrote:

> Hi Erlon,
>
> We've got a thread mailing-list [1] for it and some details in wiki [2].
> Anyway, need to get confirmation from our core devs and/or Mike.
>
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
> [2]
> https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond
>
> Regards,
> Ivan Kolodyazhny
>
> On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz  wrote:
>
>> Hi all, hi cinder core devs,
>>
>> I have read on IRC discussions about a deadline for drivers vendors to
>> have their CI running and voting until kilo-2, but I didn't find any post
>> on this list to confirm this. Can anyone confirm this?
>>
>> Thanks,
>> Erlon
>>
>> ___
>> 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
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Cutoff deadlines for cinder drivers

[Ivan Kolodyazhny]

Hi Erlon,

We've got a thread mailing-list [1] for it and some details in wiki [2].
Anyway, need to get confirmation from our core devs and/or Mike.

[1]
http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
[2]
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond

Regards,
Ivan Kolodyazhny

On Fri, Jan 9, 2015 at 2:26 PM, Erlon Cruz  wrote:

> Hi all, hi cinder core devs,
>
> I have read on IRC discussions about a deadline for drivers vendors to
> have their CI running and voting until kilo-2, but I didn't find any post
> on this list to confirm this. Can anyone confirm this?
>
> Thanks,
> Erlon
>
> ___
> 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

[openstack-dev] [Cinder] Cutoff deadlines for cinder drivers

[Erlon Cruz]

Hi all, hi cinder core devs,

I have read on IRC discussions about a deadline for drivers vendors to have
their CI running and voting until kilo-2, but I didn't find any post on
this list to confirm this. Can anyone confirm this?

Thanks,
Erlon
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev