Hi! That sounds similar to my idea :) Looks like it is already part of 4.7.1, I will give it a try...
Thanks Martin -----Ursprüngliche Nachricht----- Von: Koushik Das [mailto:koushik....@citrix.com] Gesendet: Donnerstag, 11. Februar 2016 04:43 An: <users@cloudstack.apache.org> Betreff: Re: Still having capacity calculation problems with XenServer. Check if the fix for CLOUDSTACK-8181 helps. > On 10-Feb-2016, at 7:33 PM, Martin Emrich <martin.emr...@empolis.com> wrote: > > Hi! > > I am still/again having issues with the capacity calculation on Cloudstack: > > https://issues.apache.org/jira/browse/CLOUDSTACK-2344 > https://issues.apache.org/jira/browse/CLOUDSTACK-7857 > > As these Issues are still in 4.7.1, I thought about implementing a fix > myself, I thought of a "LeastMemoryUsedAllocator". Used instead of the > FirstFitAllocator, it should always return the host with the most free memory > left, thus "Pushing" the problem to the point where all hosts are nearly > full. (Of course, a "real" fix would be preferred, when Cloudstack would try > the next host instead of returning a deployment error). > > I have the latest source code and Eclipse ready, found the example > "RandomAllocator", but now I am stuck: > > > - How do I get the memory used on each host inside the Allocator? > > - And how do I actually build the plugin? Can I build it, and get > some small .jar file, and just put that in the server and use it in > host.allocators.order? > > Yes, it sounds naïve, but I maybe it could be that simple... As my cloud is > unusable despite having hundreds of gigabytes of RAM available, I'm eager to > dive into cloudstack dev ;) > > Thanks > > Martin >
