Hi Eugene, Thanks for the update. This looks a good plan for Grizzly. One question on the time we select a device. Do we call the scheduler to select a device (given a certain service type) at the time of the pool creation or at the time of the vip creation? Youcef From: Eugene Nikanorov [mailto:enikanorov at mirantis.com] Sent: Tuesday, January 22, 2013 7:21 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Quantum][LBaaS] Scheduling & device management for LBaaS Hi folks, I'd like to present blueprint https://blueprints.launchpad.net/quantum/+spec/quantum-service-scheduler which I feel needs to be in grizzly. You can find more detailed description in specification page. Initially we planned to have comprehensive device management as separate plugin with extension and complicated schedulers. However due to the lack of time and reviewer resources we desided to greatly reduce the scope of this work. So, currently the code on review ( https://review.openstack.org/#/c/20225/ ) introduces the following: 1) Configuration management for service schedulers, e.g. admin can configure particular scheduler for particular service type 2) Simplistic scheduler for lbaas: - scheduling algorithm that randomly chooses a device from list of devices - device manager that reads devices from predefined conf-file (suggestion from Salvatore) I believe this is reasonable minimum that will allow to use LBaaS service at least with some convenience. (In fact, I'd provide some more scheduling algorithms) We have also started to integrate this code with code of lbaas-agent-and-rpc<https://blueprints.launchpad.net/quantum/+spec/lbaas-agent-and-rpc> according to the call sequence diagram: http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler So we plan that this code will be base patch for lbaas-agent-and-rpc<https://blueprints.launchpad.net/quantum/+spec/lbaas-agent-and-rpc>. Thanks, Eugene. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130123/9f3d9ba3/attachment.html>