Re: [Openstack] Quantum -. Multi-Plugin and support for provisioning of other devices.
Hi Dan, Can you give us some insight into CINDER component of folsom release. Thanks in advance. -balaji On Mon, Sep 10, 2012 at 10:28 PM, Dan Wendlandt d...@nicira.com wrote: Yes, Tim is correct that we expect to discuss load-balancing capabilities at the Grizzly summit. This is a topic for discussion at the summit, but I expect that it will be possible to run many different types of load balancers independent of your choice of the core L2/L3 plugin you're using to run Quantum (perhaps this is what you're getting at with mentioning 'multi-plugins'). As far as storage devices that require network access, I suspect that would more be under the purview of something like Cinder, which may need to integrate with Quantum (similar to Nova's integration with Quantum) if the goal is to plug storage devices into networks directly. Dan On Sun, Sep 9, 2012 at 10:56 PM, Tim Bell tim.b...@cern.ch wrote: There has been some load balancing discussion and more is due at the summit. The various current activities are summarised in http://wiki.openstack.org/Quantum/LBaaS Can you explain what you mean by storage devices with respect to Quantum ? The storage activities are underway as part of Cinder. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Endre Karlson Sent: 09 September 2012 19:57 To: openstack@lists.launchpad.net Subject: [Openstack] Quantum -. Multi-Plugin and support for provisioning of other devices. Hi, I am wondering if there are any community plans to support to use Quantum to provision up interfaces on other devices in areas of say LoadBalancers, Storage devices etc and if there are plans to support multi-active plugins in Quantum for this? Is there a timeframe maybe? Endre. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Quantum -. Multi-Plugin and support for provisioning of other devices.
On Wed, Sep 12, 2012 at 2:09 PM, balaji patnala patnala...@gmail.comwrote: Hi Dan, Can you give us some insight into CINDER component of folsom release. http://www.mirantis.com/blog/openstack-cinder-first-look/ Thanks in advance. -balaji On Mon, Sep 10, 2012 at 10:28 PM, Dan Wendlandt d...@nicira.com wrote: Yes, Tim is correct that we expect to discuss load-balancing capabilities at the Grizzly summit. This is a topic for discussion at the summit, but I expect that it will be possible to run many different types of load balancers independent of your choice of the core L2/L3 plugin you're using to run Quantum (perhaps this is what you're getting at with mentioning 'multi-plugins'). As far as storage devices that require network access, I suspect that would more be under the purview of something like Cinder, which may need to integrate with Quantum (similar to Nova's integration with Quantum) if the goal is to plug storage devices into networks directly. Dan On Sun, Sep 9, 2012 at 10:56 PM, Tim Bell tim.b...@cern.ch wrote: There has been some load balancing discussion and more is due at the summit. The various current activities are summarised in http://wiki.openstack.org/Quantum/LBaaS Can you explain what you mean by storage devices with respect to Quantum ? The storage activities are underway as part of Cinder. Tim From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Endre Karlson Sent: 09 September 2012 19:57 To: openstack@lists.launchpad.net Subject: [Openstack] Quantum -. Multi-Plugin and support for provisioning of other devices. Hi, I am wondering if there are any community plans to support to use Quantum to provision up interfaces on other devices in areas of say LoadBalancers, Storage devices etc and if there are plans to support multi-active plugins in Quantum for this? Is there a timeframe maybe? Endre. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Shake Chen ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Horizon and Quantum Folsom RC1 available
Hello everyone, Two weeks away from 2012.2 (Folsom) final release, we are starting to produce release candidates. The tarballs for the first release candidate for OpenStack Network service (Quantum) and Dashboard (Horizon) are now available at: https://launchpad.net/quantum/folsom/folsom-rc1 https://launchpad.net/horizon/folsom/folsom-rc1 Congrats to both projects on this significant milestone ! Unless release-critical issues are found that warrant a release candidate respin, these RC1s will be formally released as the 2012.2 final version in two weeks. You are therefore strongly encouraged to test and validate those tarballs. Alternatively, you can directly test the milestone-proposed branch at: https://github.com/openstack/quantum/tree/milestone-proposed https://github.com/openstack/horizon/tree/milestone-proposed If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/quantum/+filebug or https://bugs.launchpad.net/horizon/+filebug and tag it *folsom-rc-potential* to bring it to the release crew's attention. Note that the master branches of Quantum and Horizon are now open for Grizzly development, and feature freeze restrictions no longer apply. Regards, -- 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
Re: [Openstack] [ceilometer] *ALT TIME* Metering meeting agenda for Wed at 21:00 UTC (Sept 12th, 2012)
On Tue, Sep 11, 2012 at 5:22 PM, Nick Barcet nick.bar...@canonical.comwrote: PLEASE NOTE THE ALTERNATIVE MEETING TIME WED 21:00 UTC The metering project team will hold its next meeting at alternate time on *Wednesday* at 9PM UTC http://www.timeanddate.com/worldclock/fixedtime.html?hour=21min=0sec=0 . Everyone is welcome. Agenda: http://wiki.openstack.org/Meetings/MeteringAgenda * Review last week's actions * nijaba to see with ttx how our sessions can be shown on official program * nijaba to update meeting page to note new alternating meeting time * gmb to a plan on the ml with fixed dates * dhellmann make sure flask is listed as a dependency of ceilometer In case I can't make it to the meeting, I did check that Flask is listed in the tools/pip-requires file. It is pegged to version 0.9. * Open discussion If you are not able to attend or have additional topic you would like to cover, please update the agenda on the wiki. Cheers, -- Nick Barcet nick.bar...@canonical.com aka: nijaba, nicolas ___ 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] [ceilometer] Release plan for 0.1
Hi all, Based on the discussion in the last Ceilometer meeting[1], here's my proposal for dates for the Ceilometer 0.1 release calendar: - Feature freeze for 0.1 QA: 2012-09-28 - Release: 2012-10-12 Arguments for / against welcome. [1] http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-06-15.00.log.html ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Openstack-announce] [OSSA 2012-014] Revoking a role does not affect existing tokens (CVE-2012-4413)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/12/2012 01:07 PM, Matt Joyce wrote: This is not a repeat of cve-2012-3426? It's related, but not the same. That CVE did not include this specific issue (existing tokens including roles that may have since been revoked). It was for some other problems around token expiration, though. For reference: https://lists.launchpad.net/openstack/msg15164.html - -- Russell Bryant -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBQyDwACgkQFg9ft4s9SAYVGgCfcQuY/uk4HlXh9ToPqqSPl7Nf h6kAoK/ZUqvTeHSkPbWyi1Y8+PEkt4tD =Cz/+ -END PGP 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] Fwd: Cinder PTL candidacy
Hi Rob, Thanks, initial thoughts regarding your questions are inline below. John On Wed, Sep 12, 2012 at 10:43 AM, Esker, Robert rob.es...@netapp.comwrote: Hi John, Good to see you running and thanks for your efforts thus far... I do have a few questions about your thoughts on Cinder's future: • We (NetApp) have heard from folks looking to potentially use Cinder independently of Nova, et cetera (as a generalized storage backend abstraction layer). Where do you stand on retaining the option to do so? I would strongly agree with this mindset. This was in fact part of a number of discussions at the Folsom summit last spring. Ideally I would like to see Cinder mature to a point where it could be used exactly in this sort of manner. Plugged in to different architectures and used as it's own entity with or without Nova, but obviously working with Nova is the main charter and first priority. • We've also been asked by several in the operator (or soon to be) community to look at expanding the role of Cinder beyond block storage only. This was touched upon a bit at the last summit. Given the significant effort associated with breaking out Cinder it wasn't a focus at the time though. We're planning talks on this at the Grizzly design summit next month, but more significantly have prototyped Cinder support for accommodating shared filesystems. We've specifically avoided submitting most of it while Folsom is in play, but will do so as soon as Grizzly revs up. Could you please comment on your philosophy for the future of Cinder as it applies to extending the API for such? I don't think my opinion regarding this has ever been much of a secret (regardless of how unpopular it may be) :) During the initial proposals to start the Cinder project I shared my opinion that the idea was to provide an independent block storage service that would be consumed by Nova and possibly others. I've never been a big fan of the idea of shoe horning in all sorts of extras (network shares, file systems etc.). My experience has been that if you don't have a very clear and focused definition regarding what your purpose is you tend to not be very good at anything. I'd like to keep Cinder focused on being a Block Storage service, not an NFS service or other shared file system service etc. That being said, I also understand the needs/desires from folks in the community. As you know NetApp submitted changes to Cinder to enable NFS support and they were accepted and merged. I would never object to something that the majority of team members and especially end users ask for. I would just like to avoid trying to be everything to everyone and in turn not being very good at any of it. In my opinion if changes are somewhat isolated and the only real impact is things like new drivers (such as the NFS addition) without impacting the API etc then I'm all for it. I also think that this is a philosophy that can evolve over time as the project matures. Right now I see a significant need for improvements to block storage and that's where I would like to focus efforts. Down the road when Cinder is the *best* block storage service that it can be, that opens up the door to a change in philosophies and focus. Thanks! Rob Esker NetApp, Inc. On Aug 31, 2012, at 3:27 PM, John Griffith john.griff...@solidfire.com wrote: Hello, For the many folks that don't know me, my name is John Griffith and I'd like to announce my candidacy for Cinder PTL. Qualifications: I've been an active contributor to Nova since November of 2011, starting out as many by adding a driver, but then began helping out anywhere and everywhere I could. IRC questions/conversations, assigning bugs to myself etc. In addition I've been involved in multiple conversations with customers interested in OpenStack and have been acting as an OpenStack evangelist to a number of both small and large companies looking to deploy OpenStack in public and private clouds. Contribution over the last six months: During the last summit I lead conversations around the idea of Cinder and organized the effort to kick off the project. Since then I've been acting as interim PTL for the Cinder project and have successfully driven the effort to promote Cinder to core status as an OpenStack project. I'm continually learning, and absolutely love doing the work! While it's been a learning experience I have been fulfilling the responsibilities or PTL, and dedicated every day to the success of the project. I'm passionate about the success of Cinder and believe it has vast potential and is critically important to OpenStack as a whole. Most critical aspects for Cinder in the next 6 months: The next six months are going to be defining for Cinder. The most important thing is going to be showing a smooth transition from Nova-Volume to Cinder is possible. There's a lot of concern regarding this subject and it's something that I keep in
Re: [Openstack] [oss-security] Re: [Openstack-announce] [OSSA 2012-014] Revoking a role does not affect existing tokens (CVE-2012-4413)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/12/2012 11:07 AM, Matt Joyce wrote: This is not a repeat of cve-2012-3426? Quite different: CVE-2012-3426 OpenStack-Keystone: token expiration issues https://bugzilla.redhat.com/show_bug.cgi?id=843311 CVE-2012-4413 OpenStack-Keystone: role revocation token issues https://bugzilla.redhat.com/show_bug.cgi?id=855491 - -- Kurt Seifried Red Hat Security Response Team (SRT) PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQUMSyAAoJEBYNRVNeJnmTtXkP/RrHCL0aOigaKrV4X/giNR3q KbUcbRl2evec6d5mNryQjOT+lAQK96DHApTCvjvVNFZ/ubFKn22A5ld761IAnsbV QE72PqM6UxriZFFujgW0RXRpjmmtTwcw0tjDb5xZh6PaVg41RJxMzjMNV8DmGLoi 1Gg6YyQabD8RkkYxlCqSw2Msfo2a+Zh3VZRzM1HmZwyY69dwIdW6YfCyH+owfUgL rAjDpfX5sAc3rpEwfDrstV86UzdwI9bPDa9U2nuOM07/BP7FX+3DCi8R36hZq4ey caVermEytfVWiiLfARz0KC7O/KhTSmEKaVplLAdxNK716HstCjZTsFf72LchwnHP AG0gyu1em00wTAuR/oDXjOinwtnk14wKc4pZZa5g7TeCgG9N9KTyrXqEEuDPjdB7 3gTWmhflKSQLzBkrhZ1AdurkFJolFLiYfIvfw4VlZjluYbHOkJkXhxLw6CHNLcOf QSzD+S5n6Glb16r5eHoBNdUk3bvdlm3B7eaIHWfnsnRFMuFegpnp5sEBqdtgd8nC KOD3U4KQI6BAtq3HI6YnsK8QuJC5PBLeT1nZmvmdD0S4v/wMQ8hLf7rPfm8xhtmZ 6r6gKoPMgGDss/2dZWpX8upWt5X9IxBUimRc2ItKQZdII6s+iGclVixq7JqqEI30 31C8uRBQ6pO6zCVXrU/q =RgK0 -END PGP 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] [OSSA 2012-014] Revoking a role does not affect existing tokens (CVE-2012-4413)
Ryan Lane deserves recognition for originally identifying this as a potential vulnerability. Thanks, Ryan! -Dolph On Wed, Sep 12, 2012 at 11:36 AM, Thierry Carrez thie...@openstack.orgwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenStack Security Advisory: 2012-014 CVE: CVE-2012-4413 Date: September 12, 2012 Title: Revoking a role does not affect existing tokens Impact: High Reporter: Dolph Mathews (Rackspace) Products: Keystone Affects: Essex, Folsom Description: Dolph Mathews reported a vulnerability in Keystone. Granting and revoking roles from a user is not reflected upon token validation for pre-existing tokens. Pre-existing tokens continue to be valid for the original set of roles for the remainder of the token's lifespan, or until explicitly invalidated. This fix invalidates all tokens held by a user upon role grant/revoke to circumvent the issue. Folsom fix: http://github.com/openstack/keystone/commit/efb6b3fca0ba0ad768b3e803a324043095d326e2 Essex fix: http://github.com/openstack/keystone/commit/58ac6691a21675be9e2ffb0f84a05fc3cd4d2e2e References: https://bugs.launchpad.net/keystone/+bug/1041396 http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2012-4413 Notes: This fix will be included in the future Keystone 2012.1.3 stable update and the upcoming Folsom-RC1 development milestone. - -- Thierry Carrez (ttx) OpenStack Vulnerability Management Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBCAAGBQJQULoUAAoJEFB6+JAlsQQjGacQAJUvJb+oIjh73KAYYuDpl/YP PqJa4nmjVin7CyQ8AbxHK63xrAQ7isPFpCCqtEmjZ5kvFCrJRHiQggHNqISRhnvo +HyS6RSn4Vrp001PSZSmQI5MpgkeWhbOy+fk4/ZY7hFgUyS2YqC8YiK7DTMdKRBi toWOHRVWrmA4fUEDDcDdm9XzRseTC0cZAbj9bYAF+vXPdpxeGpq5l9Kb6yDezXGD 62dFvHghVTWdUIN+gK4V4d77PoyeO9NRd4Ud0GjDpV/asQL31dW6B4aRPYVDPhL3 7xcnhRsnZ3Y5J31n+7E/gMF+J+6kOaY/DNFZQ8chNW18kplYnmJnm7s3BJNjD512 UF/S5A5sH1Rk/vwe2nAHSqvQ1Dq3K0sRvW3YCijG2Rdj3mhBOr6OlvT5uJmnkeJT GQQ8SR3y+ZLS/2EEW+cVjDMxV4Gnf9Zzrw/tSjVp6QLmJAkG8qrFmgdisQ/Jao4M ygE8ZVu8lJq7N8b+k8XkB+bhz9E9V6hYOUuGoifEHRIPki/Ed7++BcdVTQdQYpAL kDTaoVZt1+plwAu4ZBLxUg1vhVz19qgDc7UeoY1sPc1JcRWp/ONnp6K4z+Y+7Rsx 3E4FLH0/qgFxKDHdGX91Plehk9dIEjHcGtKaXI8vOvGT17srYQaF6Y7rc+9TwaqI bggBCxcI2PLQgjuWyF4M =+6UN -END PGP 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 ___ 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] [OSSA 2012-014] Revoking a role does not affect existing tokens (CVE-2012-4413)
So if I can grant people access to a particular tenant, I can invalidate everyone's tokens at will now? Best regards, Soren. Sent from my phone. Please pardon my brevity. On Sep 12, 2012 6:40 PM, Thierry Carrez thie...@openstack.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenStack Security Advisory: 2012-014 CVE: CVE-2012-4413 Date: September 12, 2012 Title: Revoking a role does not affect existing tokens Impact: High Reporter: Dolph Mathews (Rackspace) Products: Keystone Affects: Essex, Folsom Description: Dolph Mathews reported a vulnerability in Keystone. Granting and revoking roles from a user is not reflected upon token validation for pre-existing tokens. Pre-existing tokens continue to be valid for the original set of roles for the remainder of the token's lifespan, or until explicitly invalidated. This fix invalidates all tokens held by a user upon role grant/revoke to circumvent the issue. Folsom fix: http://github.com/openstack/keystone/commit/efb6b3fca0ba0ad768b3e803a324043095d326e2 Essex fix: http://github.com/openstack/keystone/commit/58ac6691a21675be9e2ffb0f84a05fc3cd4d2e2e References: https://bugs.launchpad.net/keystone/+bug/1041396 http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2012-4413 Notes: This fix will be included in the future Keystone 2012.1.3 stable update and the upcoming Folsom-RC1 development milestone. - -- Thierry Carrez (ttx) OpenStack Vulnerability Management Team -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBCAAGBQJQULoUAAoJEFB6+JAlsQQjGacQAJUvJb+oIjh73KAYYuDpl/YP PqJa4nmjVin7CyQ8AbxHK63xrAQ7isPFpCCqtEmjZ5kvFCrJRHiQggHNqISRhnvo +HyS6RSn4Vrp001PSZSmQI5MpgkeWhbOy+fk4/ZY7hFgUyS2YqC8YiK7DTMdKRBi toWOHRVWrmA4fUEDDcDdm9XzRseTC0cZAbj9bYAF+vXPdpxeGpq5l9Kb6yDezXGD 62dFvHghVTWdUIN+gK4V4d77PoyeO9NRd4Ud0GjDpV/asQL31dW6B4aRPYVDPhL3 7xcnhRsnZ3Y5J31n+7E/gMF+J+6kOaY/DNFZQ8chNW18kplYnmJnm7s3BJNjD512 UF/S5A5sH1Rk/vwe2nAHSqvQ1Dq3K0sRvW3YCijG2Rdj3mhBOr6OlvT5uJmnkeJT GQQ8SR3y+ZLS/2EEW+cVjDMxV4Gnf9Zzrw/tSjVp6QLmJAkG8qrFmgdisQ/Jao4M ygE8ZVu8lJq7N8b+k8XkB+bhz9E9V6hYOUuGoifEHRIPki/Ed7++BcdVTQdQYpAL kDTaoVZt1+plwAu4ZBLxUg1vhVz19qgDc7UeoY1sPc1JcRWp/ONnp6K4z+Y+7Rsx 3E4FLH0/qgFxKDHdGX91Plehk9dIEjHcGtKaXI8vOvGT17srYQaF6Y7rc+9TwaqI bggBCxcI2PLQgjuWyF4M =+6UN -END PGP 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 ___ 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] [Doc] This week in Docs 9/12/12
Wow, we went from 34 High folsom-targeted doc bugs two weeks ago to 17 on Monday. Great work everyone. I think there might be something to this community documentation thing. :-P Tom Fifield and Ying Chun Guo (Daisy) are tearing it up with reviews and patches! Still over 100 doc bugs (some are tasks) to be worked. Here's the summary for this week. 1. In review and merged this past week: Object Storage API dev guide now contains object versioning and static web information. Add swift name_check filter to docs. Add retry host cost weight function to scheduler docs. Remove ArchFilter, adds ImagePropertiesFilter. Extended section on overloading ldap attrs. Add GET (show) to OS API keypairs extension docs. Add the network association api docs. Add Network creation to OS API docs. Reviews still needed: The Compute extensions for createBackup, os-migrateLive, and os-resetState api for api.openstack.org. https://review.openstack.org/#/c/12857/ The CLI user guide has been updated with Quantum information. https://review.openstack.org/#/c/12851/ A glossary has been added that now builds properly. https://review.openstack.org/#/c/12707/ 2. High priority doc work: Please pick up a bug from this list: https://launchpad.net/openstack-manuals/+milestone/folsom I'd like to get the tested samples that are going into nova into the api.openstack.org site, can someone help with that? Quantum is working diligently on their API guide and Admin guide so you can install and run Quantum. Sounds like lots of people want this, I'd like the focus on the official docs, but unoffficial docs are fine too of course. 3. Doc work going on that I know of: I'm working on new landing pages and navigation for the docs and api sites. Please take a look at https://review.openstack.org/#/c/11232/ to see the work in progress. David Hendler is working with John Griffith to finalize a Volume API developer guide (a spec, more or less). Bug fixes and more bug fixes. We're still at 111 doc bugs, all have been reviewed and triaged, so jump in. 4. New incoming doc requests: Need help with https://review.openstack.org/#/c/12214/ on the CI puppet scripts to get the Image API 2.0 draft published. 5. Doc tools updates: Think these are the doc tools bugs that the tools team is working on this sprint: http://bit.ly/Q9eGsu 6. Other doc news: We've got two proposals for the Documentation Track at the Design Summit and I'd like more! Please propose at http://summit.openstack.org. I've done a summary spreadsheet of what API docs live where at https://docs.google.com/a/justwriteclick.com/spreadsheet/ccc?key=0Ar7TiePyvTNVdFhGVTZCSzRQQzJCYWtNZnZXblV6aUE#gid=0 titled OpenStack API Docs - What lives where? It should be a good reference for which specs have what types of information (WADL? XSD? DocBook? Markdown? RST?) all answers are here. We met this week for our monthly doc meeting. Summary: http://eavesdrop.openstack.org/meetings/doc_web_meeting/2012/doc_web_meeting.2012-09-10-20.01.html Meeting Log: http://eavesdrop.openstack.org/meetings/doc_web_meeting/2012/doc_web_meeting.2012-09-10-20.01.log.html Thanks, Anne ___ 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] Future of Launchpad OpenStack mailing list (this list)
On 09/04/2012 09:57 AM, Duncan McGreggor wrote: Do we have information on the type/number of discussions that are user and not operator? general and not user or operator? well, that would be good to know. Like it would be good to understand what sort of topics we get on each lists. From what I see, the topics discussed on operators and on launchpad seem very similar to me. I'm leaning on the side of merging the two lists because even if the operators are a very specific, identifiable group of people, the discussions they have seem to be 'general'. I can run some numbers but I'm not sure what to look for. I can calculate the most frequent words in the subject lines in the operators lists (not on launchpad): would that give us an understanding of what discussions are being held there? How else would you mine the mailbox archives? One thing to keep in mind is that the more divisions there are in a set of things which are conceptually similar, the greater amount of confusion that will result... a sacred truth. I know that technically operators are different than users different than firstcomers to OpenStack. The reality of human interaction though is that nobody reads the descriptions of the lists and messages end up being posted randomly. Generally more lists equals more crossposts (at best). /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] Future of Launchpad OpenStack mailing list (this list)
My two penneth worth: I'd be confused as to what the difference between general and operators would be and would result in people posting to both - so that goes for openstack@... openstack-general@... and openstack-operators@ It would seem that there is a clear distinction between development questions (-dev), announcements (-announce) and then anything else (people asking for help from a variety of skill levels) - so: openstack@... openstack-dev@ openstack-announce@ openstack-security@ Would be my vote (sorry for adding in -security, would that be considered?) Cheers, Kev On 4 September 2012 10:37, Thierry Carrez thie...@openstack.org wrote: Stefano Maffulli wrote: Now, the main question is still open: where should the General mailing list go? Anybody disagrees that we should merge this list into 'Operators'? I think there are two options: Option A1: openstack-gene...@lists.openstack.org openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... openstack-general makes it clear this is about general questions and things that address the whole community. This would be a straight replacement of the current openstack@launchpad mailing-list. Option A2: openst...@lists.openstack.org openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... Same, using openstack instead of openstack-general. Makes it clear it's the default list. Option B: openstack-u...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... User would be a merge of the current list with the operators list. The benefit is that it matches a recognized pattern in open source project lists (-user, -dev, -announce). The drawback is that there is no default list for newcomers or general discussion, and operators-specific topics will get lost on the -user list, the same way the dev topics used to be. Personally, I prefer option A. On one side you have a general list where almost everyone lurks, on the other you have several topic- or team-oriented lists with sharper focus. One issue is that it's difficult to spot important things on the (noisy) general list, but we also have a (moderated) -announce list that we can more actively use for things we want to make sure everyone sees. Any other option ? Which one do you prefer ? -- 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 -- Kevin Jackson @itarchitectkev ___ 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] [swift] 1.7.0-final pushed
I just pushed the final versioning change to Swift 1.7.0. This is our part of OpenStack Folsom. Good work everyone, and thanks the time and effort you have put into keeping Swift world-class software. I'll follow up later with more details about what is in Swift 1.7.0 and the changes since the Essex release, but I wanted to publicly thank everyone who contributed to Swift during the Folsom release cycle. The following people have code contributions in Swift during the Folsom release cycle. Thanks again! Greg Holt John Dickinson Darrell Bishop Samuel Merritt Florian Hines David Goetz Greg Lange Victor Rodionov Michael Barton Ionuț Arțăriși Vincent Untz Pete Zaitcev Chmouel Boudjnah Alex Yang Morita Kazutaka Iryoung Jeong Julien Danjou Dan Prince Adrian Smith ning_zhang Anne Gentle Brent Roskos Clark Boylan Constantine Peresypkin Dan Dillinger François Charlier Josh Kearney Kota Tsuyuzaki Li Riqiang Marcelo Martins Monty Taylor Paul McMillan Ray Chen Scott Simpson Thierry Carrez Tom Fifield Tong Li smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [ceilometer] *ALT TIME* Metering meeting agenda for Wed at 21:00 UTC (Sept 12th, 2012)
On 09/11/2012 11:22 PM, Nick Barcet wrote: PLEASE NOTE THE ALTERNATIVE MEETING TIME WED 21:00 UTC The metering project team will hold its next meeting at alternate time on *Wednesday* at 9PM UTC http://www.timeanddate.com/worldclock/fixedtime.html?hour=21min=0sec=0. Everyone is welcome. Agenda: http://wiki.openstack.org/Meetings/MeteringAgenda * Review last week's actions * nijaba to see with ttx how our sessions can be shown on official program * nijaba to update meeting page to note new alternating meeting time * gmb to a plan on the ml with fixed dates * dhellmann make sure flask is listed as a dependency of ceilometer * Open discussion If you are not able to attend or have additional topic you would like to cover, please update the agenda on the wiki. Cheers, The meeting took place, here is the summary: == #openstack-meeting: Ceilometer == Meeting started by nijaba at 21:00:17 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/ceilometer/2012/ceilometer.2012-09-12-21.00.log.html . Meeting summary --- * LINK: http://wiki.openstack.org/Meetings/MeteringAgenda (nijaba, 21:00:17) * actions from previous meeting (nijaba, 21:01:27) * nijaba to see with ttx how our sessions can be shown on official program (nijaba, 21:01:40) * nijaba to update meeting page to note new alternating meeting time (nijaba, 21:03:50) * VOTE: Voted on should we maintain alt meet time for the next month? Results are, yes: 1, bleh: 1, no: 2 (nijaba, 21:10:09) * gmb to a plan on the ml with fixed dates (nijaba, 21:10:36) * AGREED: 0.1 feature freeze will take effect on 2012-09-28 (nijaba, 21:12:15) * AGREED: 0.1 release date will be 2012-10-12 (nijaba, 21:12:15) * dhellmann make sure flask is listed as a dependency of ceilometer (nijaba, 21:12:32) * Open Discusssion (nijaba, 21:13:29) * LINK: http://wiki.openstack.org/EfficientMetering/RoadMap (nijaba, 21:22:54) * ACTION: dhellmann write up details of blueprint https://blueprints.launchpad.net/ceilometer/+spec/config-driven-notification-monitoring (dhellmann, 21:23:36) * LINK: http://teambox.com/n/8fb5404848e9f0b9/ceilometer (nijaba, 21:25:13) * AGREED: next meeting thu sept 20 at 15UTC! (nijaba, 21:40:54) Meeting ended at 21:41:15 UTC. Action items, by person --- * dhellmann * dhellmann write up details of blueprint https://blueprints.launchpad.net/ceilometer/+spec/config-driven-notification-monitoring People present (lines said) --- * nijaba (70) * jtran (42) * asalkeld (26) * dhellmann (18) * spn2 (17) * jd___ (17) * openstack (10) * notmyname (2) * uvirtbot (1) Generated by `MeetBot`_ 0.1.4 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] Future of Launchpad OpenStack mailing list (this list)
+ 2 shekels On Sep 12, 2012, at 3:54 PM, Kevin Jackson ke...@linuxservices.co.uk wrote: My two penneth worth: I'd be confused as to what the difference between general and operators would be and would result in people posting to both - so that goes for openstack@... openstack-general@... and openstack-operators@ It would seem that there is a clear distinction between development questions (-dev), announcements (-announce) and then anything else (people asking for help from a variety of skill levels) - so: openstack@... openstack-dev@ openstack-announce@ openstack-security@ Would be my vote (sorry for adding in -security, would that be considered?) Cheers, Kev On 4 September 2012 10:37, Thierry Carrez thie...@openstack.org wrote: Stefano Maffulli wrote: Now, the main question is still open: where should the General mailing list go? Anybody disagrees that we should merge this list into 'Operators'? I think there are two options: Option A1: openstack-gene...@lists.openstack.org openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... openstack-general makes it clear this is about general questions and things that address the whole community. This would be a straight replacement of the current openstack@launchpad mailing-list. Option A2: openst...@lists.openstack.org openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... Same, using openstack instead of openstack-general. Makes it clear it's the default list. Option B: openstack-u...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... User would be a merge of the current list with the operators list. The benefit is that it matches a recognized pattern in open source project lists (-user, -dev, -announce). The drawback is that there is no default list for newcomers or general discussion, and operators-specific topics will get lost on the -user list, the same way the dev topics used to be. Personally, I prefer option A. On one side you have a general list where almost everyone lurks, on the other you have several topic- or team-oriented lists with sharper focus. One issue is that it's difficult to spot important things on the (noisy) general list, but we also have a (moderated) -announce list that we can more actively use for things we want to make sure everyone sees. Any other option ? Which one do you prefer ? -- 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 -- Kevin Jackson @itarchitectkev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Reuse part of Nova-API
Sure, you could write a different implementation of compute.api (and network.api and volume.api if needed) to talk to the other provider. Vish On Sep 12, 2012, at 8:45 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've been tasked with translating the OpenStack API to another provider, so that the other provider is able to handle both it's own API and requests nova's API. Is it possible to reuse most of nova-api's handling of the REST request and simply change the underlying execution? In other words, make nova-api act as a translation proxy for the other provider?. -- Cumprimentos / Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] Future of Launchpad OpenStack mailing list (this list)
To chime in as a lurker around here, this sounds good, but why add the security list? It seems like security specific topics would interest those subscribed to the general list as well. On Wed, Sep 12, 2012 at 4:54 PM, Kevin Jackson ke...@linuxservices.co.ukwrote: My two penneth worth: I'd be confused as to what the difference between general and operators would be and would result in people posting to both - so that goes for openstack@... openstack-general@... and openstack-operators@ It would seem that there is a clear distinction between development questions (-dev), announcements (-announce) and then anything else (people asking for help from a variety of skill levels) - so: openstack@... openstack-dev@ openstack-announce@ openstack-security@ Would be my vote (sorry for adding in -security, would that be considered?) Cheers, Kev On 4 September 2012 10:37, Thierry Carrez thie...@openstack.org wrote: Stefano Maffulli wrote: Now, the main question is still open: where should the General mailing list go? Anybody disagrees that we should merge this list into 'Operators'? I think there are two options: Option A1: openstack-gene...@lists.openstack.org openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... openstack-general makes it clear this is about general questions and things that address the whole community. This would be a straight replacement of the current openstack@launchpad mailing-list. Option A2: openst...@lists.openstack.org openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... Same, using openstack instead of openstack-general. Makes it clear it's the default list. Option B: openstack-u...@lists.openstack.org openstack-annou...@lists.openstack.org openstack-...@lists.openstack.org ... User would be a merge of the current list with the operators list. The benefit is that it matches a recognized pattern in open source project lists (-user, -dev, -announce). The drawback is that there is no default list for newcomers or general discussion, and operators-specific topics will get lost on the -user list, the same way the dev topics used to be. Personally, I prefer option A. On one side you have a general list where almost everyone lurks, on the other you have several topic- or team-oriented lists with sharper focus. One issue is that it's difficult to spot important things on the (noisy) general list, but we also have a (moderated) -announce list that we can more actively use for things we want to make sure everyone sees. Any other option ? Which one do you prefer ? -- 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 -- Kevin Jackson @itarchitectkev ___ 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] Future of Launchpad OpenStack mailing list (this list)
Guess the only advantage would be to minimize the chance of someone missing the security related messages in the noise of a heavy traffic mailing list. Even if there were a specialized list, I'd think you'd want to cross post security issues to all lists, depending on severity (and with security, all issues are generally severe). syd From: openstack-bounces+slogan=broadcom@lists.launchpad.net [mailto:openstack-bounces+slogan=broadcom@lists.launchpad.net] On Behalf Of Asher Newcomer Sent: Wednesday, September 12, 2012 5:38 PM To: Kevin Jackson Cc: Thierry Carrez; openstack@lists.launchpad.net Subject: Re: [Openstack] Future of Launchpad OpenStack mailing list (this list) To chime in as a lurker around here, this sounds good, but why add the security list? It seems like security specific topics would interest those subscribed to the general list as well. On Wed, Sep 12, 2012 at 4:54 PM, Kevin Jackson ke...@linuxservices.co.ukmailto:ke...@linuxservices.co.uk wrote: My two penneth worth: I'd be confused as to what the difference between general and operators would be and would result in people posting to both - so that goes for openstack@... openstack-general@... and openstack-operators@ It would seem that there is a clear distinction between development questions (-dev), announcements (-announce) and then anything else (people asking for help from a variety of skill levels) - so: openstack@... openstack-dev@ openstack-announce@ openstack-security@ Would be my vote (sorry for adding in -security, would that be considered?) Cheers, Kev On 4 September 2012 10:37, Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org wrote: Stefano Maffulli wrote: Now, the main question is still open: where should the General mailing list go? Anybody disagrees that we should merge this list into 'Operators'? I think there are two options: Option A1: openstack-gene...@lists.openstack.orgmailto:openstack-gene...@lists.openstack.org openstack-operat...@lists.openstack.orgmailto:openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.orgmailto:openstack-annou...@lists.openstack.org openstack-...@lists.openstack.orgmailto:openstack-...@lists.openstack.org ... openstack-general makes it clear this is about general questions and things that address the whole community. This would be a straight replacement of the current openstack@launchpad mailing-list. Option A2: openst...@lists.openstack.orgmailto:openst...@lists.openstack.org openstack-operat...@lists.openstack.orgmailto:openstack-operat...@lists.openstack.org openstack-annou...@lists.openstack.orgmailto:openstack-annou...@lists.openstack.org openstack-...@lists.openstack.orgmailto:openstack-...@lists.openstack.org ... Same, using openstack instead of openstack-general. Makes it clear it's the default list. Option B: openstack-u...@lists.openstack.orgmailto:openstack-u...@lists.openstack.org openstack-annou...@lists.openstack.orgmailto:openstack-annou...@lists.openstack.org openstack-...@lists.openstack.orgmailto:openstack-...@lists.openstack.org ... User would be a merge of the current list with the operators list. The benefit is that it matches a recognized pattern in open source project lists (-user, -dev, -announce). The drawback is that there is no default list for newcomers or general discussion, and operators-specific topics will get lost on the -user list, the same way the dev topics used to be. Personally, I prefer option A. On one side you have a general list where almost everyone lurks, on the other you have several topic- or team-oriented lists with sharper focus. One issue is that it's difficult to spot important things on the (noisy) general list, but we also have a (moderated) -announce list that we can more actively use for things we want to make sure everyone sees. Any other option ? Which one do you prefer ? -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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 -- Kevin Jackson @itarchitectkev ___ 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
[Openstack] paas in openstack and forked cloudfoindry
hi all we try to make openstack as paas using cloudfoundry. and also seeking alternative to it shocked that there are forked cloudfiundry. and got that vmware manage different way his cloudfoundry there are piston, stackato i hear appfog never hear cf manage the way people do. in this case forking esp bosh bosh is the link to openstack and got the forker using openstack as platform i try to see in different way. hoe openstack work with them and what is the best glad there are competition. but sadly one become many rather unique innovation any feedback? i try to promote open paas and openstack in one community program thx all Frans Thamura Meruvian ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [OpenStack][Nova] Reuse part of Nova-API
Hi vish- Can please outline about or point to some source where we get info on nava compute api code structure and relationship between the different classes This helps devs to understand the code orientation and request flow inside the api. - Trinaths On Sep 13, 2012 6:04 AM, Vishvananda Ishaya vishvana...@gmail.com wrote: Sure, you could write a different implementation of compute.api (and network.api and volume.api if needed) to talk to the other provider. Vish On Sep 12, 2012, at 8:45 AM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I've been tasked with translating the OpenStack API to another provider, so that the other provider is able to handle both it's own API and requests nova's API. Is it possible to reuse most of nova-api's handling of the REST request and simply change the underlying execution? In other words, make nova-api act as a translation proxy for the other provider?. -- Cumprimentos / Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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] [heat] Meeting Minutes 2012/09/10
= #heat Meeting = Meeting started by sdake at 21:12:45 UTC. http://heat-api.org/heat-irc-meetings/heat.2012-09-10-21.12.html Meeting summary --- * rollcall (sdake, 21:14:29) * sdake, steveb_ slower shardy zaneb jpeeler present (sdake, 21:16:19) * heat-v6 (sdake, 21:16:33) * LINK: https://github.com/heat-api/heat/issues?milestone=7state=open (sdake, 21:17:12) * team voted to move v6 release to September 18th, 2012 (sdake, 21:23:56) * half-day incibuation miniconf at OpenStack Summit in San Diego (sdake, 21:43:44) * agenda item for summit - New Orchestration API from Zane (sdake, 21:54:19) * agenda item for summit - What CloudWatch is and how to make it a reality in OpenStack (sdake, 21:54:37) * agenda item for summit - heat roadmap feature open suggestions (sdake, 21:55:10) * agenda item for summit -overview of heat (sdake, 21:55:51) * open items (sdake, 21:56:52) Meeting ended at 22:07:24 UTC. ___ 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-translation-* jobs in Jenkins
Dear CI team, I'd like to understand if there are any jobs in Jenkins running to upload and download translations from Transifex. I see some nova-translation-* jobs active, but I cannot figure out which website they are connecting with, Lauchpad or Transifex. Can somebody tell me? Regards Ying Chun Guo (Daisy) China Standards and Open Source Team Emerging Technology Institute (ETI) IBM China Development Lab Tel:(86-10)82453491 Email: guoyi...@cn.ibm.com Address: 1F Tower B, Diamond Building 19 Zhongguancun Software Park, 8 Dongbeiwang West Road, Haidian District, Beijing, P.R.C.100193___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Failure: precise_essex_keystone_stable #20
text/html; charset=UTF-8: Unrecognized -- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_keystone_trunk #55
Title: precise_folsom_keystone_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_keystone_trunk/55/Project:precise_folsom_keystone_trunkDate of build:Wed, 12 Sep 2012 13:44:08 -0400Build duration:4 min 55 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 5266 lines...]git log -n1 --no-merges --pretty=format:%Hgit log c13d0ba606f7b2bdc609a7f388334e5efec3f3aa..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201209121344~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201209121344~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [efb6b3f] Delete user tokens after role grant/revokedch -a [235c4ce] Implementation of tenant,user,role list functions for ldapdch -a [fa9f0f1] Initialize Metadata variabledch -a [201a109] Cleanup PEP8 errors from Commondch -a [150413c] List tokens for memcached backenddch -a [32b82ae] Ignore eclipse files.dch -a [7d9b239] Sync some misc changes from openstack-commondch -a [e09a121] Sync latest cfg from openstack-commondch -a [a9ee611] Remove id_hash columndch -a [a411412] Fixed: test_default_tenant_uuid_token not runningdch -a [5446577] Upgrade PEP8 to 1.3.3 (bug 1037303)dch -a [4c32b5c] Expand PEP8 coverage to include docs & testsdch -a [ac95f83] Removed/fixed unused variable referencesdch -a [b82a0e2] HACKING compliance & staticly init module varsdch -a [685c1c2] PEP8 fix E251dch -a [7ad8497] PEP8 fixdch -a [7c93e84] Removed unused importsdch -a [2759c22] Check for expected cfg impl (bug 1043479)dch -a [026bea6] Fixed typos in commentdch -a [8a84c03] HACKING: Import by full module pathdch -a [379354b] HACKING: Use single quotesdch -a [13ce482] mistake in doc stringdch -a [861670e] pep8 1.3.3 cleanup removing unused importsdch -a [6b04662] Removed dead codedch -a [3fa4ba5] Fix auth_token middleware to fetch revocation list as admin.dch -a [98d3a89] Code cleanup in doc/source/conf.pydch -a [067fcf0] Typo fix in keystone: existant => existentdch -a [1749644] allow middleware configuration from app configdch -a [1698094] change verbose and debug to Fasle in keystone.conf.sampledch -a [ddc8995] add token_format=UUID to keystone.conf.sampledch -a [af52ef1] Demonstrate that authenticate() returns roles.dch -a [3974105] Add nosehtmloutput as a test dependency.dch -a [dcb1e84] Less information returned with IntegrityErrordebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201209121344~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A keystone_2012.2+git201209121344~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing keystone_2012.2+git201209121344~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom keystone_2012.2+git201209121344~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/keystone/precise-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_horizon_trunk #135
Title: quantal_folsom_horizon_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_horizon_trunk/135/Project:quantal_folsom_horizon_trunkDate of build:Wed, 12 Sep 2012 14:15:19 -0400Build duration:1 min 32 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 1717 lines...]|Index: horizon/openstack_dashboard/wsgi/django.wsgi|===|--- horizon.orig/openstack_dashboard/wsgi/django.wsgi 2012-07-03 14:07:21.316118123 -0700|+++ horizon/openstack_dashboard/wsgi/django.wsgi 2012-07-03 14:07:26.176118333 -0700--No file to patch. Skipping patch.1 out of 1 hunk ignoredPatch fix-dashboard-django-wsgi.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5bb23fee-4971-4a46-b9fc-26f1a25d6872', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5bb23fee-4971-4a46-b9fc-26f1a25d6872', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.git archive milestone/proposed --format tar --prefix horizon-2012.2-201209121415/git archive milestone/proposed --format tar --prefix horizon-2012.2-201209121415/git log -n1 --no-merges --pretty=format:%Hgit log 34cd3163e43eecb073404e7ce1ca180217a47ce5..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+git201209121415~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201209121415~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [0ba2753] Open Grizzly (2013.1)dch -a [968a6aa] Document limitations of quantum/nova/floating ip integration.dch -a [a8c92dc] Remove template comments from compressed blocks.dch -a [347e95a] Admin panel: Don't poll shutoff instancesdch -a [5950c1f] Adds release notes for 2012.2 "Folsom".dch -a [4e6107c] Adds a docs example for a customization module.debcommitbzr builddeb -S -- -sa -us -ucmk-build-deps -i -r -t apt-get -y /tmp/tmpPPkFEK/horizon/debian/controlbzr builddeb -S -- -sa -us -ucTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5bb23fee-4971-4a46-b9fc-26f1a25d6872', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-5bb23fee-4971-4a46-b9fc-26f1a25d6872', '-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 Fixed: quantal_folsom_horizon_trunk #140
Title: quantal_folsom_horizon_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_horizon_trunk/140/Project:quantal_folsom_horizon_trunkDate of build:Wed, 12 Sep 2012 14:30:14 -0400Build duration:3 min 0 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 7485 lines...]Good signature on /tmp/tmp7D7r3W/horizon_2012.2+git201209121430~quantal-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading horizon_2012.2+git201209121430~quantal-0ubuntu1.dsc: done. Uploading horizon_2012.2+git201209121430~quantal.orig.tar.gz: done. Uploading horizon_2012.2+git201209121430~quantal-0ubuntu1.debian.tar.gz: done. Uploading horizon_2012.2+git201209121430~quantal-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'quantal-folsom', 'horizon_2012.2+git201209121430~quantal-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/h/horizon/openstack-dashboard-ubuntu-theme_2012.2+git201209110039~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/openstack-dashboard_2012.2+git201209110039~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-horizon_2012.2+git201209110039~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-openstack_2012.2+git201209110039~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/horizon/quantal-folsom']Pushed up to revision 124.1 tag updated.INFO:root:Storing current commit for next build: 55002fddefc25ac3c075e96c450316997a45d456INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/quantal-folsom-proposed /tmp/tmp7D7r3W/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmp7D7r3W/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 34cd3163e43eecb073404e7ce1ca180217a47ce5..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/horizon/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201209121430~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201209121430~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a [55002fd] Set FINAL versioningdch -a [968a6aa] Document limitations of quantum/nova/floating ip integration.dch -a [a8c92dc] Remove template comments from compressed blocks.dch -a [347e95a] Admin panel: Don't poll shutoff instancesdch -a [5950c1f] Adds release notes for 2012.2 "Folsom".dch -a [4e6107c] Adds a docs example for a customization module.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC horizon_2012.2+git201209121430~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A horizon_2012.2+git201209121430~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing horizon_2012.2+git201209121430~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom horizon_2012.2+git201209121430~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/horizon/quantal-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Fixed: quantal_folsom_glance_trunk #171
Title: quantal_folsom_glance_trunk General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_glance_trunk/171/Project:quantal_folsom_glance_trunkDate of build:Wed, 12 Sep 2012 14:33:43 -0400Build duration:9 min 33 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 11586 lines...]gpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key)"Checking signature on .changesGood signature on /tmp/tmpGkr9vz/glance_2012.2+git201209121433~quantal-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpGkr9vz/glance_2012.2+git201209121433~quantal-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net): Uploading glance_2012.2+git201209121433~quantal-0ubuntu1.dsc: done. Uploading glance_2012.2+git201209121433~quantal.orig.tar.gz: done. Uploading glance_2012.2+git201209121433~quantal-0ubuntu1.debian.tar.gz: done. Uploading glance_2012.2+git201209121433~quantal-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'quantal-folsom', 'glance_2012.2+git201209121433~quantal-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2012.2+git201209111730~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-client_2012.2+git201209111730~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2012.2+git201209111730~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2012.2+git201209111730~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2012.2+git201209111730~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2012.2+git201209111730~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2012.2+git201209111730~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/glance/quantal-folsom']Pushed up to revision 201.INFO:root:Storing current commit for next build: 4de8670bcbb4e977f1d550bcf470926bbd77803fINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/quantal-folsom-proposed /tmp/tmpGkr9vz/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpGkr9vz/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/glance/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201209121433~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201209121433~quantal-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2012.2+git201209121433~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A glance_2012.2+git201209121433~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing glance_2012.2+git201209121433~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom glance_2012.2+git201209121433~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/quantal-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_glance_trunk #163
Title: precise_folsom_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_trunk/163/Project:precise_folsom_glance_trunkDate of build:Wed, 12 Sep 2012 17:30:34 -0400Build duration:2 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUpdate v2.0 API version to CURRENTby bcwaldoneditglance/api/versions.pyeditglance/tests/unit/test_versions.pyeditglance/tests/functional/test_api.pyConsole Output[...truncated 1413 lines...]hard linking glance/tests/unit/test_versions.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/test_wsgi.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/utils.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/common/test_exception.py -> glance-2013.1/glance/tests/unit/commonhard linking glance/tests/unit/v1/__init__.py -> glance-2013.1/glance/tests/unit/v1hard linking glance/tests/unit/v1/test_api.py -> glance-2013.1/glance/tests/unit/v1hard linking glance/tests/unit/v2/__init__.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_image_data_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_image_tags_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_images_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_schemas_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/var/ca.crt -> glance-2013.1/glance/tests/varhard linking glance/tests/var/certificate.crt -> glance-2013.1/glance/tests/varhard linking glance/tests/var/privatekey.key -> glance-2013.1/glance/tests/varhard linking tools/install_venv.py -> glance-2013.1/toolshard linking tools/migrate_image_owners.py -> glance-2013.1/toolshard linking tools/pip-requires -> glance-2013.1/toolshard linking tools/test-requires -> glance-2013.1/toolshard linking tools/with_venv.sh -> glance-2013.1/toolscopying setup.cfg -> glance-2013.1Writing glance-2013.1/setup.cfgcreating distCreating tar archiveremoving 'glance-2013.1' (and everything under it)ERROR:root:Error occurred during package creation/build: [Errno 2] No such file or directory: '/tmp/tmpFI9846/git/glance/dist/glance-2012.2.tar.gz'ERROR:root:[Errno 2] No such file or directory: '/tmp/tmpFI9846/git/glance/dist/glance-2012.2.tar.gz'INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-folsom-proposed /tmp/tmpFI9846/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpFI9846/glance/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpFI9846/git/glance/dist/glance-2012.2.tar.gz'Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpFI9846/git/glance/dist/glance-2012.2.tar.gz'Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_swift_trunk #83
Title: quantal_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/83/Project:quantal_folsom_swift_trunkDate of build:Wed, 12 Sep 2012 18:00:32 -0400Build duration:4 min 29 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesadded disable_fallocate info to docsby meeditdoc/source/deployment_guide.rstConsole Output[...truncated 3576 lines...]dch -a [d24e280] obj replicator speed updch -a [063789b] container_info returns a dictdch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [73846c2] fix update_deleted directory creation. bug 1035274dch -a [07b4c21] 1.7.1 version bumpdch -a [341da75] changelog and authors updates for 1.7 releasedch -a [2e16b1f] Update swift.common.db to us swift.cmmn.utils.jsondch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [0bb5d6d] use simplejson to serialize acct/cont resultsdch -a [54a2907] bumped version to 1.7.0 to reflect current dev effortdch -a [7b664c9] Fix PEP8 issues in ./test/unit/common .dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.dch -a [4a2ae2b] Upating proxy-server StatsD logging.dch -a [c509ac2] Added ability to disable fallocatedch -a [2a38a04] Remove the gettext wrapper of server_type.dch -a [9290471] x-newest cleanup code with test. Fixes bug 1037337dch -a [9bda92d] Misc. swift-bench improvements.dch -a [e1ff51c] Do not use pickle for serialization in memcache, but JSONdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.1+git201209121800~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.7.1+git201209121800~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209121800~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.1+git201209121800~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #566
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/566/Project:precise_folsom_nova_trunkDate of build:Wed, 12 Sep 2012 18:03:38 -0400Build duration:5 min 12 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesChange comment for function _destroyby gudujianjskeditnova/virt/libvirt/driver.pyAvoid VM task state revert on instance terminationby eglynneditnova/tests/compute/test_compute.pyeditnova/compute/manager.pyConsole Output[...truncated 5531 lines...]dch -a [f5ad3bc] Reset task state before reschedulingdch -a [3531288] Convert to ints in VlanManager.create_networksdch -a [1b19fae] Remove unused AddressAlreadyAllocated exceptiondch -a [6281d67] Remove an unused importdch -a [7b24a76] Make ip block splitting a bit more self documenting.dch -a [c2501d8] Prevent Partial terminations in EC2dch -a [7483115] Handle missing network_size in nova-managedch -a [210dc28] Make size optional when creating a volume from a snapshot.dch -a [847fb38] Add documentation for scheduler filters scopedch -a [c2ec406] Add and fix tests for attaching volumes.dch -a [5f9ae51] Fix auth parameter passed to libvirt openAuth() methoddch -a [4c72bfc] xapi: Fix live block migrationdch -a [69f6b86] Add a criteria to sort a list of dict in api samplesdch -a [0d956a8] delete a module never useddch -a [0599406] Adds get_available_resource to hyperv driverdch -a [c3476b5] Create image of volume-backed instance via native APIdch -a [5339141] Improve floating IP delete speed.dch -a [1b87d59] Have device mapping use autocreated device nodesdch -a [79db483] remove a never used importdch -a [b35b34a] fix unmounting of LXC containers in the presence of symlinksdch -a [4fe722a] Add ServerStartStop extension API testdch -a [ccc0bfb] Set install_requires in setup.py.dch -a [85923aa] Add Server Detail and Metadata testsdch -a [6392ad2] xenapi: Make dom0 serialization consistent.dch -a [b97a0be] Correct ephemeral disk cache filename.dch -a [ff3b994] Handle missing 'provider_location' in rm_export.dch -a [4fc05bf] Nail the pip requirement at 1.1.dch -a [f192a16] rbd: implement create_volume_from_snapshotdch -a [0a09bf5] Specify the conf file when creating a volume.dch -a [1f82e30] Fix xml metadata for volumes api in nova-volume.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_glance_trunk #164
Title: precise_folsom_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_trunk/164/Project:precise_folsom_glance_trunkDate of build:Wed, 12 Sep 2012 18:30:32 -0400Build duration:2 min 8 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesUpdate openstack-common log and setup codeby bcwaldoneditglance/openstack/common/setup.pyeditglance/openstack/common/log.pyConsole Output[...truncated 1413 lines...]hard linking glance/tests/unit/test_versions.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/test_wsgi.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/utils.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/common/test_exception.py -> glance-2013.1/glance/tests/unit/commonhard linking glance/tests/unit/v1/__init__.py -> glance-2013.1/glance/tests/unit/v1hard linking glance/tests/unit/v1/test_api.py -> glance-2013.1/glance/tests/unit/v1hard linking glance/tests/unit/v2/__init__.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_image_data_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_image_tags_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_images_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_schemas_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/var/ca.crt -> glance-2013.1/glance/tests/varhard linking glance/tests/var/certificate.crt -> glance-2013.1/glance/tests/varhard linking glance/tests/var/privatekey.key -> glance-2013.1/glance/tests/varhard linking tools/install_venv.py -> glance-2013.1/toolshard linking tools/migrate_image_owners.py -> glance-2013.1/toolshard linking tools/pip-requires -> glance-2013.1/toolshard linking tools/test-requires -> glance-2013.1/toolshard linking tools/with_venv.sh -> glance-2013.1/toolscopying setup.cfg -> glance-2013.1Writing glance-2013.1/setup.cfgcreating distCreating tar archiveremoving 'glance-2013.1' (and everything under it)ERROR:root:Error occurred during package creation/build: [Errno 2] No such file or directory: '/tmp/tmpY5Fzcf/git/glance/dist/glance-2012.2.tar.gz'ERROR:root:[Errno 2] No such file or directory: '/tmp/tmpY5Fzcf/git/glance/dist/glance-2012.2.tar.gz'INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-folsom-proposed /tmp/tmpY5Fzcf/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpY5Fzcf/glance/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpY5Fzcf/git/glance/dist/glance-2012.2.tar.gz'Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpY5Fzcf/git/glance/dist/glance-2012.2.tar.gz'Build 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_glance_trunk #165
Title: precise_folsom_glance_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_trunk/165/Project:precise_folsom_glance_trunkDate of build:Wed, 12 Sep 2012 19:30:33 -0400Build duration:3 min 9 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesRewrite Swift store functional testsby bcwaldoneditglance/store/swift.pyedittools/test-requiresdeleteglance/tests/functional/v1/test_swift.pyaddglance/tests/functional/store/test_swift.pyaddglance/tests/functional/store/__init__.pyConsole Output[...truncated 1415 lines...]hard linking glance/tests/unit/test_versions.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/test_wsgi.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/utils.py -> glance-2013.1/glance/tests/unithard linking glance/tests/unit/common/test_exception.py -> glance-2013.1/glance/tests/unit/commonhard linking glance/tests/unit/v1/__init__.py -> glance-2013.1/glance/tests/unit/v1hard linking glance/tests/unit/v1/test_api.py -> glance-2013.1/glance/tests/unit/v1hard linking glance/tests/unit/v2/__init__.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_image_data_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_image_tags_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_images_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/unit/v2/test_schemas_resource.py -> glance-2013.1/glance/tests/unit/v2hard linking glance/tests/var/ca.crt -> glance-2013.1/glance/tests/varhard linking glance/tests/var/certificate.crt -> glance-2013.1/glance/tests/varhard linking glance/tests/var/privatekey.key -> glance-2013.1/glance/tests/varhard linking tools/install_venv.py -> glance-2013.1/toolshard linking tools/migrate_image_owners.py -> glance-2013.1/toolshard linking tools/pip-requires -> glance-2013.1/toolshard linking tools/test-requires -> glance-2013.1/toolshard linking tools/with_venv.sh -> glance-2013.1/toolscopying setup.cfg -> glance-2013.1Writing glance-2013.1/setup.cfgcreating distCreating tar archiveremoving 'glance-2013.1' (and everything under it)ERROR:root:Error occurred during package creation/build: [Errno 2] No such file or directory: '/tmp/tmpxd5yuE/git/glance/dist/glance-2012.2.tar.gz'ERROR:root:[Errno 2] No such file or directory: '/tmp/tmpxd5yuE/git/glance/dist/glance-2012.2.tar.gz'INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-folsom-proposed /tmp/tmpxd5yuE/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpxd5yuE/glance/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpxd5yuE/git/glance/dist/glance-2012.2.tar.gz'Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpxd5yuE/git/glance/dist/glance-2012.2.tar.gz'Build 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 #567
Title: precise_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/567/Project:precise_folsom_nova_trunkDate of build:Wed, 12 Sep 2012 19:39:26 -0400Build duration:3 min 52 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix flavor deletion when there is a deleted flavorby vishvanandaeditnova/api/openstack/compute/contrib/flavormanage.pyeditnova/tests/api/openstack/compute/contrib/test_flavor_manage.pyAdds API sample test for Flavors Extra Data extension.by tmelloaddnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-resp.xml.tpladdnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-list-resp.xml.tpladdnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-get-resp.xml.tpladddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-get-resp.xmladdnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-list-resp.json.tpleditnova/tests/integrated/test_api_samples.pyaddnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-resp.json.tpladddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-resp.jsonadddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-req.xmladddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-list-resp.jsonadddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-resp.xmladdnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-req.json.tpladddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-list-resp.xmladddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-req.jsonaddnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-post-req.xml.tpladddoc/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-get-resp.jsonaddnova/tests/integrated/api_samples/OS-FLV-EXT-DATA/flavors-extra-data-get-resp.json.tplAdd detaching to volume statusby zrzhiteditnova/tests/test_volume.pyeditnova/volume/cinder.pyeditnova/tests/fake_volume.pyeditnova/compute/manager.pyeditnova/volume/api.pyeditnova/compute/api.pyeditnova/tests/policy.jsonRename _unplug_vifs to unplug_vifsby yunmaoeditnova/virt/vmwareapi/vmops.pyCheck flavor id on resize.by tagliapietra.alessandroeditnova/exception.pyeditnova/compute/api.pyeditnova/api/openstack/compute/servers.pyeditnova/tests/compute/test_compute.pyMakes key_name show in details view of serversby vishvanandaeditnova/api/openstack/compute/contrib/keypairs.pyeditnova/tests/api/openstack/compute/contrib/test_keypairs.pyConsole Output[...truncated 5567 lines...]dch -a [1b19fae] Remove unused AddressAlreadyAllocated exceptiondch -a [6281d67] Remove an unused importdch -a [7b24a76] Make ip block splitting a bit more self documenting.dch -a [c2501d8] Prevent Partial terminations in EC2dch -a [7483115] Handle missing network_size in nova-managedch -a [223b9f1] Adds API sample test for Flavors Extra Data extension.dch -a [d741328] Fix flavor deletion when there is a deleted flavordch -a [210dc28] Make size optional when creating a volume from a snapshot.dch -a [847fb38] Add documentation for scheduler filters scopedch -a [c2ec406] Add and fix tests for attaching volumes.dch -a [5f9ae51] Fix auth parameter passed to libvirt openAuth() methoddch -a [4c72bfc] xapi: Fix live block migrationdch -a [69f6b86] Add a criteria to sort a list of dict in api samplesdch -a [0d956a8] delete a module never useddch -a [0599406] Adds get_available_resource to hyperv driverdch -a [c3476b5] Create image of volume-backed instance via native APIdch -a [5339141] Improve floating IP delete speed.dch -a [1b87d59] Have device mapping use autocreated device nodesdch -a [79db483] remove a never used importdch -a [b35b34a] fix unmounting of LXC containers in the presence of symlinksdch -a [4fe722a] Add ServerStartStop extension API testdch -a [ccc0bfb] Set install_requires in setup.py.dch -a [85923aa] Add Server Detail and Metadata testsdch -a [6392ad2] xenapi: Make dom0 serialization consistent.dch -a [b97a0be] Correct ephemeral disk cache filename.dch -a [ff3b994] Handle missing 'provider_location' in rm_export.dch -a [4fc05bf] Nail the pip requirement at 1.1.dch -a [f192a16] rbd: implement create_volume_from_snapshotdch -a [0a09bf5] Specify the conf file when creating a volume.dch -a [1f82e30] Fix xml metadata for volumes api in nova-volume.debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File