[Openstack] [OpenStack][Nova] Help with Cloudpipe setup
Hello, I've been trying to set up cloud pipe for OpenStack. I'm running OpenStack Essex on Ubuntu 12.04 with the default packages. I'm following the instructions from [1,2]. When i get to the part of generating certificates to connect to the cloudpipe instance i get this error [3]. Any ideas? [1] http://docs.openstack.org/developer/nova/devref/cloudpipe.html [2] http://docs.openstack.org/essex/openstack-compute/admin/content/cloudpipe-per-project-vpns.html [3] http://paste.openstack.org/show/20735/ -- Cumprimentos / Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Help with Cloudpipe setup
I'd like to add that i'm unable to ping or ssh this instance from any nodes in my setup. Ping and ssh are working on normal instances. On Fri, Sep 7, 2012 at 10:28 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've been trying to set up cloud pipe for OpenStack. I'm running OpenStack Essex on Ubuntu 12.04 with the default packages. I'm following the instructions from [1,2]. When i get to the part of generating certificates to connect to the cloudpipe instance i get this error [3]. Any ideas? [1] http://docs.openstack.org/developer/nova/devref/cloudpipe.html [2] http://docs.openstack.org/essex/openstack-compute/admin/content/cloudpipe-per-project-vpns.html [3] http://paste.openstack.org/show/20735/ -- Cumprimentos / Regards, Leander -- Cumprimentos / Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [ceilometer] Weekly irc meetings time change?
On 09/05/2012 11:51 AM, Nick Barcet wrote: Thanks for asking, I was just about to come up with this. So based on the poll, it seems that the 3-4pm UTC time slot received the most favors with 9 yes, 1 if need be and 1 no. So I guess we'll have to do without Angus, unless we want to do alternating meetings to satisfy both sides of the planet. In the later case we could do one week at 3pm UTC, and the other at 9PM. What would the others think about this? In any case, the next meeting will be tomorrow at 3pm UTC. I'll be sending a formal invite later today. Based on yesterday's meeting, we decided to try alternating time. Since 9PM UTC is taken on thursdays, I am proposing to move it on Wednesdays. If Nobody objects, this means that starting next week we'll have our meetings on: Wednesday at 9PM UTC for odd weeks (September 12, 26) Thursday at 3PM UTC for even weeks (September 20 and October 4) Does this work for everyone? Nick signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [ceilometer] Weekly irc meetings time change?
On 07/09/12 12:39 +0200, Nick Barcet wrote: On 09/05/2012 11:51 AM, Nick Barcet wrote: Thanks for asking, I was just about to come up with this. So based on the poll, it seems that the 3-4pm UTC time slot received the most favors with 9 yes, 1 if need be and 1 no. So I guess we'll have to do without Angus, unless we want to do alternating meetings to satisfy both sides of the planet. In the later case we could do one week at 3pm UTC, and the other at 9PM. What would the others think about this? In any case, the next meeting will be tomorrow at 3pm UTC. I'll be sending a formal invite later today. Based on yesterday's meeting, we decided to try alternating time. Since 9PM UTC is taken on thursdays, I am proposing to move it on Wednesdays. If Nobody objects, this means that starting next week we'll have our meetings on: Wednesday at 9PM UTC for odd weeks (September 12, 26) Cool thanks, good idea! -Angus Thursday at 3PM UTC for even weeks (September 20 and October 4) Does this work for everyone? Nick ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [ceilometer] Weekly irc meetings time change?
On Fri, Sep 7, 2012 at 6:39 AM, Nick Barcet nick.bar...@canonical.comwrote: On 09/05/2012 11:51 AM, Nick Barcet wrote: Thanks for asking, I was just about to come up with this. So based on the poll, it seems that the 3-4pm UTC time slot received the most favors with 9 yes, 1 if need be and 1 no. So I guess we'll have to do without Angus, unless we want to do alternating meetings to satisfy both sides of the planet. In the later case we could do one week at 3pm UTC, and the other at 9PM. What would the others think about this? In any case, the next meeting will be tomorrow at 3pm UTC. I'll be sending a formal invite later today. Based on yesterday's meeting, we decided to try alternating time. Since 9PM UTC is taken on thursdays, I am proposing to move it on Wednesdays. If Nobody objects, this means that starting next week we'll have our meetings on: Wednesday at 9PM UTC for odd weeks (September 12, 26) Thursday at 3PM UTC for even weeks (September 20 and October 4) Does this work for everyone? That time on Wednesday does not work for me. An hour earlier or later would work, if you want to try to stay close to the same time. I am available during the Thursday time slot. Doug ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] issues with fixed_range blocking new instance creation?
On Thu, Sep 6, 2012 at 9:59 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: fixed range is likely fine. I suspect you created your network with a 10.0.0.0/24 though. It might be a bit tricky to switch to a larger range now. You may have to create the rest of your fixed ips manually in the db associated with the same network and then change the cidr entry on the network in the db to 10.0.0.0/16. You also might have to manually destroy the bridges and let nova-network recreate them. That does seem to be the case, if you'd asked me 24hr ago I'd have sworn I never put /24 anywhere but that's the only explaination that fits observed reality. Luckily I haven't quite called the system production yet so I'm taking a maintenance window now, terminating all instances and deleting and recreating network Being able to expand networks more easily would be a nice thing (and in a dhcp controlled world it's not too disruptive as long as you don't go pushing the gateway address around), but best I can tell this is what I've got right now. Thanks, -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Keystone] LDAP integratiom
On 09/06/2012 05:23 PM, Ivan Kolodyazhny wrote: Hi Everyone, Keystone uses python-ldap library to communicate with LDAP server. There are to points where Keystone communicates with LDAP server: keystone.common ldap and keystone.identity.backends.ldap packages. According to the current Keystone architecture it is solid application w/o extensions or plugins. So it will be useful to add python-ldap library to pip-requires file. This dependency is already resolved in the test-requires with comment: 'Optional backend: LDAP'. LDAP support is optional, which is why it is not currently in pip-requires, but I suspect that, as it grows in visibility, it will make sense to include it. It would be helpful to report things like this as a bug and to provide a patch. Best regards, Ivan Kolodyazhny ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [ceilometer] Weekly irc meetings time change?
Does 6PM UTC , Thursdays work?? This slot looks free. From: openstack-bounces+surya_prabhakar=dell@lists.launchpad.net [openstack-bounces+surya_prabhakar=dell@lists.launchpad.net] On Behalf Of Doug Hellmann [doug.hellm...@dreamhost.com] Sent: Friday, September 07, 2012 4:27 PM To: Nick Barcet Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [ceilometer] Weekly irc meetings time change? On Fri, Sep 7, 2012 at 6:39 AM, Nick Barcet nick.bar...@canonical.commailto:nick.bar...@canonical.com wrote: On 09/05/2012 11:51 AM, Nick Barcet wrote: Thanks for asking, I was just about to come up with this. So based on the poll, it seems that the 3-4pm UTC time slot received the most favors with 9 yes, 1 if need be and 1 no. So I guess we'll have to do without Angus, unless we want to do alternating meetings to satisfy both sides of the planet. In the later case we could do one week at 3pm UTC, and the other at 9PM. What would the others think about this? In any case, the next meeting will be tomorrow at 3pm UTC. I'll be sending a formal invite later today. Based on yesterday's meeting, we decided to try alternating time. Since 9PM UTC is taken on thursdays, I am proposing to move it on Wednesdays. If Nobody objects, this means that starting next week we'll have our meetings on: Wednesday at 9PM UTC for odd weeks (September 12, 26) Thursday at 3PM UTC for even weeks (September 20 and October 4) Does this work for everyone? That time on Wednesday does not work for me. An hour earlier or later would work, if you want to try to stay close to the same time. I am available during the Thursday time slot. Doug ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Keystone] LDAP integratiom
pip-requires/test-requires is aimed at developers and is broken up into two files more-so for documentation/organization purposes. IMO, including LDAP as a dependency should be solved by real packaging (e.g. $ apt-get install keystone keystone-ldap). -Dolph On Fri, Sep 7, 2012 at 8:30 AM, Adam Young ayo...@redhat.com wrote: On 09/06/2012 05:23 PM, Ivan Kolodyazhny wrote: Hi Everyone, Keystone uses python-ldap library to communicate with LDAP server. There are to points where Keystone communicates with LDAP server: keystone.common ldap and keystone.identity.backends.ldap packages. According to the current Keystone architecture it is solid application w/o extensions or plugins. So it will be useful to add python-ldap library to pip-requires file. This dependency is already resolved in the test-requires with comment: 'Optional backend: LDAP'. LDAP support is optional, which is why it is not currently in pip-requires, but I suspect that, as it grows in visibility, it will make sense to include it. It would be helpful to report things like this as a bug and to provide a patch. Best regards, Ivan Kolodyazhny ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom
great work thanks; As you said the main missing feature of quantum is the multi-host L3-agent. So I wonder if we can combine nova-network and quantum in a way that nova-network is only used for L3 features? On Thu, Sep 6, 2012 at 6:29 PM, Dan Wendlandt d...@nicira.com wrote: On Thu, Sep 6, 2012 at 12:50 AM, rohon mathieu mathieu.ro...@gmail.com wrote: There is still the security filtering issue (https://blueprints.launchpad.net/quantum/+spec/ovs-security-filtering) which prevent some cloud operator from using OVS. Do you have a workaround to use security group with OVS in folsom? Yes, it merged into Nova yesterday. https://bugs.launchpad.net/quantum/+bug/1039400 We're still working on the new Quantum docs for Folsom, but if you're already familiar with using Quantum + Nova, the key difference is that you use should a libvirt vif-plugging config of LibvirtHybridOVSBridgeDriver, rather than just LibvirtOpenVswitchDriver . Dan On Wed, Sep 5, 2012 at 7:01 PM, Dan Wendlandt d...@nicira.com wrote: On Wed, Sep 5, 2012 at 5:23 AM, andi abes andi.a...@gmail.com wrote: late to the party... but I'll dabble. On Mon, Aug 27, 2012 at 12:21 PM, Chris Wright chr...@sous-sol.org wrote: * rob_hirschf...@dell.com (rob_hirschf...@dell.com) wrote: We've been discussing using Open vSwitch as the basis for non-Quantum Nova Networking deployments in Folsom. While not Quantum, it feels like we're bringing Nova Networking a step closer to some of the core technologies that Quantum uses. To what end? OVS provides much more robust monitoring and operational facilities (e.g sFlow monitoring, better switch table visibility etc). You won't find any disagreement from me about OVS having more advanced capabilities :) It also provides a linux-bridge compatibility layer (ovs-brcompatd [1]), which should work out-of-box with the linux-bridge. As such, switching to using OVS rather than the linux bridge could be done without any code changes to nova, just deployment changes (e.g. ensure that ovs-brcompatd is running to intercept brctl ioctl's - [2]). Using ovs-brcompatd would be possible, though some distros do not package and run it by default and in general it is not the preferred way to run things according to email on the OVS mailing list. For the more adventurous, there could be any number of interesting scenarios enabled by having access to ovs capabilities (e.g. tunneling) Tunneling is definitely a huge benefit of OVS, but you still need someone to setup the tunnels and direct packets into them correctly. That's is exactly what the Quantum OVS plugin does and it is completely open source and freely available, so if people want to experiment with OVS tunneling, using Quantum would seem like the obvious way to do this. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] After expanding fixed ip range instances no longer have network
Hi All, Running Essex on Ununtu 12.04 using multi-host FlatDHCP nova-networking I ran out of IPs on my fixed_ip range so I shut everything (instances, nova-network, nova-compute) down deleted the old network and recreated it with a smaller netmask. This seems to have almost worked. I can start more instances than I previously had fixed ip's, the right ones seem to be being assigned and the mask on the recreated bridge interfaces is correct, but the (ubuntu-cloudimage) instances can't seem to see their NIC's any more, or perhaps aren't getting dhcp properly I'm still trying to force my way in as our instances rather rely on net access for accounts. On the compute node things seem OK the bridge is up and the right things are connected: root@nova-5:/var/log/nova# brctl show br100 bridge name bridge id STP enabled interfaces br100 8000.60eb69d22521 no eth1 vnet0 vnet1 vnet2 I do notice this in iptables: Chain nova-network-POSTROUTING (1 references) target prot opt source destination ACCEPT all -- 10.0.0.0/16 nova-5.csail.mit.edu ACCEPT all -- 10.0.0.0/16 10.128.0.0/24 ACCEPT all -- 10.0.0.0/16 10.0.0.0/16 ! ctstate DNAT my fixed range is 10.0.0.0/16 not sure where 10.128.0.0/24 comes into it as I don't use that network, but can't see that as a problem. Can any one tell me what I've looked? -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] After expanding fixed ip range instances no longer have network
On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx j...@jonproulx.com wrote: Can any one tell me what I've looked? I assumed stopping and restarting nova-network would restart dnsmasq since dnsmasq doesn't have it's own init script, but this seems not to be the case. dnsmasq is listening on an IP the system nolonger has, I'm sure I'll find the answer ot this on my own soon enough but how does one properly restart openstack's dnsmasq (on ubuntu)? It clearly gets started with lots of command line args from nova.conf -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] After expanding fixed ip range instances no longer have network
VERY IMPORTANT FIRST STEP: nova will have moved the ip from eth0 (or whichever device br100 is on) to br100, so if that ip address is needed, you will have to move it back to eth0. If you are connecting over that ip you will have to do it in a script so your connection doesn't drop. Check the ip/netmask by using ip addr show. DISCLAIMER: writing this from memory so check for typos (if br100 was bridged into a device without an ip address you can skip moving the ips but i would still delete br100) On each node running nova-network: ip addr del ip/netmask dev br100 ifconfig br100 down brctl delbr br100 ip addr add ip/netmask dev eth0 Now you should be able to make nova recreate everything for you On each node running nova-network: stop nova-network killall dnsmasq rm /var/lib/nova/networks/* start nova-network Vish On Sep 7, 2012, at 8:33 AM, Jonathan Proulx j...@jonproulx.com wrote: Hi All, Running Essex on Ununtu 12.04 using multi-host FlatDHCP nova-networking I ran out of IPs on my fixed_ip range so I shut everything (instances, nova-network, nova-compute) down deleted the old network and recreated it with a smaller netmask. This seems to have almost worked. I can start more instances than I previously had fixed ip's, the right ones seem to be being assigned and the mask on the recreated bridge interfaces is correct, but the (ubuntu-cloudimage) instances can't seem to see their NIC's any more, or perhaps aren't getting dhcp properly I'm still trying to force my way in as our instances rather rely on net access for accounts. On the compute node things seem OK the bridge is up and the right things are connected: root@nova-5:/var/log/nova# brctl show br100 bridge name bridge id STP enabled interfaces br100 8000.60eb69d22521 no eth1 vnet0 vnet1 vnet2 I do notice this in iptables: Chain nova-network-POSTROUTING (1 references) target prot opt source destination ACCEPT all -- 10.0.0.0/16 nova-5.csail.mit.edu ACCEPT all -- 10.0.0.0/16 10.128.0.0/24 ACCEPT all -- 10.0.0.0/16 10.0.0.0/16 ! ctstate DNAT my fixed range is 10.0.0.0/16 not sure where 10.128.0.0/24 comes into it as I don't use that network, but can't see that as a problem. Can any one tell me what I've looked? -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] After expanding fixed ip range instances no longer have network
On Fri, Sep 07, 2012 at 11:59:20AM -0400, Jonathan Proulx wrote: :On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx j...@jonproulx.com wrote: :dnsmasq is listening on an IP the system nolonger has, I'm sure I'll :find the answer ot this on my own soon enough but how does one :properly restart openstack's dnsmasq (on ubuntu)? It clearly gets :started with lots of command line args from nova.conf For teh record: One way that works is to kill all dnsmasq processes then restart nova-network. Hopefully there's a cleaner way, but I no longer *need* to find it. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Folsom] First Guide to try Folsom Packages into Ubuntu 12.04
Hi Stackers, This week, I've been moving forward with Folsom testing. It seems that I'm not alone in wanting to see what will provide Folsom and what will be the changes for Deployment. I also decided to start a guide (with some scripts) [1] which helps anyone who wants to deploy Folsom Testing Packages [1] into Ubuntu 12.04. Keep in mind my work is still under development, but please fill free to report any problem. At this moment, Networking with Quantum is not working since I've some packaging issues but it should be fixed very soon. Of course, this doc is really far to be ready for full deployment, but it will evolute in the future and I hope everyone will enjoy with it. Thank's to the developers for the great job which has been done, and good testing ! [1] https://github.com/EmilienM/openstack-folsom-guide [2] https://launchpad.net/~openstack-ubuntu-testing/+archive/folsom-trunk-testing Regards, -- Emilien Macchi *System Engineer* *www.stackops.com | *emilien.mac...@stackops.com** *|* skype:emilien.macchi* * http://www.stackops.com * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] After expanding fixed ip range instances no longer have network
If you are sure this is the issue: killall dnsmasq restart nova-network Vish On Sep 7, 2012, at 8:59 AM, Jonathan Proulx j...@jonproulx.com wrote: On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx j...@jonproulx.com wrote: Can any one tell me what I've looked? I assumed stopping and restarting nova-network would restart dnsmasq since dnsmasq doesn't have it's own init script, but this seems not to be the case. dnsmasq is listening on an IP the system nolonger has, I'm sure I'll find the answer ot this on my own soon enough but how does one properly restart openstack's dnsmasq (on ubuntu)? It clearly gets started with lots of command line args from nova.conf -Jon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [HPC] Reminder monthly telecon Sep. 10
Hi, This is a reminder that we'll hold our next monthly HPC telecon this coming Monday, Sep. 10 and 12:00 noon Eastern Time. We'll use webex (details below). The agenda is somewhat open. Our default will be to start the conversation about HPC features that folks are interested in adding to the Grizzly release. If anyone has any other specific agenda items, they're welcome to propose them. I'm unable to attend, so my colleague David Kang will be hosting this meeting. We look forward to talking to you! best, JP John Paul Walters invites you to attend this online meeting. Topic: HPC Monthly Telecon Date: Monday, September 10, 2012 Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) Meeting Number: 927 246 497 Meeting Password: hpcmonthly --- To join the online meeting (Now from mobile devices!) --- 1. Go to https://openstack.webex.com/openstack/j.php?ED=203524102UID=1431607857PW=NYzljOTEwYThjRT=MiMxMQ%3D%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: hpcmonthly 4. Click Join. To view in other time zones or languages, please click the link: https://openstack.webex.com/openstack/j.php?ED=203524102UID=1431607857PW=NYzljOTEwYThjORT=MiMxMQ%3D%3D ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] After expanding fixed ip range instances no longer have network
Thanks Vish, Your directions were correct would have saved me a few hours of floundering had I just started a little later :) particularly the `killall dnsmasq` -Jon On Fri, Sep 07, 2012 at 09:12:52AM -0700, Vishvananda Ishaya wrote: :If you are sure this is the issue: : :killall dnsmasq :restart nova-network : :Vish : :On Sep 7, 2012, at 8:59 AM, Jonathan Proulx j...@jonproulx.com wrote: : : On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx j...@jonproulx.com wrote: : : Can any one tell me what I've looked? : : I assumed stopping and restarting nova-network would restart dnsmasq : since dnsmasq doesn't have it's own init script, but this seems not to : be the case. : : dnsmasq is listening on an IP the system nolonger has, I'm sure I'll : find the answer ot this on my own soon enough but how does one : properly restart openstack's dnsmasq (on ubuntu)? It clearly gets : started with lots of command line args from nova.conf : : -Jon : : ___ : Mailing list: https://launchpad.net/~openstack : Post to : openstack@lists.launchpad.net : Unsubscribe : https://launchpad.net/~openstack : More help : https://help.launchpad.net/ListHelp : ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack-hpc] [HPC] Reminder monthly telecon Sep. 10
All, I have a blue print on proximity scheduler at http://wiki.openstack.org/ProximityScheduler, and would like to get feedback on it. Thanks, Joseph - Original Message - From: John Paul Walters jwalt...@isi.edu To: openstack@lists.launchpad.net Cc: openstack-...@lists.openstack.org Sent: Friday, September 7, 2012 12:12:20 PM Subject: [openstack-hpc] [HPC] Reminder monthly telecon Sep. 10 Hi, This is a reminder that we'll hold our next monthly HPC telecon this coming Monday, Sep. 10 and 12:00 noon Eastern Time. We'll use webex (details below). The agenda is somewhat open. Our default will be to start the conversation about HPC features that folks are interested in adding to the Grizzly release. If anyone has any other specific agenda items, they're welcome to propose them. I'm unable to attend, so my colleague David Kang will be hosting this meeting. We look forward to talking to you! best, JP John Paul Walters invites you to attend this online meeting. Topic: HPC Monthly Telecon Date: Monday, September 10, 2012 Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) Meeting Number: 927 246 497 Meeting Password: hpcmonthly --- To join the online meeting (Now from mobile devices!) --- 1. Go to https://openstack.webex.com/openstack/j.php?ED=203524102UID=1431607857PW=NYzljOTEwYThjRT=MiMxMQ%3D%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: hpcmonthly 4. Click Join. To view in other time zones or languages, please click the link: https://openstack.webex.com/openstack/j.php?ED=203524102UID=1431607857PW=NYzljOTEwYThjORT=MiMxMQ%3D%3D ___ OpenStack-HPC mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom
On Fri, Sep 7, 2012 at 8:36 AM, rohon mathieu mathieu.ro...@gmail.com wrote: great work thanks; As you said the main missing feature of quantum is the multi-host L3-agent. So I wonder if we can combine nova-network and quantum in a way that nova-network is only used for L3 features? I agree that it would be great if there was a simple work around like that, but I think the core of the problem is the multi_host logic in nova-network is closely tied to the IP Address Management (IPAM) logic in nova. Quantum has its own IPAM logic, as it supports more advanced scenarios like overlapping IP addresses on different networks. As a result, I think trying to get the nova-network multi_host logic working with Quantum would be on the same order of difficultly has getting a multi_host equivalent working in Quantum. I don't think its fundamentally hard, we just need to be spending our current Quantum cycles on testing, bug fixing, and documentation and so had to drop this feature for the Folsom release. Dan On Thu, Sep 6, 2012 at 6:29 PM, Dan Wendlandt d...@nicira.com wrote: On Thu, Sep 6, 2012 at 12:50 AM, rohon mathieu mathieu.ro...@gmail.com wrote: There is still the security filtering issue (https://blueprints.launchpad.net/quantum/+spec/ovs-security-filtering) which prevent some cloud operator from using OVS. Do you have a workaround to use security group with OVS in folsom? Yes, it merged into Nova yesterday. https://bugs.launchpad.net/quantum/+bug/1039400 We're still working on the new Quantum docs for Folsom, but if you're already familiar with using Quantum + Nova, the key difference is that you use should a libvirt vif-plugging config of LibvirtHybridOVSBridgeDriver, rather than just LibvirtOpenVswitchDriver . Dan On Wed, Sep 5, 2012 at 7:01 PM, Dan Wendlandt d...@nicira.com wrote: On Wed, Sep 5, 2012 at 5:23 AM, andi abes andi.a...@gmail.com wrote: late to the party... but I'll dabble. On Mon, Aug 27, 2012 at 12:21 PM, Chris Wright chr...@sous-sol.org wrote: * rob_hirschf...@dell.com (rob_hirschf...@dell.com) wrote: We've been discussing using Open vSwitch as the basis for non-Quantum Nova Networking deployments in Folsom. While not Quantum, it feels like we're bringing Nova Networking a step closer to some of the core technologies that Quantum uses. To what end? OVS provides much more robust monitoring and operational facilities (e.g sFlow monitoring, better switch table visibility etc). You won't find any disagreement from me about OVS having more advanced capabilities :) It also provides a linux-bridge compatibility layer (ovs-brcompatd [1]), which should work out-of-box with the linux-bridge. As such, switching to using OVS rather than the linux bridge could be done without any code changes to nova, just deployment changes (e.g. ensure that ovs-brcompatd is running to intercept brctl ioctl's - [2]). Using ovs-brcompatd would be possible, though some distros do not package and run it by default and in general it is not the preferred way to run things according to email on the OVS mailing list. For the more adventurous, there could be any number of interesting scenarios enabled by having access to ovs capabilities (e.g. tunneling) Tunneling is definitely a huge benefit of OVS, but you still need someone to setup the tunnels and direct packets into them correctly. That's is exactly what the Quantum OVS plugin does and it is completely open source and freely available, so if people want to experiment with OVS tunneling, using Quantum would seem like the obvious way to do this. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net
Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom
I'm I correct in believing that the Quantum L3 Abstractions and API Framework (https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api) is the current plan of record for bringing L2toL3 functionality (e.g., VXLAN/NVGRE) into Quantum? Is anyone signed up to do this or has this blueprint been deprecated in favor of some other approach? Thanks, syd -Original Message- From: openstack-bounces+slogan=broadcom@lists.launchpad.net [mailto:openstack-bounces+slogan=broadcom@lists.launchpad.net] On Behalf Of Dan Wendlandt Sent: Friday, September 07, 2012 9:57 AM To: OpenStack Development Mailing List Cc: openstack-operat...@lists.openstack.org; andi abes; openstack@lists.launchpad.net Subject: Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom On Fri, Sep 7, 2012 at 8:36 AM, rohon mathieu mathieu.ro...@gmail.com wrote: great work thanks; As you said the main missing feature of quantum is the multi-host L3-agent. So I wonder if we can combine nova-network and quantum in a way that nova-network is only used for L3 features? I agree that it would be great if there was a simple work around like that, but I think the core of the problem is the multi_host logic in nova-network is closely tied to the IP Address Management (IPAM) logic in nova. Quantum has its own IPAM logic, as it supports more advanced scenarios like overlapping IP addresses on different networks. As a result, I think trying to get the nova-network multi_host logic working with Quantum would be on the same order of difficultly has getting a multi_host equivalent working in Quantum. I don't think its fundamentally hard, we just need to be spending our current Quantum cycles on testing, bug fixing, and documentation and so had to drop this feature for the Folsom release. Dan On Thu, Sep 6, 2012 at 6:29 PM, Dan Wendlandt d...@nicira.com wrote: On Thu, Sep 6, 2012 at 12:50 AM, rohon mathieu mathieu.ro...@gmail.com wrote: There is still the security filtering issue (https://blueprints.launchpad.net/quantum/+spec/ovs-security-filtering) which prevent some cloud operator from using OVS. Do you have a workaround to use security group with OVS in folsom? Yes, it merged into Nova yesterday. https://bugs.launchpad.net/quantum/+bug/1039400 We're still working on the new Quantum docs for Folsom, but if you're already familiar with using Quantum + Nova, the key difference is that you use should a libvirt vif-plugging config of LibvirtHybridOVSBridgeDriver, rather than just LibvirtOpenVswitchDriver . Dan On Wed, Sep 5, 2012 at 7:01 PM, Dan Wendlandt d...@nicira.com wrote: On Wed, Sep 5, 2012 at 5:23 AM, andi abes andi.a...@gmail.com wrote: late to the party... but I'll dabble. On Mon, Aug 27, 2012 at 12:21 PM, Chris Wright chr...@sous-sol.org wrote: * rob_hirschf...@dell.com (rob_hirschf...@dell.com) wrote: We've been discussing using Open vSwitch as the basis for non-Quantum Nova Networking deployments in Folsom. While not Quantum, it feels like we're bringing Nova Networking a step closer to some of the core technologies that Quantum uses. To what end? OVS provides much more robust monitoring and operational facilities (e.g sFlow monitoring, better switch table visibility etc). You won't find any disagreement from me about OVS having more advanced capabilities :) It also provides a linux-bridge compatibility layer (ovs-brcompatd [1]), which should work out-of-box with the linux-bridge. As such, switching to using OVS rather than the linux bridge could be done without any code changes to nova, just deployment changes (e.g. ensure that ovs-brcompatd is running to intercept brctl ioctl's - [2]). Using ovs-brcompatd would be possible, though some distros do not package and run it by default and in general it is not the preferred way to run things according to email on the OVS mailing list. For the more adventurous, there could be any number of interesting scenarios enabled by having access to ovs capabilities (e.g. tunneling) Tunneling is definitely a huge benefit of OVS, but you still need someone to setup the tunnels and direct packets into them correctly. That's is exactly what the Quantum OVS plugin does and it is completely open source and freely available, so if people want to experiment with OVS tunneling, using Quantum would seem like the obvious way to do this. Dan -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ OpenStack-dev mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list openstack-...@lists.openstack.org
Re: [Openstack] [Keystone] LDAP integratiom
On 09/07/2012 10:31 AM, Dolph Mathews wrote: pip-requires/test-requires is aimed at developers and is broken up into two files more-so for documentation/organization purposes. IMO, including LDAP as a dependency should be solved by real packaging (e.g. $ apt-get install keystone keystone-ldap). True, and now that I think of it, I would agree that a pip-requires would not make sense here. Where it would make sense is in devstack. And I have a ticket for that already. https://bugs.launchpad.net/devstack/+bug/1021319 My thinking is that if we add ldap to the supported list, keystone would be configured to use LDAP as the identity store. -Dolph On Fri, Sep 7, 2012 at 8:30 AM, Adam Young ayo...@redhat.com mailto:ayo...@redhat.com wrote: On 09/06/2012 05:23 PM, Ivan Kolodyazhny wrote: Hi Everyone, Keystone uses python-ldap library to communicate with LDAP server. There are to points where Keystone communicates with LDAP server: keystone.common ldap and keystone.identity.backends.ldap packages. According to the current Keystone architecture it is solid application w/o extensions or plugins. So it will be useful to add python-ldap library to pip-requires file. This dependency is already resolved in the test-requires with comment: 'Optional backend: LDAP'. LDAP support is optional, which is why it is not currently in pip-requires, but I suspect that, as it grows in visibility, it will make sense to include it. It would be helpful to report things like this as a bug and to provide a patch. Best regards, Ivan Kolodyazhny ___ Mailing list:https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to :openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help :https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom
Hi Syd, On Fri, Sep 7, 2012 at 10:34 AM, Syd (Sydney) Logan slo...@broadcom.com wrote: I'm I correct in believing that the Quantum L3 Abstractions and API Framework (https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api) is the current plan of record for bringing L2toL3 functionality (e.g., VXLAN/NVGRE) into Quantum? Several Quantum plugins already have L3-over-L3 overlay tunneling capability to provide private L2 tenant networks without VLANs. These plugins include the Open vSwitch plugin (completely free/open source) and the Nicira NVP plugin (commercial). I suspect others will add this capability as well in the future, and in general its a great example of the new network technologies that Quantum enables. The blueprint above is actually complete and merged, but is actually about letting tenants define routers that connect multiple L2 Quantum networks (e.g., to make multi-tier web applications). These routers can also provide access to external networks and implement floating IPs. We're still wrapping up the Folsom Quantum docs, but hopefully this capability will be more clear soon. Thanks, Dan Is anyone signed up to do this or has this blueprint been deprecated in favor of some other approach? Thanks, syd -Original Message- From: openstack-bounces+slogan=broadcom@lists.launchpad.net [mailto:openstack-bounces+slogan=broadcom@lists.launchpad.net] On Behalf Of Dan Wendlandt Sent: Friday, September 07, 2012 9:57 AM To: OpenStack Development Mailing List Cc: openstack-operat...@lists.openstack.org; andi abes; openstack@lists.launchpad.net Subject: Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom On Fri, Sep 7, 2012 at 8:36 AM, rohon mathieu mathieu.ro...@gmail.com wrote: great work thanks; As you said the main missing feature of quantum is the multi-host L3-agent. So I wonder if we can combine nova-network and quantum in a way that nova-network is only used for L3 features? I agree that it would be great if there was a simple work around like that, but I think the core of the problem is the multi_host logic in nova-network is closely tied to the IP Address Management (IPAM) logic in nova. Quantum has its own IPAM logic, as it supports more advanced scenarios like overlapping IP addresses on different networks. As a result, I think trying to get the nova-network multi_host logic working with Quantum would be on the same order of difficultly has getting a multi_host equivalent working in Quantum. I don't think its fundamentally hard, we just need to be spending our current Quantum cycles on testing, bug fixing, and documentation and so had to drop this feature for the Folsom release. Dan On Thu, Sep 6, 2012 at 6:29 PM, Dan Wendlandt d...@nicira.com wrote: On Thu, Sep 6, 2012 at 12:50 AM, rohon mathieu mathieu.ro...@gmail.com wrote: There is still the security filtering issue (https://blueprints.launchpad.net/quantum/+spec/ovs-security-filtering) which prevent some cloud operator from using OVS. Do you have a workaround to use security group with OVS in folsom? Yes, it merged into Nova yesterday. https://bugs.launchpad.net/quantum/+bug/1039400 We're still working on the new Quantum docs for Folsom, but if you're already familiar with using Quantum + Nova, the key difference is that you use should a libvirt vif-plugging config of LibvirtHybridOVSBridgeDriver, rather than just LibvirtOpenVswitchDriver . Dan On Wed, Sep 5, 2012 at 7:01 PM, Dan Wendlandt d...@nicira.com wrote: On Wed, Sep 5, 2012 at 5:23 AM, andi abes andi.a...@gmail.com wrote: late to the party... but I'll dabble. On Mon, Aug 27, 2012 at 12:21 PM, Chris Wright chr...@sous-sol.org wrote: * rob_hirschf...@dell.com (rob_hirschf...@dell.com) wrote: We've been discussing using Open vSwitch as the basis for non-Quantum Nova Networking deployments in Folsom. While not Quantum, it feels like we're bringing Nova Networking a step closer to some of the core technologies that Quantum uses. To what end? OVS provides much more robust monitoring and operational facilities (e.g sFlow monitoring, better switch table visibility etc). You won't find any disagreement from me about OVS having more advanced capabilities :) It also provides a linux-bridge compatibility layer (ovs-brcompatd [1]), which should work out-of-box with the linux-bridge. As such, switching to using OVS rather than the linux bridge could be done without any code changes to nova, just deployment changes (e.g. ensure that ovs-brcompatd is running to intercept brctl ioctl's - [2]). Using ovs-brcompatd would be possible, though some distros do not package and run it by default and in general it is not the preferred way to run things according to email on the OVS mailing list. For the more adventurous, there could be any number of interesting scenarios enabled
Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom
I've observed and studied the OVS L3oL3 tunneling in a multi-node configuration with F3 by packet sniffing VM to VM pings, and have a basic understanding about how the mesh of tunnels comes into existence. Pretty cool. Guessing https://github.com/openstack/quantum/commit/3005d16fe3588bdf4b928e79f640b991df9fae3b is the merge you are referring to that implements the blueprint. There was also a link to a quantum fork created by CISCO that was mentioned in the blueprint, not sure how the code relates (I'm reading both right now). How this ties in with VXLAN and NVGRE (which I guessed from the blueprint both would be plugin instances) is still a bit of a mystery to me, so I look forward to whatever documentation appears. Thanks, syd -Original Message- From: Dan Wendlandt [mailto:d...@nicira.com] Sent: Friday, September 07, 2012 11:11 AM To: Syd (Sydney) Logan Cc: OpenStack Development Mailing List; openstack-operat...@lists.openstack.org; andi abes; openstack@lists.launchpad.net Subject: Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom Hi Syd, On Fri, Sep 7, 2012 at 10:34 AM, Syd (Sydney) Logan slo...@broadcom.com wrote: I'm I correct in believing that the Quantum L3 Abstractions and API Framework (https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api) is the current plan of record for bringing L2toL3 functionality (e.g., VXLAN/NVGRE) into Quantum? Several Quantum plugins already have L3-over-L3 overlay tunneling capability to provide private L2 tenant networks without VLANs. These plugins include the Open vSwitch plugin (completely free/open source) and the Nicira NVP plugin (commercial). I suspect others will add this capability as well in the future, and in general its a great example of the new network technologies that Quantum enables. The blueprint above is actually complete and merged, but is actually about letting tenants define routers that connect multiple L2 Quantum networks (e.g., to make multi-tier web applications). These routers can also provide access to external networks and implement floating IPs. We're still wrapping up the Folsom Quantum docs, but hopefully this capability will be more clear soon. Thanks, Dan Is anyone signed up to do this or has this blueprint been deprecated in favor of some other approach? Thanks, syd -Original Message- From: openstack-bounces+slogan=broadcom@lists.launchpad.net [mailto:openstack-bounces+slogan=broadcom@lists.launchpad.net] On Behalf Of Dan Wendlandt Sent: Friday, September 07, 2012 9:57 AM To: OpenStack Development Mailing List Cc: openstack-operat...@lists.openstack.org; andi abes; openstack@lists.launchpad.net Subject: Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom On Fri, Sep 7, 2012 at 8:36 AM, rohon mathieu mathieu.ro...@gmail.com wrote: great work thanks; As you said the main missing feature of quantum is the multi-host L3-agent. So I wonder if we can combine nova-network and quantum in a way that nova-network is only used for L3 features? I agree that it would be great if there was a simple work around like that, but I think the core of the problem is the multi_host logic in nova-network is closely tied to the IP Address Management (IPAM) logic in nova. Quantum has its own IPAM logic, as it supports more advanced scenarios like overlapping IP addresses on different networks. As a result, I think trying to get the nova-network multi_host logic working with Quantum would be on the same order of difficultly has getting a multi_host equivalent working in Quantum. I don't think its fundamentally hard, we just need to be spending our current Quantum cycles on testing, bug fixing, and documentation and so had to drop this feature for the Folsom release. Dan On Thu, Sep 6, 2012 at 6:29 PM, Dan Wendlandt d...@nicira.com wrote: On Thu, Sep 6, 2012 at 12:50 AM, rohon mathieu mathieu.ro...@gmail.com wrote: There is still the security filtering issue (https://blueprints.launchpad.net/quantum/+spec/ovs-security-filtering) which prevent some cloud operator from using OVS. Do you have a workaround to use security group with OVS in folsom? Yes, it merged into Nova yesterday. https://bugs.launchpad.net/quantum/+bug/1039400 We're still working on the new Quantum docs for Folsom, but if you're already familiar with using Quantum + Nova, the key difference is that you use should a libvirt vif-plugging config of LibvirtHybridOVSBridgeDriver, rather than just LibvirtOpenVswitchDriver . Dan On Wed, Sep 5, 2012 at 7:01 PM, Dan Wendlandt d...@nicira.com wrote: On Wed, Sep 5, 2012 at 5:23 AM, andi abes andi.a...@gmail.com wrote: late to the party... but I'll dabble. On Mon, Aug 27, 2012 at 12:21 PM, Chris Wright chr...@sous-sol.org wrote: * rob_hirschf...@dell.com (rob_hirschf...@dell.com) wrote: We've been discussing using Open vSwitch as the basis for
Re: [Openstack] [openstack-hpc] [HPC] Reminder monthly telecon Sep. 10
I am guessing your intent is to determine the maximum available bandwidth and lowest latency (commonly implemented as least hops) path between hosts. In other platforms there is the notion of Cell, Zone, Row, Rack etc where the host that you are running your workload has the topology encoded in the host meta information itself. In instances where this is not encoded within some sort of meta of the host either shortest path first or constrained shortest path first can be run to determine the network, topology and either distributed to the nodes. The challenge here is that it is really hard to take into account available bandwidth between nodes vs hops. Regards, Colin If you would like to schedule a time to speak with me, please click here to see my calendar and pick a time that works for your schedule. The system will automatically send us both an outlook meeting invite. Colin McNamara (858)208-8105 CCIE #18233,VCP http://www.colinmcnamara.com http://www.linkedin.com/in/colinmcnamara The difficult we do immediately, the impossible just takes a little longer On Sep 7, 2012, at 9:54 AM, Joseph Suh j...@isi.edu wrote: All, I have a blue print on proximity scheduler at http://wiki.openstack.org/ProximityScheduler, and would like to get feedback on it. Thanks, Joseph - Original Message - From: John Paul Walters jwalt...@isi.edu To: openstack@lists.launchpad.net Cc: openstack-...@lists.openstack.org Sent: Friday, September 7, 2012 12:12:20 PM Subject: [openstack-hpc] [HPC] Reminder monthly telecon Sep. 10 Hi, This is a reminder that we'll hold our next monthly HPC telecon this coming Monday, Sep. 10 and 12:00 noon Eastern Time. We'll use webex (details below). The agenda is somewhat open. Our default will be to start the conversation about HPC features that folks are interested in adding to the Grizzly release. If anyone has any other specific agenda items, they're welcome to propose them. I'm unable to attend, so my colleague David Kang will be hosting this meeting. We look forward to talking to you! best, JP John Paul Walters invites you to attend this online meeting. Topic: HPC Monthly Telecon Date: Monday, September 10, 2012 Time: 12:00 pm, Eastern Daylight Time (New York, GMT-04:00) Meeting Number: 927 246 497 Meeting Password: hpcmonthly --- To join the online meeting (Now from mobile devices!) --- 1. Go to https://openstack.webex.com/openstack/j.php?ED=203524102UID=1431607857PW=NYzljOTEwYThjRT=MiMxMQ%3D%3D 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: hpcmonthly 4. Click Join. To view in other time zones or languages, please click the link: https://openstack.webex.com/openstack/j.php?ED=203524102UID=1431607857PW=NYzljOTEwYThjORT=MiMxMQ%3D%3D ___ OpenStack-HPC mailing list openstack-...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-hpc ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] ResourceExtension member_actions question
Is it possible to define a ResourceExtension with a member_action that is
the same for both PUT and GET requests?
For example, let's say I want to add foo as a member action for images. I
tried to define the extension as:
res = extensions.ResourceExtension('images',
MyController(),
member_actions={'foo':'PUT', 'foo' :'GET'},
collection_actions={})
But the mapper only finds my foo method for either the PUT or the GET and
not both (depending on whether the method has declared a body parameter).
I'd like to use the same URL (/images/id/foo) for both PUT and GET
requests.
It works if I define 2 different controllers with the PUT in one and GET in
the other, but it seems like there should be a better way.
Any ideas?
Thanks.
-Paul___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Nova] Instance Type Extra Specs clarifications
Hello all, I am part of the SF south bay meetup group and trying to add a Disk I/O QoS feature which is based on the blkiotune in libvirt. We would like to add flavor types in which we specify the blkiotune in the create flavor screen. After reviewing the discussions and some emails it appears that it makes sense to use the instance_type_extra_specs to add the blkiotune as a key/value pair instead of extending the instance_type table in nova db. I am able to use nova-manage to create instance type and use set_key to add extra specs. The set_key seems to make a direct call to the db to insert the keys whereas the instance_type create takes the more traditional path through the flavomanage controller. However I notice that there is no documentation on how to add the extra_specs keys using a RESTful api. Is this something still in discussions? Thanks Vinay On Tue, Aug 28, 2012 at 8:02 AM, Patrick Petit patrick.michel.pe...@gmail.com wrote: Hi Don, I added a comment in https://bugs.launchpad.net/nova/+bug/1039386regarding your point. Best regards, Patrick 2012/8/24 Dugger, Donald D donald.d.dug...@intel.com Patrick- ** ** We’ve enhanced `nova-manage’ to manipulate the `extra_specs’ entries, c.f. https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value, You can add an `extra_specs’ key/value pair to a flavor with the command: ** ** nova-manage instance_type add_key m1.humongous cpu_type itanium ** ** And delete a key/value pair with the command: ** ** nova-manage instance_type del_key m1.humongous cpu_type** ** ** ** We’re in the process of enhancing `python-novaclient’ and Horizon with similar capabilities and hope to have them ready for the Folsom release.* *** ** ** Currently, there’s no hook to set `extra_specs’ through the `nova.conf’ file, the mechanism is to dynamically add the `extra_specs’ key/values after the administrator has created a flavor. ** ** Currently, the keys are completely free form but there are some issues with that so that should change. Checkout the bug: ** ** https://bugs.launchpad.net/nova/+bug/1039386 ** ** Based upon that bug we need to put some sort of scope on the keys to indicate which components a key applies to. I’m in favor of adding a new column to the `extra_specs’ table that would explicitly set the scope but an alternative would be to encode the scope into the key itself, something like `TrustedFilter:trust’ to indicate that the `trust’ key only applies to the `TrustedFilter’ scheduler component. Feel free to chime in on the BZ entry on how to specify the scope, once we decide on how to deal with this I’ll create a patch to handle it. ** ** -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 ** ** *From:* openstack-bounces+donald.d.dugger=intel@lists.launchpad.net[mailto: openstack-bounces+donald.d.dugger=intel@lists.launchpad.net] *On Behalf Of *Patrick Petit *Sent:* Friday, August 24, 2012 7:13 AM *To:* openstack@lists.launchpad.net (openstack@lists.launchpad.net) *Subject:* [Openstack] [Nova] Instance Type Extra Specs clarifications*** * ** ** Hi, ** ** Could someone give a practical overview of how configuring and using the instance type extra specs extension capability introduced in Folsom? ** ** If how extending an instance type is relatively clear. ** ** Eg.: #nova-manage instance_type set_key --name=my.instancetype --key cpu_arch --value 's== x86_64' ** ** The principles of capability advertising is less clearer. Is it assumed that the key/value pairs are always declared statically as flags in nova.conf of the compute node, or can they be generated dynamically and if so, who would that be? And also, are the keys completely free form strings or strings that are known (reserved) by Nova? ** ** Thanks in advance for clarifying this. ** ** Patrick -- *Give me a place to stand, and I shall move the earth with a lever* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Vinay Bannai Email: vban...@gmail.com Google Voice: 415 938 7576 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Nova] Instance Type Extra Specs clarifications
Well, Yunhong added the API to allow you to update the extra specs table so he should be able to give you the details on that (he's in China, he might not get back to you until next week). Also, make sure you add a scope (where scope is a string followed by a `:' at the beginning of the key) to whatever key you are adding to the extra specs table, otherwise your key will create problems with some of the scheduler filters. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 From: Vinay Bannai [mailto:vban...@gmail.com] Sent: Friday, September 07, 2012 2:20 PM To: Patrick Petit Cc: Dugger, Donald D; openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [Nova] Instance Type Extra Specs clarifications Hello all, I am part of the SF south bay meetup group and trying to add a Disk I/O QoS feature which is based on the blkiotune in libvirt. We would like to add flavor types in which we specify the blkiotune in the create flavor screen. After reviewing the discussions and some emails it appears that it makes sense to use the instance_type_extra_specs to add the blkiotune as a key/value pair instead of extending the instance_type table in nova db. I am able to use nova-manage to create instance type and use set_key to add extra specs. The set_key seems to make a direct call to the db to insert the keys whereas the instance_type create takes the more traditional path through the flavomanage controller. However I notice that there is no documentation on how to add the extra_specs keys using a RESTful api. Is this something still in discussions? Thanks Vinay On Tue, Aug 28, 2012 at 8:02 AM, Patrick Petit patrick.michel.pe...@gmail.commailto:patrick.michel.pe...@gmail.com wrote: Hi Don, I added a comment in https://bugs.launchpad.net/nova/+bug/1039386 regarding your point. Best regards, Patrick 2012/8/24 Dugger, Donald D donald.d.dug...@intel.commailto:donald.d.dug...@intel.com Patrick- We've enhanced `nova-manage' to manipulate the `extra_specs' entries, c.f. https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value, You can add an `extra_specs' key/value pair to a flavor with the command: nova-manage instance_type add_key m1.humongous cpu_type itanium And delete a key/value pair with the command: nova-manage instance_type del_key m1.humongous cpu_type We're in the process of enhancing `python-novaclient' and Horizon with similar capabilities and hope to have them ready for the Folsom release. Currently, there's no hook to set `extra_specs' through the `nova.conf' file, the mechanism is to dynamically add the `extra_specs' key/values after the administrator has created a flavor. Currently, the keys are completely free form but there are some issues with that so that should change. Checkout the bug: https://bugs.launchpad.net/nova/+bug/1039386 Based upon that bug we need to put some sort of scope on the keys to indicate which components a key applies to. I'm in favor of adding a new column to the `extra_specs' table that would explicitly set the scope but an alternative would be to encode the scope into the key itself, something like `TrustedFilter:trust' to indicate that the `trust' key only applies to the `TrustedFilter' scheduler component. Feel free to chime in on the BZ entry on how to specify the scope, once we decide on how to deal with this I'll create a patch to handle it. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786tel:303%2F443-3786 From: openstack-bounces+donald.d.dugger=intel@lists.launchpad.netmailto:intel@lists.launchpad.net [mailto:openstack-bounces+donald.d.duggermailto:openstack-bounces%2Bdonald.d.dugger=intel@lists.launchpad.netmailto:intel@lists.launchpad.net] On Behalf Of Patrick Petit Sent: Friday, August 24, 2012 7:13 AM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: [Openstack] [Nova] Instance Type Extra Specs clarifications Hi, Could someone give a practical overview of how configuring and using the instance type extra specs extension capability introduced in Folsom? If how extending an instance type is relatively clear. Eg.: #nova-manage instance_type set_key --name=my.instancetype --key cpu_arch --value 's== x86_64' The principles of capability advertising is less clearer. Is it assumed that the key/value pairs are always declared statically as flags in nova.conf of the compute node, or can they be generated dynamically and if so, who would that be? And also, are the keys completely free form strings or strings that are known (reserved) by Nova? Thanks in advance for clarifying this. Patrick -- Give me a place to stand, and I shall move the earth with a lever ___ Mailing list:
Re: [Openstack] [Nova] Instance Type Extra Specs clarifications
Yes, the intent has been to use something along the lines of OS-FLV-EXTRA-DATA:disk_qos This leads to another question which I saw being discussed earlier in the email thread. Are we looking for consistency in adding the extra specs? For the most obvious ones it may be worth while to come up with a standardized convention for the names. I was looking at the code and it appears that the extra_specs and the instance_types creation don't have similar code flow. When you delete a instance_type that you created with extra_specs (using the set_key method in nova-manage), the extra_specs are not cleaned up. I would have thought that they should go away too, right? Unless I understood the concept of extra_specs wrong. Vinay On Fri, Sep 7, 2012 at 1:27 PM, Dugger, Donald D donald.d.dug...@intel.comwrote: Well, Yunhong added the API to allow you to update the extra specs table so he should be able to give you the details on that (he’s in China, he might not get back to you until next week). ** ** Also, make sure you add a scope (where scope is a string followed by a `:’ at the beginning of the key) to whatever key you are adding to the extra specs table, otherwise your key will create problems with some of the scheduler filters. ** ** -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 ** ** *From:* Vinay Bannai [mailto:vban...@gmail.com] *Sent:* Friday, September 07, 2012 2:20 PM *To:* Patrick Petit *Cc:* Dugger, Donald D; openstack@lists.launchpad.net ( openstack@lists.launchpad.net) *Subject:* Re: [Openstack] [Nova] Instance Type Extra Specs clarifications ** ** Hello all, ** ** I am part of the SF south bay meetup group and trying to add a Disk I/O QoS feature which is based on the blkiotune in libvirt. We would like to add flavor types in which we specify the blkiotune in the create flavor screen. After reviewing the discussions and some emails it appears that it makes sense to use the instance_type_extra_specs to add the blkiotune as a key/value pair instead of extending the instance_type table in nova db. ** ** I am able to use nova-manage to create instance type and use set_key to add extra specs. The set_key seems to make a direct call to the db to insert the keys whereas the instance_type create takes the more traditional path through the flavomanage controller. However I notice that there is no documentation on how to add the extra_specs keys using a RESTful api. Is this something still in discussions? ** ** Thanks Vinay ** ** On Tue, Aug 28, 2012 at 8:02 AM, Patrick Petit patrick.michel.pe...@gmail.com wrote: Hi Don, ** ** I added a comment in https://bugs.launchpad.net/nova/+bug/1039386regarding your point. Best regards, Patrick 2012/8/24 Dugger, Donald D donald.d.dug...@intel.com ** ** Patrick- We’ve enhanced `nova-manage’ to manipulate the `extra_specs’ entries, c.f. https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value, You can add an `extra_specs’ key/value pair to a flavor with the command: nova-manage instance_type add_key m1.humongous cpu_type itanium And delete a key/value pair with the command: nova-manage instance_type del_key m1.humongous cpu_type*** * We’re in the process of enhancing `python-novaclient’ and Horizon with similar capabilities and hope to have them ready for the Folsom release.** ** Currently, there’s no hook to set `extra_specs’ through the `nova.conf’ file, the mechanism is to dynamically add the `extra_specs’ key/values after the administrator has created a flavor. Currently, the keys are completely free form but there are some issues with that so that should change. Checkout the bug: https://bugs.launchpad.net/nova/+bug/1039386 Based upon that bug we need to put some sort of scope on the keys to indicate which components a key applies to. I’m in favor of adding a new column to the `extra_specs’ table that would explicitly set the scope but an alternative would be to encode the scope into the key itself, something like `TrustedFilter:trust’ to indicate that the `trust’ key only applies to the `TrustedFilter’ scheduler component. Feel free to chime in on the BZ entry on how to specify the scope, once we decide on how to deal with this I’ll create a patch to handle it. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 *From:* openstack-bounces+donald.d.dugger=intel@lists.launchpad.net[mailto: openstack-bounces+donald.d.dugger=intel@lists.launchpad.net] *On Behalf Of *Patrick Petit *Sent:* Friday, August 24, 2012 7:13 AM *To:* openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Re: [Openstack] [Nova] Instance Type Extra Specs clarifications
OS-FLV-EXTRA-DATA: Do you really need a 17 character scope? Your current scope (I assume it's a derivative of OpenStack Flavor Extra Data) is really just redundant info, we know it's extra data for a flavor since we're talking about the `extra_specs' table which is used for flavors. I would think something like `disk:qos' would be sufficient, informative and succinct. Naming consistency: I don't see a real problem here. As long as a unique scope is used then the actual key names can be arbitrary. Since they are limited to a specific scope there is no danger of overlap so no need for a naming convention. Deletion issues: You raise a good point and I think we should address this. When a flavor is deleted any `extra_specs' entries for that flavor should be deleted also. Not a major issue but it would avoid surprises where sale `extra_specs' could be associated with a new flavor that re-used an ID. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 From: Vinay Bannai [mailto:vban...@gmail.com] Sent: Friday, September 07, 2012 2:41 PM To: Dugger, Donald D Cc: Patrick Petit; Jiang, Yunhong; openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [Nova] Instance Type Extra Specs clarifications Yes, the intent has been to use something along the lines of OS-FLV-EXTRA-DATA:disk_qos This leads to another question which I saw being discussed earlier in the email thread. Are we looking for consistency in adding the extra specs? For the most obvious ones it may be worth while to come up with a standardized convention for the names. I was looking at the code and it appears that the extra_specs and the instance_types creation don't have similar code flow. When you delete a instance_type that you created with extra_specs (using the set_key method in nova-manage), the extra_specs are not cleaned up. I would have thought that they should go away too, right? Unless I understood the concept of extra_specs wrong. Vinay On Fri, Sep 7, 2012 at 1:27 PM, Dugger, Donald D donald.d.dug...@intel.commailto:donald.d.dug...@intel.com wrote: Well, Yunhong added the API to allow you to update the extra specs table so he should be able to give you the details on that (he's in China, he might not get back to you until next week). Also, make sure you add a scope (where scope is a string followed by a `:' at the beginning of the key) to whatever key you are adding to the extra specs table, otherwise your key will create problems with some of the scheduler filters. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786tel:303%2F443-3786 From: Vinay Bannai [mailto:vban...@gmail.commailto:vban...@gmail.com] Sent: Friday, September 07, 2012 2:20 PM To: Patrick Petit Cc: Dugger, Donald D; openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: Re: [Openstack] [Nova] Instance Type Extra Specs clarifications Hello all, I am part of the SF south bay meetup group and trying to add a Disk I/O QoS feature which is based on the blkiotune in libvirt. We would like to add flavor types in which we specify the blkiotune in the create flavor screen. After reviewing the discussions and some emails it appears that it makes sense to use the instance_type_extra_specs to add the blkiotune as a key/value pair instead of extending the instance_type table in nova db. I am able to use nova-manage to create instance type and use set_key to add extra specs. The set_key seems to make a direct call to the db to insert the keys whereas the instance_type create takes the more traditional path through the flavomanage controller. However I notice that there is no documentation on how to add the extra_specs keys using a RESTful api. Is this something still in discussions? Thanks Vinay On Tue, Aug 28, 2012 at 8:02 AM, Patrick Petit patrick.michel.pe...@gmail.commailto:patrick.michel.pe...@gmail.com wrote: Hi Don, I added a comment in https://bugs.launchpad.net/nova/+bug/1039386 regarding your point. Best regards, Patrick 2012/8/24 Dugger, Donald D donald.d.dug...@intel.commailto:donald.d.dug...@intel.com Patrick- We've enhanced `nova-manage' to manipulate the `extra_specs' entries, c.f. https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value, You can add an `extra_specs' key/value pair to a flavor with the command: nova-manage instance_type add_key m1.humongous cpu_type itanium And delete a key/value pair with the command: nova-manage instance_type del_key m1.humongous cpu_type We're in the process of enhancing `python-novaclient' and Horizon with similar capabilities and hope to have them ready for the Folsom release. Currently, there's no hook to set `extra_specs' through the `nova.conf' file, the mechanism is to dynamically add the `extra_specs' key/values after the administrator
[Openstack] OpenStack Community Weekly Newsletter (Aug 31-Sep 7)
Highlights of the week New OpenStack Foundation Gold Members: Intel, VmWare, NEC http://lists.openstack.org/pipermail/foundation/2012-September/001091.html Today, the OpenStack Board of Directors approved the applications of three companies wishing to become Gold Members: Intel, NEC and VMware. The factors considered by the Board included a commitment to helping achieve the OpenStack Foundation Mission through demonstrated and potential contribution to the OpenStack community in terms of code, adoption into product roadmaps, adoption as an end user, geographic and industry diversity and community development efforts. Join us to welcome them to the Foundation. Session proposals for the Design Summit now open http://lists.openstack.org/pipermail/openstack-dev/2012-September/001059.html Differently from previous OpenStack Design Summit and Confernece, this time the Design Summit is a specific track in the overall OpenStack Summit event. It is different from other tracks, too. Please make sure to read the full announcement http://lists.openstack.org/pipermail/openstack-dev/2012-September/001059.html and help make this summit the best Design Summit ever. Caimito 0.9 -- WebDAV frontend http://markmail.org/message/hcnyvanvu6pojjxqe http://markmail.org/message/hcnyvanvu6pojjxqfor OpnStack Swift Cloud Storage http://markmail.org/message/hcnyvanvu6pojjxq Caimito is an open source (Apache Software License 2.0) WebDAV,caching, and content management and delivery server frontend for cloud storage. Caimito supports Openstack Swift Storage http://openstack.org/projects/storage/ (Rackspace, Softlayer, etc.), and Amazon S3 http://aws.amazon.com/s3/. Caimito also features a REST API in addition to the Web interface for configuring user access. Caimito is designed with an event-driven and non-blocking architecture for Scalability. Caimito is ideal for Hosting and Reseller environments. Quantum vs. Nova-network in Folsom http://markmail.org/message/kg3arb4gn57cm4rl tl;dr both Quantum and nova-network will be core and fully supported in Folsom. More details from Quantum and Nova PTLs on Quantum vs. Nova-network in Folsom http://markmail.org/message/yvkaq7jubab6vkjh. OpenStack, Xen and XenServer: a match made in Heaven! http://blogs.citrix.com/2012/09/06/openstack-xen-and-xenserver-a-match-made-in-heaven/ A report from John Garbutt, back from XenSummit in San Diego. There was lots of OpenStack related news in many of the CloudOpen sessions, including the announcement from SUSE that they have an OpenStack distribution that supports Xen. XCP-XAPI on Precise http://blogs.citrix.com/2012/09/03/xcp-xapi-on-precise-2/ The Citrix-Openstack team is already running automated OpenStack tests against the stable, and the latest XenServer. As the XCP-XAPI is already available for Ubuntu systems, the team plans to run the tests against that platform as well. Register now for OpenStack Summit in San Diego http://www.openstack.org/summit/san-diego-2012/ The OpenStack room rate is now sold out at the Grand Hyatt. We've set up another room block at the Embassy Suites located across the street. Reserve a room http://embassysuites.hilton.com/en/es/groups/personalized/S/SANDNES-OPE-20121014/index.jhtml?WT.mc_id=POG at the OpenStack rate. Security announcements * Horizon, Open redirect through 'next' parameter (CVE-2012-3540) http://lists.openstack.org/pipermail/openstack-announce/2012-August/26.html * Keystone, Lack of authorization for adding users to tenants (CVE-2012-3542) http://lists.openstack.org/pipermail/openstack-announce/2012-August/25.html Tips and tricks * By Mirantis: Using Software Load Balancing in High Availability (HA) for OpenStack Cloud API Services http://www.mirantis.com/blog/software-high-availability-load-balancing-openstack-cloud-api-servic/ * By Mate Lakat: VHD to OpenStack using a XAPI host plugin http://blogs.citrix.com/2012/09/06/vhd-to-openstack-using-a-xapi-host-plugin/ * By Brian Waldon: Upgrading OpenStack Glance -- Essex to Folsom http://bcwaldon.cc/2012/09/05/glance-essex-to-folsom-upgrade.html * A paper on handling compromised components of IaaS with a specific use case in OpenStack. Definitely worth a read: Aryan TaheriMonfared / Martin G Jaatun -- Handling Compromised Components in an IaaS Cloud Installation http://secstack.org/2012/09/aryan-taherimonfared-martin-g-jaatun-handling-compromised-components-in-an-iaas-cloud-installation/ * By Everett Toews: Getting jclouds and OpenStack work together http://blog.phymata.com/2012/09/04/jclouds-and-openstack/ Upcoming Events * OpenStack Summit http://openstack.org/ Oct 15 -- 18, 2012 -- San Diego, CA Other news * OpenStack election of Project Tech Leads is ongoing. Results will be announced on September 13th
Re: [Openstack] [Folsom] First Guide to try Folsom Packages into Ubuntu 12.04
Thanks for the greate document and script. I have read the document and have some question, queston 1 If eth1 is connected to a Switch, it should be in tagged mode. my question is If the eth1 not connected to Switch, it wolud work? queston 2 Enable IP forwarding : my question is In Essex, seem no need Enable IP forwarding , just because we use quantum, so we need setting Enable IP forwarding, right? On Sat, Sep 8, 2012 at 12:22 AM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi Stackers, This week, I've been moving forward with Folsom testing. It seems that I'm not alone in wanting to see what will provide Folsom and what will be the changes for Deployment. I also decided to start a guide (with some scripts) [1] which helps anyone who wants to deploy Folsom Testing Packages [1] into Ubuntu 12.04. Keep in mind my work is still under development, but please fill free to report any problem. At this moment, Networking with Quantum is not working since I've some packaging issues but it should be fixed very soon. Of course, this doc is really far to be ready for full deployment, but it will evolute in the future and I hope everyone will enjoy with it. Thank's to the developers for the great job which has been done, and good testing ! [1] https://github.com/EmilienM/openstack-folsom-guide [2] https://launchpad.net/~openstack-ubuntu-testing/+archive/folsom-trunk-testinghttps://launchpad.net/%7Eopenstack-ubuntu-testing/+archive/folsom-trunk-testing Regards, -- Emilien Macchi *System Engineer* *www.stackops.com | *emilien.mac...@stackops.com** *|* skype:emilien.macchi* * http://www.stackops.com * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Shake Chen ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #537
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/537/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 05:30:33 -0400Build duration:4 min 1 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix synchronized decorator path cleanupby jogoeditnova/utils.pySimplify setting up test notifierby markmceditnova/tests/compute/test_compute.pyeditnova/tests/test_volume_utils.pyeditnova/tests/compute/test_compute_utils.pyeditnova/tests/test_notifications.pyeditnova/tests/test_volume.pyConsole Output[...truncated 5429 lines...] upstream has moved to setuptools-git, doing so results in missing files from built package.* New upstream release.'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484, line 10472.debcommit: commit failedERROR:root:Error occurred during package creation/build: Command '['debcommit']' returned non-zero exit status 7ERROR:root:Command '['debcommit']' returned non-zero exit status 7INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpTHG1P0/novamk-build-deps -i -r -t apt-get -y /tmp/tmpTHG1P0/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 08f172bb6c14f75171ac29e1c257f9581202b7e9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209070532~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209070532~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [4c9ae2c] Simplify setting up test notifierdch -a [daf0681] Generate a flavorid if needed at flavor creationdch -a [25b0b58] Allow cinder catalog match values to be configureddch -a [27c08dc] Fix synchronized decorator path cleanupdch -a [8dc34a0] Fix and cleanup compute node stat trackingdch -a [64f1916] avoid the buffer cache when copying volumesdch -a [76068c2] Add missing argument to novncproxy websockify calldch -a [aeacea1] Fixing call to hasManagedSaveImagedch -a [e5a0ef4] Fix typo in simple_tenant_usage testsdch -a [6bc7055] Move api_samples to doc dirdch -a [a750438] Get the extension alias to compose the path to save the api samplesdch -a [66f6a9e] Fix creation of iscsi targetsdch -a [eb86e97] Fix xml metadata for volumes extension.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_python-quantumclient_trunk #32
Title: precise_folsom_python-quantumclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_python-quantumclient_trunk/32/Project:precise_folsom_python-quantumclient_trunkDate of build:Fri, 07 Sep 2012 07:00:32 -0400Build duration:2 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40Changesrouter/floating commands support resource reference by nameby motokieditquantumclient/quantum/v2_0/floatingip.pyeditquantumclient/quantum/v2_0/router.pyConsole Output[...truncated 1598 lines...]Install-Time: 29Job: python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1.dscPackage: python-quantumclientPackage-Time: 53Source-Version: 1:2.0.17+git201209070700~precise-0ubuntu1Space: 1068Status: attemptedVersion: 1:2.0.17+git201209070700~precise-0ubuntu1Finished at 20120907-0703Build needed 00:00:53, 1068k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-quantumclient/precise-folsom-proposed /tmp/tmpHY_T3K/python-quantumclientmk-build-deps -i -r -t apt-get -y /tmp/tmpHY_T3K/python-quantumclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 5e2f6fd375ddfab0898d62ba88ce7a7951d6f17e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/python-quantumclient --forcedch -b -D precise --newversion 1:2.0.17+git201209070700~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 1:2.0.17+git201209070700~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [99d7d70] router/floating commands support resource reference by namedch -a [010e715] update error message to make clear that we were search for a name.dch -a [62f5089] *-list command shows only limited fields normally.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-quantumclient_2.0.17+git201209070700~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_swift_trunk #65
Title: precise_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/65/Project:precise_folsom_swift_trunkDate of build:Fri, 07 Sep 2012 13:30:33 -0400Build duration:3 min 54 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix pep8 issues in test_memcached.py.by alex890714edittest/unit/common/test_memcached.pyConsole Output[...truncated 2633 lines...]Package: swiftPackage-Time: 77Source-Version: 1.7.1+git201209071330~precise-0ubuntu1Space: 16828Status: attemptedVersion: 1.7.1+git201209071330~precise-0ubuntu1Finished at 20120907-1334Build needed 00:01:17, 16828k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071330~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071330~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmpmGqeN4/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpmGqeN4/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 73846c2c38728fb32da2b7c8540cffb738b22c42..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.7.1+git201209071330~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 1.7.1+git201209071330~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209071330~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.1+git201209071330~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071330~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071330~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_horizon_trunk #121
Title: precise_folsom_horizon_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_horizon_trunk/121/Project:precise_folsom_horizon_trunkDate of build:Fri, 07 Sep 2012 15:30:33 -0400Build duration:2 min 22 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesUse device name from nova for attach message.by gabrieledithorizon/dashboards/nova/volumes/forms.pyedithorizon/api/nova.pyConsole Output[...truncated 1560 lines...]bzr: ERROR: An error (1) occurred running quilt: Applying patch fix-dashboard-django-wsgi.patchpatching file openstack_dashboard/wsgi/django.wsgiApplying patch fix-dashboard-manage.patchpatching file manage.pyHunk #1 FAILED at 3.1 out of 1 hunk FAILED -- rejects in file manage.pyPatch fix-dashboard-manage.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-213adfd7-284b-43b8-bf15-e1c91b7491f9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-213adfd7-284b-43b8-bf15-e1c91b7491f9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.git archive master --format tar --prefix horizon-2012.2-201209071530/git archive master --format tar --prefix horizon-2012.2-201209071530/git log -n1 --no-merges --pretty=format:%Hgit log 856083a6d4e7ef29b2abdd807f78af9e9634aa67..HEAD --no-merges --pretty=format:[%h] %sbzr branch lp:~openstack-ubuntu-testing/horizon/precise-folsom-proposed horizonbzr merge lp:~openstack-ubuntu-testing/horizon/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209071530~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209071530~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [85b0bfe] Use device name from nova for attach message.dch -a [caf8eaf] Fix BatchAction class incongruence between documentation and code Fixes launchpad bug #1044424dch -a [9c77ce0] Fix PEP8 issues.dch -a [7d2e14c] Add Quantum public network support.debcommitbzr builddeb -S -- -sa -us -ucmk-build-deps -i -r -t apt-get -y /tmp/tmpdE2S99/horizon/debian/controlbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-213adfd7-284b-43b8-bf15-e1c91b7491f9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-213adfd7-284b-43b8-bf15-e1c91b7491f9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #538
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/538/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 16:30:34 -0400Build duration:4 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd a tunable to control how many ARPs are sent.by brian.haleyeditnova/network/linux_net.pyFix EC2 cinder volume creation as an admin user.by dprinceeditnova/api/ec2/cloud.pyFix typo in tgtadm LOG.error() callby markmceditnova/volume/iscsi.pyConsole Output[...truncated 5438 lines...]Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484, line 10475.debcommit: commit failedERROR:root:Error occurred during package creation/build: Command '['debcommit']' returned non-zero exit status 7ERROR:root:Command '['debcommit']' returned non-zero exit status 7INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpodPbdI/novamk-build-deps -i -r -t apt-get -y /tmp/tmpodPbdI/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 08f172bb6c14f75171ac29e1c257f9581202b7e9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209071631~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209071631~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [39b757f] Fix typo in tgtadm LOG.error() calldch -a [4c9ae2c] Simplify setting up test notifierdch -a [daf0681] Generate a flavorid if needed at flavor creationdch -a [a766d81] Fix EC2 cinder volume creation as an admin user.dch -a [25b0b58] Allow cinder catalog match values to be configureddch -a [27c08dc] Fix synchronized decorator path cleanupdch -a [8dc34a0] Fix and cleanup compute node stat trackingdch -a [64f1916] avoid the buffer cache when copying volumesdch -a [76068c2] Add missing argument to novncproxy websockify calldch -a [aeacea1] Fixing call to hasManagedSaveImagedch -a [e5a0ef4] Fix typo in simple_tenant_usage testsdch -a [6bc7055] Move api_samples to doc dirdch -a [e9b05ca] Add a tunable to control how many ARPs are sent.dch -a [a750438] Get the extension alias to compose the path to save the api samplesdch -a [66f6a9e] Fix creation of iscsi targetsdch -a [eb86e97] Fix xml metadata for volumes extension.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #539
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/539/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 17:00:34 -0400Build duration:4 min 36 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImplement paginate query use marker in nova-apiby pengyuweieditnova/tests/test_db_api.pyeditnova/tests/api/openstack/compute/test_servers.pyeditnova/compute/api.pyeditnova/tests/api/openstack/fakes.pyeditnova/db/api.pyeditnova/api/openstack/common.pyeditnova/exception.pyaddnova/common/sqlalchemyutils.pyeditnova/api/openstack/compute/servers.pyeditnova/db/sqlalchemy/api.pyFake requests in tests should be to v1by markmceditnova/tests/api/openstack/volume/test_types.pyeditnova/tests/api/openstack/volume/test_volumes.pyeditnova/tests/api/openstack/volume/test_snapshots.pyUse volume driver specific exceptionsby markmceditnova/tests/test_storwize_svc.pyeditnova/volume/storwize_svc.pyeditnova/volume/manager.pyeditnova/volume/san.pyeditnova/exception.pyeditnova/volume/xensm.pyeditnova/volume/driver.pyeditnova/volume/netapp.pyeditnova/tests/test_volume.pyConsole Output[...truncated 5448 lines...]ERROR:root:Command '['debcommit']' returned non-zero exit status 7INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpMcKnam/novamk-build-deps -i -r -t apt-get -y /tmp/tmpMcKnam/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 08f172bb6c14f75171ac29e1c257f9581202b7e9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209071702~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209071702~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [39b757f] Fix typo in tgtadm LOG.error() calldch -a [3379e82] Use volume driver specific exceptionsdch -a [8c9d9e7] Fake requests in tests should be to v1dch -a [75ca5df] Implement paginate query use marker in nova-apidch -a [4c9ae2c] Simplify setting up test notifierdch -a [daf0681] Generate a flavorid if needed at flavor creationdch -a [a766d81] Fix EC2 cinder volume creation as an admin user.dch -a [25b0b58] Allow cinder catalog match values to be configureddch -a [27c08dc] Fix synchronized decorator path cleanupdch -a [8dc34a0] Fix and cleanup compute node stat trackingdch -a [64f1916] avoid the buffer cache when copying volumesdch -a [76068c2] Add missing argument to novncproxy websockify calldch -a [aeacea1] Fixing call to hasManagedSaveImagedch -a [e5a0ef4] Fix typo in simple_tenant_usage testsdch -a [6bc7055] Move api_samples to doc dirdch -a [e9b05ca] Add a tunable to control how many ARPs are sent.dch -a [a750438] Get the extension alias to compose the path to save the api samplesdch -a [66f6a9e] Fix creation of iscsi targetsdch -a [eb86e97] Fix xml metadata for volumes extension.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_swift_trunk #77
Title: quantal_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/77/Project:quantal_folsom_swift_trunkDate of build:Fri, 07 Sep 2012 18:00:34 -0400Build duration:4 min 15 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesObj replicator cleans up files where part dirs should be.by revieweditswift/obj/replicator.pyedittest/unit/obj/test_replicator.pyFix pep8 issuesby meizu647editswift/obj/auditor.pyConsole Output[...truncated 3526 lines...]python setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log eb5f89ac25fb3edf5d6f0dcc238d4dea4cbbc7c8..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/quantal-folsom --forcedch -b -D quantal --newversion 1.7.1+git201209071800~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1.7.1+git201209071800~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [cde6d59] Fix pep8 issuesdch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [73846c2] fix update_deleted directory creation. bug 1035274dch -a [07b4c21] 1.7.1 version bumpdch -a [341da75] changelog and authors updates for 1.7 releasedch -a [2e16b1f] Update swift.common.db to us swift.cmmn.utils.jsondch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [0bb5d6d] use simplejson to serialize acct/cont resultsdch -a [54a2907] bumped version to 1.7.0 to reflect current dev effortdch -a [7b664c9] Fix PEP8 issues in ./test/unit/common .dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.dch -a [4a2ae2b] Upating proxy-server StatsD logging.dch -a [c509ac2] Added ability to disable fallocatedch -a [2a38a04] Remove the gettext wrapper of server_type.dch -a [9290471] x-newest cleanup code with test. Fixes bug 1037337dch -a [9bda92d] Misc. swift-bench improvements.dch -a [e1ff51c] Do not use pickle for serialization in memcache, but JSONdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209071800~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.7.1+git201209071800~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209071800~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209071800~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #540
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/540/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 18:00:34 -0400Build duration:5 min 9 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesCall driver for attach/detach_volumeby markmceditnova/volume/driver.pyeditnova/volume/manager.pyConsole Output[...truncated 5451 lines...]INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmp2ssO05/novamk-build-deps -i -r -t apt-get -y /tmp/tmp2ssO05/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 08f172bb6c14f75171ac29e1c257f9581202b7e9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209071802~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209071802~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [39b757f] Fix typo in tgtadm LOG.error() calldch -a [6fba30c] Call driver for attach/detach_volumedch -a [3379e82] Use volume driver specific exceptionsdch -a [8c9d9e7] Fake requests in tests should be to v1dch -a [75ca5df] Implement paginate query use marker in nova-apidch -a [4c9ae2c] Simplify setting up test notifierdch -a [daf0681] Generate a flavorid if needed at flavor creationdch -a [a766d81] Fix EC2 cinder volume creation as an admin user.dch -a [25b0b58] Allow cinder catalog match values to be configureddch -a [27c08dc] Fix synchronized decorator path cleanupdch -a [8dc34a0] Fix and cleanup compute node stat trackingdch -a [64f1916] avoid the buffer cache when copying volumesdch -a [76068c2] Add missing argument to novncproxy websockify calldch -a [aeacea1] Fixing call to hasManagedSaveImagedch -a [e5a0ef4] Fix typo in simple_tenant_usage testsdch -a [6bc7055] Move api_samples to doc dirdch -a [e9b05ca] Add a tunable to control how many ARPs are sent.dch -a [a750438] Get the extension alias to compose the path to save the api samplesdch -a [66f6a9e] Fix creation of iscsi targetsdch -a [eb86e97] Fix xml metadata for volumes extension.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_swift_trunk #67
Title: precise_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/67/Project:precise_folsom_swift_trunkDate of build:Fri, 07 Sep 2012 18:30:33 -0400Build duration:3 min 41 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesformat some code according to pep8by meizu647editswift/account/server.pyeditswift/account/reaper.pyeditswift/account/auditor.pyBreakout search_devs add get_builder() for reuseby synedittest/unit/common/ring/test_builder.pyeditbin/swift-ring-buildereditdoc/source/development_saio.rsteditswift/common/ring/builder.pyedittools/test-requireseditswift/common/ring/ring.pyFix pep8 issuesby meizu647editswift/obj/expirer.pyConsole Output[...truncated 2651 lines...]Version: 1.7.1+git201209071830~precise-0ubuntu1Finished at 20120907-1834Build needed 00:01:10, 16856k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071830~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071830~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmpo9E21H/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpo9E21H/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 73846c2c38728fb32da2b7c8540cffb738b22c42..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.7.1+git201209071830~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 1.7.1+git201209071830~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209071830~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.1+git201209071830~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071830~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071830~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #541
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/541/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 18:30:33 -0400Build duration:4 min 18 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesStop lock decorator from leaving tempdirs in testsby vishvanandaeditnova/utils.pyRefer to correct column names in migration 98by bcwaldoneditnova/tests/test_migrations.pyeditnova/db/sqlalchemy/migrate_repo/versions/098_update_volume_attach_time.pyConsole Output[...truncated 5457 lines...]bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmprK23KV/novamk-build-deps -i -r -t apt-get -y /tmp/tmprK23KV/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 08f172bb6c14f75171ac29e1c257f9581202b7e9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209071831~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209071831~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [4c2f6fe] Refer to correct column names in migration 98dch -a [67f7499] Stop lock decorator from leaving tempdirs in testsdch -a [39b757f] Fix typo in tgtadm LOG.error() calldch -a [6fba30c] Call driver for attach/detach_volumedch -a [3379e82] Use volume driver specific exceptionsdch -a [8c9d9e7] Fake requests in tests should be to v1dch -a [75ca5df] Implement paginate query use marker in nova-apidch -a [4c9ae2c] Simplify setting up test notifierdch -a [daf0681] Generate a flavorid if needed at flavor creationdch -a [a766d81] Fix EC2 cinder volume creation as an admin user.dch -a [25b0b58] Allow cinder catalog match values to be configureddch -a [27c08dc] Fix synchronized decorator path cleanupdch -a [8dc34a0] Fix and cleanup compute node stat trackingdch -a [64f1916] avoid the buffer cache when copying volumesdch -a [76068c2] Add missing argument to novncproxy websockify calldch -a [aeacea1] Fixing call to hasManagedSaveImagedch -a [e5a0ef4] Fix typo in simple_tenant_usage testsdch -a [6bc7055] Move api_samples to doc dirdch -a [e9b05ca] Add a tunable to control how many ARPs are sent.dch -a [a750438] Get the extension alias to compose the path to save the api samplesdch -a [66f6a9e] Fix creation of iscsi targetsdch -a [eb86e97] Fix xml metadata for volumes extension.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_swift_trunk #78
Title: quantal_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/78/Project:quantal_folsom_swift_trunkDate of build:Fri, 07 Sep 2012 18:33:47 -0400Build duration:3 min 17 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesformat some code according to pep8by meizu647editswift/account/reaper.pyeditswift/account/server.pyeditswift/account/auditor.pyBreakout search_devs add get_builder() for reuseby synedittools/test-requireseditbin/swift-ring-buildereditswift/common/ring/ring.pyeditdoc/source/development_saio.rsteditswift/common/ring/builder.pyedittest/unit/common/ring/test_builder.pyFix pep8 issuesby meizu647editswift/obj/expirer.pyConsole Output[...truncated 3536 lines...]bzr merge lp:~openstack-ubuntu-testing/swift/quantal-folsom --forcedch -b -D quantal --newversion 1.7.1+git201209071833~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1.7.1+git201209071833~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [73846c2] fix update_deleted directory creation. bug 1035274dch -a [07b4c21] 1.7.1 version bumpdch -a [341da75] changelog and authors updates for 1.7 releasedch -a [2e16b1f] Update swift.common.db to us swift.cmmn.utils.jsondch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [0bb5d6d] use simplejson to serialize acct/cont resultsdch -a [54a2907] bumped version to 1.7.0 to reflect current dev effortdch -a [7b664c9] Fix PEP8 issues in ./test/unit/common .dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.dch -a [4a2ae2b] Upating proxy-server StatsD logging.dch -a [c509ac2] Added ability to disable fallocatedch -a [2a38a04] Remove the gettext wrapper of server_type.dch -a [9290471] x-newest cleanup code with test. Fixes bug 1037337dch -a [9bda92d] Misc. swift-bench improvements.dch -a [e1ff51c] Do not use pickle for serialization in memcache, but JSONdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209071833~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.7.1+git201209071833~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209071833~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209071833~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_swift_trunk #68
Title: precise_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/68/Project:precise_folsom_swift_trunkDate of build:Fri, 07 Sep 2012 19:30:33 -0400Build duration:3 min 8 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesswift constraints are now settable via configby meedittest/unit/common/test_constraints.pyeditswift/common/constraints.pyaddtest/functional/swift_test_client.pyedittest/unit/proxy/test_server.pyedittest/sample.confdeletetest/functional/swift.pyedittest/functional/tests.pyedittest/unit/obj/test_server.pyeditetc/swift.conf-sampleConsole Output[...truncated 2654 lines...]Finished at 20120907-1933Build needed 00:01:10, 16892k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071930~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071930~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmplC4aeM/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmplC4aeM/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 73846c2c38728fb32da2b7c8540cffb738b22c42..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.7.1+git201209071930~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 1.7.1+git201209071930~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209071930~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.1+git201209071930~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071930~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.1+git201209071930~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_swift_trunk #79
Title: quantal_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/79/Project:quantal_folsom_swift_trunkDate of build:Fri, 07 Sep 2012 19:30:33 -0400Build duration:3 min 41 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesswift constraints are now settable via configby meedittest/unit/proxy/test_server.pydeletetest/functional/swift.pyedittest/unit/common/test_constraints.pyaddtest/functional/swift_test_client.pyeditetc/swift.conf-sampleedittest/sample.confeditswift/common/constraints.pyedittest/unit/obj/test_server.pyedittest/functional/tests.pyConsole Output[...truncated 3539 lines...]dch -b -D quantal --newversion 1.7.1+git201209071930~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1.7.1+git201209071930~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [73846c2] fix update_deleted directory creation. bug 1035274dch -a [07b4c21] 1.7.1 version bumpdch -a [341da75] changelog and authors updates for 1.7 releasedch -a [2e16b1f] Update swift.common.db to us swift.cmmn.utils.jsondch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [0bb5d6d] use simplejson to serialize acct/cont resultsdch -a [54a2907] bumped version to 1.7.0 to reflect current dev effortdch -a [7b664c9] Fix PEP8 issues in ./test/unit/common .dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.dch -a [4a2ae2b] Upating proxy-server StatsD logging.dch -a [c509ac2] Added ability to disable fallocatedch -a [2a38a04] Remove the gettext wrapper of server_type.dch -a [9290471] x-newest cleanup code with test. Fixes bug 1037337dch -a [9bda92d] Misc. swift-bench improvements.dch -a [e1ff51c] Do not use pickle for serialization in memcache, but JSONdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209071930~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.7.1+git201209071930~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209071930~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209071930~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #543
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/543/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 20:30:33 -0400Build duration:3 min 14 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesExecute attach_time query earlier in migration 98by bcwaldoneditnova/db/sqlalchemy/migrate_repo/versions/098_update_volume_attach_time.pyConsole Output[...truncated 5463 lines...]python setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 08f172bb6c14f75171ac29e1c257f9581202b7e9..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209072031~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209072031~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [43ae413] Execute attach_time query earlier in migration 98dch -a [6392ad2] xenapi: Make dom0 serialization consistent.dch -a [4c2f6fe] Refer to correct column names in migration 98dch -a [67f7499] Stop lock decorator from leaving tempdirs in testsdch -a [39b757f] Fix typo in tgtadm LOG.error() calldch -a [6fba30c] Call driver for attach/detach_volumedch -a [3379e82] Use volume driver specific exceptionsdch -a [8c9d9e7] Fake requests in tests should be to v1dch -a [75ca5df] Implement paginate query use marker in nova-apidch -a [4c9ae2c] Simplify setting up test notifierdch -a [daf0681] Generate a flavorid if needed at flavor creationdch -a [a766d81] Fix EC2 cinder volume creation as an admin user.dch -a [25b0b58] Allow cinder catalog match values to be configureddch -a [27c08dc] Fix synchronized decorator path cleanupdch -a [8dc34a0] Fix and cleanup compute node stat trackingdch -a [64f1916] avoid the buffer cache when copying volumesdch -a [76068c2] Add missing argument to novncproxy websockify calldch -a [aeacea1] Fixing call to hasManagedSaveImagedch -a [e5a0ef4] Fix typo in simple_tenant_usage testsdch -a [6bc7055] Move api_samples to doc dirdch -a [e9b05ca] Add a tunable to control how many ARPs are sent.dch -a [a750438] Get the extension alias to compose the path to save the api samplesdch -a [66f6a9e] Fix creation of iscsi targetsdch -a [eb86e97] Fix xml metadata for volumes extension.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_nova_trunk #545
Title: precise_folsom_nova_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/545/Project:precise_folsom_nova_trunkDate of build:Fri, 07 Sep 2012 21:52:37 -0400Build duration:12 minBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 20067 lines...]deleting and forgetting pool/main/n/nova/nova-api-os-volume_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-api_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-cert_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-common_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-kvm_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-lxc_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-qemu_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-uml_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xcp_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xen_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-vncproxy_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2012.2+git201209061436~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2012.2+git201209061436~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-folsom']Pushed up to revision 387.INFO:root:Storing current commit for next build: 43ae413da583509448d82ce4ab48f8c8a66a9eb5INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpWZY64e/novamk-build-deps -i -r -t apt-get -y /tmp/tmpWZY64e/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209072153~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209072153~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201209072153~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201209072153~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing nova_2012.2+git201209072153~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom nova_2012.2+git201209072153~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-folsom+ [ ! 0 ]+ jenkins-cli build precise_folsom_deployEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
