Re: [openstack-dev] [glance][openstack-ansible] Moving on

On Thu, May 18, 2017 at 11:55 PM, Steve Lewis wrote: > It is clear to me now that I won't be able to work on OpenStack as a part of > my next day job, wherever that ends up being. As such, I’ll no longer be > able to invest the time and energy required to maintain my

[openstack-dev] [glance] no meeting this week

Hello Glancers, The weekly Glance IRC meeting is cancelled for tomorrow (May 4) and the summit week (May 11). We'll resume our regular weekly meeting cadence on Thursday, May 18. If you'll be at the summit/forum in Boston, you may find some fellow glance people at these sessions: Mon 8 ,

[Openstack-operators] Glance image cache survey

Hello operators, The Glance team is conducting another survey about Glance usage. We could use responses from *all* operators on this one. It's about using the glance-cache tool, and we are interested in hearing from both operators who use it and also operators who don't. The length of the

[openstack-dev] [glance] priorities for the current week (04/23-04/27)

1 Pike midcycle review == Hopefully, you saw my summary of the Glance Pike virtual midcycle meeting ... if not, here it is: - http://lists.openstack.org/pipermail/openstack-dev/2017-April/115777.html 2 Spec finalization === I realize that many Glance cores are

Re: [openstack-dev] Affected by OSIC, Layoffs? Or want to help?

As an OSIC casualty, I want to thank Lauren for organizing this. While being hit by layoffs is extremely unpleasant, it's really awesome how supportive the OpenStack community has been--reaching out with job leads, offering general commiseration, as well as this practical effort to get us to the

[openstack-dev] [glance] virtual midcycle summary

Hello Glancers, Due to technical difficulties, today's virtual midcycle was not recorded. So here's a summary of the discussion; refer to the etherpad for each session for more details, and feel free to ask for clarifications in #openstack-glance or here on the ML. A link to the etherpads for

[openstack-dev] [glance] reminder: virtual midcycle at 14:00 UTC today

The Glance virtual midcycle is being held today (Thursday 20 April) from 14:00-17:00 UTC. Please see the etherpad for signup, agenda, and connection information: https://etherpad.openstack.org/p/glance-pike-virtual-midcycle cheers, brian

[openstack-dev] [glance] virtual midcycle thursday 20 april

The Glance virtual midcycle meeting will be held on Thursday 20 April 2017 from 14:00-17:00 UTC. Please signup on the agenda page: https://etherpad.openstack.org/p/glance-pike-virtual-midcycle The meeting will be held in Zoom. Connection information is on the midcycle etherpad. See you there!

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 4/12/17 2:47 AM, Tony Breeds wrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all projects ... Hi Tony, just wanted to give

[openstack-dev] [glance] priorities for the coming week (04/14-04/20)

I'm going to keep the list light this week. Use your reviewing time as you see fit and hopefully we can show some love to non-priority items that have been sitting a while for glance_store and python-glanceclient. Additionally: 1. Spec freeze extension: as you saw in an earlier email, the spec

[openstack-dev] [glance] virtual midcycle April 20

As discussed at today's Glance weekly meeting, we'll hold the virtual midcycle next week on Thursday, April 20. We'll keep it short, just 3 hours from 14:00-17:00 UTC. Please plan ahead and have breakfast/lunch/snacks/dinner ready at your workstation so we can work straight through. Agenda and

[openstack-dev] [glance] spec freeze extension

It has come to my attention that the deadline to have Glance-related specs merged for Pike is in the middle of religious holidays/institutional holidays in the EU. Hence, the spec freeze is extended to 23:59 UTC on Wednesday 19 April 2017. Here's a link to the spec tracking etherpad:

[openstack-dev] [glance] reminder: spec freeze happens Friday!

All Glance, python-glanceclient, and glance_store specs must be merged into the glance-specs repository by 23:59 on Friday 14 April 2017. I've just updated the etherpad with the status of the various patches: https://etherpad.openstack.org/p/glance-pike-specs-review If you're a glance core,

[openstack-dev] [glance] priorities for the coming week (04/07-04/13)

First, thanks to everyone who coded and reviewed the items identified as Pike milestone 1 priorities. They were merged yesterday and Hemanth, our release czar, proposed a patch to enable the release: https://review.openstack.org/#/c/454760/ Next, don't forget that the spec freeze is the end of

[openstack-dev] [glance] call for comments on next operator survey draft

Hello Glancers, The topic of the April operators' survey is Glance cache usage. Any developers who are interested in the Glance cache should take a look and let me know if there are any questions that should be added/revised: https://goo.gl/forms/LvAq0anMiHRh7Hb32 Please respond before the

[openstack-dev] [glance] specs awaiting revision

All glance specs that were received before the spec proposal freeze have been reviewed by at least one glance core reviewer and are now awaiting revision. Keep in mind that the spec freeze is 23:59 UTC on Friday 14 April 2017. cheers, brian

[openstack-dev] [api] glance specs with API impact

Hello API WG, Glance has two specs currently under review that have API impact: add multihash support: https://review.openstack.org/#/c/448680/ add protected filter: https://review.openstack.org/#/c/451560/ The changes are minor, non-breaking, and (hopefully) uncontroversial. But you might want

Re: [Openstack-operators] newton heat stack glance error

1T19:47:52Z | > | virtual_size | None | > | visibility | public | > +--+--+ > > It seems to under /v2 :-( > So an h

Re: [Openstack] [heat] Fwd: newton heat stack glance error

Adding "heat" to the subject line. Heat people, I've responded to Ignazio on the operators' list [0], but you may have some helpful info. [0] (would link here, but can't find the April 2017 page in pipermail) Thread starts here:

[openstack-dev] [glance] priorities for the coming week (03/31-04/06)

As discussed at today's meeting, here are the priorities for Glance this week: Pike-1 milestone approaching Hemanth announced Thursday 6 April as the deadline for patches to be merged for P-1. That will give us roughly a week before P-1 to fix any bugs or regressions

Re: [openstack-dev] Project Navigator Updates - Feedback Request

On 3/29/17 12:55 AM, Jimmy McArthur wrote: [snip] > What we really need is the following: > > * A project history, including the date of project inception that's > included in the TC tags. > * An API history in an easily digestible format that all projects share. > So whether you're doing micro

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On 3/8/17 2:03 PM, Matthew Thode wrote: > So, pycrypto upstream is dead and has been for a while, we should look > at moving off of it for both bugfix and security reasons. > > Currently it's used by the following. > > barbican, cinder, trove, glance, heat, keystoneauth, keystonemiddleware, >

Re: [openstack-dev] Project Navigator Updates - Feedback Request

On 3/27/17 5:01 PM, Lauren Sell wrote: > Hi Matt, > > Thanks for the feedback. > >> On Mar 24, 2017, at 3:50 PM, Matt Riedemann wrote: [snip] >> 2. The "API Version History" section in the bottom right says: >> >> "Version v2.1 (Ocata) - LATEST RELEASE" >> >> And links to

[openstack-dev] [glance] priorities for the coming week (03/24-03/30)

Here are the priorities for Glance this week. I'm keeping the list short so we can focus. 0. Unblocking requirements Hemanth is working on the WebOb 1.7 incompatibilities issue, so keep an eye out for updates to his patch: - https://review.openstack.org/#/c/423366/ Also keep an eye on the gate

Re: [openstack-dev] Arrivederci

On 3/22/17 8:06 AM, Ian Cordasco wrote: > Friday 24 March 2017 will be my last day working on OpenStack. Well, I was hoping for divine intervention, but it's almost the close of business today and it hasn't happened. So I guess I'll have to say, on behalf of myself and the entire Glance team,

Re: [openstack-dev] [requirements][keystone][glance] WebOb

On 3/20/17 6:54 AM, Davanum Srinivas wrote: > Dear Keystone and Glance teams, > > WebOb update of u-c to 1.7.1 is stuck for a while[1]. Can you please > prioritize reviews (keystone) review [1] and (glance) review [2] for > this week? Hi Dims, quick update on this. We do have it prioritized,

[Openstack-operators] Glance image 'owner' survey

Hello operators, The Glance team is conducting another survey about Glance usage. This one is about image ownership, as controlled by the configuration option 'owner_is_tenant'. We could use answers from both operators who deploy using the default value as well as operators who use the

Re: [openstack-dev] [ptls] Project On-Boarding Rooms

On 3/16/17 11:18 AM, Kendall Nelson wrote: > Hello Emilien, > > So, we have our slots basically filled, BUT you can ask one of the projects > that did get a slot if you can be refugees in their room and share. Or the > rooms will be empty over lunch and we can make sure to get you time there >

Re: [openstack-dev] [api][qa][tc][glance][keystone][cinder] Testing of deprecated API versions

Big snip ... the original message is here: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113798.html On 3/13/17 3:09 AM, Ghanshyam Mann wrote: > On Sat, Mar 11, 2017 at 12:10 AM, Andrea Frittoli > wrote: >> On Fri, Mar 10, 2017 at 2:49 PM Andrea

Re: [openstack-dev] [glance] UPDATED priorities for the coming week (03/10-03/16)

://review.openstack.org/#/c/419074/ Please give them your attention. (The other patch mentioned by Dims has been merged.) thanks, brian On 3/9/17 2:32 PM, Brian Rosmaita wrote: > Hello Glancers, > > As discussed at today's Glance weekly meeting, here are the review > priorities for this

[openstack-dev] [glance] priorities for the coming week (03/10-03/16)

Hello Glancers, As discussed at today's Glance weekly meeting, here are the review priorities for this week: 1. image import refactor Erno has posted a number of patches related to the backend implementation: - https://review.openstack.org/443636 - https://review.openstack.org/391441 -

Re: [openstack-dev] [glance] image import sync tomorrow CANCELLED

The Glance image import sync scheduled for 16:00 UTC on 8 March 2017 is postponed until next week. More details at the regular Glance weekly meeting on Thursday. cheers, brian On 3/7/17 9:49 AM, Brian Rosmaita wrote: > Sorry for the late notice, but we'll be having a one-hour image imp

[openstack-dev] [glance] image import sync tomorrow

Sorry for the late notice, but we'll be having a one-hour image import sync via video conference at 16:00 UTC tomorrow (8 March 2017). Watch the ML for more details later today, plus connection info will be posted in #openstack-glance around 15:45 UTC tomorrow. cheers, brian

Re: [Openstack] migrate instances to another openstack environment

On 3/1/17 6:25 PM, Manuel Sopena Ballesteros wrote: > Hi, > > I am having a hard time trying to migrate my instances to another openstack > installation. > > My understanding is that I could do instance --> snapshot --> image and then > migrate this image to another openstack > > I started

[openstack-dev] [glance] image import virtual meetup

As discussed in today's Glance meeting, we'll have a one-hour virtual meetup next week to get things rolling. Please indicate your availability on this doodle poll: http://doodle.com/poll/eh2mk4fdwgd4sv7b If none of those time options work, reply to this email with a counter-proposal. Please

Re: [openstack-dev] [docs][release][ptl] Adding docs to the release schedule

On 3/2/17 9:45 AM, Ian Cordasco wrote: > -Original Message- > From: Telles Nobrega > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: March 2, 2017 at 08:01:29 > To: OpenStack Development Mailing List

[openstack-dev] [glance] PTG summary, Thursday Feb 23

The Glance PTG schedule etherpad contains links to the etherpads for each of the sessions discussed below: https://etherpad.openstack.org/p/glance-pike-ptg-schedule 1. glance/glare/artifacts/images The tldr; is Glance needs to complete image import before taking on anything else, and the Glare

[openstack-dev] [glance] PTG summary, Wednesday, Feb 22

The Glance PTG schedule etherpad contains links to the etherpads for each of the sessions discussed below: https://etherpad.openstack.org/p/glance-pike-ptg-schedule 1. Short topics dharinic led a discussion of a three recent items she's been looking into. First up was how the Glance limited JSON

[openstack-dev] [glance] user survey question results

The responses to the Glance user survey question are in the following etherpad to make it easy to record reactions and/or suggestions for follow-up: https://etherpad.openstack.org/p/glance-user-survey-q-feb-2017 This was the question we asked: "As you're aware, the Images API v1 supplied by

[openstack-dev] [glance] revising the core list

Following Doug's suggestion in [0], I'm revising the Glance core list before next week's PTG. First, I'd again like to thank the following former Glance cores, who stepped down during the Ocata cycle, for their past service to Glance: - Sabari Murugesan - Stuart McLaren Second, I'd like to

[openstack-dev] [glance] priorities for the coming week (02/17-02/23)

Hello Glancers, Here are the weekly priorities: 1. RC-1 Testing It's still looking like RC-1 is going to be the real thing. If you have some free time, give it a workout. 2. PTG Here are some key URLs for your convenience: - https://etherpad.openstack.org/p/glance-pike-ptg-planning -

[openstack-dev] artifacts code removed from the glance codebase in Pike

If you've never deployed, packaged, or used the Artifacts API supplied by Glance or Glare, you can safely disregard this message. There's a patch up [0] to remove the legacy EXPERIMENTAL Artifacts API code from the Glance code repository. (This is an entirely separate issue from the question of

[openstack-dev] [glance] glance mascot/logo available

Hello Glancers, Heidi Joy Tretheway at the Foundation has released the Glance mascot logo files for full use as you see fit: "Inside this folder, you’ll find full-color and one-color versions of the logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use them on presentations

[openstack-dev] [glance] priorities for the coming week (02/10-02/16)

Hello Glancers, Here are the weekly priorities: 1. RC-1 Testing It's looking like there won't be an RC-2, so no need to wait, do some testing on RC-1 now. If you do find an issue, please create a bug, tag it as 'ocata-rc-potential' and give a shout in #openstack-glance for rosmaita or

[openstack-dev] [tc][glance][glare][all] glance/glare/artifacts/images at the PTG

I want to give all interested parties a heads up that I have scheduled a session in the Macon room from 9:30-10:30 a.m. on Thursday morning (February 23). Here's what we need to discuss. This is from my perspective as Glance PTL, so it's going to be Glance-centric. This is a quick narrative

Re: [openstack-dev] [all][api] POST /api-wg/news

On 2/6/17 4:28 PM, Ken'ichi Ohmichi wrote: > 2017-02-06 6:45 GMT-08:00 Brian Rosmaita <rosmaita.foss...@gmail.com>: >> On 2/6/17 5:51 AM, Jordan Pittier wrote: >> [super-enormous snip -- Chris, Ken, and Jordan make good points, I >> encourage you to read the

Re: [openstack-dev] [all][api] POST /api-wg/news

On 2/6/17 5:51 AM, Jordan Pittier wrote: [super-enormous snip -- Chris, Ken, and Jordan make good points, I encourage you to read the entire thread; I just want to concentrate on one point] > > I would say we should make compromise, not solve dilemma. I can live in a > world where we sometimes

[openstack-dev] [glance] priorities for the coming week (02/03-02/09)

Congratulations to the Glance team for delivering Ocata RC-1! As discussed at yesterday's Glance meeting, here are the weekly priorities: 1. RC-1 Testing Glance Ocata RC-1 (14.0.0.0rc1) is available and the stable/ocata branch has been created. Please test and create bugs for any anomalies

[openstack-dev] [glance] new draft logo of the Glance mascot

Hello Glancers, Attached is the new draft logo of the Glance mascot. It looks to me like this draft captures the key features we requested (and is much more personable than the previous version). If you have a contrary opinion, please reply quickly as Heidi Joy's team wants to have all the

[openstack-dev] [glance] priorities for the coming week (01/27-02/02)

First, please read the email from Ian (our release czar) about the feature freeze: http://lists.openstack.org/pipermail/openstack-dev/2017-January/111067.html We have three priorities this week. The first is an all-hands-on-deck super priority, namely, reviewing (and re-reviewing, as

Re: [openstack-dev] [glance] FFE Request

Update: The FFE for the Rolling Upgrades work was discussed at today's Glance meeting, and an FFE was granted. On 1/26/17 8:58 AM, Brian Rosmaita wrote: > On 1/26/17 8:52 AM, Steve Lewis wrote: >> I'm requesting a FFE to enable us to complete the work described as the >> &q

Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

Having heard only affirmative responses, I've added Dharini Chandrasekar to the Glance core group, with all the rights and privileges pertaining thereto. Welcome to the Glance core team, Dharini! On 1/24/17 8:36 AM, Brian Rosmaita wrote: > I'd like to propose Dharini Chandrasekar (dhari

Re: [openstack-dev] [glance] FFE Request

On 1/26/17 8:52 AM, Steve Lewis wrote: > I'm requesting a FFE to enable us to complete the work described as the > "Rolling Upgrades" priority [0]. > Thanks, Steve. FFE exception requests are on the agenda for today's Glance meeting at 14:00 UTC. cheers, brian > > [0] >

[openstack-dev] [glance] PTL candidacy for Pike

u for your consideration, Brian Rosmaita __ 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-operators] Glance image 'visibility' migration in Ocata

, Brian Rosmaita wrote: > Hello Operators, > > Here are the results of the recent operators' poll concerning the > upcoming image visibility changes in Glance and the direction we plan to > take. Thanks to all participants for helping us come to a data-driven > decision on a

[openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance core. She has been an active reviewer and contributor to the Glance project during the Newton and Ocata cycles, has contributed to other OpenStack projects, and has represented Glance in some interactions with other project

[openstack-dev] Sabari Murugesan stepping down from Glance core

Sabari Murugesan has communicated to me that he's no longer able to commit time to working on Glance, and he's stepping down from the core reviewers' team. This message isn't all bad news, however: I'm particularly grateful that Sabari has agreed to continue as the VMware driver maintainer for

[Openstack-operators] Glance swift multi-user storage backend survey

Hello operators, The Glance team is conducting another survey about Glance usage. This one is for operators who are currently using (or contemplating using) the swift multi-tenant storage backend for Glance, a feature which is *not* enabled by default. The survey is only 5 questions long, so it

Re: [openstack-dev] [osc][openstackclient][glance] broken image functional test

/17 11:46 AM, Dean Troyer wrote: > On Fri, Jan 20, 2017 at 10:00 AM, Brian Rosmaita > <rosmaita.foss...@gmail.com> wrote: >> We've approved the revert to get the OSC unblocked, though it may be a >> while before jenkins gets around to processing it, as (of course) the &g

[openstack-dev] [glance] priorities for the coming week (01/20-01/26)

As discussed in the weekly meeting yesterday, here are our priorities for the week: (1) final release for client libraries is next week, so glanceclient patches need attention. This list is in priority order (first one is the highest): - https://review.openstack.org/#/c/352892/ -

Re: [openstack-dev] [osc][openstackclient][glance] broken image functional test

On 1/20/17 9:05 AM, Dean Troyer wrote: > On Fri, Jan 20, 2017 at 6:46 AM, Steve Martinelli > wrote: >> it seems the OSC gate is broken, several patches are failing the same way: > > [...] > >> did something break? at first glance (hehe), it seems this patch may be to >>

Re: [openstack-dev] [infra][qa][glance] gate-tempest-dsvm-full-ceph-plugin-src-glance_store-ubuntu-xenial failures

bled in that patch and should not block > gate etc. > > Also if any CI failing due to that they can quickly disable that flag and > skip the tests which not meant to be run on their CI. > > > ​-gmann > > On Tue, Jan 17, 2017 at 11:18 AM, Brian Rosmaita <rosmai

[openstack-dev] [infra][qa][glance] gate-tempest-dsvm-full-ceph-plugin-src-glance_store-ubuntu-xenial failures

I need some help troubleshooting a glance_store gate failure that I think is due to a recent change in a tempest test and a configuration problem (or it could be something else entirely). I'd appreciate some help solving this as it appears to be blocking all merges into glance_store, which, as a

[openstack-dev] [glance] priorities for the coming week (01/13-01/19)

As discussed at the Glance weekly meeting yesterday, please concentrate on the following items: (0) Glance coresec: you know what I'm talking about (and if you don't contact me immediately offline). We need to get this wrapped up before January 18. (1) Ian wants to release glance_store on

[openstack-dev] Pike PTG facilities and remote participation

Hi Thierry, I have a quick facilities question about the PTG. I know of at least one developer who can't attend physically but will be willing to join via some type of videoconferencing software (vidyo, or blue jeans, or google hangout). Do you think it will be possible? The wifi has gotten

Re: [openstack-dev] [glance] draft logo of glance mascot

ghtful input! > > Best, > Heidi Joy > >> On Nov 3, 2016, at 9:55 AM, Brian Rosmaita >> <brian.rosma...@rackspace.com> wrote: >> >> Hello Heidi Joy, >> >> First, let me say on behalf of the Glance community that we appreciate >> the

Re: [openstack-dev] Consistent Versioned Endpoints

On 1/13/17 7:42 AM, Steve Martinelli wrote: > On Fri, Jan 13, 2017 at 7:39 AM, Sean Dague wrote: > >> On 01/12/2017 01:35 PM, Scott D'Angelo wrote: >>> TL;DR: Let's discuss Version Discovery and Endpoints in the Service >>> Catalog at the PTG in Atlanta. >>> >>> The topic of

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

(Top-posting, don't bother digging through for more.) We're following the tempest HACKING.rst procedure. The patch for step #2 is: https://review.openstack.org/#/c/419658/ Please review at your earliest convenience. thanks, brian On 1/12/17 3:34 PM, Brian Rosmaita wrote: > Ken, > &g

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

Ken, Thanks for the quick response ... we'll follow the procedure outlined in the tempest HACKING.rst that you pointed out. cheers, brian On 1/12/17 2:32 PM, Ken'ichi Ohmichi wrote: > 2017-01-12 5:47 GMT-08:00 Brian Rosmaita <rosmaita.foss...@gmail.com>: >> On 1/11/17 10:35 PM,

Re: [openstack-dev] [qa] glance issue at QA team meeting on 12 January

eptability of the patch so that we can figure out our next steps. thanks, brian On 1/11/17 12:10 PM, Brian Rosmaita wrote: > Hello QA Team, > > There wasn't an agenda for 12 January on the Meetings/QATeamMeeting page > on the wiki, so I took the liberty of creating one. I added an ite

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

/specs/api/v2/sharing-image-api-v2.html > > > Regards > Ghanshyam Mann > +818011120698 > > > On Mon, Jan 9, 2017 at 10:30 PM, Brian Rosmaita <rosmaita.foss...@gmail.com> > wrote: > >> On 1/5/17 10:19 AM, Brian Rosmaita wrote: >>> To anyone interested in

[openstack-dev] [qa] glance issue at QA team meeting on 12 January

Hello QA Team, There wasn't an agenda for 12 January on the Meetings/QATeamMeeting page on the wiki, so I took the liberty of creating one. I added an item under the "Tempest" section to discuss a patch to modify a Glance test that is currently blocking a few Glance Ocata priorities (community

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

On 1/5/17 10:19 AM, Brian Rosmaita wrote: > To anyone interested in this discussion: I put it on the agenda for > today's API-WG meeting (16:00 UTC): > > https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda As you probably noticed in the API-WG newsletter [A], this issue was discu

[openstack-dev] [glance] priorities for the coming week (01/06-01/12)

Hopefully everyone's had some rest over the holidays, and are ready to code & review for O-3. Please concentrate on the following: (0) If you're a member of the Glance coresec team, you should be getting a separate notification about an issue that could use your attention. Please make some time

Re: [openstack-dev] [Release-job-failures] Release of openstack/glance failed

On 1/5/17 3:17 AM, Erno Kuvaja wrote: > On Wed, Jan 4, 2017 at 9:22 PM, Tony Breeds wrote: >> On Wed, Jan 04, 2017 at 01:31:42PM -0500, Ian Cordasco wrote: >> >>> I believe you asked in another thread (that I cannot locate) if it was >>> acceptable to the Glance team to

Re: [openstack-dev] [glance] question for OpenStack User Survey

add your refinements before 23:59 UTC 8 January 2017. thanks, brian On 1/3/17 6:11 AM, Erno Kuvaja wrote: > On Thu, Dec 22, 2016 at 11:05 PM, Brian Rosmaita > <rosmaita.foss...@gmail.com> wrote: >> Glancers, >> >> We have the opportunity to submit one question for the

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

g to break cloud. > > .. [1] https://review.openstack.org/#/c/412731/ > > .. [2] > https://github.com/openstack/tempest/blob/master/tempest/api/image/v2/test_images.py#L339 > > ​-gmann > > On Fri, Dec 23, 2016 at 5:51 AM, Matthew Treinish <mtrein...@kortar.org>

[openstack-dev] [glance] question for OpenStack User Survey

Glancers, We have the opportunity to submit one question for the upcoming User Survey, which launches on or before February 1. We'd receive responses in advance of the February PTG, so this would be a good opportunity for glancers who are thinking of organizing design sessions at the PTG to get

[openstack-dev] [glance] priorities for the next 2 weeks (12/23-01/05)

Item number 1 is the same as last week, but it was reviewed and has a new patch coming soon, so please keep an eye out for it. Everything else is new. (1) Patch to enable better request-id tracking: https://review.openstack.org/#/c/352892/ (2) Community images The current patch:

[openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

Something has come up with a tempest test for Glance and the community images implementation, and I think it could use some mailing list discussion, as everyone might not be aware of the patch where the discussion is happening now [1]. First, the Glance background, to get everyone on the same

[openstack-dev] [glance] priorities for the coming week (12/16-12/22)

We had good movement in the Glance priority list this past week, with most items being resolved. Good work, everyone! Here's what we're focusing on now: (1) Patch to enable better request-id tracking: https://review.openstack.org/#/c/352892/ This has been sitting on the list for a few weeks and

[openstack-dev] [glance] meeting schedule for next 3 weeks

The weekly IRC meetings for Glance are held in #openstack-meeting-4 on Thursdays at 14:00 UTC. The agenda [0] and transcripts [1] are publicly available. Given the upcoming holidays, here's what we decided today about the next 3 weeks: December 22: We will meet, but don't feel bad if you can't

Re: [openstack-dev] [glance] Propose Steve Lewis for Glance core

Having heard only affirmative responses, I've added Steve Lewis to the Glance core group, with all the rights and privileges pertaining thereto. Welcome to the Glance core team, Steve! On 12/13/16 5:05 PM, Brian Rosmaita wrote: > I'd like to propose Steve Lewis (stevelle on IRC) for Glance c

Re: [openstack-dev] [glance] respecting glance priorities

ers, brian On 12/9/16 7:14 AM, Brian Rosmaita wrote: > As discussed at the Glance weekly meeting yesterday, the priorities for > 12/1 through 12/8, unfortunately look very similar to last week's > priorities. Some core reviewers need to step up. The priorities are: &g

[openstack-dev] [glance] Propose Steve Lewis for Glance core

I'd like to propose Steve Lewis (stevelle on IRC) for Glance core. Take a look at any of his reviews, and you can see that he's thorough and comprehensive in his reviewing. He's knowledgeable about Python, Glance, and software engineering in general. He's gained a lot of experience in various

[openstack-dev] Stuart McLaren stepping down from Glance core

Stuart McLaren has communicated to me that he's no longer able to commit time to working on Glance, and he's stepping down from the core reviewers' team. I'd like to thank Stuart for all his past service to Glance, which has been substantial ... he'll be much missed. I'd particularly like to

Re: [openstack-dev] [glance] priorities for the coming week (12/09-12/15)

t your patch. cheers, brian > And please consider backport to Newton. > > This bug is very annoying for deployments with several controllers and > glance over cinder... > > On Fri, Dec 9, 2016 at 3:14 PM, Brian Rosmaita <rosmaita.foss...@gmail.com> > wrote: > &g

[openstack-dev] [glance] priorities for the coming week (12/09-12/15)

As discussed at the Glance weekly meeting yesterday, the priorities for 12/1 through 12/8, unfortunately look very similar to last week's priorities. Some core reviewers need to step up. The priorities are: Highest priority (1) database strategy for rolling upgrades:

[openstack-dev] [glance] priorities for the coming week

This is aimed particularly at Glance core reviewers, many of whom have been very quiet lately. Ideally, people will reply to this message saying "I've got #2", for example, so that we don't duplicate efforts. As discussed at the Glance weekly meeting yesterday, the priorities for 12/1 through

[Openstack-operators] Glance image 'visibility' migration in Ocata

Hello Operators, Here are the results of the recent operators' poll concerning the upcoming image visibility changes in Glance and the direction we plan to take. Thanks to all participants for helping us come to a data-driven decision on a contentious issue. (For background on the operators'

Re: [Openstack-operators] Discontinue multiple image location support in Glance?

UTC on Friday 9 December 2016 On 11/22/16, 4:34 PM, "Brian Rosmaita" <brian.rosma...@rackspace.com> wrote: > Hello Operators, > > Glance has a "multiple image locations" feature that's been a pain point > for developers and operators. > > The orig

[openstack-dev] [glance] Ocata specs - final push

The Glance spec freeze for Ocata is 23:59 UTC on Friday 25 November 2016. Glance cores, please review the proposed specs listed below, and please keep a watch for submitted revisions. Spec contributors, please keep an eye on your specs so you can make timely revisions and resubmit for review.

[Openstack-operators] Discontinue multiple image location support in Glance?

Hello Operators, Glance has a "multiple image locations" feature that's been a pain point for developers and operators. The original developers have left the project and we are trying to determine the use cases people have that involve multiple image locations, because we'd like to either (a)

Re: [Openstack-operators] need feedback about Glance image 'visibility' migration in Ocata

e sense on shared images, that's the reason why member operations can only be performed on an image in 'shared' visibility. Cheers, Sam On Fri, Nov 18, 2016 at 12:27 AM, Brian Rosmaita <brian.rosma...@rackspace.com<mailto:brian.rosma...@rackspace.com>> wrote: On 11/17/16, 1:39 AM, &quo

Re: [Openstack-operators] need feedback about Glance image 'visibility' migration in Ocata

On 11/17/16, 1:39 AM, "Sam Morrison" <sorri...@gmail.com<mailto:sorri...@gmail.com>> wrote: On 17 Nov. 2016, at 3:49 pm, Brian Rosmaita <brian.rosma...@rackspace.com<mailto:brian.rosma...@rackspace.com>> wrote: Ocata workflow: (1) create an image with

[Openstack-operators] need feedback about Glance image 'visibility' migration in Ocata

Hello Operators, The long-awaited implementation of "community images" in Glance [0] is just around the corner, but before we can merge it, we need to make a decision about how the database migration of the image 'visibility' field will work. We could use your help. Here's what's at issue: Up

[openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'

Hello Translators, We're having a discussion about a new image "visibility" value for Glance, and before we go too far, it would be helpful to know whether what we're worried about is going to matter for ESL people. Here's the situation: Since the Diablo release, Glance end users have had the

[openstack-dev] [Glance] [api] Community Images Impasse

Adding '[api]' to subject to get API-WG attention. On 11/15/16, 11:26 AM, "Ian Cordasco" wrote: >Hi all, > >One of our priorities for Ocata-1 (whose deadline Glance has set for >17 November 2016) is the Community Images work that has been discussed >now for several

[openstack-dev] [glance] priorities for O-1

Hello Glancers, O-1 is around the corner (i.e., next week). The priority for Glance is Community Images. Please review the following patches: https://review.openstack.org/#/c/369110/ https://review.openstack.org/#/c/387660/ https://review.openstack.org/#/c/391968/ Also, don't forget about the

[openstack-dev] [glance] spec proposal freeze

Just a friendly reminder that the Glance Spec Proposal Freeze is imminent: All Glance, python-glanceclient, and glance_store specs must be proposed as patches to the glance-specs repository by 23:59 UTC on Thursday 10 November 2016. The purpose of the proposal freeze is to allow sufficient time

<    1   2   3   >