Neutron/LBaaS/requirements

Overview
Every cloud operator, vendor, etc. that wants load balancing as a service (LBaaS) has a different view on what load balancing is and how it should work. The goal of this page is to list overall requirements and use cases for the Neutron LBaaS plugin in an effort to concretely understand everyone's view on what load balancing is and how it should work. Furthermore, ranking requirements in terms of priority should also aid in determining the focus of current design and development efforts. This page should also help newcomers to the project understand where current efforts are being placed and why certain areas are not being worked on. If requirements can be created in a prioritized fashion, hopefully all participants in the project can understand expectations and maintain focus in an effort to have a more efficient development experience.

User Requirements
' *Priority is ranked Low to High. '

User Use Cases

 * TODO: Need user use cases

Operator Requirements
' *Priority is ranked Low to High. '

Operator Use Cases

 * TODO: Need operator use cases

Overview
Cloud operators have different types of cloud users. Thus, it fair to say that there will be times when disagreement on priorities will occur. The goal of this section is for cloud operators to provide data on how cloud users are consuming LBaaS. The aggregate of operator data below should be used to determine priority of requirements. Instead of blindly picking priorities of requirements, operator data should provide some guidance as to what features LBaaS users actually use (and thus value). If you are a cloud operator please feel free to add your data below. *Please note that all percentages are out of total number of load balancer instances*