<div dir="ltr">If we consider dropping "os", should we entertain dropping "api", too? Do we have a good reason to keep "api"?<div><br></div><div>I wouldn't be opposed to simple service types (e.g "compute" or "loadbalancer").</div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Sep 15, 2018 at 9:01 AM Morgan Fainberg <<a href="mailto:morgan.fainberg@gmail.com">morgan.fainberg@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>I am generally opposed to needlessly prefixing things with "os".<div dir="auto"><br></div><div dir="auto">I would advocate to drop it.</div><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 14, 2018, 20:17 Lance Bragstad <<a href="mailto:lbragstad@gmail.com" target="_blank">lbragstad@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ok - yeah, I'm not sure what the history behind that is either...<div><br></div><div>I'm mainly curious if that's something we can/should keep or if we are opposed to dropping 'os' and 'api' from the convention (e.g. load-balancer:loadbalancer:post as opposed to os_load-balancer_api:loadbalancer:post) and just sticking with the service-type?</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 14, 2018 at 2:16 PM Michael Johnson <<a href="mailto:johnsomor@gmail.com" rel="noreferrer" target="_blank">johnsomor@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I don't know for sure, but I assume it is short for "OpenStack" and<br>
prefixing OpenStack policies vs. third party plugin policies for<br>
documentation purposes.<br>
<br>
I am guilty of borrowing this from existing code examples[0].<br>
<br>
[0] <a href="http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/policy-in-code.html" rel="noreferrer noreferrer" target="_blank">http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/policy-in-code.html</a><br>
<br>
Michael<br>
On Fri, Sep 14, 2018 at 8:46 AM Lance Bragstad <<a href="mailto:lbragstad@gmail.com" rel="noreferrer" target="_blank">lbragstad@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Thu, Sep 13, 2018 at 5:46 PM Michael Johnson <<a href="mailto:johnsomor@gmail.com" rel="noreferrer" target="_blank">johnsomor@gmail.com</a>> wrote:<br>
>><br>
>> In Octavia I selected[0] "os_load-balancer_api:loadbalancer:post"<br>
>> which maps to the "os-<service-type>-api:<resource>:<method>" format.<br>
><br>
><br>
> Thanks for explaining the justification, Michael.<br>
><br>
> I'm curious if anyone has context on the "os-" part of the format? I've seen that pattern in a couple different projects. Does anyone know about its origin? Was it something we converted to our policy names because of API names/paths?<br>
><br>
>><br>
>><br>
>> I selected it as it uses the service-type[1], references the API<br>
>> resource, and then the method. So it maps well to the API reference[2]<br>
>> for the service.<br>
>><br>
>> [0] <a href="https://docs.openstack.org/octavia/latest/configuration/policy.html" rel="noreferrer noreferrer" target="_blank">https://docs.openstack.org/octavia/latest/configuration/policy.html</a><br>
>> [1] <a href="https://service-types.openstack.org/" rel="noreferrer noreferrer" target="_blank">https://service-types.openstack.org/</a><br>
>> [2] <a href="https://developer.openstack.org/api-ref/load-balancer/v2/index.html#create-a-load-balancer" rel="noreferrer noreferrer" target="_blank">https://developer.openstack.org/api-ref/load-balancer/v2/index.html#create-a-load-balancer</a><br>
>><br>
>> Michael<br>
>> On Wed, Sep 12, 2018 at 12:52 PM Tim Bell <<a href="mailto:Tim.Bell@cern.ch" rel="noreferrer" target="_blank">Tim.Bell@cern.ch</a>> wrote:<br>
>> ><br>
>> > So +1<br>
>> ><br>
>> ><br>
>> ><br>
>> > Tim<br>
>> ><br>
>> ><br>
>> ><br>
>> > From: Lance Bragstad <<a href="mailto:lbragstad@gmail.com" rel="noreferrer" target="_blank">lbragstad@gmail.com</a>><br>
>> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" rel="noreferrer" target="_blank">openstack-dev@lists.openstack.org</a>><br>
>> > Date: Wednesday, 12 September 2018 at 20:43<br>
>> > To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" rel="noreferrer" target="_blank">openstack-dev@lists.openstack.org</a>>, OpenStack Operators <<a href="mailto:openstack-operators@lists.openstack.org" rel="noreferrer" target="_blank">openstack-operators@lists.openstack.org</a>><br>
>> > Subject: [openstack-dev] [all] Consistent policy names<br>
>> ><br>
>> ><br>
>> ><br>
>> > The topic of having consistent policy names has popped up a few times this week. Ultimately, if we are to move forward with this, we'll need a convention. To help with that a little bit I started an etherpad [0] that includes links to policy references, basic conventions *within* that service, and some examples of each. I got through quite a few projects this morning, but there are still a couple left.<br>
>> ><br>
>> ><br>
>> ><br>
>> > The idea is to look at what we do today and see what conventions we can come up with to move towards, which should also help us determine how much each convention is going to impact services (e.g. picking a convention that will cause 70% of services to rename policies).<br>
>> ><br>
>> ><br>
>> ><br>
>> > Please have a look and we can discuss conventions in this thread. If we come to agreement, I'll start working on some documentation in oslo.policy so that it's somewhat official because starting to renaming policies.<br>
>> ><br>
>> ><br>
>> ><br>
>> > [0] <a href="https://etherpad.openstack.org/p/consistent-policy-names" rel="noreferrer noreferrer" target="_blank">https://etherpad.openstack.org/p/consistent-policy-names</a><br>
>> ><br>
>> > _______________________________________________<br>
>> > OpenStack-operators mailing list<br>
>> > <a href="mailto:OpenStack-operators@lists.openstack.org" rel="noreferrer" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org" rel="noreferrer" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote></div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div>
__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>