On 2014-05-21 14:57:06 -0700 (-0700), James E. Blair wrote:
[...]
> Joshua Hesketh has been reviewing a truly impressive number of infra
> patches for quite some time now. He has an excellent grasp of how the
> CI system functions, no doubt in part because he runs a copy of it and
> has been doing
Hi,
I notice that the templated catalog doesn't support the V3 API*. This
is a blocker for us, particularly for Heat since it uses V3
internally. We could switch to the SQL backend, but I'm sure others
are affected by this too. Is it hard to fix?
Cheers,
Kieran
* https://bugs.launchpad.net/keys
On 2014-05-22 18:33:34 -0400 (-0400), Matthew Treinish wrote:
[...]
> I'd like to stick with one scheme and not decide to change it
> later on. I figured I should bring this out to a wider audience to
> see if there were other suggestions or opinions before I pushed
> out the tag, especially becaus
Tempest API’s XML test will run with 1 test failure when run with Nosetest.
When we run the tempest with nosetest command (ex -nosetest –v
./tempest/api/compute/test_xyz.py), it run *BaseComputeTest
::create_test_server & create_test_server_group *functions also as test
with any of the API tests. B
On 05/22/2014 08:33 PM, Jeremy Stanley wrote:
> On 2014-05-22 18:33:34 -0400 (-0400), Matthew Treinish wrote:
> [...]
>> I'd like to stick with one scheme and not decide to change it
>> later on. I figured I should bring this out to a wider audience to
>> see if there were other suggestions or opin
On 2014-05-22 20:40:16 -0400 (-0400), Sean Dague wrote:
> Given that we're not really going to have major / minor bumps at this
> point (more a continous roll), I might argue that we should just go
> Firefox on it and bump the integer on every release.
[...]
Marvellously pragmatic. If you need min
I plan on attending.
-bryan
On Thu, May 22, 2014 at 10:48 AM, Jarret Raim wrote:
> All,
>
> There was some interest at the Summit in semi-combining the mid-cycle meet
> ups for Barbican, Keystone and the OSSG as there is some overlap in team
> members and interest areas. The current dates being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/05/14 05:00, W Chan wrote:
> Renat,
>
> I want to avoid having to explicitly import the mistral.config module in
> order
> to have configuration loaded properly. The problem with the way
> mistral.config
> is coded is that we have to use im
Thanks for your helping.
But in our system, the problem is that:
If using the nova cli, this libvirt problem not occurred.
But in deleting cluster of the sahara , this problem occurred.
That if our problem.
Can it influence the step on deleting cluster in the process to destroy vm
of libvir
On Fri, May 23, 2014 at 09:34:35AM +0900, GHANSHYAM MANN wrote:
> Tempest API’s XML test will run with 1 test failure when run with Nosetest.
> When we run the tempest with nosetest command (ex -nosetest –v
> ./tempest/api/compute/test_xyz.py), it run *BaseComputeTest
> ::create_test_server & creat
On Fri, May 23, 2014 at 01:01:42AM +, Jeremy Stanley wrote:
> On 2014-05-22 20:40:16 -0400 (-0400), Sean Dague wrote:
> > Given that we're not really going to have major / minor bumps at this
> > point (more a continous roll), I might argue that we should just go
> > Firefox on it and bump the
Yes, Issue is in nose. I do not like nose due to these kind of assumption
for test running :). There is no reason of using nose, I just ran that and
counter this issue.
I totally agree on your point not to spent time to fix these kind of issue.
As you mentioned. may be blocking nose would be good
Hi Everyone,
As part of moving to the new blueprint review process with the qa-specs repo [1]
I'm going to do a purge of the current tempest blueprint list. I'm planning to
do this next Thursday, the 29th, sometime before the QA meeting. This is really
just an exercise to cleanup and prioritize t
Well, for a use case we had in mind we were trying to figure out how to
simply get an IP address on a subnet. We essentially want to use such an
address internally by the controller and make sure it is not used for a
port that gets created on a network with that subnet. In this use case, an
interf
On 22 May 2014 13:59, Mandeep Dhami wrote:
>
> Maru's concerns are that:
> 1. It is large
> 2. It is complex
>
> And Armando's related concerns are:
> 3. Could dev/review cycles be better spent on refactoring
> 4. If refactored neutron was available, would a simpler option become more
> viable
Th
Yes that’s the one Yi, thanks ;-)
/Alan
From: Yi Sun [mailto:beyo...@gmail.com]
Sent: May-22-14 2:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Alan Kavanagh; Balázs Gibizer
Subject: Re: [openstack-dev] [NFV][Neutron] Link to patch/review for allowing
instances to rec
Hi
Just wanted to comment on some points below inline.
/Alan
-Original Message-
From: A, Keshava [mailto:keshav...@hp.com]
Sent: May-22-14 2:25 AM
To: Kyle Mestery; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at desig
Thanks to everyone who participated in the Group Policy meeting [1] earlier
today. A lot of good discussion that hopefully will continue with
participation from the larger community. I wanted to first make a comment
about how the Group Policy work was received outside the Neutron community
and the
+1
I agree. Lets focus on client SSL Termination at LB for Juno release.
Thanks,
Vivek
From: , German
mailto:german.eichber...@hp.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 22, 2014 at 12:53 PM
To
Hi Armando:
Those are good points. I will let Bob Kukura chime in on the specifics of
how we intend to do that integration. But if what you see in the
prototype/PoC was our final design for integration with Neutron core, I
would be worried about that too. That specific part of the code
(events/not
Thanks Carl, for pitching in for us.
As Carl said, this is the last detail that is being worked out.
Wuhogning,
I am requesting Rajeev and Mike(CC'ed) who are working in DVR SNAT
to post the document into to the blueprint link here, so that you
can take a look.
https://blueprints.launchpad.net
For specs repo renaming old github links will still work due to the
github feature that makes a redirect while renaming project in one
organization.
On Fri, May 23, 2014 at 4:16 AM, Jeremy Stanley wrote:
> On 2014-05-21 23:52:14 -0700 (-0700), Clint Byrum wrote:
>> You didn't also ask them to sub
Hi,
We have an openstack deployment (Havana on CentOS) in HA mode with
nova-network service deployed using Mirantis Fuel v4.0 .
When uploading images with large filesize (more than 1 GB) from dashboard,
after upload is done the dashboard is showing "504 Gateway Timeout". What
could be the problem?
Do you have a loadbalancer or something that limits the request time in the
path? That would be my guess, you probably need to raise the
request_termination_timeout.
Best,
Aaron
On Thu, May 22, 2014 at 10:59 PM, Tizy Ninan wrote:
> Hi,
>
> We have an openstack deployment (Havana on CentOS) i
Adding one more renaming last day - murano-api repo to murano
(https://review.openstack.org/95085).
On Fri, May 23, 2014 at 9:41 AM, Sergey Lukjanov wrote:
> For specs repo renaming old github links will still work due to the
> github feature that makes a redirect while renaming project in one
>
101 - 125 of 125 matches
Mail list logo
