Amit,
For Glance, all the user-specified image metadata must be String data type.
You can see this in the image schema [0], where "additionalProperties":
{"type": "string"}
(The only image properties that are *not* strings are those assigned non-string
types in the schema.)
So for your
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:
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
that happen to my
statement about this issue in the Queens release notes [0]; the
situation described there still stands.
[0]
https://docs.openstack.org/releasenotes/glance/queens.html#relnotes-16-0-0-stable-queens-known-issues
> Bernd
>
> On 11/12/2018 11:27 PM, Brian Rosmaita wrote:
&g
On 11/7/18 8:46 AM, Bernd Bausch wrote:
> Does the new image import process work? Am I missing something? Uploaded
> images stay in an intermediate state, either /uploading/ or /importing/,
> and never become /active.///Where should I look?
Apologies for the late reply to your question. For
On 11/12/18 5:07 AM, Bernd Bausch wrote:
> Trying Glance's new import process, my images are all stuck in status
> uploading (both methods glance-direct and web-download).
>
> I can see that there are tasks for those images; they are pending. The
> Glance API log doesn't contain anything that
The Glance where are the docs? wiki page has been updated:
https://wiki.openstack.org/wiki/Glance-where-are-the-docs
By the way, the Docs Team is having a bug-squash day on 9th September 2014 if
you feel like writing prose instead of python:
I am really sorry to see you step down, but congratulations!
cheers,
brian
From: Mark Washenberger [mark.washenber...@markwash.net]
Sent: Monday, September 22, 2014 12:22 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Glance] PTL Non-Candidacy
Greg,
This might be useful: https://wiki.openstack.org/wiki/Qonos-scheduling-service
There's a link to the code repository at the bottom of the document. It might
be kind of overkill for what you want, though.
cheers,
brian
From: Greg Hill
+1
From: Kuvaja, Erno [kuv...@hp.com]
Sent: Thursday, June 12, 2014 9:34 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance] Nominating Nikhil Komawar for Core
+1
From: Alex Meade
I agree with Erno. I think that the glance registry service being optional is
a good argument for keeping its config separate rather than munging it into the
API config.
rosmaita
From: Kuvaja, Erno [kuv...@hp.com]
Sent: Tuesday, June 17, 2014 10:29 AM
Hi Facundo,
Can you attend the Glance meeting this week at 20:00 UTC on Thursday in
#openstack-meeting-alt ?
I may be misunderstanding what's at stake, but it looks like:
- Glance holds the image metadata (some user-modifiable, some not)
- Cinder copies the image metadata to use as volume
The Glance Mid-Cycle Meeting will be held July 24-25 at VMware, Inc, in Palo
Alto, CA, USA.
Info is here: https://etherpad.openstack.org/p/glance-juno-mid-cycle-meeting
Please add proposals for discussion topics to the bottom of that etherpad, or
just add your name so we can guage interest, or
There's been some work in Glance on this already. In addition to the BP Mark
mentioned for import, please take a look at these so we don't duplicate efforts:
https://wiki.openstack.org/wiki/Glance-tasks-import
https://blueprints.launchpad.net/glance/+spec/new-download-workflow
That said, I prefer to have resources actually be things that the software
creates. An action
isn't created. It is performed.
I would prefer to replace the term action(s) with the term task(s), as is
proposed for Nova [1].
Glance already uses tasks in the v2 URL for creating resources
Just to add some more to what Fei Long said:
There's some mention of tags in the regular API docs [1, 2]. Various
OpenStack vendors also have support docs explaining them [3].
Tags are sort of informal metadata, and support for tags (and they way you
use them) varies widely among OpenStack
After lots of discussion, I think we've come to a consensus on what property
protections should look like in Glance. Please reply with comments!
The blueprint:
https://blueprints.launchpad.net/glance/+spec/api-v2-property-protection
The full specification:
Stuart,
I agree with Mark's comments, wanted to address this:
3) we could potentially link roles to the regex
eg this could allow role1_xxx to be writable only if you have 'role1'.
By assigning appropriate roles (com.provider/com.partner/nova?) you
could provide the ability to write to that
After lots of discussion, here are the image import/export/cloning blueprints
unified as a tasks API. Please reply with comments!
Take a look at this doc first:
https://wiki.openstack.org/wiki/Glance-tasks-api
It's got a related documents section with links to the previous proposals and
asynchronous worker meeting 2 Aug 2013 14:00 UTC in #openstack-glance
please look at https://etherpad.openstack.org/havana-glance-requirements before
the meeting
cheers,
brian
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
images API. This view seems to be shared and well highlighted by Jay in this
thread: http://lists.openstack.org/pipermail/openstack-dev/2013-May/009527.html
Was there any follow up to that mail? (sorry if I missed it!)
Thanks,
-Paul
On 30 July 2013 19:36, Brian Rosmaita
brian.rosma
] [Glance] async worker design meeting tomorrow!
On 08/05/2013 04:34 AM, Brian Rosmaita wrote:
Well, it's tomorrow as I write this, maybe it's today as you read
this. Anyway:
- asynchronous worker meeting Tuesday 6 Aug 2013 14:00 UTC in
#openstack-glance
- the etherpad
https
In light of today's IRC meeting in #openstack-glance (notes in etherpad
https://etherpad.openstack.org/LG39UnQA7z), I've updated the tasks api document
and the import document:
https://wiki.openstack.org/wiki/Glance-tasks-api
https://wiki.openstack.org/wiki/Glance-tasks-import
cheers,
...@yahoo-inc.com]
Sent: Tuesday, August 20, 2013 6:18 PM
To: OpenStack Development Mailing List; Brian Rosmaita
Subject: Re: [openstack-dev] [Glance] import task update
Very cool, would u consider trying to use taskflow for some of this. It
seems to fit (or could fit) part of the bill nicely.
I'd
We're shooting for 15:00 UTC Monday 26 August. (Let me know ASAP if you really
want to be in on this and can't make it, but this is probably the best time
available.)
Topics:
(1) taskflow seam for integration
(2) tasks api and executor interface
(3) indexable column in db for tasks to be
We'll now be holding the below meeting at 15:00 UTC Tuesday 27 August in
#openstack-glance on Freenode.
From: Brian Rosmaita [brian.rosma...@rackspace.com]
Sent: Thursday, August 22, 2013 5:33 PM
To: Joshua Harlow; OpenStack Development Mailing List
This thread continued past the announcement that the meeting was moved to
Tuesday ... so, no task meeting today (Monday), we will be meeting at 15:00 UTC
Tuesday 27 August in #openstack-glance on Freenode.
Topics:
(1) taskflow seam for integration
(2) tasks api and executor interface
(3)
Sorry for the repost, just want to make sure everyone is aware that the meeting
was moved.
From: Brian Rosmaita [brian.rosma...@rackspace.com]
Sent: Friday, August 23, 2013 1:48 PM
To: OpenStack Development Mailing List; Joshua Harlow; Jessica Lucci
From: Kevin L. Mitchell [kevin.mitch...@rackspace.com]
Sent: Monday, January 19, 2015 4:54 PM
When we look at consistency, we look at everything else in OpenStack.
From the standpoint of the nova API (with which I am the most familiar),
I am not aware of any property that is ever omitted from
On 2/9/15, 8:44 PM, Joe Gordon
joe.gord...@gmail.commailto:joe.gord...@gmail.com wrote:
On Mon, Feb 9, 2015 at 1:22 PM, Jay Pipes
jaypi...@gmail.commailto:jaypi...@gmail.com wrote:
On 01/20/2015 10:54 AM, Brian Rosmaita wrote:
From: Kevin L. Mitchell
[kevin.mitch
On 2/15/15, 2:35 PM, Jay Pipes jaypi...@gmail.com wrote:
On 02/15/2015 01:13 PM, Brian Rosmaita wrote:
On 2/15/15, 10:10 AM, Jay Pipes jaypi...@gmail.com wrote:
On 02/15/2015 01:31 AM, Brian Rosmaita wrote:
This is a follow-up to the discussion at the 12 February API-WG
meeting [1] concerning
The response on the review is overwhelmingly positive (or, strictly speaking,
unanimously non-negative).
If anyone has an objection, could you please register it before 12:00 UTC on
Monday, January 12?
https://review.openstack.org/#/c/145025/
thanks,
brian
On 2/12/15, 9:57 AM, Ian Cordasco ian.corda...@rackspace.com wrote:
On 2/11/15, 11:10, Okuma, Wayne wayne.ok...@hp.com wrote:
Hello,
I would like to change the metadef-tags create API which was checked into
Kilo (cycle 1).
The python-glanceclient that would support metadef-tags has not been
This is a follow-up to the discussion at the 12 February API-WG meeting
[1] concerning functional API in Glance [2]. We made some progress, but
need to close this off so the spec can be implemented in Kilo.
I believe this is where we left off:
1. The general consensus was that POST is the
On 2/15/15, 10:10 AM, Jay Pipes jaypi...@gmail.com wrote:
On 02/15/2015 01:31 AM, Brian Rosmaita wrote:
This is a follow-up to the discussion at the 12 February API-WG meeting
[1] concerning functional API in Glance [2]. We made some progress,
but
need to close this off so the spec can
request to this URI to obtain status info, such as whether the task completed
or not. And since tasks are now real resources, they should have a documented
representation as well.
Miguel
On Wed, Feb 18, 2015 at 1:19 PM, Brian Rosmaita
brian.rosma...@rackspace.commailto:brian.rosma...@rackspace.com
I don't know how elaborate we want to get here, but Everett Toews had an
interesting suggestion in the openstack-api channel. It would go something
like this:
(1) User gets /x1/search endpoint from service catalog
(2) User does some request against /x1/search
(3) User receives 400 with an error
Su,
The patch you are referring to is a work-in-progress patch. It only partially
implements the feature, and as one of the comments in the patch indicates, it's
defining an Integer column in the database that might be replaced by an enum.
So even if it were a full implementation, it would
Greetings to all Glance people,
kragniz has proposed that we have an informal social event for Glance and
Glance-related people attending the summit next week. Please keep your
calendars open for about 2 hours or so starting at 7:30 p.m. on Wednesday,
May 20. Neither kragniz nor I are familiar
On 8/7/15, 1:07 PM, Jay Pipes jaypi...@gmail.com wrote:
So, here's the crux of the issue. Nova and Cinder **do not want to speak
the Glance REST API** to either upload or download image bits from
storage. Streaming image bits through the Glance API endpoint is a
needless and inefficient step, and
On 8/13/15, 11:32 AM, Mike Perez thin...@gmail.com wrote:
* Role based properties [5] (who is asking for this, and why is Glance
enforcing roles?)
I can answer this one.
Property protections have been available in Glance since Havana [6].
The feature was requested by deployers.
In general,
tl;dr Word on the street is that image property protections are a pain
point for some projects (e.g., Nova, Cinder). We'd like to find out from
some other projects (and deployers) how they interact with Glance with
respect to property protections and how we can improve this process.
The Glance
There was a lot of great pre-summit discussion on the Glance spec for image
import refactoring, and more lively discussion at the summit, but it's been
very quiet since I posted patch set 5 last week.
Please take a few minutes to look over the revised spec and let the Glance
community know
On 10/20/15, 1:06 PM, "Brian Rosmaita" <brian.rosma...@rackspace.com>
wrote:
>Hello,
>
>I've updated the image import spec [4] to incorporate the discussion thus
>far.
>
>The fishbowl session [5] is scheduled for Thursday, October 29,
>2:40pm-3:
s
>between v1 and v2 and how this is making some pandas sad.
>
>The above served as a starting point for a discussion around the
>current API, how it can be improved, etc. This discussions happened on
>IRC[1], on a call (sorry, I forgot to record this call, this is entirely
>my fault) a
I added an agenda item for this for today's Glance meeting:
https://etherpad.openstack.org/p/glance-team-meeting-agenda
I'd prefer to hold my vote until after the meeting.
cheers,
brian
On 9/3/15, 6:14 AM, "Kuvaja, Erno" wrote:
>Malini, all,
>
>My current opinion is -1 for
Apologies for forking the thread, but there was way too much in Doug's
email (and Flavio's response) and I only want to make a few points about
tasks. Please read Doug's original email and Flavio's reply at some
point, preferably before you read this.
I'm going to limit myself to 4 points.
I'd like to clarify something.
On 9/25/15, 12:16 PM, "Mark Voelker" wrote:
[big snip]
>Also worth pointing out here: when we talk about ³doing the same thing²
>from a DefCore perspective, we¹re essentially talking about what¹s
>exposed to the end user, not how that¹s
+1 from me! Glad to have Ian back.
On 12/7/15, 11:36 AM, "Flavio Percoco" wrote:
>Greetings,
>
>Not long ago, Ian Cordasco, sent an email out stepping down from his
>core roles as he didn't have the time to dedicate to the project
>team's he was part of.
>
>Ian has contacted
On 12/11/15, 3:13 PM, "Ian Cordasco" wrote:
>On 12/11/15, 12:25, "Alexander Tivelkov" wrote:
>
>>Hi folks!
>>
>>
>>As it was decided during the Mitaka design summit, we are separating the
>>experimental Artifact Repository API from the main
Thanks to all the OpenStackers who have participated so far. A major revision
is now available for your reading pleasure.
https://review.openstack.org/#/c/232371/
I realize a USA holiday is coming up very soon this week ... the Glance
community would be thankful to get some comments before
I am definitely +1 on this! Thanks for volunteering, Ian.
On 5/26/16, 2:42 AM, "Tony Breeds" wrote:
>On Wed, May 25, 2016 at 05:12:56PM -0400, Nikhil Komawar wrote:
>> Hi all,
>>
>>
>> I would like to propose adding Ian to glance-stable-maint team. The
>> interest is
Fei Long and I have followed up on our action item from the glance/ops
mid-cycle sync, namely, to start a discussion among the operators and
product working group so that the Glance team can get a better
understanding of what "Better image lifecycle support" means. Please
leave comments on this
-lite,
https://bugs.launchpad.net/glance/+bug/1535900
If you have an opinion, please leave a comment in the appropriate place.
thanks,
brian
On 1/23/16, 9:54 AM, "Brian Rosmaita" <brian.rosma...@rackspace.com> wrote:
>Please provide feedback about a proposal to add 't
Hello everyone,
Joe, I think you are proposing a perfectly legitimate use case, but it's
not what the Glance community is calling "image import", and that's
leading to some confusion.
The Glance community has defined "image import" as: "A cloud end-user has
a bunch of bits that they want to give
Here's the situation:
image property set:
- Images v1 API: all image property names are converted to lowercase
before they're stored
- Compute v2 API: all image property names are converted to lowercase
before they're stored
- Images v2 API: image properties are stored in the case specified when
Please provide feedback about a proposal to add 'tar' as a new Glance
disk_format.[0]
The Ironic team is adding support for "OS tarball images" in Mitaka. This is a
compressed tar archive of a / (root filesystem). These tarballs are created by
first installing the OS packages in a chroot and
+1
On 1/22/16, 7:09 PM, "Tripp, Travis S" wrote:
>I am nominating Li Yingjun (yingjun on IRC) to join the Searchlight core
>reviewers team. We are a young project and he has already made a
>noticeable impact with his contributions. You may review his Searchlight
>[0] and
Tuesday, April 12 1400-1800 UTC works for me, I will attend.
On 3/31/16, 5:34 PM, "Nikhil Komawar" wrote:
>Hi all,
>
>I'm excited to see you all Glancers at the Austin summit and discuss
>more on our project.
>
>Nevertheless, I feel that our summit conversations will have
+1
On 5/24/16, 11:11 AM, "Chris Hoge" wrote:
>+1
>
>> On May 23, 2016, at 8:25 PM, Mike Perez wrote:
>>
>>> On 18:00 May 20, Nikhil Komawar wrote:
>>> Hello all,
>>>
>>>
>>> I want to propose having a dedicated virtual sync next week Thursday
>>>May
Subject was: Re: [openstack-dev] [tc] [all] [glance] On operating a high
throughput or otherwise team
Un-hijacking the thread. Here are some answers to John's questions, hope they
are helpful.
On 5/16/16, 9:06 PM, "John Griffith"
>
+1
I second the motion!
On 5/17/16, 3:42 PM, "Tripp, Travis S" wrote:
>I am nominating Lei Zhang from Intel (lei-zh on IRC) to join the
>Searchlight core reviewers team. He has been actively participating with
>thoughtful patches and reviews demonstrating his depth of
On 5/18/16, 2:15 AM, "Clint Byrum" <cl...@fewbar.com> wrote:
>Excerpts from Robert Collins's message of 2016-05-18 14:57:05 +1200:
>> On 18 May 2016 at 00:54, Brian Rosmaita <brian.rosma...@rackspace.com>
>>wrote:
>>
>> >> Coup
+1 from me, Rick has been doing great work and will be a good addition to
the Searchlight core team.
On 7/25/16, 5:01 PM, "Tripp, Travis S" wrote:
>Hello!
>
>I am nominating Rick Aulino for Searchlight core. Rick has been working
>on the core indexing engine throughout
I have a question about the api-ref. Right now, for example, the new
images v1/v2 api-refs are accurate for Mitaka. But DocImpact bugs are
being generated as we speak for changes in master that won't be
available to consumers until Newton is released (unless they build from
source). If those bug
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
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
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
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
, 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
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
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
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]
>
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
/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
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/
-
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
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
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
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
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
-
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
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
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
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
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
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
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
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
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
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
>>
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
On 9/1/16, 7:31 AM, "Flavio Percoco" wrote:
>On 01/09/16 08:50 +0100, Erno Kuvaja wrote:
>>Hi all,
>>
>>As it seems by the "Improving help text for *" string of patches like
>>[0][1] that the Glance core group is willing to get around -2s by
>>abandoning, reproposing and
Nikhil,
Thank you for all your hard work as Glance PTL (3 times!). Glad to hear
that you will be continuing to work in OpenStack, and especially that you
plan to continue working with Glance.
cheers,
brian
On 9/12/16, 2:08 AM, "Nikhil Komawar" wrote:
>Hi team,
>
>
lot of the
ideas presented above come from those conversations.
Thank you for your consideration,
Brian Rosmaita
[0]
http://git.openstack.org/cgit/openstack/governance/commit/?id=0b1da15253d50
d6486bf60d87205e5c796662646
[1]
http://git.openstack.org/cgit/openstack/glance/commit/?id=63e6dbb
I'd like to reiterate what we discussed during the "Core Awareness" topic
at yesterday's Glance weekly meeting for those who weren't able to attend
or read through the meeting logs yet.
Three Ocata priorities have already been determined:
(1) image import refactor
(2) community images (including
+ 1 on both issues. Great work, Matt!
On 9/19/16, 1:13 PM, "Tripp, Travis S" wrote:
>Hello!
>
>I am nominating Matt Borland for Searchlight UI core. Matt has been
>working on searchlight UI since we started it and he is the primary
>author of the angular registration
We're going to need to cut rc-2 for Glance to accommodate some new
translations, so there is an opportunity to include some conservative
bugfixes. Any such must be merged before 16:00 UTC on Wed 28 Sept, so I
am setting a deadline of 12:00 UTC on Tue 27 Sept for approval. If you
have a bugfix
Quick reminder to Glancers and People Interested in Glance that the Glance
Ocata design summit session proposals close at 14:00 UTC Wednesday Sept 28
and voting closes at 13:59 UTC Thursday Sept 29 (that is, just before next
week's Glance meeting). We'll have final discussion during the Glance
The voting has closed. By acclamation the weekly image import sync will
occur as follows:
when: Tuesdays, 14:00 UTC
where: #openstack-glance
duration: 20 minutes
I realize this time isn't great for everyone. Since #openstack-glance is
logged, I'll use "#startmeeting image import sync" and
1 - 100 of 279 matches
Mail list logo