<div dir="ltr">Mike, <div><br>Great intiative, unfortunately I wasn't able to attend it, however I have some thoughts... </div><div>You can't simplify OpenStack just by fixing few issues that are described in the etherpad mostly.. </div><div><br></div><div>TC should work on shrinking the OpenStack use cases and moving towards the product (box) complete solution instead of pieces of bunch barely related things..</div><div><br></div><div><b>Simple things to improve: </b></div><div><i>This is going to allow community to work together, and actually get feedback in standard way, and incrementally improve quality. </i></div><div><br></div><div>1) There should be one and only one: <br></div><div>1.1) deployment/packaging(may be docker) upgrade mechanism used by everybody </div><div>1.2) monitoring/logging/tracing mechanism used by everybody </div><div>1.3) way to configure all services (e.g. k8 etcd way)</div><div>2) Projects must have standardize interface that allows these projects to use them in same way. </div><div>3) Testing & R&D should be performed only against this standard deployment</div><div><br></div><div><b>Hard things to improve: </b></div><div><br></div><div>OpenStack projects were split in far from ideal way, which leads to bunch of gaps that we have now: <br></div><div>1.1) Code & functional duplications: Quotas, Schedulers, Reservations, Health checks, Loggign, Tracing, .... </div><div>1.2) Non optimal workflows (booting VM takes 400 DB requests) because data is stored in Cinder,Nova,Neutron....</div><div>1.3) Lack of resources (as every project is doing again and again same work about same parts) </div><div><br></div><div>What we can do: </div><div><br></div><div><b>1) Simplify internal communication </b></div><div>1.1) Instead of AMQP for internal communication inside projects use just HTTP, load balancing & retries. </div><div><br></div><div><b>2) Use API Gateway pattern </b></div><div>3.1) Provide to use high level API one IP address with one client </div><div>3.2) Allows to significant reduce load on Keystone because tokens are checked only in API gateway </div><div>3.3) Simplifies communication between projects (they are now in trusted network, no need to check token) </div><div><br></div><div><b>3) Fix the OpenStack split </b></div><div>3.1) Move common functionality to separated internal services: Scheduling, Logging, Monitoring, Tracing, Quotas, Reservations (it would be even better if this thing would have more or less monolithic architecture) </div><div>3.2) Somehow deal with defragmentation of resources e.g. VM Volumes and Networks data which is heavily connected. </div><div><br></div><div> </div><div><b>4) Don't be afraid to break things</b></div><div>Maybe it's time for OpenStack 2: </div><div><ul><li>In any case most of people provide API on top of OpenStack for usage </li><li>In any case there is no standard and easy way to upgrade </li></ul><div>So basically we are not losing anything even if we do not backward compatible changes and rethink completely architecture and API. </div></div><div> </div><div><br></div><div>I know this sounds like science fiction, but I believe community will appreciate steps in this direction... </div><div><br></div><div><br></div><div>Best regards,<br>Boris Pavlovic </div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 12, 2017 at 2:33 PM, Mike Perez <span dir="ltr"><<a href="mailto:thingee@gmail.com" target="_blank">thingee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hey all,<br>
<br>
The session is over. I’m hanging near registration if anyone wants to<br>
discuss things. Shout out to John for coming by on discussions with<br>
simplifying dependencies. I welcome more packagers to join the<br>
discussion.<br>
<br>
<a href="https://etherpad.openstack.org/p/simplifying-os" rel="noreferrer" target="_blank">https://etherpad.openstack.org<wbr>/p/simplifying-os</a><br>
<br>
—<br>
<span class="gmail-m_-1963404707342125122HOEnZb"><font color="#888888">Mike Perez<br>
</font></span><div class="gmail-m_-1963404707342125122HOEnZb"><div class="gmail-m_-1963404707342125122h5"><br>
<br>
On September 12, 2017 at 11:45:05, Mike Perez (<a href="mailto:thingee@gmail.com" target="_blank">thingee@gmail.com</a>) wrote:<br>
> Hey all,<br>
><br>
> Back in a joint meeting with the TC, UC, Foundation and The Board it was decided as an area<br>
> of OpenStack to focus was Simplifying OpenStack. This intentionally was very broad<br>
> so the community can kick start the conversation and help tackle some broad feedback<br>
> we get.<br>
><br>
> Unfortunately yesterday there was a low turn out in the Simplification room. A group<br>
> of people from the Swift team, Kevin Fox and Swimingly were nice enough to start the conversation<br>
> and give some feedback. You can see our initial ether pad work here:<br>
><br>
> <a href="https://etherpad.openstack.org/p/simplifying-os" rel="noreferrer" target="_blank">https://etherpad.openstack.org<wbr>/p/simplifying-os</a><br>
><br>
> There are efforts happening everyday helping with this goal, and our team has made some<br>
> documented improvements that can be found in our report to the board within the ether<br>
> pad. I would like to take a step back with this opportunity to have in person discussions<br>
> for us to identify what are the area of simplifying that are worthwhile. I’m taking a break<br>
> from the room at the moment for lunch, but I encourage people at 13:30 local time to meet<br>
> at the simplification room level b in the big thompson room. Thank you!<br>
><br>
> —<br>
> Mike Perez<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>