Eugene: The BP name is a little confusing. It is not all about scheduler. But it needs us to have a scheduler. The BP spec in Read the full specification <https://docs.google.com/presentation/d/1eiBx6roRyk-mUfgBfJZUtEjEGbgTB5Gf4r7varAyDpg/edit> is old. But I cannot change the URL. the new Spec is ' https://docs.google.com/document/d/1TJlW0_tMpeENA_ia38fvRu7ioKRt9fsWXBjivwd1mMw/edit <https://docs.google.com/document/d/1TJlW0_tMpeENA_ia38fvRu7ioKRt9fsWXBjivwd1mMw/edit>' I have a patch for this BP: https://review.openstack.org/#/c/18216/ please see the schedule_xxxx methods in this file: https://review.openstack.org/#/c/18216/3/quantum/db/multipleagents_db.py I composed a draft admin guide (attached) for the BP, please have a look at: Appendix A. Demos Setup ->Scale and HA of agents. I read your http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler and have this: 1. Quantum scheduler can be multischeduler, just like one in nova-scheduler although it schedules only VM to compute hosts now. 2. With multischeduler, we can have sub schedulers. for example sub scheduler for allocating networks to DHCP agents sub scheduler for allocating quantum routers to l3 agents, and subscheduler for allocating 'pool' to devices So here it is: class multischeduler(object): scheduler['network'] = import_class(conf.network_scheduler) scheduler['router'] = import_class(conf.router_scheduler) scheduler['pool'] = import_class(conf.pool_scheduler) 3. Then the sequence diagram is calling scheduler['pool']. My BP is calling other two. Thanks Yong Sheng Gong On 12/18/2012 10:25 PM, Eugene Nikanorov wrote: > Hi Yong Sheng, > > I see you've started working > on https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler > > We also thought on designing/implementing scheduler for load balancer > service. > Although we're working on it within LBaaS effort, we're designing > scheduler to be a framework where service-specific scheduling > algorithms may easily be plugged. > > Could you briefly go > over http://wiki.openstack.org/Quantum/LBaaS/Architecture/Scheduler and share > your thoughts? > I think it would be better to have one scheduling component in quantum > rather than a set of shedulers for each kind of service. > > Also I have a question regarding quantum scheduler architecture > proposal (both options1 and 2) in blueprint spec: > why does it need to be a separate process? > > Thanks, > Eugene. > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121219/6344e2bc/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: bk-quantum-admin-guide-local.pdf Type: application/pdf Size: 759181 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121219/6344e2bc/attachment-0001.pdf>