John Griffith wrote on 07/26/2013 03:44:12
AM:
> I think it would be a very useful tool for initial introduction of a
> new driver and even perhaps some sort of check that's run and
> submitted again prior to milestone releases.
+1. Do you see this happening for Havana? Or should this be a su
> From: Joe Gordon [mailto:[email protected]]
> Sent: 26 July 2013 23:16
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [Nova] support for multiple active scheduler
> policies/drivers
>
>
>>
>> On Wed, Jul 24, 2013 at 6:18 PM, Alex Glikson wrote:
>>> Russell Bryant
Hi
Hi, I am interested in helping out with QE efforts on upstream
OpenStack, specifically around Neutron.
I'm trying to understand the following blueprint,can you please point me to
more detailed design
https://blueprints.launchpad.net/neutron/+spec/auto-associate-floating-ip
Thanks
Ofer Bla
On Sun, Jul 28, 2013 at 3:56 AM, Avishay Traeger wrote:
> John Griffith wrote on 07/26/2013 03:44:12
> AM:
>
> > I think it would be a very useful tool for initial introduction of a
> > new driver and even perhaps some sort of check that's run and
> > submitted again prior to milestone releases
Stuart,
I agree with Mark's comments, wanted to address this:
3) we could potentially link roles to the regex
eg this could allow role1_xxx to be writable only if you have 'role1'.
By assigning appropriate roles (com.provider/com.partner/nova?) you
could provide the ability to write to that prefi
Hi dims,
All of the deployments I've been a part of so far use 5.0 or newer, as do
most of the developers I interact with. I'm not aware of anything specific
as to why 4.1 would not work (someone more familiar with details of the
vSphere APIs than I may be able to chime in), but based on customer
- Original Message -
> From: "Doug Hellmann"
> To: "OpenStack Development Mailing List"
> Sent: Saturday, 27 July, 2013 4:15:53 AM
> Subject: Re: [openstack-dev] [Keystone] Alembic support
>
>
>
>
> On Fri, Jul 26, 2013 at 2:04 PM, Adam Young < [email protected] > wrote:
>
>
>
Hey all!
There is currently an issue with which is causing a very high failure
rate in the gate. From IRC:
18:32:19 clarkb | the grenade failures seem to get very
consistent in the gate at 2013-0-27 1552UTC
18:32:27 clarkb | before that the success rate is much higher
18:34:53
On 26/07/13 09:43 -0700, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2013-07-26 06:37:09 -0700:
On 25/07/13 19:07, Bartosz Górski wrote:
> We want to start from something simple. At the beginning we are assuming
> no dependencies between resources from different region. Our first u
Hey Everyone,
I thought I'd send a note out to ask folks to try and be a bit more
diligent when it comes to assigning bugs to recheck/reverify entries in the
gate.
I've noticed a few bugs that are frequently listed for recheck, even though
they have little or nothing to do with the failure. Just
On 07/28/2013 08:02 PM, Monty Taylor wrote:
Hey all!
There is currently an issue with which is causing a very high failure
rate in the gate. From IRC:
18:32:19 clarkb | the grenade failures seem to get very
consistent in the gate at 2013-0-27 1552UTC
18:32:27 clarkb | before t
Monty,
I picked up a latest run
https://jenkins.openstack.org/job/gate-grenade-devstack-vm/22236/
which lead me to
http://logs.openstack.org/51/38951/2/check/gate-grenade-devstack-vm/22236/logs/new/screen-c-vol.txt.gz
So could the problem be 38810 itself?
2013-07-29 00:46:37.562 27821 TRACE cind
On 07/28/2013 09:28 PM, Davanum Srinivas wrote:
Monty,
I picked up a latest run
https://jenkins.openstack.org/job/gate-grenade-devstack-vm/22236/
which lead me to
http://logs.openstack.org/51/38951/2/check/gate-grenade-devstack-vm/22236/logs/new/screen-c-vol.txt.gz
So could the problem be 38810
On 07/28/2013 09:42 PM, Sean Dague wrote:
On 07/28/2013 09:28 PM, Davanum Srinivas wrote:
Monty,
I picked up a latest run
https://jenkins.openstack.org/job/gate-grenade-devstack-vm/22236/
which lead me to
http://logs.openstack.org/51/38951/2/check/gate-grenade-devstack-vm/22236/logs/new/screen-
14 matches
Mail list logo