<div dir="ltr"><br><br>2018-04-25 22:13 GMT+08:00 Jeremy Stanley <<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>>:<br>><br>> On 2018-04-25 14:12:00 +0800 (+0800), Rico Lin wrote:<br>> [...]<br>> > I believe to combine API services into one service will be able to<br>> > scale much easier. As we already starting from providing multiple<br>> > services and binding with Apache(Also concern about Zane's<br>> > comment), we can start this goal by saying providing unified API<br>> > service architecture (or start with new oslo api service). If we<br>> > reduce the difference between implementation from API service in<br>> > each OpenStack services first, maybe will make it easier to manage<br>> > or upgrade (since we unfied the package requirements) and even<br>> > possible to accelerate APIs.<br>> [...]<br>><br>> How do you see this as being either similar to or different from the<br>> <a href="https://git.openstack.org/cgit/openstack/oaktree/tree/README.rst">https://git.openstack.org/cgit/openstack/oaktree/tree/README.rst</a><br>> effort which is currently underway?<div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I think it's different from<span> </span></span><span class="gmail-gr_ gmail-gr_48 gmail-gr-alert gmail-gr_gramm gmail-gr_inline_cards gmail-gr_run_anim gmail-Punctuation gmail-only-del gmail-replaceWithoutSep" id="gmail-48" style="display:inline;color:rgb(34,34,34);font-size:small;border-bottom:2px solid transparent;background-repeat:no-repeat;font-family:arial,sans-serif;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span class="gmail-gr_ gmail-gr_36 gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards gmail-gr_disable_anim_appear gmail-ContextualSpelling gmail-ins-del gmail-multiReplace" id="gmail-36" style="display:inline;border-bottom:2px solid transparent;background-repeat:no-repeat;color:inherit;font-size:inherit">oaktree</span>,</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span> </span>since oaktree is an upper layer which depends on API Services (allow<span> </span></span><span class="gmail-gr_ gmail-gr_83 gmail-gr-alert gmail-gr_gramm gmail-gr_inline_cards gmail-gr_run_anim gmail-Grammar gmail-only-ins gmail-replaceWithoutSep" id="gmail-83" style="display:inline;color:rgb(34,34,34);font-size:small;border-bottom:2px solid transparent;background-repeat:no-repeat;font-family:arial,sans-serif;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">shade</span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span> </span>to connected with), And what I'm saying is to unify all API Servers. An example will be like what tempest do for tests, tempest provide cmd and tools to help you generate and run test cases, each service only required to provide a plugin. So if first step (to unified) is complete, we can even focus on enhancing API service for all, and the cool part is, we only need to do it in a single place for all projects. Think about what happens when Tempest trying to enhance test performance (just do it and check the gate is green).</span><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Also, what kevin's idea is to have a API service to replace all API service, which IIUC will be a API server directly use RPC to reach backend for each services in OpenStack. So it's also different too.</span></div><div><br>> --<br>> Jeremy Stanley<br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>><br><br><br><br>--<br>May The Force of OpenStack Be With You, <br>Rico Lin<br>irc: ricolin</div></div>