Open Stack

On 02/15/2017 09:12 AM, Hayes, Graham wrote:
> On 15/02/2017 15:00, Monty Taylor wrote:
>> On 02/14/2017 07:08 PM, Qiming Teng wrote:
>>> When reviewing a recent patch that adds openstacksdk support to octavia,
>>> I found that octavia is using 'octavia' as its service name instead of
>>> 'loadbalancing' or 'loadbalancingv2' or something similar.
>>
>> Please not loadbalancingv2. As dean says in his email, we should be
>> using service_type not service_name for this. And service type should
>> not contain a version (please ignore what cinder did for v2 and v3
>> entries in the service catalog, it is a pattern that should not happen)
> 
> +1000
> 
>> All the services should have a version discovery endpoint on their
>> unversioned endpoint. If there is a v1 and a v2, then a user looking for
>> the loadbalancing service, if they want v2, should be able to get there
>> through version discovery.
>>
>> Also, if you haven't used loadbalancing anywhere yet, can I suggest
>> load-balancing instead to match object-store and key-manager?
>>
>>> The overall suggestion is to use a word/phrase that indicates what a
>>> service do instead of the name of the project providing that service.
>>>
>>> Below is the list of the service types currently supported by
>>> openstacksdk:
>>>
>>>     'alarming',    # aodh
>>>     'baremetal',   # ironic
>>>     'clustering',  # senlin
>>>     'compute',     # nova
>>>     'database',    # trove
>>>     'identity',    # keystone
>>>     'image',       # glance
>>>     'key-manager', # barbican
>>>     'messaging',   # zaqar
>>>     'metering',    # ceilometer
>>>     'network',     # neutron
>>>     'object-store',   # swift
>>>     'octavia',        # <--- this is an exception
>>>     'orchestration',  # heat
>>>     'volume',         # cinder
>>>     'workflowv2',     # mistral

Also - while we're on the topic - can we fix that to just be workflow ^^ ?