Re: [openstack-dev] [octavia][sdk] service name for octavia

2017-02-15 Thread Morgan Fainberg
On Wed, Feb 15, 2017 at 7:25 AM, Monty Taylor  wrote:

> 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 ^^ ?
>
>
> ++
Please change that to workflow if possible.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [octavia][sdk] service name for octavia

2017-02-15 Thread Michael Johnson
Funny,  I had posted a patch to fix the devstack plugin earlier the same day
you sent this e-mail.

https://review.openstack.org/#/c/433817/

I also found that it was using "octavia" for the service type and wanted to
fix it.

I had picked "loadbalancing" but I am fine with "load-balancing" as well.  I
will update the patch.

Michael


-Original Message-
From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] 
Sent: Tuesday, February 14, 2017 5:09 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [octavia][sdk] service name for octavia

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.

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

While I believe this has been discussed about a year ago, I'm not sure if
there are things we missed so I'm brining this issue to a broader audience
for discussion.

Reference:

[1] Patch to python-openstacksdk:
https://review.openstack.org/#/c/428414
[2] Octavia service naming:
http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52

Regards,
 Qiming


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [octavia][sdk] service name for octavia

2017-02-15 Thread Monty Taylor
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 ^^ ?



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [octavia][sdk] service name for octavia

2017-02-15 Thread Hayes, Graham
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
>>
>> While I believe this has been discussed about a year ago, I'm not sure
>> if there are things we missed so I'm brining this issue to a broader
>> audience for discussion.
>>
>> Reference:
>>
>> [1] Patch to python-openstacksdk:
>> https://review.openstack.org/#/c/428414
>> [2] Octavia service naming:
>> http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52
>>
>> Regards,
>>  Qiming
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [octavia][sdk] service name for octavia

2017-02-15 Thread Monty Taylor
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)

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
> 
> While I believe this has been discussed about a year ago, I'm not sure
> if there are things we missed so I'm brining this issue to a broader
> audience for discussion.
> 
> Reference:
> 
> [1] Patch to python-openstacksdk:
> https://review.openstack.org/#/c/428414
> [2] Octavia service naming:
> http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52
> 
> Regards, 
>  Qiming
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [octavia][sdk] service name for octavia

2017-02-14 Thread Dean Troyer
On Tue, Feb 14, 2017 at 7: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.

The service name is actually irrelevant from a technical point of
view. It is maintained for deployer configuration and is often used
just for branding purposes.  It is the service type that should
uniquely identify a service in the catalog.

> 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.

Correct, this is the service type.

> [2] Octavia service naming:
> http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52

This points to Octavia's DevStack plugin configuration, which is by no
means authoritative.

There was a beginning of a service catalog type registry [3] that has
not gone beyond an initial proposal.  Sean Dague recently revived this
and I believe it will be discussed next week at the PTG.

dt

[3] https://git.openstack.org/cgit/openstack/service-types-authority

-- 

Dean Troyer
dtro...@gmail.com

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [octavia][sdk] service name for octavia

2017-02-14 Thread Qiming Teng
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.

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

While I believe this has been discussed about a year ago, I'm not sure
if there are things we missed so I'm brining this issue to a broader
audience for discussion.

Reference:

[1] Patch to python-openstacksdk:
https://review.openstack.org/#/c/428414
[2] Octavia service naming:
http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52

Regards, 
 Qiming


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev