Re: [Openstack] how to decide orders of multiple nic
Hi, It would be important to understand if you are using Quantum or traditional nova networking (e.g., Flat/Vlan Managers). Vish's patch is targeted only for traditional nova-networking, but based on this post by you (https://bugs.launchpad.net/quantum/+bug/1077304) it seems like you may be using Quantum. Nic ordering worked with Quantum in Essex, but a bug was introduced in Folsom that broke it. This bug was recently fixed and merged during early grizzly (thanks to mark mcclain from dreamhost), see: https://bugs.launchpad.net/nova/+bug/1064524 . This bug is tagged with folsom-backport-potential, so the team in charge of stable releases for nova should be pulling it into an upcoming folsom release. Dan On Fri, Nov 9, 2012 at 3:38 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: Pardon me, the bottom line should have said, propose it into trunk and backport it (into folsom/stable). So the answer to your question is yes. Vish On Nov 9, 2012, at 3:22 PM, Yi Sun beyo...@gmail.com wrote: Thanks, will these changes ever be added back to the later releases? Yi ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ 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] [openstack][puppetlabs] : folsom deployment using puppetlabs
Hi all, I want to deploy Folsom (multinode) using Puppetlabs. But I don't know from where to start. Any help will be highly appreciated. Waiting for your responses. Thanks in advance. Regards, Girija___ 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][puppetlabs] : folsom deployment using puppetlabs
This page offers information: http://docs.openstack.org/folsom/openstack-compute/admin/content/openstack-compute-deployment-tool-with-puppet.html The authors have been maintaining that documentation for Folsom. Hope it is helpful. Anne On Sat, Nov 10, 2012 at 7:54 AM, Raja Gajju gajjur...@yahoo.com wrote: Hi all, I want to deploy Folsom (multinode) using Puppetlabs. But I don't know from where to start. Any help will be highly appreciated. Waiting for your responses. Thanks in advance. Regards, Girija ___ 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 :: Folsom] Quantum Network Node setup
Hi Yong, I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you and found that in slide-10: lL3-agent lTo implement floating Ips and other L3 features, such as NAT *lOne per network* Can you elaborate on the comment 'one per network' for L3-Agent. As i understood that the L3-Agent will be only one for complete setup. If we have more than one Network Node then we must install dhcp-agent and L3-Agent in each of these Network Nodes. So, the comment of 'one per network' is like we can have one router/gateway per tenant network. Can you give us your comments on this. bye, balaji On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala patnala...@gmail.comwrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.comwrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.comwrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ 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 ___ 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 :: Folsom] Quantum Network Node setup
Does anyone know how to configure l3 agent and dhcp agent when you have a router for each of your tenants ! i am loosing internet connection each time i don't assign a value to #router_id in the l3_agent.ini file ! Le 10/11/2012 15:06, balaji patnala a écrit : Hi Yong, I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you and found that in slide-10: lL3-agent lTo implement floating Ipsand other L3 features, such as NAT _lOne per network_ Can you elaborate on the comment 'one per network' for L3-Agent. As i understood that the L3-Agent will be only one for complete setup. If we have more than one Network Node then we must install dhcp-agent and L3-Agent in each of these Network Nodes. So, the comment of 'one per network' is like we can have one router/gateway per tenant network. Can you give us your comments on this. bye, balaji On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala patnala...@gmail.com mailto:patnala...@gmail.com wrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on How to achieve the same. Thanking you -- Regards, -- Trinath Somanchi, +91 9866 235 130 tel:%2B91%209866%20235%20130 ___ 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
[Openstack] nova-volumes problem after host reboot
Hi there, I am dealing with this issue for a while, but could not figure out what is going on. After a reboot in the openstack server, I am not able to restart ANY instance that had a nova-volume attached. I tried the DR procedure here without any improvement: http://docs.openstack.org/trunk/openstack-compute/admin/content/nova-disaster-recovery-process.html The error in compute.log is: ERROR nova.compute.manager [req-adacca25-ede8-4c6d-be92-9e8bd8578469 cb302c58bb4245cebc61e132c79c 768bd68a0ac149eb8e300665eb3d3950] [instance: 3cd109e4-addf-4aa8-bf66-b69df6573cea] Cannot reboot instance: iSCSI device not found at /dev/disk/by-path/ip-10.100.200.120:3260-iscsi-iqn.2010-10.org.openstack:volume-20db45cc-c97f-4589-9c9f-ed283b0bc16e-lun-1 This is a very restrictive issue, because I can not simply attach volumes to instances knowing that in a power failure or reboot for maintenance I will have my instances unavailable. Below there is some info about my setup. Any idea? Anything! :) Linux nova-controller 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux rpm -qa |grep openstack openstack-nova-api-2012.2-2.el6.noarch openstack-dashboard-2012.2-3.el6.noarch openstack-utils-2012.2-5.el6.noarch openstack-nova-volume-2012.2-2.el6.noarch openstack-nova-novncproxy-0.4-2.el6.noarch openstack-nova-common-2012.2-2.el6.noarch openstack-nova-console-2012.2-2.el6.noarch openstack-nova-network-2012.2-2.el6.noarch openstack-nova-compute-2012.2-2.el6.noarch openstack-nova-cert-2012.2-2.el6.noarch openstack-nova-2012.2-2.el6.noarch openstack-glance-2012.2-2.el6.noarch python-django-openstack-auth-1.0.2-3.el6.noarch openstack-nova-objectstore-2012.2-2.el6.noarch openstack-nova-scheduler-2012.2-2.el6.noarch openstack-keystone-2012.2-1.el6.noarch -- -- Ronivon C. Costa IBM Certified for Tivoli Software ITIL V3 Certified Tlm: (+351) 96 676 4458 Skype: ronivon.costa BLog ((hosted in my own personal cloud infrastructure): http://cloud0.dyndns-web.com/blog/ ___ 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-volumes problem after host reboot
Hi, Ronivon Costa If you use kvm(libvirt), you can logon the compute node. use virsh list --all list all your no-running vm. For example, there is an instance name instance-0001, you cannot reboot using nova command because it attached block disk. You need do: 1. virsh undefine instance-001 2. goto the instances dir(default /var/lib/nova/instances/instance-0001), run virsh define libvirt.xml 3. then virsh start instance-0001, it can be started now/ 4. then you should update information about instances and volumes table in nova db. I think you already done it. 5. then you can reboot use nova-client or in dashboard. 6. then attach volume to the instance in nova-client or dashboard I hope it can help you. On Saturday, November 10, 2012, Ronivon Costa ronivon.co...@gmail.com wrote: Hi there, I am dealing with this issue for a while, but could not figure out what is going on. After a reboot in the openstack server, I am not able to restart ANY instance that had a nova-volume attached. I tried the DR procedure here without any improvement: http://docs.openstack.org/trunk/openstack-compute/admin/content/nova-disaster-recovery-process.html The error in compute.log is: ERROR nova.compute.manager [req-adacca25-ede8-4c6d-be92-9e8bd8578469 cb302c58bb4245cebc61e132c79c 768bd68a0ac149eb8e300665eb3d3950] [instance: 3cd109e4-addf-4aa8-bf66-b69df6573cea] Cannot reboot instance: iSCSI device not found at /dev/disk/by-path/ip-10.100.200.120:3260-iscsi-iqn.2010-10.org.openstack:volume-20db45cc-c97f-4589-9c9f-ed283b0bc16e-lun-1 This is a very restrictive issue, because I can not simply attach volumes to instances knowing that in a power failure or reboot for maintenance I will have my instances unavailable. Below there is some info about my setup. Any idea? Anything! :) Linux nova-controller 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux rpm -qa |grep openstack openstack-nova-api-2012.2-2.el6.noarch openstack-dashboard-2012.2-3.el6.noarch openstack-utils-2012.2-5.el6.noarch openstack-nova-volume-2012.2-2.el6.noarch openstack-nova-novncproxy-0.4-2.el6.noarch openstack-nova-common-2012.2-2.el6.noarch openstack-nova-console-2012.2-2.el6.noarch openstack-nova-network-2012.2-2.el6.noarch openstack-nova-compute-2012.2-2.el6.noarch openstack-nova-cert-2012.2-2.el6.noarch openstack-nova-2012.2-2.el6.noarch openstack-glance-2012.2-2.el6.noarch python-django-openstack-auth-1.0.2-3.el6.noarch openstack-nova-objectstore-2012.2-2.el6.noarch openstack-nova-scheduler-2012.2-2.el6.noarch openstack-keystone-2012.2-1.el6.noarch -- -- Ronivon C. Costa IBM Certified for Tivoli Software ITIL V3 Certified Tlm: (+351) 96 676 4458 Skype: ronivon.costa BLog ((hosted in my own personal cloud infrastructure): http://cloud0.dyndns-web.com/blog/ -- Blog Site: livemoon.org Twitter: mwjpiero 非淡薄无以明志，非宁静无以致远 ___ 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] Fwd: [keystone] Tokens representing authorization to projects/tenants in the Keystone V3 API
I agree with the vast majority of what Jorge says below. The idea I would like to bounce around is that of the unscoped token. What does it mean conceptually? What is its purpose? Why do we need it? Why should a user be given an unscoped token to exchange at a later time for a scoped token? My view is as follows: i) a user is authenticated and identified, and from this, keystone can see that the user has access to a number of different tenants and services. Keystone creates an unscoped token to encapsulate this. Note that the unscoped token is scoped to the services/tenants available to this user, and consequently it is different for each identified user. Thus it does have some scope i.e. it cannot be swapped for access to any service by any tenant. ii) the user must choose which service/tenant he wishes to activate. This is in line with the principle of least privileges. iii) the user informs keystone which service(s) and tenant(s) he wishes to access and Keystone swaps the unscoped token for one that is scoped to the choice of the user. The issue then becomes, what is the allowable scope of a scoped token? Jorge below believes it should cover multiple services/endpoints/tenants. So one must then ask, what is the difference between the most widely scoped scoped-token and the unscoped token? Surely they will have the same scope won't they? In which case there is no need for both concepts. Comments please regards David On 23/10/2012 06:25, Jorge Williams wrote: Here's my view: On making the default token a configuration option: Like the idea. Disabling the option by default. That's fine too. On scoping a token to a specific endpoint: That's fine, though I believe that that's in the API today. Currently, the way that we scope tokens to endpoints is by validating against the service catalog. I'm not sure if the default middleware checks for this yet, but the Repose middleware does. If you try to use a token in an endpoint that's not in the service catalog the request fails -- well, if the check is turned on. Obviously, I'd like the idea of scoping a single token to multiple tenants / endpoints. I don't like the idea of calling tokens sloppy tokens -- it's confusing. All you have to say is that a token has a scope -- and the scope of the token is the set of resources that the token can provide access to. You can limit the scope of a token to a tenant, to a endpoint, to a set of endpoints or tenants etc -- what limits you place on the scope of an individual token should be up to the operator. Keep in mind that as we start digging into delegation and fine grained authorization (after Grizzly, I'm sure), we'll end up with tokens that have a scope of a subset of resources in a single or multiple tenants. So calling them sloppy now is just confusing. Simply stating that a token has a scope (as I've defined above) should suffice. This is part of the reason why I've never liked the term unscoped token, because an unscoped token does have a scope. It just so happens that the scope of that token is the resource that provides a list of available tenants. -jOrGe W. On Oct 22, 2012, at 9:57 PM, Adam Young wrote: Are you guys +1 ing the original Idea, my suggestion to make it optional, the fact that I think we should call these sloppy tokens? On 10/22/2012 03:40 PM, Jorge Williams wrote: +1 here too. At the end of the day, we'd like the identity API to be flexible enough to allow the token to be scoped in a manner that the deployer sees fit. What the keystone implementation does by default is a different matter -- and disabling multiple tenant scope by default would be fine by me. -jOrGe W. On Oct 21, 2012, at 11:10 AM, Joe Savak wrote: +1. ;) So the issue is that the v2 API contract allows a token to be scoped to multiple tenants. For v3, I'd like to have the same flexibility. I don't see security issues, as if a token were to be sniffed you can change the password of the account using it and use those creds to scope tokens to any tenant you wish. Scope should always be kept as limited as possible. Personally, I don't feel like limiting the tenant list makes much difference. THe more I think about it, the real benefit comes from limiting the endpoints. On Oct 20, 2012, at 21:07, Adam Young ayo...@redhat.com mailto:ayo...@redhat.com wrote: On 10/20/2012 01:50 PM, heckj wrote: I sent this to the openstack-dev list, and thought I'd double post this onto the openstack list at Launchpad for additional feedback. -joe Begin forwarded message: *From: *heckj he...@mac.com mailto:he...@mac.com *Subject: **[openstack-dev] [keystone] Tokens representing authorization to projects/tenants in the Keystone V3 API* *Date: *October 19, 2012 1:51:16 PM PDT *To: *OpenStack Development Mailing List openstack-...@lists.openstack.org mailto:openstack-...@lists.openstack.org *Reply-To: *OpenStack Development Mailing List openstack-...@lists.openstack.org
Re: [Openstack] how to decide orders of multiple nic
Yes, I was talking about quantum. And in that case ,I will close the bug I filed Thx Yi On Nov 10, 2012, at 4:25 AM, Dan Wendlandt d...@nicira.com wrote: Hi, It would be important to understand if you are using Quantum or traditional nova networking (e.g., Flat/Vlan Managers). Vish's patch is targeted only for traditional nova-networking, but based on this post by you (https://bugs.launchpad.net/quantum/+bug/1077304) it seems like you may be using Quantum. Nic ordering worked with Quantum in Essex, but a bug was introduced in Folsom that broke it. This bug was recently fixed and merged during early grizzly (thanks to mark mcclain from dreamhost), see: https://bugs.launchpad.net/nova/+bug/1064524 . This bug is tagged with folsom-backport-potential, so the team in charge of stable releases for nova should be pulling it into an upcoming folsom release. Dan On Fri, Nov 9, 2012 at 3:38 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Pardon me, the bottom line should have said, propose it into trunk and backport it (into folsom/stable). So the answer to your question is yes. Vish On Nov 9, 2012, at 3:22 PM, Yi Sun beyo...@gmail.com wrote: Thanks, will these changes ever be added back to the later releases? Yi ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ 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] how to configure l3_agent when you have Per-tenant Routers !
Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ 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-volumes problem after host reboot
Hi, Had some improvement with this issue. Could boot the instance using virsh, following livemoon advice with small adaptation. However the problem still is not fixed. The volume table was update: mysql -unova -p$PW nova -e update volumes set mountpoint=NULL, attach_status='detached', instance_uuid=0 mysql -unova -p$PW nova -e update volumes set status='available' where status 'error_deleting' Restarted the instance: # virsh undefine instance-0038 error: Refusing to undefine while domain managed save image exists # virsh undefine instance-0038 --managed-save Domain instance-0038 has been undefined # virsh define libvirt.xml Domain instance-0038 defined from libvirt.xml # virsh start instance-0038 Domain instance-0038 started Then I update the database with the new instances status: # mysql -unova -p nova -e update instances set power_state='1',vm_state='active',task_state=NULL where uuid = '7e732b31-2ff8-4cf2-a7ac-f1562070cfb3' I can now connect to the instance. That is a great improvement from my original problem. But there still some serius issues to fix: The instance can not be rebooted (hard reboot). It will not start, with the same errors as before. Also, we can not attach the volume back to the instance: # nova volume-attach 7e732b31-2ff8-4cf2-a7ac-f1562070cfb3 647db677-aa48-4d1e-b875-80be73469cb5 /dev/vdc ERROR: The supplied device path (/dev/vdb) is in use. ... The error is: DevicePathInUse: The supplied device path (/dev/vdb) is in use. /dev/vdb is one ephemeral disk. Why nova is trying to use /dev/vdb when I specified /dev/vdc ? ___ 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] Cloud with Essex for educational purposes
Hi all, Sometime ago, I asked to the list for some help about hardware specification for implementing a little cloud for educational purposes. Finally we've successfully finished the deployment of the cloud with OpenStack Essex and we've documented all the procedure [1], so we are glad to share our experience with you all. There is only an important limitation: all this documentation has been written in our mother tongue (spanish), so It will mainly be useful to the spanish-speaking community inside OpenStack. At this moment we are just beginning to discover with our students the tremendous educational possibilities that the cloud can bring to us, so we would like to thank everyone involved in this great project! Alberto [1] http://www.gonzalonazareno.org/cloud ___ 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] how to configure l3_agent when you have Per-tenant Routers !
Hey there,which guide did you followed ? Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 10 nov. 2012 à 17:57, Skible OpenStack skible.openst...@gmail.com a écrit :Hello,I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible !However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet !please help___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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] Cloud with Essex for educational purposes
Yah I remember you :)thanks a lot for sharing your experienceregards,Raziuqe Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 10 nov. 2012 à 18:29, Alberto Molina Coballes alb.mol...@gmail.com a écrit :Hi all,Sometime ago, I asked to the list for some help about hardwarespecification for implementing a little cloud for educationalpurposes. Finally we've successfully finished the deployment of thecloud with OpenStack Essex and we've documented all the procedure [1],so we are glad to share our experience with you all. There is only animportant limitation: all this documentation has been written in ourmother tongue (spanish), so It will mainly be useful to thespanish-speaking community inside OpenStack.At this moment we are just beginning to discover with our studentsthe tremendous educational possibilities that the cloud can bring tous, so we would like to thank everyone involved in this great project!Alberto[1] http://www.gonzalonazareno.org/cloud___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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] how to configure l3_agent when you have Per-tenant Routers !
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a crit: Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 10 nov. 2012 17:57, Skible OpenStack skible.openst...@gmail.com a crit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ 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] Instances unable to acquire IP address
My instances are never able to get an IP address. udhcpc sends a DHCP Discover, then receives the DHCP Offer for the IP address the instance should be assigned and follows that with a DHCP Request but then is never able to receive the DHCP ACK. I've manually set the interface to the IP address and I am able to ping the DHCP server IP address. I can not ping or access anything past that. I am running OpenStack Folsom on Ubuntu 12.04 via the Cloud Archive PPA. I am using Quantum with Nova for networking, but I have tried Nova Network with FlatDHCP. I currently have one machine that is running all the services but ultimately plan to have multiple machines. Each machine has 2 NICs, eth0 is connected to the same network my desktop sits on. eth1 is on its own physical switch connecting all the OpenStack machines. My test VMs have been CirrOS 0.3. My configs are all visible at: http://dev.gentoo.org/~cardoe/files/openstack/conf/ My logs are all visible at: http://dev.gentoo.org/~cardoe/files/openstack/logs/ The following network interfaces are setup: root@cocacola:~# ip a; ip n 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:24:e8:3e:56:a1 brd ff:ff:ff:ff:ff:ff inet 192.168.200.135/24 brd 192.168.200.255 scope global eth0 inet6 fe80::224:e8ff:fe3e:56a1/64 scope link valid_lft forever preferred_lft forever 3: eth1: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:1b:21:a4:82:f2 brd ff:ff:ff:ff:ff:ff 4: br-int: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 00:1b:21:a4:82:f2 brd ff:ff:ff:ff:ff:ff 5: br-ex: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 1e:ff:8d:5a:f8:4a brd ff:ff:ff:ff:ff:ff 13: phy-br-ex: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 6e:ff:43:02:44:db brd ff:ff:ff:ff:ff:ff inet6 fe80::6cff:43ff:fe02:44db/64 scope link valid_lft forever preferred_lft forever 14: int-br-ex: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether e6:4f:95:3e:d6:1b brd ff:ff:ff:ff:ff:ff inet6 fe80::e44f:95ff:fe3e:d61b/64 scope link valid_lft forever preferred_lft forever 17: vnet0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500 link/ether fe:16:3e:02:d5:75 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe02:d575/64 scope link valid_lft forever preferred_lft forever 192.168.200.180 dev eth0 lladdr 00:22:19:15:30:61 DELAY 192.168.200.1 dev eth0 lladdr 00:15:17:76:a8:91 REACHABLE If any more information would be useful please let me know. Thanks. -- Doug Goldstein ___ 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_grizzly_nova_trunk #65
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/65/Project:precise_grizzly_nova_trunkDate of build:Sat, 10 Nov 2012 03:01:23 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdated scheduler and compute for multiple capabilities.by notsueditnova/tests/compute/test_resource_tracker.pyeditnova/tests/scheduler/test_host_manager.pyaddnova/db/sqlalchemy/migrate_repo/versions/136_add_index_to_instances.pyaddnova/tests/compute/test_multiple_nodes.pyeditnova/scheduler/host_manager.pyeditnova/compute/resource_tracker.pyeditnova/tests/test_hypervapi.pyeditnova/virt/baremetal/driver.pyeditnova/virt/hyperv/driver.pyeditnova/scheduler/driver.pyeditnova/tests/scheduler/test_host_filters.pyeditnova/tests/scheduler/test_least_cost.pyeditnova/compute/manager.pyeditnova/virt/fake.pyeditnova/db/sqlalchemy/models.pyeditnova/virt/vmwareapi/driver.pyeditnova/tests/scheduler/fakes.pyaddnova/db/sqlalchemy/migrate_repo/versions/135_add_node_to_instances.pyeditnova/tests/compute/test_compute.pyeditnova/db/api.pyeditnova/manager.pyeditnova/db/sqlalchemy/api.pyeditnova/virt/driver.pyeditnova/virt/powervm/driver.pyeditnova/virt/xenapi/driver.pyeditnova/scheduler/filter_scheduler.pyeditnova/tests/scheduler/test_filter_scheduler.pyeditnova/virt/libvirt/driver.pyConsole Output[...truncated 31117 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211092302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211092302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211092302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211092302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211092302~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmppZfR3c/novamk-build-deps -i -r -t apt-get -y /tmp/tmppZfR3c/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git201211100302~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211100302~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git201211100302~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211100302~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211100302~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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: raring_grizzly_nova_trunk #67
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/67/Project:raring_grizzly_nova_trunkDate of build:Sat, 10 Nov 2012 03:01:24 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdated scheduler and compute for multiple capabilities.by notsueditnova/virt/driver.pyeditnova/compute/resource_tracker.pyeditnova/tests/scheduler/test_least_cost.pyeditnova/compute/manager.pyeditnova/tests/compute/test_resource_tracker.pyeditnova/db/sqlalchemy/api.pyeditnova/virt/xenapi/driver.pyeditnova/scheduler/driver.pyeditnova/tests/scheduler/test_filter_scheduler.pyeditnova/virt/powervm/driver.pyeditnova/virt/libvirt/driver.pyeditnova/tests/scheduler/fakes.pyeditnova/virt/vmwareapi/driver.pyeditnova/tests/scheduler/test_host_filters.pyeditnova/virt/baremetal/driver.pyeditnova/virt/hyperv/driver.pyeditnova/scheduler/host_manager.pyeditnova/db/api.pyaddnova/db/sqlalchemy/migrate_repo/versions/135_add_node_to_instances.pyeditnova/tests/compute/test_compute.pyaddnova/db/sqlalchemy/migrate_repo/versions/136_add_index_to_instances.pyeditnova/scheduler/filter_scheduler.pyeditnova/db/sqlalchemy/models.pyaddnova/tests/compute/test_multiple_nodes.pyeditnova/manager.pyeditnova/tests/scheduler/test_host_manager.pyeditnova/virt/fake.pyeditnova/tests/test_hypervapi.pyConsole Output[...truncated 32407 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211092302~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211092302~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211092302~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211092302~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211092302~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpGHIrt6/novamk-build-deps -i -r -t apt-get -y /tmp/tmpGHIrt6/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git201211100302~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git201211100302~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git201211100302~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211100302~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git201211100302~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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_grizzly_python-quantumclient_trunk #4
Title: precise_grizzly_python-quantumclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-quantumclient_trunk/4/Project:precise_grizzly_python-quantumclient_trunkDate of build:Sun, 11 Nov 2012 02:01:22 -0500Build duration:3 min 10 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix curl command for PUT and DELETE.by gongysheditquantumclient/common/utils.pyeditquantumclient/client.pyConsole Output[...truncated 2136 lines...]INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_amd64.changes']File "pool/main/p/python-quantumclient/python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_all.deb" is already registered with different checksums!md5 expected: e52f75b41879c219b39140d2f91d05e4, got: e0b881042a26a10b0ca92ba8e9f53b4esha1 expected: 784a8b576b14ab5ffccad7c8fdac4153787a42d5, got: 9f651a614c242cc965c1f2b99ac926258ca27321sha256 expected: 7145fe78b0012f6701acfaac228e070457182284807e6c4841f8777ab4434622, got: 24adbc3cbed5aae050833c009fe2faf2a204567a087728b1aa2efba5cf9csize expected: 41670, got: 41694There have been errors!ERROR:root:Error occurred during package creation/build: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254ERROR:root:Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-quantumclient/precise-grizzly-proposed /tmp/tmpzPFKfx/python-quantumclientmk-build-deps -i -r -t apt-get -y /tmp/tmpzPFKfx/python-quantumclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/quantum/python-quantumclient --forcedch -b -D precise --newversion 1:2.1.7.g57f0e91+git20120201~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [57f0e91] Fix curl command for PUT and DELETE.dch -a [6857c2a] Fixes setup compatibility issue on Windowsdch -a [4ca0365] Adds securitygroup implementationdch -a [855c4a1] Add OpenStack trove classifier for PyPIdch -a [c8e7ed2] Generate bash_completion string so that we can use bash completion.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_amd64.changesTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254Error 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.getcwd(), 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 '['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-grizzly', 'python-quantumclient_2.1.7.g57f0e91+git20120201~precise-0ubuntu1_amd64.changes']' returned non-zero exit status 254Build 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_grizzly_nova_trunk #66
Title: precise_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/66/Project:precise_grizzly_nova_trunkDate of build:Sun, 11 Nov 2012 02:31:22 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix incorrect LOG.error usage in _compare_cpuby darreneditnova/virt/libvirt/driver.pyConsole Output[...truncated 31091 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211100302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211100302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211100302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211100302~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211100302~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly']Pushed up to revision 402.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmp9e16HR/novamk-build-deps -i -r -t apt-get -y /tmp/tmp9e16HR/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --forcedch -b -D precise --newversion 2013.1+git20120232~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git20120232~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A nova_2013.1+git20120232~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git20120232~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git20120232~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly+ [ ! 0 ]+ jenkins-cli build precise_grizzly_deployNo such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild 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
