> On Apr 8, 2014 10:24 PM, "Doug Hellmann"
> wrote:
>>
>> Maybe those changes should be added to our cgit stylesheet?
>>
>> Doug
>>
>> On Mon, Apr 7, 2014 at 9:23 PM, Zhongyue Luo
>> wrote:
>> > Hi,
>> >
>> >
I have started writing up some general steps for adding oslo libs to
projects, and I would like some feedback about the results. They can't
go into too much detail about specific changes in a project, because
those will vary by library and project. I would like to know if the
order makes sense and
lps!
>
> Cheers,
> Josh
> ____
> From: Doug Hellmann [doug.hellm...@dreamhost.com]
> Sent: Thursday, April 10, 2014 12:24 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Infra] How to s
I see that several projects have their Oslo liaisons lined up
(https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons). It would be
great if we had at least one volunteer from each project before the
summit, so we can get a head start on the coordination work.
Doug
_
Thanks, Thomas! If you're on IRC, you can join us in #openstack-oslo.
On Fri, Apr 11, 2014 at 11:19 AM, Thomas Herve
wrote:
>> I see that several projects have their Oslo liaisons lined up
>> (https://wiki.openstack.org/wiki/Oslo/ProjectLiaisons). It would be
>> great if we had at least one volun
The Oslo team has had a regular meeting slot on Friday at 1400 UTC. In
the past, we only held meetings irregularly when we had something
definite to discuss. During Juno, I expect us to need to coordinate
more closely with the new liaison team as well as internally, so I
would like to start holding
As someone who maintains a shell-script project across several
"sh-like" shells, I can say the edge cases cause enough work and
testing hassles that you shouldn't undertake it lightly. Is there any
particular need to run these tools under a non-bash shell?
Doug
On Mon, Apr 14, 2014 at 12:26 PM, B
ed to move to another room, but that's not a big deal.
Doug
On Mon, Apr 14, 2014 at 1:54 PM, Joshua Harlow wrote:
> Is anything around 1800 UTC or 1900 UTC possible?
>
> I'll try to be there, 1400 UTC is pretty early for us pacific coast folk.
>
> -----Original
> too?
>
> One week @ 1600UTC, next week @ 2000UTC (and so-on).
>
> -Original Message-
> From: Doug Hellmann
> Date: Monday, April 14, 2014 at 11:53 AM
> To: Joshua Harlow
> Cc: "OpenStack Development Mailing List (not for usage questions)"
>
>
On Wed, Apr 16, 2014 at 1:56 PM, Dan Smith wrote:
>> Do we really want to -1 for spelling mistake in nova-specs?
>
> I do, yes. These documents are intended to be read by deployers and
> future developers. I think it's really important that they're useful in
> that regard.
>
>> This is really a ba
ay 25 April at 1600 UTC in #openstack-meeting-alt
Sorry for any confusion the change causes,
Doug
On Mon, Apr 14, 2014 at 12:07 PM, Doug Hellmann
wrote:
> The Oslo team has had a regular meeting slot on Friday at 1400 UTC. In
> the past, we only held meetings irregularly when we had something
&g
Nice work, Victor!
I left a few comments on the commits that were made after the original
history was exported from the incubator. There were a couple of small
things to address before importing the library, and a couple that can
wait until we have the normal code review system. I'd say just add n
I propose that we add Victor Stinner (haypo on freenode) to the Oslo
core reviewers team.
Victor is a Python core contributor, and works on the development team
at eNovance. He created trollius, a port of Python 3's tulip/asyncio
module to Python 2, at least in part to enable a driver for
oslo.mes
On Mon, Apr 21, 2014 at 3:07 PM, Kyle Mestery wrote:
> For the upcoming Summit there are 3 sessions filed around "Service
> VMs" in Neutron. After discussing this with a few different people,
> I'd like to propose the idea that the "Service VM" work be moved out
> of Neutron and into it's own proj
On Tue, Apr 22, 2014 at 6:49 PM, Isaku Yamahata
wrote:
> Hi. Keyle, thank you for starting this discussion to make progress.
>
> On Mon, Apr 21, 2014 at 08:41:19PM -0500,
> Kyle Mestery wrote:
>
>> On Mon, Apr 21, 2014 at 4:20 PM, Doug Hellmann
>> wrote:
>>
The Oslo team is starting to remove deprecated code from the incubator for
libraries that graduated this cycle, in preparation for the work we will be
doing in Kilo.
Any fixes for those modules needed before the final releases for the other
projects should be submitted to the stable/juno branch
On Sep 19, 2014, at 10:34 AM, Ken Giusti wrote:
> On Mon Sep 8 15:18:35 UTC 2014, Doug Hellmann wrote:
>> On Sep 8, 2014, at 10:35 AM, Antonio Messina > gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We tested briefly ZeroMQ with Havana last year, bu
Done.
Welcome to the team, Radoslav!
Doug
On Sep 19, 2014, at 7:52 AM, Vipin Balachandran
wrote:
> +1
>
> From: Vui Chiap Lam [mailto:vuich...@vmware.com]
> Sent: Tuesday, September 16, 2014 10:52 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [opensta
On Sep 19, 2014, at 6:56 AM, David Chadwick wrote:
>
>
> On 18/09/2014 22:14, Doug Hellmann wrote:
>>
>> On Sep 18, 2014, at 4:34 PM, David Chadwick
>> wrote:
>>
>>>
>>>
>>> On 18/09/2014 21:04, Doug Hellmann wrote:
>>
On Sep 19, 2014, at 11:22 AM, Sean Dague wrote:
> I'd like to request a requirements freeze exception for websockify -
> https://review.openstack.org/#/c/122702/
>
> The rationale for this is that websockify version bump fixes a Nova bug
> about zombie processes - https://bugs.launchpad.net/nova
The Oslo team has released oslo.db 1.0.1, a patch release on the final version
of the library released for juno. This update includes a fix for a test fixture
class that has been causing some stability problems in the nova gate.
https://launchpad.net/oslo.db/+milestone/1.0.1
Doug
On Sep 21, 2014, at 9:59 PM, Adam Young wrote:
> On 09/19/2014 01:43 PM, Doug Hellmann wrote:
>> On Sep 19, 2014, at 6:56 AM, David Chadwick wrote:
>>
>>>
>>> On 18/09/2014 22:14, Doug Hellmann wrote:
>>>> On Sep 18, 2014, at 4:34 PM, David Chad
On Sep 19, 2014, at 10:37 PM, Monty Taylor wrote:
> On 09/19/2014 03:29 AM, Thierry Carrez wrote:
>> Monty Taylor wrote:
>>> I've recently been thinking a lot about Sean's Layers stuff. So I wrote
>>> a blog post which Jim Blair and Devananda were kind enough to help me edit.
>>>
>>> http://ina
On Sep 19, 2014, at 6:29 AM, Thierry Carrez wrote:
> Monty Taylor wrote:
>> I've recently been thinking a lot about Sean's Layers stuff. So I wrote
>> a blog post which Jim Blair and Devananda were kind enough to help me edit.
>>
>> http://inaugust.com/post/108
>
> Hey Monty,
>
> As you can i
On Sep 18, 2014, at 2:53 PM, Monty Taylor wrote:
> Hey all,
>
> I've recently been thinking a lot about Sean's Layers stuff. So I wrote
> a blog post which Jim Blair and Devananda were kind enough to help me edit.
>
> http://inaugust.com/post/108
>
> Enjoy.
I’ve read through this a few times
On Sep 22, 2014, at 11:07 AM, Radomir Dopieralski
wrote:
> Horizon's tests were recently broken by a change in the Ceilometer
> client that removed a deprecated exception. The exception was deprecated
> for a while already, but as it often is, nobody did the
> work of removing all references to
On Sep 22, 2014, at 12:19 PM, Gordon Sim wrote:
> On 09/22/2014 03:40 PM, Geoff O'Callaghan wrote:
>> That being said I'm not sure why a well constructed zaqar with an rpc
>> interface couldn't meet the requirements of oslo.messsaging and much more.
>
> What Zaqar is today and what it might bec
On Sep 22, 2014, at 3:11 PM, Tim Bell wrote:
>
> On 22 Sep 2014, at 20:53, Doug Hellmann wrote:
>
>>
>> On Sep 19, 2014, at 6:29 AM, Thierry Carrez wrote:
>>
>>> Monty Taylor wrote:
>>>> I've recently been thinking a lot about Sean&
On Sep 22, 2014, at 2:17 PM, Monty Taylor wrote:
> On 09/22/2014 10:58 AM, Kevin L. Mitchell wrote:
>> On Mon, 2014-09-22 at 10:32 -0700, Armando M. wrote:
>>> What about:
>>>
>>> https://github.com/openstack/neutron/blob/master/test-requirements.txt#L12
>>
>> Pulling in ordereddict doesn't do
On Sep 22, 2014, at 3:43 PM, Doug Hellmann wrote:
>
> On Sep 22, 2014, at 2:17 PM, Monty Taylor wrote:
>
>> On 09/22/2014 10:58 AM, Kevin L. Mitchell wrote:
>>> On Mon, 2014-09-22 at 10:32 -0700, Armando M. wrote:
>>>> What about:
>>>>
>&
We started a retrospective for Oslo during our meeting last week. I promised to
summarize the notes and start a thread here on the mailing list to make
discussion easier. See [1] for the rough notes. Please follow up here,
especially if you have any thoughts on things we can improve during kilo.
On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
wrote:
> On Mon, Sep 22, 2014 at 12:33 PM, Doug Hellmann wrote:
>>
>> On Sep 22, 2014, at 3:11 PM, Tim Bell wrote:
>>
>>>
>>> On 22 Sep 2014, at 20:53, Doug Hellmann wrote:
>>>
>&g
On Sep 23, 2014, at 4:35 AM, Thomas Goirand wrote:
> On 09/18/2014 10:04 PM, Doug Hellmann wrote:
>> All of the final releases for the Oslo libraries for the Juno cycle are
>> available on PyPI. I’m working on a couple of patches to the global
>> requirements list to u
On Sep 23, 2014, at 5:18 AM, Thierry Carrez wrote:
> Devananda van der Veen wrote:
>> On Mon, Sep 22, 2014 at 2:27 PM, Doug Hellmann wrote:
>>> On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
>>> wrote:
>>>
>>>> One of the prima
On Sep 22, 2014, at 8:05 PM, Devananda van der Veen
wrote:
> On Mon, Sep 22, 2014 at 2:27 PM, Doug Hellmann wrote:
>>
>> On Sep 22, 2014, at 5:10 PM, Devananda van der Veen
>> wrote:
>>
>>> One of the primary effects of integration, as far as the releas
On Sep 23, 2014, at 7:53 AM, Daniel P. Berrange wrote:
> On Tue, Sep 23, 2014 at 07:42:30AM -0400, Sean Dague wrote:
>> On 09/23/2014 02:56 AM, Thierry Carrez wrote:
>>> Hi everyone,
>>>
>>> Rather than waste a design summit session about it, I propose we review
>>> the proposed Kilo release cy
I am running for PTL for Oslo for the Kilo release cycle.
I have served 2 terms now, and my tl;dr platform for Kilo is, “More of the
same!”
I have already posted the retrospective the team put together for Juno [1], so
I won’t go over those items in depth here. From my perspective, the team is
On Sep 19, 2014, at 1:16 PM, Doug Hellmann wrote:
> The Oslo team is starting to remove deprecated code from the incubator for
> libraries that graduated this cycle, in preparation for the work we will be
> doing in Kilo.
>
> Any fixes for those modules needed before the fin
On Sep 23, 2014, at 1:24 PM, Mark McClain wrote:
>
> On Sep 19, 2014, at 9:13 AM, Sean Dague wrote:
>
>> Cross interaction with Neutron and Cinder remains racey. We are pretty
>> optimistic on when resources will be available. Even the event interface
>> with Neutron hasn't fully addressed th
James Carey (jecarey) from IBM has done the 3rd most reviews of oslo.i18n this
cycle [1]. His feedback has been useful, and I think he would be a good
addition to the team for maintaining oslo.i18n.
Let me know what you think, please.
Doug
[1] http://stackalytics.com/?module=oslo.i18n
On Sep 23, 2014, at 12:52 PM, Thierry Carrez wrote:
> Devananda van der Veen wrote:
>> On Tue, Sep 23, 2014 at 8:40 AM, Doug Hellmann wrote:
>>> One is a technical discussion that has nothing at all to do with
>>> governance. The other is entirely about govern
Since the Oslo team works slightly out of phase with the rest of OpenStack, and
we’re going to have less summit space than usual, I thought we should go ahead
and start queuing up specs for review. That will give us some time to approve
the “easy” ones and identify issues we need to work through
On Sep 25, 2014, at 6:14 PM, Robert Collins wrote:
> On 24 September 2014 11:03, Robert Collins wrote:
>
>> So... FWIW I think I've got a cleaner implementation of namespaces
>> *for our context* - it takes inspiration from the PEP-420 discussion
>> and final design. It all started when Mike r
On Sep 23, 2014, at 7:03 PM, Robert Collins wrote:
> On 29 August 2014 04:42, Sean Dague wrote:
>> On 08/28/2014 12:22 PM, Doug Hellmann wrote:
> ...
>>> The problem is that the setuptools implementation of namespace packages
>>> breaks in a way that is repeatab
On Sep 26, 2014, at 2:27 PM, Sean Dague wrote:
> As we've been talking about the test disaggregation the hamster wheels
> in the back of my brain have been churning on the library testing
> problem I think we currently have. Namely, openstack components mostly
> don't rely on released library ve
On Sep 26, 2014, at 4:50 PM, Sean Dague wrote:
> On 09/26/2014 04:22 PM, Doug Hellmann wrote:
>>
>> On Sep 26, 2014, at 2:27 PM, Sean Dague wrote:
>>
>>> As we've been talking about the test disaggregation the hamster wheels
>>> in the back o
On Sep 28, 2014, at 5:00 PM, Robert Collins wrote:
> On 27 September 2014 10:07, Robert Collins wrote:
>
>> TripleO has been running pip releases of clients in servers from the
>> get go, and I've lost track of the number of bad dependency bugs we've
>> encounted. We've hit many more of those
On Sep 29, 2014, at 12:03 PM, Julien Danjou wrote:
> Hi,
>
> I was looking at xmlutils today, and I took a look at the history of
> this file that seems to come from a CVE almost 2 years ago.
>
> What is surprising is that, unless I missed something, the only user of
> that lib is Nova. Other
On Sep 29, 2014, at 5:51 AM, Thierry Carrez wrote:
> Boris Pavlovic wrote:
>> it goes without saying that working on cross-project stuff in OpenStack
>> is quite hard task.
>>
>> Because it's always hard to align something between a lot of people from
>> different project. And when topic start
On Sep 29, 2014, at 4:22 PM, Robert Collins wrote:
> On 30 September 2014 03:10, Doug Hellmann wrote:
>>
>> On Sep 28, 2014, at 5:00 PM, Robert Collins
>> wrote:
>
>> As far as I know, the client libraries aren’t being released as alphas. The
>> Oslo li
I agree, it sounds like option 2 is safe.
Julien, I updated your commit message on
https://review.openstack.org/#/c/125021/ to point to this thread.
Write-it-down-ly,
Doug
On Sep 30, 2014, at 7:17 AM, Davanum Srinivas wrote:
> Julien,
>
> I believe all the lessons learned from defusedxml (se
;
> -Ben
>
> On 09/30/2014 08:28 AM, Doug Hellmann wrote:
>> I agree, it sounds like option 2 is safe.
>>
>> Julien, I updated your commit message on
>> https://review.openstack.org/#/c/125021/ to point to this thread.
>>
>> Write-it-down-ly,
>&g
The Oslo team has released version 1.0.2 of oslo.db. This patch release on the
Juno series includes a fix for bug 1374497 (“change in oslo.db ‘ping’ handling
is causing issues in projects that are not using transactions”).
https://bugs.launchpad.net/oslo.db/+bug/1374497
Doug
_
As promised at this week’s TC meeting, I have applied the various blog posts
and mailing list threads related to changing our governance model to a series
of patches against the openstack/governance repository [1].
I have tried to include all of the inputs, as well as my own opinions, and look
On Oct 2, 2014, at 5:16 PM, Doug Hellmann wrote:
> As promised at this week’s TC meeting, I have applied the various blog posts
> and mailing list threads related to changing our governance model to a series
> of patches against the openstack/governance repository [1].
>
>
Sean Dague is working on adjusting the gate tests related to Oslo libraries and
the integrated projects. I don’t think we have any releases planned, but just
in case:
Please wait to tag any new releases of any Oslo libraries until this work is
complete to ensure that the new jobs are functionin
On Oct 3, 2014, at 7:13 AM, Eoghan Glynn wrote:
>
>> As promised at this week’s TC meeting, I have applied the various blog posts
>> and mailing list threads related to changing our governance model to a
>> series of patches against the openstack/governance repository [1].
>>
>> I have tried t
On Oct 3, 2014, at 12:46 AM, Joe Gordon wrote:
>
> On Thu, Oct 2, 2014 at 4:16 PM, Devananda van der Veen
> wrote:
> On Thu, Oct 2, 2014 at 2:16 PM, Doug Hellmann wrote:
> > As promised at this week’s TC meeting, I have applied the various blog
> > posts and mailing
On Oct 3, 2014, at 9:02 AM, Doug Hellmann wrote:
>
> On Oct 3, 2014, at 7:13 AM, Eoghan Glynn wrote:
>
>>
>>> As promised at this week’s TC meeting, I have applied the various blog posts
>>> and mailing list threads related to changing our governance model t
On Oct 3, 2014, at 9:25 AM, Anne Gentle wrote:
>
>
> On Fri, Oct 3, 2014 at 8:07 AM, Doug Hellmann wrote:
>
> On Oct 3, 2014, at 12:46 AM, Joe Gordon wrote:
>
>>
>> On Thu, Oct 2, 2014 at 4:16 PM, Devananda van der Veen
>> wrote:
>> On Thu, Oc
On Oct 3, 2014, at 12:26 PM, Joe Gordon wrote:
>
>
> On Fri, Oct 3, 2014 at 6:07 AM, Doug Hellmann wrote:
>
> On Oct 3, 2014, at 12:46 AM, Joe Gordon wrote:
>
>>
>> On Thu, Oct 2, 2014 at 4:16 PM, Devananda van der Veen
>> wrote:
>> On Thu, Oc
On Oct 3, 2014, at 1:09 PM, Neal, Phil wrote:
>> From: Dina Belova [mailto:dbel...@mirantis.com]
>> On Friday, October 03, 2014 2:53 AM
>>
>> Igor,
>>
>> Personally this idea looks really nice to me, as this will help to avoid
>> strange code being merged and not found via reviewing process.
>
The Oslo team is responsible for managing code shared between projects. There
are a LOT more projects than Oslo team members, so we created the liaison
program at the beginning of the Juno cycle, asking each team that uses Oslo
libraries to provide one volunteer liaison. Our liaisons facilitate
On Oct 3, 2014, at 11:38 AM, Tristan Cacqueray
wrote:
> Candidate proposals for the Technical Committee positions (6 positions)
> are now open and will remain open until 05:59 UTC October 10, 2014.
>
> Candidates for the Technical Committee Positions: Any Foundation
> individual member can pro
In the past, summit planning has been left up to the PTL, but this time all of
the projects are trying a more collaborative process. We’ve talked about it
briefly in previous meetings, and set up an etherpad to record ideas [1]. I
would like to use our meeting this week to work through some of t
On Oct 7, 2014, at 7:55 AM, Ihar Hrachyshka wrote:
> Signed PGP part
> On 06/10/14 17:56, Doug Hellmann wrote:
> > The Oslo team is responsible for managing code shared between
> > projects. There are a LOT more projects than Oslo team members, so
> > we created th
On Oct 7, 2014, at 3:01 PM, Roman Podoliaka wrote:
> Hi all,
>
> Last Friday we decided to find a better time for the weekly team
> meeting. Keeping in mind that DST ends soon (October the 26th in
> Europe, November the 2nd in the US), I think, we can choose from:
>
> - Mondays at 1600 UTC [1]
ory: https://review.openstack.org/#/q/reviewer:2472,n,z
Commit history: https://review.openstack.org/#/q/owner:2472,n,z
Stackalytics: http://stackalytics.com/?user_id=doug-hellmann
Foundation: http://www.openstack.org/community/members/profile/359
OpenHUB: https://www.openhub.net/accounts/doughellmann
Freenode:
At the project meeting today we decided that since we have several programs
following the liaison system we should have a single page listing all liaisons,
instead of separate project-specific pages.
I have created https://wiki.openstack.org/wiki/CrossProjectLiaisons as that
page, and moved the
On Sep 23, 2014, at 5:03 PM, Doug Hellmann wrote:
> James Carey (jecarey) from IBM has done the 3rd most reviews of oslo.i18n
> this cycle [1]. His feedback has been useful, and I think he would be a good
> addition to the team for maintaining oslo.i18n.
>
> Let me know
On Oct 8, 2014, at 1:22 AM, Robert Collins wrote:
> On 8 October 2014 11:10, Mike Bayer wrote:
>> Hi folks -
>>
>> So just to update on the status here, for the transactional testing and all
>> that, I’ve had a blueprint in the queue for quite awhile:
>
> ...
>
> I'll probably time it out u
On Oct 8, 2014, at 5:20 AM, Julien Danjou wrote:
> On Tue, Oct 07 2014, Roman Podoliaka wrote:
>
>> - Mondays at 1600 UTC [1]: #openstack-meeting-alt, #openstack-meeting-3
>> - Thursdays at 1600 UTC [2]: #openstack-meeting-3
>
> One of these would be cool.
>
> --
> Julien Danjou
> -- Free So
On Oct 8, 2014, at 7:03 AM, Davanum Srinivas wrote:
> Salvatore, Joe,
>
> We do have this at the moment:
>
> https://github.com/openstack/oslo-incubator/blob/master/openstack/common/quota.py
>
> — dims
If someone wants to drive creating a useful library during kilo, please
consider adding t
On Oct 8, 2014, at 10:14 AM, Doug Hellmann wrote:
>
> On Oct 8, 2014, at 1:22 AM, Robert Collins wrote:
>
>> On 8 October 2014 11:10, Mike Bayer wrote:
>>> Hi folks -
>>>
>>> So just to update on the status here, for the transactional testing and
On Oct 9, 2014, at 4:30 PM, Matt Riedemann wrote:
> The sqlalchemy-migrate project is basically maintenance mode and the core
> team [1] is kind of a weird mix of people - all great people I'm sure, but I
> think it's more a team of people that stepped up when OpenStack took over the
> projec
On Oct 10, 2014, at 6:10 AM, Ihar Hrachyshka wrote:
> Signed PGP part
> On 09/10/14 23:44, Doug Hellmann wrote:
> >
> > On Oct 9, 2014, at 4:30 PM, Matt Riedemann
> > wrote:
> >
> >> The sqlalchemy-migrate project is basically maintenance mode and
> &
On Oct 10, 2014, at 12:36 PM, Chen CH Ji wrote:
> Thanks a lot for the info,
>
> So, my understanding is I need to wait for its released then someone need to
> change the code in
> projects (e.g. nova) to switch from its original method
> (nova/openstack/common/) to oslo.concurrency
> just
On Oct 8, 2014, at 10:19 AM, Doug Hellmann wrote:
>
> On Oct 8, 2014, at 5:20 AM, Julien Danjou wrote:
>
>> On Tue, Oct 07 2014, Roman Podoliaka wrote:
>>
>>> - Mondays at 1600 UTC [1]: #openstack-meeting-alt, #openstack-meeting-3
>>> - Thursday
On Oct 12, 2014, at 12:32 AM, Li Ma wrote:
>
> On 2014/9/17 22:34, Doug Hellmann wrote:
>>
>> The documentation in the oslo.messaging repository [2] would be a good place
>> to start for that. If we decide deployers/operators need the information we
>> can eith
I’ve put together a little script to generate a report of the projects using
modules that used to be in the oslo-incubator but that have moved to libraries
[1]. These modules have been deleted, and now only exist in the stable/juno
branch of the incubator. We do not anticipate back-porting fixes
The openstack/oslo-specs repository is open for submissions for Kilo, and the
Oslo team would appreciate your help in reviewing the proposed changes. Changes
to Oslo libraries affect all projects, so we want to collect as much input as
we can before committing to a direction. There are several s
On Oct 13, 2014, at 11:06 AM, Steven Hardy wrote:
> On Mon, Oct 13, 2014 at 09:20:38AM -0400, Doug Hellmann wrote:
>> I’ve put together a little script to generate a report of the projects using
>> modules that used to be in the oslo-incubator but that have moved to
>>
The QA and Documentation teams have adopted a liaison program similar to what
we did for Oslo during Juno. That means we need to provide someone from our
team to work with each of their teams. If you would like to volunteer for one
of the positions, put your name in the appropriate table on the
On Oct 13, 2014, at 5:49 PM, Chris Dent wrote:
> On Tue, 7 Oct 2014, Sandy Walsh wrote:
>
>> Haven't had any time to get anything written down (pressing deadlines
>> with StackTach.v3) but open to suggestions. Perhaps we should just add
>> something to the olso.messaging etherpad to find time a
o have
the work happen in Oslo somewhere so we can ensure those changes are useful to
and usable by all of the existing consumers.
Doug
[1] https://etherpad.openstack.org/p/kilo-oslo-library-proposals
>
> What's your opinion?
>
> Regards,
> Salvatore
>
> [1] https
On Oct 14, 2014, at 6:00 PM, Lance Bragstad wrote:
>
>
> On Tue, Oct 14, 2014 at 4:29 PM, Christopher Yeoh wrote:
> On Tue, 14 Oct 2014 10:29:34 -0500
> Lance Bragstad wrote:
>
> > I found a couple of free times available for a weekly meeting if
> > people are interested:
> >
> > https://re
orking on syncing it back with oslo-incubator during the Kilo
> release cycle.
>
> However, my query was about the quota module.
> From what I gather it seems not a lot of projects use it:
>
> $ find . -name openstack-common.conf | xargs grep quota
> $
>
> Salv
volumes across all
> his projects.
>
> -Ajaya
>
> Cheers,
> Ajaya
>
> On Wed, Oct 15, 2014 at 7:04 PM, Doug Hellmann wrote:
> Sigh. Because I typed the wrong command. Thanks for pointing that out.
>
> I don’t see any instances of “quota” in openstack-common.co
After today’s meeting, we have filled our seven session slots. Here’s the
proposed list, in no particular order. If you think something else needs to be
on the list, speak up today because I’ll be plugging all of this into the
scheduling tool in the next day or so.
https://etherpad.openstack.or
The Oslo team is pleased to announce the release of oslotest 1.2.0, our first
release for the Kilo cycle.
This release includes:
cfdb562 Updated from global requirements
118885e Set install_command in tox to avoid pre-releases
e5c14b7 Add an extra parameter for test directory in debugger script
The application projects are dropping python 2.6 support during Kilo, and I’ve
had several people ask recently about what this means for Oslo. Because we
create libraries that will be used by stable versions of projects that still
need to run on 2.6, we are going to need to maintain support for
On Oct 20, 2014, at 1:22 PM, Doug Hellmann wrote:
> After today’s meeting, we have filled our seven session slots. Here’s the
> proposed list, in no particular order. If you think something else needs to
> be on the list, speak up today because I’ll be plugging all of this
On Oct 23, 2014, at 6:27 AM, Chris Dent wrote:
>
> I've proposed a spec to Ceilometer
>
> https://review.openstack.org/#/c/129669/
>
> for a suite of declarative HTTP tests that would be runnable both in
> gate check jobs and in local dev environments.
>
> There's been some discussion that
On Oct 23, 2014, at 2:56 AM, Flavio Percoco wrote:
> On 10/22/2014 08:15 PM, Doug Hellmann wrote:
>> The application projects are dropping python 2.6 support during Kilo, and
>> I’ve had several people ask recently about what this means for Oslo. Because
>> we create l
On Oct 23, 2014, at 12:30 PM, Kevin L. Mitchell
wrote:
> On Thu, 2014-10-23 at 18:56 +0300, Andrey Kurilin wrote:
>> Just a joke: Can we drop supporting Python 2.6, when several project
>> still have hooks for Python 2.4?
>>
>> https://github.com/openstack/python-novaclient/blob/master/novacli
On Oct 24, 2014, at 6:58 AM, Chris Dent wrote:
> On Thu, 23 Oct 2014, Doug Hellmann wrote:
>
> Thanks for the feedback Doug, it's useful.
>
>> WebTest isn’t quite what you’re talking about, but does provide a
>> way to talk to a WSGI app from within a test su
The Oslo team is pleased to announce the release of stevedore version 1.1.0,
the first release in the Kilo series for stevedore.
This release includes the following fixes:
$ git log --oneline --no-merges 1.0.0..1.1.0
5749d54 Add pbr to dependency list
bb43bc4 Updated from global requirements
82f
The Oslo team is pleased to announce the release of oslo.conccurrency 0.1.0,
the first development release of the new library containing lockutils and
processutils.
Documentation for the library is available at
http://docs.openstack.org/developer/oslo.concurrency/
Please report issues via laun
On Oct 24, 2014, at 3:33 AM, Angelo Matarazzo
wrote:
> Hi all,
> I have a question for you devs.
> I don't understand the difference between this link
> http://git.openstack.org/cgit/openstack/governance/tree/reference/
> project-testing-interface.rst
> and
> https://wiki.openstack.org/wiki/P
On Oct 23, 2014, at 8:14 PM, Jeremy Stanley wrote:
> On 2014-10-23 17:18:04 -0400 (-0400), Doug Hellmann wrote:
>> I think we have to actually wait for M, don’t we (K & L represents
>> 1 year where J is supported, M is the first release where J is not
>> supported and
601 - 700 of 3431 matches
Mail list logo
