On Sep 10, 2014, at 4:34 PM, Yuriy Taraday wrote:
>
>
> On Tue, Sep 9, 2014 at 9:58 PM, Doug Hellmann wrote:
>
> On Sep 9, 2014, at 10:51 AM, Sean Dague wrote:
>
> > On 09/09/2014 10:41 AM, Doug Hellmann wrote:
> >>
> >> On Sep 8, 2014, at 8:18
On Sep 10, 2014, at 5:07 PM, James E. Blair wrote:
> Doug Hellmann writes:
>
>> I originally thought we would want to add these feeds to
>> planet.openstack.org, but given the length of some of the specs I’m
>> less sure of that. Instead, now I think it would be be
On Sep 10, 2014, at 5:05 PM, Chmouel Boudjnah wrote:
> Doug Hellmann writes:
>
>> I have completed a series of patches [1] for (I think) all of the
>> specs repositories to add RSS feeds so that when specs are approved
>> and merged they are easily publicized.
>
&g
On Sep 10, 2014, at 5:20 PM, Brant Knudson wrote:
>
>
> On Tue, Sep 9, 2014 at 4:19 PM, Sean Dague wrote:
> As we try to stabilize OpenStack Juno, many server projects need to get
> out final client releases that expose new features of their servers.
> While this seems like not a big deal, ea
On Sep 12, 2014, at 7:39 AM, Sean Dague wrote:
> I assume you, gentle OpenStack developers, often find yourself in a hair
> tearing out moment of frustration about why local unit tests are doing
> completely insane things. The code that it is stack tracing on is no
> where to be found, and yet i
On Sep 12, 2014, at 9:23 AM, Ihar Hrachyshka wrote:
> Signed PGP part
> On 12/09/14 13:20, Sean Dague wrote:
> > On 09/12/2014 06:41 AM, Ihar Hrachyshka wrote:
> >> Some updates/concerns/questions.
> >>
> >> The status of introducing a new driver to gate is:
> >>
> >> - all the patches for mysql
On Sep 12, 2014, at 11:21 AM, Mike Bayer wrote:
>
> On Sep 12, 2014, at 7:39 AM, Sean Dague wrote:
>
>> I assume you, gentle OpenStack developers, often find yourself in a hair
>> tearing out moment of frustration about why local unit tests are doing
>> completely insane things. The code that
On Sep 12, 2014, at 1:03 PM, Ihar Hrachyshka wrote:
> Signed PGP part
> On 12/09/14 17:30, Mike Bayer wrote:
> >
> > On Sep 12, 2014, at 10:40 AM, Ihar Hrachyshka
> > wrote:
> >
> >> Signed PGP part On 12/09/14 16:33, Mike Bayer wrote:
> >>> I agree with this, changing the MySQL driver now is n
On Sep 12, 2014, at 12:03 PM, Sean Dague wrote:
> On 09/12/2014 11:52 AM, Doug Hellmann wrote:
>>
>> On Sep 12, 2014, at 11:21 AM, Mike Bayer wrote:
>>
>>>
>>> On Sep 12, 2014, at 7:39 AM, Sean Dague wrote:
>>>
>>>> I assume you
On Sep 12, 2014, at 12:48 PM, Chris Dent wrote:
> On Fri, 12 Sep 2014, Doug Hellmann wrote:
>
>> We could use a git hook (see my earlier message in this thread) or we
>> could add a command to tox to remove them before starting the tests.
>> Neither of those solutions
The Oslo team has released version 0.4.0 of oslo.i18n. This version fixes a
missing dependency on the six library. We expect this to be the last
pre-release of oslo.i18n before the final release on Thursday.
Doug
___
OpenStack-dev mailing list
OpenSt
The Oslo team is pleased to announce the release of oslo.config 1.4.0.0a5. We
expect this to be the final alpha of oslo.config before the final release of
1.4 on Thursday.
This update includes a fix for variable substitution for deprecated or moved
options.
Doug
_
The Oslo team is pleased to announce the release of version 0.3.0 of
oslo.serialization. This version updates the dependencies of oslo.serialization
to be consistent with the other libraries. We expect this to be the last update
before we release 1.0.0 on Thursday
Doug
___
We’re down to 2 bugs, both of which have patches up for review.
James Carey has a fix for the decoding error we’re seeing in mask_password().
It needs to land in oslo.utils and oslo-incubator:
- utils: https://review.openstack.org/#/c/121657/
- incubator: https://review.openstack.org/#/c/121632/
This thread [1] has turned more “future focused", so I’m moving the
conversation to the -dev list where we usually have those sorts of discussions.
[1] http://lists.openstack.org/pipermail/openstack/2014-September/009253.html
On Sep 17, 2014, at 7:54 AM, James Page wrote:
> Signed PGP part
> H
On Sep 16, 2014, at 6:02 PM, Flavio Percoco wrote:
> On 09/16/2014 11:55 PM, Ben Nemec wrote:
>> Based on my reading of the wiki page about this it sounds like it should
>> be a sub-project of the Storage program. While it is targeted for use
>> by multiple projects, it's pretty specific to int
Earlier today we discovered a problem with the way pbr is generating dev
version numbers for commits following tags using alpha pre-version suffixes
[1]. Basically what’s happening is a commit following a tag like 1.3.0.0a3 is
coming out as a 1.3.0.devX version, which then appears to be older th
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 update the baseline in the applications. In all cases, the
final release is a second tag on a previously released version.
- oslo.conf
verlap in the instrumentation/annotation inside the main code for
> all of these.
>
> And from Doug Hellmann:
> 1. Sean has done a lot of analysis and started a spec on standardizing
> logging guidelines where he is gathering input from developers, deployers,
> and operators [1]. Becau
On Sep 18, 2014, at 10:16 AM, Kapil Thangavelu
wrote:
>
>
> On Thu, Sep 18, 2014 at 4:18 AM, Flavio Percoco wrote:
> On 09/17/2014 04:34 PM, Doug Hellmann wrote:
> > This thread [1] has turned more “future focused", so I’m moving the
> > conversation to the -d
On Sep 18, 2014, at 12:36 PM, David Chadwick wrote:
> Our recent work on federation suggests we need an improvement to the way
> the policy engine works. My understanding is that most functions are
> protected by the policy engine, but some are not. The latter functions
> are publicly accessible
On Sep 18, 2014, at 4:16 PM, Eric Windisch wrote:
>
>
> On Thu, Sep 18, 2014 at 3:55 PM, Doug Hellmann wrote:
>
> On Sep 18, 2014, at 10:16 AM, Kapil Thangavelu
> wrote:
>
> >
> >
> > On Thu, Sep 18, 2014 at 4:18 AM, Flavio Percoco wrote:
> >
On Sep 18, 2014, at 4:34 PM, David Chadwick wrote:
>
>
> On 18/09/2014 21:04, Doug Hellmann wrote:
>>
>> On Sep 18, 2014, at 12:36 PM, David Chadwick
>> wrote:
>>
>>> Our recent work on federation suggests we need an improvement to
>>> t
For our meeting tomorrow I would like to hold a retrospective of this cycle,
and talk about things that did or didn’t work and what we might want to do
differently during kilo. I’ve created an etherpad [1] for the notes in advance,
so if you have something to discuss please add it there. If you
Doug Hellmann writes:
> z...@openstack.org writes:
>
>> Build failed.
>>
>> - publish-openstack-releasenotes-python3
>> http://logs.openstack.org/86/86022835fb39cb318e28994ed0290caddfb451be/tag/publish-openstack-releasenotes-python3/7347218/
>> : POST_FAILU
z...@openstack.org writes:
> Build failed.
>
> - publish-openstack-releasenotes-python3
> http://logs.openstack.org/86/86022835fb39cb318e28994ed0290caddfb451be/tag/publish-openstack-releasenotes-python3/7347218/
> : POST_FAILURE in 13m 53s
> - publish-openstack-releasenotes
> http://logs.openst
TC members,
I have a series of patches up for review starting at [1] to create a
small library for reading and manipulating the project reference data in
the YAML files in the openstack/governance repository. After copying
similar code into a 3rd repository that wants to consume it last cycle,
I t
Jeremy Stanley writes:
> On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> Did I miss any options or issues with this approach?
>
> https://review.openstack.org/578557
How high of a priority is rolling that feature out? It does seem to
eliminate this part
Doug Hellmann writes:
> TC members,
>
> The TC will be meeting on 1 Nov at 1400 UTC in #openstack-tc to discuss
> some of our ongoing initiatives. Here is the agenda for this week.
>
> * meeting procedures
>
> * discussion of topics for joint leadership meeting
We will have a session at the forum to discuss the community-wide goals
[0] we want to select for the T cycle. That's a long way off, but given
the fact that we don't have a PTG between Berlin and Denver, and that
we've recently had feedback that we need to have tools finished better
before startin
Doug Hellmann writes:
> Doug Hellmann writes:
>
> I asked the owners of the name "heat" to allow us to use it, and they
> rejected the request. So, I proposed a change to heat to update the
> sdist name to "openstack-heat".
>
> * https://review.openst
Matt Riedemann writes:
> This is a follow up to a dev ML email [1] where I noticed that some
> implementations of the upgrade-checkers goal were failing because some
> projects still use the oslo_i18n.enable_lazy() hook for lazy log message
> translation (and maybe API responses?).
>
> The ver
TC members,
I have updated the liaison assignments to fill in all of the
gaps. Please take a moment to review the list [1] so you know your
assignments.
Next week will be a good opportunity to touch bases with your teams.
Doug
[1] https://wiki.openstack.org/wiki/OpenStack_health_tracker#Project
This is the weekly summary of work being done by the Technical Committee
members. The full list of active items is managed in the wiki:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
Matt Riedemann writes:
> On 11/5/2018 1:36 PM, Doug Hellmann wrote:
>> I think the lazy stuff was all about the API responses. The log
>> translations worked a completely different way.
>
> Yeah maybe. And if so, I came across this in one of the blueprints:
>
> https
Sean McGinnis writes:
> I'm interested in some feedback from the community, particularly those running
> OpenStack deployments, as to whether FIPS compliance [0][1] is something folks
> are looking for.
>
> I've been seeing small changes starting to be proposed here and there for
> things like MD
Luke Hinds writes:
> On Tue, Nov 6, 2018 at 2:04 PM Julia Kreger
> wrote:
>
>>
>>
>> On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann
>> wrote:
>>
>>> Sean McGinnis writes:
>>>
>>> > I'm interested in some feedback from the
Ghanshyam Mann writes:
> On Wed, 07 Nov 2018 06:51:32 +0900 Slawomir Kaplonski
> wrote
> > Hi,
> >
> > > Wiadomość napisana przez Jeremy Stanley w dniu
> 06.11.2018, o godz. 22:25:
> > >
> > > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
> > > [...]
> > >
Joshua Cornutt writes:
> Doug,
>
> I have such a list put together (my various installation documents for
> getting these clouds working in FIPS mode) but it's hardly ready for
> public consumption. I planned on releasing each bit as a code change
> and/or bug ticket and letting the community con
Corey Bryant writes:
> On Wed, Oct 10, 2018 at 8:45 AM Corey Bryant
> wrote:
>
> I'd like to start moving forward with enabling py37 unit tests for a subset
> of projects. Rather than putting too much load on infra by enabling 3 x py3
> unit tests for every project, this would just focus on enab
Mohammed Naser writes:
> On Wed, Nov 7, 2018 at 2:07 PM Dr. Jens Harbott (frickler)
> wrote:
>>
>> 2018-11-07 12:47 GMT+00:00 Mohammed Naser :
>> > On Wed, Nov 7, 2018 at 1:37 PM Doug Hellmann wrote:
>> >>
>> >> Corey Bryant writes:
>>
Joshua Cornutt writes:
> On Wed, Nov 7, 2018 at 7:30 AM Doug Hellmann wrote:
>>
>> Joshua Cornutt writes:
>>
>> > Doug,
>> >
>> > I have such a list put together (my various installation documents for
>> > getting these clouds wo
Luka Peschke writes:
> Hello,
>
> I'm making this e-mail to announce that the CloudKitty project will be
> holding IRC meetings from now on. They will be held in the #cloudkitty
> channel on Freenode. They should (for now) be held on the first Friday
> of each month at 15h00 UTC. Of course, th
ngs, so that sounds like a good
plan.
Thanks!
>
> Le 2018-11-07 18:43, Doug Hellmann a écrit :
>> Luka Peschke writes:
>>
>>> Hello,
>>>
>>> I'm making this e-mail to announce that the CloudKitty project will
>>> be
>>> holdin
Akihiro Motoki writes:
> Hi,
>
> Horizon logging depends on Django configuration which supports full python
> logging [1].
> [1] does not provide enough examples.
> Perhaps [2] will help you (though I haven't tested it).
Based on https://docs.djangoproject.com/en/2.1/topics/logging/ it looks
lik
On Mon, Nov 18, 2013 at 8:58 PM, Lu, Lianhao wrote:
>
> Doug Hellmann wrote on 2013-11-19:
> >
> > On Mon, Nov 18, 2013 at 12:25 PM, Devananda van der Veen <
> devananda@gmail.com> wrote:
> >
> >
> > Hi Lianhao Lu,
> >
> >
On Tue, Nov 19, 2013 at 9:12 PM, John Griffith
wrote:
> On Mon, Nov 18, 2013 at 3:53 PM, Mark McLoughlin
> wrote:
> > On Mon, 2013-11-18 at 17:24 +, Duncan Thomas wrote:
> >> Random OSLO updates with no list of what changed, what got fixed etc
> >> are unlikely to get review attention - doing
On Wed, Nov 20, 2013 at 3:37 AM, Elena Ezhova wrote:
>
> 20.11.2013, 06:18, "John Griffith" :
>
>
> On Mon, Nov 18, 2013 at 3:53 PM, Mark McLoughlin
> wrote:
>
> > On Mon, 2013-11-18 at 17:24 +, Duncan Thomas wrote:
> >> Random OSLO updates with no list of what changed, what got fixed etc
On Fri, Nov 22, 2013 at 11:21 AM, Duncan Thomas wrote:
> On 22 November 2013 12:27, Elena Ezhova wrote:
> > But what if I want to update some module that consists of ten or even
> more
> > files (like rpc or db) and each of these files has quite a long change
> log?
> > In that case the commit me
On Fri, Nov 22, 2013 at 4:11 AM, Flavio Percoco wrote:
> Greetings,
>
> Based on the recent discussion that came out about not having enough
> information in the commit message when syncing oslo-incubator modules,
> I was thinking that besides encouraging people to write better commit
> messages,
On Fri, Nov 22, 2013 at 11:24 AM, Duncan Thomas wrote:
> On 22 November 2013 14:59, Ben Nemec wrote:
>
> > One other thought I had was to add the ability to split one Oslo sync up
> > into multiple commits, either one per module, or even one per Oslo commit
> > for some really large module change
On Thu, Nov 21, 2013 at 2:37 PM, Gordon Chung wrote:
>
> > In all cases, these are free string fields. `user_id' and `project_id'
> > map to Keystone _most of the time_,
>
> i'm sort of torn between the two -- which is why i brought it up i guess.
> i like the flexibility of having resource as a
Thanks for the reminder, Sandy.
https://bugs.launchpad.net/oslo/+bug/1254300
On Sat, Nov 23, 2013 at 9:39 AM, Sandy Walsh wrote:
> Seeing this thread reminded me:
>
> We need support in the update script for entry points in olso setup.cfg to
> make their way into the target project.
>
> So, if
On Sun, Nov 24, 2013 at 12:08 AM, Morgan Fainberg wrote:
> In all honesty it doesn't matter which term we go with. As long as we are
> consistent and define the meaning. I think we can argue intuitive vs
> non-intuitive in this case unto the ground. I prefer "project" to tenant,
> but beyond b
On Mon, Nov 25, 2013 at 3:56 PM, Devananda van der Veen <
devananda@gmail.com> wrote:
> Hi!
>
> Very good questions. I think most of them are directed towards the
> Ceilometer team, but I have answered a few bits inline.
>
>
> On Mon, Nov 25, 2013 at 7:24 AM, wanghaomeng wrote:
>
>>
>> Hello
On Wed, Nov 27, 2013 at 5:21 PM, Georgy Okrokvertskhov <
gokrokvertsk...@mirantis.com> wrote:
> Hi,
>
> I am working on the user-authentication BP implementation. I need to
> introduce a new configuration option for enable or disable keystone
> authentication for incoming request. I am looking for
On Thu, Nov 28, 2013 at 1:00 PM, Devananda van der Veen <
devananda@gmail.com> wrote:
>
> On Nov 25, 2013 7:13 PM, "Doug Hellmann"
> wrote:
> >
> >
> >
> >
> > On Mon, Nov 25, 2013 at 3:56 PM, Devananda van der Veen <
> deva
We have a review up (https://review.openstack.org/#/c/58297/) to add some
features to the notification system in the oslo incubator. THe notification
system is being moved into oslo.messaging, and so we have the question of
whether to accept the patch to the incubated version, move it to
oslo.messa
On Fri, Nov 29, 2013 at 2:14 PM, Sandy Walsh wrote:
> So, as I mention in the branch, what about deployments that haven't
> transitioned to the library but would like to cherry pick this feature?
>
> "after it starts moving into a library" can leave a very big gap when the
> functionality isn't av
On Sat, Nov 30, 2013 at 3:52 PM, Sandy Walsh wrote:
>
>
> On 11/29/2013 03:58 PM, Doug Hellmann wrote:
> >
> >
> >
> > On Fri, Nov 29, 2013 at 2:14 PM, Sandy Walsh > <mailto:sandy.wa...@rackspace.com>> wrote:
> >
> > So, as I m
On Mon, Dec 2, 2013 at 8:08 AM, Sandy Walsh wrote:
>
>
> On 12/01/2013 06:40 PM, Doug Hellmann wrote:
> >
> >
> >
> > On Sat, Nov 30, 2013 at 3:52 PM, Sandy Walsh > <mailto:sandy.wa...@rackspace.com>> wrote:
> >
> >
On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant wrote:
> On 11/29/2013 01:39 PM, Doug Hellmann wrote:
> > We have a review up (https://review.openstack.org/#/c/58297/) to add
> > some features to the notification system in the oslo incubator. THe
> > notification syste
On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann
wrote:
>
>
>
> On Mon, Dec 2, 2013 at 8:36 AM, Russell Bryant wrote:
>
>> On 11/29/2013 01:39 PM, Doug Hellmann wrote:
>> > We have a review up (https://review.openstack.org/#/c/58297/) to add
>> > some features
On Mon, Dec 2, 2013 at 9:06 AM, Russell Bryant wrote:
> On 12/02/2013 08:53 AM, Doug Hellmann wrote:
> >
> >
> >
> > On Mon, Dec 2, 2013 at 8:46 AM, Doug Hellmann
> > mailto:doug.hellm...@dreamhost.com>>
> wrote:
> >
> >
> >
On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote:
>
>
>
> On Mon, Dec 2, 2013 at 6:06 AM, Russell Bryant wrote:
>
>> On 12/02/2013 08:53 AM, Doug Hellmann wrote:
>> >
>> >
>> >
>> > On Mon, Dec 2, 2013 at 8:46 AM, Doug He
On Mon, Dec 2, 2013 at 9:25 AM, Flavio Percoco wrote:
> On 02/12/13 09:06 -0500, Russell Bryant wrote:
>
>> On 12/02/2013 08:53 AM, Doug Hellmann wrote:
>> So, to clarify, possible flows would be:
>>
>> 1) An API moving to a library as-is, like rootwrap
>>
&g
On Mon, Dec 2, 2013 at 10:05 AM, Joe Gordon wrote:
>
>
>
> On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann > wrote:
>
>>
>>
>>
>> On Mon, Dec 2, 2013 at 9:22 AM, Joe Gordon wrote:
>>
>>>
>>>
>>>
>>> On Mon,
On Mon, Dec 2, 2013 at 10:26 AM, Doug Hellmann
wrote:
>
>
>
> On Mon, Dec 2, 2013 at 10:05 AM, Joe Gordon wrote:
>
>>
>>
>>
>> On Mon, Dec 2, 2013 at 6:37 AM, Doug Hellmann <
>> doug.hellm...@dreamhost.com> wrote:
>>
>>
On Mon, Dec 2, 2013 at 10:12 PM, Jarret Raim wrote:
> > There are two big parts to this, I think. One is techincal - a
> significant
> > portion
> > of OpenStack deployments will not work with this because Celery does not
> > work with their deployed messaging architecture.
> > See another reply
On Wednesday, December 4, 2013, Flavio Percoco wrote:
> On 04/12/13 01:13 +, Adrian Otto wrote:
>
>> Jay is right. What we have is probably close enough to what's in Nova to
>> qualify for oslo-incubator. The simplifications seem to me to have general
>> appeal so this code would be more attra
The stevedore library source repository is now hosted on stackforge (
https://git.openstack.org/cgit/stackforge/stevedore/) and I am in the
process of moving the bug tracker to launchpad (
https://launchpad.net/python-stevedore).
Doug
___
OpenStack-dev m
On Tue, Dec 10, 2013 at 9:47 AM, Nadya Privalova wrote:
> Julien,
>
> Yes, I use the same SQL for Nova and Ceilometer. Thanks for pointing this
> out. My bad, I didn't take it into account. So if we want to use Ceilometer
> + MySQL in production (in theory :) ) we need to use separate controllers
On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello
wrote:
> Hello,
>
> I’ve spent the past week experimenting with using Pecan for Nova’s API,
> and have opened an experimental review:
>
> https://review.openstack.org/#/c/61303/6
>
> …which implements the `versions` v3 endpoint using pecan (and paves
ata will be replicated and all
> the Galera nodes will be synced.
>
> Nadya
>
>
> On Thu, Dec 12, 2013 at 2:01 AM, Doug Hellmann <
> doug.hellm...@dreamhost.com> wrote:
>
>>
>>
>>
>> On Tue, Dec 10, 2013 at 9:47 AM, Nadya Privalova > > wrote:
On Wed, Dec 11, 2013 at 6:29 PM, Christopher Yeoh wrote:
> On Thu, Dec 12, 2013 at 7:11 AM, Ryan Petrello <
> ryan.petre...@dreamhost.com> wrote:
>
>> Hello,
>>
>> I’ve spent the past week experimenting with using Pecan for Nova’s API,
>> and have opened an experimental review:
>>
>> https://revi
On Thu, Dec 12, 2013 at 9:22 PM, Christopher Yeoh wrote:
> On Fri, Dec 13, 2013 at 4:12 AM, Jay Pipes wrote:
>
>> On 12/11/2013 11:47 PM, Mike Perez wrote:
>>
>>> On 10:06 Thu 12 Dec , Christopher Yeoh wrote:
>>>
>>>>
ed in the WSGI app’s __init__).
>
> ---
> Ryan Petrello
> Senior Developer, DreamHost
> ryan.petre...@dreamhost.com
>
> On Dec 13, 2013, at 12:56 PM, Doug Hellmann
> wrote:
>
> >
> >
> >
> > On Thu, Dec 12, 2013 at 9:22 PM, Christopher Yeoh
&g
On Sat, Dec 14, 2013 at 7:55 AM, Christopher Yeoh wrote:
>
> On Sat, Dec 14, 2013 at 8:48 AM, Doug Hellmann <
> doug.hellm...@dreamhost.com> wrote:
>
>> That covers routes. What about the properties of the inputs and outputs?
>>
>>
> I think the best way
On Mon, Dec 16, 2013 at 9:49 AM, Thierry Carrez wrote:
> Flavio Percoco wrote:
> > What I'm arguing here is:
> >
> > 1. Programs that are not part of OpenStack's release cycle shouldn't
> > be considered official nor they should have the rights that integrated
> > projects have.
> >
> > 2. I think
It might be good, to start out, if we all look at them. That way we can all
learn a bit about tempest, too. If you add "ceilometer-core" as a reviewer
gerrit will expand the group name.
Doug
On Mon, Dec 16, 2013 at 5:33 PM, David Kranz wrote:
> Ceilometer team, we are reviewing tempest tests a
On Wed, Dec 18, 2013 at 6:04 AM, Sylvain Bauza wrote:
> Le 18/12/2013 11:40, Thierry Carrez a écrit :
>
> I guess there are 3 options:
>>
>> 1. Require diversity for incubation, but find ways to bless or recommend
>> projects pre-incubation so that this diversity can actually be achieved
>>
>> 2.
On Wed, Dec 18, 2013 at 6:18 AM, Daniel P. Berrange wrote:
> On Wed, Dec 18, 2013 at 11:40:21AM +0100, Thierry Carrez wrote:
> > Hi everyone,
> >
> > The TC meeting yesterday uncovered an interesting question which, so
> > far, divided TC members.
> >
> > We require that projects have a number of
On Wed, Dec 18, 2013 at 8:06 AM, Jarret Raim wrote:
>
>
> > -Original Message-
> > From: Sylvain Bauza [mailto:sylvain.ba...@bull.net]
> > Sent: Wednesday, December 18, 2013 5:04 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] Divers
On Wed, Dec 18, 2013 at 10:58 AM, Sean Dague wrote:
> On 12/18/2013 10:37 AM, Steven Dake wrote:
> > On 12/18/2013 03:40 AM, Thierry Carrez wrote:
> >> Hi everyone,
> >>
> >> The TC meeting yesterday uncovered an interesting question which, so
> >> far, divided TC members.
> >>
> >> We require th
On Wed, Dec 18, 2013 at 10:20 AM, Jarret Raim wrote:
> > It is a difficult thing to measure, and I don't think the intent is to
> set
> a hard %
> > for contributions. I think the numbers for Barbican were just
> illustrating
> the
> > fact that the concrete contributions are very coming very heav
On Fri, Dec 20, 2013 at 1:54 AM, Clint Byrum wrote:
> Excerpts from Sean Dague's message of 2013-12-19 16:33:12 -0800:
> > So a few people had been reporting recently that unstack no longer stops
> > nova processes, which I only got around to looking at today. It turns
> > out the new common.serv
On Thu, Dec 19, 2013 at 6:31 PM, Herndon, John Luke wrote:
> Hi Folks,
>
> The Rackspace-HP team has been putting a lot of effort into performance
> testing event collection in the ceilometer storage drivers[0]. Based on
> some results of this testing, we would like to support batch consumption
>
On Fri, Dec 20, 2013 at 10:42 AM, Flavio Percoco wrote:
> Greetings,
>
> In the last Glance meeting, it was proposed to pull out glance's
> stores[0] code into its own package. There are a couple of other
> scenarios where using this code is necessary and it could also be
> useful for other consu
On Fri, Dec 20, 2013 at 11:22 AM, Sean Dague wrote:
> On 12/20/2013 10:56 AM, Sean Dague wrote:
> > On 12/20/2013 09:59 AM, Sean Dague wrote:
> >
> >> So as Clint said, SIGHUP is only appropriate to do that *if* the process
> >> is daemonized. If it's in the foreground it's not.
> >>
> >> So tha
On Fri, Dec 20, 2013 at 12:15 PM, Herndon, John Luke wrote:
>
> On Dec 20, 2013, at 8:10 AM, Doug Hellmann
> wrote:
>
>
>
>
> On Thu, Dec 19, 2013 at 6:31 PM, Herndon, John Luke
> wrote:
>
>> Hi Folks,
>>
>> The Rackspace-HP team has been put
The cliff library source repository is now hosted on stackforge (
https://git.openstack.org/cgit/stackforge/cliff/) and the bug tracker has
moved to launchpad (https://launchpad.net/python-cliff).
Doug
___
OpenStack-dev mailing list
OpenStack-dev@lists.o
On Mon, Dec 30, 2013 at 5:23 AM, Flavio Percoco wrote:
> On 26/12/13 20:05 +0200, Sergey Skripnick wrote:
>
>>
>> Hi all,
>>
>> I'm surprised there is no common ssh library in oslo so I filed this
>> blueprint[0]. I would be happy to address any comments/suggestions.
>>
>>
>> [0] https://blueprin
On Fri, Jan 3, 2014 at 12:45 PM, Joshua Harlow wrote:
> Ok, I think I'm fine with that (although not really sure what that
> entails).
>
> What does the living under the 'oslo program' change?
>
> Does that entail getting sucked into the incubator (which seems to be what
> your graduating link is
On Fri, Jan 3, 2014 at 3:13 PM, Sean Dague wrote:
> On 01/03/2014 02:44 PM, Doug Hellmann wrote:
>
>>
>>
>>
>> On Fri, Jan 3, 2014 at 12:45 PM, Joshua Harlow > <mailto:harlo...@yahoo-inc.com>> wrote:
>>
>> Ok, I think I'm fine w
On Fri, Jan 3, 2014 at 4:08 PM, Sean Dague wrote:
> On 01/03/2014 03:30 PM, Doug Hellmann wrote:
>
>>
>>
>>
>> On Fri, Jan 3, 2014 at 3:13 PM, Sean Dague > <mailto:s...@dague.net>> wrote:
>>
>> On 01/03/2014 02:44 PM, Doug Hellmann wrot
On Sat, Jan 4, 2014 at 8:02 AM, Sean Dague wrote:
> On 01/03/2014 08:27 PM, Robert Collins wrote:
>
>> On 4 January 2014 08:44, Doug Hellmann
>> wrote:
>>
>>> It seems safer to gate changes to libraries against the apps' trunk (to
>>> avoid making
On Sun, Jan 5, 2014 at 5:02 PM, James E. Blair wrote:
> Joshua Harlow writes:
>
> > It seems simple to have variations of venvs (or something similar)
> > that taskflow tox.ini can have that specify the different 0.7, 0.8,
> > 0.9, when sqlalchemy 1.0 comes out then this should become a nonissue
On Mon, Dec 30, 2013 at 2:53 PM, David Kranz wrote:
> On 12/27/2013 05:27 AM, Nadya Privalova wrote:
>
> Hello guys!
>
> I hope all of you are enjoying the holidays! But I'd like to raise a
> Tempest question. Again. I hope this email will not be lost after vacations
> :)
> After the sum
On Tue, Dec 31, 2013 at 4:53 AM, Kodam, Vijayakumar (EXT-Tata Consultancy
Ser - FI/Espoo) wrote:
> Hi,
>
> Currently there is no way to enable or disable meters without restarting
> ceilometer.
>
> There are cases where operators do not want to run all the meters
> continuously.
> In these cases
On Mon, Jan 6, 2014 at 2:56 PM, Georgy Okrokvertskhov <
gokrokvertsk...@mirantis.com> wrote:
> Hi,
>
> In Solum project we will need to implement security and ACL for Solum API.
> Currently we use Pecan framework for API. Pecan has its own security model
> based on SecureController class. At the s
101 - 200 of 3431 matches
Mail list logo
