Re: [Openstack] Testing NOVA-OVS-Quantum setup
Hi Trinath, Yes, you need to install openvswitch and the quantum-agent on the nova compute nodes as well. Aaron On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- With respect to your document, on Openstack - OVS and Quantum, I'm unable to understand the setup of OVS and Quantum in ESSEX-2/Compute-node machine. In the Document, https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No: 17/19, In the section Open-vSwitch Quantum-agent, Do we need to install OVS and Quantum in the Compute-nodes too..?? . On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I wrote a documentation about installation of Essex with Quantum, OVS in multi-node architecture. You can read it here : https://github.com/EmilienM/doc-openstack Regards On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote: Trinath, I found the following Quantun admin guide was useful for that purpose: http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w Thanks, Joseph (w) 703-248-6160 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Trinath Somanchi trinath.soman...@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, June 20, 2012 7:04:21 AM Subject: [Openstack] Testing NOVA-OVS-Quantum setup Hi- I have installed configured NOVA-OVS-Quantum based setup using the guide provided by openstack and OVS. I have a instance up and running. I'm new to Openstack. Can you any one help me out on the testing/validating on is instance up with OVS and Quantum. 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 -- Emilien Macchi *SysAdmin (Intern)* *www.stackops.com* | emilien.mac...@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. -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list:
Re: [Openstack] Testing NOVA-OVS-Quantum setup
Hi - Thanks a lot for the reply. Following the document ( https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for installing the OVS and Quantum Agent in Compute nodes. *Open-vSwitch Quantum-agent* apt-get install openvswitch-switch quantum-openvswitch-agent modprobe openvswitch_mod echo openvswitch_mod/etc/modules Trinath After following the above steps, I'm unable to find below specified editable file. in /etc there no directory with quantum. Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and change the SQL connection to : sql_connection = mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum Please guide me understand the same, On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.com wrote: Hi Trinath, Yes, you need to install openvswitch and the quantum-agent on the nova compute nodes as well. Aaron On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- With respect to your document, on Openstack - OVS and Quantum, I'm unable to understand the setup of OVS and Quantum in ESSEX-2/Compute-node machine. In the Document, https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No: 17/19, In the section Open-vSwitch Quantum-agent, Do we need to install OVS and Quantum in the Compute-nodes too..?? . On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I wrote a documentation about installation of Essex with Quantum, OVS in multi-node architecture. You can read it here : https://github.com/EmilienM/doc-openstack Regards On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote: Trinath, I found the following Quantun admin guide was useful for that purpose: http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w Thanks, Joseph (w) 703-248-6160 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Trinath Somanchi trinath.soman...@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, June 20, 2012 7:04:21 AM Subject: [Openstack] Testing NOVA-OVS-Quantum setup Hi- I have installed configured NOVA-OVS-Quantum based setup using the guide provided by openstack and OVS. I have a instance up and running. I'm new to Openstack. Can you any one help me out on the testing/validating on is instance up with OVS and Quantum. 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 -- Emilien Macchi *SysAdmin (Intern)* *www.stackops.com* | emilien.mac...@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
Re: [Openstack] Testing NOVA-OVS-Quantum setup
Hi Trinath, I'm not sure off hand, I've never installed the deb package. If you just looking to get up and running quickly I'd recommend following this http://wiki.openstack.org/QuantumDevstack using devstack. Aaron On Fri, Jul 13, 2012 at 2:00 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi - Thanks a lot for the reply. Following the document ( https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for installing the OVS and Quantum Agent in Compute nodes. *Open-vSwitch Quantum-agent* apt-get install openvswitch-switch quantum-openvswitch-agent modprobe openvswitch_mod echo openvswitch_mod/etc/modules Trinath After following the above steps, I'm unable to find below specified editable file. in /etc there no directory with quantum. Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and change the SQL connection to : sql_connection = mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum Please guide me understand the same, On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.com wrote: Hi Trinath, Yes, you need to install openvswitch and the quantum-agent on the nova compute nodes as well. Aaron On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- With respect to your document, on Openstack - OVS and Quantum, I'm unable to understand the setup of OVS and Quantum in ESSEX-2/Compute-node machine. In the Document, https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No: 17/19, In the section Open-vSwitch Quantum-agent, Do we need to install OVS and Quantum in the Compute-nodes too..?? . On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I wrote a documentation about installation of Essex with Quantum, OVS in multi-node architecture. You can read it here : https://github.com/EmilienM/doc-openstack Regards On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote: Trinath, I found the following Quantun admin guide was useful for that purpose: http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w Thanks, Joseph (w) 703-248-6160 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Trinath Somanchi trinath.soman...@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, June 20, 2012 7:04:21 AM Subject: [Openstack] Testing NOVA-OVS-Quantum setup Hi- I have installed configured NOVA-OVS-Quantum based setup using the guide provided by openstack and OVS. I have a instance up and running. I'm new to Openstack. Can you any one help me out on the testing/validating on is instance up with OVS and Quantum. 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 -- Emilien Macchi *SysAdmin (Intern)* *www.stackops.com* | emilien.mac...@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
Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom
Matt Joyce wrote: To certain extent I agree with george's sentiment. Recent example... we're changing tenants to projects in the keystone api. Yes we maintain v2 api compatibility but there will be a cost to users in the confusion of decisions like this. George is right to be calling for openstack to grow up. I agree that technical decisions tend to be weighted towards developers, which is precisely the reason why this thread was open on the mailing-list, rather than silently decided by a PPB. We needed to hear from users in that specific matter, to weigh the real drawbacks of the options we had. That said, being offensive and not constructive actually weakens that party and makes your opinion less likely to prevail. There is no excuse for going beyond the line. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] [metering] General request for feedback on Ceilometer's road-map
Hello everyone, If you have been following this list, you might have seen that the Ceilometer project, while not yet fully functional, has made some great progress over the past three month. The next summit being just a few months away, we thought it would be time to start collecting general feedback on what we should be working on next and how to prioritize this. In order to prime your feedback, we prepared a road-map wiki page [1]. Have a look at it and let us know if you think we should be adding other elements to it. When doing so, please remember that the target of Ceilometer is to collect the metering information for OpenStack components in a single place, not to build a full rating or billing engine. Billing or rating tools should connect to Ceilometer to get their information they need, so feedback on this aspect is welcome (what additional information should we collect? could some evolution of our API[2] make the life of billing or rating engine simpler?) You will certainly notice that we are also tracking, in the same page, some features as bug requests and some of them are targeted for folsom.3: this is what we think needs urgent work _right now_, so if you think you are in a good position to contribute a little code to Ceilometer, feel free to assign yourself to the bug and start contributing patches. If you wonder how to contribute to Ceilometer, we also have put together a little documentation which you can read at [3]. [1] http://wiki.openstack.org/EfficientMetering/RoadMap [2] http://wiki.openstack.org/EfficientMetering/APIProposalv1 [3] http://ceilometer.readthedocs.org Thanks for your help and support, -- Nick Barcet nick.bar...@canonical.com aka: nijaba, nicolas 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] [nova] [cinder] Nova-volume vs. Cinder in Folsom
+1 to Vish's proposal I'd go a step further and suggest adopt this model for such changes going forward. Chris Sent from my iPad On Jul 12, 2012, at 5:40 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: On Jul 12, 2012, at 2:36 PM, David Mortman wrote: On Thu, Jul 12, 2012 at 3:38 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Two thoughts: 1) I think this is the wrong forum to poll operators on their preferences in general 2) We don't yet even have a fully laid out set of requirements and steps for how someone would convert or how hard it will be. Historically (with openstack and software in general), it is _always_ harder to upgrade then we think it will be. I'm an optimist and I think it will be a disaster... Excellent points. Let me make the following proposal: 1) Leave the code in nova-volume for now. 2) Document and test a clear migration path to cinder. 3) Take the working example upgrade to the operators list and ask them for opinions. 4) Decide based on their feedback whether it is acceptable to cut the nova-volume code out for folsom. Vish___ 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] [cinder] Nova-volume vs. Cinder in Folsom
This is exactly the sort of interaction we need between the two perspectives of the OpenStack community. Thanks Chris Sent from my iPad On Jul 12, 2012, at 11:20 PM, Joe Topjian joe.topj...@cybera.ca wrote: Hello, I'm not an OpenStack developer nor any type of developer. I am, however, heavily involved with operations for a few production OpenStack environments. I understand the debate going on and wanted to add an administrator's point of view. For admins, OpenStack is not our job, but a tool we use in our job. It's terribly frustrating when that tool drastically changes every six months. I find Gabriel's reply interesting and sane. I think if it was agreed upon to ensure N+1 compatibility, then OpenStack should adhere to that. The change being discussed involves storage volumes. This is dead serious. If the migration goes awry, there's potential for production data loss. If the badly-migrated OpenStack environment is used to offer services for outside customers, we've just lost data for those customers. It's one of the worst scenarios for admins. If upgrading from one version of OpenStack to the next is too dangerous due to the possibility of getting into situations such as described above, then it needs to be clearly announced. There's a reason why major RHEL releases are maintained in parallel for so long. With regard to Option 1, I understand the benefits of making this change. If Option 1 was chosen, IMO, the best-case scenario would be if the extra work involved with upgrading to Cinder/Folsom was just a schema migration and everything else still worked as it did with Essex. If this were to happen, though, I would spend /weeks/ testing and planning the Folsom upgrade. I'd estimate that my production environments would make it to Folsom 3 months after it was released. But then what major change am I going to have to worry about in another 3 months? Thanks, Joe On Thu, Jul 12, 2012 at 2:48 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: The stated and agreed-upon goal from Essex forward is to make the core OpenStack projects N+1 compatible (e.g. Essex-Folsom, Folsom-Grizzly), and to make the clients capable of talking to every API version forever. Anything standing in the way of that should be considered a release-blocking bug, and should be filed against the appropriate projects. I for one intend to see to that as best I can. That said, there *is* a grey area around “migration” steps like Nova Volume - Cinder. If the migration path is clear, stable, well-documented, uses the same schemas and same APIs… I’d say that *may* still fall into the category of N+1 compatible. It sounds like that’s the idea here, but that we need to thoroughly vet the practicality of that assertion. I don’t think we can decide this without proof that the clean transition is 100% possible. Code isn’t the only thing of value; constructively and respectfully shaping design decisions is great, testing and filing bugs is also fantastic. Profanity and disrespect are not acceptable. Ever. All the best, - Gabriel -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. ___ 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] [nova] [cinder] Nova-volume vs. Cinder in Folsom
Sent from my iPad On Jul 13, 2012, at 12:41 AM, Blake Yeager blake.yea...@gmail.com wrote: snip I am excited to see such passion from the community but we need to make sure that passion is directed in a constructive manner. +1 Chris___ 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] INDIA OpenStack User Group Meetup in DELHI
Hi All, INDIA OpenStack User Group is planning to organise a meetup in DELHI NCR. All those who are interested in attending, presenting or helping to organise. Please reply here or mail me at syedarm...@ymail.com Cheers! Syed Armani ___ 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] [Keystone] Services API
Hi, I'm trying to make an update request (PUT /v2.0/OS-KSADM/services/53ccd2984389495cab439640dc5596d3) and it's returning HTTP 404. The docs also miss the PUT method [1], so I guess if there is a way to update a service through the WS API? Thanks, Antonio. [1] http://docs.rackspace.com/openstack-extensions/auth/OS-KSADM-admin-devguide/content/Service_Operations_OS-KSADM.html -- Antonio Manuel Muñiz Martín Software Developer at klicap - ingeniería del puzle work phone + 34 954 894 322 www.klicap.es | blog.klicap.es ___ 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] Services API
There are no method update_service here [1], so I think update is not possible, am I right? Thanks, Antonio. [1] https://github.com/openstack/keystone/blob/0425fba560e7d68e52f922667972765e64ad17dc/keystone/controllers/services.py 2012/7/13 Antonio Manuel Muñiz Martín amu...@klicap.es: Hi, I'm trying to make an update request (PUT /v2.0/OS-KSADM/services/53ccd2984389495cab439640dc5596d3) and it's returning HTTP 404. The docs also miss the PUT method [1], so I guess if there is a way to update a service through the WS API? Thanks, Antonio. [1] http://docs.rackspace.com/openstack-extensions/auth/OS-KSADM-admin-devguide/content/Service_Operations_OS-KSADM.html -- Antonio Manuel Muñiz Martín Software Developer at klicap - ingeniería del puzle work phone + 34 954 894 322 www.klicap.es | blog.klicap.es -- Antonio Manuel Muñiz Martín Software Developer at klicap - ingeniería del puzle work phone + 34 954 894 322 www.klicap.es | blog.klicap.es ___ 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] Nova-manage service list shows old and new hostname
Hello list, i've this problem, when i run nova-manage service list i get nova-compute server1.site.it nova enabled :-) 2012-07-13 12:15:44 nova-volume server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-network server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-consoleauth server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-scheduler server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-scheduler Ubuntu-1204-precise-64-minimal nova enabled XXX 2012-07-13 12:06:57 nova-certUbuntu-1204-precise-64-minimal nova enabled XXX 2012-07-13 12:06:57 nova-consoleauth Ubuntu-1204-precise-64-minimal nova enabled XXX 2012-07-13 12:06:57 nova-compute Ubuntu-1204-precise-64-minimal nova enabled XXX None nova-network Ubuntu-1204-precise-64-minimal nova enabled XXX 2012-07-13 12:06:57 nova-certserver1.site.it nova enabled :-) 2012-07-13 12:15:51 that's because i installed openstack changing only the hostname with the hostname command and not in /etc/hostname, laters i've changed that and restarted, now i see services from both the old and new host. Is there a way to remove those services from the hostname Ubuntu-1204-precise-64-minimal? Regards Alessandro ___ 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] [cinder] Nova-volume vs. Cinder in Folsom
It would seem that those voting for option 1 do so primarily from a code hygiene and maintenance perspective. If code hygiene were the only issue this would make sense. But for those of us with a production environment going straight from Nova-volumes to a full Cinder deployment is too big a step. From an operational perspective integrating multiple new things at the same time is too high risk. Not only does all of the code have to work together but all of the operational services for standing up a Cinder production service need to be in place and working. This is too risky for people with services in production. I believe we need to have an approach that provides a migration path that will allow systems in production migrate from Nova-volumes in Folsom to a Cinder based production in a reliable and incremental way. From HP’s perspective we need option #2. I think the code maintenance issue can me ameliorated by just freezing the Nova-Volumes code in Folsom. This will incentivize people to move off it, but will allow them to do it in a way that supports production services. Tim From: openstack-bounces+tim.reddin=hp@lists.launchpad.net [mailto:openstack-bounces+tim.reddin=hp@lists.launchpad.net] On Behalf Of Shake Chen Sent: 12 July 2012 01:31 To: Renuka Apte Cc: Openstack (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom option 1. On Thu, Jul 12, 2012 at 7:10 AM, Renuka Apte renuka.a...@citrix.commailto:renuka.a...@citrix.com wrote: It would be great if anyone who is already deploying Openstack, even if in non-production environments, could give cinder a try. For a test environment, it seems easy enough to make the switch using devstack (I have verified this with XenServer, and I believe, John and folks at Rackspace have tried on KVM). Of course, only when more people start trying it will we get a realistic picture. Thanks, Renuka. From: Flavia Missi [mailto:flaviami...@gmail.commailto:flaviami...@gmail.com] Sent: Wednesday, July 11, 2012 12:56 PM To: Renuka Apte Cc: Vishvananda Ishaya; Openstack (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom For me it's +1 to 1, but... Here at Globo.com we're already deploying clouds based on openstack (not in production yet, we have dev and lab), and it's really painful when openstack just forces us to change, I mean, sysadmins are not that happy, so I think it's more polite if we warn them in Folsom, and remove everything next. Maybe this way nobody's going to fear the update. It also make us lose the chain of thought.. you're learning, and suddenly you have to change something for an update, and then you come back to what you we're doing... Anyway... :) Thanks, On Wed, Jul 11, 2012 at 3:09 PM, Renuka Apte renuka.a...@citrix.commailto:renuka.a...@citrix.com wrote: +1 for 1 On 11/07/12 8:26 AM, Vishvananda Ishaya vishvana...@gmail.commailto:vishvana...@gmail.com wrote: Hello Everyone, Now that the PPB has decided to promote Cinder to core for the Folsom release, we need to decide what happens to the existing Nova Volume code. As far as I can see it there are two basic strategies. I'm going to give an overview of each here: Option 1 -- Remove Nova Volume == Process --- * Remove all nova-volume code from the nova project * Leave the existing nova-volume database upgrades and tables in place for Folsom to allow for migration * Provide a simple script in cinder to copy data from the nova database to the cinder database (The schema for the tables in cinder are equivalent to the current nova tables) * Work with package maintainers to provide a package based upgrade from nova-volume packages to cinder packages * Remove the db tables immediately after Folsom Disadvantages - * Forces deployments to go through the process of migrating to cinder if they want to use volumes in the Folsom release Option 2 -- Deprecate Nova Volume = Process --- * Mark the nova-volume code deprecated but leave it in the project for the folsom release * Provide a migration path at folsom * Backport bugfixes to nova-volume throughout the G-cycle * Provide a second migration path at G * Package maintainers can decide when to migrate to cinder Disadvantages - * Extra maintenance effort * More confusion about storage in openstack * More complicated upgrade paths need to be supported Personally I think Option 1 is a much more manageable strategy because the volume code doesn't get a whole lot of attention. I want to keep things simple and clean with one deployment strategy. My opinion is that if we choose option 2 we will be sacrificing significant feature development in G
[Openstack] [Folsom Testing Packages] Feedback
Thank's to Adam Gandelman for the last e-mail about *Folsom Testing Packages * in *Ubuntu* [1]. I would like to share here my feedback and also the Issues I have today with that : - Glance Packaging [2] : Conflict between two packages. - Glance Endpoint does not work with API V2 but works with API V1. If I comment */etc/glance/glance-api-paste.ini* the part about V2, everything works. Maybe it's my bad, I need to understand more what's wrong. Anyway, I did not have this issue with Essex. - Horizon does not work [3] [1] http://www.mail-archive.com/openstack@lists.launchpad.net/msg14298.html [2] https://bugs.launchpad.net/python-glanceclient/+bug/1024281 [3] https://bugs.launchpad.net/horizon/+bug/1024326 Let me know if you have any idea. Regards -- Emilien Macchi *System Engineer* *www.stackops.com* | emilien.mac...@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
[Openstack] Capacity based scheduling: What updated free_ram_mb in Folsom
Hi Folks, I was reviewing a code change to add generic retries for build failures ( https://review.openstack.org/#/c/9540/2 ), and wanted to be sure that it wouldn't invalidate the capacity accounting used by the scheduler. However I've been sitting here for a while working through the Folsom scheduler code trying to understand how the capacity based scheduling now works, and I'm sure I'm missing something obvious but I just can't work out where the free_ram_mb value in the compute_node table gets updated. I can see the database api method to update the values, compute_node_utilization_update(), it doesn't look as if anything in the code ever calls that ? From when I last looked at this / various discussions here and at the design summits I thought the approach was that: - The scheduler would make a call (rather than a cast) to the compute manger, which would then do some verification work, update the DB table whilst in the context of that call, and then start a thread to complete the spawn. The need to go all the way to the compute node as a call was to avoid race conditions from multiple schedulers. (the change I'm looking at is part of a blueprint to avoid such a race, so maybe I imagined the change from cast to call ?) - On a delete, the capacity_notifer (which had to be configured into the list_notifier) would detect the delete message, and decrement the database values. But now I look through the code it looks as if the scheduler is still doing a cast (scheduler/driver), and although I can see the database api call to update the values, compute_node_utilization_update(), it doesn't look as if anything in the code ever calls that ? The ram_filter scheduler seems to use the free_ram_mb value, and that value seems to come from the host_manager in the scheduler which is read from the Database, but I can't for the life of me work out where these values are updated in the Database. The capacity_notifier, which used to decrement values on a VM deletion only (according to the comments the increment was done in the scheduler) seems to have now disappeared altogether in the move of the notifier to openstack/common ? So I'm sure I'm missing some other even more cunning plan on how to keep the values current, but I can't for the life of me work out what it is - can someone fill me in please ? Thanks, Phil ___ 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] Questions about ceilometer
On Thu, Jul 12, 2012 at 9:42 PM, 张家龙 zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to it.
According to the docs of ceilometer,I deploied it in openstack exsse
environment.
While,I cannot start the ceilometer collector and agent.
The follows are my operations.
1.Install openstack nova ,mongodb and ceilometer.
2.configurate nova ,mongodb and ceilometer
The /etc/nova/nova.conf file is here:
http://pastebin.com/sW5d8eRv
Here is the /etc/ceilometer-collector.conf file is here:
http://pastebin.com/u5vH22Lh
And the /etc/mongodb.conf is here:
http://pastebin.com/D5GMkLsb
3.Start openstack nova ,mongodb
4.Then I start the ceilometer-collector
/usr/bin/ceilometer-collector start
While,some errors occurred:
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb storage
engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb storage
engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage.impl_mongodb [-]
connecting to MongoDB on localhost:27017
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
attempting to load notification handler for
ceilometer.collector.compute:instance
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.create.end events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.exists events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.delete.start events
Traceback (most recent call last):
File /usr/lib/python2.6/site-packages/eventlet/hubs/poll.py, line
97, in wait
readers.get(fileno, noop).cb(fileno)
File /usr/lib/python2.6/site-packages/eventlet/greenthread.py,
line 192, in main
result = function(*args, **kwargs)
File /usr/lib/python2.6/site-packages/nova/service.py, line 101,
in run_server
server.start()
File /usr/lib/python2.6/site-packages/nova/service.py, line 162,
in start
self.manager.init_host()
File
/usr/lib/python2.6/site-packages/ceilometer-0-py2.6.egg/ceilometer/collector/manager.py,
line 69, in init_host
topic='%s.info' % flags.FLAGS.notification_topics[0],
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 867,
in __getattr__
return self._substitute(self._get(name))
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1070,
in _get
info = self._get_opt_info(name, group)
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1161,
in _get_opt_info
raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: notification_topics
Removing descriptor: 12
If anyone can help me ? Waiting your reply. Thanks !
It looks like we have a problem with the way we are loading nova's settings
under Essex. I know some of the flags and cfg code was moved around and
changed between Essex and Folsom as part of it moved into openstack-common.
Julien, you're more familiar with Essex than I am, do you have any ideas
about this problem?
Doug
**
--
Best Regards
ZhangJialong
**
** **
___
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] Questions about ceilometer
On Fri, Jul 13, 2012 at 10:04 AM, Doug Hellmann doug.hellm...@dreamhost.com
wrote:
On Thu, Jul 12, 2012 at 9:42 PM, 张家龙 zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to it.
According to the docs of ceilometer,I deploied it in openstack exsse
environment.
While,I cannot start the ceilometer collector and agent.
The follows are my operations.
1.Install openstack nova ,mongodb and ceilometer.
2.configurate nova ,mongodb and ceilometer
The /etc/nova/nova.conf file is here:
http://pastebin.com/sW5d8eRv
Here is the /etc/ceilometer-collector.conf file is here:
http://pastebin.com/u5vH22Lh
And the /etc/mongodb.conf is here:
http://pastebin.com/D5GMkLsb
3.Start openstack nova ,mongodb
4.Then I start the ceilometer-collector
/usr/bin/ceilometer-collector start
While,some errors occurred:
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb
storage engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb
storage engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage.impl_mongodb [-]
connecting to MongoDB on localhost:27017
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
attempting to load notification handler for
ceilometer.collector.compute:instance
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.create.end events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.exists events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.delete.start events
Traceback (most recent call last):
File /usr/lib/python2.6/site-packages/eventlet/hubs/poll.py, line
97, in wait
readers.get(fileno, noop).cb(fileno)
File /usr/lib/python2.6/site-packages/eventlet/greenthread.py,
line 192, in main
result = function(*args, **kwargs)
File /usr/lib/python2.6/site-packages/nova/service.py, line 101,
in run_server
server.start()
File /usr/lib/python2.6/site-packages/nova/service.py, line 162,
in start
self.manager.init_host()
File
/usr/lib/python2.6/site-packages/ceilometer-0-py2.6.egg/ceilometer/collector/manager.py,
line 69, in init_host
topic='%s.info' % flags.FLAGS.notification_topics[0],
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 867,
in __getattr__
return self._substitute(self._get(name))
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1070,
in _get
info = self._get_opt_info(name, group)
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1161,
in _get_opt_info
raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: notification_topics
Removing descriptor: 12
If anyone can help me ? Waiting your reply. Thanks !
It looks like we have a problem with the way we are loading nova's
settings under Essex. I know some of the flags and cfg code was moved
around and changed between Essex and Folsom as part of it moved into
openstack-common. Julien, you're more familiar with Essex than I am, do you
have any ideas about this problem?
I think I left out a configuration step in the instructions at
http://ceilometer.readthedocs.org/en/latest/install.html.
Did you configure your system to use the Rabbit notifier?
Doug
Doug
**
--
Best Regards
ZhangJialong
**
** **
___
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] Questions about ceilometer
Dear Doug,
I`m use Qpid instead of Rabbit .
Did it cause the error ?
In addition,my nova.conf,mongodb.conf and ceilometer-collector.conf are
here:
http://pastebin.com/sW5d8eRv
http://pastebin.com/D5GMkLsb
http://pastebin.com/u5vH22Lh
Were there some errors in my config files?
Waiting your reply. Thanks.
--
Best Regards
ZhangJialong
-- Original --
From: Doug Hellmanndoug.hellm...@dreamhost.com;
Date: Fri, Jul 13, 2012 11:28 PM
To: ??zhan...@awcloud.com; Julien Danjoujul...@danjou.info;
Cc: openstackopenstack@lists.launchpad.net;
Subject: Re: [Openstack] Questions about ceilometer
On Fri, Jul 13, 2012 at 10:04 AM, Doug Hellmann doug.hellm...@dreamhost.com
wrote:
On Thu, Jul 12, 2012 at 9:42 PM, ?? zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to it.
According to the docs of ceilometer,I deploied it in openstack exsse
environment.
While,I cannot start the ceilometer collector and agent.
The follows are my operations.
1.Install openstack nova ,mongodb and ceilometer.
2.configurate nova ,mongodb and ceilometer
The /etc/nova/nova.conf file is here:
http://pastebin.com/sW5d8eRv
Here is the /etc/ceilometer-collector.conf file is here:
http://pastebin.com/u5vH22Lh
And the /etc/mongodb.conf is here:
http://pastebin.com/D5GMkLsb
3.Start openstack nova ,mongodb
4.Then I start the ceilometer-collector
/usr/bin/ceilometer-collector start
While,some errors occurred:
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb storage
engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb storage
engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage.impl_mongodb [-] connecting to
MongoDB on localhost:27017
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-] attempting to
load notification handler for ceilometer.collector.compute:instance
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-] subscribing
instance handler to compute.instance.create.end events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-] subscribing
instance handler to compute.instance.exists events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-] subscribing
instance handler to compute.instance.delete.start events
Traceback (most recent call last):
File /usr/lib/python2.6/site-packages/eventlet/hubs/poll.py, line 97,
in wait
readers.get(fileno, noop).cb(fileno)
File /usr/lib/python2.6/site-packages/eventlet/greenthread.py, line
192, in main
result = function(*args, **kwargs)
File /usr/lib/python2.6/site-packages/nova/service.py, line 101, in
run_server
server.start()
File /usr/lib/python2.6/site-packages/nova/service.py, line 162, in
start
self.manager.init_host()
File
/usr/lib/python2.6/site-packages/ceilometer-0-py2.6.egg/ceilometer/collector/manager.py,
line 69, in init_host
topic='%s.info' % flags.FLAGS.notification_topics[0],
File /usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py,
line 867, in __getattr__
return self._substitute(self._get(name))
File /usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py,
line 1070, in _get
info = self._get_opt_info(name, group)
File /usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py,
line 1161, in _get_opt_info
raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: notification_topics
Removing descriptor: 12
If anyone can help me ? Waiting your reply. Thanks !
It looks like we have a problem with the way we are loading nova's settings
under Essex. I know some of the flags and cfg code was moved around and changed
between Essex and Folsom as part of it moved into openstack-common. Julien,
you're more familiar with Essex than I am, do you have any ideas about this
problem?
I think I left out a configuration step in the instructions at
http://ceilometer.readthedocs.org/en/latest/install.html.
Did you configure your system to use the Rabbit notifier?
Doug
Doug
--
Best Regards
ZhangJialong
___
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 :
Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom
On 07/12/2012 03:54 PM, George Reese wrote: This community needs offending. This is your opinion and you're entitled to it but let me assure you that *nobody* here wants to be offended by you. This community is made of smart people that deserve respect: stop offending them, now. Make your point in a civil way and try to build consensus around it: that's how this community operates. /stef ___ 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 Cells
Hi Chris, What happens to notifications to other compute servers that are generated as side effect of VM creation a result of using the IPtables firewall driver ? Are they somehow propagated to other Cells, or is there something that keeps all VMs in a particular security group within a Cell ? I looked in the doc and code, but I couldn't see anything that seems to indicate either way. Thanks Phil From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of Chris Behrens Sent: 12 July 2012 20:13 To: Michael J Fork Cc: openstack@lists.launchpad.net; Chris Behrens Subject: Re: [Openstack] Nova Cells Partially developed. This probably isn't much use, but I'll throw it out there: http://comstud.com/cells.pdf ATM the messy code speaks for itself here: https://github.com/comstud/nova/tree/cells_service The basic architecture is: Top level cell with API service has DB, rabbit, and the nova-cells service. API's compute_api_class is overridden to use a new class that shoves every action on an instance into the nova-cells service, telling it which cell to route the request to based on instance['cell_name']. The nova-cells service routes the request to correct cell as requested... 1 hop at a time to the nova-cells service in each child. (Each child runs this new nova-cells service also) If nova-cells service gets a message destined for itself, it'll call the appropriate compute_api call in the child. DB updates are hooked in the child and pushed up to parent cells. New instance creation is slightly different. API will create the DB entry up front... and pass the uuid and all of the same data to the nova-cells service, which will pick a cell for the instance. When it is decided to use the 'current cell' in some child, it will create the DB entry there as well... push a notification upward... and cast the message over to the host scheduler (current scheduler). And the build continues as normal from there (host is picked, and message is casted to the host, etc). There's some code to sync instances in case of lost DB updates.. but there's improvements to make yet.. Sorry... that's very quick. I'm going to be AFK for a couple days.. - Chris On Jul 12, 2012, at 10:39 AM, Michael J Fork wrote: Outside of the Etherpad (http://etherpad.openstack.org/FolsomComputeCells) and presentation referenced there (http://comstud.com/FolsomCells.pdf), are there additional details available on the architecture / implementation of Cells? Thanks. Michael - Michael Fork Cloud Architect, Emerging Solutions IBM Systems Technology Group ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto: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] Questions about ceilometer
On Fri, Jul 13, 2012 at 11:36 AM, 张家龙 zhan...@awcloud.com wrote:
Dear Doug,
I`m use Qpid instead of Rabbit .
Did it cause the error ?
Qpid should work, but I haven't been testing with that so you might have
found a bug.
There are (at least) two differences between your setup and what I normally
use: Essex and qpid. Have you tried running against a folsom install? That
would at least tell us if the qpid configuration is correct or if the
problem is related to Essex.
Doug
In addition,my nova.conf,mongodb.conf and ceilometer-collector.conf
are here:
http://pastebin.com/sW5d8eRv
http://pastebin.com/D5GMkLsb
http://pastebin.com/u5vH22Lh
Were there some errors in my config files?
Waiting your reply. Thanks.
**
--
Best Regards
ZhangJialong
**
-- Original --
*From: * Doug Hellmanndoug.hellm...@dreamhost.com;
*Date: * Fri, Jul 13, 2012 11:28 PM
*To: * 张家龙zhan...@awcloud.com; Julien Danjoujul...@danjou.info; **
*Cc: * openstackopenstack@lists.launchpad.net; **
*Subject: * Re: [Openstack] Questions about ceilometer
On Fri, Jul 13, 2012 at 10:04 AM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:
On Thu, Jul 12, 2012 at 9:42 PM, 张家龙 zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to
it.
According to the docs of ceilometer,I deploied it in openstack exsse
environment.
While,I cannot start the ceilometer collector and agent.
The follows are my operations.
1.Install openstack nova ,mongodb and ceilometer.
2.configurate nova ,mongodb and ceilometer
The /etc/nova/nova.conf file is here:
http://pastebin.com/sW5d8eRv
Here is the /etc/ceilometer-collector.conf file is here:
http://pastebin.com/u5vH22Lh
And the /etc/mongodb.conf is here:
http://pastebin.com/D5GMkLsb
3.Start openstack nova ,mongodb
4.Then I start the ceilometer-collector
/usr/bin/ceilometer-collector start
While,some errors occurred:
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb
storage engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb
storage engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage.impl_mongodb [-]
connecting to MongoDB on localhost:27017
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
attempting to load notification handler for
ceilometer.collector.compute:instance
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.create.end events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.exists events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.delete.start events
Traceback (most recent call last):
File /usr/lib/python2.6/site-packages/eventlet/hubs/poll.py,
line 97, in wait
readers.get(fileno, noop).cb(fileno)
File /usr/lib/python2.6/site-packages/eventlet/greenthread.py,
line 192, in main
result = function(*args, **kwargs)
File /usr/lib/python2.6/site-packages/nova/service.py, line 101,
in run_server
server.start()
File /usr/lib/python2.6/site-packages/nova/service.py, line 162,
in start
self.manager.init_host()
File
/usr/lib/python2.6/site-packages/ceilometer-0-py2.6.egg/ceilometer/collector/manager.py,
line 69, in init_host
topic='%s.info' % flags.FLAGS.notification_topics[0],
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 867,
in __getattr__
return self._substitute(self._get(name))
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1070,
in _get
info = self._get_opt_info(name, group)
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1161,
in _get_opt_info
raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: notification_topics
Removing descriptor: 12
If anyone can help me ? Waiting your reply. Thanks !
It looks like we have a problem with the way we are loading nova's
settings under Essex. I know some of the flags and cfg code was moved
around and changed between Essex and Folsom as part of it moved into
openstack-common. Julien, you're more familiar with Essex than I am, do you
have any ideas about this problem?
I think I left out a configuration step in the instructions at
http://ceilometer.readthedocs.org/en/latest/install.html.
Did you configure your system to use the Rabbit notifier?
Doug
Doug
* *
--
Best Regards
ZhangJialong
* *
* * * *
Re: [Openstack] [metering] Ceilometer PTL Election Process - Call for candidate
On 07/11/2012 02:24 PM, Nick Barcet wrote: Candidates should, before July 24th: 1/ declare themselves on this mailing list It has been so much fun and so rewarding to kick-start this project, that I can't resist to propose myself as Candidate. Not being a true developer places me in an awkward position to run for this function, but I think I have shown, as other have done before, that coding is not the only talent one can contribute and lead with. 2/ add their name on the wiki page [1] http://wiki.openstack.org/EfficientMetering/PTLElectionProcess Done, and added a few more words at [1] following the steps of the previous 2 candidates, which are both exceptionally skilled to run this project too. It's absolutely a wonderful feeling that I am not the only one caring enough about this project. Truly, I think this project would be nowhere if we had not met. The road ahead is still quite steep, and we'll all have lots to do, regardless of whom leads next. [1] http://wiki.openstack.org/EfficientMetering/PTLElectionProcess/NickBarcet 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] [nova] [cinder] Nova-volume vs. Cinder in Folsom
Because the community has done such a good job in the area of interoperability and compatibility over the past few years that it thus deserves the benefit of the doubt even though we have a thread previously showing blatant disregard for such concerns? No, this community has, by and large, been overtly hostile to concerns of interoperability and compatibility and I jumped into this thread exactly because it was in active expression of that ongoing overt hostility. As I said before, that needs to change. If you don't like my methods, oh well. But this is a serious problem that is a distinct threat to the viability of OpenStack. Much, much, much more so than whether block storage is represented by the nova-volumes model or the Cinder model. Having said that, I believe I've made my point. I think the net result is that some people better understand the pain caused by the lack of OpenStack interoperability and compatibility, and others are still interested in just paying it lips service. We'll see what wins out come GA of Folsom, won't we? -George On Jul 13, 2012, at 10:47 AM, Stefano Maffulli wrote: On 07/12/2012 03:54 PM, George Reese wrote: This community needs offending. This is your opinion and you're entitled to it but let me assure you that *nobody* here wants to be offended by you. This community is made of smart people that deserve respect: stop offending them, now. Make your point in a civil way and try to build consensus around it: that's how this community operates. /stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: +1.207.956.0217 enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com To schedule a meeting with me: http://tungle.me/GeorgeReese ___ 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] Glance/Swift tenant specific storage
Eglynn pointed out some concurrency concerns in this review that I wanted to highlight: https://review.openstack.org/#/c/9552/ The issue is we need to provide Glance stores access to the request context. The current thought is that we'd like to modify Glance to create new Store objects for each request (thus avoiding concurrency issues). The existing Glance model creates singleton Store objects at startup. Before I go changing Glance in this regard I wanted to ask... Does this seem reasonable? We can still in create Store instances at startup for validation purposes. Although now that I think of it I find the log messages Glance generates from missing S3 and or Swift configs to be somewhat unnecessary. Perhaps we should rethink this startup validation as well? Eoghan: Thanks for the detail comments on the reviews. Keep them coming. Dan - Original Message - From: Dan Prince dpri...@redhat.com To: OpenStack Mailing List openstack@lists.launchpad.net Sent: Sunday, July 8, 2012 9:59:54 PM Subject: Glance/Swift tenant specific storage I started working on the Glance swift-tenant-specific-storage blueprint last week. I've got a working branch in play here: https://github.com/dprince/glance/commits/swift_multi_tenant3 Some details on how I've done things so far: * Update Glance so that it uses the service catalog for each user to obtain the Swift storage URL. * Provide backend stores access to the context. Glance Essex doesn't give stores access to the RequestContext (auth token). We'll need this information for tenant specific storage if we want to be able to access individual swift accounts. * Store images in separate containers. Swift only allows individual ACL's to be set per container... not per object. As such it appears we'll need to store each image in a separate container in order to support setting public and/or individual read/write access on each image. * Set 'public' access for images in Swift. * Set 'private' read and/or write access for Glance image members which have been granted access to specific images. * Delayed delete (scrubber) will require an authenticated context in order to delete Swift images from the backend. Glance can either be make to grant write access to this account (for all images) or an administrative Swift account could be used to run the delayed delete operation. * Maintain full support with the existing single tenant Glance swift storage scheme. I made some general implementation notes up on this wiki page as well: http://wiki.openstack.org/GlanceSwiftTenantSpecificStorage I'm anxious to get things up for review but before I do so I wanted to ask if this implementation looks reasonable? Any thoughts or feedback? Dan ___ 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] Capacity based scheduling: What updated free_ram_mb in Folsom
Hi Phil, The nova.db.api.compute_node_update() call is what the individual virt drivers call to update the compute node stats. grep for that and you'll see where the calls to set the compute node data are called. Best, -jay On 07/13/2012 09:38 AM, Day, Phil wrote: Hi Folks, I was reviewing a code change to add generic retries for build failures ( https://review.openstack.org/#/c/9540/2 ), and wanted to be sure that it wouldn’t invalidate the capacity accounting used by the scheduler. However I've been sitting here for a while working through the Folsom scheduler code trying to understand how the capacity based scheduling now works, and I’m sure I’m missing something obvious but I just can’t work out where the free_ram_mb value in the compute_node table gets updated. I can see the database api method to update the values, compute_node_utilization_update(), it doesn’t look as if anything in the code ever calls that ? From when I last looked at this / various discussions here and at the design summits I thought the approach was that: - The scheduler would make a call (rather than a cast) to the compute manger, which would then do some verification work, update the DB table whilst in the context of that call, and then start a thread to complete the spawn. The need to go all the way to the compute node as a call was to avoid race conditions from multiple schedulers. (the change I’m looking at is part of a blueprint to avoid such a race, so maybe I imagined the change from cast to call ?) - On a delete, the capacity_notifer (which had to be configured into the list_notifier) would detect the delete message, and decrement the database values. But now I look through the code it looks as if the scheduler is still doing a cast (scheduler/driver), and although I can see the database api call to update the values, compute_node_utilization_update(), it doesn’t look as if anything in the code ever calls that ? The ram_filter scheduler seems to use the free_ram_mb value, and that value seems to come from the host_manager in the scheduler which is read from the Database, but I can't for the life of me work out where these values are updated in the Database. The capacity_notifier, which used to decrement values on a VM deletion only (according to the comments the increment was done in the scheduler) seems to have now disappeared altogether in the move of the notifier to openstack/common ? So I’m sure I’m missing some other even more cunning plan on how to keep the values current, but I can’t for the life of me work out what it is – can someone fill me in please ? Thanks, Phil ___ 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] [Keystone] Services API
In the V2 API, there's no update available - it's just create/delete. -joe On Jul 13, 2012, at 5:19 AM, Antonio Manuel Muñiz Martín wrote: There are no method update_service here [1], so I think update is not possible, am I right? Thanks, Antonio. [1] https://github.com/openstack/keystone/blob/0425fba560e7d68e52f922667972765e64ad17dc/keystone/controllers/services.py 2012/7/13 Antonio Manuel Muñiz Martín amu...@klicap.es: Hi, I'm trying to make an update request (PUT /v2.0/OS-KSADM/services/53ccd2984389495cab439640dc5596d3) and it's returning HTTP 404. The docs also miss the PUT method [1], so I guess if there is a way to update a service through the WS API? Thanks, Antonio. [1] http://docs.rackspace.com/openstack-extensions/auth/OS-KSADM-admin-devguide/content/Service_Operations_OS-KSADM.html -- Antonio Manuel Muñiz Martín Software Developer at klicap - ingeniería del puzle work phone + 34 954 894 322 www.klicap.es | blog.klicap.es -- Antonio Manuel Muñiz Martín Software Developer at klicap - ingeniería del puzle work phone + 34 954 894 322 www.klicap.es | blog.klicap.es ___ 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] Bad performance on physical hosts kvm + bonding + bridging
On 07/13/2012 06:55 AM, Leandro Reox wrote: Ok, here is the story, we deployed some inhouse APIs in our Openstack privade cloud, and we were stressing them up, we realize that some packages were taking so long, to discard the behavior of the api, we installed apache, lighttpd and event tried with netcat, of course on the guest systems running ubuntu 10.10 w/virtio, after getting nuts modifing sysctl parameters to change the guest behavior, we realized that if we installed apache, or lighttpd on the PHYSICAL host the behavior was the same , that surprised us, when we try the same benchmark on a node without bonding, bridging and without any KVM packages or nova installed, with the same HW specs, the benchmark passes OK, but if we run the same tests on a spare nova node with everything installed + bonding + bridging that never run a virtual guest machine, the test fails too, so, so far: Tested on hosts with Ubuntu 10.10, 11.10 and 12.04 - Clean node without bonding + briding or KVM - just the eth0 configured - PASS - Spare node with bridging - PASS - Spare node with just bonding (dynamic link aggr mode4) - PASS - Spare node with nova + kvm + bonding + bridging - FAILS - Spare node with nova + kvm - PASS Is there a chance that working with bridging + bonding + nova some module get screwed, ill attach the tests , you can see that a small amount of packages takes TOO LONG, like 3secs, and the overhead time is on the CONNECT phase If I recall correctly, 3 seconds is the default, initial TCP retransmission timeout (at least in older kernels - what is your load generator running?). Between that, and your mentioning connect phase, my first guess (it is only a guess) would be that something is causing TCP SYNchronize segments to be dropped. If that is the case, it should show-up in netstat -s statistics. Snap them on both client and server before the test is started, and after the test is completed, and then run them through something like beforeafter ( ftp://ftp.cup.hp.com/dist/networking/tools ) netstat -s before.server # run benchmark netstat -s after.server beforeafter before.server after.server delta.server less delta.server (As a sanity check, make certain that before.server and after.server have the same number of lines. The habit of Linux's netstat to avoid printing a statistic with a value of zero can, sometimes, confuse beforeafter if a stat appears in after that was not present in before.) It might not be a bad idea to include ethtool -S statistics from each of the interfaces in that procedure as well. rick jones probably a good idea to mention the bonding mode you are using This is ApacheBench, Version 2.3 $Revision: 655654 $ Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking 172.16.161.25 (be patient) Completed 2500 requests Completed 5000 requests Completed 7500 requests Completed 1 requests Completed 12500 requests Completed 15000 requests Completed 17500 requests Completed 2 requests Completed 22500 requests Completed 25000 requests Finished 25000 requests Server Software:Apache/2.2.16 Server Hostname:172.16.161.25 Server Port:80 Document Path: / Document Length:177 bytes Concurrency Level: 5 Time taken for tests: 7.493 seconds Complete requests: 25000 Failed requests:0 Write errors: 0 Total transferred: 1135 bytes HTML transferred: 4425000 bytes Requests per second:3336.53 [#/sec] (mean) Time per request: 1.499 [ms] (mean) Time per request: 0.300 [ms] (mean, across all concurrent requests) Transfer rate: 1479.28 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect:01 46.6 03009 Processing: 01 5.7 0 277 Waiting:00 4.6 0 277 Total: 01 46.9 13010 Percentage of the requests served within a certain time (ms) 50% 1 66% 1 75% 1 80% 1 90% 1 95% 1 98% 1 99% 1 100% 3010 (longest request) Regards! ___ 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] [Folsom Testing Packages] Feedback
On 07/13/2012 05:50 AM, Emilien Macchi wrote: Thank's to Adam Gandelman for the last e-mail about *Folsom Testing Packages* in *Ubuntu* [1]. I would like to share here my feedback and also the Issues I have today with that : * Glance Packaging [2] : Conflict between two packages. * Glance Endpoint does not work with API V2 but works with API V1. If I comment */etc/glance/glance-api-paste.ini* the part about V2, everything works. Maybe it's my bad, I need to understand more what's wrong. Anyway, I did not have this issue with Essex. * Horizon does not work [3] [1] http://www.mail-archive.com/openstack@lists.launchpad.net/msg14298.html [2] https://bugs.launchpad.net/python-glanceclient/+bug/1024281 [3] https://bugs.launchpad.net/horizon/+bug/1024326 Let me know if you have any idea. Regards Thanks Emilien, this is exacly the kind of testing I was hoping to get! In the future, please target bugs against the Ubuntu distro package rather than the upstream project. Thanks again, hope to have those fixed for you soon. Adam Emilien Macchi *System Engineer* **www.stackops.com* http://www.stackops.com/*|emilien.mac...@stackops.com mailto:emilien.mac...@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 ___ 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] Testing NOVA-OVS-Quantum setup
Hi Trinath, I suspect that /etc/quantum should be created when you run the following line from Emilien's document: apt-get install -y quantum-server quantum-plugin-openvswitch python-keystone python-keystoneclient openvswitch-datapath-source If /etc/quantum was not created, perhaps its an issue with the packaging. Dan On Thu, Jul 12, 2012 at 11:00 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi - Thanks a lot for the reply. Following the document ( https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for installing the OVS and Quantum Agent in Compute nodes. *Open-vSwitch Quantum-agent* apt-get install openvswitch-switch quantum-openvswitch-agent modprobe openvswitch_mod echo openvswitch_mod/etc/modules Trinath After following the above steps, I'm unable to find below specified editable file. in /etc there no directory with quantum. Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and change the SQL connection to : sql_connection = mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum Please guide me understand the same, On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.com wrote: Hi Trinath, Yes, you need to install openvswitch and the quantum-agent on the nova compute nodes as well. Aaron On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- With respect to your document, on Openstack - OVS and Quantum, I'm unable to understand the setup of OVS and Quantum in ESSEX-2/Compute-node machine. In the Document, https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No: 17/19, In the section Open-vSwitch Quantum-agent, Do we need to install OVS and Quantum in the Compute-nodes too..?? . On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I wrote a documentation about installation of Essex with Quantum, OVS in multi-node architecture. You can read it here : https://github.com/EmilienM/doc-openstack Regards On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote: Trinath, I found the following Quantun admin guide was useful for that purpose: http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w Thanks, Joseph (w) 703-248-6160 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Trinath Somanchi trinath.soman...@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, June 20, 2012 7:04:21 AM Subject: [Openstack] Testing NOVA-OVS-Quantum setup Hi- I have installed configured NOVA-OVS-Quantum based setup using the guide provided by openstack and OVS. I have a instance up and running. I'm new to Openstack. Can you any one help me out on the testing/validating on is instance up with OVS and Quantum. 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 -- Emilien Macchi *SysAdmin (Intern)* *www.stackops.com* | emilien.mac...@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,
[Openstack] Cannot add floating ip
Hi guys, i've 2 hosts configured in multi_host, i had 2 vm (1 per host) with 1 floating ip each, then nova-compute on second host crashed when deleting the vm2, i've restarted host2 and it deleted the vm successfully, then i've got an error about floating ip cannot be associated to vm2 in logs, so i've removed the floating ip using nova-manage, now i'm not able anymore to add floating ip, when i do sudo nova-manage floating add 5.9.x.x i get no output in both console and /var/log/nova/* logs. Floating list doesn't show the new ip. Any way to debug this? Best regards ___ 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] Capacity based scheduling: What updated free_ram_mb in Folsom
Phil, This may shine some light. https://bugs.launchpad.net/nova/+bug/1016273 best, Joe On Fri, Jul 13, 2012 at 10:27 AM, Day, Phil philip@hp.com wrote: Hi Jay, If I read it correctly that updates the *_used values that show actual consumption, but what I was looking for is the updates to the allocated values (free_ram_mb / free_disk_gb ) that were added for schedulers that didn’t want to over commit. I remember some detailed discussion with Chris and Sandy about how best to implement this in the face of multiple schedulers, failing creates, etc, some of which involved the notification systems. Brian Elliot pointed me to where in the fliter scheduler just recalculates these values from the instance table - so I guess the plans to maintain the info in the Database were dropped along the way. Cheers, Phil -Original Message- From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto: openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of Jay Pipes Sent: 13 July 2012 17:36 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Capacity based scheduling: What updated free_ram_mb in Folsom Hi Phil, The nova.db.api.compute_node_update() call is what the individual virt drivers call to update the compute node stats. grep for that and you'll see where the calls to set the compute node data are called. Best, -jay On 07/13/2012 09:38 AM, Day, Phil wrote: Hi Folks, I was reviewing a code change to add generic retries for build failures ( https://review.openstack.org/#/c/9540/2 ), and wanted to be sure that it wouldn’t invalidate the capacity accounting used by the scheduler. However I've been sitting here for a while working through the Folsom scheduler code trying to understand how the capacity based scheduling now works, and I’m sure I’m missing something obvious but I just can’t work out where the free_ram_mb value in the compute_node table gets updated. I can see the database api method to update the values, compute_node_utilization_update(), it doesn’t look as if anything in the code ever calls that ? From when I last looked at this / various discussions here and at the design summits I thought the approach was that: - The scheduler would make a call (rather than a cast) to the compute manger, which would then do some verification work, update the DB table whilst in the context of that call, and then start a thread to complete the spawn. The need to go all the way to the compute node as a call was to avoid race conditions from multiple schedulers. (the change I’m looking at is part of a blueprint to avoid such a race, so maybe I imagined the change from cast to call ?) - On a delete, the capacity_notifer (which had to be configured into the list_notifier) would detect the delete message, and decrement the database values. But now I look through the code it looks as if the scheduler is still doing a cast (scheduler/driver), and although I can see the database api call to update the values, compute_node_utilization_update(), it doesn’t look as if anything in the code ever calls that ? The ram_filter scheduler seems to use the free_ram_mb value, and that value seems to come from the host_manager in the scheduler which is read from the Database, but I can't for the life of me work out where these values are updated in the Database. The capacity_notifier, which used to decrement values on a VM deletion only (according to the comments the increment was done in the scheduler) seems to have now disappeared altogether in the move of the notifier to openstack/common ? So I’m sure I’m missing some other even more cunning plan on how to keep the values current, but I can’t for the life of me work out what it is – can someone fill me in please ? Thanks, Phil ___ 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
[Openstack] Api startup issue (maybe pastedeploy related)
Hi all, I just tried to install nova from the folsom-2 package and run into an issue with the api server, which I can't really figure out. Tracking the progress with a large number of strategically placed prints I get to the stage where the api (for example metadata) app is being loaded in load_app() (from nova/wsgi.py) Then, going deeper into paste.deploy, I can see the configuration being loaded via the loadobj / loadcontext functions. Finally the context (LoaderContext) is returned and loadobj() tries to return context.create() Here python just stops on a line which tries to access self.object_type. There's no exception, error or segfault. Python just closes down. If I change the create function to: def create(self) : print 'creating context' print 'for object type %s' % (type(object_type),) return the last message I see is creating context. Any attempt to access object_type (even just to get its type) causes a crash (?), but doesn't leave any trace like a coredump. Additionally I run into http://bugs.python.org/issue1596321 but I don't think that's related, since I no threads are started by this point (I think...) I'm running on a clean Ubuntu Precise machine with: python 2.7.3-0ubuntu2 python-pastedeploy 1.5.0-2build1 Does anyone have a good idea how to fix or at least debug it? Regards, Stanisław Pitucha Cloud Services Hewlett Packard ___ 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] Questions about ceilometer
I *just* ran into a problem today triggered by some code moving around in
nova and common. I had to set my driver to
nova.openstack.common.notifier.rabbit_notifier (in both files).
I didn't see any errors from that until I tried to launch an instance, so
it doesn't seem to prevent any of the nova services from starting up.
Doug
On Fri, Jul 13, 2012 at 1:17 PM, TRAN, JOHN jt7...@att.com wrote:
I'm having the same problem. I'm running against nova trunk and I have
rabbit notifier enabled.
/etc/nova/nova.conf:notification_driver=nova.notifier.rabbit_notifier
/home/stack/ceilometer-collector.conf:notification_driver=nova.notifier.rabbit_notifier
From:
openstack-bounces+jhtran=att@lists.launchpad.net[openstack-bounces+jhtran=
att@lists.launchpad.net] on behalf of 张家龙 [zhan...@awcloud.com]
Sent: Friday, July 13, 2012 8:36 AM
To: Doug Hellmann; Julien Danjou
Cc: openstack
Subject: Re: [Openstack] Questions about ceilometer
Dear Doug,
I`m use Qpid instead of Rabbit .
Did it cause the error ?
In addition,my nova.conf,mongodb.conf and ceilometer-collector.conf
are here:
http://pastebin.com/sW5d8eRv
http://pastebin.com/D5GMkLsb
http://pastebin.com/u5vH22Lh
Were there some errors in my config files?
Waiting your reply. Thanks.
--
Best Regards
ZhangJialong
-- Original --
From: Doug Hellmanndoug.hellm...@dreamhost.com;
Date: Fri, Jul 13, 2012 11:28 PM
To: 张家龙zhan...@awcloud.com; Julien Danjoujul...@danjou.info;
Cc: openstackopenstack@lists.launchpad.net;
Subject: Re: [Openstack] Questions about ceilometer
On Fri, Jul 13, 2012 at 10:04 AM, Doug Hellmann
doug.hellm...@dreamhost.commailto:doug.hellm...@dreamhost.com wrote:
On Thu, Jul 12, 2012 at 9:42 PM, 张家龙 zhan...@awcloud.commailto:
zhan...@awcloud.com wrote:
Dear all,
As the project named ceilometer appeared,I paid close attention to it.
According to the docs of ceilometer,I deploied it in openstack exsse
environment.
While,I cannot start the ceilometer collector and agent.
The follows are my operations.
1.Install openstack nova ,mongodb and ceilometer.
2.configurate nova ,mongodb and ceilometer
The /etc/nova/nova.conf file is here:
http://pastebin.com/sW5d8eRv
Here is the /etc/ceilometer-collector.conf file is here:
http://pastebin.com/u5vH22Lh
And the /etc/mongodb.conf is here:
http://pastebin.com/D5GMkLsb
3.Start openstack nova ,mongodb
4.Then I start the ceilometer-collector
/usr/bin/ceilometer-collector start
While,some errors occurred:
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb storage
engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage [-] Loaded mongodb storage
engine EntryPoint.parse('mongodb =
ceilometer.storage.impl_mongodb:MongoDBStorage')
2012-07-11 05:25:35 INFO ceilometer.storage.impl_mongodb [-]
connecting to MongoDB on localhost:27017
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
attempting to load notification handler for
ceilometer.collector.compute:instance
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.create.end events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.exists events
2012-07-11 05:25:35 INFO ceilometer.collector.dispatcher [-]
subscribing instance handler to compute.instance.delete.start events
Traceback (most recent call last):
File /usr/lib/python2.6/site-packages/eventlet/hubs/poll.py, line
97, in wait
readers.get(fileno, noop).cb(fileno)
File /usr/lib/python2.6/site-packages/eventlet/greenthread.py,
line 192, in main
result = function(*args, **kwargs)
File /usr/lib/python2.6/site-packages/nova/service.py, line 101,
in run_server
server.start()
File /usr/lib/python2.6/site-packages/nova/service.py, line 162,
in start
self.manager.init_host()
File
/usr/lib/python2.6/site-packages/ceilometer-0-py2.6.egg/ceilometer/collector/manager.py,
line 69, in init_host
topic='%s.infohttp://s.info' %
flags.FLAGS.notification_topics[0],
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 867,
in __getattr__
return self._substitute(self._get(name))
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1070,
in _get
info = self._get_opt_info(name, group)
File
/usr/lib/python2.6/site-packages/nova/openstack/common/cfg.py, line 1161,
in _get_opt_info
raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: notification_topics
Removing descriptor: 12
If anyone can help me ? Waiting your reply.
Re: [Openstack] Nova-manage service list shows old and new hostname
The only way currently is to delete the records from the services table in the database. Vish On Jul 13, 2012, at 5:27 AM, Alessandro Tagliapietra wrote: Hello list, i've this problem, when i run nova-manage service list i get nova-compute server1.site.it nova enabled :-) 2012-07-13 12:15:44 nova-volume server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-network server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-consoleauth server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-scheduler server1.site.it nova enabled :-) 2012-07-13 12:15:51 nova-scheduler Ubuntu-1204-precise-64-minimal nova enabledXXX 2012-07-13 12:06:57 nova-certUbuntu-1204-precise-64-minimal nova enabledXXX 2012-07-13 12:06:57 nova-consoleauth Ubuntu-1204-precise-64-minimal nova enabledXXX 2012-07-13 12:06:57 nova-compute Ubuntu-1204-precise-64-minimal nova enabledXXX None nova-network Ubuntu-1204-precise-64-minimal nova enabledXXX 2012-07-13 12:06:57 nova-certserver1.site.it nova enabled :-) 2012-07-13 12:15:51 that's because i installed openstack changing only the hostname with the hostname command and not in /etc/hostname, laters i've changed that and restarted, now i see services from both the old and new host. Is there a way to remove those services from the hostname Ubuntu-1204-precise-64-minimal? Regards Alessandro ___ 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] [nova] VM stucks in deleting task state
Larsk Kellogg-Stedman shared a few weeks ago the tool he uses to clean up OpenStack database after messing with it: http://markmail.org/message/gygnjvdy3njwfrtg maybe it's useful for others, too. Cheers, stef On 07/12/2012 12:48 PM, Sébastien Han wrote: http://www.sebastien-han.fr/blog/2012/07/10/delete-a-vm-in-an-error-state/ On Thu, Jul 12, 2012 at 8:34 PM, Tong Li liton...@us.ibm.com mailto:liton...@us.ibm.com wrote: Hi, Hien, I had same problem. The only way that I can get rid of it is to remove the record for that instance from the following 3 mysql db tables in the following order. security_group_instance_association instance_info_caches instances hope that helps. Tong Li Emerging Technologies Standards Inactive hide details for Hien Phan ---07/12/2012 02:08:58 PM---Hello list, I've just installed Openstack Essex on Ubuntu 12.04Hien Phan ---07/12/2012 02:08:58 PM---Hello list, I've just installed Openstack Essex on Ubuntu 12.04. Everything works well From: Hien Phan phanquoch...@gmail.com mailto:phanquoch...@gmail.com To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Date: 07/12/2012 02:08 PM Subject: [Openstack] [nova] VM stucks in deleting task state Sent by: openstack-bounces+litong01=us.ibm@lists.launchpad.net mailto:us.ibm@lists.launchpad.net Hello list, I've just installed Openstack Essex on Ubuntu 12.04. Everything works well except one problem I just faced: When I try terminate VM in dashboard. It stuck in deleting ask for few hours until now. I can not connect VM. I try reboot using nova command and error : root@openstack-node01:~# nova reboot hien-vm02 ERROR: Cannot 'reboot' while instance is in task_state deleting (HTTP 409) root@openstack-node01:~# nova reboot hien-vm01 ERROR: Cannot 'reboot' while instance is in task_state deleting (HTTP 409) root@openstack-node01:~# nova list +--+---++-+ | ID |Name | Status | Networks | +--+---++-+ | b924a325-b07f-480b-9a31-3049736fbfde | hien-vm02 | ACTIVE | private=172.16.1.35, 192.168.255.34 | | e7908096-83e6-480d-9131-efa4ea73ca0d | hien-vm01 | ACTIVE | private=172.16.1.34, 192.168.255.33 | +--+---++-+ Openstack Dashboard screenshot image: _http://i.imgur.com/7e4cf.png_ How i can delete VMs completely ? Thanks in advance. -- Best regards, Phan Quoc Hien _ _http://www.mrhien.info/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto: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 mailto: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] Cannot add floating ip
What an idtio, it's create, not add. Sorry for the spam Il giorno 13/lug/2012, alle ore 20:00, Alessandro Tagliapietra ha scritto: Hi guys, i've 2 hosts configured in multi_host, i had 2 vm (1 per host) with 1 floating ip each, then nova-compute on second host crashed when deleting the vm2, i've restarted host2 and it deleted the vm successfully, then i've got an error about floating ip cannot be associated to vm2 in logs, so i've removed the floating ip using nova-manage, now i'm not able anymore to add floating ip, when i do sudo nova-manage floating add 5.9.x.x i get no output in both console and /var/log/nova/* logs. Floating list doesn't show the new ip. Any way to debug this? Best regards ___ 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] About images list in dashboard
Hi Sam, Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. Sam On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com (mailto:susltd...@gmail.com) wrote: Thank you for your suggestion. I can see all images in other tenants from dashboard, so I think the images type should be ok. On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com (mailto:gabriel.hur...@nebula.com) wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net (mailto:nebula@lists.launchpad.net) [mailto:openstack-bounces+gabriel.hurley (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net (mailto:nebula@lists.launchpad.net)] On Behalf Of Sam Su Sent: Thursday, July 05, 2012 11:20 AM To: openstack Subject: [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: Image Name Type Status Public Container Format Actions CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result) # nova image-list +-+--+- --+--+ | ID | Name | Status |Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel| ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | | 99be14c0-3b15-470b-9e2d-a9d7e2242c7a | CentOS-5.8-x86_64 | ACTIVE | | | a486733f-c011-4fa1-8ce2-553084f9bc0e | ubuntu-11.10-server-amd64 | ACTIVE | | | ec7f9c5d-48b4-40e3-8e36-87fbdd099fee | ubuntu-12.04-server-amd64-ramdisk | ACTIVE | | | fbb3a182-e610-448f-8042-0b1addb90750 | ubuntu-12.04-server-amd64-hostname | ACTIVE | | +-+--+--- +--+ I am wondering how to make all these images seen in my the dashboard? It will be much
Re: [Openstack] Cannot add floating ip
From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Alessandro Tagliapietra [tagliapietra.alessan...@gmail.com] Sent: Saturday, July 14, 2012 12:18 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Cannot add floating ip snip What an idtio, it's create, not add. Sorry for the spam /snip Its okey. :) Cheers!! Il giorno 13/lug/2012, alle ore 20:00, Alessandro Tagliapietra ha scritto: Hi guys, i've 2 hosts configured in multi_host, i had 2 vm (1 per host) with 1 floating ip each, then nova-compute on second host crashed when deleting the vm2, i've restarted host2 and it deleted the vm successfully, then i've got an error about floating ip cannot be associated to vm2 in logs, so i've removed the floating ip using nova-manage, now i'm not able anymore to add floating ip, when i do sudo nova-manage floating add 5.9.x.x i get no output in both console and /var/log/nova/* logs. Floating list doesn't show the new ip. Any way to debug this? Best regards ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp http://www.csscorp.com/common/email-disclaimer.php ___ 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] About images list in dashboard
Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of John Postlethwait Sent: Friday, July 13, 2012 12:05 PM To: Sam Su Cc: openstack Subject: Re: [Openstack] About images list in dashboard Hi Sam, Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug John Postlethwait Nebula, Inc. 206-999-4492 On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. Sam On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.commailto:susltd...@gmail.com wrote: Thank you for your suggestion. I can see all images in other tenants from dashboard, so I think the images type should be ok. On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.commailto:gabriel.hur...@nebula.com wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.netmailto:nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurleymailto:openstack-bounces%2Bgabriel.hurley=nebula@lists.launchpad.netmailto:nebula@lists.launchpad.net] On Behalf Of Sam Su Sent: Thursday, July 05, 2012 11:20 AM To: openstack Subject: [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: Image Name Type Status Public Container Format Actions CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result) # nova image-list +-+--+- --+--+ | ID| Name | Status | Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel | ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | | 99be14c0-3b15-470b-9e2d-a9d7e2242c7a | CentOS-5.8-x86_64 | ACTIVE | | | a486733f-c011-4fa1-8ce2-553084f9bc0e | ubuntu-11.10-server-amd64 | ACTIVE | | | ec7f9c5d-48b4-40e3-8e36-87fbdd099fee | ubuntu-12.04-server-amd64-ramdisk | ACTIVE | | | fbb3a182-e610-448f-8042-0b1addb90750 | ubuntu-12.04-server-amd64-hostname | ACTIVE | | +-+--+--- +--+ I am wondering how to make all these images seen in my the dashboard? It will be much appreciated if someone can give me some hints about this. Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help :
Re: [Openstack] About images list in dashboard
Thank you for you guys' suggestions. Even so, I'd like to file a bug to track this issue, if someone else have the same problem, they would know what happened and what progressed from the bug trace. Sam On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *John Postlethwait *Sent:* Friday, July 13, 2012 12:05 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] About images list in dashboard ** ** Hi Sam, ** ** Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug ** ** ** ** ** ** John Postlethwait Nebula, Inc. 206-999-4492 ** ** On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. ** ** If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. ** ** ** ** Sam ** ** ** ** On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com wrote: Thank you for your suggestion. ** ** I can see all images in other tenants from dashboard, so I think the images type should be ok. ** ** ** ** ** ** On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 05, 2012 11:20 AM *To:* openstack *Subject:* [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: *Image Name Type Status Public Container Format Actions* CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result)* *** # nova image-list +-+--+- --+--+ | ID | Name | Status |Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel | ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | | 99be14c0-3b15-470b-9e2d-a9d7e2242c7a | CentOS-5.8-x86_64 | ACTIVE | | | a486733f-c011-4fa1-8ce2-553084f9bc0e | ubuntu-11.10-server-amd64 | ACTIVE | | | ec7f9c5d-48b4-40e3-8e36-87fbdd099fee | ubuntu-12.04-server-amd64-ramdisk | ACTIVE | | | fbb3a182-e610-448f-8042-0b1addb90750 | ubuntu-12.04-server-amd64-hostname | ACTIVE | | +-+--+--- +--+ I am wondering how to
Re: [Openstack] Testing NOVA-OVS-Quantum setup
That's actually an issue with Packaging and I met in April during Essex Release. My document does not explain in details how to manage Quantum, but this is a document which allow to get something working in dual node. Of course, maybe I did some errors and the best way for me to correct it asap is to write here : https://github.com/EmilienM/doc-openstack/issues/add Good luck, Regards On Fri, Jul 13, 2012 at 7:31 PM, Dan Wendlandt d...@nicira.com wrote: Hi Trinath, I suspect that /etc/quantum should be created when you run the following line from Emilien's document: apt-get install -y quantum-server quantum-plugin-openvswitch python-keystone python-keystoneclient openvswitch-datapath-source If /etc/quantum was not created, perhaps its an issue with the packaging. Dan On Thu, Jul 12, 2012 at 11:00 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi - Thanks a lot for the reply. Following the document ( https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf,) for installing the OVS and Quantum Agent in Compute nodes. *Open-vSwitch Quantum-agent* apt-get install openvswitch-switch quantum-openvswitch-agent modprobe openvswitch_mod echo openvswitch_mod/etc/modules Trinath After following the above steps, I'm unable to find below specified editable file. in /etc there no directory with quantum. Edit /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini and change the SQL connection to : sql_connection = mysql://ovs_quantum:password@10.68.1.40:3306/ovs_quantum Please guide me understand the same, On Fri, Jul 13, 2012 at 11:25 AM, Aaron Rosen aro...@nicira.com wrote: Hi Trinath, Yes, you need to install openvswitch and the quantum-agent on the nova compute nodes as well. Aaron On Fri, Jul 13, 2012 at 1:29 AM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- With respect to your document, on Openstack - OVS and Quantum, I'm unable to understand the setup of OVS and Quantum in ESSEX-2/Compute-node machine. In the Document, https://lists.launchpad.net/openstack/pdfuNjHGvU5UA.pdf, Page.No: 17/19, In the section Open-vSwitch Quantum-agent, Do we need to install OVS and Quantum in the Compute-nodes too..?? . On Wed, Jun 20, 2012 at 5:38 PM, Emilien Macchi emilien.mac...@stackops.com wrote: Hi, I wrote a documentation about installation of Essex with Quantum, OVS in multi-node architecture. You can read it here : https://github.com/EmilienM/doc-openstack Regards On Wed, Jun 20, 2012 at 1:30 PM, Joseph Suh j...@isi.edu wrote: Trinath, I found the following Quantun admin guide was useful for that purpose: http://www.google.com/url?sa=trct=jq=esrc=ssource=webcd=4ved=0CHsQFjADurl=http%3A%2F%2Fdocs.openstack.org%2Ftrunk%2Fopenstack-network%2Fadmin%2Fquantum-admin-guide-trunk.pdfei=prHhT-SMMMa70QG_uJTwAwusg=AFQjCNEq2fuo4dQrvFQT0zw8v05zMdIFWwsig2=6eAgFutMS_VLrhpR4Lhy2w Thanks, Joseph (w) 703-248-6160 (f) 703-812-3712 3811 N. Fairfax Drive Suite 200 Arlington, VA, 22203, USA http://www.east.isi.edu/~jsuh - Original Message - From: Trinath Somanchi trinath.soman...@gmail.com To: openstack@lists.launchpad.net Sent: Wednesday, June 20, 2012 7:04:21 AM Subject: [Openstack] Testing NOVA-OVS-Quantum setup Hi- I have installed configured NOVA-OVS-Quantum based setup using the guide provided by openstack and OVS. I have a instance up and running. I'm new to Openstack. Can you any one help me out on the testing/validating on is instance up with OVS and Quantum. 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 -- Emilien Macchi *SysAdmin (Intern)* *www.stackops.com* | emilien.mac...@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
Re: [Openstack] About images list in dashboard
Well, it sounds like this issue only happens in Essex, and is no longer an issue in Folsom, so the bug will just be closed as invalid, as it is now fixed in the newer code... John Postlethwait Nebula, Inc. 206-999-4492 On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote: Thank you for you guys' suggestions. Even so, I'd like to file a bug to track this issue, if someone else have the same problem, they would know what happened and what progressed from the bug trace. Sam On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley gabriel.hur...@nebula.com (mailto:gabriel.hur...@nebula.com) wrote: Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net (mailto:nebula@lists.launchpad.net) [mailto:openstack-bounces+gabriel.hurley (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net (mailto:nebula@lists.launchpad.net)] On Behalf Of John Postlethwait Sent: Friday, July 13, 2012 12:05 PM To: Sam Su Cc: openstack Subject: Re: [Openstack] About images list in dashboard Hi Sam, Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug John Postlethwait Nebula, Inc. 206-999-4492 (tel:206-999-4492) On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. Sam On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com (mailto:susltd...@gmail.com) wrote: Thank you for your suggestion. I can see all images in other tenants from dashboard, so I think the images type should be ok. On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com (mailto:gabriel.hur...@nebula.com) wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net (mailto:nebula@lists.launchpad.net) [mailto:openstack-bounces+gabriel.hurley (mailto:openstack-bounces%2Bgabriel.hurley)=nebula@lists.launchpad.net (mailto:nebula@lists.launchpad.net)] On Behalf Of Sam Su Sent: Thursday, July 05, 2012 11:20 AM To: openstack Subject: [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: Image Name Type Status Public Container Format Actions CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result) # nova image-list +-+--+- --+--+ | ID | Name | Status |
Re: [Openstack] Capacity based scheduling: What updated free_ram_mb in Folsom
Capacity based scheduling currently adds up all instance usage in host_manager.py There's another review marked as WIP that will be ready when retries go in that cleans that and the capacity tracking up. Look for it from Brian Elliott. On Jul 13, 2012, at 6:38 AM, Day, Phil philip@hp.com wrote: Hi Folks, I was reviewing a code change to add generic retries for build failures ( https://review.openstack.org/#/c/9540/2 ), and wanted to be sure that it wouldn’t invalidate the capacity accounting used by the scheduler. However I've been sitting here for a while working through the Folsom scheduler code trying to understand how the capacity based scheduling now works, and I’m sure I’m missing something obvious but I just can’t work out where the free_ram_mb value in the compute_node table gets updated. I can see the database api method to update the values, compute_node_utilization_update(), it doesn’t look as if anything in the code ever calls that ? From when I last looked at this / various discussions here and at the design summits I thought the approach was that: - The scheduler would make a call (rather than a cast) to the compute manger, which would then do some verification work, update the DB table whilst in the context of that call, and then start a thread to complete the spawn. The need to go all the way to the compute node as a call was to avoid race conditions from multiple schedulers. (the change I’m looking at is part of a blueprint to avoid such a race, so maybe I imagined the change from cast to call ?) - On a delete, the capacity_notifer (which had to be configured into the list_notifier) would detect the delete message, and decrement the database values. But now I look through the code it looks as if the scheduler is still doing a cast (scheduler/driver), and although I can see the database api call to update the values, compute_node_utilization_update(), it doesn’t look as if anything in the code ever calls that ? The ram_filter scheduler seems to use the free_ram_mb value, and that value seems to come from the host_manager in the scheduler which is read from the Database, but I can't for the life of me work out where these values are updated in the Database. The capacity_notifier, which used to decrement values on a VM deletion only (according to the comments the increment was done in the scheduler) seems to have now disappeared altogether in the move of the notifier to openstack/common ? So I’m sure I’m missing some other even more cunning plan on how to keep the values current, but I can’t for the life of me work out what it is – can someone fill me in please ? Thanks, Phil ___ 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] Routing ReST API Calls by URL
I am attempting to find a workable solution for the following use case, and would like to get feedback from the community about it. There are some situations when it is required to put a proxy in front of multiple API endpoints and route by URL. This allows for more flexible routing/filtering in load balancers and firewalls, and makes it possible to differentiate between services in unified HTTP logs. In the current OpenStack model a typical API endpoint looks something like this: http(s)://hostname:port/api version/account/container/object In essence, separate services have similar URLs, and are separated by the port number. It is difficult to use a request-header-aware proxy to route to a particular endpoint, since there is no clear differentiation between service URLs if the hostname and port are the same. With standard HTTP, this can be handled by using several different hostnames pointing to the same IP. This is particularly a problem with SSL certificates, which need to match the hostname. If the URLs contained a service identifier at the beginning of the URL, this would allow a proxy to make decisions about where to route requests based on the beginning of the URL, for example the URL above would become: http(s)://hostname:port/service/api version/account/container/object e.g. https://api-host:443/compute/v2.0/... https://api-host:443/auth/v2.0/... etc. It seems that the API services are compatible with this through the use of the urlmap configuration by including both versions of the URL: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1: openstack_compute_api_v2 /v2: openstack_compute_api_v2 /compute/: oscomputeversions /compute/v1.1: openstack_compute_api_v2 /compute/v2: openstack_compute_api_v2 Is allowing both forms of this URL in all services likely to break anything down the line? Does this seem like a common enough use case that it should be considered as an addition to the default configuration? Also, as services change (such as nova-volume being replaced by cinder) is there a set of generic service descriptors defined that can be used to abstract from the particular name of the service? Some of these are obvious, like network, but it would be nice to be consistent across versions and instances. Thank you for your feedback, -- Dan Sneddon Senior Engineer, Cloudscaling d...@cloudscaling.com - @dxs on Twitter ___ 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] Routing ReST API Calls by URL
Dan, Adam Young was advocating for something like this. I don't know if a consensus was ever reached, but I thought it was a good idea. https://lists.launchpad.net/openstack/msg10864.html Nate On Jul 13, 2012 5:31 PM, Dan Sneddon d...@cloudscaling.com wrote: I am attempting to find a workable solution for the following use case, and would like to get feedback from the community about it. There are some situations when it is required to put a proxy in front of multiple API endpoints and route by URL. This allows for more flexible routing/filtering in load balancers and firewalls, and makes it possible to differentiate between services in unified HTTP logs. In the current OpenStack model a typical API endpoint looks something like this: http(s)://hostname:port/api version/account/container/object In essence, separate services have similar URLs, and are separated by the port number. It is difficult to use a request-header-aware proxy to route to a particular endpoint, since there is no clear differentiation between service URLs if the hostname and port are the same. With standard HTTP, this can be handled by using several different hostnames pointing to the same IP. This is particularly a problem with SSL certificates, which need to match the hostname. If the URLs contained a service identifier at the beginning of the URL, this would allow a proxy to make decisions about where to route requests based on the beginning of the URL, for example the URL above would become: http(s)://hostname:port/service/api version/account/container/object e.g. https://api-host:443/compute/v2.0/... https://api-host:443/auth/v2.0/... etc. It seems that the API services are compatible with this through the use of the urlmap configuration by including both versions of the URL: [composite:osapi_compute] use = call:nova.api.openstack.urlmap:urlmap_factory /: oscomputeversions /v1.1: openstack_compute_api_v2 /v2: openstack_compute_api_v2 /compute/: oscomputeversions /compute/v1.1: openstack_compute_api_v2 /compute/v2: openstack_compute_api_v2 Is allowing both forms of this URL in all services likely to break anything down the line? Does this seem like a common enough use case that it should be considered as an addition to the default configuration? Also, as services change (such as nova-volume being replaced by cinder) is there a set of generic service descriptors defined that can be used to abstract from the particular name of the service? Some of these are obvious, like network, but it would be nice to be consistent across versions and instances. Thank you for your feedback, -- Dan Sneddon Senior Engineer, Cloudscaling d...@cloudscaling.com - @dxs on Twitter ___ 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] About images list in dashboard
On Fri, Jul 13, 2012 at 10:56 PM, John Postlethwait john.postlethw...@nebula.com wrote: Well, it sounds like this issue only happens in Essex, and is no longer an issue in Folsom, so the bug will just be closed as invalid, as it is now fixed in the newer code... Please backport this bug then. That is, the bug report indeed makes absolutely sense to me. :-) John Postlethwait Nebula, Inc. 206-999-4492 On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote: Thank you for you guys' suggestions. Even so, I'd like to file a bug to track this issue, if someone else have the same problem, they would know what happened and what progressed from the bug trace. Sam On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *John Postlethwait *Sent:* Friday, July 13, 2012 12:05 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] About images list in dashboard ** ** Hi Sam, ** ** Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug ** ** ** ** ** ** John Postlethwait Nebula, Inc. 206-999-4492 ** ** On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. ** ** If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. ** ** ** ** Sam ** ** ** ** On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com wrote: Thank you for your suggestion. ** ** I can see all images in other tenants from dashboard, so I think the images type should be ok. ** ** ** ** ** ** On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 05, 2012 11:20 AM *To:* openstack *Subject:* [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: *Image Name Type Status Public Container Format Actions* CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result)* *** # nova image-list +-+--+- --+--+ | ID | Name | Status |Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel | ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | | 99be14c0-3b15-470b-9e2d-a9d7e2242c7a | CentOS-5.8-x86_64 | ACTIVE | | | a486733f-c011-4fa1-8ce2-553084f9bc0e | ubuntu-11.10-server-amd64 |
Re: [Openstack] Can't attach a RBD volume to an instance
Was this problem ever resolved? I'm having the identical issue right now
(perhaps because I am following Sebastien's guide [0]). I found this
question raised on LP [1], but no helpful responses, and no linked bug. I
can confirm that I can attach an RBD instance manually through virsh, no
problem. So it is not a libvirt thing. It sure appears to be a faulty disk
attachment definition from OpenStack.
I'm running the latest packages on Ubuntu 12.04 for OpensStack (essex) and
Ceph (argonaut).
I can confirm when using nova volume-attach it does not matter what device
you pick, dev/vdb, dev/vdf, whatever. Always fails. /dev/vdb manually
works great.
[0]
http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/
[1] https://answers.launchpad.net/nova/+question/201366
- Travis
On Fri, May 25, 2012 at 8:32 PM, Josh Durgin josh.dur...@inktank.comwrote:
On 05/25/2012 01:31 AM, Sébastien Han wrote:
Hi everyone,
I setup a ceph cluster and I use the RBD driver for nova-volume.
I can create volumes and snapshots but currently I can't attach them to
an instance.
Apparently the volume is detected as busy but it's not, no matter which
name I choose.
I tried from horizon and the command line, same issue.
$ nova --debug volume-attach de3743be-69be-4ec3-8de3-**fc7df6903a97 12
/dev/vdc
connect: (localhost, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
localhost:5000\r\nContent-**Length: 100\r\ncontent-type:
application/json\r\naccept-**encoding: gzip, deflate\r\naccept:
application/json\r\nuser-**agent: python-novaclient\r\n\r\n{**auth:
{tenantName: admin, passwordCredentials: {username: admin,
password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Fri, 25 May 2012 08:29:46 GMT
header: Transfer-Encoding: chunked
connect: (172.17.1.6, 8774)
send: u'GET
/v2/**d1f5d27ccf594cdbb034c8a4123494**e9/servers/de3743be-69be-4ec3-**
8de3-fc7df6903a97
HTTP/1.1\r\nHost: 172.17.1.6:8774
http://172.17.1.6:8774\r\nx-**auth-project-id: admin\r\nx-auth-token:
37ff6354b9114178889128175494c6**66\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-**agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-fc7686dd-7dff-4ea2-b2dd-**be584dadb7c1
header: Content-Type: application/json
header: Content-Length: 1371
header: Date: Fri, 25 May 2012 08:29:46 GMT
send: u'POST
/v2/**d1f5d27ccf594cdbb034c8a4123494**e9/servers/de3743be-69be-4ec3-**
8de3-fc7df6903a97/os-volume_**attachments
HTTP/1.1\r\nHost: 172.17.1.6:8774
http://172.17.1.6:8774\r\**nContent-Length: 60\r\nx-auth-project-id:
admin\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nx-auth-**token:
37ff6354b9114178889128175494c6**66\r\nuser-agent:
python-novaclient\r\ncontent-**type:
application/json\r\n\r\n{**volumeAttachment: {device: /dev/vdc,
volumeId: 12}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-4a22f603-4aad-4ae9-99a2-**6a7bcacf974f
header: Content-Type: application/json
header: Content-Length: 48
header: Date: Fri, 25 May 2012 08:29:46 GMT
$ echo $?
0
See the logs here:
http://paste.openstack.org/**show/18163/http://paste.openstack.org/show/18163/
Hi Seb,
It looks like the DeviceIsBusy exception is raised when libvirt
returns failure for any reason when attaching a volume. Try turning on
debug logging for libvirt and attaching again, and posting the logs
from libvirt.
You might need to upgrade libvirt - the version in Ubuntu 12.04 should
work, or upstream libvirt 0.9.12.
Josh
If you need more information let me know :)
Thank you in advance.
Cheers.
~Seb
__**_
Mailing list:
https://launchpad.net/~**openstackhttps://launchpad.net/%7Eopenstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
https://launchpad.net/~**openstackhttps://launchpad.net/%7Eopenstack
More help :
https://help.launchpad.net/**ListHelphttps://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] [Folsom Testing Packages] Feedback
My bad. I know for the future now. Thank's and sorry for the mistake. Regards On Fri, Jul 13, 2012 at 7:19 PM, Adam Gandelman ad...@canonical.com wrote: On 07/13/2012 05:50 AM, Emilien Macchi wrote: Thank's to Adam Gandelman for the last e-mail about *Folsom Testing Packages* in *Ubuntu* [1]. I would like to share here my feedback and also the Issues I have today with that : - Glance Packaging [2] : Conflict between two packages. - Glance Endpoint does not work with API V2 but works with API V1. If I comment */etc/glance/glance-api-paste.ini* the part about V2, everything works. Maybe it's my bad, I need to understand more what's wrong. Anyway, I did not have this issue with Essex. - Horizon does not work [3] [1] http://www.mail-archive.com/openstack@lists.launchpad.net/msg14298.html [2] https://bugs.launchpad.net/python-glanceclient/+bug/1024281 [3] https://bugs.launchpad.net/horizon/+bug/1024326 Let me know if you have any idea. Regards Thanks Emilien, this is exacly the kind of testing I was hoping to get! In the future, please target bugs against the Ubuntu distro package rather than the upstream project. Thanks again, hope to have those fixed for you soon. Adam Emilien Macchi *System Engineer* *www.stackops.com* | emilien.mac...@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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Emilien Macchi *System Engineer* *www.stackops.com* | emilien.mac...@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
Re: [Openstack] File injection support
On Tue, Jun 12, 2012 at 8:20 AM, Pádraig Brady p...@draigbrady.com wrote:
On 06/12/2012 04:07 PM, Fredric Morenius wrote:
From: Scott Moser [mailto:ssmos...@gmail.com] On Behalf Of Scott Moser
Sent: den 11 juni 2012 23:16
...Without digging around on older versions of OS's and their included
kernel/udev/kpartx i'd have to say that from your message above, and my
testing that running 'kpartx' is no longer necessary. That can reasonably
be expected to be created by the kernel or some other plumbing bits
automatically...
I just now tested to remove the kpartx invocation from
/nova/virt/disk/mount.py, like this:
diff --git a/nova/virt/disk/mount.py b/nova/virt/disk/mount.py
index 11959b2..4d9527b 100644
--- a/nova/virt/disk/mount.py
+++ b/nova/virt/disk/mount.py
@@ -61,25 +61,9 @@ class Mount(object):
if self.partition == -1:
self.error = _('partition search unsupported with %s') %
self.mode
elif self.partition:
-map_path = '/dev/mapper/%sp%s' % (os.path.basename(self.device),
- self.partition)
-assert(not os.path.exists(map_path))
-
-# Note kpartx can output warnings to stderr and succeed
-# Also it can output failures to stderr and succeed
-# So we just go on the existence of the mapped device
-_out, err = utils.trycmd('kpartx', '-a', self.device,
- run_as_root=True,
discard_warnings=True)
-
-# Note kpartx does nothing when presented with a raw image,
-# so given we only use it when we expect a partitioned image,
fail
-if not os.path.exists(map_path):
-if not err:
-err = _('partition %s not found') % self.partition
-self.error = _('Failed to map partitions: %s') % err
-else:
-self.mapped_device = map_path
-self.mapped = True
+#qemu-nbd already has mapped the partition for mounting
+self.mapped_device = '%sp%s' % (self.device, self.partition)
+self.mapped = True
Looks good. That should also support raw through the /dev/loop%s devices.
It might be safer to fallback to kpartx if not exists ...
'%sp%s' % (self.device, self.partition)
That would support kernels before 3.2
I'd also add a comment in the code, that nbd must be mounted with param
max_part=16 or whatever.
Might be totally unrelated to the above issues but I figured I'd throw
it out there. I was messing with file injection today and was getting
odd errors.
Some were due to hitting errors on a previous boot and partitions not
getting cleaned up (e.g. kpartx -d never ran and the /dev/mapper/nbd*
entries were still there, or qemu-nbd was still running). Some of
those were likely a result of my own circumstances.
More interesting though, and what might be of use to other people, the
kpartx -a calls get run and then the code in nova/virt/disk/mount.py
immediately checks for whether or not the newly created
/dev/mapper/nbdXXpX partitions exist. They'd actually get created but
the os.exists call would fail. Apparently the os.exists call was
getting run too soon. I added a time.sleep() after both the 'kpartx
-a' and 'kpartx -d' calls, to give things time to catch up before the
os.exists calls and things worked much better.
___
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] Can't attach a RBD volume to an instance
On 07/13/2012 03:09 PM, Travis Rhoden wrote:
Was this problem ever resolved? I'm having the identical issue right now
(perhaps because I am following Sebastien's guide [0]). I found this
question raised on LP [1], but no helpful responses, and no linked bug. I
can confirm that I can attach an RBD instance manually through virsh, no
problem. So it is not a libvirt thing. It sure appears to be a faulty disk
attachment definition from OpenStack.
I didn't notice this launchpad question before, but I'll copy my answer
below for the mailing list archives:
Right now the RBD driver in OpenStack requires you to have your monitor
addresses in /etc/ceph/ceph.conf. When you have them there, putting them
in the libvirt xml is unnecessary. You do have to make sure that the
unix user who ends up running qemu/kvm has read access to
/etc/ceph/ceph.conf, and e.g. apparmor isn't preventing qemu/kvm from
reading it.
This dependency on /etc/ceph/ceph.conf should be removed in the future.
I'm running the latest packages on Ubuntu 12.04 for OpensStack (essex) and
Ceph (argonaut).
I can confirm when using nova volume-attach it does not matter what device
you pick, dev/vdb, dev/vdf, whatever. Always fails. /dev/vdb manually
works great.
If the answer above doesn't help, what error message do you get?
Is there any info in the libvirt logs for the instance?
Josh
[0]
http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/
[1] https://answers.launchpad.net/nova/+question/201366
- Travis
On Fri, May 25, 2012 at 8:32 PM, Josh Durgin josh.dur...@inktank.comwrote:
On 05/25/2012 01:31 AM, Sébastien Han wrote:
Hi everyone,
I setup a ceph cluster and I use the RBD driver for nova-volume.
I can create volumes and snapshots but currently I can't attach them to
an instance.
Apparently the volume is detected as busy but it's not, no matter which
name I choose.
I tried from horizon and the command line, same issue.
$ nova --debug volume-attach de3743be-69be-4ec3-8de3-**fc7df6903a97 12
/dev/vdc
connect: (localhost, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
localhost:5000\r\nContent-**Length: 100\r\ncontent-type:
application/json\r\naccept-**encoding: gzip, deflate\r\naccept:
application/json\r\nuser-**agent: python-novaclient\r\n\r\n{**auth:
{tenantName: admin, passwordCredentials: {username: admin,
password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Fri, 25 May 2012 08:29:46 GMT
header: Transfer-Encoding: chunked
connect: (172.17.1.6, 8774)
send: u'GET
/v2/**d1f5d27ccf594cdbb034c8a4123494**e9/servers/de3743be-69be-4ec3-**
8de3-fc7df6903a97
HTTP/1.1\r\nHost: 172.17.1.6:8774
http://172.17.1.6:8774\r\nx-**auth-project-id: admin\r\nx-auth-token:
37ff6354b9114178889128175494c6**66\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-**agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-fc7686dd-7dff-4ea2-b2dd-**be584dadb7c1
header: Content-Type: application/json
header: Content-Length: 1371
header: Date: Fri, 25 May 2012 08:29:46 GMT
send: u'POST
/v2/**d1f5d27ccf594cdbb034c8a4123494**e9/servers/de3743be-69be-4ec3-**
8de3-fc7df6903a97/os-volume_**attachments
HTTP/1.1\r\nHost: 172.17.1.6:8774
http://172.17.1.6:8774\r\**nContent-Length: 60\r\nx-auth-project-id:
admin\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nx-auth-**token:
37ff6354b9114178889128175494c6**66\r\nuser-agent:
python-novaclient\r\ncontent-**type:
application/json\r\n\r\n{**volumeAttachment: {device: /dev/vdc,
volumeId: 12}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-4a22f603-4aad-4ae9-99a2-**6a7bcacf974f
header: Content-Type: application/json
header: Content-Length: 48
header: Date: Fri, 25 May 2012 08:29:46 GMT
$ echo $?
0
See the logs here:
http://paste.openstack.org/**show/18163/http://paste.openstack.org/show/18163/
Hi Seb,
It looks like the DeviceIsBusy exception is raised when libvirt
returns failure for any reason when attaching a volume. Try turning on
debug logging for libvirt and attaching again, and posting the logs
from libvirt.
You might need to upgrade libvirt - the version in Ubuntu 12.04 should
work, or upstream libvirt 0.9.12.
Josh
If you need more information let me know :)
Thank you in advance.
Cheers.
~Seb
__**_
Mailing list:
https://launchpad.net/~**openstackhttps://launchpad.net/%7Eopenstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
https://launchpad.net/~**openstackhttps://launchpad.net/%7Eopenstack
More help :
https://help.launchpad.net/**ListHelphttps://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] About images list in dashboard
I agree if someone wants to commit a backported fix. This makes sense to do. It's a pretty significant bug for essex users. -Matt On Fri, Jul 13, 2012 at 3:00 PM, Christian Parpart tra...@gmail.com wrote: On Fri, Jul 13, 2012 at 10:56 PM, John Postlethwait john.postlethw...@nebula.com wrote: Well, it sounds like this issue only happens in Essex, and is no longer an issue in Folsom, so the bug will just be closed as invalid, as it is now fixed in the newer code... Please backport this bug then. That is, the bug report indeed makes absolutely sense to me. :-) John Postlethwait Nebula, Inc. 206-999-4492 On Friday, July 13, 2012 at 1:36 PM, Sam Su wrote: Thank you for you guys' suggestions. Even so, I'd like to file a bug to track this issue, if someone else have the same problem, they would know what happened and what progressed from the bug trace. Sam On Fri, Jul 13, 2012 at 12:43 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: Glance pagination was added in Folsom. Adding a bug for this won’t help since it’s already been added in the current code. ** ** **- **Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *John Postlethwait *Sent:* Friday, July 13, 2012 12:05 PM *To:* Sam Su *Cc:* openstack *Subject:* Re: [Openstack] About images list in dashboard ** ** Hi Sam, ** ** Would you mind filing a bug against Horizon with the details so that we can get it fixed? You can do so here: https://bugs.launchpad.net/horizon/+filebug ** ** ** ** ** ** John Postlethwait Nebula, Inc. 206-999-4492 ** ** On Thursday, July 12, 2012 at 3:55 PM, Sam Su wrote: I finally found why this happened. ** ** If in one tenant, there are more than 30 images and snapshots so that glance cannot return the images list in one response, some images and snapshots will not be seen in the page Images Snapshots of Horizon. ** ** ** ** Sam ** ** ** ** On Thu, Jul 5, 2012 at 1:19 PM, Sam Su susltd...@gmail.com wrote: Thank you for your suggestion. ** ** I can see all images in other tenants from dashboard, so I think the images type should be ok. ** ** ** ** ** ** On Thu, Jul 5, 2012 at 11:54 AM, Gabriel Hurley gabriel.hur...@nebula.com wrote: The “Project Dashboard” hides images with an AKI or AMI image type (as they’re not launchable and generally shouldn’t be edited by “normal” users). You can see those in the “Admin Dashboard” if you want to edit them. So my guess is that the kernel and ramdisk images are being hidden correctly and your “ubuntu-11.10-server-amd64” and “ubuntu-12.04-server-amd64” have the wrong image type set. All the best, - Gabriel *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Sam Su *Sent:* Thursday, July 05, 2012 11:20 AM *To:* openstack *Subject:* [Openstack] About images list in dashboard Hi, I have an Openstack Essex environment. The nova control services, glance, keystone and dashboard are all deployed in one server. Now I encounter a strange problem. I can only see two images (all images are set is_public=true) in the tenant 'demo' from dashboard, i.e., Horizon, as below: *Image Name Type Status Public Container Format Actions* CentOS-6.2-x86_64 Image Active YesOVF Launch CentOS-5.8-x86_64 Image Active YesOVF Launch However, when I use 'nova image-list' with the same credential for the same tenant 'demo', I can see many more images (see the following result) # nova image-list +-+--+- --+--+ | ID | Name | Status |Server | +-+--+--- +--+ | 18b130ce-a815-4671-80e8-9308a7b6fc6d | ubuntu-12.04-server-amd64 | ACTIVE | | | 388d16ce-b80b-4e9e-b8db-db6dce6f4a83 | ubuntu-12.04-server-amd64-kernel| ACTIVE | | | 8d9505ce-0974-431d-a53d-e9ed6dc89033 | CentOS-6.2-x86_64 | ACTIVE | | |
[Openstack] OpenStack Community Weekly Newsletter (July 6-13)
Highlights of the week G stands for Grizzly Results of the naming poll for next OpenStack release are in, and the G release will be named Grizzly. The regular poll selected Gazelle (35 votes), with Gilroy (27 votes) being a close second. But the Grizzly revolt poll showed overwhelming support for the Grizzly name (88 votes) rather than going with the results of the regular poll (46 votes). The Waldon exception (accepting elements of the state/country flag in addition to city/county names) will be added to our naming rules for future naming contests Some clarifications about Cinder With the promotion of Cinder to OpenStack core project, Cinders PTL John Griffith explained what the project does and what the future release, Grizzly, may look like. OpenStack operators are invited to give their opinion and help developers take the best decision. Lots Of OpenStack At OSCON 2012 Only a few days to OSCON: find the full list of talks related to OpenStack and dont forget to RSVP fort the OpenStack Party at Spirit of 77 (500 NE MLK Blvd.) on July 18th. OpenStack Summit Fall 2012: Tickets Sponsorships now available The OpenStack Summit is coming to San Diego October 15th-18th at the Manchester Grand Hyatt . Check out the new Summit websiteto learn more, buy tickets, or to become a sponsor. The early bird price for tickets is $400 until August 31st, then it goes up to $600, so please buy your ticket now! Everybody is invited to participate, there are no caps like in past events (the only limit is the physical capacity of the location). OpenStack Overview Operational Details of a Large Python Project Pdraig Brady spoke at EuroPython 2012 about OpenStack. His talk was recorded (audio starts at minute 11:40). Tips and tricks By Michael Still: how to use glance replication By Yong Sheng Gong: Openstacks Floating IPs Upcoming Events OpenStack India Users July meetup Jul 14, 2012 Bangalore, India Details The 1st London OpenStack Meetup Jul 25, 2012 London, UK Details OSCON Jul 16 20, 2012 Portland, OR 13th International Free Software Forum OpenStack Track Jul 25 28, 2012 Porto Alegre, Brazil Coordination 2012 OpenStack APEC Conference Aug 10 11, 2012 Bejing+Shanghai, China Details OpenStack Summit Oct 15 18, 2012 San Diego, CA Other news New mailing lists: http://wiki.openstack.org/MailingLists Subscribe to the relevant ones for you. OpenStack ProjectMeeting logs: 2012-07-10: Summary and full meeting log Welcome new contributors Celebrating the first patches submitted this week by: Tim Daly Jr, Yahoo The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment. ___ 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] [cinder] Nova-volume vs. Cinder in Folsom
Disagreements and misunderstanding concerning etiquette and upgrading Cassandra aside, this thread has three major themes: 1) the relative ease or burden of upgrade paths 2) compatibility between versions and 3) what OpenStack values when making decisions. I believe the first two hinge on the third and the overriding theme is how do the inevitable burdens of the choices made impact individuals and organizations. OpenStack choices impact at least these different personas across different organizations: core, operators and consumers. Those groups can obviously be segmented further. Work in core has been done by individuals with a wide range of motives and interests. Operators are in stages of deploying and supporting services of various shapes and sizes. Consumers represent everyone trying to integrate or use OpenStack in one or all of it's incarnations. Some people fit into more than one of these groups. The last two groups are clearly under represented in OpenStack decision making across the board. This impacts every decision from what code gets written to how releases are scheduled and gated. I personally believe this imbalance seriously jeopardizes the stated OpenStack mission. In this particular case, I chose option 1 under the following assumptions (which may be wrong): - the api for the end user would not change - the code for the service is essentially the same, it is just being renamed - option 2 doesn't lower risk or burden for anyone, it just postpones them, while increasing complexity, confusion and future burdens for core development and probably operators as well Under these assumptions, the impact on users would be negligible if any, and for the operators of existing deployments the burden is copying a database, changing some configurations and starting some services. Data and consequently storage should arguably be the most important thing in the hierarchy of priorities. Any risk of losing user data should be given the highest consideration. My assumption was that this could be applied to running deployments without risk of data loss. On the question of compatibility, my assumption is this a non-issue for the moment. On the question of an upgrade path and the relative ease of deployment, my assumption is this is no worse than any of the other upgrades. On the question of how we make decisions as a community and how they are perceived in the ecosystem at large, I believe this thread reveals more questions than answers. These assumptions could be totally wrong. If they are correct, I still advocate option 1. If they are wrong, or the preponderance of support is for option 2, I would support that and hope we collectively attempt to mitigate the complexity and confusion by over communicating with the community and each other. In specific, I think getting more information from operators and users is generally good. Ultimately, if OpenStack cannot be operated and utilized, the mission will fail. I'd hope that doesn't have to be done in a reactionary way and we can collectively get better at considering the cascading impacts of the choices we make both for operators, users and also across projects. I don't agree with George Reese on every point and he clearly knows nothing about Cassandra, but I don't have a problem with his message or his language choices. In this case, he is in a position to provide valuable insights into the current state of the OpenStack ecosystem, both relative to itself and most other cloud platforms. He's only mad because he cares. I prefer that to silent apathy. For the future, OpenStack has to come to terms with what it wants to be when it grows up. API compatibility should not be taken lightly. It doesn't mean things can't change, for me it means being mindful about how things are versioned and communicated. This is all about attitude and discipline. Ease of deployment and operations has been left as an exercise for the reader. Configuration management and packaging is something people understand to various degrees. Reliability and availability have been left up to deployment specific architectural choices. API end points can be scaled like any http service. Scaling up and scaling out relational databases is something people know how to do. There are technically more sophisticated ways to handle many of these issues by giving them more consideration in the projects and making openstack services more aware of themselves and each other. These changes would be a considerable undertaking and should not be taken lightly. So far, we haven't collectively had the patience or stomach to move in this direction, and in some places where progress has been made, it hasn't been pushed back upstream for a variety of reasons, real or imagined. I personally hope OpenStack will one day be able to deploy itself on bare metal and sensibly adding or removing capacity is relatively trivial compared to today. As for community, I am personally disappointed by
Re: [Openstack] File injection support
On 07/14/2012 12:09 AM, Mark Moseley wrote:
On Tue, Jun 12, 2012 at 8:20 AM, Pádraig Brady p...@draigbrady.com wrote:
On 06/12/2012 04:07 PM, Fredric Morenius wrote:
From: Scott Moser [mailto:ssmos...@gmail.com] On Behalf Of Scott Moser
Sent: den 11 juni 2012 23:16
...Without digging around on older versions of OS's and their included
kernel/udev/kpartx i'd have to say that from your message above, and
my testing that running 'kpartx' is no longer necessary. That can
reasonably be expected to be created by the kernel or some other plumbing
bits automatically...
I just now tested to remove the kpartx invocation from
/nova/virt/disk/mount.py, like this:
diff --git a/nova/virt/disk/mount.py b/nova/virt/disk/mount.py
index 11959b2..4d9527b 100644
--- a/nova/virt/disk/mount.py
+++ b/nova/virt/disk/mount.py
@@ -61,25 +61,9 @@ class Mount(object):
if self.partition == -1:
self.error = _('partition search unsupported with %s') %
self.mode
elif self.partition:
-map_path = '/dev/mapper/%sp%s' %
(os.path.basename(self.device),
- self.partition)
-assert(not os.path.exists(map_path))
-
-# Note kpartx can output warnings to stderr and succeed
-# Also it can output failures to stderr and succeed
-# So we just go on the existence of the mapped device
-_out, err = utils.trycmd('kpartx', '-a', self.device,
- run_as_root=True,
discard_warnings=True)
-
-# Note kpartx does nothing when presented with a raw image,
-# so given we only use it when we expect a partitioned image,
fail
-if not os.path.exists(map_path):
-if not err:
-err = _('partition %s not found') % self.partition
-self.error = _('Failed to map partitions: %s') % err
-else:
-self.mapped_device = map_path
-self.mapped = True
+#qemu-nbd already has mapped the partition for mounting
+self.mapped_device = '%sp%s' % (self.device, self.partition)
+self.mapped = True
Looks good. That should also support raw through the /dev/loop%s devices.
It might be safer to fallback to kpartx if not exists ...
'%sp%s' % (self.device, self.partition)
That would support kernels before 3.2
I'd also add a comment in the code, that nbd must be mounted with param
max_part=16 or whatever.
Might be totally unrelated to the above issues but I figured I'd throw
it out there. I was messing with file injection today and was getting
odd errors.
Some were due to hitting errors on a previous boot and partitions not
getting cleaned up (e.g. kpartx -d never ran and the /dev/mapper/nbd*
entries were still there, or qemu-nbd was still running). Some of
those were likely a result of my own circumstances.
More interesting though, and what might be of use to other people, the
kpartx -a calls get run and then the code in nova/virt/disk/mount.py
immediately checks for whether or not the newly created
/dev/mapper/nbdXXpX partitions exist. They'd actually get created but
the os.exists call would fail. Apparently the os.exists call was
getting run too soon. I added a time.sleep() after both the 'kpartx
-a' and 'kpartx -d' calls, to give things time to catch up before the
os.exists calls and things worked much better.
Sigh.
The amount of synchronization bugs I've noticed in lower
Linux layers lately is worrying.
Anyway I've created a bug for this:
https://bugs.launchpad.net/nova/+bug/1024586
cheers,
Pádraig
___
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] File injection support
On Friday, July 13, 2012 at 20:35 PM, Pádraig Brady wrote: More interesting though, and what might be of use to other people, the kpartx -a calls get run and then the code in nova/virt/disk/mount.py immediately checks for whether or not the newly created /dev/mapper/nbdXXpX partitions exist. They'd actually get created but the os.exists call would fail. Apparently the os.exists call was getting run too soon. I added a time.sleep() after both the 'kpartx -a' and 'kpartx -d' calls, to give things time to catch up before the os.exists calls and things worked much better. Sigh. The amount of synchronization bugs I've noticed in lower Linux layers lately is worrying. The kernel tools can certainly be asynchronous at times. Perhaps try to see if using inotify would solve this. It is platform-dependent, but it is the best way to solve these problems without race conditions. If we're calling kpartx, platform independence is unlikely to be an issue anyway. However, if compatibility is desired, BSD/MacOS provide similar functionality via kqueue, and Windows FindFirstChangeNotification. Regards, Eric Windisch ___ 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] Can't attach a RBD volume to an instance
Josh,
Thanks so much for the pointers. I did not figure out that libvirt was
trying to read /etc/ceph/ceph.conf. It was in fact being denied by
apparmor. I fixed my problem by editing /etc/apparmor.d/libvirt/TEMPLATE
and adding /etc/ceph/** r, to the template. Now it works for newly
spawned VMs.
Again, thanks a lot.
- Travis
On Fri, Jul 13, 2012 at 7:40 PM, Josh Durgin josh.dur...@inktank.comwrote:
On 07/13/2012 03:09 PM, Travis Rhoden wrote:
Was this problem ever resolved? I'm having the identical issue right now
(perhaps because I am following Sebastien's guide [0]). I found this
question raised on LP [1], but no helpful responses, and no linked bug. I
can confirm that I can attach an RBD instance manually through virsh, no
problem. So it is not a libvirt thing. It sure appears to be a faulty
disk
attachment definition from OpenStack.
I didn't notice this launchpad question before, but I'll copy my answer
below for the mailing list archives:
Right now the RBD driver in OpenStack requires you to have your monitor
addresses in /etc/ceph/ceph.conf. When you have them there, putting them in
the libvirt xml is unnecessary. You do have to make sure that the unix user
who ends up running qemu/kvm has read access to /etc/ceph/ceph.conf, and
e.g. apparmor isn't preventing qemu/kvm from reading it.
This dependency on /etc/ceph/ceph.conf should be removed in the future.
I'm running the latest packages on Ubuntu 12.04 for OpensStack (essex) and
Ceph (argonaut).
I can confirm when using nova volume-attach it does not matter what device
you pick, dev/vdb, dev/vdf, whatever. Always fails. /dev/vdb manually
works great.
If the answer above doesn't help, what error message do you get?
Is there any info in the libvirt logs for the instance?
Josh
[0]
http://www.sebastien-han.fr/**blog/2012/06/10/introducing-**
ceph-to-openstack/http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/
[1]
https://answers.launchpad.net/**nova/+question/201366https://answers.launchpad.net/nova/+question/201366
- Travis
On Fri, May 25, 2012 at 8:32 PM, Josh Durgin josh.dur...@inktank.com**
wrote:
On 05/25/2012 01:31 AM, Sébastien Han wrote:
Hi everyone,
I setup a ceph cluster and I use the RBD driver for nova-volume.
I can create volumes and snapshots but currently I can't attach them to
an instance.
Apparently the volume is detected as busy but it's not, no matter which
name I choose.
I tried from horizon and the command line, same issue.
$ nova --debug volume-attach de3743be-69be-4ec3-8de3-fc7df6903a97
12
/dev/vdc
connect: (localhost, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
localhost:5000\r\nContent-Length: 100\r\ncontent-type:
application/json\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nuser-agent: python-novaclient\r\n\r\n{
auth:
{tenantName: admin, passwordCredentials: {username: admin,
password: admin}}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: Content-Type: application/json
header: Vary: X-Auth-Token
header: Date: Fri, 25 May 2012 08:29:46 GMT
header: Transfer-Encoding: chunked
connect: (172.17.1.6, 8774)
send: u'GET
/v2/d1f5d27ccf594cdbb034c8a4123494e9/servers/de3743be-69be-**
4ec3-**
8de3-fc7df6903a97
HTTP/1.1\r\nHost: 172.17.1.6:8774
http://172.17.1.6:8774\r\nx-auth-project-id:
admin\r\nx-auth-token:
37ff6354b9114178889128175494c666\r\naccept-encoding: gzip,
deflate\r\naccept: application/json\r\nuser-agent:
python-novaclient\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-fc7686dd-7dff-4ea2-b2dd-
be584dadb7c1
header: Content-Type: application/json
header: Content-Length: 1371
header: Date: Fri, 25 May 2012 08:29:46 GMT
send: u'POST
/v2/d1f5d27ccf594cdbb034c8a4123494e9/servers/de3743be-69be-**
4ec3-**
8de3-fc7df6903a97/os-volume_attachments
HTTP/1.1\r\nHost: 172.17.1.6:8774
http://172.17.1.6:8774\r\nContent-Length:
60\r\nx-auth-project-id:
admin\r\naccept-encoding: gzip, deflate\r\naccept:
application/json\r\nx-auth-token:
37ff6354b9114178889128175494c666\r\nuser-agent:
python-novaclient\r\ncontent-type:
application/json\r\n\r\n{volumeAttachment: {device: /dev/vdc,
volumeId: 12}}'
reply: 'HTTP/1.1 200 OK\r\n'
header: X-Compute-Request-Id: req-4a22f603-4aad-4ae9-99a2-
6a7bcacf974f
header: Content-Type: application/json
header: Content-Length: 48
header: Date: Fri, 25 May 2012 08:29:46 GMT
$ echo $?
0
See the logs here:
http://paste.openstack.org/show/18163/http://paste.openstack.org/**show/18163/
http://paste.**openstack.org/show/18163/http://paste.openstack.org/show/18163/
Hi Seb,
It looks like the DeviceIsBusy exception is raised when libvirt
returns failure for any reason when attaching a volume. Try turning on
debug logging for libvirt and attaching again, and posting the logs
from libvirt.
You might need to upgrade
[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_python-glanceclient_trunk #20
Title: precise_folsom_python-glanceclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_python-glanceclient_trunk/20/Project:precise_folsom_python-glanceclient_trunkDate of build:Fri, 13 Jul 2012 12:01:53 -0400Build duration:3 min 15 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd --is-public to image-createby bcwaldoneditglanceclient/v1/shell.pyConsole Output[...truncated 1622 lines...]Build-Time: 3Distribution: precise-folsomFail-Stage: buildInstall-Time: 54Job: python-glanceclient_2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1.dscPackage: python-glanceclientPackage-Time: 85Source-Version: 2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1Space: 648Status: attemptedVersion: 2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1Finished at 20120713-1205Build needed 00:01:25, 648k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-glanceclient_2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-glanceclient/precise-folsom-proposed /tmp/tmp_F_Lng/python-glanceclientmk-build-deps -i -r -t apt-get -y /tmp/tmp_F_Lng/python-glanceclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log cf8613e76d4682c924a900a17b43197d569d7ad3..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-glanceclient/precise-folsom --forcedch -b -D precise --newversion 2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-glanceclient_2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A python-glanceclient_2012.2~0.1.1.24.49bc6f9+git201207131201~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-glanceclient_2012.2~0.1.1.24.49bc6f9+git201207131201~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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'python-glanceclient_2012.2~0.1.1.24.49bc6f9+git201207131201~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_horizon_trunk #47
Title: quantal_folsom_horizon_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_horizon_trunk/47/Project:quantal_folsom_horizon_trunkDate of build:Fri, 13 Jul 2012 16:31:54 -0400Build duration:2 min 9 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdded always-enabled submit button selectorby t.trifonovedithorizon/dashboards/settings/project/templates/project/_openrc.htmledithorizon/dashboards/settings/ec2/templates/ec2/download_form.htmledithorizon/static/horizon/js/horizon.forms.jsConsole Output[...truncated 1396 lines...]Hunk #2 succeeded at 271 (offset -9 lines).Applying patch turn-off-debug.patchpatching file openstack_dashboard/local/local_settings.py.exampleApplying patch use-memcache.patchpatching file openstack_dashboard/local/local_settings.py.exampleApplying patch fix-ubuntu-tests.patchpatching file horizon/tests/testsettings.pypatching file run_tests.shHunk #1 FAILED at 266.1 out of 1 hunk FAILED -- rejects in file run_tests.shPatch fix-ubuntu-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8e25c2eb-5e7f-42ac-bbd4-581ae05622c2', '-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-201207131631/git archive master --format tar --prefix horizon-2012.2-201207131631/git log -n1 --no-merges --pretty=format:%Hgit log f3dc3b93c49d922505b2d15e6b064ba9ed716413..HEAD --no-merges --pretty=format:[%h] %sbzr branch lp:~openstack-ubuntu-testing/horizon/quantal-folsom-proposed horizonbzr merge lp:~openstack-ubuntu-testing/horizon/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207131631~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207131631~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucmk-build-deps -i -r -t apt-get -y /tmp/tmpKVnQyI/horizon/debian/controlbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8e25c2eb-5e7f-42ac-bbd4-581ae05622c2', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8e25c2eb-5e7f-42ac-bbd4-581ae05622c2', '-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 Failure: quantal_folsom_nova_trunk #148
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/148/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 16:31:55 -0400Build duration:3 min 25 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUse explicit destination user in xenapi rsync callby johannes.erdfelteditplugins/xenserver/xenapi/etc/xapi.d/plugins/migrationExclude openstack-common from pep8 checks.by dprinceeditrun_tests.shedittox.iniFix RuntimeWarning nova_manage not foundby jogoeditnova/tests/test_nova_manage.pyConsole Output[...truncated 3758 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-d821233c-11ca-40e2-b2d2-750d9455e63e', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpyYi_og/novamk-build-deps -i -r -t apt-get -y /tmp/tmpyYi_og/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207131632~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207131632~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-d821233c-11ca-40e2-b2d2-750d9455e63e', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-d821233c-11ca-40e2-b2d2-750d9455e63e', '-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 Failure: precise_folsom_nova_trunk #151
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/151/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 16:34:05 -0400Build duration:3 min 29 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUse explicit destination user in xenapi rsync callby johannes.erdfelteditplugins/xenserver/xenapi/etc/xapi.d/plugins/migrationExclude openstack-common from pep8 checks.by dprinceedittox.inieditrun_tests.shFix RuntimeWarning nova_manage not foundby jogoeditnova/tests/test_nova_manage.pyConsole Output[...truncated 2973 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f29726b5-033e-4ce2-aa70-892c59024686', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpmCsHMT/novamk-build-deps -i -r -t apt-get -y /tmp/tmpmCsHMT/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207131634~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207131634~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f29726b5-033e-4ce2-aa70-892c59024686', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-f29726b5-033e-4ce2-aa70-892c59024686', '-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 #152
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/152/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 17:31:55 -0400Build duration:3 min 12 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesAttach ISO as separate disk if given proper instruction.by josheditnova/virt/libvirt/driver.pyConsole Output[...truncated 2975 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-2b5f83b7-d43c-4324-8c82-c7c2f42fbc8f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpM4ZBOp/novamk-build-deps -i -r -t apt-get -y /tmp/tmpM4ZBOp/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207131732~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207131732~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-2b5f83b7-d43c-4324-8c82-c7c2f42fbc8f', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-2b5f83b7-d43c-4324-8c82-c7c2f42fbc8f', '-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: quantal_folsom_nova_trunk #150
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/150/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:01:54 -0400Build duration:2 min 52 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesExtension to show usage of limited resources in /limits response.by alex.meadeaddnova/api/openstack/compute/contrib/used_limits.pyaddnova/tests/api/openstack/compute/contrib/test_used_limits.pyConsole Output[...truncated 3772 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-2a695895-c209-4d23-955c-33cc7403d35d', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpyV2ByM/novamk-build-deps -i -r -t apt-get -y /tmp/tmpyV2ByM/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207131802~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207131802~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-2a695895-c209-4d23-955c-33cc7403d35d', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-2a695895-c209-4d23-955c-33cc7403d35d', '-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 #153
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/153/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:01:54 -0400Build duration:3 min 5 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesExtension to show usage of limited resources in /limits response.by alex.meadeaddnova/api/openstack/compute/contrib/used_limits.pyaddnova/tests/api/openstack/compute/contrib/test_used_limits.pyConsole Output[...truncated 2979 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-21d34e4b-5745-4a72-8f24-6e4be9825f22', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpezFmKo/novamk-build-deps -i -r -t apt-get -y /tmp/tmpezFmKo/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207131802~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207131802~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-21d34e4b-5745-4a72-8f24-6e4be9825f22', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-21d34e4b-5745-4a72-8f24-6e4be9825f22', '-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: quantal_folsom_nova_trunk #151
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/151/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:31:56 -0400Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix SADeprecationWarning: useexisting is deprecatedby jogoeditnova/db/sqlalchemy/migrate_repo/versions/087_add_uuid_to_bw_usage_cache.pyConsole Output[...truncated 3778 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5ce46563-6b70-4e62-899d-9003071d09de', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpATu5Ai/novamk-build-deps -i -r -t apt-get -y /tmp/tmpATu5Ai/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207131832~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207131832~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5ce46563-6b70-4e62-899d-9003071d09de', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5ce46563-6b70-4e62-899d-9003071d09de', '-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 #154
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/154/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 18:31:55 -0400Build duration:3 min 24 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix SADeprecationWarning: useexisting is deprecatedby jogoeditnova/db/sqlalchemy/migrate_repo/versions/087_add_uuid_to_bw_usage_cache.pyConsole Output[...truncated 2981 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bdf795b6-f117-4cb6-86de-df2e8adb81a4', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpoUmq5H/novamk-build-deps -i -r -t apt-get -y /tmp/tmpoUmq5H/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207131832~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207131832~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bdf795b6-f117-4cb6-86de-df2e8adb81a4', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-bdf795b6-f117-4cb6-86de-df2e8adb81a4', '-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: quantal_folsom_nova_trunk #152
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/152/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 19:01:56 -0400Build duration:3 min 26 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix snapshots tests failingby gheeditnova/tests/test_libvirt.pyFix spelling in docstringsby jogoeditnova/compute/manager.pyConsole Output[...truncated 3789 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-b1dadf4f-63cc-4770-a897-abeb6acc0c04', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpn7LkAn/novamk-build-deps -i -r -t apt-get -y /tmp/tmpn7LkAn/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207131903~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207131903~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-b1dadf4f-63cc-4770-a897-abeb6acc0c04', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-b1dadf4f-63cc-4770-a897-abeb6acc0c04', '-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: quantal_folsom_nova_trunk #153
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/153/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 19:31:54 -0400Build duration:2 min 52 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesJanitorial: Catch rpc up with a change in commonby abogotteditnova/openstack/common/rpc/impl_fake.pyeditnova/openstack/common/notifier/log_notifier.pyeditnova/openstack/common/rpc/impl_zmq.pyeditnova/openstack/common/rpc/impl_qpid.pyConsole Output[...truncated 3795 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f2a64b6a-d302-4b98-9618-19d376ba0a73', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmp6jrnAD/novamk-build-deps -i -r -t apt-get -y /tmp/tmp6jrnAD/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207131932~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207131932~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f2a64b6a-d302-4b98-9618-19d376ba0a73', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f2a64b6a-d302-4b98-9618-19d376ba0a73', '-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 #156
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/156/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 19:31:54 -0400Build duration:3 min 25 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesJanitorial: Catch rpc up with a change in commonby abogotteditnova/openstack/common/notifier/log_notifier.pyeditnova/openstack/common/rpc/impl_fake.pyeditnova/openstack/common/rpc/impl_zmq.pyeditnova/openstack/common/rpc/impl_qpid.pyConsole Output[...truncated 2986 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-73ac7e47-3556-4673-acd1-5986fc818cdd', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpmp5P8E/novamk-build-deps -i -r -t apt-get -y /tmp/tmpmp5P8E/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207131932~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207131932~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-73ac7e47-3556-4673-acd1-5986fc818cdd', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-73ac7e47-3556-4673-acd1-5986fc818cdd', '-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: quantal_folsom_nova_trunk #155
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/155/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 20:31:55 -0400Build duration:2 min 36 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesadd network creation call to network.api.APIby aababiloveditnova/network/api.pynetwork manager returns empty list, not raise an exceptionby aababiloveditnova/network/manager.pyConsole Output[...truncated 3842 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-c1422472-f689-455d-aedd-ea596e763347', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpI9TTvG/novamk-build-deps -i -r -t apt-get -y /tmp/tmpI9TTvG/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207132032~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207132032~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-c1422472-f689-455d-aedd-ea596e763347', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-c1422472-f689-455d-aedd-ea596e763347', '-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 #158
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/158/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 20:31:54 -0400Build duration:3 min 5 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesadd network creation call to network.api.APIby aababiloveditnova/network/api.pynetwork manager returns empty list, not raise an exceptionby aababiloveditnova/network/manager.pyConsole Output[...truncated 3001 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-88187ff2-8ad7-4466-ad7e-5520672ca7a9', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpduWCy_/novamk-build-deps -i -r -t apt-get -y /tmp/tmpduWCy_/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207132032~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207132032~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-88187ff2-8ad7-4466-ad7e-5520672ca7a9', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-88187ff2-8ad7-4466-ad7e-5520672ca7a9', '-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 #159
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/159/Project:precise_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 22:31:54 -0400Build duration:3 min 32 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSync gettextutils fixes from openstack-common.by rbryanteditnova/openstack/common/policy.pyeditnova/openstack/common/rpc/matchmaker.pyeditnova/openstack/common/notifier/rabbit_notifier.pyeditnova/openstack/common/notifier/list_notifier.pyeditnova/openstack/common/log.pyeditnova/openstack/common/rpc/amqp.pyeditnova/openstack/common/notifier/api.pyConsole Output[...truncated 3003 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-69c0144f-8be5-4126-9c91-0635541e670f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmp9Sje4r/novamk-build-deps -i -r -t apt-get -y /tmp/tmp9Sje4r/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201207132232~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201207132232~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-69c0144f-8be5-4126-9c91-0635541e670f', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-69c0144f-8be5-4126-9c91-0635541e670f', '-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: quantal_folsom_nova_trunk #156
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/156/Project:quantal_folsom_nova_trunkDate of build:Fri, 13 Jul 2012 22:35:27 -0400Build duration:2 min 24 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSync gettextutils fixes from openstack-common.by rbryanteditnova/openstack/common/notifier/rabbit_notifier.pyeditnova/openstack/common/rpc/amqp.pyeditnova/openstack/common/notifier/api.pyeditnova/openstack/common/rpc/matchmaker.pyeditnova/openstack/common/notifier/list_notifier.pyeditnova/openstack/common/log.pyeditnova/openstack/common/policy.pyConsole Output[...truncated 3848 lines...]patching file plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhostApplying patch fix-ubuntu-tests.patchpatching file nova/tests/test_api.pyApplying patch fix-docs-build-without-network.patchpatching file doc/source/conf.pyApplying patch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patchpatching file tools/hacking.pypatching file tools/test-requirespatching file tox.iniHunk #1 FAILED at 17.1 out of 1 hunk FAILED -- rejects in file tox.iniPatch 0001-Update-tools-hacking-for-pep8-1.2-and-beyond.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/buildERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5335acd0-7370-4a4d-8602-8e1937ca7d02', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpW4oqHH/novamk-build-deps -i -r -t apt-get -y /tmp/tmpW4oqHH/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 43677fc6dab76d9b6ad0375eba4b3c2a78e5b405..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207132236~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207132236~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5335acd0-7370-4a4d-8602-8e1937ca7d02', '-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 135, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5335acd0-7370-4a4d-8602-8e1937ca7d02', '-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
