> From: Ronald Bradford [mailto:m...@ronaldbradford.com]
> Sent: Wednesday, January 20, 2016 6:34 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Oslo] Improving deprecated options
> identification and documentation
>
> Markus,
>
>
>> Yes, in
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Monday, January 25, 2016 3:07 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all][tc] Stabilization cycles: Elaborating on
> the
> idea to move it forward
>
> On 20/01/16 13:23 -0430
>
>
>
> On 1/27/2016 9:40 AM, Tan, Lin wrote:
> > Thank you so much. Eron. This really helps me a lot!!
> >
> > Tan
> >
> > *From:*Kuvaja, Erno [mailto:kuv...@hpe.com]
> > *Sent:* Tuesday, January 26, 2016 8:34 PM
> > *To:* OpenStack Developm
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 26 January 2016 14:42
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [glance] Glance Core team additions/removals
>
>
> Greetings,
>
> I'd like us to have one more core cleanup for this cyc
Hi Tan,
While the cross project spec was discussed Glance already had implementation of
request ids in place. At the time of the Glance implementation we assumed that
one request id is desired through the chain of services and we implemented the
req id to be accepted as part of the request. Thi
> -Original Message-
> From: McLellan, Steven
> Sent: Friday, December 11, 2015 6:37 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog
> name for Glance Artifact Repository API
>
> Hi Alex,
>
> -Original Message-
> From: Ian Cordasco [mailto:ian.corda...@rackspace.com]
> Sent: Friday, December 11, 2015 8:13 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog
> name for Glance Artifact
> -Original Message-
> From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com]
> Sent: 11 December 2015 09:19
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [python-glanceclient] Return request-id to
> caller
>
>
>
> -Original Me
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: 09 December 2015 08:57
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [stable] Stable team PTL nominations are open
>
> Thierry Carrez wrote:
> > Thierry Carrez wrote:
> >> The nomina
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Monday, December 07, 2015 4:36 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [glance] Add Ian Cordasco back into glance-core
>
> Greetings,
>
> Not long ago, Ian Cordasco, sent an email
penstack-operators] [stable][all] Keeping Juno "alive" for longer.
>
> [Apologies for the delayed reply, after more than a week without Internet
> access it's taking me more than a week to catch up with everything on the
> mailing lists.]
>
> On 2015-11-20 10:21:4
> -Original Message-
> From: Nikhil Komawar [mailto:nik.koma...@gmail.com]
> Sent: Tuesday, December 01, 2015 6:21 AM
> To: OpenStack Development Mailing List (not for usage questions); Kekane,
> Abhishek
> Subject: [openstack-dev] [all] [glance] Proposal to add Abhishek to Glance
> core te
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: Monday, November 23, 2015 5:11 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [stable] Stable team PTL nominations are open
>
> Hi everyone,
>
> We discussed setting up a standalone
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Monday, November 23, 2015 8:21 PM
> To: openstack-dev@lists.openstack.org
> Cc: Sabari Kumar Murugesan
> Subject: [openstack-dev] [all][glance] Add Sabari Kumar Murugesan
>
>
> Greetings,
>
> I'd like to propo
able][all] Keeping Juno "alive" for longer.
>
> Kuvaja, Erno wrote:
> > So we were brainstorming this with Rocky the other night. Would this be
> possible to do by following:
> > 1) we still tag juno EOL in few days time
> > 2) we do not remove the stable/j
> -Original Message-
> From: Alan Pevec [mailto:ape...@gmail.com]
> Sent: Friday, November 20, 2015 10:46 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [stable][infra][qa] Preparing 2014.2.4 (Juno)
> WAS Re: [Openstack-operators] [stabl
> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Tuesday, November 17, 2015 2:57 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re:
> [Openstack-operators] [stable][all] Keeping Juno "al
> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Thursday, November 19, 2015 10:43 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [stable][neutron] How we handle Kilo
> backports
>
> Tony Breeds wrote:
Stack project team
>
> On Mon, Nov 09, 2015 at 10:54:43PM +, Kuvaja, Erno wrote:
> > > On Mon, Nov 09, 2015 at 05:28:45PM -0500, Doug Hellmann wrote:
> > > > Excerpts from Matt Riedemann's message of 2015-11-09 16:05:29 -0600:
> > > > >
> > >
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: 09 November 2015 22:40
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [stable] Making stable maintenance its own
> OpenStack project team
>
> On Mon, Nov 0
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: 09 November 2015 16:42
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [stable] Making stable maintenance its own
> OpenStack project team
>
> Hi everyone,
>
> A few cycles ago we set up
> -Original Message-
> From: Tony Breeds [mailto:t...@bakeyournoodle.com]
> Sent: Friday, November 06, 2015 6:15 AM
> To: OpenStack Development Mailing List
> Cc: openstack-operat...@lists.openstack.org
> Subject: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.
>
> Hello all
> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Friday, October 16, 2015 1:34 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [neutron][stable] proactive backporting
>
> Hi all,
>
> I’d like to introduce a
Kairat,
We do not validate against schema on image-list (see
43769d6cc7266d7c81db31ad58b4fa403c35b611). This said there was discussion
around throwing all that validation code out, exactly like Jay said, we should
not validate responses coming from our own servers.
This discussion happened jus
Hi all,
I'd like to propose following changes to glance-stable-maint team:
1) Removing Zhi Yan Liu from the group; unfortunately he has moved on to
other ventures and is not actively participating our operations anymore.
2) Adding Mike Fedosin to the group; Mike has been reviewing and
Dear PTLs, cross-project liaisons and anyone else interested,
We'll have a cross-project meeting today at 21:00 UTC, with the
following agenda:
* Review of past action items
* Team announcements (horizontal, vertical, diagonal)
* Cross-Project Specs to discuss:
** Service Catalog Standard
> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: Monday, September 14, 2015 5:40 PM
> To: openstack-dev
> Subject: Re: [openstack-dev] [glance] proposed priorities for Mitaka
>
> Excerpts from Kuvaja, Erno's message of 2015-09-14 15:02:59 +:
> > > -
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Monday, September 14, 2015 1:41 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance] proposed priorities for Mitaka
>
> On 14/09/15 08:10 -0400, Doug Hell
Hi Doug,
Please find python-glanceclient 1.0.1 release request
https://review.openstack.org/#/c/222716/
- Erno
> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: Monday, September 14, 2015 1:46 PM
> To: openstack-dev
> Subject: [openstack-dev] [all][ptl][r
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: Monday, September 14, 2015 9:03 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all][TC] 'team:danger-not-diverse tag' and my
> concerns
>
>
> Or are you suggesting it is prefera
+1
From: Alex Meade [mailto:mr.alex.me...@gmail.com]
Sent: Friday, September 11, 2015 7:37 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Glance] glance core rotation part 1
+1
On Fri, Sep 11, 2015 at 2:33 PM, Ian Cordasco
mailto:ian.corda...@r
This was the case until about two weeks ago.
Since 1.0.0 release we have been defaulting to Images API v2 instead of v1 [0].
If you want to exercise the v1 functionality from the CLI client you would need
to specify the either environmental variable OS_IMAGE_API_VERSION=1 or use the
command lin
Malini, all,
My current opinion is -1 for FFE based on the concerns in the spec and
implementation.
I'm more than happy to realign my stand after we have updated spec and a) it's
agreed to be the approach as of now and b) we can evaluate how much work the
implementation needs to meet with the
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: Monday, August 24, 2015 1:47 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [oslo][release] oslo freeze this week?
>
> On Aug 23, 2015, at 5:51 PM, Robert Collins
> wrote:
> > On
> -Original Message-
> From: Dave Walker [mailto:em...@daviey.com]
> Sent: 21 August 2015 12:43
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [stable] [infra] How to auto-generate stable
> release notes
>
> On 21 August 2015 at 11:38, Thi
> -Original Message-
> From: Robert Collins [mailto:robe...@robertcollins.net]
> Sent: Wednesday, August 19, 2015 11:38 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [stable] [infra] How to auto-generate stable
> release notes
>
> On 1
On Wed, Aug 12, 2015 at 2:23 AM, Kuvaja, Erno wrote:
> >> -Original Message-
> >> From: Mike Perez [mailto:thin...@gmail.com]
> >> Sent: 11 August 2015 19:04
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> Subject: Re:
> -Original Message-
> From: Mike Perez [mailto:thin...@gmail.com]
> Sent: 11 August 2015 19:04
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] [Cinder] [Glance] glance_store and
> glance
>
> On 15:06 Au
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Tuesday, August 11, 2015 3:10 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] [Cinder] [Glance] glance_store and
> glance
>
> On 08/11/2015 09:42 AM, Brian Rosmaita wrote:
> > On 8/7
gt;>>>>
> >>>>> Hi,
> >>>>>
> >>>>> I think Erno made a valid point here. If that would touch only
> >>>>>vmware code, that could be an option to consider. But it looks
> >>>>>like both pat
Hi,
Flagged Nova and Cinder into this discussion as they were the first intended
adopters iirc.
I don't have big religious view about this topic. I wasn't huge fan of the idea
separating it in the first place and I'm not huge fan of keeping it separate
either.
After couple of cycles we have s
Hi Gary,
While I do understand the interest to get this functionality included, I really
fail to see how it would comply with the Stable Branch Policy:
https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy
Obviously the last say is on stable-maint-core, but normally new features are
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Tuesday, July 28, 2015 3:15 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [nova][glance][stable] Stable exception for bug
> #1447215: Allow ramdisk/kernel_id to be None
>
> Greetings,
>
I do agree, we don't depend or are cleaning the other clients out of the glance
dependencies as well and I think swift should not be there either.
The default store is filesystem store and if something is depending on the
actual store clients it should be either glance_store or deployer (well fo
> -Original Message-
> From: Ian Cordasco [mailto:ian.corda...@rackspace.com]
> Sent: Friday, July 24, 2015 4:58 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance][api] Response when a illegal body is
> sent
>
>
>
> On 7/23/15, 19:38, "michael mccune" wro
Hi all,
Log Working Group has been running weekly meetings Wednesdays at 20:00 UTC.
There were queries while back to adjust the meeting time to facilitate EMEA/APJ
folks bit better.
Current regular participants are fine with the time we're having the meeting
now, but we wanted to probe the com
Hi all,
We have been waiting python-cinderclient stable/kilo release for couple of
weeks to be able to merge glance_store stable/kilo backports. Namigly:
https://review.openstack.org/#/q/status:open+project:openstack/glance_store+branch:stable/kilo,n,z
As Alan blocked them all, I'd like to ask e
Victor,
That was related to stable/kilo branch as stated on the line above:
14:39:58 jokke_: was that you on python-glanceclient stable/kilo
14:39:59 also queued up bunch of stable stuff ... glance_store gotta
wait until Cinder gets their client requirements fixed, but glanceclient
backports
First of all, Thanks Flavio for bring this open to the daylight!
I have been really frustrated about the Glance spec process since the beginning
and as glance core tried to work around the limitations the best I can. I'm not
sure if the process is similar way broken on the other projects, but I
Hi Mike,
We have similar functionality in Glance and I think this is critical enough fix
to backport to Juno.
Considered for Icehouse, definitely not:
http://lists.openstack.org/pipermail/openstack-announce/2015-June/000372.html
- Erno (jokke_)
> -Original Message-
> From: Mike Perez
As this Fri Jun 19th did not seem to have weight, I just express my opinion to
the mailing list for the records.
Personally I think this is bad idea, but as not being Glance Driver I can't say
how much need there is for such meeting. The specs should be raised during our
weekly meeting and/or d
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: Friday, June 05, 2015 1:46 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all] [stable] No longer doing stable point
> releases
>
> So.. summarizing the various options again:
>
Hi all,
We do not have any burning items (or any what so ever that I'm aware of) on the
agenda today, Rocky is away and I have myself conflicting schedules. Lets
gather together again next week.
Meeting cancelled today Wed 3rd of June!
Best,
Erno
___
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 27 May 2015 00:58
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Glance] [all] Liberty summit: Updates in Glance
>
> Jesse, you beat me on this one :)
>
> On
except Glance images and metadefinitions. CIS
is not just exposing "raw" Elasticsearch capabilities, but it provides strict
boundaries - using policy checks, RBAC and namespace protection (index/type in
the Elasticsearch world) of what can be stored within it and what can be
retrie
Hi all,
As you probably know CIS was expanded from Juno metadefs work this cycle based
on spec [1] provided. The implementation was merged in quite a rush just before
feature freeze.
During the spec review [2] for client functionality for CIS it came to our
attention that the implementation ex
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 20 April 2015 15:04
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [Glance] Open glance-drivers to all glance-cores
>
> Hello Glance folks, and not Glance folks :D
>
> Here's a thought. I be
Hi all,
We have found critical faults from python-glanceclient causing operational
failures if https is enabled. We're in process to backport the fixes to our new
stable branch and will release 0.17.1 of the client as soon as possible.
Please note this if your project is using glanceclient. Aff
> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: Friday, March 13, 2015 3:07 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all] Do we need release announcements for all
> the things?
>
>
>
> On Fri, Mar 13, 2015, at 06:57 AM,
> -Original Message-
> From: Stefano Maffulli [mailto:stef...@openstack.org]
> Sent: 12 March 2015 00:26
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] Avoiding regression in project governance
>
> On Wed, 2015-03-11 at 17:59 -0500, Ed Leafe wrote:
> > The longer
Hi all,
Following the code reviews lately I've noticed that we (the fan club seems to
be growing on weekly basis) have been growing culture of nitpicking [1] and
bikeshedding [2][3] over almost every single change.
Seriously my dear friends, following things are not worth of "-1" vote if even
I'd prefer 1400 as well. But "A Foolish Consistency is the Hobgoblin of Little
Minds"
- Erno
> -Original Message-
> From: Nikhil Komawar [mailto:nikhil.koma...@rackspace.com]
> Sent: 11 March 2015 20:40
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [op
You mean for tomorrow? No worries, I can kick off the meeting and run through
agenda if we have something to address.
Take best out of the ops meetup!
- Erno
From: Rochelle Grober [mailto:rochelle.gro...@huawei.com]
Sent: Tuesday, March 10, 2015 4:04 PM
To: OpenStack Development Maili
Hi all,
We had our first logging workgroup meeting [1] yesterday where we agreed 3 main
priorities for the group to focus on. Please review and provide your feedback:
1) Educating the community About the Logging Guidelines spec
a.
http://specs.openstack.org/openstack/openstack-spec
> From: Nikhil Komawar [mailto:nikhil.koma...@rackspace.com]
> Sent: Tuesday, March 03, 2015 4:10 PM
> To: OpenStack Development Mailing List (not for usage questions); Daniel P.
> Berrange
> Cc: krag...@gmail.com
> Subject: Re: [openstack-dev] [Glance] Core nominations.
>
> If it was not clear i
, Mar 3, 2015 at 7:18 AM, Kuvaja, Erno
mailto:kuv...@hp.com>> wrote:
> -Original Message-
> From: Thierry Carrez
> [mailto:thie...@openstack.org<mailto:thie...@openstack.org>]
> Sent: 03 March 2015 10:00
> To:
> openstack-dev@lists.openstack.org<mailto:
Nikhil,
If I recall correctly this matter was discussed last time at the start of the
L-cycle and at that time we agreed to see if there is change of pattern to
later of the cycle. There has not been one and I do not see reason to postpone
this again, just for the courtesy of it in the hopes so
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: 03 March 2015 10:00
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] auto-abandon changesets considered harmful
> (was Re: [stable][all] Revisiting the 6 month release cycle [metrics])
>
Hi Eugeniya,
Please have a look on the discussion under tag [log]. We’ve been discussing
around this topic (bit wider, not limiting to API errors) quite regular since
Paris Summit and we should have X-project specs for review quite soon after the
Ops meetup. The workgroup meetings will start as
> -Original Message-
> From: Clark Boylan [mailto:cboy...@sapwetik.org]
> Sent: Tuesday, February 17, 2015 6:06 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] The root-cause for IRC private channels (was
> Re: [all][tc] Lets keep our community open, lets fight for
> -Original Message-
> From: James E. Blair [mailto:cor...@inaugust.com]
> Sent: 13 February 2015 16:44
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance] Cleanout of inactive change proposals
> from review
>
>
't know or don't want to spend time for
launchpad/specs/ and so on.
Then we need to educate and encourage them instead of support the behavior of
“Throw it in and someone at some day will maybe take care of it”-attitude.
- Erno
Best regards,
Boris Pavlovic
b 13, 2015 at 3:52 PM, Flavio Percoco
mailto:fla...@redhat.com>> wrote:
On 13/02/15 11:06 +, Kuvaja, Erno wrote:
Hi all,
We have almost year old (from last update) reviews still in the queue for
glance. The discussion was initiated on yesterday’s meeting for adopting
abandon policy fo
Hi all,
We have almost year old (from last update) reviews still in the queue for
glance. The discussion was initiated on yesterday's meeting for adopting
abandon policy for stale changes.
The documentation can be found from
https://etherpad.openstack.org/p/glance-cleanout-of-inactive-PS and a
t
>
>
> > On Feb 11, 2015, at 11:15 AM, Jeremy Stanley wrote:
> >
> > On 2015-02-11 11:31:13 + (+), Kuvaja, Erno wrote:
> > [...]
> >> If you don't belong to the group of privileged living in the area and
> >> receiving free ticket some
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: Wednesday, February 11, 2015 9:55 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [all][tc] Lets keep our community open, lets fight
> for it
>
> Greetings all,
>
> During the last two cyc
Now in my understanding our services does not log to user. The user gets
whatever error message/exception it happens to be thrown at. This is exactly
Why we need some common identifier between them (and who ever offers request ID
being that, I can get some of my friends with well broken English
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 02 February 2015 16:19
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Product] [all][log] Openstack HTTP error codes
>
> On 02/01/2015 06:20 PM, Morgan Fainberg wrote:
> > Putting on my "sorry-
> -Original Message-
> From: Dave Walker [mailto:em...@daviey.com]
> Sent: 13 January 2015 15:10
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Glance] IRC logging
>
> On 13 January 2015 at 12:32, Kuvaja, Erno w
> -Original Message-
> From: Thierry Carrez [mailto:thie...@openstack.org]
> Sent: 13 January 2015 13:02
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Glance] IRC logging
>
> Kuvaja, Erno wrote:
> > [...]
> > 1) One does not ne
I'm heavily against the public logging to the level that I will just leave the
channel if that will be enabled. My point is not foul language and I do
understand that there could be some benefits out of it. Personally I think we
have enough tracked public communication means like ask.openstack.o
I think that's horrible idea. How do we do that store independent with the
linking dependencies?
We should not depend universal use case like this on limited subset of
backends, specially non-OpenStack ones. Glance (nor Nova) should never depend
having direct access to the actual medium where t
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 02 December 2014 09:45
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [glance] Deprecating osprofiler option 'enabled'
> in favour of 'profiler_enabled'
>
> On
Sean,
Please correct me if I'm wrong, but I think this needs to happen on RCs not on
CI tests.
Couple of possible problems I personally see with this approach:
1) Extensive pressure to push new client releases (perhaps the released client
is not as good as intended for just to provide someone t
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: 16 September 2014 18:10
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance][all] Help with interpreting the log
> level
> guidelines
>
> On 09/16/2014 1
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 16 September 2014 17:31
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance][all] Help with interpreting the log
> level
> guidelines
>
> On 09/16/2014 1
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 16 September 2014 15:56
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance][all] Help with interpreting the log
> level
> guidelines
>
> On 09/16/2014 1
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 16 September 2014 12:40
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance][all] Help with interpreting the log
> level
> guidelines
>
> On 09/16/2014 0
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 16 September 2014 10:08
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance][all] Help with interpreting the log
> level
> guidelines
>
> On 09/16/2014 01:10 AM, Clint Byrum wrote:
>
All,
There is two changes still not landed from
https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging
https://review.openstack.org/116626
and
https://review.openstack.org/#/c/117204/
Merge of the changes was delayed over J3 to avoid any potential merge
conflicts. There was
> -Original Message-
> From: Clark Boylan [mailto:cboy...@sapwetik.org]
> Sent: 03 September 2014 21:57
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt
>
>
>
> On Wed, Sep 3, 2014, at 0
> -Original Message-
> From: Clark Boylan [mailto:cboy...@sapwetik.org]
> Sent: 03 September 2014 20:10
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt
>
>
>
> On Wed, Sep 3, 2014, at 1
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 03 September 2014 13:37
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [all] [glance] do NOT ever sort requirements.txt
>
> I'm not sure why people keep showing up with "s
In principle I like the idea and concept, a lot. In practice I don't think
glance code is ready in a state that we could say SIGHUP reloads our configs.
Even more my concern is that based on the behavior seen some config options
gets picked up and some does not.
As long as we do not have defini
Another well working option that can be easily used:
1) get a Linux system with internet connection (local box, VM in a cloud,
whatever floats your boat)
2) install irssi and screen
3) run irssi in a screen
Now you can login (local console, ssh, telnet, mosh again pick your
preferred) into
Hi All,
While investigating glanceclient gating issues we narrowed it down to requests
2.4.0 which was released 2014-08-29. Urllib3 seems to be raising new
ProtocolError which does not get catched and breaks at least glanceclient.
Following error can be seen on console "ProtocolError: ('Connecti
Hi All,
Looking the queue lengths from Zuul, one thing came to my mind. There is quite
a few heavy non-voting test jobs running specifically on the check lines. Would
it be possible to disable these non-voting jobs, lets say, week before freeze
and re-enable them after the rush has calmed down?
Good Morning/Day,
I have just started Etherpad
https://etherpad.openstack.org/p/glance-bugday-progress for tracking. Please
also join to #openstack-glance @Freenode to join the chat. All hands onboard
would be appreciated!
BR,
Erno
From: Fei Long Wang [mailto:feil...@catalyst.net.nz]
Sent: 11
Hi all,
As Arnaud requested on his comment to https://review.openstack.org/#/c/99622/ I
have done quick analysis of Glance logging.
Please find the results attached to this e-mail. The output is file by file,
but if you're interested only about the totals, please see the end of the file.
BR,
E
Hi,
We hit nasty situation where _() was removed from DEBUG level logging and there
is exception included like following:
msg = "Forbidden upload attempt: %s" % e
This caused gettextutils raising UnicodeError:
2014-06-26 18:16:24.221 | File "glance/openstack/common/gettextutils.py",
line 333,
1 - 100 of 106 matches
Mail list logo
