On Nov 1, 2013 6:46 PM, John Garbutt j...@johngarbutt.com wrote:
On 29 October 2013 16:11, Eddie Sheffield eddie.sheffi...@rackspace.com
wrote:
John Garbutt j...@johngarbutt.com said:
Going back to Joe's comment:
Can both of these cases be covered by configuring the keystone
catalog?
On Nov 1, 2013 10:20 AM, John Garbutt j...@johngarbutt.com wrote:
Its intentional. Cells is there to split up your nodes into more
manageable chunks.
There are quite a few design summit sessions on looking into
alternative approaches to our current scheduler.
While I would love a single
On Wed, Oct 30, 2013 at 8:31 AM, Alex Glikson glik...@il.ibm.com wrote:
Russell Bryant rbry...@redhat.com wrote on 30/10/2013 10:20:34 AM:
On 10/30/2013 03:13 AM, Alex Glikson wrote:
Maybe a more appropriate approach could be to have a tool/script that
does it, as a one time thing.
On Oct 30, 2013 9:10 AM, Robert Collins robe...@robertcollins.net wrote:
Hi, like most OpenStack projects we need to keep the core team up to
date: folk who are not regularly reviewing will lose context over
time, and new folk who have been reviewing regularly should be trusted
with -core
On Wed, Oct 30, 2013 at 9:31 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Wed, Oct 30, 2013 at 10:08:03AM +1100, Tom Fifield wrote:
Hi all,
Recently, I did something crazy and got into the top 10 reviewers
for OpenStack in a 30/60 day window. Admittedly, this was for
+topic:noboilerplate,n,z
https://review.openstack.org/#/c/51295/
On Mon, Oct 28, 2013 at 10:54 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Mon, Oct 28, 2013 at 9:35 AM, Alexis Lee alex...@hp.com wrote:
As a new OpenStack contributor, +1 for lower barriers to entry. It's
helpful for OS
On Tue, Oct 29, 2013 at 11:17 AM, Robert Collins
robe...@robertcollins.netwrote:
On 28 October 2013 23:54, Joe Gordon joe.gord...@gmail.com wrote:
We don't just gate without telling people, the first two items in hacking
are read pep8
http://docs.openstack.org/developer/hacking
On Mon, Oct 28, 2013 at 8:41 AM, Flavio Percoco fla...@redhat.com wrote:
On 27/10/13 22:13 -0400, Monty Taylor wrote:
On 10/26/2013 04:38 AM, Robert Collins wrote:
So nova has a massive .mailmap that maps multiple addresses for one
person together. I'm wondering if a) it's still needed,
On Mon, Oct 28, 2013 at 11:10 AM, Roman Bogorodskiy
rbogorods...@mirantis.com wrote:
Hi,
I've been noticing since this morning that the check-grenade-devstack-vm
job constantly fails.
https://jenkins01.openstack.org/job/check-grenade-devstack-vm/
You can see that there were no single
This sounds like a bug in Havana, please file a bug at
https://bugs.launchpad.net/nova.
On Mon, Oct 28, 2013 at 3:29 PM, David Kang dk...@isi.edu wrote:
I've installed Havana using RDO Packstack.
When one key:value pair is described in instance_type_extra_specs,
the scheduler works fine.
On Oct 24, 2013 9:14 PM, Robert Collins robe...@robertcollins.net wrote:
On 24 October 2013 04:33, Russell Bryant rbry...@redhat.com wrote:
Greetings,
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we
On Oct 24, 2013 11:38 PM, Michael Still mi...@stillhq.com wrote:
On Fri, Oct 25, 2013 at 9:07 AM, Boris Pavlovic bo...@pavlovic.me wrote:
Johannes,
+1, purging should help here a lot.
Sure, but my point is more:
- pruning isn't done by the system automatically, so we have to
assume
On Oct 25, 2013 12:24 PM, Dan Prince dpri...@redhat.com wrote:
-1
Slight preference for keeping them. I personally would go the other way
and just add them everywhere.
May I ask why? Do you use the modeline?
- Original Message -
From: Joe Gordon joe.gord...@gmail.com
On Wed, Oct 23, 2013 at 4:33 PM, Russell Bryant rbry...@redhat.com wrote:
Greetings,
At the last Nova meeting we started talking about some updates to the
Nova blueprint process for the Icehouse cycle. I had hoped we could
talk about and finalize this in a Nova design summit session on Nova
On Thu, Oct 24, 2013 at 3:24 PM, Lars Kellogg-Stedman l...@redhat.comwrote:
On Thu, Oct 24, 2013 at 07:05:19AM -0700, Dan Smith wrote:
Some of them are not useful to me (but might be to others), like the
amqp channel lines. However, everything else has been pretty crucial at
one point or
This is being tracked in bug
https://bugs.launchpad.net/tempest/+bug/1244055and a fix is working
its way through the gate now (
https://review.openstack.org/#/c/53699/)
On Thu, Oct 24, 2013 at 2:51 PM, Gary Kotton gkot...@vmware.com wrote:
Hi,
The gate for stable Hanava is broken in Nova with
On Sun, Oct 20, 2013 at 12:18 PM, Tim Bell tim.b...@cern.ch wrote:
Is it easy ? No... it is hard, whether in an integrated test suite or on
its own
Can it be solved ? Yes, we have done incredible things with the current
QA infrastructure
Should it be split off from other testing ? No, I
On Sun, Oct 20, 2013 at 6:38 AM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2013-10-20 20:57:56 +0800 (+0800), Thomas Goirand wrote:
Well, good luck finding all the copyright holders for such a large and
old project. It's not really practical in this case, unfortunately.
To a great extent,
On Oct 20, 2013 11:29 AM, Robert Collins robe...@robertcollins.net
wrote:
On 20 October 2013 02:35, Monty Taylor mord...@inaugust.com wrote:
However, even as a strong supporter of accurate license headers, I would
like to know more about the FTP masters issue. I dialog with them, as
folks
On Sat, Oct 12, 2013 at 12:21 PM, Alessandro Pilotti
apilo...@cloudbasesolutions.com wrote:
On 12.10.2013, at 20:22, Dan Smith d...@danplanet.com wrote:
From the user perspective, splitting off the projects seems to be
focussing on the ease of commit compared to the final user
On Fri, Oct 11, 2013 at 6:02 AM, Alessandro Pilotti
apilo...@cloudbasesolutions.com wrote:
On Oct 11, 2013, at 14:15 , Sean Dague s...@dague.net
wrote:
On 10/10/2013 08:43 PM, Tim Smith wrote:
snip
Again, I don't have any vested interest in this discussion, except that
I believe the
It looks like you were unable to connect to quantum.
Thank you very much for your help.
Ravi
On Fri, Oct 11, 2013 at 5:04 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Oct 11, 2013 at 4:44 PM, Ravikanth Samprathi
rsamp...@gmail.comwrote:
Hi
I am trying to issue the boot
On Thu, Oct 10, 2013 at 4:47 AM, Vladik Romanovsky
vladik.romanov...@enovance.com wrote:
Hello everyone,
I have been recently working on a migration bug in nova (Bug #1233184).
I noticed that compute service remains available, even if a connection to
libvirt is broken.
I thought that it
On Fri, Oct 11, 2013 at 4:44 PM, Ravikanth Samprathi rsamp...@gmail.comwrote:
Hi
I am trying to issue the boot command to provision baremetal server. But
i see the following error:
Also, where can i get the bootstrap kernel and ramdisk images to boot into
the baremetal? And how to get the
It looks like you were unable to connect to quantum.
Thank you very much for your help.
Ravi
On Fri, Oct 11, 2013 at 5:04 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Oct 11, 2013 at 4:44 PM, Ravikanth Samprathi
rsamp...@gmail.comwrote:
Hi
I am trying to issue the boot
On Thu, Oct 10, 2013 at 11:20 AM, Alessandro Pilotti
apilo...@cloudbasesolutions.com wrote:
Hi all,
As the Havana release date is approaching fast, I'm sending this email
to sum up the situation for pending bugs and reviews related to the Hyper-V
integration in OpenStack.
In the past
On Thu, Oct 10, 2013 at 6:57 PM, Matt Riedemann mrie...@us.ibm.com wrote:
Getting integration testing hooked up for the hyper-v driver with tempest
should go a long way here which is a good reason to have it. As has been
mentioned, there is a core team of people that understand the internals
On Thu, Oct 10, 2013 at 5:43 PM, Tim Smith tsm...@gridcentric.com wrote:
On Thu, Oct 10, 2013 at 1:50 PM, Russell Bryant rbry...@redhat.comwrote:
Please understand that I only want to help here. Perhaps a good way for
you to get more review attention is get more karma in the dev community
On Thu, Oct 10, 2013 at 7:28 PM, Matt Riedemann mrie...@us.ibm.com wrote:
Dan Smith d...@danplanet.com wrote on 10/10/2013 08:26:14 PM:
From: Dan Smith d...@danplanet.com
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org,
Date: 10/10/2013 08:31 PM
Subject:
On Thu, Sep 26, 2013 at 7:49 AM, Sean Dague s...@dague.net wrote:
As many folks know, gerrit takes comments of either the form
recheck bug #X
or
recheck no bug
To kick off the check queue jobs again to handle flakey tests.
The problem is that we're getting a lot more no bug than bugs
On Thu, Sep 26, 2013 at 1:30 AM, Julien Danjou jul...@danjou.info wrote:
On Thu, Sep 26 2013, Joe Gordon wrote:
TL;DR: We will be automatically identifying your flaky tempest runs, so
you
just have to confirm that you hit bug x, not identify which bug you hit.
I love you guys. It's
On Thu, Sep 26, 2013 at 1:53 PM, Soren Hansen so...@linux2go.dk wrote:
Hey, sorry for necroposting. I completely missed this thread when it was
active, but Russel just pointed it out to me on Twitter earlier today and
I couldn't help myself.
2013/7/19 Sandy Walsh sandy.wa...@rackspace.com:
On Thu, Sep 26, 2013 at 3:12 PM, Michael Davies mich...@the-davies.netwrote:
On Mon, Sep 23, 2013 at 6:20 PM, Thierry Carrez thie...@openstack.org
wrote:
Monty Taylor wrote:
On 09/20/2013 02:47 PM, Michael Still wrote:
Before https://review.openstack.org/#/c/46867/ if file injection of
On Thu, Sep 26, 2013 at 6:41 PM, Joe Gordon joe.gord...@gmail.com wrote:
Hi All,
As many of you may have suspected the gate has gotten less stable in the
past few days. Turns out we have the numbers to prove it too!
http://graphite.openstack.org/graphlot/?width=586from=00
Hi All,
TL;DR: We will be automatically identifying your flaky tempest runs, so you
just have to confirm that you hit bug x, not identify which bug you hit.
http://status.openstack.org/rechecks/ is a great tool to identify which
bugs are causing our gating to be flaky allowing for better
On Fri, Sep 20, 2013 at 11:52 AM, Russell Bryant rbry...@redhat.com wrote:
On 09/20/2013 02:02 PM, Dan Wendlandt wrote:
I think the real problem here is that in Nova there are bug fixes that
are tiny and very important to a particular subset of the user
population and yet have been around
On Sep 20, 2013 1:27 PM, Dan Wendlandt d...@nicira.com wrote:
On Fri, Sep 20, 2013 at 1:09 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Fri, Sep 20, 2013 at 11:52 AM, Russell Bryant rbry...@redhat.com
wrote:
On 09/20/2013 02:02 PM, Dan Wendlandt wrote:
I think the real problem here
On Mon, Sep 9, 2013 at 10:48 AM, Martinez, Castulo
castulo.marti...@intel.com wrote:
Best Regards / Saludos!
Castulo J. Martinez
ISTQB Test Manager
QA Engineer | Q1st team @GDC
Intel | Security Engineering and Cloud Integration (SECI)
Office: +52.33.2282.4083 | iNet: 8286-4083
Before
On Fri, Sep 6, 2013 at 4:17 PM, Bryan D. Payne bdpa...@acm.org wrote:
2) There is general consensus that the simple config based key manager
(single key) does provide some amount of useful security. I believe it
does, just want to make sure we're in agreement on it. Obviously we
want to
On Tue, Sep 3, 2013 at 4:38 PM, Coffman, Joel M. joel.coff...@jhuapl.eduwrote:
We have fully implemented support for transparently encrypting Cinder
volumeshttps://blueprints.launchpad.net/nova/+spec/encrypt-cinder-volumesfrom
within Nova (see
https://review.openstack.org/#/c/30976/), but
.html*
***
[3]
http://lists.openstack.org/pipermail/openstack-dev/2013-April/008268.html*
***
** **
** **
*From:* Joe Gordon [mailto:joe.gord...@gmail.com]
*Sent:* Tuesday, September 03, 2013 4:48 PM
*To:* OpenStack Development Mailing List
*Subject:* Re: [openstack-dev] [nova] key
On Tue, Sep 3, 2013 at 6:44 PM, John Griffith
john.griff...@solidfire.comwrote:
On Tue, Sep 3, 2013 at 7:27 PM, Bryan D. Payne bdpa...@acm.org wrote:
How can someone use your code without a key manager?
Some key management mechanism is required although it could be
simplistic.
On Aug 28, 2013 9:42 AM, Shawn Hartsock hartso...@vmware.com wrote:
tl;dr at the end... I can ramble on a bit.
I agree with Daniel.
I'm not a core reviewer, but I'm trying to think like one. Over the last
few weeks I've divested myself of almost all coding tasks, instead trying
to increase
On Thu, Aug 22, 2013 at 12:29 PM, Kurt Griffiths
kurt.griffi...@rackspace.com wrote:
What was wrong with qpid, rabbitmq, activemq, zeromq, ${your favorite
queue here} that required marconi?
That's a good question. The features supported by AMQP brokers, ZMQ, and
Marconi certainly do
Day has been posting
some really good feedback on the review. I asked Joe Gordon to take a
look and provide another opinion. He agreed with Phil that we really
need to have scheduler policies be a first class API citizen.
So, that pushes this feature out to Icehouse, as it doesn't seem
://github.com/openstack/nova/blob/master/nova/scheduler/filters/ram_filter.py
doesn't
duplicate all the code, it uses a base class. The check the aggregate for
the value logic is duplicated, but that is easy to fix.
Regards,
Alex
From:Joe Gordon joe.gord...@gmail.com
On Wed, Aug 28, 2013 at 4:34 PM, Alex Glikson glik...@il.ibm.com wrote:
Joe Gordon joe.gord...@gmail.com wrote on 28/08/2013 11:04:45 PM:
Well, first, at the moment each of these filters today duplicate the
code that handles aggregate-based overrides. So, it would make sense
to have
On Tue, Aug 27, 2013 at 11:04 AM, Daniel P. Berrange berra...@redhat.comwrote:
On Tue, Aug 27, 2013 at 10:55:03AM -0400, Russell Bryant wrote:
On 08/27/2013 10:43 AM, Daniel P. Berrange wrote:
I tend to focus the bulk of my review activity on the libvirt driver,
since that's where most
On Tue, Aug 20, 2013 at 2:21 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Mark McLoughlin's message of 2013-08-20 03:26:01 -0700:
On Thu, 2013-08-15 at 14:12 +1200, Robert Collins wrote:
This may interest data-driven types here.
. Several projects including tempest have
begun doing this (https://review.openstack.org/#/c/43168/5). And because
we have 53 repos in the openstack namespace (github.com/openstack) it is
easier to send this out to hunt down 53 patches and add comments to them.
best,
Joe Gordon
On Mon, Aug 19, 2013 at 5:42 PM, Russell Bryant rbry...@redhat.com wrote:
Greetings,
Some OpenStack programs have started a nice trend of getting together in
the middle of the development cycle. These meetups can serve a number
of useful purposes: community building, ramping up new
On Aug 23, 2013 12:24 PM, Dolph Mathews dolph.math...@gmail.com wrote:
On Fri, Aug 23, 2013 at 10:51 AM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:
Hello,
I would think you would want to reuse the same token but update the
expiration time as if it were the
On Aug 18, 2013 3:58 PM, Jay Pipes jaypi...@gmail.com wrote:
On 08/18/2013 03:53 AM, Joshua Harlow wrote:
I always just liked SQL as the database abstraction layer ;)
On a more serious note I think novas new object model might be a way to
go but in all honesty there won't be a one size fits
On Sat, Aug 17, 2013 at 9:46 AM, Robert Collins
robe...@robertcollins.netwrote:
On 17 August 2013 23:49, Salvatore Orlando sorla...@nicira.com wrote:
I tend to agree that when the gate for a project is broken, nothing
should
be merged for that project until the gate jobs are green again.
On Aug 17, 2013 7:52 AM, Salvatore Orlando sorla...@nicira.com wrote:
I tend to agree that when the gate for a project is broken, nothing
should be merged for that project until the gate jobs are green again.
In the case of Neutron, making the job non voting only caused more bugs
to slip
.
best,
Joe Gordon
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Aug 13, 2013 at 6:56 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Alex Gaynor's message of 2013-08-13 14:58:56 -0700:
Hi all,
(This references this changeset: https://review.openstack.org/#/c/38415/
)
One of the goals I've been working at has been getting swift
This touches on one of my big pet peeves, in the commit message one should:
*Describe why a change is being made.*
A common mistake is to just document how the code has been written, without
describing /why/ the developer chose to do it that way. By all means
describe the overall code structure,
need to be online to have access to all information about the code
repository. The commit message should be totally self-contained, to
maintain that benefit.
https://wiki.openstack.org/wiki/GitCommitMessages#Information_in_commit_messages
From: Joe Gordon joe.gord...@gmail.com
Reply
On Thu, Aug 8, 2013 at 12:41 AM, Álvaro López García
alvaro.lopez.gar...@cern.ch wrote:
Hi John.
On Wed 07 Aug 2013 (15:56), Joe Gordon wrote:
Can you provide more detail in the BP, there isn't very much to review
it
on right now.
Thanks for your interest, I've updated it a bit [1
Can you provide more detail in the BP, there isn't very much to review it
on right now.
On Wed, Aug 7, 2013 at 12:48 AM, Álvaro López García
alvaro.lopez.gar...@cern.ch wrote:
Dear all.
I've registered a blueprint [1] to improve and extend the current
image cache handler on the compute
It looks like everyone is in agreement on this, so here is the patch:
https://review.openstack.org/#/c/40565/
On Tue, Aug 6, 2013 at 4:36 AM, Roman Bogorodskiy rbogorods...@mirantis.com
wrote:
Joe Gordon wrote:
On Mon, Aug 5, 2013 at 9:11 AM, Roman Bogorodskiy
rbogorods...@mirantis.com
On Sat, Aug 3, 2013 at 6:54 AM, Joe Gordon **joe.gord...@gmail.com**
=mailto:joe.gord...@gmail.com; wrote:
Hi All,
even though Glance, has been pulled out of Nova years ago, Nova still has
a images API that proxies back to Glance. Since Nova is in the process of
creating a new, V3, API, we
On Mon, Aug 5, 2013 at 9:11 AM, Roman Bogorodskiy rbogorods...@mirantis.com
wrote:
Joe Gordon wrote:
Hi All,
even though Glance, has been pulled out of Nova years ago, Nova still
has a
images API that proxies back to Glance. Since Nova is in the process of
creating a new, V3, API
use Glance
directly? I have vague concerns about making Glance API publicly
accessible, but I am not sure what the underlying reason is
* If it is still needed in Nova today, can we remove it in the future and
if so what is the timeline?
best,
Joe Gordon
On Fri, Aug 2, 2013 at 10:33 AM, Dan Smith d...@danplanet.com wrote:
Any solution where you need to modify sudoers every time the code
changes is painful, because there is only one sudo configuration on a
machine and it's owned by root.
Hmm? At least on ubuntu there is a default
On Tue, Jul 30, 2013 at 8:55 AM, Thierry Carrez thie...@openstack.orgwrote:
Joe Gordon wrote:
Going forward I think we should support two approaches:
1) some faster mostly python based (because we are a python project)
rootwrap solution, there are many good ideas proposed above
On Aug 1, 2013 2:06 AM, Thierry Carrez thie...@openstack.org wrote:
Joe Gordon wrote:
I tried
swapping out rootwrap for sudo and that made the issue go away.So I
think we should go back to supporting just using sudo instead of
rootwrap, and make sure any future solutions support
+1
On Wed, Jul 31, 2013 at 12:56 PM, Matt Riedemann mrie...@us.ibm.com wrote:
+1
Thanks,
*MATT RIEDEMANN*
Advisory Software Engineer
Cloud Solutions and OpenStack Development
--
*Phone:* 1-507-253-7622 | *Mobile:* 1-507-990-1889*
E-mail:*
+1
On Wed, Jul 31, 2013 at 9:41 AM, Lucas Alvares Gomes
lucasago...@gmail.comwrote:
+1
On Wed, Jul 31, 2013 at 5:29 PM, Anita Kuno ak...@lavabit.com wrote:
I agree too.
On 13-07-31 12:20 PM, Ghe Rivero wrote:
+1
On Wed, Jul 31, 2013 at 6:10 PM, Devananda van der Veen
at 7:42 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Jul 23, 2013 12:34 PM, Sergey Lukjanov slukja...@mirantis.com
wrote:
Hi evereyone,
We’ve started working on upgrading Savanna architecture in version 0.3
to
make it horizontally scalable.
The most part of information
On Mon, Jul 29, 2013 at 5:51 AM, Thierry Carrez thie...@openstack.orgwrote:
John Garbutt wrote:
I tend to agree that (option 3) aggregating all of the calls to
rootwrap may be impractical:
Sean Dague wrote:
The reason there are 20 different call outs is that they aren't all in
the
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Python overhead for rootwrap
Joe Gordon wrote:
time python -c print 'test'
Is this a fair test, because I assume we don't need to compile
rootwrap each time?
Having said that, I believe you that there is overhead in starting
On Fri, Jul 26, 2013 at 11:34 AM, Jay Pipes jaypi...@gmail.com wrote:
On 07/25/2013 04:21 PM, Joe Gordon wrote:
Hi All,
We have recently hit some performance issues with nova-network. It
turns out the root cause of this was we do roughly 20 rootwrapped shell
commands, many inside
On Jul 26, 2013 5:53 AM, Russell Bryant rbry...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2013 05:35 AM, Roman Bogorodskiy wrote:
Alex Meade wrote:
+1 to everything Russell just said and of course Blueprints for
this. One for #3 (changing from mox -
On Jul 23, 2013 12:34 PM, Sergey Lukjanov slukja...@mirantis.com wrote:
Hi evereyone,
We’ve started working on upgrading Savanna architecture in version 0.3 to
make it horizontally scalable.
The most part of information is in the wiki page -
this email out to get the discussion started.
best,
Joe Gordon
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Wed, Jul 24, 2013 at 12:24 PM, Russell Bryant rbry...@redhat.com wrote:
On 07/23/2013 06:00 PM, Clint Byrum wrote:
This is really interesting work, thanks for sharing it with us. The
discussion that has followed has brought up some thoughts I've had for
a while about this choke point in
that real-time processing is a similar model as what is
needed here.
Maybe something like that is where this should end up?
-Josh
From: Joe Gordon joe.gord...@gmail.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Date: Monday, July 22, 2013 3:47 PM
then just send directly to scheduler
information.
Best regards,
Boris Pavlovic
---
Mirantis Inc.
On Tue, Jul 23, 2013 at 11:56 PM, Joe Gordon joe.gord...@gmail.comwrote:
On Jul 23, 2013 3:44 PM, Ian Wells ijw.ubu...@cack.org.uk wrote:
* periodic updates can overwhelm things
On Mon, Jul 22, 2013 at 3:04 PM, Russell Bryant rbry...@redhat.com wrote:
On 07/22/2013 05:15 PM, Alex Glikson wrote:
Dear all,
Following the initial discussions at the last design summit, we have
published the design [2] and the first take on the implementation [3] of
the blueprint
On Jul 19, 2013 9:57 AM, Day, Phil philip@hp.com wrote:
-Original Message-
From: Dan Smith [mailto:d...@danplanet.com]
Sent: 19 July 2013 15:15
To: OpenStack Development Mailing List
Cc: Day, Phil
Subject: Re: [openstack-dev] Moving task flow to conductor - concern
about
Along these lines, OpenStack is now maintaining sqlachemy-migrate, and we
have our first patch up for better SQLite support, taken from nova,
https://review.openstack.org/#/c/37656/
Do we want to go the direction of explicitly not supporting sqllite and not
running migrations with it, like
Hi All,
I am pleased to announce we have just released version 0.6.0 of OpenStack's
Style Guide tool, hacking. In addition to bug fixes version 0.6.0
introduces several new checks:
H102: Apache 2.0 license header not found
H103: header does not match Apache 2.0 License notice
H231: Python 3.x
I am happy to help to but I don't have much extra bandwidth at the moment,
so I can only play a supporting role as a core and not a leadership role.
On Sat, Jul 13, 2013 at 2:58 PM, Michael Still mi...@stillhq.com wrote:
I'm happy to help, although I'm pretty busy...
Michael
On Fri, Jul
On Thu, Jul 11, 2013 at 9:39 AM, Mark McLoughlin mar...@redhat.com wrote:
Hi Daisy,
On Wed, 2013-07-10 at 21:48 +0800, Ying Chun Guo wrote:
Hi, Mark
I think there is a blueprint we discussed in the Havana summit to
separate translation domains.
On Thu, Jul 11, 2013 at 1:48 PM, John Griffith
john.griff...@solidfire.comwrote:
On Thu, Jul 11, 2013 at 6:29 AM, Dirk Müller d...@dmllr.de wrote:
Hi Sean,
Cinder uncapping python-keystoneclient will get us past this.
There is a review exactly proposing that:
On Mon, Jul 8, 2013 at 8:53 AM, Ilya Kharin ikha...@mirantis.com wrote:
Hi all.
In my opinion it is about things that can live in one form or another,
because
in some cases there is a need to place an instance in the same place where
its
block device is located or will be attached. Both
On Tue, Jul 9, 2013 at 1:28 PM, Kieran Spear kisp...@gmail.com wrote:
Hi all,
There's a review up to make Horizon pass H304 (no relative imports):
https://review.openstack.org/#/c/35664/
Old-style relative imports are dangerous, but I can't think of a good
enough reason to forbid
On Jul 3, 2013 5:22 PM, Ala Rezmerita ala.rezmer...@cloudwatt.com wrote:
Hi everyone,
I have a question regarding too many token generation in nova when using
quantumclient (also related to bug reports
https://bugs.launchpad.net/nova/+bug/1192383 +
On Wed, Jul 3, 2013 at 6:19 PM, Christopher Armstrong
chris.armstr...@rackspace.com wrote:
On Tue, Jul 2, 2013 at 11:38 PM, Robert Collins
robe...@robertcollins.net wrote:
Radix points out I missed the naunce that you're targeting the users
of python-novaclient, for instance, rather than
On Mon, Jul 1, 2013 at 11:08 PM, Alex Gaynor alex.gay...@gmail.com wrote:
Hi all,
I suspect many of you don't know me as I've only started to get involved in
OpenStack recently, I work at Rackspace and I'm pretty involved in other
Python
open source stuff, notably Django and PyPy, I also
+1
On Wed, Jun 26, 2013 at 10:06 AM, Sean Dague s...@dague.net wrote:
+1
On 06/26/2013 11:09 AM, Russell Bryant wrote:
Greetings,
I would like to nominate John Garbutt for the nova-core team.
John has been involved with nova for a long time now. He's primarily
known for his great
On Tue, Jun 25, 2013 at 7:22 AM, Andrew Laski andrew.la...@rackspace.comwrote:
I have a couple of reviews up to introduce the concept of shelving an
instance into Nova. The question has been raised as to whether or not this
belongs in Nova, or more rightly belongs in Heat. The blueprint for
On Mon, Jun 24, 2013 at 3:19 PM, Sean Dague s...@dague.net wrote:
On 06/24/2013 06:15 PM, Monty Taylor wrote:
On 06/24/2013 05:56 PM, Mark McLoughlin wrote:
On Mon, 2013-06-24 at 22:50 +0100, Mark McLoughlin wrote:
Hey,
Pulling this out of gerrit for discussion.
Background is one of
It sounds like the censuses in this thread is:
In the long run, we want to kill run_tests.sh in favor of explaining how to
use the underlying tools in a TESTING file.
But in the short term, we should start moving toward using a TESTING file
(such as https://review.openstack.org/#/c/33456/) but
Hi All,
A patch to move the run_tests.sh script into oslo-incubator (
https://review.openstack.org/#/c/32736/), has brought up the bigger
question of what is the future of './run_tests.sh.'
This seems like a topic that directly affects all developers, so it sounded
like it should be brought to
701 - 797 of 797 matches
Mail list logo
