Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-28 Thread Luis Fernandez Alvarez
In Nova, "ram_allocation_ratio" & "reserved_host_memory_mb" are not mutually exclusive options, so they work together [0]. If it make sense or not to use "ram_allocation_ratio != 1" when "reserved memory != 0" is up to the cloud admin (depending on your use case, the purpose of your cloud, the

Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-28 Thread mad Engineer
Excellent answer thank you sir. One doubt comes into my mind is for this reservation to work RAM over committing should be disabled? ie ram_allocation_ratio=1 Thanks for your help On Thu, Nov 27, 2014 at 7:20 PM, Luis Fernandez Alvarez wrote: > Hi, > > In general, you can see 'reserved_host_memo

Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-27 Thread Luis Fernandez Alvarez
Hi, In general, you can see 'reserved_host_memory_mb' as your estimation of how much memory your hypervisor needs. From the point of view of Nova, your system is consuming the amount you set in 'reserved_host_memory_mb' [0]. Then, the field 'free_ram_mb' (the one that is checked when VMs are

Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-27 Thread mad Engineer
it reports "Free ram (MB): 425" but free -m has different result. Is it working for you.Are you using icehouse On Thu, Nov 27, 2014 at 6:16 PM, George Mihaiescu wrote: > Then I would enable debug and verbose in nova.conf and restart the scheduler > service. In this way you should see in the logs

Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-27 Thread George Mihaiescu
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" wrote: > George, > overcommit of RAM is 1 and tha

Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-27 Thread mad Engineer
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 wrote: > Depending on your overcommit ratio, the scheduler can schedule instances >

Re: [Openstack] significanse of reserved_host_memory_mb

2014-11-27 Thread George Mihaiescu
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" wrote: > hi all i have set > reserved_host_memory_mb in nova.conf of controller and compute

[Openstack] significanse of reserved_host_memory_mb

2014-11-27 Thread mad Engineer
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