The poll has closed and the winning time for the Glance virtual design
session on zero downtime rolling upgrades will be 14:00 UTC on Friday, 11
November 2016. The virtual design session will be held in an on-air
Google hangout which should allow it to be recorded (though of course it
would be
As discussed at the Summit and at yesterday's Glance meeting, Alex
Bashmakov and Hemanth Makkapati will present a virtual design session
(including a demo!) of the work they're doing toward zero downtime rolling
upgrades on Friday, 11 November 2016. Please fill in your availability on
a doodle
[3] https://www.fortwhyte.org/wp-content/uploads/2014/12/chip2.jpg
On 10/21/16, 12:43 PM, "Brian Rosmaita" <brian.rosma...@rackspace.com>
wrote:
>Hello Glancers,
>
>Heidi Joy Tretheway and Todd Morey from the foundation have sent us the
>attached sneak previ
This issue came up during a code review; I've asked around a bit but
haven't been able to find an answer.
Some of the help output for utility scripts associated with Glance aren't
being translated, so Li Wei put up a patch to fix this [0], but there are
at least two problematic cases.
Case 1:
For those who couldn't attend the Glance design sessions in Barcelona,
here's a quick synopsis of what was discussed.
1. glance_store refactoring (Fishbowl)
The aim of the glance_store is to present a unified interface to a variety
of backend storage technologies supported by different drivers.
Hello Glancers,
Heidi Joy Tretheway and Todd Morey from the foundation have sent us the
attached sneak preview of the Glance mascot/logo. (As you may recall, we
voted for a chipmunk [0].)
They've set up a handy form [1] so that you can provide individual
feedback. The project logos will be
+1 from me, I'll be happy to see Kevin on the core list.
On 10/19/16, 10:10 AM, "McLellan, Steven"
> wrote:
Hi,
I'd like to propose Zhenyu Zheng (Kevin_Zheng on IRC) for Searchlight core.
While he's most active on Nova, he's also been very
Hello everyone,
First, I'd like to thank Flavio Percoco and Kairat Kushaev for their past
service as members of the Glance core security contacts team.
Unfortunately, due to other commitments, they don't have time to continue
on coresec.
Thus, the main point of this email is to propose Ian
On 10/10/16, 11:31 AM, "Erno Kuvaja" wrote:
>On Mon, Oct 10, 2016 at 3:58 PM, Andrey Pavlov
>wrote:
>> Hi,
>>
>> I want to backport this bug -
>> https://bugs.launchpad.net/glance-store/+bug/1616556
>> but review for master is stuck since August -
>>
on what we
discuss
at the Summit.
At this point, we already have three priorities carried over from Newton,
and
I just want to make sure we keep the momentum going.
cheers,
brian
>
>On 07/10/16 18:50 +, Brian Rosmaita wrote:
>>I'd like to reiterate what we discussed during the &q
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
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
Just want to send out a quick recap of a discussion in #openstack-meeting
during the release team meeting this morning, in case any other projects
are in a similar situation.
As you're aware, the api-ref was moved out of docs and into the source
code tree for each project this cycle. Since the
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
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
+ 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
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
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,
>
>
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
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
+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
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
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
+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
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
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
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"
>
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
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
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
-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
+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
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
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
+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
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
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:
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
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'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
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 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
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,
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
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
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
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
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
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
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
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/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
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
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
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
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
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
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:
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
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
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
+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
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
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
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
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
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
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
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
] [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
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
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
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
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, 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:
201 - 279 of 279 matches
Mail list logo