[openstack-dev] [nova] Simulating many fake nova compute nodes for scheduler testing

John Garbutt john at johngarbutt.com
Mon Feb 24 16:50:54 UTC 2014


On 24 February 2014 16:24, David Peraza <david_peraza at persistentsys.com> wrote:
> Hello all,
>
> I have been trying some new ideas on scheduler and I think I'm reaching a
> resource issue. I'm running 6 compute service right on my 4 CPU 4 Gig VM,
> and I started to get some memory allocation issues. Keystone and Nova are
> already complaining there is not enough memory. The obvious solution to add
> more candidates is to get another VM and set another 6 Fake compute service.
> I could do that but I think I need to be able to scale more without the need
> to use this much resources. I will like to simulate a cloud of 100 maybe
> 1000 compute nodes that do nothing (Fake driver) this should not take this
> much memory. Anyone knows of a more efficient way to  simulate many
> computes? I was thinking changing the Fake driver to report many compute
> services in different threads instead of having to spawn a process per
> compute service. Any other ideas?

It depends what you want to test, but I was able to look at tuning the
filters and weights using the test at the end of this file:
https://review.openstack.org/#/c/67855/33/nova/tests/scheduler/test_caching_scheduler.py

Cheers,
John



More information about the OpenStack-dev mailing list