On 03/23/2017 01:01 PM, Jean-Philippe Methot wrote:
Hi,
Lately, on my production openstack Newton setup, I've ran into a
situation that defies my assumptions regarding memory management on
Openstack compute nodes and I've been looking for explanations.
Basically, we had a VM with a flavor that l
- Original Message -
> From: "Jean-Philippe Methot"
> To: "Edmund Rhudy"
> Cc: openstack-operators@lists.openstack.org
> Sent: Thursday, March 23, 2017 3:49:26 PM
> Subject: Re: [Openstack-operators] Memory usage of guest vms, ballooning and
> no
tomatic, which is in
accordance to what you're conjecturing.
From: jp.met...@planethoster.info
Subject: Re: [Openstack-operators] Memory usage of guest vms,
ballooning and nova
Hi, This is indeed linux, CentOS 7 to be more precise, using
qemu-kvm as hypervisor. The used ram was in
ject: Re: [Openstack-operators] Memory usage of guest vms, ballooning and
nova
Hi,
This is indeed linux, CentOS 7 to be more precise, using qemu-kvm as
hypervisor. The used ram was in the used column. While we have made
adjustments by moving and resizing the specific guest that was using 96
GB (v
Hi,
This is indeed linux, CentOS 7 to be more precise, using qemu-kvm as
hypervisor. The used ram was in the used column. While we have made
adjustments by moving and resizing the specific guest that was using 96
GB (verified in top), the ram usage is still fairly high for the amount
of alloc
On 03/23/2017 11:01 AM, Jean-Philippe Methot wrote:
So basically, my question is, how does openstack actually manage ram allocation?
Will it ever take back the unused ram of a guest process? Can I force it to take
back that ram?
I don't think nova will automatically reclaim memory.
I'm pretty
Hi,
Lately, on my production openstack Newton setup, I've ran into a
situation that defies my assumptions regarding memory management on
Openstack compute nodes and I've been looking for explanations.
Basically, we had a VM with a flavor that limited it to 96 GB of ram,
which, to be quite hon
