Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

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 possible solution here is > to do the following: > > - revert the l

Re: [openstack-dev] [Neutron][Nova] API design and usability

On 08/07/2014 07:57 AM, Mathieu Gagné wrote: On 2014-08-06 7:58 PM, Robert Collins wrote: I'm astounded by this proposal - it doesn't remove the garbage collection complexity at all - it transfers it from our code - Nova - onto end users. So rather than one tested and consolidated implementati

[openstack-dev] [Ceilometer] Question on decorators in Ceilometer pecan framework

Hi, We have been struggling to get a decorator working for proposed new RBAC functionality in ceilometer-api. We're hitting a problem where GET request query parameters are mucked up by our decorator. Here's an example call: curl -H "X-Auth-Token:$TOKEN" 'http://localhost:8777/v2/meters?q.fi

Re: [openstack-dev] [nova] Deprecating CONF.block_device_allocate_retries_interval

On 08/06/2014 07:54 PM, Jay Pipes wrote: > I bring this up on the mailing list because I think Liyi's patch offers > an interesting future direction to the way that we think about our retry > approach in Nova. Instead of having hard-coded or configurable interval > times, I think Liyi's approach of

Re: [openstack-dev] ceilometer] [ft] Improving ceil.objectstore.swift_middleware

On Fri, 8 Aug 2014, Osanai, Hisashi wrote: Is there any way to proceed ahead the following topic? There are three active reviews that are somewhat related to this topic: Use a FakeRequest object to test middleware: https://review.openstack.org/#/c/110302/ Publish samples on other threads: ht

[openstack-dev] [Manila] Debug data for the NFS v4 hang issue

Per yesterday's IRC meeting, I have updated the debug data I had collected in the github issue @ https://github.com/csabahenk/cirros/issues/9 It has data for both : 32bit nfs client accessing 64bit cirros nfs server 64bit nfs client accessing 64bit cirros nfs server thanx, deepak ___

Re: [openstack-dev] [nova][oslo] oslo.config and import chains

On 08/08/14 11:04, Matthew Booth wrote: > On 07/08/14 18:54, Kevin L. Mitchell wrote: >> On Thu, 2014-08-07 at 17:46 +0100, Matthew Booth wrote: In any case, the operative point is that CONF. must >>> always be evaluated inside run-time code, never at module load time. >>> >>> ...unless y

Re: [openstack-dev] Which program for Rally

- Original Message - From: "Thierry Carrez" To: "OpenStack Development Mailing List" Sent: Wednesday, August 6, 2014 4:00:35 PM Subject: [openstack-dev] Which program for Rally 1. Rally as an essential QA tool Performance testing (and especially performance regression testing) is an es

Re: [openstack-dev] [ceilometer] [swift] Improving ceilometer.objectstore.swift_middleware

Hi, Is there any way to proceed ahead the following topic? Best Regards, Hisashi Osanai On Friday, August 01, 2014 7:32 PM, Hisashi Osanai wrote: > I would like to follow this discussion so I picked up points. > > - There are two way to collect info from swift, one is pollster and > the othe

Re: [openstack-dev] [devstack] Core team proposals

On 08/08/2014 01:05 PM, Chmouel Boudjnah wrote: On Thu, Aug 7, 2014 at 8:09 PM, Dean Troyer > wrote: Please respond in the usual manner, +1 or concerns. +1, I would be happy to see Ian joining the team. +1 Chmouel __

Re: [openstack-dev] backport fixes to old branches

Hi, On Tuesday, August 05, 2014 8:57 PM, Ihar Hrachyshka wrote: > > Thanks. To facilitate quicker backport, you may also propose the patch > > for review yourself. It may take time before stable maintainers or > > other interested parties get to the bug and do cherry-pick. I did cherry-pick for

Re: [openstack-dev] [nova][oslo] oslo.config and import chains

On 07/08/14 19:02, Kevin L. Mitchell wrote: > On Thu, 2014-08-07 at 17:41 +0100, Matthew Booth wrote: >> ... or arg is an object which defines __nonzero__(), or defines >> __getattr__() and then explodes because of the unexpected lookup of a >> __nonzero__ attribute. Or it's False (no quotes when p

Re: [openstack-dev] [nova][oslo] oslo.config and import chains

On 07/08/14 18:54, Kevin L. Mitchell wrote: > On Thu, 2014-08-07 at 17:46 +0100, Matthew Booth wrote: >>> In any case, the operative point is that CONF. must >> always be >>> evaluated inside run-time code, never at module load time. >> >> ...unless you call register_opts() safely, which is what I'

Re: [openstack-dev] [all] The future of the integrated release

On 08/08/2014 11:37 AM, Thierry Carrez wrote: > Personally I think we just need to get better at communicating the > downstream expectations, so that if we create waste, it's clearly > upstream fault rather than downstream. Currently it's the lack of > communication that makes developers produce mo

Re: [openstack-dev] [all] The future of the integrated release

Eoghan Glynn wrote: >> On 08/07/2014 01:41 PM, Eoghan Glynn wrote: >>> My point was simply that we don't have direct control over the >>> contributors' activities >> >> This is not correct and I've seen it repeated too often to let it go >> uncorrected: we (the OpenStack project as a whole) have a

Re: [openstack-dev] [all] The future of the integrated release

Michael Still wrote: > [...] I think an implied side effect of > the runway system is that nova-drivers would -2 blueprint reviews > which were not occupying a slot. > > (If we start doing more -2's I think we will need to explore how to > not block on someone with -2's taking a vacation. Some sor

Re: [openstack-dev] introducing cyclops

On Thu, Aug 07, 2014 at 12:01:04PM +0200, Piyush Harsh wrote: > Dear All, > > Let me use my first post to this list to introduce Cyclops and initiate a > discussion towards possibility of this platform as a future incubated project > in OpenStack. > > We at Zurich university of Applied Sciences h

[openstack-dev] use of compute node as a storage

i made 4 vm 1 controller, 1 network and 2 compute and i want 1 compute to run as a storage so plz help how can i do such ? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Deprecating CONF.block_device_allocate_retries_interval

Hi John, I have some comments as well. see blow :) _On 6 August 2014 18:54, Jay Pipes wrote: > So, Liyi Meng has an interesting patch up for Nova: > > https://review.openstack.org/#/c/104876 > > 1) We should just deprecate both the options, with a note in the option help > te

[openstack-dev] Further discussions on Cyclops

Dear Andre, I have not been an active user or IRC, but I have just now started using it, I use the handle PH7_0 on irc://rajaniemi.freenode.net ... Tell me the time and date and we can discuss more on cyclops. Cheers, Piyush. ___ Dr. Piyush Harsh, Ph.D. Resear

Re: [openstack-dev] [Neutron] how to deprecate a plugin

> On Thu, Jul 31, 2014 at 1:43 AM, YAMAMOTO Takashi > wrote: >>> On Wed, Jul 30, 2014 at 12:17 PM, YAMAMOTO Takashi >>> wrote: hi, what's the right procedure to deprecate a plugin? we (ryu team) are considering deprecating ryu plugin, in favor of ofagent. probably in K-

Re: [openstack-dev] [gerrit] Preparing a patch that has dependency to more than one code under review

Hi Nader, Le 08/08/2014 09:23, Nader Lahouti a écrit : Hi, Is it possible to send a patch for review (i.e. A) on gerrit based on multiple commit under the review (i.e. B and C)? Based on the wiki page to add dependency these command should be used: A->B, A->C (no dependency between B and C) #f

Re: [openstack-dev] [Neutron] "Neutron Ryu" status

just an update: the "Neutron Ryu" CI is getting stable now. please let me know if you noticed any problems. thank you. YAMAMOTO Takashi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] [devstack] Core team proposals

On Thu, Aug 7, 2014 at 8:09 PM, Dean Troyer wrote: > Please respond in the usual manner, +1 or concerns. +1, I would be happy to see Ian joining the team. Chmouel ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack

Re: [openstack-dev] introducing cyclops

Dear Eoghan, Thanks for your comments. Although you are correct that rating, charging, and billing policies are commercially sensitive to the operators, still if an operator has an openstack installation, I do not see why the stack could not offer a service that supports ways for the operator to i

Re: [openstack-dev] [all] The future of the integrated release

On 08/08/2014 12:12 AM, Stefano Maffulli wrote: > On 08/07/2014 01:41 PM, Eoghan Glynn wrote: >> My point was simply that we don't have direct control over the >> contributors' activities > > This is not correct and I've seen it repeated too often to let it go > uncorrected: we (the OpenStack proj

[openstack-dev] [HEAT] Is there any line length limitation in paste deploy configuration file?

Hi, Recently I have noticed the api-paste. ini file in heat has some very long lines (over the popular 80c). Wondering if there's recommended length limitation on it? Sometime, users have to read the file and change the configuration value, so I think it should be kept readable. Th

[openstack-dev] [gerrit] Preparing a patch that has dependency to more than one code under review

Hi, Is it possible to send a patch for review (i.e. A) on gerrit based on multiple commit under the review (i.e. B and C)? Based on the wiki page to add dependency these command should be used: A->B, A->C (no dependency between B and C) #fetch change under review and check out branch based on tha

<    1   2