Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Thomas Goirand
On 10/19/2013 11:50 PM, Jeremy Stanley wrote: On 2013-10-19 23:29:28 +0800 (+0800), Thomas Goirand wrote: Though the Debian FTP masters seems to insist on having correct copyright holders in debian/copyright, and I am a bit lost after the 2 rejects I just had. Well, this is still a fuzzy

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Robert Collins
On 20 October 2013 04:50, Jeremy Stanley fu...@yuggoth.org wrote: Well, this is still a fuzzy topic. We have a lot of contributions and know who the authors are, but not necessarily who the copyright s/authors/submitters/. I've heard (though I lack direct evidence) that some teams funnel their

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Robert Collins
On 20 October 2013 02:35, Monty Taylor mord...@inaugust.com wrote: However, even as a strong supporter of accurate license headers, I would like to know more about the FTP masters issue. I dialog with them, as folks who deal with this issue and its repercutions WAY more than any of us might

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Joe Gordon
On Oct 20, 2013 11:29 AM, Robert Collins robe...@robertcollins.net wrote: On 20 October 2013 02:35, Monty Taylor mord...@inaugust.com wrote: However, even as a strong supporter of accurate license headers, I would like to know more about the FTP masters issue. I dialog with them, as folks

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Thomas Goirand
On 10/20/2013 05:41 PM, Joe Gordon wrote: http://ftp-master.metadata.debian.org/changelogs//main/l/linux/linux_3.11.5-1_copyright Not even the kernel itself has a complete list of all the copyright owners. best, Joe Well, good luck finding all the copyright holders for such a large and

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Jeremy Stanley
On 2013-10-20 22:20:25 +1300 (+1300), Robert Collins wrote: [...] OTOH registering one's nominated copyright holder on the first patch to a repository is probably a sustainable overhead. And it's probably amenable to automation - a commit hook could do it locally and a check job can assert

[openstack-dev] [ceilometer] [qa] Ceilometer ERRORS in normal runs

2013-10-20 Thread Sean Dague
Dave Kranz has been building a system so that we can ensure that during a Tempest run services don't spew ERRORs in the logs. Eventually, we're going to gate on this, because there is nothing that Tempest does to the system that should cause any OpenStack service to ERROR or stack trace

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Jeremy Stanley
On 2013-10-20 20:57:56 +0800 (+0800), Thomas Goirand wrote: Well, good luck finding all the copyright holders for such a large and old project. It's not really practical in this case, unfortunately. To a great extent, the same goes for projects a quarter the size and age of the Linux

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

2013-10-20 Thread Jeremy Stanley
On 2013-10-20 13:00:31 + (+), Jeremy Stanley wrote: [...] automated job which proposes changes to a copyright holders list in each project by running a query with the author and date of each commit looking for new affiliations [...] Though the more I think about this, it would be

Re: [openstack-dev] [novaclient]should administrator can see all servers of all tenants by default?

2013-10-20 Thread Lingxian Kong
two questions here: 1. whther '--all-tenants' should be with '--tenant' or not. 2. can admin see other tenant's server using its name instead of id? 2013/10/16 Robert Collins robe...@robertcollins.net I think that would be fine: --tenant FOO implying 'show me results from FOO if I have access

Re: [openstack-dev] [Neutron] Linux Bridge MTU bug when the VXLAN tunneling is used

2013-10-20 Thread Salvatore Orlando
It might be worth both documenting this limitation on the admin guide and provide a fix which we should backport to havana too. It sounds like the fix should not be too extensive, so the backport should be easily feasible. Regards, Salvatore On 18 October 2013 21:50, Édouard Thuleau

Re: [openstack-dev] [Openstack] Does openstack have a notification system that will let us know when a server changes state ?

2013-10-20 Thread Jay Lau
Please get more detail from https://wiki.openstack.org/wiki/SystemUsageData Thanks, Jay 2013/10/19 Gabriel Hurley gabriel.hur...@nebula.com The answer is “sort of”. Most projects (including Nova) publish to an RPC “notifications” channel (e.g. in rabbitMQ or whichever you use in your

Re: [openstack-dev] Does openstack have a notification system that will let us know when a server changes state ?

2013-10-20 Thread Sandy Walsh
Notifications work great. Actually StackTach has a web interface where you can watch the notifications coming through in real-time. We're slowing trying to get Ceilometer to have this functionality. StackTach works with Nova and Glance events currently. https://github.com/rackerlabs/stacktach

[openstack-dev] Fwd: Change in openstack/nova[master]: Moved quota headroom calculations into quota_reserve

2013-10-20 Thread Michael Bright
OK Dan, On 20 October 2013 16:08, Dan Smith d...@danplanet.com wrote: I'm afraid I really need help now - in particular on how to add a suitable test case. I've been looking at /opt/stack/nova/nova/tests/compute/test_compute_api.py running test_create_quota_exceeded_messages under the

[openstack-dev] Fwd: Change in openstack/nova[master]: Moved quota headroom calculations into quota_reserve

2013-10-20 Thread Michael Bright
OK Dan, On 20 October 2013 16:08, Dan Smith d...@danplanet.com wrote: I'm afraid I really need help now - in particular on how to add a suitable test case. I've been looking at /opt/stack/nova/nova/tests/compute/test_compute_api.py running test_create_quota_exceeded_messages under the

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

2013-10-20 Thread Boris Pavlovic
Hi Sean, Honestly, there has been so much work done in Tempest with the stress tests and the scenario tests in this release, and a large growing community around those, that it doesn't make any sense to me that you put item #3 as a non Tempest thing. I really don't like to copy paste

[openstack-dev] [GIT] Reset a commit in Gerrit

2013-10-20 Thread Floren Llanos
Hello, I'm a newbie contributor in Openstack, and I'm newbie using git and gerrit too. I committed a change to gerrit of two files but one of them is not correct and I must to undo the change (only one of this files). I need to remove this file from gerrit and leave only one. I found in

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

2013-10-20 Thread Tim Bell
From a user perspective, I want that a gate on changes which significantly degrade performance to be rejected. Tempest (and its associated CI) provide a current check on functionality. It is inline and understood. Let's just add a set of benchmarks to Tempest which can validate that improved

Re: [openstack-dev] [GIT] Reset a commit in Gerrit

2013-10-20 Thread Edgar Magana
Floren, Just just need to send a patch to gerrit. From you local repo, do the necessary fixes and be sure everything is just as you want. Then simply run: #git commit -a --amend #git review Thanks, Edgar On 10/20/13 11:26 AM, Floren Llanos florenlla...@gmail.com wrote: Hello, I'm a newbie

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

2013-10-20 Thread Alex Gaynor
There's several issues involved in doing automated regression checking for benchmarks: - You need a platform which is stable. Right now all our CI runs on virtualized instances, and I don't think there's any particular guarantee it'll be the same underlying hardware, further virtualized systems

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

2013-10-20 Thread Robert Collins
On 21 October 2013 07:36, Alex Gaynor alex.gay...@gmail.com wrote: There's several issues involved in doing automated regression checking for benchmarks: - You need a platform which is stable. Right now all our CI runs on virtualized instances, and I don't think there's any particular

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

2013-10-20 Thread Tim Bell
Is it easy ? No... it is hard, whether in an integrated test suite or on its own Can it be solved ? Yes, we have done incredible things with the current QA infrastructure Should it be split off from other testing ? No, I want EVERY commit to have this check. Performance through benchmarking at

Re: [openstack-dev] [GIT] Reset a commit in Gerrit

2013-10-20 Thread Dolph Mathews
On Sun, Oct 20, 2013 at 1:31 PM, Edgar Magana emag...@plumgrid.com wrote: Floren, Just just need to send a patch to gerrit. From you local repo, do the necessary fixes and be sure everything is just as you want. Then simply run: #git commit -a --amend #git review The only gotcha here

Re: [openstack-dev] Fwd: Change in openstack/nova[master]: Moved quota headroom calculations into quota_reserve

2013-10-20 Thread Dan Smith
As I don't see how to keep it in the review, I'll copy to openstack-dev. Just keep making your comments in Gerrit. That way all the discussion related to a specific patch is preserved with proper linkage in case we ever need to go back to it. OK, I think I see what I need to do to do to not

Re: [openstack-dev] Announce of Rally - benchmarking system for OpenStack

2013-10-20 Thread David Kranz
On 10/20/2013 03:03 PM, Robert Collins wrote: On 21 October 2013 07:36, Alex Gaynor alex.gay...@gmail.com wrote: There's several issues involved in doing automated regression checking for benchmarks: - You need a platform which is stable. Right now all our CI runs on virtualized instances, and

[openstack-dev] [Mistral] Agenda for today's meeting at 16.00 UTC

2013-10-20 Thread Renat Akhmerov
Hi, Today we'll have the kick-off Mistral community meeting at 16.00 UTC (#openstack-meeting). Everyone interested in things like TaskFlow, Convection, Workflow as a service or whatever you call it, is very welcome to participate and share your ideas. The agenda can always be found at

Re: [openstack-dev] Change in openstack/nova[master]: Moved quota headroom calculations into quota_reserve

2013-10-20 Thread Michael Bright
Dan, * If some kind soul can guide me on adding unit tests - per my question* * below - then I'll add them, otherwise I'll just complete the fix for now* * and add the tests in a later change.* The change really needs to come with tests. A fix is only good if we know it's a fix :) I pulled