Jump to: navigation, search

Difference between revisions of "Neutron/LBaaS"

Line 5: Line 5:
 
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.
 
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 Documents being discussed ==
+
== Current Design Discussions + whats need to be done ==
* Object Model proposal - [[LBaaS/CoreResourceModel/proposal]]
+
# Initial Discussions Document [[NetworkLoadBalancingIntegrationsWithQuantum]]
* REST API proposal - [[Quantum/LBaaS/RESTAPI/proposal]] and [[Quantum/LBaaS/RESTAPI/proposal2]]
+
  May need to specify workflow of LB provisioning in all scenarios that LBaaS is going to support.
* Engineering Resource Allocation - [[Quantum/LBaaS/ResourceAllocation]]
+
 
 +
# Object Model proposal - [[LBaaS/CoreResourceModel/proposal]]
 +
  All agreed upon.
 +
  Might need minor update to include resources needed for device management (HW device catalog)
 +
 
 +
# 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)
 +
 
 +
# Service Insertion - main proposal [[Quantum/ServiceInsertion]]
 +
  Things to be discussed:
 +
# Code architecture: multiplugin / multivendor approach, changes in infrastructure (extension and plugin frameworks)
 +
# changes in existing resource model (router)
 +
# service catalog configuration
 +
# API
 +
# Provider API / Device Management - proposal [[Quantum/LBaaS/RESTAPI/ProviderAPI]]
 +
  The document describes API/process of registering a physical appliance as an LB device.
 +
 
 +
# Balancer provisioning - proposal [[Quantum/LBaaS/Provisioning/proposal]]
 +
  The document needs to be updated with workflows that correspond to (1)
 +
 
 +
# 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.
 +
 
 +
# Miscellaneous
 +
## Device Locking - proposal [[Quantum/LBaaS/Architecture/ConcurrentRequests]]
 +
## Asynchronous execution (discussion):
 +
    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):
 +
    Resources of different advanced services may depend on one another. Solution options: (?)
  
 
= Mettings =
 
= Mettings =
Line 59: Line 88:
 
* [[Quantum/LBaaS/LBaaS_reuse_option]] - resource model & API suggestions (Serge Maskalik)
 
* [[Quantum/LBaaS/LBaaS_reuse_option]] - resource model & API suggestions (Serge Maskalik)
 
* [[LBaaS/CoreResourceModel/proposal]] - revised resource model suggestion (Youcef Laribi)
 
* [[LBaaS/CoreResourceModel/proposal]] - revised resource model suggestion (Youcef Laribi)
 
== Network Load Balancing Integration with Quantum Considerations ==
 
* [[NetworkLoadBalancingIntegrationsWithQuantum|Initial Discussions Document]]
 
  
 
== LBaaS Integrated with Quantum (Sam Bercovici) ==
 
== LBaaS Integrated with Quantum (Sam Bercovici) ==

Revision as of 21:11, 4 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.
  1. Object Model proposal - LBaaS/CoreResourceModel/proposal
 All agreed upon. 
 Might need minor update to include resources needed for device management (HW device catalog)
  1. 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)
  1. Service Insertion - main 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.
  1. Balancer provisioning - proposal Quantum/LBaaS/Provisioning/proposal
 The document needs to be updated with workflows that correspond to (1)
  1. 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.
  1. 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.
  1. 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)