Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Nikhil Komawar
Thanks Amrith! I am a big supporter on including +0s. On 4/9/16 6:31 PM, Amrith Kumar wrote: > Thanks to Dims and Steve for bringing this up. > > It has long been my opinion that +0's are invaluable for the question > asking, and for getting to understand software, and unfortunately +0's

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Joshua Harlow
+1 from me also, I also use +0 for question asking and the like, because IMHO that's not what -1 are for. As for myself losing stackalytics stats when *I* do this (ie using +0 instead of -1), meh, I got better things in my life to think/care about :-P -Josh Nikhil Komawar wrote: Thanks

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

2016-04-10 Thread Hongbin Lu
My preference is #1, but I don’t feel strong to exclude #2. I would agree to go with #2 for now and switch back to #1 if there is a demand from users. For Ton’s suggestion to push Marathon into the introduced configuration hook, I think it is a good idea. Best regards, Hongbin From: Ton Ngo

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

2016-04-10 Thread Ton Ngo
I would agree that #2 is the most flexible option, providing a well defined path for additional frameworks such as Kubernetes and Swarm. I would suggest that the current Marathon framework be refactored to use this new hook, to serve as an example and to be the supported framework in Magnum. This

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Ricardo Carrillo Cruz
++, exactly my thoughts. I believe most people don't vote 0 for questions about the change because 'it won't count'. That's really bad, IMHO 0 should be for asking things not clear in the patch, whereas a -1 should be a 'this code here is not right'. I believe the 0s should be tracked somehow.

[openstack-dev] [Infra] Gerrit performance

2016-04-10 Thread Gary Kotton
Hi, Is anyone else having problems with gerrit: 1. Sometimes get a proxy error 2. Performance is very bad Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Vitrage] putting overlapping-templates-basic-support on the back-burner

2016-04-10 Thread Rosensweig, Elisha (Nokia - IL)
Hi All, Since * the overlapping templates BP (https://blueprints.launchpad.net/vitrage/+spec/overlapping-templates-basic-support) is a large one, which deserves a lot of design and discussion * there is a lot of focus on stability and clarity for the summit I'll be putting working on this BP

Re: [openstack-dev] [Infra] Gerrit performance

2016-04-10 Thread Andrey Kurilin
https://twitter.com/andrey_kurilin/status/681861838263443457 On Sun, Apr 10, 2016 at 10:39 AM, Gary Kotton wrote: > Hi, > Is anyone else having problems with gerrit: > >1. Sometimes get a proxy error >2. Performance is very bad > > Thanks > Gary > >

Re: [openstack-dev] [Vitrage] putting overlapping-templates-basic-support on the back-burner

2016-04-10 Thread Afek, Ifat (Nokia - IL)
> -Original Message- > From: Rosensweig, Elisha (Nokia - IL) > [mailto:elisha.rosensw...@nokia.com] > > Hi All, > > Since > * the overlapping templates BP > (https://blueprints.launchpad.net/vitrage/+spec/overlapping-templates- > basic-support) is a large one, which deserves a lot of

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

2016-04-10 Thread Moshe Levi
From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Friday, April 08, 2016 4:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource

Re: [openstack-dev] [Infra] Gerrit performance

2016-04-10 Thread Andreas Jaeger
Jeremy has restarted gerrit now (Thanks!), should be fine now. Next time, please report on IRC #openstack-infra directly, Andreas - you didn't know that the whole world waited on gerrit __ OpenStack Development Mailing List

Re: [openstack-dev] [Infra] Gerrit performance

2016-04-10 Thread Jeremy Stanley
On 2016-04-10 12:43:06 +0300 (+0300), Andrey Kurilin wrote: > https://twitter.com/andrey_kurilin/status/681861838263443457 A lot of the Infra team (me included) aren't on social media Web sites like that one, but Andreas Jaeger helpfully mentioned it in the #openstack-infra IRC channel on

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Matt Riedemann
On 4/10/2016 6:37 PM, Clint Byrum wrote: Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: There is also disincentive in +1ing a change that you don't understand and is wrong and then a core comes along and -1s it (you get dinged for the disagreement). And there is

Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay

2016-04-10 Thread Kai Qiang Wu
#2 seems more flexible, and if it be proved it can "make the SAME mesos bay applied with mutilple frameworks." It would be great. Which means, one mesos bay should support multiple frameworks. Thanks Best Wishes,

Re: [openstack-dev] [Docs] Austin Design Summit Sessions - Docs

2016-04-10 Thread Lana Brindley
The docs sessions are now in Sched, complete with etherpad links: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Documentation%3A Note the Install Guide working session is on Wednesday at 11:50, timed so that we can run into lunch if required. I strongly suggest

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Masayuki Igawa
2016-04-11 9:46 GMT+09:00 Matt Riedemann : > > > On 4/10/2016 6:37 PM, Clint Byrum wrote: >> >> Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: >>> >>> There is also disincentive in +1ing a change that you don't understand >>> and is wrong and then

[openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress

2016-04-10 Thread Hongbin Lu
Hi requirements team, In short, the recently introduced package py2-ipaddress [1] seems to break Magnum. In details, Magnum gate recently broke by an error: "'\xac\x18\x05\x07' does not appear to be an IPv4 or IPv6 address" [2] (the gate breakage has been temporarily fixed but we are looking

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Sheel Rana Insaan
> So should we add what we don't want to see people -1 for? >[1] http://docs.openstack.org/infra/manual/developers.html#peer-review This seems right way.. but concern is do everyone follow all docs? But atleast we should document it somewhere. Regards, Sheel Rana On Apr 11, 2016 6:52 AM,

Re: [openstack-dev] [Ironic] Failed to update Neutron port

2016-04-10 Thread Haomeng, Wang
Hi, With my experence, for such "2016-04-08 16:31:38.690 31893 ERROR ironic.dhcp.neutron [-] Failed to update Neutron port 7fb98457-90e6-43be-a353-f03ea1959912." issue, some cases are that root cause is we did not register baremetal's mac into ironic, so neutron can not bind mac for baremetal

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Masayuki Igawa
2016-04-11 10:31 GMT+09:00 Sheel Rana Insaan : >> So should we add what we don't want > to see people -1 for? > >>[1] http://docs.openstack.org/infra/manual/developers.html#peer-review > > This seems right way.. but concern is do everyone follow all docs? Nice point.

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Amrith Kumar
Thanks Nikhil, appreciate the comment on the gerrit bug. -amrith > -Original Message- > From: Nikhil Komawar [mailto:nik.koma...@gmail.com] > Sent: Sunday, April 10, 2016 10:27 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all][stackalytics] Gaming the

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Clint Byrum
Excerpts from Morgan Fainberg's message of 2016-04-10 16:47:28 -0700: > On Sun, Apr 10, 2016 at 4:37 PM, Clint Byrum wrote: > > > Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > > > There is also disincentive in +1ing a change that you don't understand >

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Clint Byrum
Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > There is also disincentive in +1ing a change that you don't understand > and is wrong and then a core comes along and -1s it (you get dinged for > the disagreement). And there is disincentive in -1ing a change for the >

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

2016-04-10 Thread Morgan Fainberg
On Sun, Apr 10, 2016 at 4:37 PM, Clint Byrum wrote: > Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > > There is also disincentive in +1ing a change that you don't understand > > and is wrong and then a core comes along and -1s it (you get dinged for > >

Re: [openstack-dev] [Neutron] Newton blueprints call for action

2016-04-10 Thread Sukhdev Kapur
Hi Rossella, Good to hear that you will follow through with this. Ironic is looking for this API as well for bare metal deployments. We would love to work with you to make sure that this API/Implementation works for all servers ( VMs as well BMs) Thanks -Sukhdev On Wed, Apr 6, 2016 at 4:32 AM,