<div dir="ltr"><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><snip></span></div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">you know, i've never worked anywhere that didn't roll their own distro.</span><br style="font-family:arial,sans-serif;font-size:12.800000190734863px">
<div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><snip></span></div><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">git clone nova</span></div>
<div><font face="arial, sans-serif">git clone <a href="https://github.com/stackforge/nova-docker">https://github.com/stackforge/nova-docker</a> </font><span style="font-family:arial,sans-serif">nova/nova/virt/</span><span style="font-family:arial,sans-serif">docker</span><br>
</div><div><br></div><div><font face="arial, sans-serif">/me Rage Quit :) </font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">In all seriousness though, this was discussed in lengths on openstack-dev. I do feel your pain as an operator if you find that support for a feature you were using was removed. I think this is the only way to go though in order to continue raising the openstack bar. </font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Best, </font></div><div><font face="arial, sans-serif"><br>Aaron</font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, May 1, 2014 at 11:24 PM, matt <span dir="ltr"><<a href="mailto:matt@nycresistor.com" target="_blank">matt@nycresistor.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div>operators perspective... <br><br></div>you guys had a lot of levity from austin on up to grizzly. not too many folks were using openstack back then. that's not the case anymore. even early adopters are exiting greenfield testing, and there's an upswing in adoption all over. <br>
<br></div>you can't cut features out without causing us a lot of work. the lack of an upgrade path is bad enough, we don't need to deal with containers and hypervisors being dropped from mainline. even if it's available from stackforge... it's being dropped from mainline means something to us. usually a hell of a lot of work.<br>
<br></div>and if it means something to us that's different from what you intended, then you shouldn't have dropped it. you need to be more restrictive in your choices as it relates to impacting major features. now i'm going to grant you the benefit of the doubt that you think docker is no longer up to par for openstack's use. but if that's not the case and this is just a move to try to motivate developers to write better tempest tests, i'd suggest you just burned down the barn to get the horses out. We needed that barn. It was a good barn. And now that it's gone we need to go figure out where we're going to put our stuff.<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></div><span class="HOEnZb"><font color="#888888">-matt<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 2, 2014 at 2:13 AM, Michael Still <span dir="ltr"><<a href="mailto:mikal@stillhq.com" target="_blank">mikal@stillhq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Fri, May 2, 2014 at 2:32 PM, matt <<a href="mailto:matt@nycresistor.com" target="_blank">matt@nycresistor.com</a>> wrote:<br>
<br>
> I am all for enforcing CI. But, my understanding of the workflow is code<br>
> doesn't go in without unit tests. Frankly you guys removing sections of<br>
> code for not having proper unit testing is downright terrifying. Doubly so<br>
> when it's major feature sets.<br>
<br>
</div>You are misunderstanding what we mean by CI in this case. We have unit<br>
tests (although the coverage isn't always great, but its pretty much<br>
on par with every other software project), but what we're talking<br>
about here is tempest tests -- which are scenario tests. Things like<br>
does booting a virtual machine actually work. Does getconsolelog()<br>
actually return a console. etc etc.<br>
<br>
We're raising the bar on testing. That's always a good thing. Worrying<br>
about what we had in the past doesn't really help, because there's<br>
nothing I can do about that.<br>
<span><font color="#888888"><br>
Michael<br>
<br>
--<br>
Rackspace Australia<br>
</font></span></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>