. Gale
Ph: 303/443-3786
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Wednesday, August 13, 2014 10:12 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Is there a way to let nova schedule plugin fetch
glance image metadata
On 08/13/2014 11:06 PM
Mmm... I can understand that you perhaps need an external scheduler for
your own purposes, but I think you can't expect your plugin merged upstream
for two reasons :
- during Icehouse, there was an effort for not having the scheduler
proxying to the compute nodes
- Call for scheduler needs to go
Hi all,
We wrote a nova schedule plugin that need to fetch image metadata by
image_id, but encountered one thing, we did not have the glance context.
Our solution is to configure OpenStack admin user and password to
nova.conf, as you know this is not good.
So, I want to ask if there are any
On 08/13/2014 08:31 PM, zhiwei wrote:
Hi all,
We wrote a nova schedule plugin that need to fetch image metadata by
image_id, but encountered one thing, we did not have the glance context.
Our solution is to configure OpenStack admin user and password to
nova.conf, as you know this is not good.
Thanks Jay.
The scheduler plugin is not a scheduler filter.
We implemented a scheduler instead of using nova native scheduler.
One of our scheduler component need to fetch image metadata by image_id( at
this time, there is not instance ).
On Thu, Aug 14, 2014 at 9:29 AM, Jay Pipes
On 08/13/2014 10:22 PM, zhiwei wrote:
Thanks Jay.
The scheduler plugin is not a scheduler filter.
We implemented a scheduler instead of using nova native scheduler.
OK. Any reason why you did this? Without any details on what your
scheduler does, it's tough to give advice on how to solve
Hi Jay.
The case is: When heat create a stack, it will first call our
scheduler(will pass image_id), our scheduler will get image metadata by
image_id.
Our scheduler will build a placement policy through image metadata, then
start booting VM.
Thanks.
On Thu, Aug 14, 2014 at 10:28 AM, Jay
On 08/13/2014 11:06 PM, zhiwei wrote:
Hi Jay.
The case is: When heat create a stack, it will first call our
scheduler(will pass image_id), our scheduler will get image metadata by
image_id.
Our scheduler will build a placement policy through image metadata, then
start booting VM.
How exactly
