Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 12 March 2015 at 12:07, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/11/2015 07:48 PM, Joe Gordon wrote: >> Out of sync Quotas -- >> >> https://etherpad.openstack.org/p/PHL-ops-nova-feedback L63 >> >> The quotas code is quite racey (this is

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

I'd prefer 1400 as well. But "A Foolish Consistency is the Hobgoblin of Little Minds" - Erno > -Original Message- > From: Nikhil Komawar [mailto:nikhil.koma...@rackspace.com] > Sent: 11 March 2015 20:40 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [op

Re: [openstack-dev] Avoiding regression in project governance

On 11 March 2015 at 05:29, Russell Bryant wrote: > The TC is in the middle of implementing a fairly significant change in > project governance. You can find an overview from Thierry on the > OpenStack blog [1]. > > Part of the change is to recognize more projects as being part of the > OpenStack

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

On 12 March 2015 at 12:37, Ian Wienand wrote: > On 03/11/2015 08:10 AM, Robert Collins wrote: >> The wheel has been removed from PyPI and anyone installing testtools >> 1.7.0 now will install from source which works fine. > > I noticed the centos7 job failed with the source version. > > The failin

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

On 11/03/15 23:49 +, Kuvaja, Erno wrote: I'd prefer 1400 as well. But "A Foolish Consistency is the Hobgoblin of Little Minds" Either work for me, as long as someone pings me :P Flavio - Erno -Original Message- From: Nikhil Komawar [mailto:nikhil.koma...@rackspace.com] Sent:

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

> On 11 Mar 2015, at 11:59 pm, Sean Dague wrote: > > Nova Rolling Upgrades > - > > Most people really like the concept, couldn't find anyone that had > used it yet because Neutron doesn't support it, so they had to big > bang upgrades anyway. I couldn’t make it to the ops s

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

It sounds like we're diverging a bit from the original topic, but... whatever. Yeah! We should totally work towards a quota service - that's what we said back in 2011 This is a topic that comes back regularly like the Halley's comet. With the only difference that it happens every 6 months, not 75

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

In summary, we have decided to use the usage notification events emitted by heat (http://tinyurl.com/oultjm5). This should allow us to detect stack action completions, and errors (with reasons) which should be enough for a Bay implementation that does not need to poll. Stack timeouts can be pass

Re: [openstack-dev] [neutron] [dhcp] dnsmasq scale problem

The easy way to scale it is to just launch more dhcp agents. The scaling issue arises when a single dhcp agent is managing thousands of dnsmasq instances and interfaces. On Wed, Mar 11, 2015 at 4:07 PM, Wanjing Xu wrote: > One of my peers mentioned that people talked about dnsmasq scale problems

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

On 03/12/2015 10:37 AM, Ian Wienand wrote: > File "/tmp/easy_install-mV2rSm/unittest2-1.0.0/unittest2/case.py", line > 16, in > ImportError: cannot import name range > Complete output from command python setup.py egg_info: OK, so this suggests the version of "six" is wrong. unittest2 do

Re: [openstack-dev] Avoiding regression in project governance

On 11/03/15 19:06 +, Tim Bell wrote: -Original Message- From: Stefano Maffulli [mailto:stef...@openstack.org] Sent: 11 March 2015 03:16 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Avoiding regression in project governance On Tue, 2015-03-10 at 15:23 -0700, Jame

Re: [openstack-dev] [stable] Icehouse 2014.1.4 freeze exceptions

On 11/03/15 12:46 +0100, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2015 12:21 PM, Alan Pevec wrote: Hi, next Icehouse stable point release 2014.1.4 has been slipping last few weeks due to various gate issues, see "Recently closed" section in https://etherpad

Re: [openstack-dev] [nova][neutron][nfv] is there any reason neutron.allow_duplicate_networks should not be True by default?

On 11 March 2015 at 10:56, Matt Riedemann wrote: > While looking at some other problems yesterday [1][2] I stumbled across > this feature change in Juno [3] which adds a config option > "allow_duplicate_networks" to the [neutron] group in nova. The default > value is False, but according to the s

[openstack-dev] [Glance] Nitpicking in code reviews

Hi all, Following the code reviews lately I've noticed that we (the fan club seems to be growing on weekly basis) have been growing culture of nitpicking [1] and bikeshedding [2][3] over almost every single change. Seriously my dear friends, following things are not worth of "-1" vote if even

Re: [openstack-dev] Avoiding regression in project governance

On Wed, 2015-03-11 at 17:59 -0500, Ed Leafe wrote: > The longer we try to be both sides of this process, the longer we will > continue to have these back-and-forths about stability vs. innovation. If I understand correctly your model, it works only for users/operators who decide to rely on a vendo

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On Wed, Mar 11, 2015 at 4:07 PM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/11/2015 07:48 PM, Joe Gordon wrote: > > Out of sync Quotas -- > > > > https://etherpad.openstack.org/p/PHL-ops-nova-feedback L63 > > > > The quotas code is quite rac

Re: [openstack-dev] [Openstack-operators] [all][qa][gabbi][rally][tempest] Extend "rally verfiy" to unify work with Gabbi, Tempest and all in-tree functional tests

Alex, * rally plugin should be a part of project (for example, located in > functional tests directory) There are 2 issues with such solution: 1) If rally didn't load plugin, command "rally verify " won't exist 2) Putting some strange Rally plugin to source of other projects will be quit

[openstack-dev] [QA] Meeting Thursday March 12th at 17:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, March 12th at 17:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to a

[openstack-dev] [Group-Based-Policy] How to deal with "improvements"

Hello Folks, As a follow up of [0] I was working on a proposal for adding the same sharing capabilities to servicechain constructs. While thinking about the use cases for doing this, a question came to my mind: How should I deal with this improvement from a process perspective? I'm not sure addi

Re: [openstack-dev] [Glance] Nitpicking in code reviews

FWIW I agree with #3 and #4 but not #1 and #2. Spelling is an easy enough thing to get right and speaks to the quality standard to which the product is held even in commit messages and comments (consider the 'broken window theory'). Of course everyone makes mistakes (I am a terrible speller)

Re: [openstack-dev] [Manila] Ceph native driver for manila

On 03/04/2015 09:33 AM, Danny Al-Gaaf wrote: Am 04.03.2015 um 15:18 schrieb Csaba Henk: Hi Danny, - Original Message - From: "Danny Al-Gaaf" To: "Deepak Shetty" Cc: "OpenStack Development Mailing List (not for usage questions)" , ceph-de...@vger.kernel.org Sent: Wednesday, March 4,

Re: [openstack-dev] [cinder] K3 Feature Freeze Exception request for bp/nfs-backup

Also, can https://review.openstack.org/#/c/163647 be considered. all it does is move code from the accepted nfs.py to posix.py as described in the approved spec. This enables all posix complient file systems to be used, such as lustre instead of just n

Re: [openstack-dev] Avoiding regression in project governance

> -Original Message- > From: Stefano Maffulli [mailto:stef...@openstack.org] > Sent: 12 March 2015 00:26 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Avoiding regression in project governance > > On Wed, 2015-03-11 at 17:59 -0500, Ed Leafe wrote: > > The longer

Re: [openstack-dev] [kolla] about the image size

> On Mar 12, 2015, at 04:08, Steven Dake (stdake) wrote: > > > > On 3/10/15, 12:22 AM, "Bohai (ricky)" wrote: > >> Hi, stackers >> >> I try to use the Kolla Images and pull them down from docker hub. >> I found the size of the image is bigger than what I thought(for example, >> the images o

Re: [openstack-dev] [nova] readout from Philly Operators Meetup

On 12 March 2015 at 13:05, Salvatore Orlando wrote: > It sounds like we're diverging a bit from the original topic, but... > whatever. > Yeah! We should totally work towards a quota service - that's what we said > back in 2011 :). > This is a topic that comes back regularly like the Halley's com

Re: [openstack-dev] [Ironic] Thinking about our python client UX

Oh, sure - switching to the spec is fine, I didn't realise there was one, given the list thread had gone quiet :) -Rob On 12 March 2015 at 12:24, Ruby Loo wrote: > On 11 March 2015 at 18:21, Robert Collins wrote: > ... >> >> Since there was no debate on the compat thing, I've thrown up an >> et

Re: [openstack-dev] [cinder]difference between spec merged and BP approval

Hi Stefano, Thanks so much for your detailed answer, I finally know the reason why those patches are not reviewed in this cycle. Actually, this BP (https://blueprints.launchpad.net/python-cinderclient/+spec/support-modify-volume-image-metadata) is created very early around Nov. 2014, and there

[openstack-dev] [Horizon][Keystone] Failed to set up keystone v3 api for horizon

is there anyone tryed this and successfully? On Mon, Mar 9, 2015 at 4:25 PM, Lei Zhang wrote: > Hi guys, > > I am setting up the keytone v3 api. Now I meet a issue about the > `cloud_admin` policy. > > Base on the > http://www.florentflament.com/blog/setting-keystone-v3-domains.html > article, I

Re: [openstack-dev] [Neutron] Issue when upgrading from Juno to Kilo due to agent report_state RPC namespace patch

- Original Message - > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Should we target it for Kilo? It does not seem right to allow it > slipping into the next release while we know there are operators > relying on the feature. Of course, this will be fixed for Kilo. This is the i

Re: [openstack-dev] [neutron] [metadata] metadata service when NOT using name space

Can you explain why are you not using namespaces? (I'm really curious). I've been thinking of proposing to deprecate that option only for the simple truth that it's not tested and we have no idea if it works anymore, or if anyone actually uses it. - Original Message - > When use_namespace

Re: [openstack-dev] [Neutron] Ryu/ofagent CI outage

hi, sorry for keep forgetting and thank you for reminder. YAMAMOTO Takashi > Hi- > > Regarding the CI offline mails, I previously received an email from Anita. > Please find the summary below. > > Please set your account listing to down on this page: > https://wiki.openstack.org/wiki/ThirdPar

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

On 12 March 2015 at 13:18, Ian Wienand wrote: > On 03/12/2015 10:37 AM, Ian Wienand wrote: >> File "/tmp/easy_install-mV2rSm/unittest2-1.0.0/unittest2/case.py", line >> 16, in >> ImportError: cannot import name range >> Complete output from command python setup.py egg_info: > > OK, so th

Re: [openstack-dev] [cinder]difference between spec merged and BP approval

On Wed, Mar 11, 2015 at 8:17 PM, Chen, Wei D wrote: > Hi Stefano, > > Thanks so much for your detailed answer, I finally know the reason why > those patches are not reviewed in this cycle. > Actually, this BP ( > https://blueprints.launchpad.net/python-cinderclient/+spec/support-modify-volume-ima

Re: [openstack-dev] [Glance] Nitpicking in code reviews

+1 to what John said (overall). However, I think I know where Erno is coming from. We're very close to the FF and people are trying hard to get green on the check as well as ensure thoroughness of the feature; this might lead to bunch of these errors. Pointing them out and expecting to comple

<    1   2