Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.
Sorry for late response, 1600 GMT is a little late in China, will check the meeting minutes if not attend. On Fri, May 8, 2015 at 12:19 AM, JJ Asghar wrote: > > On May 6, 2015, at 11:33 PM, Samuel Cassiba wrote: >> >> >> This has actually caused a situation that I’d like to make public. In the >> documentation the times for the meetings are suggested at the top of the >> hour, we have ours that start at :30 past. This allows for our friends and >> community members on the west coast of the United States able to join at a >> pseudo-reasonable time. The challenge is, if we move it forward to the top >> of the hour, we may lose the west coast, but if we move it back to the top >> of the next hour we may lose our friends in Germany and earlier time zones. >> > Moving it to the top of the hour would still fall in the realm of > pseudo-reasonable, as reasonable as meetings in that timeframe can be. 0800 > is more reasonable than 0730. ;-) > > By doing that, it would allow the group to remain as inclusive as possible, > while still allowing time for commutes for us west coasters. > > > Awesome! Yeah so it looks like we’ve gotten some positive feedback about > moving the meeting to 1600GMT. We’ll discuss it and ideally make it official > on Monday, and it’s already added to the agenda[1]. > > > -JJ > > [1]: https://etherpad.openstack.org/p/openstack-chef-meeting-20150511 > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata
Dugger, Sylvain, thanks for your replies.
On Fri, Aug 15, 2014 at 3:55 AM, Sylvain Bauza
wrote:
> 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 thru Nova-api and no endpoints are there
> got just scheduling
>
> That said, once Gantt will be lifted, discussing about possible endpoints
> sounds reasonable to me.
>
> -Sylvain
>
> Le 14 août 2014 05:07, "zhiwei" a écrit :
>
> >
> > 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 Pipes wrote:
> >>
> >> 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 your problems.
> >>
> >>
> >>> One of our scheduler component need to fetch image metadata by
> image_id(
> >>> at this time, there is not instance ).
> >>
> >>
> >> Why? Again, the request_spec contains all the information you need
> about the image...
> >>
> >> Best,
> >> -jay
> >>
> >>> On Thu, Aug 14, 2014 at 9:29 AM, Jay Pipes >>> <mailto:jaypi...@gmail.com>> wrote:
> >>>
> >>> 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.
> >>>
> >>> So, I want to ask if there are any other ways to do this?
> >>>
> >>>
> >>> You should not have to do a separate fetch of image metadata in a
> >>> scheduler filter (which is what I believe you meant by "plugin"
> above?).
> >>>
> >>> The filter object's host_passes() method has a filter_properties
> >>> parameter that contains the request_spec, that in turn contains the
> >>> image, which in turn contains the image "metadata". You can access
> >>> it like so:
> >>>
> >>> def host_passes(self, host_state, filter_properties):
> >>> request_spec = filter_properties['request___spec']
> >>>
> >>> image_info = request_spec['image']
> >>> # Certain image attributes are accessed via top-level keys,
> like
> >>> # size, disk_format, container_format and checksum
> >>> image_size = image_info['size']
> >>> # Other attributes can be accessed in the "properties"
> collection
> >>> # of key/value pairs
> >>> image_props = image.get('properties', {})
> >>> for key, value in image_props.items():
> >>> # do something...
> >>>
> >>> Best,
> >>> -jay
> >>>
> >>>
> >>>
> >>> _
> >>> OpenStack-dev mailing list
> >>> OpenStack-dev@lists.openstack.__org
> >>> <mailto:OpenStack-dev@lists.openstack.org>
> >>>
> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev <
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ___
> >>> OpenStack-dev mailing list
> >>> OpenStack-dev@lists.openstack.org
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>
> >>
> >> ___
> >> OpenStack-dev mailing list
> >> OpenStack-dev@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata
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 Pipes wrote:
> 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 your problems.
>
>
> One of our scheduler component need to fetch image metadata by image_id(
>> at this time, there is not instance ).
>>
>
> Why? Again, the request_spec contains all the information you need about
> the image...
>
> Best,
> -jay
>
> On Thu, Aug 14, 2014 at 9:29 AM, Jay Pipes > <mailto:jaypi...@gmail.com>> wrote:
>>
>> 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.
>>
>> So, I want to ask if there are any other ways to do this?
>>
>>
>> You should not have to do a separate fetch of image metadata in a
>> scheduler filter (which is what I believe you meant by "plugin"
>> above?).
>>
>> The filter object's host_passes() method has a filter_properties
>> parameter that contains the request_spec, that in turn contains the
>> image, which in turn contains the image "metadata". You can access
>> it like so:
>>
>> def host_passes(self, host_state, filter_properties):
>> request_spec = filter_properties['request___spec']
>>
>> image_info = request_spec['image']
>> # Certain image attributes are accessed via top-level keys, like
>> # size, disk_format, container_format and checksum
>> image_size = image_info['size']
>> # Other attributes can be accessed in the "properties"
>> collection
>> # of key/value pairs
>> image_props = image.get('properties', {})
>> for key, value in image_props.items():
>> # do something...
>>
>> Best,
>> -jay
>>
>>
>>
>> _
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.__org
>> <mailto:OpenStack-dev@lists.openstack.org>
>> http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>
>>
>>
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata
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 wrote:
> 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.
>>
>> So, I want to ask if there are any other ways to do this?
>>
>
> You should not have to do a separate fetch of image metadata in a
> scheduler filter (which is what I believe you meant by "plugin" above?).
>
> The filter object's host_passes() method has a filter_properties parameter
> that contains the request_spec, that in turn contains the image, which in
> turn contains the image "metadata". You can access it like so:
>
> def host_passes(self, host_state, filter_properties):
> request_spec = filter_properties['request_spec']
> image_info = request_spec['image']
> # Certain image attributes are accessed via top-level keys, like
> # size, disk_format, container_format and checksum
> image_size = image_info['size']
> # Other attributes can be accessed in the "properties" collection
> # of key/value pairs
> image_props = image.get('properties', {})
> for key, value in image_props.items():
> # do something...
>
> Best,
> -jay
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Is there a way to let nova schedule plugin fetch glance image metadata
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 other ways to do this? Thanks. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
