-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 09 June 2014 19:03
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory
allocation ratio out of scheduler
On 06/09/2014 12:32 PM, Chris Friesen wrote:
On 06
Pray tell, what is that valid use case?
The valid use cases I've seen are mostly around testing.
As an administrator/operator, a scheduler hint to boot directly to a
host is useful to fully QC new compute hosts coming online.
It's also useful for testing some networking flow cases, a specific
PM
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation
ratio out of scheduler
From: Scott Devoid [ mailto:dev...@anl.gov ]
Sent: 04 June 2014 17:36
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Proposal
Subject: Re: [openstack-dev] [nova]
Proposal: Move CPU and memory allocation ratio out of scheduler
On 06/04/2014 06:10 AM, Murray, Paul (HP Cloud) wrote:
Hi Jay,
This sounds good to me. You left out the part of limits from the
discussion - these filters set the limits used at the resource
On 06/05/2014 09:54 AM, Day, Phil wrote:
-Original Message- From: Jay Pipes
[mailto:jaypi...@gmail.com] Sent: 04 June 2014 19:23 To:
openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]
[nova] Proposal: Move CPU and memory allocation ratio out of
scheduler
On 06/04/2014 11:56
On 06/09/2014 07:59 AM, Jay Pipes wrote:
On 06/06/2014 08:07 AM, Murray, Paul (HP Cloud) wrote:
Forcing an instance to a specific host is very useful for the
operator - it fulfills a valid use case for monitoring and testing
purposes.
Pray tell, what is that valid use case?
I find it useful
There may also be specific software entitlement issues that make it useful
to deterministically know which host your VM will be placed on. This can
be quite common in large organizations that have certain software that can
be tied to certain hardware or hardware with certain # of CPU capacity,
On 06/09/2014 12:32 PM, Chris Friesen wrote:
On 06/09/2014 07:59 AM, Jay Pipes wrote:
On 06/06/2014 08:07 AM, Murray, Paul (HP Cloud) wrote:
Forcing an instance to a specific host is very useful for the
operator - it fulfills a valid use case for monitoring and testing
purposes.
Pray tell,
On 06/09/2014 12:47 PM, Joe Cropper wrote:
There may also be specific software entitlement issues that make it
useful to deterministically know which host your VM will be placed on.
This can be quite common in large organizations that have certain
software that can be tied to certain hardware or
: [openstack-dev] [nova] Proposal: Move CPU and memory
allocation ratio out of scheduler
From: Scott Devoid [mailto:dev...@anl.gov]
Sent: 04 June 2014 17:36
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory
allocation
From: Scott Devoid [mailto:dev...@anl.gov]
Sent: 04 June 2014 17:36
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation
ratio out of scheduler
Not only live upgrades but also dynamic reconfiguration
From: Scott Devoid [mailto:dev...@anl.gov]
Sent: 04 June 2014 17:36
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation
ratio out of scheduler
Not only live upgrades but also dynamic reconfiguration
set so
it by-passes any resource constraints, which is deliberate.
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 04 June 2014 19:17
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation
ratio out
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 04 June 2014 19:23
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory
allocation ratio out of scheduler
On 06/04/2014 11:56 AM, Day, Phil wrote:
Hi Jay
+1, if doing so, a related bug related bug may be solved as well:
https://bugs.launchpad.net/nova/+bug/1323538
On Jun 3, 2014, at 21:29, Jay Pipes jaypi...@gmail.com wrote:
Hi Stackers,
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler and
into the
+1, makes sense to me.
On Wed, Jun 4, 2014 at 3:08 PM, Yingjun Li liyingjun1...@gmail.com wrote:
+1, if doing so, a related bug related bug may be solved as well:
https://bugs.launchpad.net/nova/+bug/1323538
On Jun 3, 2014, at 21:29, Jay Pipes jaypi...@gmail.com wrote:
Hi Stackers,
On 3 June 2014 14:29, Jay Pipes jaypi...@gmail.com wrote:
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler and
into the resource tracker. Remove the calculations for overcommit out of the
core_filter and ram_filter scheduler pieces.
+1
I hope to see us
+1 for this proposal.
We are highly interested in this one.
Jaesuk Ahn, Ph.D.
Team Lead, Next Generation Cloud Platform Dev. Project
KT
… active member of openstack community
On Jun 4, 2014, 5:29:36 PM, John Garbutt j...@johngarbutt.com wrote:
On 3 June 2014 14:29, Jay
Does there is any blueprint related to this? Thanks.
2014-06-03 21:29 GMT+08:00 Jay Pipes jaypi...@gmail.com:
Hi Stackers,
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler and
into the resource tracker. Remove the calculations for overcommit out of
the
the extensible resource tracker is the right way to do it ☺
Paul.
From: Jay Lau [mailto:jay.lau@gmail.com]
Sent: 04 June 2014 10:04
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation
ratio out of scheduler
John Garbutt j...@johngarbutt.com wrote on 06/04/2014 04:29:36 AM:
On 3 June 2014 14:29, Jay Pipes jaypi...@gmail.com wrote:
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler
and
into the resource tracker. Remove the calculations for overcommit out
of
Not only live upgrades but also dynamic reconfiguration.
Overcommitting affects the quality of service delivered to the cloud user.
In this situation in particular, as in many situations in general, I think
we want to enable the service provider to offer multiple qualities of
service.
On Thu, Jun 5, 2014 at 12:19 AM, Mike Spreitzer mspre...@us.ibm.com wrote:
Overcommitting affects the quality of service delivered to the cloud user.
In this situation in particular, as in many situations in general, I think
we want to enable the service provider to offer multiple qualities
On 06/03/2014 10:40 PM, ChangBo Guo wrote:
Jay, thanks for raising this up .
+1 for this .
A related question about the CPU and RAM allocation ratio, shall we
apply them when get hypervisor information with command nova
hypervisor-show ${hypervisor-name}
The output shows like
| memory_mb
On 06/04/2014 03:08 AM, Yingjun Li wrote:
+1, if doing so, a related bug related bug may be solved as well:
https://bugs.launchpad.net/nova/+bug/1323538
Yep, I agree that the above bug would be addressed.
Best,
-jay
On Jun 3, 2014, at 21:29, Jay Pipes jaypi...@gmail.com
On 06/04/2014 12:19 PM, Mike Spreitzer wrote:
John Garbutt j...@johngarbutt.com wrote on 06/04/2014 04:29:36 AM:
On 3 June 2014 14:29, Jay Pipes jaypi...@gmail.com wrote:
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova
scheduler and
into the resource
] Proposal: Move CPU and memory
allocation ratio out of scheduler
Does there is any blueprint related to this? Thanks.
2014-06-03 21:29 GMT+08:00 Jay Pipes jaypi...@gmail.com
mailto:jaypi...@gmail.com:
Hi Stackers,
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova
-Original Message- From: Jay Pipes
[mailto:jaypi...@gmail.com] Sent: 03 June 2014 14:29 To: OpenStack
Development Mailing List Subject: [openstack-dev] [nova] Proposal:
Move CPU and memory allocation ratio out of scheduler
Hi Stackers,
tl;dr =
Move CPU and RAM allocation ratio definition
- Original Message -
From: ChangBo Guo glongw...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, June 3, 2014 10:40:19 PM
Subject: Re: [openstack-dev] [nova] Proposal: Move CPU and memory allocation
ratio
Hi Stackers,
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler
and into the resource tracker. Remove the calculations for overcommit
out of the core_filter and ram_filter scheduler pieces.
Details
===
Currently, in the Nova code base, the thing that
It may be useful to have an API query which tells you all the numbers you
may need - real hardware values, values after using the configured
overcommit ratios and currently used values.
+1 to an exposed admin-API for host resource state and calculations,
especially if this allowed you to
On 06/03/2014 07:29 AM, Jay Pipes wrote:
Hi Stackers,
tl;dr
=
Move CPU and RAM allocation ratio definition out of the Nova scheduler
and into the resource tracker. Remove the calculations for overcommit
out of the core_filter and ram_filter scheduler pieces.
Makes sense to me.
Chris
Jay, thanks for raising this up .
+1 for this .
A related question about the CPU and RAM allocation ratio, shall we apply
them when get hypervisor information with command nova hypervisor-show
${hypervisor-name}
The output shows like
| memory_mb |
15824
|
| memory_mb_used
33 matches
Mail list logo
