<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Jul 14, 2017, at 2:17 PM, Zane Bitter <<a href="mailto:zbitter@redhat.com" class="">zbitter@redhat.com</a>> wrote:<br class=""><div><div class=""><br class="Apple-interchange-newline"></div><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">* The pool of OpenStack developers is a fixed resource, and if we make it clear that some projects are unwelcome then their developers will be reassigned to 'core' projects in a completely zero-sum process. (Nnnnnnope.)</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote><div><br class=""></div><div>Yeah, I’ve heard this many times, and always shake my head. If I want to work on X, and X is not in OpenStack governance, I’m going to work on that anyway because I need it. Or maybe on a similar project. I’m going to scratch my itch.</div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">* While code like e.g. the Nova scheduler might be so complicated today that even the experts routinely complain about its terrible design,[1] if only we could add dozens more cooks (see above) it would definitely get much simpler and easier to maintain. (Bwahahahahahahaha.)</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote><div><br class=""></div><div>No, they need to appoint me as the Scheduler Overlord with the power to smite all those who propose complicated code!</div><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">* Once we make it clear to users that under no circumstances will we ever e.g. provide them with notifications about when a server has failed, ways to orchestrate a replacement, and an API to update DNS to point to the new one, then they will finally stop demanding bloat-inducing VMWare/oVirt-style features that enable them to treat cloud servers like pets. (I. don't. even.)</span></div></blockquote></div><div class=""><br class=""></div>Again, itches will be scratched. What I think is more important is a marketing issue, not a technical one. When I think of what it means to be a “core” project, I think of things that people looking to “get cloudy” would likely want. It isn’t until you start using a cloud that the additional projects you mention become important. So simplifying what is presented to the cloud market is a good thing, as it won’t confuse people as to what OpenStack is. But that doesn’t require any of the other projects be stopped or in any way discouraged.<br class=""><div class="">
<br class="">-- Ed Leafe<br class=""><br class=""><br class=""><br class=""><br class="">
</div>
<br class=""></body></html>