Jump to: navigation, search

Difference between revisions of "Neutron/LBaaS"

Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
= Overview =
 
= Overview =
 
+
LBaaS (Load-balancer-as-a-Service) is Quantum extension that introduces load balancing feature set into the core. It became a sub-project of Quantum per decisions in "San Diego Oct-2012 Design Summit" since there was huge interest from Vendors and Community to participate in this effort.
LBaaS (Load-balancer-as-a-Service) is Quantum extension that introduces load balancing feature set into the core.  
 
It became a sub-project of Quantum per decisions in "San Diego Oct-2012 Design Summit" since there was huge interest from Vendors and Community to participate in this effort.
 
  
 
== Current Design Discussions + whats need to be done ==
 
== Current Design Discussions + whats need to be done ==
 
# Initial Discussions Document [[NetworkLoadBalancingIntegrationsWithQuantum]]
 
# Initial Discussions Document [[NetworkLoadBalancingIntegrationsWithQuantum]]
  May need to specify workflow of LB provisioning in all scenarios that LBaaS is going to support.
+
#* May need to specify workflow of LB provisioning in all scenarios that LBaaS is going to support.
 
 
 
# Object Model proposal - [[LBaaS/CoreResourceModel/proposal]]
 
# Object Model proposal - [[LBaaS/CoreResourceModel/proposal]]
  All agreed upon.  
+
#* All agreed upon. Might need minor update to include resources needed for device management (HW device catalog)
  Might need minor update to include resources needed for device management (HW device catalog)
 
 
 
 
# Tenant REST API - main proposal [[Quantum/LBaaS/API_1.0]]
 
# Tenant REST API - main proposal [[Quantum/LBaaS/API_1.0]]
  Discussion about tenant_id in URL ended with most people agreeing to go with 2.0 style or URL (no tenant_id in URL)
+
#* Discussion about tenant_id in URL ended with most people agreeing to go with 2.0 style or URL (no tenant_id in URL)
 
+
# Service Insertion - Spring Proposal [http://wiki.openstack.org/QuantumServicesInsertion ServicesInsertion] and Fall Proposal [[Quantum/ServiceInsertion]]
# Service Insertion - main proposal [[Quantum/ServiceInsertion]]
+
#* Things to be discussed:
  Things to be discussed:
+
#*# Code architecture: multiplugin / multivendor approach, changes in infrastructure (extension and plugin frameworks)
# Code architecture: multiplugin / multivendor approach, changes in infrastructure (extension and plugin frameworks)
+
#*# changes in existing resource model (router)
# changes in existing resource model (router)
+
#*# service catalog configuration
# service catalog configuration
+
#*# API
# API  
 
 
# Provider API / Device Management - proposal [[Quantum/LBaaS/RESTAPI/ProviderAPI]]
 
# Provider API / Device Management - proposal [[Quantum/LBaaS/RESTAPI/ProviderAPI]]
  The document describes API/process of registering a physical appliance as an LB device.
+
#* The document describes API/process of registering a physical appliance as an LB device.
 
 
 
# Balancer provisioning - proposal [[Quantum/LBaaS/Provisioning/proposal]]
 
# Balancer provisioning - proposal [[Quantum/LBaaS/Provisioning/proposal]]
  The document needs to be updated with workflows that correspond to (1)
+
#* The document needs to be updated with workflows that correspond to (1)
 
 
 
# Overall code architecture proposal [[Quantum/LBaaS/Architecture]]
 
# Overall code architecture proposal [[Quantum/LBaaS/Architecture]]
  Contains overall picture of components and what they do.  
+
#* Contains overall picture of components and what they do. Sequence diagram needs to be updated according to latest decision about async execution.
  Sequence diagram needs to be updated according to latest decision about async execution.
 
 
 
 
# Miscellaneous
 
# Miscellaneous
 
## Device Locking - proposal [[Quantum/LBaaS/Architecture/ConcurrentRequests]]
 
## Device Locking - proposal [[Quantum/LBaaS/Architecture/ConcurrentRequests]]
 
## Asynchronous execution (discussion):
 
## Asynchronous execution (discussion):
    Client gets immediate response with Job ID which it polls later on. May need to have short design spec on this.
+
##* Client gets immediate response with Job ID which it polls later on. May need to have short design spec on this.
 
# Inter-service resource dependency (discussion):
 
# Inter-service resource dependency (discussion):
    Resources of different advanced services may depend on one another. Solution options: (?)
+
#* Resources of different advanced services may depend on one another. Solution options: (?)
  
 
= Mettings =
 
= Mettings =
Line 43: Line 33:
  
 
== Agenda for 10/23/2012 Meeting ==
 
== Agenda for 10/23/2012 Meeting ==
 
 
* Work Planning and Tasks Assignment
 
* Work Planning and Tasks Assignment
 
* Discuss Deliverables for Grizzly 1 as per http://wiki.openstack.org/GrizzlyReleaseSchedule
 
* Discuss Deliverables for Grizzly 1 as per http://wiki.openstack.org/GrizzlyReleaseSchedule
Line 52: Line 41:
  
 
Phones:
 
Phones:
 +
 
* (855) 227-1767(USA) - 08003765931(UK)  Conf. Code 7152259
 
* (855) 227-1767(USA) - 08003765931(UK)  Conf. Code 7152259
 
* 0008006103229 (India – Toll Free)
 
* 0008006103229 (India – Toll Free)
 
* 81080024322044 (Moscow), 4992701688(Moscow)
 
* 81080024322044 (Moscow), 4992701688(Moscow)
Web Conf: https://myroom-na.adobeconnect.com/anandpalanisamy/
+
 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/listNumbersByCode.do?confCode=7152259&name=&email=&selectedProduct=joinMeeting
+
Web Conf: https://myroom-na.adobeconnect.com/anandpalanisamy/ https://www.intercallonline.com/portlets/scheduling/viewNumbers/listNumbersByCode.do?confCode=7152259&name=&email=&selectedProduct=joinMeeting
  
 
= Efforts Summary =
 
= Efforts Summary =
Line 68: Line 58:
 
* Project overview: https://docs.google.com/document/pub?id=1DRgQhZJ73EyzQ2KvzVQd7Li9YEL7fXWBp8reMdAEhiM
 
* Project overview: https://docs.google.com/document/pub?id=1DRgQhZJ73EyzQ2KvzVQd7Li9YEL7fXWBp8reMdAEhiM
 
* Screencast: http://www.youtube.com/watch?v=NgAL-kfdbtE
 
* Screencast: http://www.youtube.com/watch?v=NgAL-kfdbtE
* REST API: https://github.com/Mirantis/openstack-lbaas/wiki/REST%20API
+
* REST API: [https://github.com/Mirantis/openstack-lbaas/wiki/REST%20API https://github.com/Mirantis/openstack-lbaas/wiki/REST%20API]
 
* CLI tool: https://github.com/Mirantis/openstack-lbaas-cli/wiki
 
* CLI tool: https://github.com/Mirantis/openstack-lbaas-cli/wiki
 
* Roadmap: https://docs.google.com/document/pub?id=1yJZXI0WfpAZKhHaLQu7LaxGLrs4REmn0a5bYVbvsCTQ
 
* Roadmap: https://docs.google.com/document/pub?id=1yJZXI0WfpAZKhHaLQu7LaxGLrs4REmn0a5bYVbvsCTQ

Revision as of 16:18, 5 November 2012

Overview

LBaaS (Load-balancer-as-a-Service) is Quantum extension that introduces load balancing feature set into the core. It became a sub-project of Quantum per decisions in "San Diego Oct-2012 Design Summit" since there was huge interest from Vendors and Community to participate in this effort.

Current Design Discussions + whats need to be done

  1. Initial Discussions Document NetworkLoadBalancingIntegrationsWithQuantum
    • May need to specify workflow of LB provisioning in all scenarios that LBaaS is going to support.
  2. Object Model proposal - LBaaS/CoreResourceModel/proposal
    • All agreed upon. Might need minor update to include resources needed for device management (HW device catalog)
  3. Tenant REST API - main proposal Quantum/LBaaS/API_1.0
    • Discussion about tenant_id in URL ended with most people agreeing to go with 2.0 style or URL (no tenant_id in URL)
  4. Service Insertion - Spring Proposal ServicesInsertion and Fall Proposal Quantum/ServiceInsertion
    • Things to be discussed:
      1. Code architecture: multiplugin / multivendor approach, changes in infrastructure (extension and plugin frameworks)
      2. changes in existing resource model (router)
      3. service catalog configuration
      4. API
  5. Provider API / Device Management - proposal Quantum/LBaaS/RESTAPI/ProviderAPI
    • The document describes API/process of registering a physical appliance as an LB device.
  6. Balancer provisioning - proposal Quantum/LBaaS/Provisioning/proposal
    • The document needs to be updated with workflows that correspond to (1)
  7. Overall code architecture proposal Quantum/LBaaS/Architecture
    • Contains overall picture of components and what they do. Sequence diagram needs to be updated according to latest decision about async execution.
  8. Miscellaneous
    1. Device Locking - proposal Quantum/LBaaS/Architecture/ConcurrentRequests
    2. Asynchronous execution (discussion):
      • Client gets immediate response with Job ID which it polls later on. May need to have short design spec on this.
  9. Inter-service resource dependency (discussion):
    • Resources of different advanced services may depend on one another. Solution options: (?)

Mettings

We have a weekly meeting on every "Tuesday at 9:00 AM (Pacific TIme)" for discussing the Project Status, Issues, Work Item Rebalancing etc.

Agenda for 10/23/2012 Meeting

Phones:

  • (855) 227-1767(USA) - 08003765931(UK) Conf. Code 7152259
  • 0008006103229 (India – Toll Free)
  • 81080024322044 (Moscow), 4992701688(Moscow)

Web Conf: https://myroom-na.adobeconnect.com/anandpalanisamy/ https://www.intercallonline.com/portlets/scheduling/viewNumbers/listNumbersByCode.do?confCode=7152259&name=&email=&selectedProduct=joinMeeting

Efforts Summary

The following content summarizes the effort that the community put together to reach the "One-LBaaS for OpenStack" goal.

Agenda for OpenStack Summit

See http://etherpad.openstack.org/grizzly-quantum-lbaas

Link to Existing Resources

Equilibrium (Mirantis LBaaS)

Atlas project

eBay/PayPal Project

LBaaS w/ resource model focused on config re-use

LBaaS Integrated with Quantum (Sam Bercovici)

LBaaS with Quantum (Alex Gosse)