Open Stack

I also absolutely agree that Mike did a great job on the communication
with the driver maintainers and a lot more, especially in the hectic days
around the K-3 deadline.

Removing any driver lacking CI testing was just the right thing to do, even if
this affected our SMB3 driver. Hopefully this is just temporary as the related
CI is currently under test as well (whose delays are totally unrelated), so I
dont see it as a particularly dramatic decision. It also aligns well with the
policies applied it other major OpenStack projects like Nova or Neutron.

I'd be even in favor of a driver decomposition approach as Neutron did, but
that's another topic.

So, thanks again for all your great work and help!

Alessandro


> On 24 Mar 2015, at 16:41, Joshua Harlow <harlowja at outlook.com> wrote:
> 
> +10 to mike; I have no doubt this is an uneasy and tough task.
> 
> Thanks mike for pushing this through; given all the challenges and hard work (and likely not fun work) that had to be done.
> 
> I salute u! :)
> 
> -Josh
> 
> Duncan Thomas wrote:
>> On 23 March 2015 at 22:50, Mike Perez <thingee at gmail.com
>> <mailto:thingee at gmail.com>> wrote:
>> 
>> 
>>    I've talked to folks at the OpenStack foundation to get feedback on my
>>    communication, and was told this was good, and even better than previous
>>    communication to controversial changes.
>> 
>>    I expected nevertheless people to be angry with me and blame me
>>    regardless of
>>    my attempts to help people be successful and move the community forward.
>> 
>> 
>> As somebody who has previously attempted to drive 3rd party CI in Cinder
>> forward and completely burnt out on the process, I have to applaud
>> Mike's efforts. We needed a line in the sand to force the issue, or we
>> were never going to get to 100% coverage of drivers, which was what we
>> desperately needed.
>> 
>> For those who've have issues getting CI to be stable, this is a genuine
>> reflection of the stability of Openstack in general, but it is not
>> something we're going to be able to make progress on without CI systems
>> exposing problems. That's the entire point of the 3rd party CI program -
>> we knew there were bugs, stability issues and drivers that just plain
>> didn't work, but we couldn't  do much about it without being able to
>> test changes.
>> 
>> Thanks to Mike for the finally push on this, and to all of the various
>> people in both cinder and infra who've been very active in helping
>> people get their CI running, sometimes in very trying circumstances.
>> 
>> --
>> Duncan Thomas
>> 
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev