Hi Luis, As you said, the scheduler is a separate daemon, mm_sched, and can be completely replaced. But the code is also ready to accept (and combine) new policies.
To get started, take a look at the code in src/scheduler [1]. You'll see that RankPolicy is a child class of the more generic SchedulerHostPolicy. Regards [1] http://dev.opennebula.org/projects/opennebula/repository/revisions/master/show/src/scheduler -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmar...@opennebula.org> On Tue, Nov 27, 2012 at 3:49 PM, Luis Rodero Merino <lrod...@gradiant.org>wrote: > Hi all, > > We are considering using OpenNebula for some internal research tasks. We > would like to know if it is possible to change the VM scheduler module to > implement our own scheduling policies. Reading the documentation, it seems > that the VM scheduler is a monolithic component, so we should replace it > totally to develop our own scheduling policy. Is that so? Or is there any > kind of plugin mechanism for scheduling policies? > > Best regards, > Luis > > -- > ================================================= > Dr. Luis Rodero-Merino > lrod...@gradiant.org > Gradiant, Edificio CITEXVI, local 14 > R/ Fonte das Abelleiras, Campus Universitario de Vigo > Vigo, Pontevedra, Spain, CP 36310 > Tf: +34 986 120 430 (ext 2012) Fax: +34 902 87 95 37 > ================================================= > > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
