[RFE] Create a full load balancing configuration with one API call

Bug #1463202 reported by Brandon Logan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Wishlist
Trevor Vardeman

Bug Description

There have been many requests to allow the API to expose the ability to create a load balancer, listener, pool, member, and health monitor in one single API request. Some reasons for this:

1) Drivers will know immediately up front what resources will be required to satisfy the end configuration. They can make more efficient/optimized decisions based on this.

2) It's not a good UX to have a user make at minimum 4 API requests before they can actually have a load balancer.

3) Reducing the number of API requests will improve performance of the API server when at large scale and other services consuming the same API.

Revision history for this message
Doug Wiegley (dougwig) wrote :

Approved.

Changed in neutron:
status: New → Triaged
tags: added: rfe-approved
removed: rfe
Changed in neutron:
assignee: nobody → Manjeet Singh Bhatia (manjeet-s-bhatia)
Changed in neutron:
importance: Undecided → Wishlist
Changed in neutron:
milestone: none → mitaka-1
Changed in neutron:
milestone: mitaka-1 → mitaka-2
Changed in neutron:
assignee: Manjeet Singh Bhatia (manjeet-s-bhatia) → nobody
Changed in neutron:
assignee: nobody → Brandon Logan (brandon-logan)
Changed in neutron:
status: Triaged → In Progress
Changed in neutron:
milestone: mitaka-2 → mitaka-3
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Henry Gessau (gessau)
summary: - Create a full load balancing configuration with one API call
+ [RFE] Create a full load balancing configuration with one API call
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Revision history for this message
Brandon Logan (brandon-logan) wrote :

update on this. I've agreed its probably best to let the L7 work go in before this because it'll be more work for them to also have to add that work into this. This now looks doubtful to make it in Mitaka because of this.

Revision history for this message
Brandon Logan (brandon-logan) wrote :

I wasn't clear in the last comment. Basically, I'm also going to add the L7 functionality to this as well so that L7 can go in before this.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

Sorry, your comments are still cryptic to. Are you saying that it's unlikely to deliver the 'get-me-a-loadbalancer' functionality in time for Mitaka?

Revision history for this message
Brandon Logan (brandon-logan) wrote :

yes, it probably won't be able to make it in for MItaka since I'm being realistic that the L7 patch is going to take the majority of the time left to get in. Since I've agreed I'll add the L7 functionality into the get-me-a-lb feature, it is now dependent on L7 getting in. Otherwise, it'd be ready for review. Having said that, there's still a chance it does, just a low probability.

Changed in neutron:
assignee: Brandon Logan (brandon-logan) → Trevor Vardeman (trevor-vardeman)
Changed in neutron:
milestone: mitaka-3 → mitaka-rc1
Changed in neutron:
milestone: mitaka-rc1 → newton-1
Changed in neutron:
assignee: Trevor Vardeman (trevor-vardeman) → Brandon Logan (brandon-logan)
Changed in neutron:
assignee: Brandon Logan (brandon-logan) → Trevor Vardeman (trevor-vardeman)
Changed in neutron:
assignee: Trevor Vardeman (trevor-vardeman) → Phillip Toohill (phillip-toohill)
Changed in neutron:
assignee: Phillip Toohill (phillip-toohill) → Trevor Vardeman (trevor-vardeman)
Changed in neutron:
milestone: newton-1 → newton-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-lbaas (master)

Reviewed: https://review.openstack.org/257201
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=eafbfd23b246b2b9828cdeb00f2acf7cb0ac0aca
Submitter: Jenkins
Branch: master

commit eafbfd23b246b2b9828cdeb00f2acf7cb0ac0aca
Author: Trevor Vardeman <email address hidden>
Date: Tue Mar 1 14:52:33 2016 -0600

    Get Me A LB

    Allows a request to be passed to the lbaas API that contains the full graph
    structure of a load balancer. This means that an entire load balancer graph
    can be created in one POST to the API, or a partial graph can be.

    This creates a new driver method to the driver interface that when implemented
    will be called when a full or partial graph is attempted to be created. If
    the driver does not implement this method, then the request is not allowed.

    Co-Author: Trevor Vardeman <email address hidden>

    Closes-Bug: #1463202
    Depends-On: Id3a5ddb8efded8c6ad72a7118424ec01c777318d
    Change-Id: Ic16ca4cb3cb407d9e91eea74315a39bf86c654f3

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/neutron-lbaas 9.0.0.0b2

This issue was fixed in the openstack/neutron-lbaas 9.0.0.0b2 development milestone.

Changed in neutron:
milestone: newton-2 → newton-3
milestone: newton-3 → newton-2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers