yahoo-eng-team team mailing list archive

[William Kitsos <greek35t@xxxxxxxxx>]

Davanum,

I am running OpenStack Juno. Its running on three pieces of bare metal. 
Nova --version returns 2.19.0 on host compute1. This is running over Ubuntu 
server 14.04 LTS. The systems are up to date. I run an 'apt-get update && 
apt-get dist-upgrade' weekly. Please let me know if you need any more 
information. Thanks!

Affects Openstack/Nova

King Regards,

William

-----Original Message-----
From: bounces@xxxxxxxxxxxxx [mailto:bounces@xxxxxxxxxxxxx] On Behalf Of 
Davanum Srinivas (DIMS)
Sent: Friday, February 20, 2015 11:31 AM
To: greek35t@xxxxxxxxx
Subject: [Bug 1423644] Re: CPU/MEM usage not accurate. Hits quotas while 
resources are available

William, what version of OpenStack/Nova? Any specific distribution?

** Changed in: nova
       Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug 
report.
https://bugs.launchpad.net/bugs/1423644

Title:
  CPU/MEM usage not accurate. Hits quotas while resources are available

Status in OpenStack Compute (Nova):
  Incomplete
Status in Ubuntu:
  New

Bug description:
  I tried to set my quotas to exactly the hardware specs of my compute
  node for accurate reporting. My compute node runs on bare metal. After
  I did this I got quotas exceeded, unable to launch instance. I checked
  the hypervisor from the web interface and cli. 5 of 12 VCPUs used and
  6GB of 16GB used. When you try and change the quotas to match the
  hardware it errors. From the CLI it reports that quota cant be set to
  12 VCPUs because 17 are in use. Same with mem says 17GB are in use.
  But they arent in use clearly. So the bandaid is to set the quotas
  really high and then it ignores them and allows you to create
  instances against the actual nova usage stats. This also causes some
  failure to launch instance errors, no host is available meaning there
  arent enough resources even though there are. Im running this as a
  production environment for my domain so I have spent hundreds of hours
  chasing my tail. Hope this is helpful for debugging the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1423644/+subscriptions


** Also affects: juno
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1423644

Title:
  CPU/MEM usage not accurate. Hits quotas while resources are available

Status in Juno | Third-party Jupiter Broadcasting client for Ubuntu Touch:
  New
Status in OpenStack Compute (Nova):
  Incomplete
Status in Ubuntu:
  New

Bug description:
  I tried to set my quotas to exactly the hardware specs of my compute
  node for accurate reporting. My compute node runs on bare metal. After
  I did this I got quotas exceeded, unable to launch instance. I checked
  the hypervisor from the web interface and cli. 5 of 12 VCPUs used and
  6GB of 16GB used. When you try and change the quotas to match the
  hardware it errors. From the CLI it reports that quota cant be set to
  12 VCPUs because 17 are in use. Same with mem says 17GB are in use.
  But they arent in use clearly. So the bandaid is to set the quotas
  really high and then it ignores them and allows you to create
  instances against the actual nova usage stats. This also causes some
  failure to launch instance errors, no host is available meaning there
  arent enough resources even though there are. Im running this as a
  production environment for my domain so I have spent hundreds of hours
  chasing my tail. Hope this is helpful for debugging the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juno/+bug/1423644/+subscriptions