Then I would enable debug and verbose in nova.conf and restart the scheduler service. In this way you should see in the logs the entire scheduler logic and what resources it thinks your host has. On 27 Nov 2014 06:20, "mad Engineer" <themadengin...@gmail.com> wrote:
> George, > overcommit of RAM is 1 and that is working.However > instances are still getting created with available free memory < > reserved_host_memory_mb > > On Thu, Nov 27, 2014 at 4:33 PM, George Mihaiescu <lmihaie...@gmail.com> > wrote: > >> Depending on your overcommit ratio, the scheduler can schedule instances >> using more virtual memory than the available physical memory on the host, >> 700 MB in your case. >> On 27 Nov 2014 05:36, "mad Engineer" <themadengin...@gmail.com> wrote: >> >>> hi all i have set >>> reserved_host_memory_mb in nova.conf of controller and compute and >>> restarted necessary services. >>> i am expecting scheduler to not pickup host that has less than what is >>> reserved_host_memory_mb >>> in my example i put reserved_host_memory_mb = 1024 >>> and free RAM in compute node is 700 Mb. >>> But still scheduler chooses this host and created a new instance on it.I >>> am expecting scheduler to show "No valid Hosts found" as it has less ram >>> than reserved_host_memory_mb = 1024 >>> >>> Can some one help me understand this value >>> >>> Thanks >>> >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : openstack@lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
