On Fri, 2016-01-08 at 14:11 +, Daniel P. Berrange wrote:
> On Thu, Jan 07, 2016 at 09:07:00PM +0000, Mark McLoughlin wrote:
> > On Thu, 2016-01-07 at 12:23 +0100, Sahid Orentino Ferdjaoui wrote:
> > > On Mon, Jan 04, 2016 at 09:12:06PM +0000, Mark McLoughlin
On Thu, 2016-01-07 at 12:23 +0100, Sahid Orentino Ferdjaoui wrote:
> On Mon, Jan 04, 2016 at 09:12:06PM +0000, Mark McLoughlin wrote:
> > Hi
> >
> > commit 8ecf93e[1] got me thinking - the live_migration_flag config
> > option unnecessarily allows operators choos
Hi
commit 8ecf93e[1] got me thinking - the live_migration_flag config
option unnecessarily allows operators choose arbitrary behavior of the
migrateToURI() libvirt call, to the extent that we allow the operator
to configure a behavior that can result in data loss[1].
I see that danpb recently sai
Hi Emilien,
On Fri, 2015-04-17 at 10:52 -0400, Emilien Macchi wrote:
>
> On 04/16/2015 02:32 PM, Emilien Macchi wrote:
> >
> >
> > On 04/16/2015 02:23 PM, Richard Raseley wrote:
> >> Emilien Macchi wrote:
> >>> Hi all,
> >>>
> >>> I sent a patch to openstack/governance to move our project under
Hi Doug,
On Mon, 2014-12-08 at 15:58 -0500, Doug Hellmann wrote:
> As we’ve discussed a few times, we want to isolate applications from
> the configuration options defined by libraries. One way we have of
> doing that is the ConfigFilter class in oslo.config. When a regular
> ConfigOpts instance i
Hey
On Thu, 2014-09-18 at 11:53 -0700, 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
Lots of great stuff here, but too much
On Wed, 2014-09-10 at 12:46 -0700, Monty Taylor wrote:
> On 09/09/2014 07:04 PM, Samuel Merritt wrote:
> > On 9/9/14, 4:47 PM, Devananda van der Veen wrote:
> >> The questions now before us are:
> >> - should OpenStack include, in the integrated release, a
> >> messaging-as-a-service component?
>
On Wed, 2014-09-10 at 14:51 +0200, Thierry Carrez wrote:
> Flavio Percoco wrote:
> > [...]
> > Based on the feedback from the meeting[3], the current main concern is:
> >
> > - Do we need a messaging service with a feature-set akin to SQS+SNS?
> > [...]
>
> I think we do need, as Samuel puts it,
Hey
The libvirt version_cap debacle continues to come up in conversation and
one perception of the whole thing appears to be:
A controversial patch was "ninjaed" by three Red Hat nova-cores and
then the same individuals piled on with -2s when a revert was proposed
to allow further discuss
On Thu, 2014-08-28 at 13:24 +0200, Flavio Percoco wrote:
> On 08/27/2014 03:35 PM, Ken Giusti wrote:
> > Hi All,
> >
> > I believe Juno-3 is our last chance to get this feature [1] included
> > into olso.messaging.
> >
> > I honestly believe this patch is about as low risk as possible for a
> > c
On Tue, 2014-08-26 at 10:00 -0400, Doug Hellmann wrote:
> On Aug 26, 2014, at 6:30 AM, Mark McLoughlin wrote:
>
> > On Mon, 2014-08-11 at 15:06 -0400, Doug Hellmann wrote:
> >> On Aug 8, 2014, at 7:22 PM, Devananda van der Veen
> >> wrote:
> >>
>
On Mon, 2014-08-11 at 15:06 -0400, Doug Hellmann wrote:
> On Aug 8, 2014, at 7:22 PM, Devananda van der Veen
> wrote:
>
> > On Fri, Aug 8, 2014 at 12:41 PM, Doug Hellmann
> > wrote:
> >>
> >> That’s right. The preferred approach is to put the register_opt() in
> >> *runtime* code somewhere be
On Fri, 2014-08-22 at 11:59 +0200, Thierry Carrez wrote:
> TL;DR:
> Let's create an Oslo projectgroup in Launchpad to track work across all
> Oslo libraries. In library projects, let's use milestones connected to
> published versions rather than the common milestones.
Sounds good to me, Thierry. T
appreciate learning better ways to do things. I've
> > definitely become a much better python developer as a result of the
> > detailed scrutiny and feedback provided via code reviews.
> >
> > So while I agree with the general message you seem to be proposing (e.g
>
On Fri, 2014-08-22 at 11:01 -0400, Zane Bitter wrote:
> I don't see that as something the wider OpenStack community needs to
> dictate. We have a heavyweight election process for PTLs once every
> cycle because that used to be the process for electing the TC. Now that
> it no longer serves this
On Mon, 2014-08-18 at 14:23 +0200, Thierry Carrez wrote:
> Clint Byrum wrote:
> > Here's why folk are questioning Ceilometer:
> >
> > Nova is a set of tools to abstract virtualization implementations.
> > Neutron is a set of tools to abstract SDN/NFV implementations.
> > Cinder is a set of tools t
On Tue, 2014-08-12 at 15:56 +0100, Mark McLoughlin wrote:
> Hey
>
> (Terrible name for a policy, I know)
>
> From the version_cap saga here:
>
> https://review.openstack.org/110754
>
> I think we need a better understanding of how to approach situations
> like t
On Tue, 2014-08-12 at 15:56 +0100, Mark McLoughlin wrote:
> Hey
>
> (Terrible name for a policy, I know)
>
> From the version_cap saga here:
>
> https://review.openstack.org/110754
>
> I think we need a better understanding of how to approach situations
> like t
On Wed, 2014-08-13 at 12:05 -0700, James E. Blair wrote:
> cor...@inaugust.com (James E. Blair) writes:
>
> > Sean Dague writes:
> >
> >> This has all gone far enough that someone actually wrote a Grease Monkey
> >> script to purge all the 3rd Party CI content out of Jenkins UI. People
> >> are w
On Tue, 2014-07-29 at 14:04 +0200, Thierry Carrez wrote:
> Ihar Hrachyshka a écrit :
> > On 29/07/14 12:15, Daniel P. Berrange wrote:
> >> Looking at the current review backlog I think that we have to
> >> seriously question whether our stable branch review process in
> >> Nova is working to an acc
On Wed, 2014-08-13 at 10:26 +0100, Daniel P. Berrange wrote:
> On Tue, Aug 12, 2014 at 10:09:52PM +0100, Mark McLoughlin wrote:
> > On Wed, 2014-07-30 at 15:34 -0700, Clark Boylan wrote:
> > > On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote:
> > > > On 20
On Tue, 2014-08-12 at 14:12 -0700, Joe Gordon wrote:
> Here is the full nova proposal on "Blueprint in Kilo: Runways and
> Project Priorities"
>
> https://review.openstack.org/#/c/112733/
> http://docs-draft.openstack.org/33/112733/4/check/gate-nova-docs/5f38603/doc/build/html/devref/runways.h
On Tue, 2014-08-12 at 14:26 -0400, Eoghan Glynn wrote:
> > It seems like this is exactly what the slots give us, though. The core
> review
> > team picks a number of slots indicating how much work they think they can
> > actually do (less than the available number of blueprints), and then
> > blu
On Fri, 2014-08-08 at 15:36 -0700, Devananda van der Veen wrote:
> On Tue, Aug 5, 2014 at 10:02 AM, Monty Taylor wrote:
> > Yes.
> >
> > Additionally, and I think we've been getting better at this in the 2 cycles
> > that we've had an all-elected TC, I think we need to learn how to say no on
> >
On Thu, 2014-08-07 at 09:30 -0400, Sean Dague wrote:
> While I definitely think re-balancing our quality responsibilities back
> into the projects will provide an overall better release, I think it's
> going to take a long time before it lightens our load to the point where
> we get more breathing
On Tue, 2014-08-05 at 18:03 +0200, Thierry Carrez wrote:
> Hi everyone,
>
> With the incredible growth of OpenStack, our development community is
> facing complex challenges. How we handle those might determine the
> ultimate success or failure of OpenStack.
>
> With this cycle we hit new limits
On Wed, 2014-07-30 at 14:02 -0700, Michael Still wrote:
> Greetings,
>
> I would like to nominate Jay Pipes for the nova-core team.
>
> Jay has been involved with nova for a long time now. He's previously
> been a nova core, as well as a glance core (and PTL). He's been around
> so long that the
On Wed, 2014-07-30 at 15:34 -0700, Clark Boylan wrote:
> On Wed, Jul 30, 2014, at 03:23 PM, Jeremy Stanley wrote:
> > On 2014-07-30 13:21:10 -0700 (-0700), Joe Gordon wrote:
> > > While forcing people to move to a newer version of libvirt is
> > > doable on most environments, do we want to do that
Hey
(Terrible name for a policy, I know)
>From the version_cap saga here:
https://review.openstack.org/110754
I think we need a better understanding of how to approach situations
like this.
Here's my attempt at documenting what I think we're expecting the
procedure to be:
https://etherpad
On Mon, 2014-08-11 at 15:25 -0700, Joe Gordon wrote:
>
>
>
> On Sun, Aug 10, 2014 at 11:59 PM, Mark McLoughlin
> wrote:
> On Fri, 2014-08-08 at 09:06 -0400, Russell Bryant wrote:
> > On 08/07/2014 08:06 PM, Michael Still wrote:
> > > It
On Fri, 2014-08-08 at 09:06 -0400, Russell Bryant wrote:
> On 08/07/2014 08:06 PM, Michael Still wrote:
> > It seems to me that the tension here is that there are groups who
> > would really like to use features in newer libvirts that we don't CI
> > on in the gate. Is it naive to think that a poss
On Thu, 2014-07-17 at 09:58 +0100, Daniel P. Berrange wrote:
> On Thu, Jul 17, 2014 at 08:46:12AM +1000, Michael Still wrote:
> > Top posting to the original email because I want this to stand out...
> >
> > I've added this to the agenda for the nova mid cycle meetup, I think
> > most of the contr
On Wed, 2014-07-16 at 16:15 +0200, Sean Dague wrote:
..
> Based on these experiences, libvirt version differences seem to be as
> substantial as major hypervisor differences. There is a proposal here -
> https://review.openstack.org/#/c/103923/ to hold newer versions of
> libvirt to the same standa
On Tue, 2014-07-15 at 13:00 +0100, Henry Nash wrote:
> Mark,
>
>
> Thanks for your comments (as well as remarks on the WIP code-review).
>
>
> So clearly gathering and analysing log files is an alternative
> approach, perhaps not as immediate as an API call. In general, I
> believe that the mo
On Tue, 2014-07-15 at 08:54 +0100, Henry Nash wrote:
> HI
>
> As the number of configuration options increases and OpenStack
> installations become more complex, the chances of incorrect
> configuration increases. There is no better way of enabling cloud
> providers to be able to check the configu
On Thu, 2014-07-10 at 16:21 -0400, Eoghan Glynn wrote:
> > > One of the issues that has been raised in the recent discussions with
> > > the QA team about branchless Tempest relates to some legacy defects
> > > in the OpenStack notification system.
> >
> > Got links to specifics? I thought the con
On Fri, 2014-07-11 at 10:04 +0100, Chris Dent wrote:
> On Fri, 11 Jul 2014, Lucas Alvares Gomes wrote:
>
> > The data format that Ironic will send was part of the spec proposed
> > and could have been reviewed. I think there's still time to change it
> > tho, if you have a better format talk to Ha
The Oslo team is pleased to announce the release of oslo.config
1.4.0.0a2, another pre-release in the 1.4.0 series for oslo.config
during the Juno cycle:
https://pypi.python.org/pypi/oslo.config/1.4.0.0a2
oslo.config provides an API which supports parsing command line
arguments and .ini style c
On Thu, 2014-07-10 at 04:48 -0400, Eoghan Glynn wrote:
> TL;DR: do we need to stabilize notifications behind a versioned
>and discoverable contract?
>
> Folks,
>
> One of the issues that has been raised in the recent discussions with
> the QA team about branchless Tempest relates to some
PG Key … 4525ECC253E31A83
> Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
>
>
>
>
>
> On Jul 8, 2014, at 4:58 PM, Mark McLoughlin wrote:
>
> > The Oslo team is pleased to announce the release of oslo.messaging
> > 1.4.0.0a3, another pre-rel
On Mon, 2014-07-07 at 12:48 +0200, Nikola Đipanov wrote:
> When I read all of this stuff and got my head around it (took some time
> :) ), a glaring drawback of such an approach, and as I mentioned on the
> spec proposing it [1] is that we would not really doing asyncio, we
> would just be pretend
On Thu, 2014-07-03 at 16:27 +0100, Mark McLoughlin wrote:
> Hey
>
> This is an attempt to summarize a really useful discussion that Victor,
> Flavio and I have been having today. At the bottom are some background
> links - basically what I have open in my browser right now thinkin
The Oslo team is pleased to announce the release of oslo.messaging
1.4.0.0a3, another pre-release in the 1.4.0 series for oslo.messaging
during the Juno cycle:
https://pypi.python.org/pypi/oslo.messaging/1.4.0.0a3
oslo.messaging provides an API which supports RPC and notifications over
a number
On Tue, 2014-07-08 at 06:26 -0400, Sean Dague wrote:
> On 07/08/2014 04:33 AM, Mark McLoughlin wrote:
> > On Mon, 2014-07-07 at 16:46 -0400, Sean Dague wrote:
> >> This thread was unfortunately hidden under a project specific tag (I
> >> have thus stripped all the tags)
On Mon, 2014-07-07 at 16:46 -0400, Sean Dague wrote:
> This thread was unfortunately hidden under a project specific tag (I
> have thus stripped all the tags).
>
> The crux of the argument here is the following:
>
> Is a stackforge project project able to propose additions to
> global-requirement
On Mon, 2014-07-07 at 18:11 +, Angus Salkeld wrote:
> On 03/07/14 05:30, Mark McLoughlin wrote:
> > Hey
> >
> > This is an attempt to summarize a really useful discussion that Victor,
> > Flavio and I have been having today. At the bottom are some background
> &
On Mon, 2014-07-07 at 15:53 +0100, Gordon Sim wrote:
> On 07/07/2014 03:12 PM, Victor Stinner wrote:
> > The first step is to patch endpoints to add @trollius.coroutine to the
> > methods,
> > and add yield From(...) on asynchronous tasks.
>
> What are the 'endpoints' here? Are these internal to
On Sun, 2014-07-06 at 09:28 -0400, Eoghan Glynn wrote:
>
> > This is an attempt to summarize a really useful discussion that Victor,
> > Flavio and I have been having today. At the bottom are some background
> > links - basically what I have open in my browser right now thinking
> > through all of
On Fri, 2014-07-04 at 15:31 +0200, Ihar Hrachyshka wrote:
> Hi all,
> at the moment we have several bot jobs that sync contents to affected
> projects:
>
> - translations are copied from transifex;
> - requirements are copied from global requirements repo.
>
> We have another source of common cod
Hey
This is an attempt to summarize a really useful discussion that Victor,
Flavio and I have been having today. At the bottom are some background
links - basically what I have open in my browser right now thinking
through all of this.
We're attempting to take baby-steps towards moving completely
On Mon, 2014-06-30 at 15:35 -0600, John Griffith wrote:
>
>
>
>
> On Mon, Jun 30, 2014 at 3:17 PM, Mark McLoughlin
> wrote:
> On Mon, 2014-06-30 at 12:04 -0600, John Griffith wrote:
> > Hey Everyone,
> >
> >
>
On Mon, 2014-06-30 at 16:52 +, Paul Michali (pcm) wrote:
> I have out for review 103536 to add this version to global
> requirements, so that Neutron has an oslo fix (review 102909) for
> encoding failure, which affects some gate runs. This review for global
> requirements is failing requiremen
On Fri, 2014-06-27 at 17:02 +0100, Gordon Sim wrote:
> A question about the new 'retry' option. The doc says:
>
> By default, cast() and call() will block until the
> message is successfully sent.
>
> What does 'successfully sent' mean here?
Unclear, ambiguous, probably driver dependen
On Fri, 2014-06-27 at 13:28 +, Paul Michali (pcm) wrote:
> Mark,
>
> When would we be able to get a release of Oslo with 102909 fix in?
> It’s preventing Jenkins passing for some commits in Neutron.
I've just pushed 1.4.0.0a2 with the following changes:
244a902 Fix the notifier example
a7f
The Oslo team is pleased to announce the release of oslo.messaging
1.4.0.0a1, the first pre-release in the 1.4.0 series for oslo.messaging
during the Juno cycle:
https://pypi.python.org/pypi/oslo.messaging/1.4.0.0a1
oslo.messaging provides an API which supports RPC and notifications over
a numb
On Tue, 2014-06-24 at 13:56 -0700, Clint Byrum wrote:
> Excerpts from Mark McLoughlin's message of 2014-06-24 12:49:52 -0700:
> > On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote:
> > > Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700:
> > > > On 06/22/2014 02:49 PM, Duncan Tho
On Tue, 2014-06-24 at 09:51 -0700, Clint Byrum wrote:
> Excerpts from Monty Taylor's message of 2014-06-24 06:48:06 -0700:
> > On 06/22/2014 02:49 PM, Duncan Thomas wrote:
> > > On 22 June 2014 14:41, Amrith Kumar wrote:
> > >> In addition to making changes to the hacking rules, why don't we manda
On Mon, 2014-06-23 at 19:55 -0700, Joe Gordon wrote:
> * Add a new directory, contrib, for local rules that multiple
> projects use but are not generally considered acceptable to be
> enabled by default. This way we can reduce the amount of cut
> and pasted code (than
On Sat, 2014-06-21 at 07:36 -0700, Clint Byrum wrote:
> Excerpts from Sean Dague's message of 2014-06-21 05:08:01 -0700:
> > Pedantic reviewers that are reviewing for this kind of thing only should
> > be scorned. I realistically like the idea markmc came up with -
> > https://twitter.com/markmc_/
Hi
I'm not sure we've ever discussed this before, but I had previously
figured that we shouldn't translate log and exception messages in
oslo.messaging.
My thinking is:
- it seems like an odd thing for a library to do, I don't know of
examples of other libraries doing this .. but I haven'
On Thu, 2014-06-19 at 20:36 -0700, Dustin Lundquist wrote:
> Dolph,
>
>
> I appreciate the suggestion. In the mean time how does the review
> process work without core developers to approve gerrit submissions?
If you're just getting started, have a small number (possibly just 1 to
begin with) of
On Thu, 2014-06-19 at 14:29 +0200, Mehdi Abaakouk wrote:
> Hi,
>
> Le 2014-06-19 00:30, Ben Nemec a écrit :
> > On 06/18/2014 05:45 AM, Elena Ezhova wrote:
> >
> >> So I wonder whether it is something the community is interested in
> >> and, if
> >> yes, are there any recommendations concerning
On Thu, 2014-06-19 at 09:34 +0100, Matthew Booth wrote:
> On 19/06/14 08:32, Mark McLoughlin wrote:
> > Hi Armando,
> >
> > On Tue, 2014-06-17 at 14:51 +0200, Armando M. wrote:
> >> I wonder what the turnaround of trivial patches actually is, I bet you
> >&
Hey
I had been thinking of going to the Paris sprint:
https://wiki.openstack.org/wiki/Sprints/ParisJuno2014
But it only just occurred to me that we could have enough Oslo
contributors in Europe to make it worthwhile for us to use the
opportunity to get some Oslo stuff done together.
For examp
Hi Armando,
On Tue, 2014-06-17 at 14:51 +0200, Armando M. wrote:
> I wonder what the turnaround of trivial patches actually is, I bet you
> it's very very small, and as Daniel said, the human burden is rather
> minimal (I would be more concerned about slowing them down in the
> gate, but I digress
On Wed, 2014-06-18 at 09:29 -0400, Doug Hellmann wrote:
> On Wed, Jun 18, 2014 at 1:58 AM, Mark McLoughlin wrote:
> > Hey
> >
> > On Tue, 2014-06-17 at 17:43 +0200, Julien Danjou wrote:
> >> On Tue, Jun 17 2014, Arnaud Legendre wrote:
> >> > @Julien: I w
Hey
On Tue, 2014-06-17 at 17:43 +0200, Julien Danjou wrote:
> On Tue, Jun 17 2014, Arnaud Legendre wrote:
>
> > @ZhiYan: I don't like the idea of removing the sample configuration file(s)
> > from the git repository. Many people do not want to have to checkout the
> > entire codebase and tox ever
Hi Ihar,
On Mon, 2014-06-16 at 15:28 +0200, Ihar Hrachyshka wrote:
> Hi all,
>
> I'm currently pushing Neutron to oslo.messaging, and while at it, a
> question popped up.
>
> So in oslo-rpc, we have the following notification drivers available:
> neutron.openstack.common.notifier.log_notifier
>
On Sat, 2014-06-14 at 08:40 +1000, Michael Still wrote:
> Greetings,
>
> I would like to nominate Ken'ichi Ohmichi for the nova-core team.
>
> Ken'ichi has been involved with nova for a long time now. His reviews
> on API changes are excellent, and he's been part of the team that has
> driven th
On Mon, 2014-06-16 at 10:56 +0100, Daniel P. Berrange wrote:
> On Mon, Jun 16, 2014 at 05:04:51AM -0400, Eoghan Glynn wrote:
> > How about we rely instead on the values and attributes that
> > actually make our community strong?
> >
> > Specifically: maturity, honesty, and a self-correcting nature
On Fri, 2014-06-13 at 07:31 -0400, Sean Dague wrote:
> On 06/13/2014 02:36 AM, Mark McLoughlin wrote:
> > On Thu, 2014-06-12 at 22:10 -0400, Dan Prince wrote:
> >> On Thu, 2014-06-12 at 08:06 -0400, Sean Dague wrote:
> >>> We're definitely deep into capacity
On Thu, 2014-06-12 at 22:10 -0400, Dan Prince wrote:
> On Thu, 2014-06-12 at 08:06 -0400, Sean Dague wrote:
> > We're definitely deep into capacity issues, so it's going to be time to
> > start making tougher decisions about things we decide aren't different
> > enough to bother testing on every co
On Thu, 2014-06-12 at 12:13 -0600, Chris Friesen wrote:
> Hi,
>
> I'm looking for the community viewpoint on whether there is any chance
> of license contamination between mysql and nova. I realize that lawyers
> would need to be involved for a proper ruling, but I'm curious about the
> view o
On Thu, 2014-06-12 at 12:09 +0200, Thierry Carrez wrote:
> Doug Hellmann wrote:
> > On Tue, Jun 10, 2014 at 5:19 PM, Mark McLoughlin wrote:
> >> On Tue, 2014-06-10 at 12:24 -0400, Doug Hellmann wrote:
> >> [...]
> >>> Background:
> >>>
> &
On Wed, 2014-06-11 at 16:57 +1200, Steve Baker wrote:
> On 11/06/14 15:07, Jamie Lennox wrote:
> > Among the problems cause by the inconsistencies in the clients is that
> > all the options that are required to create a client need to go into the
> > config file of the service. This is a pain to co
Hi,
On Tue, 2014-06-10 at 15:47 +0400, Dina Belova wrote:
> Dims,
>
>
> No problem with creating the specs, we just want to understand if the
> community is OK with our suggestions in general :)
> If so, I'll create the appropriate specs and we'll discuss them :)
Personally, I find it difficult
On Tue, 2014-06-10 at 12:24 -0400, Doug Hellmann wrote:
> As part of the push to release code from the oslo incubator in
> stand-alone libraries, we have had several different discussions about
> versioning and release schedules. This is an attempt to collect all of
> the decisions we have made in
On Tue, 2014-06-10 at 21:59 +0100, Mark McLoughlin wrote:
> On Tue, 2014-06-10 at 17:33 +, Janczuk, Tomasz wrote:
> > From my perspective the key promise of Marconi is to provide a
> > *multi-tenant*, *HTTP* based queuing system. Think an OpenStack equivalent
> > of SQS or
On Tue, 2014-06-10 at 17:33 +, Janczuk, Tomasz wrote:
> From my perspective the key promise of Marconi is to provide a
> *multi-tenant*, *HTTP* based queuing system. Think an OpenStack equivalent
> of SQS or Azure Storage Queues.
>
> As far as I know there are no off-the-shelve message brokers
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
> On 10 June 2014 15:07, Mark McLoughlin wrote:
>
> > Exposing which configurations are actively "tested" is a perfectly sane
> > thing to do. I don't see why you think calling this "certification&q
On Tue, 2014-06-10 at 14:06 +0100, Duncan Thomas wrote:
> On 10 June 2014 09:33, Mark McLoughlin wrote:
>
> > Avoiding dragging the project into those sort of politics is something
> > I'm really keen on, and why I think the word "certification" is best
> >
On Mon, 2014-06-09 at 19:31 +, Kurt Griffiths wrote:
> Lately we have been talking about writing drivers for traditional
> message brokers that will not be able to support the message feeds
> part of the API. I’ve started to think that having a huge part of the
> API that may or may not “work”,
On Mon, 2014-06-09 at 20:14 -0400, Doug Hellmann wrote:
> On Mon, Jun 9, 2014 at 6:11 PM, Eoghan Glynn wrote:
> >
> >
> >> Based on the discussion I'd like to propose these options:
> >> 1. Cinder-certified driver - This is an attempt to move the "certification"
> >> to the project level.
> >> 2.
Hi John,
On Fri, 2014-06-06 at 13:59 -0600, John Griffith wrote:
> On Fri, Jun 6, 2014 at 1:55 PM, John Griffith
> wrote:
> On Fri, Jun 6, 2014 at 1:23 PM, Mark McLoughlin
> wrote:
> On Fri, 2014-06-06 at 13:29 -0400, Anita Kuno wrote:
>
On Fri, 2014-06-06 at 13:29 -0400, Anita Kuno wrote:
> The issue I have with the word certify is that it requires someone or a
> group of someones to attest to something. The thing attested to is only
> as credible as the someone or the group of someones doing the attesting.
> We have no process, n
Mehdi has been making great contributions and reviews on oslo.messaging
for months now, so I've added him to oslo.messaging-core.
Thank you for all your hard work Mehdi!
Mark.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lis
On Wed, 2014-06-04 at 18:03 -0700, Mark Washenberger wrote:
> Hi folks,
>
>
> I'd like to propose the Images program to adopt a mission statement
> [1] and then change it to reflect our new aspirations of acting as a
> Catalog that works with artifacts beyond just disk images [2].
>
>
> Since
On Fri, 2014-05-30 at 18:22 +, Hemanth Makkapati wrote:
> Hello All,
> I'm writing to notify you of the approach the Glance community has
> decided to take for doing functional API. Also, I'm writing to
> solicit your feedback on this approach in the light of cross-project
> API consistency.
>
On Thu, 2014-06-05 at 11:19 +0200, Radomir Dopieralski wrote:
> On 06/05/2014 10:59 AM, Mark McLoughlin wrote:
>
> >> If I'm late to the party and the only one that this is news to, that is
> >> fine. Sixteen additional repos seems like a lot of additiona
On Thu, 2014-05-29 at 15:29 -0400, Anita Kuno wrote:
> On 05/28/2014 08:54 AM, Radomir Dopieralski wrote:
> > Hello,
> >
> > we plan to finally do the split in this cycle, and I started some
> > preparations for that. I also started to prepare a detailed plan for the
> > whole operation, as it see
On Wed, 2014-02-19 at 10:27 -0600, Kevin L. Mitchell wrote:
> On Wed, 2014-02-19 at 13:47 +0100, Mehdi Abaakouk wrote:
> > But 'quota_class' is never set when a nova RequestContext is created.
>
> When I created quota classes, I envisioned the authentication component
> of the WSGI stack setting t
On Fri, 2014-05-09 at 08:20 -0400, Sean Dague wrote:
> Based on some of my blog posts on gerrit queries, I've built and gotten
> integrated a custom inbox zero dashboard which is per project in gerrit.
>
> ex:
> https://review.openstack.org/#/projects/openstack/nova,dashboards/important-changes:re
On Tue, 2014-04-29 at 10:39 -0400, Doug Hellmann wrote:
> On Tue, Apr 29, 2014 at 9:48 AM, Mark McLoughlin wrote:
> > Hey
> >
> > In this patch:
> >
> > https://review.openstack.org/83681
> >
> > by Ghanshyam Mann, we encountered an unusual situat
On Tue, 2014-04-29 at 14:48 +0100, Mark McLoughlin wrote:
> My conclusions from all that:
>
> 1) This sucks
>
> 2) At the very least, we should be clear in our API samples tests
> which of the three formats we expect - we should only change the
> format us
Hey
In this patch:
https://review.openstack.org/83681
by Ghanshyam Mann, we encountered an unusual situation where a timestamp
in the returned XML looked like this:
2014-04-08 09:00:14.399708+00:00
What appeared to be unusual was that the timestamp had both sub-second
time resolution and t
On Wed, 2014-04-23 at 07:25 +0100, Mark McLoughlin wrote:
> On Tue, 2014-04-22 at 15:54 -0700, Devananda van der Veen wrote:
> > Hi!
> >
> > When a project is using oslo.messaging, how can we change our default
> > rpc_thread_pool_size?
> >
> >
On Tue, 2014-04-22 at 15:54 -0700, Devananda van der Veen wrote:
> Hi!
>
> When a project is using oslo.messaging, how can we change our default
> rpc_thread_pool_size?
>
> ---
> Background
>
> Ironic has hit a bug where a flood of API requests can deplete the RPC
> worker po
On Mon, 2014-04-21 at 12:39 -0400, Doug Hellmann wrote:
> 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
>
On Mon, 2014-04-14 at 14:53 -0400, Doug Hellmann wrote:
> Balancing Europe and Pacific TZs is going to be a challenge. I can't
> go at 1800 or 1900, myself, and those are pushing a little late in
> Europe anyway.
>
> How about 1600?
> http://www.timeanddate.com/worldclock/converted.html?iso=201404
On Thu, 2014-04-10 at 00:23 -0700, Nathan Kinder wrote:
> OpenSSL Heartbleed vulnerability can lead to OpenStack compromise
> ---
>
> ### Summary ###
> A vulnerability in OpenSSL can lead to leaking of confidential data
> protected by SSL/TLS in an OpenStack deployment.
>
> ### Affected Services
1 - 100 of 282 matches
Mail list logo
