Excerpts from Nachi Ueno's message of 2014-01-10 13:42:30 -0700:
Hi Flavio, Clint
I agree with you guys.
sorry, may be, I wasn't clear. My opinion is to remove every
configuration in the node,
and every configuration should be done by API from central resource
manager. (nova-api or neturon
On 01/09/2014 04:16 PM, Russell Bryant wrote:
On 01/08/2014 05:53 PM, Joe Gordon wrote:
Hi All,
As you know the gate has been in particularly bad shape (gate queue over
100!) this week due to a number of factors. One factor is how many major
outstanding bugs we have in the gate. Below is a
First, thanks a ton for diving in on all this Russell. The big push by
the Nova team recently is really helpful.
On 01/11/2014 09:57 AM, Russell Bryant wrote:
On 01/09/2014 04:16 PM, Russell Bryant wrote:
On 01/08/2014 05:53 PM, Joe Gordon wrote:
Hi All,
As you know the gate has been in
Hey Cinder Team!
One of the things that's getting increasingly difficult as we grow the
number of drivers in the tree and I try to get the driver cert
initiative kicked off is rounding up an expert for each of the
drivers in the tree. I've started a simple wiki page / matrix [1]
that is designed
As someone that's done a decent amount of hacking on
status.html/status.js, I think we're getting to a level of complexity on
our JS status pages that we should probably stop doing this all inline
(probably should have stopped a while ago).
I'd like to propose that we pick some javascript
Hi everyone,
I just wanted to bring up some changes that recently merged to tempest. As part
of the tempest unit tests blueprint I converted the run_tests.sh script to
execute unit tests instead of running tempest itself. This makes the
run_tests.sh script consistent with the other projects to
Thanks! Just wanted to check before we went deeper into our coding.
- Original Message -
The Resources(Nodes) item that is collapsible on the left hand side in that
attached wireframes is a Panel Group in the Infrastructure Dashboard. The
plan is to make Panel Groups
On 01/11/2014 11:38 AM, Sean Dague wrote:
3) (still testing) https://review.openstack.org/#/c/65805/
Right now when tempest runs in the devstack-gate jobs, it runs with
concurrency=4 (run 4 tests at once). Unfortunately, it appears that
this maxes out the deployment and results in timeouts
-Original Message-
From: Tzu-Mainn Chen [mailto:tzuma...@redhat.com]
Sent: Saturday, January 11, 2014 2:23 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Tuskar-UI navigation
Thanks! Just wanted to check before we went deeper into
On Wed, Jan 8, 2014 at 10:48 PM, Matt Riedemann
mrie...@linux.vnet.ibm.com wrote:
Another question. This patch [1] failed turbo-hipster after it was approved
but I don't know if that's a gating or just voting job, i.e. should someone
do 'reverify migrations' on that patch or just let it sit
On Wed, Jan 8, 2014 at 10:57 PM, Sean Dague s...@dague.net wrote:
[snip]
So instead of trying to fix the individual runs, because t-h runs pretty
fast, can you just fix it with bulk. It seems like the issue in a migration
taking a long time isn't a race in OpenStack, it's completely
11 matches
Mail list logo
