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

Michael Johnson johnsomor at gmail.com
Wed Feb 15 17:31:02 UTC 2017

Funny,  I had posted a patch to fix the devstack plugin earlier the same day
you sent this e-mail.


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.


-----Original Message-----
From: Qiming Teng [mailto:tengqim at linux.vnet.ibm.com] 
Sent: Tuesday, February 14, 2017 5:09 PM
To: openstack-dev at 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

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


[1] Patch to python-openstacksdk:
[2] Octavia service naming:


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list