Re: [openstack-dev] [glance] about use shared image with each other

[Brian Rosmaita]

On 11/21/18 7:16 AM, Rambo wrote:
> yes, but I also have a question, Do we have the quota limit for requests
> to share the image to each other? For example, someone shares the image
> with me without stop, how do we deal with it?

Given that the producer-consumer notifications are not handled by
Glance, this is not a problem.  (Or, to be more precise, not a problem
for Glance.)  A producer can share an image with you multiple times, but
since the producer cannot change your member-status, it will remain in
'pending' (or 'rejected' if you've already rejected it).  So there is no
quota necessary for this operation.

>  
> -- Original --
> *From: * "Brian Rosmaita";
> *Date: * Mon, Nov 19, 2018 10:26 PM
> *To: * "OpenStack Developmen";
> *Subject: * Re: [openstack-dev] [glance] about use shared image with
> each other
>  
> On 11/19/18 7:58 AM, Rambo wrote:
>> Hi,all
>>
>>      Recently, I want to use the shared image with each other.I find it
>> isn't convenient that the producer notifies the consumer via email which
>> the image has been shared and what its UUID is. In other words, why the
>> image api v2 is no provision for producer-consumer communication?
> 
> The design goal for Image API v2 image sharing was to provide an
> infrastructure for an "image marketplace" in an OpenStack cloud by (a)
> making it easy for cloud end users to share images, and (b) making it
> easy for end users not to be spammed by other end users taking advantage
> of (a).  When v2 image sharing was introduced in the Grizzly release, we
> did not want to dictate how producer-consumer communication would work
> (because we had no idea how it would develop), so we left it up to
> operators and end users to figure this out.
> 
> The advantage of email communication is that client side message
> filtering is available for whatever client a particular cloud end-user
> employs, and presumably that end-user knows how to manipulate the
> filters without learning some new scheme (or, if the end-user doesn't
> know, learning how to filter messages will apply beyond just image
> sharing, which is a plus).
> 
> Also, email communication is just one way to handle producer-consumer
> communication.  Some operators have adjusted their web interfaces so
> that when an end-user looks at the list of images available, a
> notification pops up if the end-user has any images that have been
> shared with them and are still in "pending" status.  There are various
> other creative things you can do using the normal API calls with regular
> user credentials.
> 
> In brief, we figured that if an image marketplace evolved in a
> particular cloud, producers and consumers would forge their own
> relationships in whatever way made the most sense for their particular
> use cases.  So we left producer-consumer communication out-of-band.
> 
>>       To make it is more convenient,  if we can add a task to change the
>> member_status from "pending" to "accepted" when we share the image with
>> each other. It is similar to the resize_confirm in Nova, we can control
>> the time interval in config.
> 
> You could do this, but that would defeat the entire purpose of the
> member statuses implementation, and hence I do not recommend it.  See
> OSSN-0005 [1] for more about this issue.
> 
> Additionally, since the Ocata release, "community" images have been
> available.  These do not have to be accepted by an end user (but they
> also don't show up in the default image-list response).  Who can
> "communitize" an image is governed by policy.
> 
> See [2] for a discussion of the various types of image sharing currently
> available in the Image API v2.  The Image Service API v2 api-ref [3]
> contains a brief discussion of image visibility and image sharing that
> may also be useful.  Finally, the Glance Ocata release notes [4] have an
> extensive discussion of image visibility.
> 
>>        Can you tell me more about this?Thank you very much!
> 
> The original design page on the wiki [5] has a list of 14 use cases we
> wanted to address; looking through those will give you a better idea of
> why we made the design choices we did.
> 
> Hope this helps!
> 
> cheers,
> brian
> 
> [0]
> http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html
> [1] https://wiki.openstack.org/wiki/OSSN/1226078
> [2]
> http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html
> [3] https://developer.openstack.org/api-ref/image/v2/
> [4] https://docs.openstack.org/releasenotes/glance/ocata.html
> [5] https://wik

Re: [openstack-dev] [glance] about use shared image with each other

[Rambo]

yes, but I also have a question, Do we have the quota limit for requests to 
share the image to each other? For example, someone shares the image with me 
without stop, how do we deal with it?
 
-- Original --
From:  "Brian Rosmaita";
Date:  Mon, Nov 19, 2018 10:26 PM
To:  "OpenStack Developmen"; 

Subject:  Re: [openstack-dev] [glance] about use shared image with each other

 
On 11/19/18 7:58 AM, Rambo wrote:
> Hi,all
> 
>  Recently, I want to use the shared image with each other.I find it
> isn't convenient that the producer notifies the consumer via email which
> the image has been shared and what its UUID is. In other words, why the
> image api v2 is no provision for producer-consumer communication?

The design goal for Image API v2 image sharing was to provide an
infrastructure for an "image marketplace" in an OpenStack cloud by (a)
making it easy for cloud end users to share images, and (b) making it
easy for end users not to be spammed by other end users taking advantage
of (a).  When v2 image sharing was introduced in the Grizzly release, we
did not want to dictate how producer-consumer communication would work
(because we had no idea how it would develop), so we left it up to
operators and end users to figure this out.

The advantage of email communication is that client side message
filtering is available for whatever client a particular cloud end-user
employs, and presumably that end-user knows how to manipulate the
filters without learning some new scheme (or, if the end-user doesn't
know, learning how to filter messages will apply beyond just image
sharing, which is a plus).

Also, email communication is just one way to handle producer-consumer
communication.  Some operators have adjusted their web interfaces so
that when an end-user looks at the list of images available, a
notification pops up if the end-user has any images that have been
shared with them and are still in "pending" status.  There are various
other creative things you can do using the normal API calls with regular
user credentials.

In brief, we figured that if an image marketplace evolved in a
particular cloud, producers and consumers would forge their own
relationships in whatever way made the most sense for their particular
use cases.  So we left producer-consumer communication out-of-band.

>   To make it is more convenient,  if we can add a task to change the
> member_status from "pending" to "accepted" when we share the image with
> each other. It is similar to the resize_confirm in Nova, we can control
> the time interval in config.

You could do this, but that would defeat the entire purpose of the
member statuses implementation, and hence I do not recommend it.  See
OSSN-0005 [1] for more about this issue.

Additionally, since the Ocata release, "community" images have been
available.  These do not have to be accepted by an end user (but they
also don't show up in the default image-list response).  Who can
"communitize" an image is governed by policy.

See [2] for a discussion of the various types of image sharing currently
available in the Image API v2.  The Image Service API v2 api-ref [3]
contains a brief discussion of image visibility and image sharing that
may also be useful.  Finally, the Glance Ocata release notes [4] have an
extensive discussion of image visibility.

>Can you tell me more about this?Thank you very much!

The original design page on the wiki [5] has a list of 14 use cases we
wanted to address; looking through those will give you a better idea of
why we made the design choices we did.

Hope this helps!

cheers,
brian

[0]
http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html
[1] https://wiki.openstack.org/wiki/OSSN/1226078
[2]
http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html
[3] https://developer.openstack.org/api-ref/image/v2/
[4] https://docs.openstack.org/releasenotes/glance/ocata.html
[5] https://wiki.openstack.org/wiki/Glance-api-v2-image-sharing


> 
> Best Regards
> Rambo
> 
> __
> 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__
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] [glance] about use shared image with each other

[Brian Rosmaita]

On 11/19/18 7:58 AM, Rambo wrote:
> Hi,all
> 
>      Recently, I want to use the shared image with each other.I find it
> isn't convenient that the producer notifies the consumer via email which
> the image has been shared and what its UUID is. In other words, why the
> image api v2 is no provision for producer-consumer communication?

The design goal for Image API v2 image sharing was to provide an
infrastructure for an "image marketplace" in an OpenStack cloud by (a)
making it easy for cloud end users to share images, and (b) making it
easy for end users not to be spammed by other end users taking advantage
of (a).  When v2 image sharing was introduced in the Grizzly release, we
did not want to dictate how producer-consumer communication would work
(because we had no idea how it would develop), so we left it up to
operators and end users to figure this out.

The advantage of email communication is that client side message
filtering is available for whatever client a particular cloud end-user
employs, and presumably that end-user knows how to manipulate the
filters without learning some new scheme (or, if the end-user doesn't
know, learning how to filter messages will apply beyond just image
sharing, which is a plus).

Also, email communication is just one way to handle producer-consumer
communication.  Some operators have adjusted their web interfaces so
that when an end-user looks at the list of images available, a
notification pops up if the end-user has any images that have been
shared with them and are still in "pending" status.  There are various
other creative things you can do using the normal API calls with regular
user credentials.

In brief, we figured that if an image marketplace evolved in a
particular cloud, producers and consumers would forge their own
relationships in whatever way made the most sense for their particular
use cases.  So we left producer-consumer communication out-of-band.

>       To make it is more convenient,  if we can add a task to change the
> member_status from "pending" to "accepted" when we share the image with
> each other. It is similar to the resize_confirm in Nova, we can control
> the time interval in config.

You could do this, but that would defeat the entire purpose of the
member statuses implementation, and hence I do not recommend it.  See
OSSN-0005 [1] for more about this issue.

Additionally, since the Ocata release, "community" images have been
available.  These do not have to be accepted by an end user (but they
also don't show up in the default image-list response).  Who can
"communitize" an image is governed by policy.

See [2] for a discussion of the various types of image sharing currently
available in the Image API v2.  The Image Service API v2 api-ref [3]
contains a brief discussion of image visibility and image sharing that
may also be useful.  Finally, the Glance Ocata release notes [4] have an
extensive discussion of image visibility.

>        Can you tell me more about this?Thank you very much!

The original design page on the wiki [5] has a list of 14 use cases we
wanted to address; looking through those will give you a better idea of
why we made the design choices we did.

Hope this helps!

cheers,
brian

[0]
http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html
[1] https://wiki.openstack.org/wiki/OSSN/1226078
[2]
http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-image-api-v2.html
[3] https://developer.openstack.org/api-ref/image/v2/
[4] https://docs.openstack.org/releasenotes/glance/ocata.html
[5] https://wiki.openstack.org/wiki/Glance-api-v2-image-sharing


> 
> Best Regards
> Rambo
> 
> __
> 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

[openstack-dev] [glance] about use shared image with each other

[Rambo]

Hi,all


 Recently, I want to use the shared image with each other.I find it isn't 
convenient that the producer notifies the consumer via email which the image 
has been shared and what its UUID is. In other words, why the image api v2 is 
no provision for producer-consumer communication?
  To make it is more convenient,  if we can add a task to change the 
member_status from "pending" to "accepted" when we share the image with each 
other. It is similar to the resize_confirm in Nova, we can control the time 
interval in config.
   Can you tell me more about this?Thank you very much!


















Best Regards
Rambo__
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-dev] [glance][tc] Seeking feedback on the OpenStack cloud vision

[Zane Bitter]

Greetings, Glance team!
As you may be aware, I've been working with other folks in the community 
on documenting a vision for OpenStack clouds (formerly known as the 
'Technical Vision') - essentially to interpret the mission statement in 
long-form, in a way that we can use to actually help guide decisions. 
You can read the latest draft here: https://review.openstack.org/592205


We're trying to get feedback from as many people as possible - in many 
ways the value is in the process of coming together to figure out what 
we're trying to achieve as a community with OpenStack and how we can 
work together to build it. The document is there to help us remember 
what we decided so we don't have to do it all again over and over.


The vision is structured with two sections that apply broadly to every 
project in OpenStack - describing the principles that we believe are 
essential to every cloud, and the ones that make OpenStack different 
from some other clouds. The third section is a list of design goals that 
we want OpenStack as a whole to be able to meet - ideally each project 
would be contributing toward one or more of these design goals.


There's not a lot to say about Glance specifically in the document. 
Obviously a disk image management service is a fairly fundamental 
component of 'Basic Physical Data Center Management', so it certainly 
fits with the vision.


If you would like me or another TC member to join one of your team IRC 
meetings to discuss further what the vision means for your team, please 
reply to this thread to set it up. You are also welcome to bring up any 
questions in the TC IRC channel, #openstack-tc - there's more of us 
around during Office Hours 
(https://governance.openstack.org/tc/#office-hours), but you can talk to 
us at any time.


Feedback can also happen either in this thread or on the review 
https://review.openstack.org/592205


If the team is generally happy with the vision as it is and doesn't have 
any specific feedback, that's cool but I'd like to request that at least 
the PTL leave a vote on the review. It's important to know whether we 
are actually developing a consensus in the community or just talking to 
ourselves :)


many thanks,
Zane.

__
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-dev] [glance] next python-glanceclient release

[Brian Rosmaita]

Hello Glancers,

I was looking at a Cinder patch [0] and it made me realize that we
should do a glanceclient release that includes the
multihash-download-verification [1] before the next scheduled Stein
release (which was to be 3.0.0, basically Rocky with v1 support removed;
see [2]).  I think it would be good to have the new verification change
released so other projects can consume the code and we can find out
sooner if it breaks anyone.  (I'm worried about allow_md5_fallback=False
[6], which I think is definitely the right thing for the CLI client, but
the discussion about allowing users to pick an os_hash_algo on Iain's
spec-lite [4] is making me worry about the effect that default value
could have on other services.)

Here are the options:
(1) backport [1] to stable/rocky and cut 2.12.1
(2) cut 2.13.0 from master and make it the first Stein glanceclient,
leaving legacy md5 checksum verification the only validation option in Rocky
(3) wait for 3.0.0 to include [1]
(4) change the default for allow_md5_fallback to True for the data()
function [6] (the CLI code already explicitly sets it and won't need to
be adjusted [5]) and then do (1) or (2) or (3)

Obviously, I don't like (3).  Not sure I like (4) either, but figured we
should at least think about it.

If we pick (1), we should merge the periodic tips job change [3] to
master and immediately backport it to stable/rocky before cutting the
release.  That way we won't have any unreleased patches sitting in
stable/rocky.

Let me know what you think.

cheers,
brian

[0] https://review.openstack.org/#/c/611081/
[1]
http://git.openstack.org/cgit/openstack/python-glanceclient/commit/?id=a4ea9f0720214bd4aa6d72e81776e1260b30ad2f
[2] https://launchpad.net/python-glanceclient/+series
[3] https://review.openstack.org/#/c/599844/
[4] https://review.openstack.org/#/c/597648/
[5]
http://git.openstack.org/cgit/openstack/python-glanceclient/tree/glanceclient/v2/shell.py?id=a4ea9f0720214bd4aa6d72e81776e1260b30ad2f#n521
[6]
http://git.openstack.org/cgit/openstack/python-glanceclient/tree/glanceclient/v2/images.py?id=a4ea9f0720214bd4aa6d72e81776e1260b30ad2f#n201

__
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] [glance][upgrade-checkers] Question about glance rocky upgrade release note

[Lance Bragstad]

I haven't implemented any checks, but I did take a shot at laying down the
scaffolding for implementing upgrade checks in glance [0].

Anyone who is more familiar with glance should be able to build off of that
commit by implementing specific checks in glance/cmd/status.py

[0] https://review.openstack.org/#/c/610661/

On Mon, Oct 15, 2018 at 10:49 AM Brian Rosmaita 
wrote:

> On 9/24/18 3:13 PM, Matt Riedemann wrote:
> > On 9/24/2018 2:06 PM, Matt Riedemann wrote:
> >> Are there more specific docs about how to configure the 'image import'
> >> feature so that I can be sure I'm careful? In other words, are there
> >> specific things a "glance-status upgrade check" check could look at
> >> and say, "your image import configuration is broken, here are details
> >> on how you should do this"
> Apologies for this delayed reply.
> > I guess this answers the question about docs:
> >
> >
> https://docs.openstack.org/glance/latest/admin/interoperable-image-import.html
>
> Yes, you found the correct docs.  They could probably use a revision to
> eliminate some of the references to Pike and Queens, but I think the
> content is accurate with respect to proper configuration of image import.
> > Would a basic upgrade check be such that if glance-api.conf contains
> > enable_image_import=False, you're going to have issues since that option
> > is removed in Rocky?
>
> I completely missed this question when I saw this email a few weeks ago.
>
> Yes, if a Queens glance-api.conf has enable_image_import=False, then it
> was disabled on purpose since the default in Queens was True.  Given the
> Rocky defaults for import-related config (namely, all import_methods are
> enabled), the operator may need to make some kind of adjustment.
>
> As a side point, although the web-download import method is enabled by
> default in Rocky, it has whitelist/blacklist configurability to restrict
> what kind of URIs end-users may access.  By default, end users are only
> able to access URIs using the http or https scheme on the standard ports.
>
> Thanks for working on the upgrade-checker goal for Glance!
>
> __
> 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] [glance][upgrade-checkers] Question about glance rocky upgrade release note

[Brian Rosmaita]

On 9/24/18 3:13 PM, Matt Riedemann wrote:
> On 9/24/2018 2:06 PM, Matt Riedemann wrote:
>> Are there more specific docs about how to configure the 'image import'
>> feature so that I can be sure I'm careful? In other words, are there
>> specific things a "glance-status upgrade check" check could look at
>> and say, "your image import configuration is broken, here are details
>> on how you should do this"
Apologies for this delayed reply.
> I guess this answers the question about docs:
> 
> https://docs.openstack.org/glance/latest/admin/interoperable-image-import.html

Yes, you found the correct docs.  They could probably use a revision to
eliminate some of the references to Pike and Queens, but I think the
content is accurate with respect to proper configuration of image import.
> Would a basic upgrade check be such that if glance-api.conf contains
> enable_image_import=False, you're going to have issues since that option
> is removed in Rocky?

I completely missed this question when I saw this email a few weeks ago.

Yes, if a Queens glance-api.conf has enable_image_import=False, then it
was disabled on purpose since the default in Queens was True.  Given the
Rocky defaults for import-related config (namely, all import_methods are
enabled), the operator may need to make some kind of adjustment.

As a side point, although the web-download import method is enabled by
default in Rocky, it has whitelist/blacklist configurability to restrict
what kind of URIs end-users may access.  By default, end users are only
able to access URIs using the http or https scheme on the standard ports.

Thanks for working on the upgrade-checker goal for Glance!

__
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-dev] [glance] spec-lite: Embed validation data in locations

[Brian Rosmaita]

I put together an etherpad outlining the changes to Iain's spec-lite
[0] that we discussed at today's glance meeting:

https://etherpad.openstack.org/p/glance-spec-lite-stein-locations-with-checksum

It's probably best to leave comments on the etherpad.

cheers,
brian

[0] https://review.openstack.org/#/c/597648/

__
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] [glance] Glance API Caching Enhancements for Edge Computing

[Abhishek Kekane]

Geeg,

Glance uses launchpad for blueprints and for specs you can refer to
glance-specs repo.

Thank you,

Abhishek

On Thu 4 Oct, 2018, 16:14 Waines, Greg,  wrote:

> I have not yet done a blueprint or spec for this in Glance.
>
> But can do that now.
>
>
>
> Is Glance using Launchpad or Storyboard ?
>
>
>
> Greg.
>
>
>
>
>
>
>
> *From: *Abhishek Kekane 
> *Reply-To: *"openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> *Date: *Thursday, October 4, 2018 at 2:08 AM
> *To: *"openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [glance] Glance API Caching Enhancements
> for Edge Computing
>
>
>
> Hi Greg,
>
>
>
> Have you actually filed a blueprint or specs for this in glance?
>
> If yes could you please provide a reference for the same.
>
>
>
>
> Thanks & Best Regards,
>
> Abhishek Kekane
>
>
>
>
>
> On Thu, Oct 4, 2018 at 12:34 AM Waines, Greg 
> wrote:
>
> Glance Team,
>
>
>
> I am following up on discussions in the edge-computing PTG meetings.
>
> There were discussions on potential enhancements to Glance API Caching for
> support of the proposed MVP Edge Architecture.
>
> And I took the action to write up a blueprint and a specification for
> these enhancements ... and will follow up with implementation.
>
>
>
> I thought I’d start the discussions on the mailing list ... and if
> everyone is still in agreement,
>
> then I’ll move the high-level definition/requirements to Glance’s
> Launchpad (or Storyboard?) and
>
> write up a Glance spec and review it in Gerrit.
>
>
>
> *THE PROPOSAL:*
>
>
>
> Enhance Glance API Caching such that
>
> a)   It works between two Glance Services (i.e. Glance at a Central
> OpenStack Cloud and Glance at an Edge OpenStack Cloud)
>
> · i.e. current Glance API Caching only works with external
> webservers
>
> b)   Enable the Edge Cloud Glance API Caching to support the ability
> to locally use those cached images (e.g. nova boot ...)
> even when network connectivity is lost to the Central Cloud Glance Service
>
> · i.e. image meta-data is required in order to service a ‘nova
> boot ...’, and
>today image meta-data is NOT cached by Glance API Caching.
>
>
>
> The proposed solution should generically work between any two Glance
> Services.
>
> e.g.
>
> · in a Multi-Region Environment,
>
> · in a StarlingX Distributed Cloud,
>
> · etc.
>
>
>
> The proposed solution need only deal with the Edge Cloud Glance talking to
> a single Central Cloud Glance.
>
>
>
>
>
> Let me know if you have any a questions or comments,
>
> Greg.
>
>
>
>
>
>
>
> p.s.
>
> *Background:*
>
> More info on the edge-computing group’s MVP Edge Architecture can be found
> here:
>
>
> https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0
>
> and
>
>
> https://docs.google.com/document/d/1Mq6bSm_lES56S4gygEuhmMbEeCI2nBFl_U5vl50wih8/edit?ts=5baa654e#heading=h.ncllqse6iw0u
>
> __
> 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
>
__
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] [glance] Glance API Caching Enhancements for Edge Computing

[Waines, Greg]

I have not yet done a blueprint or spec for this in Glance.
But can do that now.

Is Glance using Launchpad or Storyboard ?

Greg.



From: Abhishek Kekane 
Reply-To: "openstack-dev@lists.openstack.org" 

Date: Thursday, October 4, 2018 at 2:08 AM
To: "openstack-dev@lists.openstack.org" 
Subject: Re: [openstack-dev] [glance] Glance API Caching Enhancements for Edge 
Computing

Hi Greg,

Have you actually filed a blueprint or specs for this in glance?
If yes could you please provide a reference for the same.


Thanks & Best Regards,
Abhishek Kekane


On Thu, Oct 4, 2018 at 12:34 AM Waines, Greg 
mailto:greg.wai...@windriver.com>> wrote:
Glance Team,

I am following up on discussions in the edge-computing PTG meetings.
There were discussions on potential enhancements to Glance API Caching for 
support of the proposed MVP Edge Architecture.
And I took the action to write up a blueprint and a specification for these 
enhancements ... and will follow up with implementation.

I thought I’d start the discussions on the mailing list ... and if everyone is 
still in agreement,
then I’ll move the high-level definition/requirements to Glance’s Launchpad (or 
Storyboard?) and
write up a Glance spec and review it in Gerrit.

THE PROPOSAL:

Enhance Glance API Caching such that

a)   It works between two Glance Services (i.e. Glance at a Central 
OpenStack Cloud and Glance at an Edge OpenStack Cloud)

• i.e. current Glance API Caching only works with external webservers

b)   Enable the Edge Cloud Glance API Caching to support the ability to 
locally use those cached images (e.g. nova boot ...)
even when network connectivity is lost to the Central Cloud Glance Service

• i.e. image meta-data is required in order to service a ‘nova boot 
...’, and
   today image meta-data is NOT cached by Glance API Caching.

The proposed solution should generically work between any two Glance Services.
e.g.

• in a Multi-Region Environment,

• in a StarlingX Distributed Cloud,

• etc.

The proposed solution need only deal with the Edge Cloud Glance talking to a 
single Central Cloud Glance.


Let me know if you have any a questions or comments,
Greg.



p.s.
Background:
More info on the edge-computing group’s MVP Edge Architecture can be found here:
 
https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0
and
 
https://docs.google.com/document/d/1Mq6bSm_lES56S4gygEuhmMbEeCI2nBFl_U5vl50wih8/edit?ts=5baa654e#heading=h.ncllqse6iw0u
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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] [glance] Glance API Caching Enhancements for Edge Computing

[Abhishek Kekane]

Hi Greg,

Have you actually filed a blueprint or specs for this in glance?
If yes could you please provide a reference for the same.


Thanks & Best Regards,

Abhishek Kekane


On Thu, Oct 4, 2018 at 12:34 AM Waines, Greg 
wrote:

> Glance Team,
>
>
>
> I am following up on discussions in the edge-computing PTG meetings.
>
> There were discussions on potential enhancements to Glance API Caching for
> support of the proposed MVP Edge Architecture.
>
> And I took the action to write up a blueprint and a specification for
> these enhancements ... and will follow up with implementation.
>
>
>
> I thought I’d start the discussions on the mailing list ... and if
> everyone is still in agreement,
>
> then I’ll move the high-level definition/requirements to Glance’s
> Launchpad (or Storyboard?) and
>
> write up a Glance spec and review it in Gerrit.
>
>
>
> *THE PROPOSAL:*
>
>
>
> Enhance Glance API Caching such that
>
> a)   It works between two Glance Services (i.e. Glance at a Central
> OpenStack Cloud and Glance at an Edge OpenStack Cloud)
>
> · i.e. current Glance API Caching only works with external
> webservers
>
> b)   Enable the Edge Cloud Glance API Caching to support the ability
> to locally use those cached images (e.g. nova boot ...)
> even when network connectivity is lost to the Central Cloud Glance Service
>
> · i.e. image meta-data is required in order to service a ‘nova
> boot ...’, and
>today image meta-data is NOT cached by Glance API Caching.
>
>
>
> The proposed solution should generically work between any two Glance
> Services.
>
> e.g.
>
> · in a Multi-Region Environment,
>
> · in a StarlingX Distributed Cloud,
>
> · etc.
>
>
>
> The proposed solution need only deal with the Edge Cloud Glance talking to
> a single Central Cloud Glance.
>
>
>
>
>
> Let me know if you have any a questions or comments,
>
> Greg.
>
>
>
>
>
>
>
> p.s.
>
> *Background:*
>
> More info on the edge-computing group’s MVP Edge Architecture can be found
> here:
>
>
> https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0
>
> and
>
>
> https://docs.google.com/document/d/1Mq6bSm_lES56S4gygEuhmMbEeCI2nBFl_U5vl50wih8/edit?ts=5baa654e#heading=h.ncllqse6iw0u
> __
> 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

[openstack-dev] [glance] Glance API Caching Enhancements for Edge Computing

[Waines, Greg]

Glance Team,

I am following up on discussions in the edge-computing PTG meetings.
There were discussions on potential enhancements to Glance API Caching for 
support of the proposed MVP Edge Architecture.
And I took the action to write up a blueprint and a specification for these 
enhancements ... and will follow up with implementation.

I thought I’d start the discussions on the mailing list ... and if everyone is 
still in agreement,
then I’ll move the high-level definition/requirements to Glance’s Launchpad (or 
Storyboard?) and
write up a Glance spec and review it in Gerrit.

THE PROPOSAL:

Enhance Glance API Caching such that

a)   It works between two Glance Services (i.e. Glance at a Central 
OpenStack Cloud and Glance at an Edge OpenStack Cloud)

· i.e. current Glance API Caching only works with external webservers

b)   Enable the Edge Cloud Glance API Caching to support the ability to 
locally use those cached images (e.g. nova boot ...)
even when network connectivity is lost to the Central Cloud Glance Service

· i.e. image meta-data is required in order to service a ‘nova boot 
...’, and
   today image meta-data is NOT cached by Glance API Caching.

The proposed solution should generically work between any two Glance Services.
e.g.

· in a Multi-Region Environment,

· in a StarlingX Distributed Cloud,

· etc.

The proposed solution need only deal with the Edge Cloud Glance talking to a 
single Central Cloud Glance.


Let me know if you have any a questions or comments,
Greg.



p.s.
Background:
More info on the edge-computing group’s MVP Edge Architecture can be found here:
 
https://www.dropbox.com/s/255x1cao14taer3/MVP-Architecture_edge-computing_PTG.pptx?dl=0
and
 
https://docs.google.com/document/d/1Mq6bSm_lES56S4gygEuhmMbEeCI2nBFl_U5vl50wih8/edit?ts=5baa654e#heading=h.ncllqse6iw0u
__
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] [glance][upgrade-checkers] Question about glance rocky upgrade release note

[Matt Riedemann]

On 9/24/2018 2:06 PM, Matt Riedemann wrote:
Are there more specific docs about how to configure the 'image import' 
feature so that I can be sure I'm careful? In other words, are there 
specific things a "glance-status upgrade check" check could look at and 
say, "your image import configuration is broken, here are details on how 
you should do this"?


I guess this answers the question about docs:

https://docs.openstack.org/glance/latest/admin/interoperable-image-import.html

Would a basic upgrade check be such that if glance-api.conf contains 
enable_image_import=False, you're going to have issues since that option 
is removed in Rocky?


--

Thanks,

Matt

__
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-dev] [glance][upgrade-checkers] Question about glance rocky upgrade release note

[Matt Riedemann]

Looking at the upgrade-checkers goal [1] for glance and the Rocky 
upgrade release notes [2], one upgrade note says:


"As Image Import will be always enabled, care needs to be taken that it 
is configured properly from this release forward. The 
‘enable_image_import’ option is silently ignored."


Are there more specific docs about how to configure the 'image import' 
feature so that I can be sure I'm careful? In other words, are there 
specific things a "glance-status upgrade check" check could look at and 
say, "your image import configuration is broken, here are details on how 
you should do this"?


I'm willing to help write the upgrade check for glance, but need more 
details on that release note.


[1] https://storyboard.openstack.org/#!/story/2003657
[2] https://docs.openstack.org/releasenotes/glance/rocky.html#upgrade-notes

--

Thanks,

Matt

__
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-dev] [glance] replace locations on queued image

[iain macdonnell]

I feel like I've been chasing this issue around in circles for months,
and I need the core team to make a decision. I cannot proceed with
Rocky deployment/upgrade until this gets resolved.

It's currently possible to add to, or completely replace, the
"locations" for an image with status "queued", using HTTP PATCH. Prior
to the following fix, the "add" operation would update the status to
"active", but the "replace" operation would leave it in "queued"
status, with no way to get it out of that status (other than delete).
I thought that we agreed that that was a bug, which I submitted a fix
for:

https://review.openstack.org/592775

I don't see any API breakage from this fix. The previous state left
the image in permanently unusable state. I can't see any valid
use-case for that.

Now (this morning's meeting) it seems like we're back to debating
whether or not it's valid to "replace" "locations" for an image in
"queued" status. My interpretation of "replace" is "I want it to look
exactly like this, regardless of what's there now", as opposed to
"add", which means "append this to whatever is currently there".

If it's not valid to "replace" "locations" for an image in "queued"
status, I think that the API should reject the request, not leave the
image in limbo ('queued') status. I'm OK with that - I can use "add" -
but I'll need to update this:

https://review.openstack.org/597648

to apply only to "add".

glance core team, please make the decision.

Thanks,

~iain (slightly frustrated)

__
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] [glance][keystone][nova][ironic][tripleo][edge][airship] Edge related joint sessions at the PTG next week

[Alan Bishop]

On Wed, Sep 5, 2018 at 5:41 PM Ildiko Vancsa 
wrote:

> Hi,
>
> The PTG is approaching quickly and as we are planning a couple of joint
> sessions on edge computing with a couple of OpenStack project teams I would
> like to give a quick summary of the plans.
>
> We have the Edge Computing Group meeting all day Tuesday in Ballroom A[1]
> from 9am MDT. The group is planning a use cases and requirements discussion
> in the morning and collaborative sessions with Glance, Keystone, Nova,
> Airship, TripleO and StarlingX throughout the day. Furthermore people from
> the group will participate in the relevant session on the Ironic agenda on
> Thursday.
>

Thanks, Ildiko!

I highly encourage members from other storage communities such as cinder
and manila to consider attending (I will be).

Alan


> For the full agenda and session topics please see the following etherpad:
> https://etherpad.openstack.org/p/EdgeComputingGroupPTG4
>
> The StarlingX project is meeting all day Wednesday in Winter Park[1]
> starting at 9am MDT. Their topics include discussions on initial governance
> and release planning and further technical topics concerning architecture,
> build and deployment. The StarlingX team will participate in the
> cross-project sessions on Tuesday listed on the Edge Group etherpad for
> cross-project discussions.
>
> For the full agenda of StarlingX sessions please see the following
> etherpad: https://etherpad.openstack.org/p/stx-PTG-agenda
>
> Both groups are planning to provide remote participation option for their
> sessions, the information will be provided on the etherpads above before
> the sessions start.
>
> Please let me know if you have any questions.
>
> Thanks and Best Regards,
> Ildikó
> (IRC: ildikov)
>
> [1] https://web14.openstack.org/assets/ptg/Denver-map.pdf
>
>
>
> __
> 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

[openstack-dev] [glance][keystone][nova][ironic][tripleo][edge][airship] Edge related joint sessions at the PTG next week

[Ildiko Vancsa]

Hi,

The PTG is approaching quickly and as we are planning a couple of joint 
sessions on edge computing with a couple of OpenStack project teams I would 
like to give a quick summary of the plans.

We have the Edge Computing Group meeting all day Tuesday in Ballroom A[1] from 
9am MDT. The group is planning a use cases and requirements discussion in the 
morning and collaborative sessions with Glance, Keystone, Nova, Airship, 
TripleO and StarlingX throughout the day. Furthermore people from the group 
will participate in the relevant session on the Ironic agenda on Thursday.

For the full agenda and session topics please see the following etherpad: 
https://etherpad.openstack.org/p/EdgeComputingGroupPTG4

The StarlingX project is meeting all day Wednesday in Winter Park[1] starting 
at 9am MDT. Their topics include discussions on initial governance and release 
planning and further technical topics concerning architecture, build and 
deployment. The StarlingX team will participate in the cross-project sessions 
on Tuesday listed on the Edge Group etherpad for cross-project discussions.

For the full agenda of StarlingX sessions please see the following etherpad: 
https://etherpad.openstack.org/p/stx-PTG-agenda

Both groups are planning to provide remote participation option for their 
sessions, the information will be provided on the etherpads above before the 
sessions start.

Please let me know if you have any questions.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)

[1] https://web14.openstack.org/assets/ptg/Denver-map.pdf



__
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-dev] [glance][ptl] Canceled: Glance meeting Thu 6th and 13th of Sept

[Erno Kuvaja]

Hi all,

PTG is approaching fast and I'm pretty much offline this week for
holidays so will cancel the two next meetings.

We will get together over Wed to Fri in the PTG and have next Glance
weekly meeting the week after.

Safe travels everyone and I'm looking forward to see as many of ye as
possible in Denver.

Erno -jokke- Kuvaja

__
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] [glance][horizon] Issues we found when using Community Images

[Jeremy Freudberg]

Hi again Andy,

Thanks for the update. Sounds like there is some work to do in various
client libraries first.

I also just tried to launch a Sahara cluster against a community
image-- it failed, because our current validation wants the image ID
to actually appear in the image list. So there will have to be a
server side tweak to Sahara as well (not necessarily using your
desired "list all" mechanism, but it could be).

Anyway, the Sahara team is aware, and we'll keep an eye on this moving forward.

Cheers,
Jeremy


On Thu, Aug 23, 2018 at 8:43 PM, Andy Botting  wrote:
> Hi Jeremy,
>
>>
>> Can you comment more on what needs to be updated in Sahara? Are they
>> simply issues in the UI (sahara-dashboard) or is there a problem
>> consuming community images on the server side?
>
>
> We haven't looked into it much yet, so I couldn't tell you.
>
> I think it would be great to extend the Glance API to include a
> visibility=all filter, so we can actually get ALL available images in a
> single request, then projects could switch over to this.
>
> It might need some thought on how to manage the new API request when using
> an older version of Glance that didn't support visibility=all, but I'm sure
> that could be worked out.
>
> It would be great to hear from one of the Glance devs what they think about
> this approach.
>
> cheers,
> Andy
>
> __
> 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] [glance][horizon] Issues we found when using Community Images

[Andy Botting]

Hi Jeremy,


> Can you comment more on what needs to be updated in Sahara? Are they
> simply issues in the UI (sahara-dashboard) or is there a problem
> consuming community images on the server side?


We haven't looked into it much yet, so I couldn't tell you.

I think it would be great to extend the Glance API to include a
visibility=all filter, so we can actually get ALL available images in a
single request, then projects could switch over to this.

It might need some thought on how to manage the new API request when using
an older version of Glance that didn't support visibility=all, but I'm sure
that could be worked out.

It would be great to hear from one of the Glance devs what they think about
this approach.

cheers,
Andy
__
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] [glance][horizon] Issues we found when using Community Images

[Jeremy Freudberg]

Hi Andy,

Can you comment more on what needs to be updated in Sahara? Are they
simply issues in the UI (sahara-dashboard) or is there a problem
consuming community images on the server side?

I'm happy to pitch in, just would like to do it efficiently.

Thanks,
Jeremy

On Wed, Aug 22, 2018 at 5:31 PM, Andy Botting  wrote:
> Hi all,
>
> We've recently moved to using Glance's community visibility on the Nectar
> Research Cloud. We had lots of public images (12255), and we found it was
> becoming slow to list them all and the community image visibility seems to
> fit our use-case nicely.
>
> We moved all of our user's images over to become community images, and left
> our 'official' images as the only public ones.
>
> We found a few issues, which I wanted to document, if anyone else is looking
> at doing the same thing.
>
> -> Glance API has no way of returning all images available to me in a single
> API request (https://bugs.launchpad.net/glance/+bug/1779251)
> The default list of images is perfect (all available to me, except
> community), but there's a heap of cases where you need to fetch all images
> including community. If we did have this, my next points would be a whole
> lot easier to solve.
>
> -> Horizon's support for Community images is very lacking
> (https://bugs.launchpad.net/horizon/+bug/1779250)
> On the surface, it looks like Community images are supported in Horizon, but
> it's only as far as listing images in the Images tab. Trying to boot a
> Community image from the Launch Instance wizard is actually impossible, as
> community images don't appear in that list at all. The images tab in Horizon
> dynamically builds the list of images on the Images tab through new Glance
> API calls when you use any filters (good).
> In contrast, the source tab on the Launch Images wizard loads all images at
> the start (slow with lots of images), then relies on javascript client-side
> filtering of the list. I've got a dirty patch to fix this for us by
> basically making two Glance API requests (one without specifying visibility,
> and another with visibility=community), then merging the data. This would be
> better handled the same way as the Images tab, with new Glance API requests
> when filtering.
>
> -> Users can't set their own images as Community from the dashboard
> Should be relatively easy to add this. I'm hoping to look into fixing this
> soon.
>
> -> Murano / Sahara image discovery
> These projects rely on images to be chosen when creating new environments,
> and it looks like they use a glance list for their discovery. They both
> suffer from the same issue and require their images to be non-community for
> them to find their images.
>
> -> Openstack Client didn't support listing community images at all
> (https://storyboard.openstack.org/#!/story/2001925)
> It did support setting images to community, but support for actually listing
> them was missing.  Support has  now been added, but not sure if it's made it
> to a release yet.
>
> Apart from these issues, our migration was pretty successful with minimal
> user complaints.
>
> cheers,
> Andy
>
> __
> 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] [glance][horizon] Issues we found when using Community Images

[Monty Taylor]

On 08/22/2018 04:31 PM, Andy Botting wrote:

Hi all,

We've recently moved to using Glance's community visibility on the 
Nectar Research Cloud. We had lots of public images (12255), and we 
found it was becoming slow to list them all and the community image 
visibility seems to fit our use-case nicely.


We moved all of our user's images over to become community images, and 
left our 'official' images as the only public ones.


We found a few issues, which I wanted to document, if anyone else is 
looking at doing the same thing.


-> Glance API has no way of returning all images available to me in a 
single API request (https://bugs.launchpad.net/glance/+bug/1779251)
The default list of images is perfect (all available to me, except 
community), but there's a heap of cases where you need to fetch all 
images including community. If we did have this, my next points would be 
a whole lot easier to solve.


-> Horizon's support for Community images is very lacking 
(https://bugs.launchpad.net/horizon/+bug/1779250)
On the surface, it looks like Community images are supported in Horizon, 
but it's only as far as listing images in the Images tab. Trying to boot 
a Community image from the Launch Instance wizard is actually 
impossible, as community images don't appear in that list at all. The 
images tab in Horizon dynamically builds the list of images on the 
Images tab through new Glance API calls when you use any filters (good).
In contrast, the source tab on the Launch Images wizard loads all images 
at the start (slow with lots of images), then relies on javascript 
client-side filtering of the list. I've got a dirty patch to fix this 
for us by basically making two Glance API requests (one without 
specifying visibility, and another with visibility=community), then 
merging the data. This would be better handled the same way as the 
Images tab, with new Glance API requests when filtering.


-> Users can't set their own images as Community from the dashboard
Should be relatively easy to add this. I'm hoping to look into fixing 
this soon.


-> Murano / Sahara image discovery
These projects rely on images to be chosen when creating new 
environments, and it looks like they use a glance list for their 
discovery. They both suffer from the same issue and require their images 
to be non-community for them to find their images.


-> Openstack Client didn't support listing community images at all 
(https://storyboard.openstack.org/#!/story/2001925 
)
It did support setting images to community, but support for actually 
listing them was missing.  Support has  now been added, but not sure if 
it's made it to a release yet.


We've got a few more things I want to do related to images, sdk, 
openstackclient *and* horizon to make rollouts like this a bit better.


I'm betting when I do that I shoujld add murano, sahara and heat to the 
list.


We're currently having to add the new support in like 5 places, which is 
where some of the holes come from. Hopefully we'll get stuff solid on 
that front soon - but thanks for the feedback!


Apart from these issues, our migration was pretty successful with 
minimal user complaints.


\o/

__
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-dev] [glance][horizon] Issues we found when using Community Images

[Andy Botting]

Hi all,

We've recently moved to using Glance's community visibility on the Nectar
Research Cloud. We had lots of public images (12255), and we found it was
becoming slow to list them all and the community image visibility seems to
fit our use-case nicely.

We moved all of our user's images over to become community images, and left
our 'official' images as the only public ones.

We found a few issues, which I wanted to document, if anyone else is
looking at doing the same thing.

-> Glance API has no way of returning all images available to me in a
single API request (https://bugs.launchpad.net/glance/+bug/1779251)
The default list of images is perfect (all available to me, except
community), but there's a heap of cases where you need to fetch all images
including community. If we did have this, my next points would be a whole
lot easier to solve.

-> Horizon's support for Community images is very lacking (
https://bugs.launchpad.net/horizon/+bug/1779250)
On the surface, it looks like Community images are supported in Horizon,
but it's only as far as listing images in the Images tab. Trying to boot a
Community image from the Launch Instance wizard is actually impossible, as
community images don't appear in that list at all. The images tab in
Horizon dynamically builds the list of images on the Images tab through new
Glance API calls when you use any filters (good).
In contrast, the source tab on the Launch Images wizard loads all images at
the start (slow with lots of images), then relies on javascript client-side
filtering of the list. I've got a dirty patch to fix this for us by
basically making two Glance API requests (one without specifying
visibility, and another with visibility=community), then merging the data.
This would be better handled the same way as the Images tab, with new
Glance API requests when filtering.

-> Users can't set their own images as Community from the dashboard
Should be relatively easy to add this. I'm hoping to look into fixing this
soon.

-> Murano / Sahara image discovery
These projects rely on images to be chosen when creating new environments,
and it looks like they use a glance list for their discovery. They both
suffer from the same issue and require their images to be non-community for
them to find their images.

-> Openstack Client didn't support listing community images at all (
https://storyboard.openstack.org/#!/story/2001925)
It did support setting images to community, but support for actually
listing them was missing.  Support has  now been added, but not sure if
it's made it to a release yet.

Apart from these issues, our migration was pretty successful with minimal
user complaints.

cheers,
Andy
__
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-dev] glance 17.0.0.0rc2 (rocky)

[no-reply]

Hello everyone,

A new release candidate for glance for the end of the Rocky
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/glance/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Rocky release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/rocky release
branch at:

https://git.openstack.org/cgit/openstack/glance/log/?h=stable/rocky

Release notes for glance can be found at:

https://docs.openstack.org/releasenotes/glance/




__
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-dev] glance 17.0.0.0rc1 (rocky)

[no-reply]

Hello everyone,

A new release candidate for glance for the end of the Rocky
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/glance/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Rocky release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/rocky release
branch at:

http://git.openstack.org/cgit/openstack/glance/log/?h=stable/rocky

Release notes for glance can be found at:

http://docs.openstack.org/releasenotes/glance/




__
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] [glance] FFE for multi-backend

[Erno Kuvaja]

On Thu, Jul 26, 2018 at 3:35 PM, Abhishek Kekane  wrote:
> I'm asking for a Feature Freeze Exception for Multiple backend support
> (multi-store)
> feature [0].  The only remaining work is a versioning patch to flag this
> feature as
>  experimental and should be completed early next week.
>
> [0]
> https://specs.openstack.org/openstack/glance-specs/specs/rocky/approved/glance/multi-store.html
>
> Patches open for review:
>
> https://review.openstack.org/#/q/status:open+project:openstack/glance+branch:master+topic:bp/multi-store
>
>
>
> Th
> anks & Best Regards,
>
> Abhishek Kekane
>
> __
> 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
>

As agreed on weekly meeting yesterday, this change is just pending
prerequisites to merge so it can be released as EXPERIMENTAL API,
approved for FFE.

Thanks,
Erno jokke Kuvaja

__
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] [glance] FFE for multihash

[Erno Kuvaja]

On Thu, Jul 26, 2018 at 3:28 PM, Brian Rosmaita
 wrote:
> I'm asking for a Feature Freeze Exception for the glance-side work for
> the Secure Hash Algorithm Support (multihash) feature [0].  The work
> is underway and should be completed early next week.
>
> cheers,
> brian
>
> [0] 
> https://specs.openstack.org/openstack/glance-specs/specs/rocky/approved/glance/multihash.html
>
> __
> 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

As agreed on the Weekly meeting yesterday; this work is well on it's
way, the glance_store and python-glanceclient bits have been merged
and released; this change was agreed for FFE.

Thanks,
Erno jokke Kuvaja

__
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-dev] [glance] FFE for multi-backend

[Abhishek Kekane]

I'm asking for a Feature Freeze Exception for Multiple backend support
(multi-store)
feature [0].  The only remaining work is a versioning patch to flag
this feature as
 experimental and should be completed early next week.

​[0] 
https://specs.openstack.org/openstack/glance-specs/specs/rocky/approved/glance/multi-store.html

Patches open for review:

https://review.openstack.org/#/q/status:open+project:openstack/glance+branch:master+topic:bp/multi-store​



Th​
anks & Best Regards,

Abhishek Kekane
__
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-dev] [glance] FFE for multihash

[Brian Rosmaita]

I'm asking for a Feature Freeze Exception for the glance-side work for
the Secure Hash Algorithm Support (multihash) feature [0].  The work
is underway and should be completed early next week.

cheers,
brian

[0] 
https://specs.openstack.org/openstack/glance-specs/specs/rocky/approved/glance/multihash.html

__
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] [glance][glance_store] Functional testing of multiple backend

[Abhishek Kekane]

Hi Tomoki,

Thank you for your efforts, I will check this out. Seems like with the
patch you have mentioned multi store works with cinder as well.

Thank you again.



On Sat 30 Jun, 2018, 18:05 Tomoki Sekiyama, 
wrote:

> Hi Abhishek,
>
> Thanks for your work.
> I have added a way to configure cinder stores using devstack
> that I have used to test the multi-backend feature in cinder stores:
>
> https://etherpad.openstack.org/p/multi-store-scenarios
>
> Please note that it currently require additional bugfix patch for
> glance_store:
> https://review.openstack.org/#/c/579335/
>
> Thanks,
> Tomoki Sekiyama
>
>
> 2018年6月28日(木) 15:03 Abhishek Kekane :
>
>> Hi All,
>>
>> In Rocky I have proposed a spec [1] for adding support for multiple
>> backend in glance. I have completed the coding part and so far tested this
>> feature with file, rbd and swift store. However I need support in testing
>> this feature thoroughly. So kindly help me (or provide a way to configure
>> cinder, sheepdog and vmware stores using devstack) in functional testing
>> for remaining drivers.
>>
>> I have created one etherpad [2] with steps to configure this feature and
>> some scenarios I have tested with file, rbd and swift drivers.
>>
>> Please do the needful.
>>
>> [1] https://review.openstack.org/562467
>> [2] https://etherpad.openstack.org/p/multi-store-scenarios
>>
>> Summary of upstream patches:
>>
>> https://review.openstack.org/#/q/topic:bp/multi-store+(status:open+OR+status:merged)
>> 
>>
>>
>> Thanks & Best Regards,
>>
>> Abhishek Kekane
>>
>
__
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-dev] [glance][glance_store] Functional testing of multiple backend

[Abhishek Kekane]

Hi All,

In Rocky I have proposed a spec [1] for adding support for multiple backend
in glance. I have completed the coding part and so far tested this feature
with file, rbd and swift store. However I need support in testing this
feature thoroughly. So kindly help me (or provide a way to configure
cinder, sheepdog and vmware stores using devstack) in functional testing
for remaining drivers.

I have created one etherpad [2] with steps to configure this feature and
some scenarios I have tested with file, rbd and swift drivers.

Please do the needful.

[1] https://review.openstack.org/562467
[2] https://etherpad.openstack.org/p/multi-store-scenarios

Summary of upstream patches:
https://review.openstack.org/#/q/topic:bp/multi-store+(status:open+OR+status:merged)



Thanks & Best Regards,

Abhishek Kekane
__
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-dev] [glance] bug smash today

[Brian Rosmaita]

Today (Friday, 8 June UTC time) is our Rocky-2 bug smash.  Hang out in
#openstack-glance and keep the etherpad updated:

https://etherpad.openstack.org/p/glance-rocky-bug-smash

cheers,
brian

__
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-dev] [glance] Rocky-2 milestone release

[Brian Rosmaita]

Status:

glanceclient - released 2.11.1 today

glance_store - one outstanding patch that would be worth including in
the release:
- https://review.openstack.org/#/c/534745/  (use only exceptions for
uri validations)

glance - two patches we should get in:
- https://review.openstack.org/#/c/514114/ (refactor exception
handling in cmd.api) (has one +2)
- https://review.openstack.org/#/c/572534/ (remove deprecated
'enable_image_import' option)
- note: will need to regenerate the config files before proposing a release


cheers,
brian

__
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-dev] [Glance] Vancouver Summit Glance Dinner planning

[Erno Kuvaja]

Hi all,

time to see if we could get the glance folks together for dinner and
perhaps some refreshing beverages. If you are interested, please do
contribute to the plans here:
https://etherpad.openstack.org/p/yvr-glance-dinner

- jokke

__
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-dev] [Glance] No team meeting during the summit week

[Erno Kuvaja]

As majority of the team is in Vancouver for the summit we will cancel
next weeks meeting (24th of May). Glance team will have next meeting
in IRC Thu 31st.

Thanks,
Erno "jokke" Kuvaja

__
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-dev] [glance] Priorities for WC 16th of April

[Erno Kuvaja]

Hi all,

Now when client release is out and milestone 1 is approaching quickly
I'd like to draw your attention to few things in Glance development.

1) reviews of outstanding specs
2) work towards removal of the Images API v1
3) Pending delete rollback ability

Lets get the reviews to specs so we have clear picture by the summit
next month what we are doing, work towards removing the Images API v1
endpoints as early as possible so we avoid nasty surprises at the end
of the cycle and get the first new features merged in.

Thanks all for your continuous support driving towards another great
Glance release!

- Erno -jokke- Kuvaja

__
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] [glance] python-glanceclient release status

[Brian Rosmaita]

On Mon, Apr 2, 2018 at 6:28 PM, Brian Rosmaita
 wrote:
> These need to be reviewed in master:
> - https://review.openstack.org/#/c/50/
> - https://review.openstack.org/#/c/556292/

Thanks for the reviews.  The requested changes have been made and Zuul
has given a +1, so ready for reviews again!

> Backports needing review:
> - https://review.openstack.org/#/c/555436/

This has a +2 from Sean; it's up to Erno now.

cheers,
brian

__
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-dev] [glance] python-glanceclient release status

[Brian Rosmaita]

These need to be reviewed in master:
- https://review.openstack.org/#/c/50/
- https://review.openstack.org/#/c/556292/

Backports needing review:
- https://review.openstack.org/#/c/555436/

__
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-dev] [glance] Priorities for WC 26th of March

[Erno Kuvaja]

Hi all,

Time for the priority update:

The python-glanceclient release was postponed til this week due to
some bugs Brian found and is in process of fixing. Lets review these
and see what we need for the release, so we can get it out this week.

The R-1 Milestone is approaching quickly so I would like everyone to
look at our roadmap etherpad and have our R-1 targets fresh in mind:
https://etherpad.openstack.org/p/glance-rocky-priorities

Give your feedback to the rest open specs we have in flight, specially
the OSSN-0075 one https://review.openstack.org/#/c/468179

Remember that Easter is at the coming weekend for those of us who are
affected by it, meaning that this and next week may be short for many.

Have a amazing and effective week!

- Erno jokke Kuvaja

__
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] [glance] python-glanceclient release status

[Brian Rosmaita]

Adding another review to the list:
https://review.openstack.org/#/c/556292/

Also, https://review.openstack.org/50 has been updated with more tests.

Once those are approved, they'll need to be backported to
stable/queens so we can release 2.10.0

On Thu, Mar 22, 2018 at 8:55 PM, Brian Rosmaita
 wrote:
> As promised at today's Glance meeting, here's an update on the release
> status for the glanceclient bugfix release for stable/queens.
>
> There's another bug I think needs to be addressed:
> https://bugs.launchpad.net/python-glanceclient/+bug/1758149
>
> I've got a patch up so I can get feedback (particularly on the error 
> messages):
> https://review.openstack.org/50
>
> I'll be adding more tests to the patch (it needs them).
>
> It's already Friday UTC, so we won't be releasing 2.10.0 until Monday
> at the earliest.  Here are the backports that still require approval:
>
> https://review.openstack.org/#/c/555277/
> https://review.openstack.org/#/c/555390/
> https://review.openstack.org/#/c/555436/
>
> and a cherry-pick of 50 when that's done.
>
>
> cheers,
> brian

__
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-dev] [glance] python-glanceclient release status

[Brian Rosmaita]

As promised at today's Glance meeting, here's an update on the release
status for the glanceclient bugfix release for stable/queens.

There's another bug I think needs to be addressed:
https://bugs.launchpad.net/python-glanceclient/+bug/1758149

I've got a patch up so I can get feedback (particularly on the error messages):
https://review.openstack.org/50

I'll be adding more tests to the patch (it needs them).

It's already Friday UTC, so we won't be releasing 2.10.0 until Monday
at the earliest.  Here are the backports that still require approval:

https://review.openstack.org/#/c/555277/
https://review.openstack.org/#/c/555390/
https://review.openstack.org/#/c/555436/

and a cherry-pick of 50 when that's done.


cheers,
brian

__
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] [glance] New image backend: StorPool

[Sean McGinnis]

Just updating the subject line tag to glance. ;)

On Fri, Mar 16, 2018 at 05:33:30PM +0200, Peter Penchev wrote:
> Hi,
> 
> A couple of years ago I created a Nova spec for the StorPool image
> backend: https://review.openstack.org/#/c/137830/  There was some
> discussion, but then our company could not immediately allocate the
> resources to write the driver itself, so the spec languished and was
> eventually abandoned.
> 
> Now that StorPool has a fully maintained Cinder driver and also a
> fully maintained Nova volume attachment driver, both included in the
> Queens release, and a Cinder third-party CI that runs all the tests
> tagged with "volume", including some simple Nova tests, we'd like to
> resurrect this spec and implement a Nova image backend, too.
> Actually, it looks like due to customer demand we will write the
> driver anyway and possibly maintain it outside the tree, but it would
> be preferable (and, obviously, easier to catch up with wide-ranging
> changes) to have it in.
> 
> Would there be any major opposition to adding a StorPool shared
> storage image backend, so that our customers are not limited to
> volume-backed instances?  Right now, creating a StorPool volume and
> snapshot from a Glance image and then booting instances from that
> snapshot works great, but in some cases, including some provisioning
> and accounting systems on top of OpenStack, it would be preferable to
> go the Nova way and let the hypervisor think that it has a local(ish)
> image to work with, even though it's on shared storage anyway.  This
> will go hand-in-hand with our planned Glance image driver, so that
> creating a new instance from a Glance image would happen
> instantaneously (create a StorPool volume from the StorPool snapshot
> corresponding to the Glance image).
> 
> If this will help the decision, we do have plans for adding a
> full-blown Nova third-party CI in the near future, so that both our
> volume attachment driver, this driver, and our upcoming Glance image
> driver will see some more testing.
> 
> Thanks in advance, and keep up the great work!
> 
> Best regards,
> Peter
> 
> __
> 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

[openstack-dev] [glance] bug squad meetings start Monday

[Brian Rosmaita]

The Glance Bug Squad will meet biweekly on Monday of even-numbered ISO
weeks at 10:00 UTC in #openstack-glance.  The meeting will last 45
minutes.

The first meeting will be 19 March 2018.

Agenda and notes: https://etherpad.openstack.org/p/glance-bug-squad-meeting

__
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-dev] [glance] OSSN-0076 brainstorming session Friday 16 March

[Brian Rosmaita]

I'm working on a spec to alleviate OSSN-0076 that would follow up the
OSSN-0075 proposal [0], but have run into some problems.  It would be
helpful to lay them out and get some feedback.  I'll be in the
#openstack-glance channel at 16:30 UTC tomorrow (Friday) to discuss.
Will take less than 1/2 hour.

cheers,
brian

[0] https://review.openstack.org/#/c/468179/

__
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-dev] [glance] Priorities for WC 12th of March

[Erno Kuvaja]

Hi all,

Queens is released, we had good and productive PTG so lets get the
ball rolling and start working through our Rocky priorities.

This week I'd like the focus to be, as discussed in our weekly meeting
at Thu, on python-glanceclient for 'web-download' import method and
any specs that still would needs review on the PTG topic list [0]. You
can review the topic etherpads for your convenience. Lets get those
nailed down so the people committed to those features can start
working on the implementation.

Another announcement for Glance (Core) reviewers so that you are
aware. We've had unenforced (to keep other changes to spec repo being
not depending on one person) policy in Glance that only PTL +W's any
specs so we can ensure that all our cores and invested parties are
aware and on board. This is clearly something that was forgotten and
we failed to communicate to our new cores so we did change the repo
acl accordingly [1]

[0] https://etherpad.openstack.org/p/glance-rocky-ptg
[1]https://review.openstack.org/#/c/551268/

I wish you all great and productive week!

Best,
Erno jokke Kuvaja

__
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-dev] [glance] bi-weekly bug team meeting

[Brian Rosmaita]

To anyone interested in attending the bug team meetings:

I'm proposing a 45 minute meeting every other week beginning the week
of March 19.  Time is 10:00 UTC (unless that turns out to be
unworkable for everybody).  Please indicate your preference for day of
the week on this Doodle poll:

https://doodle.com/poll/39xbzeu8nh4bgkhq

cheers,
brian

__
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] [Glance] Changes to Glance core team

[Flavio Percoco]

On 01/03/18 12:09 +, Erno Kuvaja wrote:

2) Removing Flavio Percoco from Glance core. Flavio requested to be
removed already couple of cycles ago and we did beg him to stick
around to help with the Interoperable Image Import which of he has
been integral part of designing since the very beginning and due to
his knowledge of the internals of the Glance tasks. The majority of
this work is finished and we would like to thank Flavio for his help
and hard work for Glance community.


Makes sense to me! +1

Thanks for all the fish. :)
Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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] [Glance] Changes to Glance core team

[Sean McGinnis]

Thanks team - glad to be able to help out and I am hoping I can dig in more
and be able to contribute where I can!

Sean

> On Mar 1, 2018, at 06:22, Abhishek Kekane  wrote:
> 
> Big +1 to Sean, he has been doing wonderful job for us.
> Thank you, Flavio and Mike, hope to see you back.
> 
> Cheers,
> 
> Abhishek
> 
> On 01-Mar-2018 17:40, "Erno Kuvaja"  > wrote:
> Hi all,
> 
> At the start of the cycle is good time to have a look of the Glance
> reviewers and based on the discussions amongs the group during and
> before the PTG I'd like to propose following changes:
> 
> 1) Adding Sean McGinnis to Glance core. The current active core team
> has been very positive about including Sean and he feels like he is
> comfortable to take the +2 responsibility on. It might take some more
> time for him to get fully familiar with Glance code base so we will
> leave him room to approve changes to the parts of Glance he feels to
> be ready and grow his expertise across.
> 
> 2) Removing Flavio Percoco from Glance core. Flavio requested to be
> removed already couple of cycles ago and we did beg him to stick
> around to help with the Interoperable Image Import which of he has
> been integral part of designing since the very beginning and due to
> his knowledge of the internals of the Glance tasks. The majority of
> this work is finished and we would like to thank Flavio for his help
> and hard work for Glance community.
> 
> 3) removing Mike Fedosin from glance core. Mike joined back to glance
> ocre when we did desperately need help reviewing changes and we are
> definitely grateful for his efforts to help us out when needed. By the
> looks of it, Mike has moved on to different responsibilities.
> 
> As usual, if the circumstances changes and Flavio or Mike will find
> time and interest to serve our community again, we would be more than
> happy to fast-track them back to the core team.
> 
> I'd like to take the opportunity to give big thanks for all of them
> for their help and contributions to Glance and I do hope seeing them
> all around for the cycles to come.
> 
> I'll leave until next week before doing these changes in case I have
> missed something that has changed in the situation recently.
> 
> best,
> Erno jokke_ Kuvaja
> 
> __
> 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

__
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] [Glance] Changes to Glance core team

[Abhishek Kekane]

Big +1 to Sean, he has been doing wonderful job for us.
Thank you, Flavio and Mike, hope to see you back.

Cheers,

Abhishek

On 01-Mar-2018 17:40, "Erno Kuvaja"  wrote:

> Hi all,
>
> At the start of the cycle is good time to have a look of the Glance
> reviewers and based on the discussions amongs the group during and
> before the PTG I'd like to propose following changes:
>
> 1) Adding Sean McGinnis to Glance core. The current active core team
> has been very positive about including Sean and he feels like he is
> comfortable to take the +2 responsibility on. It might take some more
> time for him to get fully familiar with Glance code base so we will
> leave him room to approve changes to the parts of Glance he feels to
> be ready and grow his expertise across.
>
> 2) Removing Flavio Percoco from Glance core. Flavio requested to be
> removed already couple of cycles ago and we did beg him to stick
> around to help with the Interoperable Image Import which of he has
> been integral part of designing since the very beginning and due to
> his knowledge of the internals of the Glance tasks. The majority of
> this work is finished and we would like to thank Flavio for his help
> and hard work for Glance community.
>
> 3) removing Mike Fedosin from glance core. Mike joined back to glance
> ocre when we did desperately need help reviewing changes and we are
> definitely grateful for his efforts to help us out when needed. By the
> looks of it, Mike has moved on to different responsibilities.
>
> As usual, if the circumstances changes and Flavio or Mike will find
> time and interest to serve our community again, we would be more than
> happy to fast-track them back to the core team.
>
> I'd like to take the opportunity to give big thanks for all of them
> for their help and contributions to Glance and I do hope seeing them
> all around for the cycles to come.
>
> I'll leave until next week before doing these changes in case I have
> missed something that has changed in the situation recently.
>
> best,
> Erno jokke_ Kuvaja
>
> __
> 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] [Glance] Changes to Glance core team

[Brian Rosmaita]

+1 to all the above.

Thanks for Flavio and Mike for all they've done for Glance, and
looking forward to working more with Sean in the future.

cheers,
brian

On Thu, Mar 1, 2018 at 7:09 AM, Erno Kuvaja  wrote:
> Hi all,
>
> At the start of the cycle is good time to have a look of the Glance
> reviewers and based on the discussions amongs the group during and
> before the PTG I'd like to propose following changes:
>
> 1) Adding Sean McGinnis to Glance core. The current active core team
> has been very positive about including Sean and he feels like he is
> comfortable to take the +2 responsibility on. It might take some more
> time for him to get fully familiar with Glance code base so we will
> leave him room to approve changes to the parts of Glance he feels to
> be ready and grow his expertise across.
>
> 2) Removing Flavio Percoco from Glance core. Flavio requested to be
> removed already couple of cycles ago and we did beg him to stick
> around to help with the Interoperable Image Import which of he has
> been integral part of designing since the very beginning and due to
> his knowledge of the internals of the Glance tasks. The majority of
> this work is finished and we would like to thank Flavio for his help
> and hard work for Glance community.
>
> 3) removing Mike Fedosin from glance core. Mike joined back to glance
> ocre when we did desperately need help reviewing changes and we are
> definitely grateful for his efforts to help us out when needed. By the
> looks of it, Mike has moved on to different responsibilities.
>
> As usual, if the circumstances changes and Flavio or Mike will find
> time and interest to serve our community again, we would be more than
> happy to fast-track them back to the core team.
>
> I'd like to take the opportunity to give big thanks for all of them
> for their help and contributions to Glance and I do hope seeing them
> all around for the cycles to come.
>
> I'll leave until next week before doing these changes in case I have
> missed something that has changed in the situation recently.
>
> best,
> Erno jokke_ Kuvaja
>
> __
> 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

[openstack-dev] [Glance] Changes to Glance core team

[Erno Kuvaja]

Hi all,

At the start of the cycle is good time to have a look of the Glance
reviewers and based on the discussions amongs the group during and
before the PTG I'd like to propose following changes:

1) Adding Sean McGinnis to Glance core. The current active core team
has been very positive about including Sean and he feels like he is
comfortable to take the +2 responsibility on. It might take some more
time for him to get fully familiar with Glance code base so we will
leave him room to approve changes to the parts of Glance he feels to
be ready and grow his expertise across.

2) Removing Flavio Percoco from Glance core. Flavio requested to be
removed already couple of cycles ago and we did beg him to stick
around to help with the Interoperable Image Import which of he has
been integral part of designing since the very beginning and due to
his knowledge of the internals of the Glance tasks. The majority of
this work is finished and we would like to thank Flavio for his help
and hard work for Glance community.

3) removing Mike Fedosin from glance core. Mike joined back to glance
ocre when we did desperately need help reviewing changes and we are
definitely grateful for his efforts to help us out when needed. By the
looks of it, Mike has moved on to different responsibilities.

As usual, if the circumstances changes and Flavio or Mike will find
time and interest to serve our community again, we would be more than
happy to fast-track them back to the core team.

I'd like to take the opportunity to give big thanks for all of them
for their help and contributions to Glance and I do hope seeing them
all around for the cycles to come.

I'll leave until next week before doing these changes in case I have
missed something that has changed in the situation recently.

best,
Erno jokke_ Kuvaja

__
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-dev] [glance] priorities for the coming week (23 Feb - 1 March)

[Brian Rosmaita]

Hello Glancers,

RC-3 was released today [0] and we expect it to be the final release
candidate (unless someone finds a critical problem in the next 3
hours).

Priority for this week is preparing for the PTG.  If you can't attend,
Erno has posted a topic list [1] you can look at.  For topics without
specs, feel free to leave questions and comments for items you would
like to see addressed.  For topics with specs proposed, please read
and comment on the gerrit reviews.

Erno has also posted a rough schedule of what we'll be discussing when
[2].  We'll keep an eye on the #openstack-glance IRC channel during
the PTG, but your best bet for getting our attention is to put
comments on the etherpad [1].

The Glance meeting is cancelled on 1 March due to the PTG.

Best wishes for safe travels for those attending the PTG, and for
those at home ... stay safe out there!

cheers,
brian

[0] http://lists.openstack.org/pipermail/openstack-dev/2018-February/127642.html
[1] https://etherpad.openstack.org/p/glance-rocky-ptg
[2] https://ethercalc.openstack.org/5ow7tkekq151

__
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-dev] [glance] glance 16.0.0.0rc3 (queens)

[no-reply]

Hello everyone,

A new release candidate for glance for the end of the Queens
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/glance/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Queens release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/queens release
branch at:

http://git.openstack.org/cgit/openstack/glance/log/?h=stable/queens

Release notes for glance can be found at:

http://docs.openstack.org/releasenotes/glance/




__
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-dev] [glance] priorities for the coming week (16 Feb - 21 Feb)

[Brian Rosmaita]

Hello Glancers,

(1)  Queens RC-2 was tagged Thursday (late Thursday night Pacific
time, but Thursday nonetheless).  A good place to concentrate testing
effort is on the URI filtering feature of the web-download import
method.  Remember that if you build a devstack, set WSGI_MODE=mod_wsgi
in your local.conf so that the import task will be processed.

(2)  We're aiming for RC-3 for Monday.  There will be some
documentation and releasenote update patches, and patches for the
glance-manage tool.  (And any image import bugs found during testing.)
 Keep an eye on the etherpad for stuff to review:
https://etherpad.openstack.org/p/glance-queens-rc1-patches
(yes, that's "rc1" in the url, I didn't want to waste a perfectly good etherpad)

(3)  Reminder: Erno will be making final decisions on what will happen
for Glance at the PTG on Monday morning.  So get your topic proposals
and votes for the stuff you want to discuss (or have discussed, if
unfortunately you won't be there) on the etherpad before 0900 UTC
Monday:
https://etherpad.openstack.org/p/glance-rocky-ptg-planning

cheers,
brian

__
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-dev] [glance] glance 16.0.0.0rc2 (queens)

[no-reply]

Hello everyone,

A new release candidate for glance for the end of the Queens
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/glance/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Queens release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/queens release
branch at:

http://git.openstack.org/cgit/openstack/glance/log/?h=stable/queens

Release notes for glance can be found at:

http://docs.openstack.org/releasenotes/glance/




__
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-dev] [glance] priorities for the coming week (9 Feb - 15 Feb)

[Brian Rosmaita]

Congratulations to Erno for his election as the Rocky PTL!  Erno is
taking over PTG planning, so don't forget to add ideas to the planning
etherpad:
https://etherpad.openstack.org/p/glance-rocky-ptg-planning

The first Release Candidate for the Queens edition of Glance was
released today and the stable/queens branch was cut.

Our focus is still on Queens this week.  It would be a good idea to
give RC-1 a workout, paying particular attention to interoperable
image import and the glance-manage and glance-scrubber tools, which
underwent some refactoring and enhancements this cycle.

We'll continue to track the development toward RC-2 on this etherpad:
https://etherpad.openstack.org/p/glance-queens-rc1-patches

Add any bugs you find that are release critical to that etherpad so
that the core team can verify that they need to be backported to
stable/queens.

There will definitely be an RC-2, which will contain whatever we come
up with to address https://bugs.launchpad.net/glance/+bug/1747869

But don't let that stop you from testing out RC-1!

cheers,
brian

__
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-dev] [glance] glance 16.0.0.0rc1 (queens)

[no-reply]

Hello everyone,

A new release candidate for glance for the end of the Queens
cycle is available!  You can find the source code tarball at:

https://tarballs.openstack.org/glance/

Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally released as the
final Queens release. You are therefore strongly
encouraged to test and validate this tarball!

Alternatively, you can directly test the stable/queens release
branch at:

http://git.openstack.org/cgit/openstack/glance/log/?h=stable/queens

Release notes for glance can be found at:

http://docs.openstack.org/releasenotes/glance/




__
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] [glance][cinder]Question about cinder as glance store

[Gorka Eguileor]

On 07/02, Erlon Cruz wrote:
> That will depend on the Cinder/OS-brick iscsiadm versions right? Can you
> tell what are the versions from where the problem was fixed?
>
> Erlon
>

Hi,

Like you said it depends on your Cinder and OS-Brick versions, and the
open-iscsi package will be different depending on your distro, for RHOS
7.4 this is iscsi-initiator-utils version 6.2.0.874-2 or later.

Things working fine may also depend on your multipath and Cinder/Nova
configuration as well as LVM filters (if your deployment can have images
that have LVM).

I think that's all that need to be properly setup.

Cheers,
Gorka.

> 2018-02-07 8:27 GMT-02:00 Gorka Eguileor :
>
> > On 07/02, Rikimaru Honjo wrote:
> > > Hello,
> > >
> > > I'm planning to use cinder as glance store.
> > > And, I'll setup cinder to connect storage by iSCSI multipath.
> > >
> > > In this case, can I run glance-api and cinder-volume on the same node?
> > >
> > > In my understanding, glance-api will attach a volume to own node and
> > > write a uploaded image to the volume if glance backend is cinder.
> > > I afraid that the race condition of cinder-volume's iSCSI operations
> > > and glance-api's iSCSI operations.
> > > Is there possibility of occurring it?
> > > --
> > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> > > Rikimaru Honjo
> > > E-mail:honjo.rikim...@po.ntt-tx.co.jp
> > >
> > >
> > >
> > > 
> > __
> > > 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
> >
> > Hi,
> >
> > When properly set with the right configuration and the right system and
> > OpenStack packages, Cinder, OS-Brick, and Nova no longer have race
> > conditions with iSCSI operations anymore (single or multipathed), not
> > even with drivers that do "shared target".
> >
> > So I would assume that Glance won't have any issues either as long as
> > it's properly making the Cinder and OS-Brick calls.
> >
> > Cheers,
> > Gorka.
> >
> > __
> > 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


__
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] [glance][cinder]Question about cinder as glance store

[Rikimaru Honjo]

Hello Gorka,

Thank you for replying!
I'll try to run glance-api and cinder-volume on the same node
according to your information.

On 2018/02/07 19:27, Gorka Eguileor wrote:

On 07/02, Rikimaru Honjo wrote:

Hello,

I'm planning to use cinder as glance store.
And, I'll setup cinder to connect storage by iSCSI multipath.

In this case, can I run glance-api and cinder-volume on the same node?

In my understanding, glance-api will attach a volume to own node and
write a uploaded image to the volume if glance backend is cinder.
I afraid that the race condition of cinder-volume's iSCSI operations
and glance-api's iSCSI operations.
Is there possibility of occurring it?
--
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Rikimaru Honjo
E-mail:honjo.rikim...@po.ntt-tx.co.jp



__
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


Hi,

When properly set with the right configuration and the right system and
OpenStack packages, Cinder, OS-Brick, and Nova no longer have race
conditions with iSCSI operations anymore (single or multipathed), not
even with drivers that do "shared target".

So I would assume that Glance won't have any issues either as long as
it's properly making the Cinder and OS-Brick calls.

Cheers,
Gorka.

__
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




--
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Rikimaru Honjo
E-mail:honjo.rikim...@po.ntt-tx.co.jp



__
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] [glance][cinder]Question about cinder as glance store

[Erlon Cruz]

That will depend on the Cinder/OS-brick iscsiadm versions right? Can you
tell what are the versions from where the problem was fixed?

Erlon

2018-02-07 8:27 GMT-02:00 Gorka Eguileor :

> On 07/02, Rikimaru Honjo wrote:
> > Hello,
> >
> > I'm planning to use cinder as glance store.
> > And, I'll setup cinder to connect storage by iSCSI multipath.
> >
> > In this case, can I run glance-api and cinder-volume on the same node?
> >
> > In my understanding, glance-api will attach a volume to own node and
> > write a uploaded image to the volume if glance backend is cinder.
> > I afraid that the race condition of cinder-volume's iSCSI operations
> > and glance-api's iSCSI operations.
> > Is there possibility of occurring it?
> > --
> > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> > Rikimaru Honjo
> > E-mail:honjo.rikim...@po.ntt-tx.co.jp
> >
> >
> >
> > 
> __
> > 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
>
> Hi,
>
> When properly set with the right configuration and the right system and
> OpenStack packages, Cinder, OS-Brick, and Nova no longer have race
> conditions with iSCSI operations anymore (single or multipathed), not
> even with drivers that do "shared target".
>
> So I would assume that Glance won't have any issues either as long as
> it's properly making the Cinder and OS-Brick calls.
>
> Cheers,
> Gorka.
>
> __
> 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] [glance][cinder]Question about cinder as glance store

[Gorka Eguileor]

On 07/02, Rikimaru Honjo wrote:
> Hello,
>
> I'm planning to use cinder as glance store.
> And, I'll setup cinder to connect storage by iSCSI multipath.
>
> In this case, can I run glance-api and cinder-volume on the same node?
>
> In my understanding, glance-api will attach a volume to own node and
> write a uploaded image to the volume if glance backend is cinder.
> I afraid that the race condition of cinder-volume's iSCSI operations
> and glance-api's iSCSI operations.
> Is there possibility of occurring it?
> --
> _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> Rikimaru Honjo
> E-mail:honjo.rikim...@po.ntt-tx.co.jp
>
>
>
> __
> 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

Hi,

When properly set with the right configuration and the right system and
OpenStack packages, Cinder, OS-Brick, and Nova no longer have race
conditions with iSCSI operations anymore (single or multipathed), not
even with drivers that do "shared target".

So I would assume that Glance won't have any issues either as long as
it's properly making the Cinder and OS-Brick calls.

Cheers,
Gorka.

__
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-dev] [glance][cinder]Question about cinder as glance store

[Rikimaru Honjo]

Hello,

I'm planning to use cinder as glance store.
And, I'll setup cinder to connect storage by iSCSI multipath.

In this case, can I run glance-api and cinder-volume on the same node?

In my understanding, glance-api will attach a volume to own node and
write a uploaded image to the volume if glance backend is cinder.
I afraid that the race condition of cinder-volume's iSCSI operations
and glance-api's iSCSI operations.
Is there possibility of occurring it?
--
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Rikimaru Honjo
E-mail:honjo.rikim...@po.ntt-tx.co.jp



__
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-dev] [glance] glance-manage db check feature needs reviews

[Brian Rosmaita]

Hello Glancers,

Please take a look at Bhagyashri's patch, which was given a FFE.

There's a slight deviation from the spec, so I need feedback about
whether this is acceptable (spoiler alert: I think it's OK).  So
please comment on that aspect of the patch even if you don't have time
at the moment to review the code thoroughly.  See my comment on PS11
for details.

thanks,
brian

__
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] [glance] FFE request for --check feature

[Brian Rosmaita]

Thanks for following up on this, Abhishek.  After our discussion
approving this at the weekly meeting, I completely forgot to send out
an update.  As Abhishek indicated, the discussion was positive, and
this FFE is APPROVED.

cheers,
brian


On Mon, Feb 5, 2018 at 3:56 AM, Abhishek Kekane  wrote:
> Sorry, Forgot to add meeting logs link in previous mail.
>
> Here it is;
> http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-02-01-14.01.log.html#l-164
>
> Thank you,
>
> Abhishek Kekane
>
> On Mon, Feb 5, 2018 at 12:30 PM, Abhishek Kekane  wrote:
>>
>> We have discussed this in glance weekly meeting [1] and most of the core
>> reviewers are inclined towards accepting this FFE.
>>
>> +1 from my side as this --check command will be very helpful for
>> operators.
>>
>> Thank you Bhagyashri for working on this.
>>
>> Abhishek Kekane
>>
>> On Wed, Jan 31, 2018 at 7:29 PM, Shewale, Bhagyashri
>>  wrote:
>>>
>>> Hi Glance Folks,
>>>
>>> I'm requesting an Feature Freeze Exception for the lite-spec
>>> http://specs.openstack.org/openstack/glance-specs/specs/untargeted/glance/lite-spec-db-sync-check.html
>>> which is implemented by https://review.openstack.org/#/c/455837/8/
>>>
>>> Regards,
>>> Bhagyashri Shewale
>>>
>>> __
>>> Disclaimer: This email and any attachments are sent in strictest
>>> confidence
>>> for the sole use of the addressee and may contain legally privileged,
>>> confidential, and proprietary data. If you are not the intended
>>> recipient,
>>> please advise the sender by replying promptly to this email and then
>>> delete
>>> and destroy this email and any attachments without any further use,
>>> copying
>>> or forwarding.
>>>
>>> __
>>> 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
>

__
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] [glance] FFE request for --check feature

[Abhishek Kekane]

Sorry, Forgot to add meeting logs link in previous mail.

Here it is;
http://eavesdrop.openstack.org/meetings/glance/2018/glance.2018-02-01-14.01.log.html#l-164

Thank you,

Abhishek Kekane

On Mon, Feb 5, 2018 at 12:30 PM, Abhishek Kekane  wrote:

> We have discussed this in glance weekly meeting [1] and most of the core
> reviewers are inclined towards accepting this FFE.
>
> +1 from my side as this --check command will be very helpful for operators.
>
> Thank you Bhagyashri for working on this.
>
> Abhishek Kekane
>
> On Wed, Jan 31, 2018 at 7:29 PM, Shewale, Bhagyashri <
> bhagyashri.shew...@nttdata.com> wrote:
>
>> Hi Glance Folks,
>>
>> I'm requesting an Feature Freeze Exception for the lite-spec
>> http://specs.openstack.org/openstack/glance-specs/specs/unta
>> rgeted/glance/lite-spec-db-sync-check.html
>> which is implemented by https://review.openstack.org/#/c/455837/8/
>>
>> Regards,
>> Bhagyashri Shewale
>>
>> __
>> Disclaimer: This email and any attachments are sent in strictest
>> confidence
>> for the sole use of the addressee and may contain legally privileged,
>> confidential, and proprietary data. If you are not the intended recipient,
>> please advise the sender by replying promptly to this email and then
>> delete
>> and destroy this email and any attachments without any further use,
>> copying
>> or forwarding.
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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] [glance] FFE request for --check feature

[Abhishek Kekane]

We have discussed this in glance weekly meeting [1] and most of the core
reviewers are inclined towards accepting this FFE.

+1 from my side as this --check command will be very helpful for operators.

Thank you Bhagyashri for working on this.

Abhishek Kekane

On Wed, Jan 31, 2018 at 7:29 PM, Shewale, Bhagyashri <
bhagyashri.shew...@nttdata.com> wrote:

> Hi Glance Folks,
>
> I'm requesting an Feature Freeze Exception for the lite-spec
> http://specs.openstack.org/openstack/glance-specs/specs/
> untargeted/glance/lite-spec-db-sync-check.html
> which is implemented by https://review.openstack.org/#/c/455837/8/
>
> Regards,
> Bhagyashri Shewale
>
> __
> Disclaimer: This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data. If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding.
> __
> 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] [Glance][PTL] Nomination for Glance PTL for Rocky cycle

[Abhishek Kekane]

All the best Erno, Long may you reign ;)

Abhishek

On 31-Jan-2018 18:38, "Erno Kuvaja"  wrote:

> Hi all,
>
> After lengthy discussions and careful thinking I have thrown my name
> into the hat for Glance PTL. You can find my thoughts from the
> candidacy patch https://review.openstack.org/#/c/539196/
>
> I'd like to take the opportunity to thank most recently Brian but also
> our other former PTLs from Mark to Flavio and everyone in between that
> I've had pleasure to work with for running the show and showing the
> way. You guys have been integral part of me growing to the point where
> I dare to do this.
>
> Nominations are still open and having an election is healthy so if any
> of you are still thinking of nominating yourselves, there's time until
> Fri. Don't miss the deadline or you will get me by default ;)
>
> Best,
> Erno jokke Kuvaja
>
> __
> 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

[openstack-dev] [glance] FFE request for --check feature

[Shewale, Bhagyashri]

Hi Glance Folks,

I'm requesting an Feature Freeze Exception for the lite-spec 
http://specs.openstack.org/openstack/glance-specs/specs/untargeted/glance/lite-spec-db-sync-check.html
  
which is implemented by https://review.openstack.org/#/c/455837/8/ 

Regards,
Bhagyashri Shewale

__
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.
__
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] [glance] Q-3 milestone released

[Brian Rosmaita]

On Tue, Jan 30, 2018 at 11:39 PM, Brian Rosmaita
 wrote:
[snip]
> Glance cores, please do not merge any patches until after
> https://review.openstack.org/#/c/536630/ has merged.

The patch merged at 08:15UTC today.  Merge away (subject to common
sense and the fact that we're in RC time).

cheers,
brian

__
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-dev] [Glance][PTL] Nomination for Glance PTL for Rocky cycle

[Erno Kuvaja]

Hi all,

After lengthy discussions and careful thinking I have thrown my name
into the hat for Glance PTL. You can find my thoughts from the
candidacy patch https://review.openstack.org/#/c/539196/

I'd like to take the opportunity to thank most recently Brian but also
our other former PTLs from Mark to Flavio and everyone in between that
I've had pleasure to work with for running the show and showing the
way. You guys have been integral part of me growing to the point where
I dare to do this.

Nominations are still open and having an election is healthy so if any
of you are still thinking of nominating yourselves, there's time until
Fri. Don't miss the deadline or you will get me by default ;)

Best,
Erno jokke Kuvaja

__
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-dev] [glance] Q-3 milestone released

[Brian Rosmaita]

Glance 16.0.0.0b3 was released today,  The tag was created at this commit:
http://git.openstack.org/cgit/openstack/glance/commit/?id=631add1ba849eac67ecb36ea4c90b57a300a96fa
which is dated Thu, 18 Jan 2018 12:09:11 +

As you'll notice, that was about 2 weeks ago.  Which prompts the
question, why did we wait so long to release it.

Q: Why that commit?
A: It's the last commit when the glance functional gates jobs were
still working.

Q: Why didn't we release it 2 weeks ago?
A: The Q-3 release marks the feature freeze.  Any code committed after
that point should be either a release-critical bug or something with a
Feature Freeze Exception.  So you really don't want to release Q-3
early.

Q: What's the deal with the glance functional gate jobs?
A: There are two patches fixing them, but they have to go through the
'integrated' queue before they can merge, and we've had some bad luck
over the past few days ... they've made it to the top of the queue to
be processed when something bad happened and they had to start over.
They're being processed again right now (keep your fingers crossed).

Q: What about my commits that show up after
631add1ba849eac67ecb36ea4c90b57a300a96fa?
A: I will be sending out FFEs or marking the bugs for RC1, as appropriate.

Glance cores, please do not merge any patches until after
https://review.openstack.org/#/c/536630/ has merged.


thanks,
brian

__
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] [glance] PTL non-candidacy

[Paul Grist]

On Mon, Jan 29, 2018 at 2:18 PM, Brian Rosmaita 
wrote:

> I've been PTL of Glance through some rocky times, but have decided not
> to stand for election for the Rocky cycle.  My plan is to stick
> around, attend to my duties as a glance core contributor, and support
> my successor in whatever way I can to make for a smooth transition.
> After three consecutive cycles of me, it's time for some new ideas and
> new approaches.
>
> For anyone out there who hasn't contributed to Glance yet, the Glance
> community is friendly and welcoming, and we've got a backlog of
> "untargeted" specs ready for you to pick up.  Weekly meetings are
> 14:00 UTC on Thursdays in #openstack-meeting-4.
>
> cheers,
> brian
>

Many thanks for all the work you've done for glance and the community. Your
leadership and commitment was remarkable at the most challenging of times
this past year.  Glad to hear you are staying with Glance!

Paul

>
> __
> 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] [glance] PTL non-candidacy

[Doug Hellmann]

Excerpts from Brian Rosmaita's message of 2018-01-29 14:18:18 -0500:
> I've been PTL of Glance through some rocky times, but have decided not
> to stand for election for the Rocky cycle.  My plan is to stick
> around, attend to my duties as a glance core contributor, and support
> my successor in whatever way I can to make for a smooth transition.
> After three consecutive cycles of me, it's time for some new ideas and
> new approaches.
> 
> For anyone out there who hasn't contributed to Glance yet, the Glance
> community is friendly and welcoming, and we've got a backlog of
> "untargeted" specs ready for you to pick up.  Weekly meetings are
> 14:00 UTC on Thursdays in #openstack-meeting-4.
> 
> cheers,
> brian
> 

Thank you for carrying the mantle for so long, Brian. I know it
hasn't necessarily been easy but you've dealt with the challenges
well and helped the team move to a healthier state than it was in
when you started in the role.

Doug

__
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] [glance] PTL non-candidacy

[Carter, Kevin]

++ Thanks for leadership within Glance and everything else you've done in
the community!


--

Kevin Carter
IRC: Cloudnull

On Mon, Jan 29, 2018 at 1:27 PM, Sean McGinnis 
wrote:

> On Mon, Jan 29, 2018 at 02:18:18PM -0500, Brian Rosmaita wrote:
> > I've been PTL of Glance through some rocky times, but have decided not
> > to stand for election for the Rocky cycle.  My plan is to stick
> > around, attend to my duties as a glance core contributor, and support
> > my successor in whatever way I can to make for a smooth transition.
> > After three consecutive cycles of me, it's time for some new ideas and
> > new approaches.
> >
> > For anyone out there who hasn't contributed to Glance yet, the Glance
> > community is friendly and welcoming, and we've got a backlog of
> > "untargeted" specs ready for you to pick up.  Weekly meetings are
> > 14:00 UTC on Thursdays in #openstack-meeting-4.
> >
> > cheers,
> > brian
> >
>
> Thanks for all your hard work as Glance PTL Brian. Great to hear you are
> not
> going anywhere.
>
>
> __
> 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] [glance] PTL non-candidacy

[Abhishek Kekane]

Thanks so much for your remarkable work for glance for the couple of
cycles. You have introduced very good processes like weekly priorities
which helped community members to keep focused on priorities.  It’s my
pleasure to work with you, and yet I need to learn lot from you. Wish you
all the best Brian!

Cheers,

Abhishek

On 30-Jan-2018 00:49, "Brian Rosmaita"  wrote:

> I've been PTL of Glance through some rocky times, but have decided not
> to stand for election for the Rocky cycle.  My plan is to stick
> around, attend to my duties as a glance core contributor, and support
> my successor in whatever way I can to make for a smooth transition.
> After three consecutive cycles of me, it's time for some new ideas and
> new approaches.
>
> For anyone out there who hasn't contributed to Glance yet, the Glance
> community is friendly and welcoming, and we've got a backlog of
> "untargeted" specs ready for you to pick up.  Weekly meetings are
> 14:00 UTC on Thursdays in #openstack-meeting-4.
>
> cheers,
> brian
>
> __
> 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] [glance] PTL non-candidacy

[Sean McGinnis]

On Mon, Jan 29, 2018 at 02:18:18PM -0500, Brian Rosmaita wrote:
> I've been PTL of Glance through some rocky times, but have decided not
> to stand for election for the Rocky cycle.  My plan is to stick
> around, attend to my duties as a glance core contributor, and support
> my successor in whatever way I can to make for a smooth transition.
> After three consecutive cycles of me, it's time for some new ideas and
> new approaches.
> 
> For anyone out there who hasn't contributed to Glance yet, the Glance
> community is friendly and welcoming, and we've got a backlog of
> "untargeted" specs ready for you to pick up.  Weekly meetings are
> 14:00 UTC on Thursdays in #openstack-meeting-4.
> 
> cheers,
> brian
> 

Thanks for all your hard work as Glance PTL Brian. Great to hear you are not
going anywhere.


__
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-dev] [glance] PTL non-candidacy

[Brian Rosmaita]

I've been PTL of Glance through some rocky times, but have decided not
to stand for election for the Rocky cycle.  My plan is to stick
around, attend to my duties as a glance core contributor, and support
my successor in whatever way I can to make for a smooth transition.
After three consecutive cycles of me, it's time for some new ideas and
new approaches.

For anyone out there who hasn't contributed to Glance yet, the Glance
community is friendly and welcoming, and we've got a backlog of
"untargeted" specs ready for you to pick up.  Weekly meetings are
14:00 UTC on Thursdays in #openstack-meeting-4.

cheers,
brian

__
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] [glance] functional gate situation

[Brian Rosmaita]

Update on the 24 hours since the last update:

tl;dr: glance cores, do not approve any substantial code changes until
after the functional tests are restored.  See below for details.

On Tue, Jan 23, 2018 at 8:09 PM, Brian Rosmaita
 wrote:
> Update on the last 24 hours:
>
> (1) Sean's patch splitting the unit and functional tests in tox has merged.

Still good.

> (2) My patch to restore the functional test gate jobs ran into a
> problem, namely, that one of the py35 tests suddenly begun failing in
> the gate, and I haven't been able to reproduce it locally.  I started
> looking into it, but this problem doesn't make any sense at all
> (you'll see what I mean when you get a chance to look at it), so I put
> up a patch to skip the failing test:
> https://review.openstack.org/#/c/536939/
> It's passed the check and I ninja-approved it, so it's in the gate now.

It's still in the gate.  Due to an unfortunate concatenation of
circumstances, today's gerrit restart occurred at the same time zuul
had passed this patch, and the success was not recorded, and it had to
be rechecked.  I believe it was moved up in the queue (thanks, infra
team!), but nonetheless it's been in the integrated queue for > 7
hours now, with zuul projecting completion in 58 minutes.

> (3) I edited the patch restoring the functional gate jobs to not run
> the py27 tests at all (no sense wasting any time until we know they
> have a chance of working).  At least we can run the py35 functional
> tests (except for the one being skipped):
> https://review.openstack.org/#/c/536630/
> (I rebased it on the skip-test patch, it's in the check now.)

This one still depends on #2, so no action yet.

> I'd prefer that nothing else be merged for glance until we get the
> functional gate restored, which will hopefully happen sometime this
> evening.  I'll keep an eye on (2) and (3) for the next few hours.

I'm still hopeful, though less hopeful than I was.  In any case, do
not approve any substantial changes until the functional tests have
been restored.

> (4) With Sean's patch merged, I put up a patch to the requirements
> repo reverting the change that made the cross-glance-py27 test
> non-voting:
> https://review.openstack.org/#/c/536946/
> That's been approved and is in the gate now.

This patch got caught in the gerrit restart, too, and is being
re-processed (and it looks like it's going to fail, although not
because of glance ... the cross-glance-py* jobs were both successful.

> So, we've got 2 outstanding bugs:
> py27 functional test failures: https://bugs.launchpad.net/glance/+bug/1744824
> py35 functional test failure: https://bugs.launchpad.net/glance/+bug/1745003
>
> ... and of course the regular stuff that was mentioned on the priority
> email for this week:
> http://lists.openstack.org/pipermail/openstack-dev/2018-January/126353.html

These continue to be areas of active interest.

On the plus side, we did release the python-glanceclient 2.9.1 today.

> cheers,
> brian

__
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] [glance] py27 gate situation

[Abhishek Kekane]

Confirmed that no issue in loading the middleware, problem lies somewhere
else.
Still trying to figure it out.

Thanks & Regards,

Abhishek

On Tue, Jan 23, 2018 at 4:00 PM, Abhishek Kekane  wrote:

> I have tried to debug this in my environment but so far not able to find
> the reason.
> While starting the api service from functional tests it fails to load
> middleware 'rootapp' from api-paste.ini
>
> What I have done is added below lines in tox.ini to enable debugging of
> functional tests
>
> [testenv:debug-functional]
> basepython = python2.7
> setenv =
>   TEST_PATH = ./glance/tests/functional
> commands = oslo_debug_helper {posargs}
>
> and added pdb at
> 'https://github.com/openstack/glance/blob/master/glance/test
> s/functional/__init__.py#L770'
>
> While executing each functional test, it creates the temp directory at
> location /tmp/tmp* where it stores config, paste.ini and other required
> files.
>
> So far no luck to find the exact cause.
>
> Thanks & Regards,
>
> Abhishek
>
>
>
> On Tue, Jan 23, 2018 at 5:37 AM, Brian Rosmaita <
> rosmaita.foss...@gmail.com> wrote:
>
>> Looks like something changed in a distro dependency over the weekend
>> and the glance py27 gate is failing.
>>
>> I did a dist-upgrade in a new Ubuntu 16.04.3 vm, and was able to
>> reproduce the failures locally.  I'll continue looking, but it's EOD
>> where I am, so I wanted to make sure this info is available to the
>> people whose day is about to begin.  The failures are confined to the
>> py27 functional tests.  Unit tests pass, as do all the py35 tests.
>>
>> The requirements team has merged a change making the cross-glance-py27
>> job non-voting:
>> https://review.openstack.org/#/c/536082/
>> Thus, this issue isn't holding up requirements changes, but it's still
>> pretty urgent for us to figure out because I don't like us running
>> around naked with respect to requirements changes that could affect
>> glance running under py27.
>>
>> Here's what I think we should do:
>>
>> (1) Sean has had a patch up for a while separating out the unit tests
>> from the functional tests.  I think it's a good idea.  If you are
>> aware of a reason why they should NOT be separated, please comment on
>> the patch:
>> https://review.openstack.org/#/c/474816/
>> I'd like to merge this soon so we can at least restore py27 unit tests
>> to the requirements gate.  We can always revert if it turns out that
>> there is a really good reason for not separating out the functional
>> tests.
>>
>> (2) I've got a patch up that depends on Sean's patch and restores the
>> functional test gate jobs to the glance .zuul.yaml file (though it
>> makes the py27 functional tests non-voting):
>> https://review.openstack.org/#/c/536630/
>>
>> (3) Continue to work on https://bugs.launchpad.net/glance/+bug/1744824
>> to figure out why the py27 functional tests are failing.  As far as I
>> can tell, it looks like a distro package issue.
>>
>>
>> thanks,
>> brian
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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

[openstack-dev] [glance] functional gate situation

[Brian Rosmaita]

Update on the last 24 hours:

(1) Sean's patch splitting the unit and functional tests in tox has merged.

(2) My patch to restore the functional test gate jobs ran into a
problem, namely, that one of the py35 tests suddenly begun failing in
the gate, and I haven't been able to reproduce it locally.  I started
looking into it, but this problem doesn't make any sense at all
(you'll see what I mean when you get a chance to look at it), so I put
up a patch to skip the failing test:
https://review.openstack.org/#/c/536939/
It's passed the check and I ninja-approved it, so it's in the gate now.

(3) I edited the patch restoring the functional gate jobs to not run
the py27 tests at all (no sense wasting any time until we know they
have a chance of working).  At least we can run the py35 functional
tests (except for the one being skipped):
https://review.openstack.org/#/c/536630/
(I rebased it on the skip-test patch, it's in the check now.)

I'd prefer that nothing else be merged for glance until we get the
functional gate restored, which will hopefully happen sometime this
evening.  I'll keep an eye on (2) and (3) for the next few hours.

(4) With Sean's patch merged, I put up a patch to the requirements
repo reverting the change that made the cross-glance-py27 test
non-voting:
https://review.openstack.org/#/c/536946/
That's been approved and is in the gate now.

So, we've got 2 outstanding bugs:
py27 functional test failures: https://bugs.launchpad.net/glance/+bug/1744824
py35 functional test failure: https://bugs.launchpad.net/glance/+bug/1745003

... and of course the regular stuff that was mentioned on the priority
email for this week:
http://lists.openstack.org/pipermail/openstack-dev/2018-January/126353.html


cheers,
brian

__
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] [glance] py27 gate situation

[Abhishek Kekane]

I have tried to debug this in my environment but so far not able to find
the reason.
While starting the api service from functional tests it fails to load
middleware 'rootapp' from api-paste.ini

What I have done is added below lines in tox.ini to enable debugging of
functional tests

[testenv:debug-functional]
basepython = python2.7
setenv =
  TEST_PATH = ./glance/tests/functional
commands = oslo_debug_helper {posargs}

and added pdb at
'https://github.com/openstack/glance/blob/master/glance/
tests/functional/__init__.py#L770'

While executing each functional test, it creates the temp directory at
location /tmp/tmp* where it stores config, paste.ini and other required
files.

So far no luck to find the exact cause.

Thanks & Regards,

Abhishek



On Tue, Jan 23, 2018 at 5:37 AM, Brian Rosmaita 
wrote:

> Looks like something changed in a distro dependency over the weekend
> and the glance py27 gate is failing.
>
> I did a dist-upgrade in a new Ubuntu 16.04.3 vm, and was able to
> reproduce the failures locally.  I'll continue looking, but it's EOD
> where I am, so I wanted to make sure this info is available to the
> people whose day is about to begin.  The failures are confined to the
> py27 functional tests.  Unit tests pass, as do all the py35 tests.
>
> The requirements team has merged a change making the cross-glance-py27
> job non-voting:
> https://review.openstack.org/#/c/536082/
> Thus, this issue isn't holding up requirements changes, but it's still
> pretty urgent for us to figure out because I don't like us running
> around naked with respect to requirements changes that could affect
> glance running under py27.
>
> Here's what I think we should do:
>
> (1) Sean has had a patch up for a while separating out the unit tests
> from the functional tests.  I think it's a good idea.  If you are
> aware of a reason why they should NOT be separated, please comment on
> the patch:
> https://review.openstack.org/#/c/474816/
> I'd like to merge this soon so we can at least restore py27 unit tests
> to the requirements gate.  We can always revert if it turns out that
> there is a really good reason for not separating out the functional
> tests.
>
> (2) I've got a patch up that depends on Sean's patch and restores the
> functional test gate jobs to the glance .zuul.yaml file (though it
> makes the py27 functional tests non-voting):
> https://review.openstack.org/#/c/536630/
>
> (3) Continue to work on https://bugs.launchpad.net/glance/+bug/1744824
> to figure out why the py27 functional tests are failing.  As far as I
> can tell, it looks like a distro package issue.
>
>
> thanks,
> brian
>
> __
> 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

[openstack-dev] [glance] py27 gate situation

[Brian Rosmaita]

Looks like something changed in a distro dependency over the weekend
and the glance py27 gate is failing.

I did a dist-upgrade in a new Ubuntu 16.04.3 vm, and was able to
reproduce the failures locally.  I'll continue looking, but it's EOD
where I am, so I wanted to make sure this info is available to the
people whose day is about to begin.  The failures are confined to the
py27 functional tests.  Unit tests pass, as do all the py35 tests.

The requirements team has merged a change making the cross-glance-py27
job non-voting:
https://review.openstack.org/#/c/536082/
Thus, this issue isn't holding up requirements changes, but it's still
pretty urgent for us to figure out because I don't like us running
around naked with respect to requirements changes that could affect
glance running under py27.

Here's what I think we should do:

(1) Sean has had a patch up for a while separating out the unit tests
from the functional tests.  I think it's a good idea.  If you are
aware of a reason why they should NOT be separated, please comment on
the patch:
https://review.openstack.org/#/c/474816/
I'd like to merge this soon so we can at least restore py27 unit tests
to the requirements gate.  We can always revert if it turns out that
there is a really good reason for not separating out the functional
tests.

(2) I've got a patch up that depends on Sean's patch and restores the
functional test gate jobs to the glance .zuul.yaml file (though it
makes the py27 functional tests non-voting):
https://review.openstack.org/#/c/536630/

(3) Continue to work on https://bugs.launchpad.net/glance/+bug/1744824
to figure out why the py27 functional tests are failing.  As far as I
can tell, it looks like a distro package issue.


thanks,
brian

__
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-dev] [glance] priorities for the coming week (18 Jan - 24 Jan)

[Brian Rosmaita]

As discussed at today's Glance meeting, the Q-3 milestone is next
week.  Please focus on the following:

(1) image metadata injection
https://review.openstack.org/#/c/527635/

(2) interoperable image import
https://review.openstack.org/532502
https://review.openstack.org/532501
may be some more, watch the ML

(3) use only E-M-C strategy in glance-manage tool
not sure the patch is up yet, will leave a note on
https://review.openstack.org/#/c/433934

Have a good week!
brian

__
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] [glance][oslo][requirements] [ironic]oslo.serialization fails with glance

[Matthew Thode]

On 18-01-17 21:24:12, John Villalovos wrote:
> I have updated the bug with info I found out:
> https://bugs.launchpad.net/oslo.serialization/+bug/1728368
> 
> Also I did a test patch with a proposed change:
> https://review.openstack.org/#/c/535166/
> 
> This patch causes the unit tests to work.
> 
> As a note there is a deprecation warning in the current code (without my
> patch) that says in the future it will raise a ValueError() as can be seen
> in a recently merged patch:
> http://logs.openstack.org/72/533872/6/check/openstack-tox-py27/4709e32/job-output.txt.gz#_2018-01-16_13_10_38_931593
> 
> The test patch gets rid of that deprecation warning for the exceptions.
> 
> Though I did see another warning about the "Response" object:
> http://logs.openstack.org/66/535166/2/check/openstack-tox-py35/33d0827/job-output.txt.gz#_2018-01-18_05_13_52_603162
> 
> But that is for someone else to figure out :)
> 
> 
> 
> On Wed, Jan 17, 2018 at 7:13 PM, ChangBo Guo  wrote:
> 
> > add Ironic team  in the loop
> >
> > the revert patch got -1 from  ironic folks , more details  please see the
> > comments in https://review.openstack.org/534736
> > The possible solution is to figure out why  the change break Glance's unit
> > test.  which side should be fixed.
> >
> >
> >
> > 2018-01-17 20:14 GMT+08:00 ChangBo Guo :
> >
> >> I dig a little.  It shows success when updating constraint to 2.21.2 [1]
> >> but failure when updating constraint to 2.22.0 [2].   according to release
> >> information [3].
> >> It means 2.21.1 works with glance test but  2.21.2 doesn't work well with
> >> glance. The only issue patch is https://github.com/openstack/o
> >> slo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8.
> >>
> >>
> >> [1] https://review.openstack.org/514833
> >> [2] https://review.openstack.org/#/c/525136
> >> [3] https://github.com/openstack/releases/blob/master/deliverabl
> >> es/queens/oslo.serialization.yaml
> >>
> >>
> >> Actions:
> >>
> >> Block  oslo.serialization  version  2.21.2,  2.22.0, 2. 23.0in
> >> https://review.openstack.org/534739
> >> Revert c1a7079c26d27a2e46cca26963d3d9aa040bdbe8 in
> >> https://review.openstack.org/534736
> >>
> >>
> >>
> >>
> >> 2018-01-16 23:35 GMT+08:00 Matthew Thode :
> >>
> >>> On 18-01-16 19:12:16, ChangBo Guo wrote:
> >>> > What's the issue for Glance,  any bug link ?
> >>> >
> >>> > 2018-01-16 0:12 GMT+08:00 Matthew Thode :
> >>> >
> >>> > > On 18-01-13 00:41:28, Matthew Thode wrote:
> >>> > > > https://review.openstack.org/531788 is the review we are seeing
> >>> it in,
> >>> > > > but 2.22.0 failed as well.
> >>> > > >
> >>> > > > I'm guessing it was introduced in either
> >>> > > >
> >>> > > > https://github.com/openstack/oslo.serialization/commit/
> >>> > > c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
> >>> > > > or
> >>> > > > https://github.com/openstack/oslo.serialization/commit/
> >>> > > cdb2f60d26e3b65b6370f87b2e9864045651c117
> >>> > >
> >>> > > bamp
> >>> > >
> >>>
> >>> The best bug for this is
> >>> https://bugs.launchpad.net/oslo.serialization/+bug/1728368 and we are
> >>> currently getting test fails in https://review.openstack.org/531788
> >>>

Thanks for that, will keep an eye on it.

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
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] [glance][oslo][requirements] [ironic]oslo.serialization fails with glance

[John Villalovos]

I have updated the bug with info I found out:
https://bugs.launchpad.net/oslo.serialization/+bug/1728368

Also I did a test patch with a proposed change:
https://review.openstack.org/#/c/535166/

This patch causes the unit tests to work.

As a note there is a deprecation warning in the current code (without my
patch) that says in the future it will raise a ValueError() as can be seen
in a recently merged patch:
http://logs.openstack.org/72/533872/6/check/openstack-tox-py27/4709e32/job-output.txt.gz#_2018-01-16_13_10_38_931593

The test patch gets rid of that deprecation warning for the exceptions.

Though I did see another warning about the "Response" object:
http://logs.openstack.org/66/535166/2/check/openstack-tox-py35/33d0827/job-output.txt.gz#_2018-01-18_05_13_52_603162

But that is for someone else to figure out :)



On Wed, Jan 17, 2018 at 7:13 PM, ChangBo Guo  wrote:

> add Ironic team  in the loop
>
> the revert patch got -1 from  ironic folks , more details  please see the
> comments in https://review.openstack.org/534736
> The possible solution is to figure out why  the change break Glance's unit
> test.  which side should be fixed.
>
>
>
> 2018-01-17 20:14 GMT+08:00 ChangBo Guo :
>
>> I dig a little.  It shows success when updating constraint to 2.21.2 [1]
>> but failure when updating constraint to 2.22.0 [2].   according to release
>> information [3].
>> It means 2.21.1 works with glance test but  2.21.2 doesn't work well with
>> glance. The only issue patch is https://github.com/openstack/o
>> slo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8.
>>
>>
>> [1] https://review.openstack.org/514833
>> [2] https://review.openstack.org/#/c/525136
>> [3] https://github.com/openstack/releases/blob/master/deliverabl
>> es/queens/oslo.serialization.yaml
>>
>>
>> Actions:
>>
>> Block  oslo.serialization  version  2.21.2,  2.22.0, 2. 23.0in
>> https://review.openstack.org/534739
>> Revert c1a7079c26d27a2e46cca26963d3d9aa040bdbe8 in
>> https://review.openstack.org/534736
>>
>>
>>
>>
>> 2018-01-16 23:35 GMT+08:00 Matthew Thode :
>>
>>> On 18-01-16 19:12:16, ChangBo Guo wrote:
>>> > What's the issue for Glance,  any bug link ?
>>> >
>>> > 2018-01-16 0:12 GMT+08:00 Matthew Thode :
>>> >
>>> > > On 18-01-13 00:41:28, Matthew Thode wrote:
>>> > > > https://review.openstack.org/531788 is the review we are seeing
>>> it in,
>>> > > > but 2.22.0 failed as well.
>>> > > >
>>> > > > I'm guessing it was introduced in either
>>> > > >
>>> > > > https://github.com/openstack/oslo.serialization/commit/
>>> > > c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
>>> > > > or
>>> > > > https://github.com/openstack/oslo.serialization/commit/
>>> > > cdb2f60d26e3b65b6370f87b2e9864045651c117
>>> > >
>>> > > bamp
>>> > >
>>>
>>> The best bug for this is
>>> https://bugs.launchpad.net/oslo.serialization/+bug/1728368 and we are
>>> currently getting test fails in https://review.openstack.org/531788
>>>
>>> --
>>> Matthew Thode (prometheanfire)
>>>
>>
>>
>>
>> --
>> ChangBo Guo(gcb)
>> Community Director @EasyStack
>>
>
>
>
> --
> ChangBo Guo(gcb)
> Community Director @EasyStack
>
> __
> 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] [glance][oslo][requirements] [ironic]oslo.serialization fails with glance

[ChangBo Guo]

add Ironic team  in the loop

the revert patch got -1 from  ironic folks , more details  please see the
comments in https://review.openstack.org/534736
The possible solution is to figure out why  the change break Glance's unit
test.  which side should be fixed.



2018-01-17 20:14 GMT+08:00 ChangBo Guo :

> I dig a little.  It shows success when updating constraint to 2.21.2 [1]
> but failure when updating constraint to 2.22.0 [2].   according to release
> information [3].
> It means 2.21.1 works with glance test but  2.21.2 doesn't work well with
> glance. The only issue patch is https://github.com/openstack/
> oslo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8.
>
>
> [1] https://review.openstack.org/514833
> [2] https://review.openstack.org/#/c/525136
> [3] https://github.com/openstack/releases/blob/master/
> deliverables/queens/oslo.serialization.yaml
>
>
> Actions:
>
> Block  oslo.serialization  version  2.21.2,  2.22.0, 2. 23.0in
> https://review.openstack.org/534739
> Revert c1a7079c26d27a2e46cca26963d3d9aa040bdbe8 in
> https://review.openstack.org/534736
>
>
>
>
> 2018-01-16 23:35 GMT+08:00 Matthew Thode :
>
>> On 18-01-16 19:12:16, ChangBo Guo wrote:
>> > What's the issue for Glance,  any bug link ?
>> >
>> > 2018-01-16 0:12 GMT+08:00 Matthew Thode :
>> >
>> > > On 18-01-13 00:41:28, Matthew Thode wrote:
>> > > > https://review.openstack.org/531788 is the review we are seeing it
>> in,
>> > > > but 2.22.0 failed as well.
>> > > >
>> > > > I'm guessing it was introduced in either
>> > > >
>> > > > https://github.com/openstack/oslo.serialization/commit/
>> > > c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
>> > > > or
>> > > > https://github.com/openstack/oslo.serialization/commit/
>> > > cdb2f60d26e3b65b6370f87b2e9864045651c117
>> > >
>> > > bamp
>> > >
>>
>> The best bug for this is
>> https://bugs.launchpad.net/oslo.serialization/+bug/1728368 and we are
>> currently getting test fails in https://review.openstack.org/531788
>>
>> --
>> Matthew Thode (prometheanfire)
>>
>
>
>
> --
> ChangBo Guo(gcb)
> Community Director @EasyStack
>



-- 
ChangBo Guo(gcb)
Community Director @EasyStack
__
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] [glance][oslo][requirements] oslo.serialization fails with glance

[Matthew Thode]

On 18-01-16 19:12:16, ChangBo Guo wrote:
> What's the issue for Glance,  any bug link ?
> 
> 2018-01-16 0:12 GMT+08:00 Matthew Thode :
> 
> > On 18-01-13 00:41:28, Matthew Thode wrote:
> > > https://review.openstack.org/531788 is the review we are seeing it in,
> > > but 2.22.0 failed as well.
> > >
> > > I'm guessing it was introduced in either
> > >
> > > https://github.com/openstack/oslo.serialization/commit/
> > c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
> > > or
> > > https://github.com/openstack/oslo.serialization/commit/
> > cdb2f60d26e3b65b6370f87b2e9864045651c117
> >
> > bamp
> >

The best bug for this is
https://bugs.launchpad.net/oslo.serialization/+bug/1728368 and we are
currently getting test fails in https://review.openstack.org/531788

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
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] [glance][oslo][requirements] oslo.serialization fails with glance

[ChangBo Guo]

What's the issue for Glance,  any bug link ?

2018-01-16 0:12 GMT+08:00 Matthew Thode :

> On 18-01-13 00:41:28, Matthew Thode wrote:
> > https://review.openstack.org/531788 is the review we are seeing it in,
> > but 2.22.0 failed as well.
> >
> > I'm guessing it was introduced in either
> >
> > https://github.com/openstack/oslo.serialization/commit/
> c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
> > or
> > https://github.com/openstack/oslo.serialization/commit/
> cdb2f60d26e3b65b6370f87b2e9864045651c117
>
> bamp
>
> --
> Matthew Thode (prometheanfire)
>
> __
> 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
>
>


-- 
ChangBo Guo(gcb)
Community Director @EasyStack
__
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] [glance][oslo][requirements] oslo.serialization fails with glance

[Matthew Thode]

On 18-01-13 00:41:28, Matthew Thode wrote:
> https://review.openstack.org/531788 is the review we are seeing it in,
> but 2.22.0 failed as well.
> 
> I'm guessing it was introduced in either
> 
> https://github.com/openstack/oslo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
> or
> https://github.com/openstack/oslo.serialization/commit/cdb2f60d26e3b65b6370f87b2e9864045651c117

bamp

-- 
Matthew Thode (prometheanfire)


signature.asc
Description: PGP signature
__
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-dev] [glance][oslo][requirements] oslo.serialization fails with glance

[Matthew Thode]

https://review.openstack.org/531788 is the review we are seeing it in,
but 2.22.0 failed as well.

I'm guessing it was introduced in either

https://github.com/openstack/oslo.serialization/commit/c1a7079c26d27a2e46cca26963d3d9aa040bdbe8
or
https://github.com/openstack/oslo.serialization/commit/cdb2f60d26e3b65b6370f87b2e9864045651c117
-- 
Matthew Thode


signature.asc
Description: PGP signature
__
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-dev] [glance] current priorities

[Brian Rosmaita]

Reminder: the Glance team has fewer than usual number of reviewers
available until after the new year.

The weekly Glance meeting is cancelled on Thursday, December 28.

Here's what we're working on between now and the next Glance meeting
on January 4, 2018:

* Glanceclient
We're aiming for a glanceclient release from the stable/pike branch on
January 2.  This depends on several patches:
- https://review.openstack.org/#/c/529834/ - this is the backport of
the changes to the functional test jobs in master to stable/pike.  At
the moment, it has two patches to devstack stable/pike as
dependencies:
- https://review.openstack.org/#/c/529878/ - backports some changes in
devstack/master needed to run the functional jobs under zuul3
- https://review.openstack.org/#/c/530138/ - backports a fix from
devstack/master of another issue the functional test jobs have run
into

* Glance scrubber refactor
- https://review.openstack.org/#/c/510449/

* Metadata injection
- https://review.openstack.org/#/c/527635/
- https://review.openstack.org/#/c/527907/

* hooks for import plugins (needed for metadata injection)
- https://review.openstack.org/#/c/528754/


Happy holidays if you're celebrating, and happy new year.
brian

__
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-dev] [glance] priorities for the week (12/08-12/14)

[Brian Rosmaita]

Let's get the scrubber refactor and anything that got postponed from
Q-2 merged before the meeting on Thursday.

scrubber:
https://review.openstack.org/#/c/510449/ (time zone bug has been addressed)

others:
https://review.openstack.org/#/c/524060/
https://review.openstack.org/#/c/521457/
https://review.openstack.org/#/c/523029/
https://review.openstack.org/#/c/523028/
https://review.openstack.org/#/c/523179/

Have a productive week!
brian

__
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-dev] [glance] priorities for the week (12/01-12/07)

[Brian Rosmaita]

Hello Glancers,

As discussed at yesterday's Glance meeting, the priority for this week
is getting ready for the release of the Q-2 milestone, so:

1. the scrubber refactor
2. bugs scheduled for Q-2
3. enhanced tests for interoperable image import ("IIR")

I've put a list of patches and their current status on an etherpad:
  https://etherpad.openstack.org/p/glance-queens-Q2

Please keep it updated as you work through the items.  Several of the
bugs impact the same file, so there may be a need to rebase and
re-approve a few of these patches.

All changes must be approved by 12:00 UTC on Wednesday 6 December to
make it into the Q-2 milestone release.

cheers,
brian

__
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-dev] [Glance] No Team Meeting Today 23rd of Nov

[Erno Kuvaja]

Hi all,

Due to the Thanks giving in US and as no agenda items were added by
the deadline yesterday we will not have glance meeting today. Will
recoup next week 30th of Nov.

Thanks,
Jokke

__
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] [glance] nominating Nikhil Komawar for glance core

[Nikhil Komawar]

Thank you all for the support. I intend to help the Glance community
flourish, again.

cheers

On Tue, Nov 21, 2017 at 10:07 AM, Brian Rosmaita  wrote:

> Having heard only positive responses, I'm happy to reinstate Nikhil
> Komawar as a glance core, with all the rights and privileges
> pertaining thereto.
>
> Welcome back, Nikhil!
>
> cheers,
> brian
>
> On Thu, Nov 16, 2017 at 8:20 PM, Abhishek Kekane 
> wrote:
> > Big +2
> > Glad you are back :)
> >
> > Abhishek
> >
> > On 17-Nov-2017 4:59 AM, "Brian Rosmaita" 
> wrote:
> >>
> >> I'm sure I don't need to introduce Nikhil Komawar (nikhil in IRC), who
> >> was Glance PTL for the Kilo, Liberty, and Newton releases and who was
> >> a long time Glance core until he stepped down at the end of June this
> >> year.  Nikhil has informed me that he now has time to do Glance code
> >> reviews again, and I will be happy to have his experience and
> >> knowledge of the Glance code base available to inform our code
> >> reviews, and I propose to reinstate him as a member of the glance core
> >> team.
> >>
> >> I discussed this with the other cores present at today's weekly Glance
> >> meeting, and they support reinstating Nikhil, so I don't see any
> >> reason to have a long waiting period.  I'd like to add Nikhil to the
> >> core list on Monday, November 20, so if anyone has any comments or
> >> concerns, please let me know before then.
> >>
> >> thanks!
> >> brian
> >>
> >> 
> __
> >> 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
> >
>



-- 
--
Thanks,
Nikhil
__
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] [glance] nominating Nikhil Komawar for glance core

[Brian Rosmaita]

Having heard only positive responses, I'm happy to reinstate Nikhil
Komawar as a glance core, with all the rights and privileges
pertaining thereto.

Welcome back, Nikhil!

cheers,
brian

On Thu, Nov 16, 2017 at 8:20 PM, Abhishek Kekane  wrote:
> Big +2
> Glad you are back :)
>
> Abhishek
>
> On 17-Nov-2017 4:59 AM, "Brian Rosmaita"  wrote:
>>
>> I'm sure I don't need to introduce Nikhil Komawar (nikhil in IRC), who
>> was Glance PTL for the Kilo, Liberty, and Newton releases and who was
>> a long time Glance core until he stepped down at the end of June this
>> year.  Nikhil has informed me that he now has time to do Glance code
>> reviews again, and I will be happy to have his experience and
>> knowledge of the Glance code base available to inform our code
>> reviews, and I propose to reinstate him as a member of the glance core
>> team.
>>
>> I discussed this with the other cores present at today's weekly Glance
>> meeting, and they support reinstating Nikhil, so I don't see any
>> reason to have a long waiting period.  I'd like to add Nikhil to the
>> core list on Monday, November 20, so if anyone has any comments or
>> concerns, please let me know before then.
>>
>> thanks!
>> brian
>>
>> __
>> 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
>

__
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-dev] [glance] priorities for the week (11/17-11/23)

[Brian Rosmaita]

Hello Glancers,

Due to the Thanksgiving holidays in the USA next week, we are
tentatively cancelling the meeting on November 23.  However, most of
our developers these days are outside the USA, so if someone has a
pressing issue and puts the same on the meeting agenda before the
usual deadline (24 hours before the meeting, so before 14:00 on
Wednesday, Nov 22), we will hold the meeting.  Erno has volunteered to
keep an eye on the agenda and send out an email to the dev list if the
November 23 meeting will be held.  (So the default setting is: no
meeting next week.)

Patches needing review:

https://review.openstack.org/#/c/510449/
https://review.openstack.org/#/c/520945/
https://review.openstack.org/#/c/510424/
https://review.openstack.org/#/c/519514/
https://review.openstack.org/#/c/520644/

Except for the first patch, they're small changes that will be quick
to review and good to get merged.

cheers,
brian

__
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] [glance] nominating Nikhil Komawar for glance core

[Abhishek Kekane]

Big +2
Glad you are back :)

Abhishek

On 17-Nov-2017 4:59 AM, "Brian Rosmaita"  wrote:

> I'm sure I don't need to introduce Nikhil Komawar (nikhil in IRC), who
> was Glance PTL for the Kilo, Liberty, and Newton releases and who was
> a long time Glance core until he stepped down at the end of June this
> year.  Nikhil has informed me that he now has time to do Glance code
> reviews again, and I will be happy to have his experience and
> knowledge of the Glance code base available to inform our code
> reviews, and I propose to reinstate him as a member of the glance core
> team.
>
> I discussed this with the other cores present at today's weekly Glance
> meeting, and they support reinstating Nikhil, so I don't see any
> reason to have a long waiting period.  I'd like to add Nikhil to the
> core list on Monday, November 20, so if anyone has any comments or
> concerns, please let me know before then.
>
> thanks!
> brian
>
> __
> 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

[openstack-dev] [glance] nominating Nikhil Komawar for glance core

[Brian Rosmaita]

I'm sure I don't need to introduce Nikhil Komawar (nikhil in IRC), who
was Glance PTL for the Kilo, Liberty, and Newton releases and who was
a long time Glance core until he stepped down at the end of June this
year.  Nikhil has informed me that he now has time to do Glance code
reviews again, and I will be happy to have his experience and
knowledge of the Glance code base available to inform our code
reviews, and I propose to reinstate him as a member of the glance core
team.

I discussed this with the other cores present at today's weekly Glance
meeting, and they support reinstating Nikhil, so I don't see any
reason to have a long waiting period.  I'd like to add Nikhil to the
core list on Monday, November 20, so if anyone has any comments or
concerns, please let me know before then.

thanks!
brian

__
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