yahoo-eng-team team mailing list archive

[Miguel Lavalle <miguel@xxxxxxxxxxxx>]

Haven't heard back from submitter in two months. Will mark it invalid.
Please feel free to restore it in case there is interest in continuing
this conversation

** Changed in: neutron
   Importance: Wishlist => Undecided

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1809628

Title:
  [RFE] Enable driver field for the api of service_providers

Status in neutron:
  Invalid

Bug description:
  I found the api of service_provider is:

  RESOURCE_NAME = "service_provider"
  COLLECTION_NAME = "%ss" % RESOURCE_NAME
  SERVICE_ATTR = 'service_type'
  PLUGIN_ATTR = 'plugin'
  DRIVER_ATTR = 'driver'
  EXT_ALIAS = 'service-type'

  # Attribute Map for Service Provider Resource
  # Allow read-only access
  RESOURCE_ATTRIBUTE_MAP = {
      COLLECTION_NAME: {
          'service_type': {'allow_post': False, 'allow_put': False,
                           'is_visible': True},
          'name': {'allow_post': False, 'allow_put': False,
                   'is_visible': True},
          'default': {'allow_post': False, 'allow_put': False,
                      'is_visible': True},
      }
  }

  I found driver filed in the body of response of get_service_providers
  .Why is there no driver field in the api?

  I think there will be some scenarios need to use this filed ：
  when i create a body for service_profile, i need know the driver what would be used, like this:
  {
      "service_profile": {
          "enabled": "true",
          "driver": "neutron_lbaas.drivers.octavia.driver.OctaviaDriver",
          "description": "Dummy profile",
          "metainfo": "{'foo': 'bar'}"
      }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1809628/+subscriptions