<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style><style type="text/css"></style><style type="text/css"></style><style type="text/css"></style><style type="text/css"></style>
</head>
<body class=" hasGoogleVoiceExt hasGoogleVoiceExt" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt"><span style="font-size: 10pt;">TL;DR: Are enterprise needed features (HA, scalability, resource management, etc) on this project's roadmap. If so, how much of a priority is it? </span></div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt"><span style="font-size: 10pt;"><br>
</span></div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt"><span style="font-size: 10pt;">I've been doing some research on Neutron LBaaS to determine the viability and what needs to be done to allow for it to become an enterprise ready solution.
Since I am fairly new to this project please forgive me, and also correct me, if my understanding of some of these things is false. I've already spoken to Eugene about some of this, but I think it would be nice to get everyone's opinion. And since the object
model discussions are going on right now I believe this to be a good time to bring it up.</span></div>
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">
<div><br>
</div>
<div>As of its current incarnation Neutron LBaaS does not seem to be HA, scalable, and doesn't isolate resources for each load balancer. I know there is a blueprint for HA for the agent (https://blueprints.launchpad.net/neutron/+spec/lbaas-ha-agent) and HA
for HaProxy (https://blueprints.launchpad.net/neutron/+spec/lbaas-ha-haproxy). That is only for HaProxy, though, and sounds like it has to be implemented at the driver level. Is that the intended direction for implementing these goals, to implement them
at the driver level? I can definitely see why that is the way to do it because some drivers may already implement these features, while others don't. It would be nice if there was a way to give those features to drivers that do not have it out of the box.</div>
<div><br>
</div>
<div>Basically, I'd like this project to have these enterprise level features to that it can be adopted in an enterprise cloud. It will require a lot of work to achieve these goals, and I believe it should be something that is a goal.</div>
</div>
</div>
<script type="text/javascript">var new_nav = new function() {};var x;var old_navigator = window.navigator;for (x in navigator) {if (typeof navigator[x] == 'function') {eval("new_nav." + x + " = function() { return old_navigator." + x + "();};");} else {eval("new_nav." + x + " = navigator." + x + ";");}}new_nav.userAgent = "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1";new_nav.vendor = "Mozilla, Inc.";window.navigator = new_nav;</script><script type="text/javascript">var new_nav = new function() {};var x;var old_navigator = window.navigator;for (x in navigator) {if (typeof navigator[x] == 'function') {eval("new_nav." + x + " = function() { return old_navigator." + x + "();};");} else {eval("new_nav." + x + " = navigator." + x + ";");}}new_nav.userAgent = "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120427 Firefox/15.0a1";new_nav.vendor = "Mozilla, Inc.";window.navigator = new_nav;</script>
</body>
</html>