Re: [Openstack] Why Image upload functionality is not there in Horizon ?
Hi Gabriel, On Thu, Aug 9, 2012 at 11:35 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: Indeed, uploading large files with the Horizon webserver as an intermediate relay is a nasty business which we want to discourage. We are looking at ways to send files directly from the Horizon client-side UI to swift/glance for large file upload in the future. I'm also trying a same kind of an approach, my question was also based on that. I was thinking of invoking Glance API s directly from the UI, not going through Horizon webserver. Earlier by Horizon I was referring to the UI only. Therefore, there is a practical usage of this kind of a feature, isn't it? All the best, - Gabriel -Original Message- From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Jay Pipes Sent: Thursday, August 09, 2012 10:43 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Why Image upload functionality is not there in Horizon ? On 08/09/2012 02:35 AM, Sajith Kariyawasam wrote: Hi all, After playing around with Openstack Mangement Console, Horizon, I realize that the image upload functionality is not provided there. Is there any special reason for that? Is it because there are no Rest services available at the moment? or else is it felt that providing image upload via the UI is not practically important? Probably because sending 20G Windows image files through a web form interface isn't very efficient ;) It's also not something a regular user of Glance/Nova would do -- and system administrators won't do it very often, and when they do, they'll use the glance CLI tool to do it. Best, -jay ___ 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 -- Best Regards Sajith ___ 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 ignores nova.conf
Nova does not respect the options set in the /etc/nova/nova.conf file. I've seen some examples with -- prefixing the flags, as if they are command line arguments. I've also seen examples without. I've tried removing the --, that does nothing. Specifically, I've set --flat_network_bridge=br0 --fixed_range=10.0.3.0/24 --flat_network_dhcp_start=10.0.3.1 I always get a br100 created with an IP address of 10.0.2.33 This is really annoying. If I empty the /etc/nova/nova.conf nothing gets created. I've greped all sorts of places for defaults, but come up blank. Any idea why this happens? Simon -- simonsmicrophone.com ___ 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 ignores nova.conf
On Fri, 2012-08-10 at 00:23 -0900, Simon Walter wrote: Nova does not respect the options set in the /etc/nova/nova.conf file. I've seen some examples with -- prefixing the flags, as if they are command line arguments. I've also seen examples without. I've tried removing the --, that does nothing. Specifically, I've set --flat_network_bridge=br0 --fixed_range=10.0.3.0/24 --flat_network_dhcp_start=10.0.3.1 I always get a br100 created with an IP address of 10.0.2.33 This is really annoying. If I empty the /etc/nova/nova.conf nothing gets created. I've greped all sorts of places for defaults, but come up blank. If nova is being run with --config-file, then the syntax is [DEFAULT] flat_network_bridge=br0 OTOH, if it is being run with --flagfile, the syntax is: --flat_network_bridge=br0 Cheers, Mark. ___ 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] why nova live-migration doesn't work？
What does compute and scheduler logs say? On Fri, Aug 10, 2012 at 10:23 AM, 王鹏 breakwin...@gmail.com wrote: Hi : everyone. when I test live-migration ,strangely,no error ,but instance don't move. please help me why ? the instance.log as follow: 2012-08-10 06:47:24.815+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-0034 -uuid 6c576b16-aabe-42d8-aae4-ef7d9ca4fbbd -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0034.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -drive file=/var/lib/nova/instances/instance-0034/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=20,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:5a:6f:fd,bus=pci.0,addr=0x3 -netdev tap,fd=21,id=hostnet1 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=fa:16:3e:76:ca:c6,bus=pci.0,addr=0x4 -chardev file,id=charserial0,path=/var/lib/nova/instances/instance-0034/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -usb -device usb-tablet,id=input0 -vnc 172.18.32.8:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 Domain id=1 is tainted: high-privileges char device redirected to /dev/pts/4 It look like just a start up log ?... thanks! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- --janis ___ 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] Metering meeting agenda for Thursday at 16:00 UTC (Aug 9th, 2012)
On 08/08/2012 05:54 PM, Nick Barcet wrote: Hi, The metering project team holds a meeting in #openstack-meeting, Thursdays at 1600 UTC http://www.timeanddate.com/worldclock/fixedtime.html?hour=16min=0sec=0. Everyone is welcome. Agenda: http://wiki.openstack.org/Meetings/MeteringAgenda * Review last week's actions - jaypipes to create ceilometer cookbook - jd_ to publish results of PTL election on general ml sometimes tomorrow - jtran to open a ticket for the DB access work - nijaba create a diagram of Ceilometer architecture * Discuss Doug's API change proposal * Discuss priority of maintaining Essex support and find contributor to work on it if we are going to do it * Discuss integration with Heat * 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. The meeting took place and here is the summary for it: == #openstack-meeting: Ceilometer == Meeting started by nijaba at 16:00:02 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-09-16.00.log.html . Meeting summary --- * LINK: http://wiki.openstack.org/Meetings/MeteringAgenda (nijaba, 16:00:02) * actions from previous meeting (nijaba, 16:01:42) * jaypipes to create ceilometer cookbook (nijaba, 16:01:56) * ACTION: jaypipes to create ceilometer cookbook (nijaba, 16:03:23) * jtran to open a ticket for the DB access work (nijaba, 16:03:41) * LINK: https://bugs.launchpad.net/ceilometer/+bug/1034666 (nijaba, 16:03:50) * nijaba to create a diagram of ceilometer architecture (nijaba, 16:04:03) * LINK: https://docs.google.com/drawings/pub?id=1_cIFir6HS6jSkPw7chrmyu8DGE2ZgXk79Kbj8nw-Hqow=960h=720 (nijaba, 16:04:13) * ACTION: nijaba to write description of componet responsibility (nijaba, 16:06:58) * Discuss dhellmann's API change proposal (nijaba, 16:07:21) * LINK: http://lists.openstack.org/pipermail/openstack-dev/2012-August/000389.html (nijaba, 16:07:21) * AGREED: new api proposal from dhellmann provide a second check that all case are covered (nijaba, 16:11:42) * ACTION: nijaba to do a second thouroughness check on API and report next week (nijaba, 16:12:01) * Discuss priority of maintaining Essex support and find contributor to work on it if we are going to do it (nijaba, 16:12:18) * AGREED: essex support postponed until someone that cares about it signals himself and want to work on it (nijaba, 16:16:57) * Discuss integration with Heat (nijaba, 16:17:19) * AGREED: propose a joint session with heat at ODS regarding cloudwatch (nijaba, 16:26:53) * Open Discusssion (nijaba, 16:28:52) Meeting ended at 16:40:44 UTC. Action items, by person --- * jaypipes * jaypipes to create ceilometer cookbook * nijaba * nijaba to write description of componet responsibility * nijaba to do a second thouroughness check on API and report next week People present (lines said) --- * nijaba (95) * dhellmann (27) * jd___ (24) * ppetit (22) * jaypipes (3) * openstack (3) * mrevell (2) * uvirtbot (1) * gmb (1) * DanD (1) Generated by `MeetBot`_ 0.1.4 -- 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] Invoking Glance REST API
Thanks Brian.. that worked ..! :) On Thu, Aug 9, 2012 at 9:31 PM, Brian Waldon bcwal...@gmail.com wrote: You're getting a '300 Multiple Choices' response as you haven't indicated a version in your request. You can parse the body as json (indicated in the headers) to see what API versions are available to you at any given time. If you don't care about taking that extra step, just use a URI with 'v1' as the first token in your path: http:// Glance_URL:PORT/v1/images/detail Brian Waldon On Aug 9, 2012, at 2:05 AM, Sajith Kariyawasam wrote: Hi all, I'm trying to invoke Openstack Glance REST API s using a Java client, to get image details. etc (Ultimately I need to upload an image) When I invoke http://Glance_URL:PORT/images/detail GET request in Java code, I'm getting *HTTP 300 *as the response code. 4 300 4 Date: Thu, 09 Aug 2012 08:56:29 GMT 4 Content-Length: 222 4 Content-Type: application/json 4 Connection: keep-alive Any idea what could have gone wrong there? -- Best Regards Sajith ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Best Regards Sajith ___ 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] Call for Help -- OpenStack API XML Support
-Original Message- From: openstack- bounces+gabe.westmaas=rackspace@lists.launchpad.net [mailto:openstack- bounces+gabe.westmaas=rackspace@lists.launchpad.net] On Behalf Of Daniel P. Berrange Sent: Friday, August 10, 2012 8:48 AM To: Vishvananda Ishaya Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [nova] Call for Help -- OpenStack API XML Support On Thu, Aug 09, 2012 at 03:25:01PM -0700, Vishvananda Ishaya wrote: Hello Everyone, We are in the unfortunate position of not knowing how good our OpenStack API XML support is. All of our integration tests use json. Many of the compute extensions don't even have XML deserializers. We also assume that there bugs we don't even know about due to underuse. We need to do something about XML by Folsom, because releasing a buggy api isn't good for anyone. I don't know this area of Nova code at all, but I must say I'm surprised that it actually needs explicit extra work to accept or output XML, instead of JSON. It should be possible to auto generate an XML document from a JSON document, and vica-verca. At which point you'd not need to have 2 sets of tests for JSON vs XML, all you need test is the XML-JSON conversions. I can imagine this isn't done because of a need to maintain compat with some special XML schema that isn't a direct 1-1 mapping from the JSON schema ? Are there other complications preventing this being done Correct. Extensions also cause some issues, though it all basically comes back to not being a 1-1 mapping. The reason it's not 1-1 is not because of different data, but just the representation of the same data. 1) We get a lot of community support and we manage to get XML into usable shape by Folsom. 2) We get enough community support to get the core api working and the most important extensions in place. We release clear documentation on what is expected to work. 3) We get no support, in which case we mark XML support deprecated and encourage people to use JSON only. 4) Deprecate the current XML schemas, and declare new XML schemas which are a 1-1 mapping from the JSON The biggest problem with this is that either json or XML ends up feeling second class. If you were writing XML for XML's sake it wouldn't come out looking like XML generated from json schemas. I will say that the reason it came out like this in the current API is that XML was first class with auto-generated JSON, which was pretty bad. Rather than going the other way, we opted to keep both optimized for development against the API rather than for development of the API. Anyway, not saying it can't be done, but I am saying that XML will feel like a second class format. This mostly has to do with figuring out when something should be an attribute of an element vs when it should be a value of an element. I think we ran into some issues around collections that were non-auto-translatable as well, but I'm struggling to remember them. We can decide to just pick a translation and go with it, of course. Although perhaps we need an expert on enterprise tools to make sure that the XML we generate properly translates into sane objects in those enterprise tools. Note that other openstack projects only support json, and there are already java bindings that use json so option 3) isn't terrible, but we don't want to go that route without discussing it with the community first. If anyone has alternative solutions or suggestions, feel free to let me know. If we can get to a position where we auto-generate XML from JSON for Nova, we could do the same for other projects too Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ 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] Call for Help -- OpenStack API XML Support
-Original Message- From: openstack- bounces+gabe.westmaas=rackspace@lists.launchpad.net [mailto:openstack- bounces+gabe.westmaas=rackspace@lists.launchpad.net] On Behalf Of Gabe Westmaas Sent: Friday, August 10, 2012 9:15 AM To: Daniel P. Berrange; Vishvananda Ishaya Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [nova] Call for Help -- OpenStack API XML Support -Original Message- From: openstack- bounces+gabe.westmaas=rackspace@lists.launchpad.net [mailto:openstack- bounces+gabe.westmaas=rackspace@lists.launchpad.net] On Behalf Of Daniel P. Berrange Sent: Friday, August 10, 2012 8:48 AM To: Vishvananda Ishaya Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] [nova] Call for Help -- OpenStack API XML Support On Thu, Aug 09, 2012 at 03:25:01PM -0700, Vishvananda Ishaya wrote: Hello Everyone, We are in the unfortunate position of not knowing how good our OpenStack API XML support is. All of our integration tests use json. Many of the compute extensions don't even have XML deserializers. We also assume that there bugs we don't even know about due to underuse. We need to do something about XML by Folsom, because releasing a buggy api isn't good for anyone. I don't know this area of Nova code at all, but I must say I'm surprised that it actually needs explicit extra work to accept or output XML, instead of JSON. It should be possible to auto generate an XML document from a JSON document, and vica-verca. At which point you'd not need to have 2 sets of tests for JSON vs XML, all you need test is the XML-JSON conversions. I can imagine this isn't done because of a need to maintain compat with some special XML schema that isn't a direct 1-1 mapping from the JSON schema ? Are there other complications preventing this being done Correct. Extensions also cause some issues, though it all basically comes back to not being a 1-1 mapping. The reason it's not 1-1 is not because of different data, but just the representation of the same data. 1) We get a lot of community support and we manage to get XML into usable shape by Folsom. 2) We get enough community support to get the core api working and the most important extensions in place. We release clear documentation on what is expected to work. 3) We get no support, in which case we mark XML support deprecated and encourage people to use JSON only. 4) Deprecate the current XML schemas, and declare new XML schemas which are a 1-1 mapping from the JSON The biggest problem with this is that either json or XML ends up feeling second class. If you were writing XML for XML's sake it wouldn't come out looking like XML generated from json schemas. I will say that the reason it came out like this in the current API is that XML was first class with auto- generated JSON, which was pretty bad. Rather than going the other way, we opted to keep both optimized for development against the API rather than for development of the API. Anyway, not saying it can't be done, but I am saying that XML will feel like a second class format. This mostly has to do with figuring out when something should be an attribute of an element vs when it should be a value of an element. I think we ran into some issues around collections that were non- auto-translatable as well, but I'm struggling to remember them. We can decide to just pick a translation and go with it, of course. Although perhaps we need an expert on enterprise tools to make sure that the XML we generate properly translates into sane objects in those enterprise tools. Oh, and, even if we do this, that does not remove the need for additional tests around XML, of course. We still need to make sure that is working correctly. Note that other openstack projects only support json, and there are already java bindings that use json so option 3) isn't terrible, but we don't want to go that route without discussing it with the community first. If anyone has alternative solutions or suggestions, feel free to let me know. If we can get to a position where we auto-generate XML from JSON for Nova, we could do the same for other projects too Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe :
Re: [Openstack] [Nova] Create multiple instances in one request
Hi, So, if I paraphrase correctly what is meant out of the stacker jargon. min_count and max_count doc will go in the API doc as an extension item once the DisableServerExtension cleanup is done. Right? However, the original question was about the *num_instances* property of the RPC request spec. I do not see a direct relationship with min_count and max_count. So, is num_instances another undocumented API extension parameter or something else? I can see also that DisableServerExtensions proposal mentions a *reservation_id *parameter... Can someone explain what it is ? Is it to support server reservation like in AWS EC2? And so, would a user be able to create a reservation (that is, not to actually create the reserve servers but to reserve the) with say additional min_count max_count parameters in the request. The reservation would fail if min_count cannot be honored by OpenStack. If the reservation can be honored, would return a reservation_id along with a value between min_count and max_count. Is this a correct understanding of the behavior or complete speculation? Thanks for shedding some light on this Best regards, Patrick 2012/8/7 Anne Gentle a...@openstack.org These were documented but then pulled out because min_count and max_count are not to spec. We are now working on a cleanup effort described at http://wiki.openstack.org/DisableServerExtensions. It seems the log from the last Nova meeting where this was discussed is gathered together with the QA team meeting due to the meetbot not being turned off between meetings. The log is here, scroll to the bottom to read. http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-17.00.log.html Hope this is helpful - though cleanup will be the most helpful, please feel free to join in the effort. :) Anne On Tue, Aug 7, 2012 at 1:13 PM, David Kranz david.kr...@qrclab.com wrote: It is a little strange but the following seems to be true. 1. The nova HTTP API has a max_count and min_count that go in the request dictionary. 2. This is not documented. 3. The novaclient python api create function has these arguments. 4. The novaclient cli does not have them, or at least they are not documented by 'nova help boot'. Beats me why this is the case... -David On 8/7/2012 1:47 PM, Patrick Petit wrote: Dear All, Looking into the details of the request_spec part of a RPC message ensuing a nova boot command. There is a 'num_instances' : 1 property that implies the value could be different than one (default) even though there is no cardinality parameter in nova boot nor in the API (unless I missed something big). So, I am curious to know: why is it there if we cannot create more than one instance at a time through the API, but more importantly is there a (secret) way to set that value different than 1 to tell the scheduler please create multiple instances of that type. Thanks in advance Patrick ___ 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 -- *Give me a place to stand, and I shall move the earth with a lever* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Manually attaching iSCSI volume to an instance
Hi, I believe I am a victim of this bug: https://bugs.launchpad.net/nova/+bug/1001088 ( I can not seem to find the fix that was committed ) After rebooting my volumes are not restored and they become stuck in the in-use state. Is there a way to manually restore the volumes? Using tgt-admin I verified that the target exists, I used iscsiadm to login, and verified that created a device node. Here is a log showing what I just mentioned: http://paste2.org/p/2101666 And here is a document I created showing my general setup, including nova.conf. (I didn't include glance, or keystone configs because they seem to be working fine): https://docs.google.com/document/d/1pkwGa22OfATp62hVGYR3jWTEbhQVyHIpwOJgaSrbQ7M/edit Any help would be greatly appreciated. Thanks, Sam ___ 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] Why Image upload functionality is not there in Horizon ?
Even being able to add images while providing an external location would be useful. You could depend on your user to put it in swift or s3 and just provide a uri that references it. On Aug 9, 2012, at 11:05 AM, Gabriel Hurley wrote: Indeed, uploading large files with the Horizon webserver as an intermediate relay is a nasty business which we want to discourage. We are looking at ways to send files directly from the Horizon client-side UI to swift/glance for large file upload in the future. All the best, - Gabriel -Original Message- From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Jay Pipes Sent: Thursday, August 09, 2012 10:43 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Why Image upload functionality is not there in Horizon ? On 08/09/2012 02:35 AM, Sajith Kariyawasam wrote: Hi all, After playing around with Openstack Mangement Console, Horizon, I realize that the image upload functionality is not provided there. Is there any special reason for that? Is it because there are no Rest services available at the moment? or else is it felt that providing image upload via the UI is not practically important? Probably because sending 20G Windows image files through a web form interface isn't very efficient ;) It's also not something a regular user of Glance/Nova would do -- and system administrators won't do it very often, and when they do, they'll use the glance CLI tool to do it. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Quantum] Removing quantum-rootwrap
From: Thierry Carrez thie...@openstack.org Date: Thu, 09 Aug 2012 16:32:23 +0200 [...] My goal is by end of today , or tomorrow morning latest, to have at least a reasonably complete understanding of the changes necessary to get the quantum-rootwrap facility up to parity with nova/cinder. If I get to that deadline and I'm not there, I'll probably punt, as it becomes too much of a hail-mary to get the stuff stabilized and reviewed etc by tues. That sounds reasonable. Ok, here's what I think I know, and what I propose to do with it: Fix quantum/bin/quantum-rootwrap to mimic changes to nova/cinder w/r/t conf file. This will introduce the notion of /etc/quantum/rootwrap.conf and allow for specifying path to filter specs. Fix quantum/rootwrap/filters.py likewise; update KillFilter (maybe more?) Fix quantum/rootwrap/wrapper.py likewise; load from files and construct filter datastructures Create etc/quantum/quantum-rootwrap.conf etc/quantum/rootwrap.d/ Move the filter specs from the various agent pieces in quantum/rootwrap to matching files in etc/quantum/filters.d. Update them while I'm at it. This probably means that those files in quantum/rootwrap go away. Alternate implementation: Collect all those pieces into a consolidated quantum.filters file and stick that in there. There appears to be no analog of nova/tests/test_nova_rootwrap.py for quantum, so I'll likely need to write something for that. It looks like the various .ini files in etc/quantum/plugins all set root helper for each agent. Keep that structure for now, revisit later. That likely means I'll need a way to propagate the a default root helper setting from the conf to each agent. Devstack appears to frob configs in nova and cinder, but copy the quantum configs verbatim. So I'm hoping I can get away without modifying devstack. Things I don't know yet: Python compatibility? I'm running 2.7; I don't believe anything I'm doing would break in earlier ones, but I gather that that will need to be tested before I'm done. Will I need to hair up the filter match code? I don't think so, but I haven't gotten enough working yet to tell. Hoping I can leave it as is. Apologies for the not-very coherent description. Please let me know if you think I'm off in the weeds or missing important bits. Thanks in advance... ___ 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] Trouble getting instances back up after hard server reboot
Hi Samuel, I am interested in some common/best practices of this as well. I'm posting this to -operators to see if anyone there has input. While having instances affected by a compute node reboot does not sound very cloudy, it is unfortunately an issue can happen often. I have added some notes inline. On Thu, Aug 9, 2012 at 1:55 PM, Samuel Winchenbach swinc...@gmail.comwrote: Hi all, I am having a terrible time getting my instances to work after a hard reboot. I am using the most up-to date version of all openstack packages provided by Ubuntu. I have included a list of packages, with version, at the end of this email. After a hard reboot nova list reports that the instance is active, but there are no kvm processes running. grepping the log file for errors I find this in nova-compute.log: If the reboot is quick, nova will still report the instances as active. If the reboot takes 10 minutes or so, nova notices that the instances are down and marks them in a Shut Down state with a continuously spinning circle. I've found that in both scenarios, issuing a reboot either via Horizon or the cli resolves the issue most of the time -- nova will send a reboot request to KVM which then re-launches the instance. 2012-08-09 14:32:51 INFO nova.rpc.common [req-dd6fcade-73ec-4378-9a6b-7bc709eefcd4 None None] Connected to AMQP server on cloudy-priv:5672 2012-08-09 14:33:51 ERROR nova.rpc.common [req-dd6fcade-73ec-4378-9a6b-7bc709eefcd4 None None] Timed out waiting for RPC response: timed out 2012-08-09 14:33:51 TRACE nova.rpc.common Traceback (most recent call last): 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 490, in ensure 2012-08-09 14:33:51 TRACE nova.rpc.common return method(*args, **kwargs) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py, line 567, in _consume 2012-08-09 14:33:51 TRACE nova.rpc.common return self.connection.drain_events(timeout=timeout) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/connection.py, line 175, in drain_events 2012-08-09 14:33:51 TRACE nova.rpc.common return self.transport.drain_events(self.connection, **kwargs) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 238, in drain_events 2012-08-09 14:33:51 TRACE nova.rpc.common return connection.drain_events(**kwargs) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 57, in drain_events 2012-08-09 14:33:51 TRACE nova.rpc.common return self.wait_multi(self.channels.values(), timeout=timeout) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 63, in wait_multi 2012-08-09 14:33:51 TRACE nova.rpc.common chanmap.keys(), allowed_methods, timeout=timeout) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 120, in _wait_multiple 2012-08-09 14:33:51 TRACE nova.rpc.common channel, method_sig, args, content = read_timeout(timeout) 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py, line 94, in read_timeout 2012-08-09 14:33:51 TRACE nova.rpc.common return self.method_reader.read_method() 2012-08-09 14:33:51 TRACE nova.rpc.common File /usr/lib/python2.7/dist-packages/amqplib/client_0_8/method_framing.py, line 221, in read_method 2012-08-09 14:33:51 TRACE nova.rpc.common raise m 2012-08-09 14:33:51 TRACE nova.rpc.common timeout: timed out 2012-08-09 14:33:51 TRACE nova.rpc.common 2012-08-09 14:33:51 CRITICAL nova [-] Timeout while waiting on RPC response. restarting nova-compute brings the instance up, so it looks like nova-compute is starting before rabbitmq? Is there a clean way around this, or should I put service nova-compute restart in rc.local? If I have a volume attached things get much worse. I can still start the instance by restarting nova-compute, but the volume does not attach. Yes, dealing with volumes after a reboot plain sucks. Most of the time, I end up manually setting the volume as detached and available in the volumes table of the database. Sometimes I have to log into the server that hosts the volume and cut the iscsi connection. And if there was IO traffic between the instance and volume at the time of reboot, you'll most likely need to fsck the volume when it is reattached to the instance. I can not seem to detach the volume in order to attach it again. Below is the only error in the log file, and how I mount the image that contains the nova-volume logical group.The error occurs because it tries to start nova-volume before the loopback device is setup. My only recommendation for this is to not use a
Re: [Openstack] [Quantum] Removing quantum-rootwrap
From: Thierry Carrez thie...@openstack.org Date: Fri, 10 Aug 2012 17:38:52 +0200 j...@redhat.com wrote: Apologies for the not-very coherent description. Please let me know if you think I'm off in the weeds or missing important bits. One other thing I spotted when I evaluated how broken quantum-rootwrap was is at quantum/agent/linux/dhcp.py:181 where a command is called with environment set. That works with sudo but rootwrap clears the environment. This call therefore needs a specific filter (and probably never worked with rootwrap). Hmmm. I hadn't even considered that. Ok, I'll keep that in mind as I'm in there. There is one filter defined for dnsmasq (the DnsmasqFilter which is defined at quantum/rootwrap/filters.py:71) but it sets a slightly different set of env variables. So it might need to be adapted (or the call adjusted). Fair enough. I don't even know what that does yet, so will need to work that out and figure out how to adjust. Hope this helps. Very much, thanks. More news as it happens... ___ 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] Operational knowledge sharing
In a standard swift deployment, the proxy server is running behind a load balancer and/or an SSL terminator. At SwiftStack, we discovered an issue that may arise from some config parameters in this layer, and we'd like to share it with other swift deployers. Symptom: Users updating metadata (ie POST) on larger objects get 503 error responses. However, there are no error responses logged by swift. Cause: Since POSTs are implemented, by default, as a server-side copy in swift and there is no traffic between the user and swift during the server-side copy, the LB or SSL terminator times out before the operation is done. Solution: Two options: 1) Raise the timeout in the LB/SSL terminator config. For example, with pound change the TimeOut for the swift backend. pound defaults to 15 seconds. The appropriate value is however log it takes to do a server side copy of your largest object. If you have a 1gbps network, it will take about 160 seconds to copy a 5GB object ((8*5*2**30)/((2**30)/4) -- the divide by 4 is because the 1gbps link is used to read one stream (the original) and write the new copy (3 replicas)). 2) Change the behavior of POSTs to not do a server-side copy. This will make POSTs faster, but it will prevent all metadata values from being updated (notably, Content-Type will not be able to be modified with a POST). Also, this will not make the issue go away with user-initiated server-side copies. I would recommend the first solution, unless your workload makes heavy use of POSTs. Hoep this helps. --John 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
[Openstack] Open Standards for Open Cloud: Call for particpation
Dear all, As a follow up of last year's session “Open Cloud in Europe”, we have the pleasure to organize a whole Open World Forumhttp://www.openworldforum.org/entrack dedicated to open cloud and open standards, and would like to invite you to participate in this session to provide feedback from open cloud projects and on the usage of open standards. The goal is to support Standards Development Organisations with your experience and insight: we want this meeting to be a forum where those who get their “hands dirty”, who are experienced in creating and deploying cloud applications, can present and question usage of and requirements for open standards. We are looking for experienced developers who have faced issues when: * using non-standard APIs, * moving from non-standard/de-facto APIs/libraries to standard implementations, * failing to use cloud standards, * achieving interoperability between implementations / standards, * achieving portability between implementations (e.g. there is no VM image standard... or is there?), * trying to avoid implementation / provider lock-in, * working on automation. So if you can answer positively at least one of the following questions, you are the kind of candidate we would be delighted to welcome on this track. * Are you implementing standards? * Are you interfacing to standards? * Are you working on standards specifications? * Do you want to bring issues and/or highlight deficiencies regarding standardisation? * Do you want to demonstrate your implementation/solution using standardised APIs? * Are you working on a “framework project” (OpenStack, OpenNebula, CloudStack, Eucalyptus, CompatibleOne, …) and like to share your thoughts on which role they play with respect to standards development and adoption? * Do you work on multiple clouds? Do you deal with many interfaces? * Do you face issues moving your application from one provider to another? Your proposal should be sent by the 10th of September 2012 at the latest, to ow...@ogf.org Your participation will be confirmed in until 25th of September 2012. Looking forward to meeting you, Alan Sill and Florian Feldhaus, Andrew Edmonds, Andre Merzky, Jean-Pierre Laisné on behalf of OGF, OCCI Working Group and OW2 When: Friday 12th October Where: Open World Forum http://www.openworldforum.org/en What: Cloud computing is perceived as a new IT domain where interoperability, portability and reversibility sound like impossible issues to solve. This session will demonstrate how open and interoperable clouds are possible in the face of service provider lock-in. The audience will be able to evaluate the gaps and the real solutions to make open cloud, i.e. a cloud of freedom of choice, a reality. ___ 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] Why Image upload functionality is not there in Horizon ?
Horizon already has what you just described. You can load images into glance by providing a URI. It's the Create Image button on the Images table. - Gabriel -Original Message- From: Brian Waldon [mailto:bcwal...@gmail.com] Sent: Friday, August 10, 2012 7:35 AM To: Gabriel Hurley Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Why Image upload functionality is not there in Horizon ? Even being able to add images while providing an external location would be useful. You could depend on your user to put it in swift or s3 and just provide a uri that references it. On Aug 9, 2012, at 11:05 AM, Gabriel Hurley wrote: Indeed, uploading large files with the Horizon webserver as an intermediate relay is a nasty business which we want to discourage. We are looking at ways to send files directly from the Horizon client-side UI to swift/glance for large file upload in the future. All the best, - Gabriel -Original Message- From: openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack- bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of bounces+Jay Pipes Sent: Thursday, August 09, 2012 10:43 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Why Image upload functionality is not there in Horizon ? On 08/09/2012 02:35 AM, Sajith Kariyawasam wrote: Hi all, After playing around with Openstack Mangement Console, Horizon, I realize that the image upload functionality is not provided there. Is there any special reason for that? Is it because there are no Rest services available at the moment? or else is it felt that providing image upload via the UI is not practically important? Probably because sending 20G Windows image files through a web form interface isn't very efficient ;) It's also not something a regular user of Glance/Nova would do -- and system administrators won't do it very often, and when they do, they'll use the glance CLI tool to do it. Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [swift] Operational knowledge sharing
Thanks for sharing. On Fri, Aug 10, 2012 at 12:31 PM, John Dickinson m...@not.mn wrote: In a standard swift deployment, the proxy server is running behind a load balancer and/or an SSL terminator. At SwiftStack, we discovered an issue that may arise from some config parameters in this layer, and we'd like to share it with other swift deployers. Symptom: Users updating metadata (ie POST) on larger objects get 503 error responses. However, there are no error responses logged by swift. Cause: Since POSTs are implemented, by default, as a server-side copy in swift and there is no traffic between the user and swift during the server-side copy, the LB or SSL terminator times out before the operation is done. Solution: Two options: 1) Raise the timeout in the LB/SSL terminator config. For example, with pound change the TimeOut for the swift backend. pound defaults to 15 seconds. The appropriate value is however log it takes to do a server side copy of your largest object. If you have a 1gbps network, it will take about 160 seconds to copy a 5GB object ((8*5*2**30)/((2**30)/4) -- the divide by 4 is because the 1gbps link is used to read one stream (the original) and write the new copy (3 replicas)). 2) Change the behavior of POSTs to not do a server-side copy. This will make POSTs faster, but it will prevent all metadata values from being updated (notably, Content-Type will not be able to be modified with a POST). Also, this will not make the issue go away with user-initiated server-side copies. I would recommend the first solution, unless your workload makes heavy use of POSTs. Hoep this helps. --John ___ 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] Create multiple instances in one request
On Aug 10, 2012, at 6:24 AM, Patrick Petit patrick.michel.pe...@gmail.com wrote: Hi, So, if I paraphrase correctly what is meant out of the stacker jargon. min_count and max_count doc will go in the API doc as an extension item once the DisableServerExtension cleanup is done. Right? Correct. However, the original question was about the num_instances property of the RPC request spec. I do not see a direct relationship with min_count and max_count. So, is num_instances another undocumented API extension parameter or something else? The RPC code is internal and undocumented at the moment. The num_instances parameter is generated from min_count and max_count based on quota: 399 num_instances, quota_reservations = self._check_num_instances_quota( 400 context, instance_type, min_count, max_count) so if you have min_count = 3, max_count = 9: whith a quota of 10 you num_instances = 5 with a quota of 10, num_instances = 9 with a quota of 2, you will get a QuotaExceeded exception. I hope that clarifies things. I can see also that DisableServerExtensions proposal mentions a reservation_id parameter... Can someone explain what it is ? Is it to support server reservation like in AWS EC2? And so, would a user be able to create a reservation (that is, not to actually create the reserve servers but to reserve the) with say additional min_count max_count parameters in the request. The reservation would fail if min_count cannot be honored by OpenStack. If the reservation can be honored, would return a reservation_id along with a value between min_count and max_count. Is this a correct understanding of the behavior or complete speculation? return_reservation_id will tell the server create request to return reservation_ids instead of a single server instance, it will be part of the os-multiple-instances extension along with min_count and max_count: https://review.openstack.org/#/c/11090/ 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] [swift] Operational knowledge sharing
This is great info, John. Thanks. John John Purrier j...@openstack.com (206) 930-0788 http://www.linkedin.com/in/johnpur On 8/10/12 9:31 AM, John Dickinson m...@not.mn wrote: In a standard swift deployment, the proxy server is running behind a load balancer and/or an SSL terminator. At SwiftStack, we discovered an issue that may arise from some config parameters in this layer, and we'd like to share it with other swift deployers. Symptom: Users updating metadata (ie POST) on larger objects get 503 error responses. However, there are no error responses logged by swift. Cause: Since POSTs are implemented, by default, as a server-side copy in swift and there is no traffic between the user and swift during the server-side copy, the LB or SSL terminator times out before the operation is done. Solution: Two options: 1) Raise the timeout in the LB/SSL terminator config. For example, with pound change the TimeOut for the swift backend. pound defaults to 15 seconds. The appropriate value is however log it takes to do a server side copy of your largest object. If you have a 1gbps network, it will take about 160 seconds to copy a 5GB object ((8*5*2**30)/((2**30)/4) -- the divide by 4 is because the 1gbps link is used to read one stream (the original) and write the new copy (3 replicas)). 2) Change the behavior of POSTs to not do a server-side copy. This will make POSTs faster, but it will prevent all metadata values from being updated (notably, Content-Type will not be able to be modified with a POST). Also, this will not make the issue go away with user-initiated server-side copies. I would recommend the first solution, unless your workload makes heavy use of POSTs. Hoep this helps. --John ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support
On 08/09/2012 11:05 PM, George Reese wrote: On Aug 9, 2012, at 8:14 PM, Doug Davis d...@us.ibm.com mailto:d...@us.ibm.com wrote: Situations like this are always interesting to watch. :-) On the one hand its open-source, so if you care about something then put up the resources to make it happen. This attitude always bothers me. This isn't some Open Source labor of love. It's a commercial collaboration in which many of the contributors have a significant economic interest. To be more blunt: if I'm writing code, it's for enStratus. Patches always welcome, George. If you can't see that code you may write for enStratus might be globally useful, then you're missing the point of this open development community. And although there are many in this OpenStack community that work for a commercial entity and contribute code as such, there are many who don't -- and dismissing their contributions as some Open Source labor of love is degrading and shows the type of opinion you have towards anything that doesn't fit nicely in your everything-is-a-commercial-agenda worldview. If you care about something, then help to fix it. -jay ___ 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] jcloud has a conneciton pool?
Hi Folks, I am working on Jcloud and Openstack. We have application(using jcloud) to connect Hp cloud service. But for each request to HP cloud service, we created restContext (RestContextNovaApi, NovaAsyncApi restContext = computeContext.unwrap();), then get NovaAPi ( NovaApi novaApi = restContext.getApi();). once task is finished, we closed restContext, so this is not efficient. since each request to create restconects, then closed once job is done. There is any way to reuse this restContext and NoavaApi? do i need to build a connection pool to reuse it? I am not sure originally why engineers did in this way. it may for security reason since each request we ask token from service. Thank you, Chwang ___ 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] Removing support for KVM Hypervisor ...
Sorry George, couldn't resist. :) ___ 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] Removing support for KVM Hypervisor ...
haha ... oh no. It's joke. Long story. Not going to happen :) From: chaohua wang [chwang...@gmail.com] Sent: Friday, August 10, 2012 5:31 PM To: Sandy Walsh Subject: Re: [Openstack] Removing support for KVM Hypervisor ... Hi I posted my question to openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net but i can't see it, Could you tell me reason why? thank you, Chaohua On Fri, Aug 10, 2012 at 2:23 PM, Sandy Walsh sandy.wa...@rackspace.commailto:sandy.wa...@rackspace.com wrote: Sorry George, couldn't resist. :) ___ 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] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support
On Aug 10, 2012, at 2:52 PM, Jay Pipes jaypi...@gmail.com wrote: On 08/09/2012 11:05 PM, George Reese wrote: On Aug 9, 2012, at 8:14 PM, Doug Davis d...@us.ibm.com mailto:d...@us.ibm.com wrote: Situations like this are always interesting to watch. :-) On the one hand its open-source, so if you care about something then put up the resources to make it happen. This attitude always bothers me. This isn't some Open Source labor of love. It's a commercial collaboration in which many of the contributors have a significant economic interest. To be more blunt: if I'm writing code, it's for enStratus. Patches always welcome, George. If you can't see that code you may write for enStratus might be globally useful, then you're missing the point of this open development community. And although there are many in this OpenStack community that work for a commercial entity and contribute code as such, there are many who don't -- and dismissing their contributions as some Open Source labor of love is degrading and shows the type of opinion you have towards anything that doesn't fit nicely in your everything-is-a-commercial-agenda worldview. If you care about something, then help to fix it. Either you aren't reading what I am writing or you can't read. I'm willing to bet I have written more lines of Open Source code over more years than you have. So don't start assigning some kind of evil capitalist motives on me. The fact that I don't have code going into enStratus that is not of use to OpenStack is not an indication that a) I have some kind of everything-is-a-commercial-agenda worldview or b) that I don't do Open Source or c) I don't think that some Open Source is a labor of love. OpenStack is a commercial agenda however. Pretending that it's a labor of love and people should feel lucky to get functionality is just daft. -George -- 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] jcloud has a conneciton pool?
On 08/10/2012 04:14 PM, chaohua wang wrote: Hi Folks, I am working on Jcloud and Openstack. We have application(using jcloud) to connect Hp cloud service. But for each request to HP cloud service, we created restContext (RestContextNovaApi, NovaAsyncApi restContext = computeContext.unwrap();), then get NovaAPi ( NovaApi novaApi = restContext.getApi();). once task is finished, we closed restContext, so this is not efficient. since each request to create restconects, then closed once job is done. There is any way to reuse this restContext and NoavaApi? do i need to build a connection pool to reuse it? I am not sure originally why engineers did in this way. it may for security reason since each request we ask token from service. Hi Chwang, an interesting question indeed, but I think it may be better to ask over on the jClouds mailing list. Not sure there are too many experts on jClouds here on the OpenStack mailing list! :) Here is the jCloud ML, for reference: https://groups.google.com/forum/?fromgroups#!forum/jclouds Best, -jay ___ 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] [swift] Operational knowledge sharing
Followup note: Though briefly mentioned by John, I like to emphasize this also affects COPY (or PUT with X-Copy-From) requests, and #1 (upping the lb timeout) is really the only solution unless we go crazy and implement async requests with status checks. Well, another weird solution is to have Swift return useless response bodies very slowly as a keep alive. :) On Aug 10, 2012, at 11:31 AM, John Dickinson m...@not.mn wrote: In a standard swift deployment, the proxy server is running behind a load balancer and/or an SSL terminator. At SwiftStack, we discovered an issue that may arise from some config parameters in this layer, and we'd like to share it with other swift deployers. Symptom: Users updating metadata (ie POST) on larger objects get 503 error responses. However, there are no error responses logged by swift. Cause: Since POSTs are implemented, by default, as a server-side copy in swift and there is no traffic between the user and swift during the server-side copy, the LB or SSL terminator times out before the operation is done. Solution: Two options: 1) Raise the timeout in the LB/SSL terminator config. For example, with pound change the TimeOut for the swift backend. pound defaults to 15 seconds. The appropriate value is however log it takes to do a server side copy of your largest object. If you have a 1gbps network, it will take about 160 seconds to copy a 5GB object ((8*5*2**30)/((2**30)/4) -- the divide by 4 is because the 1gbps link is used to read one stream (the original) and write the new copy (3 replicas)). 2) Change the behavior of POSTs to not do a server-side copy. This will make POSTs faster, but it will prevent all metadata values from being updated (notably, Content-Type will not be able to be modified with a POST). Also, this will not make the issue go away with user-initiated server-side copies. I would recommend the first solution, unless your workload makes heavy use of POSTs. Hoep this helps. --John ___ 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] instance evacuation from a failed node (rebuild for HA)
Dear all, We have submitted a patch https://review.openstack.org/#/c/11086/ to address https://blueprints.launchpad.net/nova/+spec/rebuild-for-ha that simplifies recovery from a node failure by introducing an API that recreates an instance on *another* host (similar to the existing instance 'rebuild' operation). The exact semantics of this operations varies depending on the configuration of the instances and the underlying storage topology. For example, if it is a regular 'ephemeral' instance, invoking will respawn from the same image on another node while retaining the same identity and configuration (e.g. same ID, flavor, IP, attached volumes, etc). For instances running off shared storage (i.e. same instance file accessible on the target host), the VM will be re-created and point to the same instance file while retaining the identity and configuration. More details are available at http://wiki.openstack.org/Evacuate. Note that the API must be manually invoked today. In addition, this patch modifies nova-compute such that on startup (e.g., after it failed and recovered) it verifies with the DB that it is still the owner of an instance before starting the VM. Would be great to hear whether people think that such a capability is important to push into Folsom, despite the short runway till F3. Any other thoughts/recommendations regarding such capability would be also highly appreciated. Thanks, Alex Alex Glikson Manager, Cloud Operating System Technologies, IBM Haifa Research Lab http://w3.haifa.ibm.com/dept/stt/cloud_sys.html | https://www.research.ibm.com/haifa/dept/stt/cloud_sys.shtml Email: glik...@il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-647 | Fax: +972-4-8296112 ___ 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] Setting Expectations
What is OpenStack? Clearly, OpenStack is many things to many people and organizations. What does it mean to contribute to OpenStack? What does it mean to deploy OpenStack? What does it mean to operate OpenStack? What do we mean when we say compatible? interoperable? community? branded? Is OpenStack a framework? a project? a product? Recent discussions make it clear that we have a lot of different ideas about all of these things. Our collective and individual responsibilities to each other are also a point of tension. There is a marked difference in the perspective of those developing the projects, those operating the projects as services and the final consumers/clients of those services. If OpenStack is going to live up to it's full potential and stated mission, I believe there needs to be a much stronger collective conscience about how decisions are made. I feel we will all benefit by making some things more explicit. If the expectation is that OpenStack is a framework, which is a word I've heard people use many times, then does an upgrade path have to exist? The OpenStack dashboard was essentially rewritten to upgrade to a new version of Django. Was there any expectation that Django should upgrade itself for us? Upgrading an application to use a different versions of Rails, another framework, often borders on impossible, particularly if the application happens have some feature with a dependency of a gem that hasn't been kept in sync with the upstream project. Is OpenStack more or less complicated than those frameworks? What responsibility should OpenStack core development have to consider existing deployments? Frameworks are expected be a foundation to build on. By definition, changing foundations is not easy. Clearly, OpenStack can be deployed and operated, but if OpenStack needs to be easier to deploy, operate and upgrade, and that is a responsibility of OpenStack itself, that can't be something that get's tacked on at the end. There is no 'ease of deployment' powder to sprinkle on at the end. Distributions and tooling can and do obscure the difficultly for the downstream user, but that also leads to a lot of potential fragmentation. And is that the right answer? Who can and should answer that? That OpenStack should be easy to deploy and upgrade is somewhat at odds with OpenStack supporting every possible combination of hypervisor, storage and networking option, let alone what the expectation should be with closed source customizations/integrations. Which brings up questions of compatibility. API compatibility is potentially misleading if the semantics and behaviors vary. I've heard several service provider discuss ideas about how they can be differentiated in the market, and many of those ideas lead differences in APIs to expose. Is that wrong? Maybe, maybe not, but it certainly makes a lot of work if your core business is dependent on maintaining integrations with service providers. Taken to an extreme these decisions complicate and call into question any future of federated OpenStack services. I'm not advocating any choice here. I just want to point out there are compromises that have to be made. There are goals and desires for OpenStack that are at odds with each other. Some of that is a function of the perspective of persona, but a lot is also from fundamental differences in understanding about where OpenStack is, where OpenStack needs to be, and how to get there. If there isn't a core guiding conscience about what we are trying to accomplish that gets applied across the board, then I worry that the future of OpenStack ends up with more fragments optimizing for their perspective and inevitable skirmishes when the perspectives collide. I see there are many conversations we aren't having, which leads to surfacing all the unaddressed issues when someone does try to involve the community in discussions. OpenStack can't be all things, but we get to decide what it will be. The question is will we do that explicitly and consciously, or indirectly and passively. There is no one person who can address this alone. I'm hoping this can start a conversation. Best Regards, Andrew ___ 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] instance evacuation from a failed node (rebuild for HA)
We have submitted a patch https://review.openstack.org/#/c/11086/ to address https://blueprints.launchpad.net/nova/+spec/rebuild-for-ha that simplifies recovery from a node failure by introducing an API that recreates an instance on *another* host (similar to the existing instance 'rebuild' operation). The exact semantics of this operations varies depending on the configuration of the instances and the underlying storage topology. For example, if it is a regular 'ephemeral' instance, invoking will respawn from the same image on another node while retaining the same identity and configuration (e.g. same ID, flavor, IP, attached volumes, etc). For instances running off shared storage (i.e. same instance file accessible on the target host), the VM will be re-created and point to the same instance file while retaining the identity and configuration. More details are available at http://wiki.openstack.org/Evacuate. If the instance is on shared storage, what does recreate mean? Delete the old instance and create a new instance, using the same disk image? Does that mean that the new instance will have a new nova/ec2 id? In the case where DNS is being used, this would delete the old DNS entry and create a new DNS entry. This is lossy. If shared storage is available, the only think that likely needs to happen is for the instance's host to be updated in the database, and a reboot issued for the instance. That would keep everything identical, and would likely be much faster. - Ryan ___ 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] Removing support for KVM Hypervisor ...
Hi Sandy It's not enough Let's make OpenStack to CloseStack! Nachi 2012/8/10 Sandy Walsh sandy.wa...@rackspace.com: haha ... oh no. It's joke. Long story. Not going to happen :) From: chaohua wang [chwang...@gmail.com] Sent: Friday, August 10, 2012 5:31 PM To: Sandy Walsh Subject: Re: [Openstack] Removing support for KVM Hypervisor ... Hi I posted my question to openstack@lists.launchpad.net but i can't see it, Could you tell me reason why? thank you, Chaohua On Fri, Aug 10, 2012 at 2:23 PM, Sandy Walsh sandy.wa...@rackspace.com wrote: Sorry George, couldn't resist. :) ___ 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 -- Nachi Ueno email:nati.u...@gmail.com twitter:http://twitter.com/nati ___ 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] Setting Expectations
So many questions, so hard to reply. Whats the best question to answer here ;) From: Andrew Clay Shafer a...@parvuscaptus.commailto:a...@parvuscaptus.com Date: Fri, 10 Aug 2012 14:41:03 -0700 To: openstack openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Setting Expectations What is OpenStack? Clearly, OpenStack is many things to many people and organizations. What does it mean to contribute to OpenStack? What does it mean to deploy OpenStack? What does it mean to operate OpenStack? What do we mean when we say compatible? interoperable? community? branded? Is OpenStack a framework? a project? a product? Recent discussions make it clear that we have a lot of different ideas about all of these things. Our collective and individual responsibilities to each other are also a point of tension. There is a marked difference in the perspective of those developing the projects, those operating the projects as services and the final consumers/clients of those services. If OpenStack is going to live up to it's full potential and stated mission, I believe there needs to be a much stronger collective conscience about how decisions are made. I feel we will all benefit by making some things more explicit. If the expectation is that OpenStack is a framework, which is a word I've heard people use many times, then does an upgrade path have to exist? The OpenStack dashboard was essentially rewritten to upgrade to a new version of Django. Was there any expectation that Django should upgrade itself for us? Upgrading an application to use a different versions of Rails, another framework, often borders on impossible, particularly if the application happens have some feature with a dependency of a gem that hasn't been kept in sync with the upstream project. Is OpenStack more or less complicated than those frameworks? What responsibility should OpenStack core development have to consider existing deployments? Frameworks are expected be a foundation to build on. By definition, changing foundations is not easy. Clearly, OpenStack can be deployed and operated, but if OpenStack needs to be easier to deploy, operate and upgrade, and that is a responsibility of OpenStack itself, that can't be something that get's tacked on at the end. There is no 'ease of deployment' powder to sprinkle on at the end. Distributions and tooling can and do obscure the difficultly for the downstream user, but that also leads to a lot of potential fragmentation. And is that the right answer? Who can and should answer that? That OpenStack should be easy to deploy and upgrade is somewhat at odds with OpenStack supporting every possible combination of hypervisor, storage and networking option, let alone what the expectation should be with closed source customizations/integrations. Which brings up questions of compatibility. API compatibility is potentially misleading if the semantics and behaviors vary. I've heard several service provider discuss ideas about how they can be differentiated in the market, and many of those ideas lead differences in APIs to expose. Is that wrong? Maybe, maybe not, but it certainly makes a lot of work if your core business is dependent on maintaining integrations with service providers. Taken to an extreme these decisions complicate and call into question any future of federated OpenStack services. I'm not advocating any choice here. I just want to point out there are compromises that have to be made. There are goals and desires for OpenStack that are at odds with each other. Some of that is a function of the perspective of persona, but a lot is also from fundamental differences in understanding about where OpenStack is, where OpenStack needs to be, and how to get there. If there isn't a core guiding conscience about what we are trying to accomplish that gets applied across the board, then I worry that the future of OpenStack ends up with more fragments optimizing for their perspective and inevitable skirmishes when the perspectives collide. I see there are many conversations we aren't having, which leads to surfacing all the unaddressed issues when someone does try to involve the community in discussions. OpenStack can't be all things, but we get to decide what it will be. The question is will we do that explicitly and consciously, or indirectly and passively. There is no one person who can address this alone. I'm hoping this can start a conversation. Best Regards, Andrew ___ 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] Removing support for KVM Hypervisor ...
You're just trying to give me a heart attack :) Sent from my iPhone On Aug 10, 2012, at 15:32, Sandy Walsh sandy.wa...@rackspace.com wrote: Sorry George, couldn't resist. :) ___ 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] Setting Expectations
I personally equate OpenStack to the Linux Kernel. It's the foundation and core components that, in OpenStack's case, make up an Infrastructure as as Service (IaaS) system, a cloud kernel. We should expect the core components and APIs to be stable with sane deprecation policies, but OpenStack shouldn't do everything for everyone. It should facilitate and provide the stable framework or foundation in which to build production quality, large scale (and small) public and private IaaS systems. In and of itself I believe OpenStack is not an IaaS distribution, ala Linux distributions (Debian, Fedora, RedHat, SuSe, Ubuntu) which take the Linux kernel and build all the user-space and complementary services that make up a manageable, secure, monitored system. However, that doesn't mean OpenStack ignores the user/operator/packager/distro side of things. Where we the developers and operators of OpenStack see areas to make configuration, management, development, documentation of OpenStack easier we strive to incorporate those things back into core. None of the above is meant as criticism, it's simply how I categorize OpenStack in the cloudy landscape. Nate On Aug 10, 2012 5:47 PM, Andrew Clay Shafer a...@parvuscaptus.com wrote: What is OpenStack? Clearly, OpenStack is many things to many people and organizations. What does it mean to contribute to OpenStack? What does it mean to deploy OpenStack? What does it mean to operate OpenStack? What do we mean when we say compatible? interoperable? community? branded? Is OpenStack a framework? a project? a product? Recent discussions make it clear that we have a lot of different ideas about all of these things. Our collective and individual responsibilities to each other are also a point of tension. There is a marked difference in the perspective of those developing the projects, those operating the projects as services and the final consumers/clients of those services. If OpenStack is going to live up to it's full potential and stated mission, I believe there needs to be a much stronger collective conscience about how decisions are made. I feel we will all benefit by making some things more explicit. If the expectation is that OpenStack is a framework, which is a word I've heard people use many times, then does an upgrade path have to exist? The OpenStack dashboard was essentially rewritten to upgrade to a new version of Django. Was there any expectation that Django should upgrade itself for us? Upgrading an application to use a different versions of Rails, another framework, often borders on impossible, particularly if the application happens have some feature with a dependency of a gem that hasn't been kept in sync with the upstream project. Is OpenStack more or less complicated than those frameworks? What responsibility should OpenStack core development have to consider existing deployments? Frameworks are expected be a foundation to build on. By definition, changing foundations is not easy. Clearly, OpenStack can be deployed and operated, but if OpenStack needs to be easier to deploy, operate and upgrade, and that is a responsibility of OpenStack itself, that can't be something that get's tacked on at the end. There is no 'ease of deployment' powder to sprinkle on at the end. Distributions and tooling can and do obscure the difficultly for the downstream user, but that also leads to a lot of potential fragmentation. And is that the right answer? Who can and should answer that? That OpenStack should be easy to deploy and upgrade is somewhat at odds with OpenStack supporting every possible combination of hypervisor, storage and networking option, let alone what the expectation should be with closed source customizations/integrations. Which brings up questions of compatibility. API compatibility is potentially misleading if the semantics and behaviors vary. I've heard several service provider discuss ideas about how they can be differentiated in the market, and many of those ideas lead differences in APIs to expose. Is that wrong? Maybe, maybe not, but it certainly makes a lot of work if your core business is dependent on maintaining integrations with service providers. Taken to an extreme these decisions complicate and call into question any future of federated OpenStack services. I'm not advocating any choice here. I just want to point out there are compromises that have to be made. There are goals and desires for OpenStack that are at odds with each other. Some of that is a function of the perspective of persona, but a lot is also from fundamental differences in understanding about where OpenStack is, where OpenStack needs to be, and how to get there. If there isn't a core guiding conscience about what we are trying to accomplish that gets applied across the board, then I worry that the future of OpenStack ends up with more fragments optimizing for their perspective and inevitable
[Openstack] Is it ok to post a job here?
Hello community, I'm wondering whether it's ok to post an OpenStack-related job to this mailing list. On one hand, I didn't find anything hinting that it's not ok in the MailingListEtiquette page; on the other hand, I didn't find any job postings in the archives either. So I figured I better ask first :) -- Eugene Kirpichov http://www.linkedin.com/in/eugenekirpichov ___ 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] Question on hostname generation?
Hi all, I was wondering about the following case (and am not sure if its been addressed in folsom). At yahoo, instead of the default hostname that seems to be automatically established (ie 'server-XYZ.novalocal' was in essex) we were wondering if there is anything in folsom that say lets us override that generation with either a module (or a subclass) or a new function without having to patch nova code. Sometimes we want a default hostname of a different format (as probably do others) and I just am not sure if quantum is directing this default hostname, or if nova still is, or if its some mix of both (the metadata + cloud-init can affect the hostname as well, so perhaps the configdrive work should be the only one establish a 'real' hostname?). I have found the following pieces of hostname related code but am not sure if this is all the places that make hostnames :-) * https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L109 Is this the only place nowadays?? Is there something in quantum also? Thx much, just trying to track this down. -Josh ___ 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] Setting Expectations
On Aug 10, 2012, at 20:49, Nathanael Burton nathanael.i.bur...@gmail.com wrote: I personally equate OpenStack to the Linux Kernel. It's the foundation and core components that, in OpenStack's case, make up an Infrastructure as as Service (IaaS) system, a cloud kernel. We should expect the core components and APIs to be stable with sane deprecation policies, but OpenStack shouldn't do everything for everyone. It should facilitate and provide the stable framework or foundation in which to build production quality, large scale (and small) public and private IaaS systems. In and of itself I believe OpenStack is not an IaaS distribution, ala Linux distributions (Debian, Fedora, RedHat, SuSe, Ubuntu) which take the Linux kernel and build all the user-space and complementary services that make up a manageable, secure, monitored system. An even better example might be Apache. They have their own foundation and have a number of services that get installed to machines, but they don't have a distribution or any clear deployment solutions. Some of their applications such as the httpd are just core pieces that get installed to a single system and multiple services on multiple machines don't communicate, but others are horizontally scaling solutions with inter-process communication, such as Hadoop. Whatever the case, they're still not building a distribution. OpenStack in some ways appears to be the kernel on which applications run, but its applications are just applications. If the question is where the foundation draws the line at acceptance of projects, it is an interesting one... as long as there is a foundation, you can't really use Linux as any sort of example. Instead, if you want to draw parallels to operating systems, you'll have to look more closely to the BSD systems. With BSD, they've coupled the kernels and the distributions. I do not think this is a model that OpenStack should follow, but I do see a tendency of some toward this. Instead, I believe the community and the foundation should move into the direction of Apache. If someone wants to create their own independent distribution, they should, but it shouldn't be part of the project or blessed by the foundation. Instead, they would follow the steps of Slackware, Debian, and Gentoo; not the steps taken by FreeBSD. The community already has a number of emerging proprietary and/or corporate-sponsored distributions, it would not do the community a favor for the foundation to create its own. Regards, Eric Windisch (sent from my iPad)___ 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] Is it ok to post a job here?
Hi Eugene: On Aug 10, 2012, at 9:25 PM, Eugene Kirpichov ekirpic...@gmail.com wrote: Hello community, I'm wondering whether it's ok to post an OpenStack-related job to this mailing list. On one hand, I didn't find anything hinting that it's not ok in the MailingListEtiquette page; on the other hand, I didn't find any job postings in the archives either. So I figured I better ask first :) The place to post OpenStack-related jobs is the OpenStack Job Board: http://www.openstack.org/community/jobs/ Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com ___ 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] Setting Expectations
Openstack is like linux kernel for cloud Anyone welcome to.create distro on it like ubuntu tolinux... and yea ubunti cloud to openstack On Aug 11, 2012 8:46 AM, Eric Windisch e...@cloudscaling.com wrote: On Aug 10, 2012, at 20:49, Nathanael Burton nathanael.i.bur...@gmail.com wrote: I personally equate OpenStack to the Linux Kernel. It's the foundation and core components that, in OpenStack's case, make up an Infrastructure as as Service (IaaS) system, a cloud kernel. We should expect the core components and APIs to be stable with sane deprecation policies, but OpenStack shouldn't do everything for everyone. It should facilitate and provide the stable framework or foundation in which to build production quality, large scale (and small) public and private IaaS systems. In and of itself I believe OpenStack is not an IaaS distribution, ala Linux distributions (Debian, Fedora, RedHat, SuSe, Ubuntu) which take the Linux kernel and build all the user-space and complementary services that make up a manageable, secure, monitored system. An even better example might be Apache. They have their own foundation and have a number of services that get installed to machines, but they don't have a distribution or any clear deployment solutions. Some of their applications such as the httpd are just core pieces that get installed to a single system and multiple services on multiple machines don't communicate, but others are horizontally scaling solutions with inter-process communication, such as Hadoop. Whatever the case, they're still not building a distribution. OpenStack in some ways appears to be the kernel on which applications run, but its applications are just applications. If the question is where the foundation draws the line at acceptance of projects, it is an interesting one... as long as there is a foundation, you can't really use Linux as any sort of example. Instead, if you want to draw parallels to operating systems, you'll have to look more closely to the BSD systems. With BSD, they've coupled the kernels and the distributions. I do not think this is a model that OpenStack should follow, but I do see a tendency of some toward this. Instead, I believe the community and the foundation should move into the direction of Apache. If someone wants to create their own independent distribution, they should, but it shouldn't be part of the project or blessed by the foundation. Instead, they would follow the steps of Slackware, Debian, and Gentoo; not the steps taken by FreeBSD. The community already has a number of emerging proprietary and/or corporate-sponsored distributions, it would not do the community a favor for the foundation to create its own. Regards, Eric Windisch (sent from my iPad) ___ 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] Setting Expectations
First, thanks to Andrew for starting this thread. I think it's an important discussion. Second, the problem with the analogies made so far is, IMHO, at the API level and what it does to the ecosystem. Let's take, for example, Apache HTTP Client stuff. 3.1 and 4.x are wildly different object models. But that's OK for the Apache model in a way that isn't for OpenStack. When I decided to move Dasein Cloud to the new stuff, it was on my time frame, not Apache's. With OpenStack, the deprecation of APIs is hugely problematic because the ecosystem is live dependent on the APIs. If I roll out a new version into a infrastructure with rich tool support and that version has API inconsistencies, I immediately and irrevocably break critical operational tools. With the Apache stuff, there's no external visibility into the HTTPclient APIs. It's just my code that I can compile and test pre-deployment. It's a problem for any tool with a public facing RESTful API. That's why I believe in never deprecating except in extreme circumstances. The most successful cloud API out there, the EC2 API, never breaks existing tools. NEVER. Seriously, never. -George On Aug 10, 2012, at 9:33 PM, Frans Thamura fr...@meruvian.org wrote: Openstack is like linux kernel for cloud Anyone welcome to.create distro on it like ubuntu tolinux... and yea ubunti cloud to openstack On Aug 11, 2012 8:46 AM, Eric Windisch e...@cloudscaling.com wrote: On Aug 10, 2012, at 20:49, Nathanael Burton nathanael.i.bur...@gmail.com wrote: I personally equate OpenStack to the Linux Kernel. It's the foundation and core components that, in OpenStack's case, make up an Infrastructure as as Service (IaaS) system, a cloud kernel. We should expect the core components and APIs to be stable with sane deprecation policies, but OpenStack shouldn't do everything for everyone. It should facilitate and provide the stable framework or foundation in which to build production quality, large scale (and small) public and private IaaS systems. In and of itself I believe OpenStack is not an IaaS distribution, ala Linux distributions (Debian, Fedora, RedHat, SuSe, Ubuntu) which take the Linux kernel and build all the user-space and complementary services that make up a manageable, secure, monitored system. An even better example might be Apache. They have their own foundation and have a number of services that get installed to machines, but they don't have a distribution or any clear deployment solutions. Some of their applications such as the httpd are just core pieces that get installed to a single system and multiple services on multiple machines don't communicate, but others are horizontally scaling solutions with inter-process communication, such as Hadoop. Whatever the case, they're still not building a distribution. OpenStack in some ways appears to be the kernel on which applications run, but its applications are just applications. If the question is where the foundation draws the line at acceptance of projects, it is an interesting one... as long as there is a foundation, you can't really use Linux as any sort of example. Instead, if you want to draw parallels to operating systems, you'll have to look more closely to the BSD systems. With BSD, they've coupled the kernels and the distributions. I do not think this is a model that OpenStack should follow, but I do see a tendency of some toward this. Instead, I believe the community and the foundation should move into the direction of Apache. If someone wants to create their own independent distribution, they should, but it shouldn't be part of the project or blessed by the foundation. Instead, they would follow the steps of Slackware, Debian, and Gentoo; not the steps taken by FreeBSD. The community already has a number of emerging proprietary and/or corporate-sponsored distributions, it would not do the community a favor for the foundation to create its own. Regards, Eric Windisch (sent from my iPad) ___ 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 -- 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
Re: [Openstack] Setting Expectations
On Friday, August 10, 2012 at 22:53 PM, George Reese wrote: First, thanks to Andrew for starting this thread. I think it's an important discussion. Second, the problem with the analogies made so far is, IMHO, at the API level and what it does to the ecosystem. Let's take, for example, Apache HTTP Client stuff. 3.1 and 4.x are wildly different object models. But that's OK for the Apache model in a way that isn't for OpenStack. Aren't you making the wrong comparison here? This might apply to the OS API client libraries, or euca2ools (which is NOT an OpenStack project), but this comparison does not apply to the OpenStack services or EC2 endpoint compatibility. Instead, the comparison of EC2 endpoint compatibility should be made to Apache's HTTP endpoint, their httpd. A better question is: Has the Apache httpd broken HTTP compatibility in any significant way? Besides, perhaps, from allowing you to configure it in a broken manner? In fact, this might be a good comparison, because Apache's httpd doesn't HAVE to be deployed in a standards-compliant way, although tools (i.e. browsers) and operators have figured out how to make this work, and to a large degree, people are able to successfully load webpages served by the Apache httpd. In a similar way, OpenStack Nova installations may vary greatly in their behavior. They don't HAVE to be deployed in a standards-complaint way (whatever that means); Yet, hopefully, people will be able to successfully launch instances served by OpenStack Nova with a common set of tools. I'm often advocating compatible clouds over advanced client API wrappers (such as Dasein), but the reality is that it needs to happen on both ends. The cloud server software needs to enable a compatible and standards-compliant service endpoint, enforced or not… and the client API libraries need to be flexible enough to handle a variety of services that might not be 100% identical. Just like the HTTP servers and client libraries that we have today. 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
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_essex_keystone_stable #14
Title: precise_essex_keystone_stable General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_keystone_stable/14/Project:precise_essex_keystone_stableDate of build:Fri, 10 Aug 2012 07:01:54 -0400Build duration:2 min 36 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesOpen 2012.1.3 developmentby markmceditsetup.pyConsole Output[...truncated 1486 lines...]hard linking tests/test_import_legacy.py -> keystone-2012.1.3/testshard linking tests/test_keystoneclient.py -> keystone-2012.1.3/testshard linking tests/test_keystoneclient_sql.py -> keystone-2012.1.3/testshard linking tests/test_middleware.py -> keystone-2012.1.3/testshard linking tests/test_migrate_nova_auth.py -> keystone-2012.1.3/testshard linking tests/test_overrides.conf -> keystone-2012.1.3/testshard linking tests/test_policy.py -> keystone-2012.1.3/testshard linking tests/test_s3_token_middleware.py -> keystone-2012.1.3/testshard linking tests/test_serializer.py -> keystone-2012.1.3/testshard linking tests/test_swift_auth_middleware.py -> keystone-2012.1.3/testshard linking tests/test_utils.py -> keystone-2012.1.3/testshard linking tests/test_versions.py -> keystone-2012.1.3/testshard linking tests/test_wsgi.py -> keystone-2012.1.3/testshard linking tools/convert_to_sqlite.sh -> keystone-2012.1.3/toolshard linking tools/install_venv.py -> keystone-2012.1.3/toolshard linking tools/pip-requires -> keystone-2012.1.3/toolshard linking tools/sample_data.sh -> keystone-2012.1.3/toolshard linking tools/test-requires -> keystone-2012.1.3/toolshard linking tools/with_venv.sh -> keystone-2012.1.3/toolscopying setup.cfg -> keystone-2012.1.3Writing keystone-2012.1.3/setup.cfgcreating distCreating tar archiveremoving 'keystone-2012.1.3' (and everything under it)ERROR:root:Error occurred during package creation/build: [Errno 2] No such file or directory: '/tmp/tmpDKSu2z/git/keystone/dist/keystone-2012.1.1.tar.gz'ERROR:root:[Errno 2] No such file or directory: '/tmp/tmpDKSu2z/git/keystone/dist/keystone-2012.1.1.tar.gz'INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/precise-essex-proposed /tmp/tmpDKSu2z/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpDKSu2z/keystone/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpDKSu2z/git/keystone/dist/keystone-2012.1.1.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 140, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpDKSu2z/git/keystone/dist/keystone-2012.1.1.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 Failure: precise_essex_nova_stable #36
Title: precise_essex_nova_stable General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_nova_stable/36/Project:precise_essex_nova_stableDate of build:Fri, 10 Aug 2012 07:01:55 -0400Build duration:3 min 55 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesBump version to 2012.1.3by markmceditnova/version.pyConsole Output[...truncated 2209 lines...]hard linking smoketests/random.kernel -> nova-2012.1.3/smoketestshard linking smoketests/run_tests.py -> nova-2012.1.3/smoketestshard linking smoketests/test_netadmin.py -> nova-2012.1.3/smoketestshard linking smoketests/test_sysadmin.py -> nova-2012.1.3/smoketestshard linking tools/clean-vlans -> nova-2012.1.3/toolshard linking tools/clean_file_locks.py -> nova-2012.1.3/toolshard linking tools/enable-pre-commit-hook.sh -> nova-2012.1.3/toolshard linking tools/hacking.py -> nova-2012.1.3/toolshard linking tools/install_venv.py -> nova-2012.1.3/toolshard linking tools/nova-debug -> nova-2012.1.3/toolshard linking tools/pip-requires -> nova-2012.1.3/toolshard linking tools/rfc.sh -> nova-2012.1.3/toolshard linking tools/test-requires -> nova-2012.1.3/toolshard linking tools/with_venv.sh -> nova-2012.1.3/toolshard linking tools/conf/create_conf.py -> nova-2012.1.3/tools/confhard linking tools/conf/generate_sample.sh -> nova-2012.1.3/tools/confhard linking tools/esx/guest_tool.py -> nova-2012.1.3/tools/esxhard linking tools/xenserver/vdi_chain_cleanup.py -> nova-2012.1.3/tools/xenserverhard linking tools/xenserver/vm_vdi_cleaner.py -> nova-2012.1.3/tools/xenservercopying setup.cfg -> nova-2012.1.3Writing nova-2012.1.3/setup.cfgcreating distCreating tar archiveremoving 'nova-2012.1.3' (and everything under it)ERROR:root:Error occurred during package creation/build: [Errno 2] No such file or directory: '/tmp/tmpLX26Dw/git/nova/dist/nova-2012.1.2.tar.gz'ERROR:root:[Errno 2] No such file or directory: '/tmp/tmpLX26Dw/git/nova/dist/nova-2012.1.2.tar.gz'INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-essex-proposed /tmp/tmpLX26Dw/novamk-build-deps -i -r -t apt-get -y /tmp/tmpLX26Dw/nova/debian/controlpython setup.py sdistTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpLX26Dw/git/nova/dist/nova-2012.1.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 140, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpLX26Dw/git/nova/dist/nova-2012.1.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 Failure: quantal_folsom_cinder_trunk #36
Title: quantal_folsom_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/36/Project:quantal_folsom_cinder_trunkDate of build:Fri, 10 Aug 2012 12:31:53 -0400Build duration:5 min 6 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUse setuptools-git.by mordrededitMANIFEST.inedittools/test-requireseditsetup.pyConsole Output[...truncated 2772 lines...]Build-Time: 47Distribution: quantal-folsomFail-Stage: buildInstall-Time: 73Job: cinder_2012.2+git201208101232~quantal-0ubuntu1.dscPackage: cinderPackage-Time: 147Source-Version: 2012.2+git201208101232~quantal-0ubuntu1Space: 10668Status: attemptedVersion: 2012.2+git201208101232~quantal-0ubuntu1Finished at 20120810-1236Build needed 00:02:27, 10668k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~quantal-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/quantal-folsom-proposed /tmp/tmpIR7E3U/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpIR7E3U/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208101232~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208101232~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208101232~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A cinder_2012.2+git201208101232~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~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 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~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 Failure: precise_folsom_cinder_trunk #35
Title: precise_folsom_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/35/Project:precise_folsom_cinder_trunkDate of build:Fri, 10 Aug 2012 12:31:56 -0400Build duration:5 min 13 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUse setuptools-git.by mordrededittools/test-requireseditMANIFEST.ineditsetup.pyConsole Output[...truncated 2630 lines...]Build-Time: 47Distribution: precise-folsomFail-Stage: buildInstall-Time: 66Job: cinder_2012.2+git201208101232~precise-0ubuntu1.dscPackage: cinderPackage-Time: 131Source-Version: 2012.2+git201208101232~precise-0ubuntu1Space: 10672Status: attemptedVersion: 2012.2+git201208101232~precise-0ubuntu1Finished at 20120810-1237Build needed 00:02:11, 10672k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/precise-folsom-proposed /tmp/tmp4AcjLA/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp4AcjLA/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208101232~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208101232~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208101232~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2+git201208101232~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~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 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101232~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_nova_trunk #363
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/363/Project:quantal_folsom_nova_trunkDate of build:Fri, 10 Aug 2012 15:10:19 -0400Build duration:5 min 39 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMoves security group functionality into extensionby vishvanandaeditnova/tests/api/openstack/compute/contrib/test_security_groups.pyeditnova/api/openstack/compute/contrib/security_groups.pyeditnova/api/openstack/compute/contrib/createserverext.pyeditnova/tests/api/openstack/compute/test_servers.pyeditnova/api/openstack/compute/contrib/volumes.pyeditnova/api/openstack/compute/contrib/disk_config.pyeditnova/tests/api/openstack/compute/contrib/test_createserverext.pyeditnova/api/openstack/compute/servers.pyeditnova/tests/api/openstack/compute/contrib/test_disk_config.pyCreate unique volumes_dir for testing.by dprinceeditnova/tests/test_volume.pyeditnova/tests/api/ec2/test_cloud.pyeditnova/tests/api/ec2/test_cinder_cloud.pymaint: compare singletons with is not ==by pbradyeditnova/compute/api.pyeditnova/volume/storwize_svc.pySend host not ComputeNode into uptime RPC call.by dprinceeditnova/api/openstack/compute/contrib/hypervisors.pyConsole Output[...truncated 5238 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484, line 10087.debcommit: commit failedERROR:root:Error occurred during package creation/build: Command '['debcommit']' returned non-zero exit status 7ERROR:root:Command '['debcommit']' returned non-zero exit status 7INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpMurlCR/novamk-build-deps -i -r -t apt-get -y /tmp/tmpMurlCR/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208101513~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208101513~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, 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 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #364
Title: quantal_folsom_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/364/Project:quantal_folsom_nova_trunkDate of build:Fri, 10 Aug 2012 16:01:55 -0400Build duration:8 min 56 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesMaking security group refresh more specificby dave.mcnallyeditnova/virt/libvirt/driver.pyeditnova/virt/baremetal/driver.pyeditnova/compute/api.pyeditnova/virt/firewall.pyeditnova/virt/xenapi/driver.pyeditnova/tests/compute/test_compute.pyeditnova/compute/manager.pyeditnova/virt/fake.pyeditnova/compute/rpcapi.pyeditnova/virt/xenapi/vmops.pyConsole Output[...truncated 5244 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484, line 10094.debcommit: commit failedERROR:root:Error occurred during package creation/build: Command '['debcommit']' returned non-zero exit status 7ERROR:root:Command '['debcommit']' returned non-zero exit status 7INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpUdzf2k/novamk-build-deps -i -r -t apt-get -y /tmp/tmpUdzf2k/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208101608~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208101608~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, 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 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_cinder_trunk #37
Title: quantal_folsom_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/37/Project:quantal_folsom_cinder_trunkDate of build:Fri, 10 Aug 2012 16:31:53 -0400Build duration:2 min 30 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUse openstack.common.notifier.by chmoueldeletecinder/notifier/__init__.pyeditcinder/openstack/common/jsonutils.pyeditcinder/openstack/common/setup.pyeditcinder/openstack/common/cfg.pyeditcinder/tests/test_exception.pyeditcinder/tests/scheduler/test_scheduler.pyeditopenstack-common.confeditcinder/openstack/common/exception.pyeditetc/cinder/cinder.conf.sampledeletecinder/notifier/list_notifier.pyeditcinder/openstack/common/rpc/common.pydeletecinder/notifier/no_op_notifier.pyeditcinder/flags.pyeditcinder/openstack/common/log.pyaddcinder/openstack/common/notifier/list_notifier.pyaddcinder/openstack/common/notifier/rabbit_notifier.pyaddcinder/openstack/common/notifier/no_op_notifier.pyeditcinder/exception.pydeletecinder/tests/test_notifier.pyeditcinder/openstack/common/rpc/impl_qpid.pydeletecinder/notifier/test_notifier.pyeditcinder/openstack/common/timeutils.pydeletecinder/notifier/capacity_notifier.pyeditcinder/openstack/common/rpc/proxy.pydeletecinder/tests/notifier/test_list_notifier.pydeletecinder/notifier/rabbit_notifier.pydeletecinder/notifier/api.pyaddcinder/openstack/common/notifier/test_notifier.pydeletecinder/tests/notifier/__init__.pyaddcinder/openstack/common/notifier/api.pyaddcinder/openstack/common/notifier/__init__.pyaddcinder/openstack/common/notifier/log_notifier.pyeditcinder/utils.pydeletecinder/notifier/log_notifier.pyConsole Output[...truncated 1806 lines...]Looking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmpZ0DPsMbzr: ERROR: An error (1) occurred running quilt: Applying patch 0001-Use-setuptools-git.patchpatching file MANIFEST.inHunk #1 FAILED at 1.1 out of 1 hunk FAILED -- rejects in file MANIFEST.inpatching file setup.pyHunk #1 FAILED at 31.1 out of 1 hunk FAILED -- rejects in file setup.pypatching file tools/test-requiresHunk #1 FAILED at 9.1 out of 1 hunk FAILED -- rejects in file tools/test-requiresPatch 0001-Use-setuptools-git.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-88501c6f-5966-43e3-bedb-a1c71eed74ae', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-88501c6f-5966-43e3-bedb-a1c71eed74ae', '-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/cinder/quantal-folsom-proposed /tmp/tmpZ0DPsM/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpZ0DPsM/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208101632~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208101632~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 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-88501c6f-5966-43e3-bedb-a1c71eed74ae', '-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 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-88501c6f-5966-43e3-bedb-a1c71eed74ae', '-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_cinder_trunk #36
Title: precise_folsom_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/36/Project:precise_folsom_cinder_trunkDate of build:Fri, 10 Aug 2012 16:37:49 -0400Build duration:4 min 5 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesUse openstack.common.notifier.by chmoueleditcinder/openstack/common/jsonutils.pydeletecinder/notifier/rabbit_notifier.pyeditcinder/openstack/common/setup.pyeditopenstack-common.confaddcinder/openstack/common/notifier/api.pyeditcinder/openstack/common/log.pyeditcinder/openstack/common/rpc/proxy.pyaddcinder/openstack/common/notifier/__init__.pyaddcinder/openstack/common/notifier/list_notifier.pyeditcinder/flags.pyeditcinder/openstack/common/rpc/impl_qpid.pydeletecinder/notifier/log_notifier.pyeditcinder/openstack/common/rpc/common.pyeditcinder/openstack/common/timeutils.pydeletecinder/notifier/no_op_notifier.pyeditcinder/tests/test_exception.pydeletecinder/notifier/test_notifier.pyaddcinder/openstack/common/notifier/log_notifier.pydeletecinder/notifier/capacity_notifier.pyaddcinder/openstack/common/notifier/test_notifier.pydeletecinder/tests/notifier/__init__.pyaddcinder/openstack/common/notifier/no_op_notifier.pyaddcinder/openstack/common/notifier/rabbit_notifier.pydeletecinder/tests/test_notifier.pydeletecinder/notifier/api.pydeletecinder/notifier/__init__.pyeditcinder/utils.pyeditcinder/tests/scheduler/test_scheduler.pydeletecinder/notifier/list_notifier.pyeditetc/cinder/cinder.conf.sampledeletecinder/tests/notifier/test_list_notifier.pyeditcinder/exception.pyeditcinder/openstack/common/cfg.pyeditcinder/openstack/common/exception.pyAdd iscsiadm path for qauntal.by chuck.shorteditetc/cinder/rootwrap.d/volume.filtersConsole Output[...truncated 2473 lines...]Build-Time: 47Distribution: precise-folsomFail-Stage: buildInstall-Time: 37Job: cinder_2012.2+git201208101638~precise-0ubuntu1.dscPackage: cinderPackage-Time: 99Source-Version: 2012.2+git201208101638~precise-0ubuntu1Space: 10648Status: attemptedVersion: 2012.2+git201208101638~precise-0ubuntu1Finished at 20120810-1641Build needed 00:01:39, 10648k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101638~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101638~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/precise-folsom-proposed /tmp/tmphUxl79/cindermk-build-deps -i -r -t apt-get -y /tmp/tmphUxl79/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208101638~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208101638~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208101638~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2+git201208101638~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208101638~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 140, in raise esubprocess.CalledProcessError: Command '['sbuild
[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_cinder_trunk #38
Title: quantal_folsom_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/38/Project:quantal_folsom_cinder_trunkDate of build:Fri, 10 Aug 2012 17:01:54 -0400Build duration:2 min 9 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesAdd iscsiadm path for qauntal.by chuck.shorteditetc/cinder/rootwrap.d/volume.filtersConsole Output[...truncated 1812 lines...]Looking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmp70v8xBbzr: ERROR: An error (1) occurred running quilt: Applying patch 0001-Use-setuptools-git.patchpatching file MANIFEST.inHunk #1 FAILED at 1.1 out of 1 hunk FAILED -- rejects in file MANIFEST.inpatching file setup.pyHunk #1 FAILED at 31.1 out of 1 hunk FAILED -- rejects in file setup.pypatching file tools/test-requiresHunk #1 FAILED at 9.1 out of 1 hunk FAILED -- rejects in file tools/test-requiresPatch 0001-Use-setuptools-git.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f04fa025-ae6d-4d88-84e5-3b411776673f', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f04fa025-ae6d-4d88-84e5-3b411776673f', '-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/cinder/quantal-folsom-proposed /tmp/tmp70v8xB/cindermk-build-deps -i -r -t apt-get -y /tmp/tmp70v8xB/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208101702~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208101702~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 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f04fa025-ae6d-4d88-84e5-3b411776673f', '-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 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f04fa025-ae6d-4d88-84e5-3b411776673f', '-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_python-glanceclient_trunk #63
Title: quantal_folsom_python-glanceclient_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-glanceclient_trunk/63/Project:quantal_folsom_python-glanceclient_trunkDate of build:Fri, 10 Aug 2012 18:01:53 -0400Build duration:1 min 45 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80Changessocket errors and timeouts should be CommunicationErrorsby cbehrenseditglanceclient/common/http.pyConsole Output[...truncated 1322 lines...]Distribution: quantal-folsomFail-Stage: apt-get-updateInstall-Time: 0Job: python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1.dscPackage: python-glanceclientPackage-Time: 0Source-Version: 0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1Space: 0Status: failedVersion: 0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1Finished at 20120810-1803Build needed 00:00:00, 0k disc spaceE: apt-get update failedERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1.dsc']' returned non-zero exit status 3ERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1.dsc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom-proposed /tmp/tmp7jEqbs/python-glanceclientmk-build-deps -i -r -t apt-get -y /tmp/tmp7jEqbs/python-glanceclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 3997f977fa0df34f72670e0e4a4e9e87d932b2af..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/python-glanceclient/quantal-folsom --forcedch -b -D quantal --newversion 1:0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1:0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1.dsc']' 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 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'python-glanceclient_0.3.0.12.a214d98+git201208101801~quantal-0ubuntu1.dsc']' 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
