[Openstack] Folsom-3 milestone proposed candidates

2012-08-16 Thread Thierry Carrez
Hi everyone,

Milestone-proposed branches were created for Keystone, Glance, Nova,
Horizon, Quantum and Cinder in preparation for the folsom-3 milestone
delivery on Friday.

Please test the candidate tarballs to ensure no critical regression
found its way in. Milestone-critical fixes will be backported to the
milestone-proposed branch until final delivery of the milestone, and
will be tracked using the folsom-3 milestone targeting.

You can find candidate tarballs at:
http://tarballs.openstack.org/nova/nova-milestone-proposed.tar.gz
http://tarballs.openstack.org/glance/glance-milestone-proposed.tar.gz
http://tarballs.openstack.org/keystone/keystone-milestone-proposed.tar.gz
http://tarballs.openstack.org/horizon/horizon-milestone-proposed.tar.gz
http://tarballs.openstack.org/quantum/quantum-milestone-proposed.tar.gz
http://tarballs.openstack.org/cinder/cinder-milestone-proposed.tar.gz

You can also access the milestone-proposed branches directly at:
https://github.com/openstack/nova/tree/milestone-proposed
https://github.com/openstack/glance/tree/milestone-proposed
https://github.com/openstack/keystone/tree/milestone-proposed
https://github.com/openstack/horizon/tree/milestone-proposed
https://github.com/openstack/quantum/tree/milestone-proposed
https://github.com/openstack/cinder/tree/milestone-proposed

The current plan is to deliver Folsom-3 Friday morning, US time.
Regards,

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [openstack-dev] Discussion about where to put database for bare-metal provisioning (review 10726)

2012-08-16 Thread Michael J Fork

vishvana...@gmail.com wrote on 08/15/2012 06:54:58 PM:

 From: Vishvananda Ishaya vishvana...@gmail.com
 To: OpenStack Development Mailing List
openstack-...@lists.openstack.org,
 Cc: openstack@lists.launchpad.net \(openstack@lists.launchpad.net
 \) openstack@lists.launchpad.net
 Date: 08/15/2012 06:58 PM
 Subject: Re: [Openstack] [openstack-dev] Discussion about where to
 put database for bare-metal provisioning (review 10726)
 Sent by: openstack-bounces+mjfork=us.ibm@lists.launchpad.net

 On Aug 15, 2012, at 3:17 PM, Michael J Fork mjf...@us.ibm.com wrote:

  I am interested in finding a solution that enables bare-metal and
  virtualized requests to be serviced through the same scheduler where
  the compute_nodes table has a full view of schedulable resources.
  This would seem to simplify the end-to-end flow while opening up
  some additional use cases (e.g. dynamic allocation of a node from
  bare-metal to hypervisor and back).
 
  One approach would be to have a proxy running a single nova-compute
  daemon fronting the bare-metal nodes .  That nova-compute daemon
  would report up many HostState objects (1 per bare-metal node) to
  become entries in the compute_nodes table and accessible through the
  scheduler HostManager object.
  The HostState object would set cpu_info, vcpus, member_mb and
  local_gb values to be used for scheduling with the hypervisor_host
  field holding the bare-metal machine address (e.g. for IPMI based
  commands) and hypervisor_type = NONE.  The bare-metal Flavors are
  created with an extra_spec of hypervisor_type= NONE and the
  corresponding compute_capabilities_filter would reduce the available
  hosts to those bare_metal nodes.  The scheduler would need to
  understand that hypervisor_type = NONE means you need an exact fit
  (or best-fit) host vs weighting them (perhaps through the multi-
  scheduler).  The scheduler would cast out the message to the
  topic.service-hostname (code today uses the HostState hostname),
  with the compute driver having to understand if it must be serviced
  elsewhere (but does not break any existing implementations since it
  is 1 to 1).
 
  Does this solution seem workable? Anything I missed?
  The bare metal driver already is proxying for the other nodes so it
 sounds like we need a couple of things to make this happen:

 a) modify driver.get_host_stats to be able to return a list of host
 stats instead of just one. Report the whole list back to the
 scheduler. We could modify the receiving end to accept a list as
 well or just make multiple calls to
 self.update_service_capabilities(capabilities)

 b) make a few minor changes to the scheduler to make sure filtering
 still works. Note the changes here may be very helpful:

 https://review.openstack.org/10327

 c) we have to make sure that instances launched on those nodes take
 up the entire host state somehow. We could probably do this by
 making sure that the instance_type ram, mb, gb etc. matches what the
 node has, but we may want a new boolean field used if those aren't
 sufficient.

My initial thought is that showing the actual resources the guest requested
as being consumed in HostState would enable use cases like migrating a
guest running on a too-big machine to a right-size one.  However, that
would required the bare-metal node to store the state of the requested
guest when that information could be obtained from the instance_type.

For now, the simplest is probably to have the bare-metal virt driver set
the disk_available = 0 and host_memory_free = 0 so the scheduler removes
them from consideration, with the vcpus, disk_total, host_memory_total set
to the physical machine values.  If the requested guest size is easily
accessible, the _used values could be set to those values (although not
clear if anything would break though with _total != _free + _used, in which
case setting _used = _total would seem to be acceptable for now).

Another options is to add num_instances to HostState and have the
bare-metal filter remove hypervisor_type = NONE with num_instances  0.
The scheduler would never see them and then would be no need to show them
fully consumed.  Drawback is that the num_instances call is marked as being
expensive and would incur some overhead.

 I This approach seems pretty good. We could potentially get rid of
 the shared bare_metal_node table. I guess the only other concern is
 how you populate the capabilities that the bare metal nodes are
 reporting. I guess an api extension that rpcs to a baremetal node to
 add the node. Maybe someday this could be autogenerated by the bare
 metal host looking in its arp table for dhcp requests! :)

 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

Michael

-
Michael Fork
Cloud 

Re: [Openstack] What is the most commonly used Hypervisor and toolset combination?

2012-08-16 Thread Boris-Michel Deschenes
That would be great Jim,

I've built a cloud that uses CentOS+libvirt+Xen 4.1.3 to do GPU passthrough and 
I just love to be able to use libvirt with Xen, this setup makes a lot of sense 
to me since our main, bigger cloud is the standard libvirt+KVM, using libvirt 
across the board is great for us.

I'm following your work closely, the GPU cloud is still using libvirt+xend but 
when I move to Xen 4.2 my understanding is that I will need libvirt+xl 
(xenlight) so I guess there's still some work to be done in libvirt there...

The reason I want to move to Xen 4.2 is the GPU passthrough of NVIDIA GPUs... 
currently, with Xen 4.1.3, I successfully passthrough ATI GPUs only.

Boris

-Message d'origine-
De : openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net 
[mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net]
 De la part de Jim Fehlig
Envoyé : 18 juillet 2012 17:56
À : John Garbutt
Cc : openstack@lists.launchpad.net
Objet : Re: [Openstack] What is the most commonly used Hypervisor and toolset 
combination?

John Garbutt wrote:
 To my knowledge, if you want to use Xen, using XCP or XenServer (i.e. using 
 XenAPI driver) is the way to go. If you look at the contributions to the 
 drivers, you can have a good guess at who is using them.

 I know people are going into production on XenAPI, not heard about 
 Xen+libvirt in production. Having said this, I have seen some fixes to Folsom 
 around Xen + libvirt, I think from SUSE?
   

Yes, I'm slowly working on improving support for xen.org Xen via the libvirt 
driver and hope to have these improvements in for the Folsom release.

Regards,
Jim


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [ceilometer] Metering meeting agenda for Thursday at 16:00 UTC (Aug 16th, 2012)

2012-08-16 Thread Nick Barcet
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
   - nijaba to write description of componet responsibility
   - nijaba to do a second thouroughness check on API and report next week

 * Open discussion

If you are not able to attend or have additional topic you would like to
cover, please update the agenda on the wiki.

Cheers,
--
Nick Barcet nick.bar...@canonical.com
aka: nijaba, nicolas









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


[Openstack] Snapshotting ephemeral disks?

2012-08-16 Thread Lars Kellogg-Stedman
I have a system that I've booted using a live CD image (so
.../instance-ID/disk points at the ISO file).  I've installed an OS
onto /dev/vda (which is .../instance-ID/disk.local).

Running 'nova image-create INSTANCE NAME` results in a traceback in
the compute log:

  2012-08-16 09:48:56 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected 
error while running command.
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Command: qemu-img convert -f qcow2 -O 
iso -s 6966cceec946407eb12531ddbe7bb7ac 
/virt/pools/openstack_2/instance-004c/disk 
/tmp/tmpMJ9GuL/6966cceec946407eb12531ddbe7bb7ac
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Exit code: 1
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Stdout: ''
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Stderr: qemu-img: Unknown file 
format 'iso'\n
  2012-08-16 09:48:56 TRACE nova.rpc.amqp 

And the image gets stuck in the SAVING state:

# nova image-list
...
| f269eebc-d86e-4cd0-aacc-8b0c53fb3bb2 | cloud-f17-x86_64  | 
SAVING | 4b3fccf9-28ab-4c29-acdb-cc5c18c862af |

Is there a way to do this properly?  Obviously I can just munge around
in the filesystem to do what I want, but I was hoping for something
more convenient.

I guess another option would be...

- Boot from the live CD
- Create a new volume
- Attach the volume
- Install onto the volume

Is it possible to snapshot an ephemeral disk?

-- 
Lars Kellogg-Stedman l...@seas.harvard.edu   |
Senior Technologist| http://ac.seas.harvard.edu/
Academic Computing | 
http://code.seas.harvard.edu/
Harvard School of Engineering and Applied Sciences |


___
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] What is the most commonly used Hypervisor and toolset combination?

2012-08-16 Thread John Paul Walters
Hi Boris,

We have GPU passthrough working with NVIDIA GPUs in Xen 4.1.2, if I recall 
correctly.  We don't yet have a stable Xen + Libvirt installation working, but 
we're looking at it.  Perhaps it would be worth collaborating since it sounds 
like this could be a win for both of us.

best,
JP


On Aug 16, 2012, at 9:31 AM, Boris-Michel Deschenes wrote:

 That would be great Jim,
 
 I've built a cloud that uses CentOS+libvirt+Xen 4.1.3 to do GPU passthrough 
 and I just love to be able to use libvirt with Xen, this setup makes a lot of 
 sense to me since our main, bigger cloud is the standard libvirt+KVM, using 
 libvirt across the board is great for us.
 
 I'm following your work closely, the GPU cloud is still using libvirt+xend 
 but when I move to Xen 4.2 my understanding is that I will need libvirt+xl 
 (xenlight) so I guess there's still some work to be done in libvirt there...
 
 The reason I want to move to Xen 4.2 is the GPU passthrough of NVIDIA GPUs... 
 currently, with Xen 4.1.3, I successfully passthrough ATI GPUs only.
 
 Boris
 
 -Message d'origine-
 De : openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net 
 [mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.launchpad.net]
  De la part de Jim Fehlig
 Envoyé : 18 juillet 2012 17:56
 À : John Garbutt
 Cc : openstack@lists.launchpad.net
 Objet : Re: [Openstack] What is the most commonly used Hypervisor and toolset 
 combination?
 
 John Garbutt wrote:
 To my knowledge, if you want to use Xen, using XCP or XenServer (i.e. using 
 XenAPI driver) is the way to go. If you look at the contributions to the 
 drivers, you can have a good guess at who is using them.
 
 I know people are going into production on XenAPI, not heard about 
 Xen+libvirt in production. Having said this, I have seen some fixes to 
 Folsom around Xen + libvirt, I think from SUSE?
 
 
 Yes, I'm slowly working on improving support for xen.org Xen via the libvirt 
 driver and hope to have these improvements in for the Folsom release.
 
 Regards,
 Jim
 
 
 ___
 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] Devstack multinode Installation network configuration help and bridging explanation

2012-08-16 Thread Kurt Scholtens
Very good explanation.  Thank you Vish.

A final question, if the guest vnics (fixed_addresses) get created on the
bridge of the flat_interface, how do I specify multinic instance
configurations for devstack essex?

Cheers,
~kvs

From:  Vishvananda Ishaya vishvana...@gmail.com
Date:  Wednesday, August 15, 2012 12:13 PM
To:  Kurt Scholtens burnbrigh...@hotmail.com
Cc:  openstack@lists.launchpad.net
Subject:  Re: [Openstack] Devstack multinode Installation network
configuration help and bridging explanation


On Aug 14, 2012, at 10:52 PM, Kurt Scholtens burnbrigh...@hotmail.com
wrote:

 Vish - 
 
 Thank you for responding.  So, when using multiple interfaces, will setting
 the PUBLIC_INTERFACE to the separate interface w/o VLANing work?  Is that what
 you are saying below?  Are any additional configuration parameters then
 required such as flat_network _bridge?

It should work on two separate interfaces with just that change.

 
 Something still puzzling me:
 1. From my routing table below, it appears both the public interface AND the
 flat interface are on br100 (which is bound to eth2).  I didn't think a bridge
 could have more than one subnet attached to it at any one time. I was
 apparently wrong.
multiple unrelated ips on an interface is fine
 1. My br100 has an associated address of 11.0.4.12, but eth2 has the IP
 address of 192.168.12.105br100 then, has the public_interface traffic
 (floating_range - 192.168.12.x) and the fixed_address traffic traversing eth2,
 correct? Is my understanding of what is going on correct?

if the interface specified in flat_interface has an ip on it, it moves it to
the bridge. So you will often have multiple ips on the bridge: 1) the hosts
original ip 2) an ip in the fixed_range for dnsmasq 3) all floating ips
(assuming public_interface=br100) In addition, all guest vnics are on the
same bridge.

public_interface just controls which interface is used for the floating ips.
If you want them to be usable from outside the host, you have to make sure
that is an interface (ir a bridge on an interface) that your router knows
about.

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] What is the most commonly used Hypervisor and toolset combination?

2012-08-16 Thread John Garbutt
For the record, we (i.e. Citrix) are certainly looking at exposing the GPU 
pass-through support in XCP (a Xen.org project that includes XenAPI) and 
XenServer in the Grizzly timeframe.

I now sit next to a lot of the Citrix Xen.org and XenServer people. We are all 
based in Cambridge, UK. However, you will probably get answers just as quickly 
by asking on the Xen mailing lists.

Thanks,
John

 -Original Message-
 From: John Paul Walters [mailto:jwalt...@isi.edu]
 Sent: Thursday, August 16, 2012 4:11 PM
 To: Boris-Michel Deschenes
 Cc: Jim Fehlig; John Garbutt; openstack@lists.launchpad.net
 Subject: Re: [Openstack] What is the most commonly used Hypervisor and
 toolset combination?
 
 Hi Boris,
 
 We have GPU passthrough working with NVIDIA GPUs in Xen 4.1.2, if I recall
 correctly.  We don't yet have a stable Xen + Libvirt installation working, but
 we're looking at it.  Perhaps it would be worth collaborating since it sounds 
 like
 this could be a win for both of us.
 
 best,
 JP
 
 
 On Aug 16, 2012, at 9:31 AM, Boris-Michel Deschenes wrote:
 
  That would be great Jim,
 
  I've built a cloud that uses CentOS+libvirt+Xen 4.1.3 to do GPU passthrough
 and I just love to be able to use libvirt with Xen, this setup makes a lot of 
 sense
 to me since our main, bigger cloud is the standard libvirt+KVM, using libvirt
 across the board is great for us.
 
  I'm following your work closely, the GPU cloud is still using libvirt+xend 
  but
 when I move to Xen 4.2 my understanding is that I will need libvirt+xl 
 (xenlight)
 so I guess there's still some work to be done in libvirt there...
 
  The reason I want to move to Xen 4.2 is the GPU passthrough of NVIDIA
 GPUs... currently, with Xen 4.1.3, I successfully passthrough ATI GPUs only.
 
  Boris
 
  -Message d'origine-
  De :
  openstack-bounces+boris-michel.deschenes=ubisoft.com@lists.launchpad.n
  et
  [mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.lau
  nchpad.net] De la part de Jim Fehlig Envoyé : 18 juillet 2012 17:56 À : John
 Garbutt Cc : openstack@lists.launchpad.net Objet : Re: [Openstack] What is the
 most commonly used Hypervisor and toolset combination?
 
  John Garbutt wrote:
  To my knowledge, if you want to use Xen, using XCP or XenServer (i.e. using
 XenAPI driver) is the way to go. If you look at the contributions to the 
 drivers,
 you can have a good guess at who is using them.
 
  I know people are going into production on XenAPI, not heard about
 Xen+libvirt in production. Having said this, I have seen some fixes to Folsom
 around Xen + libvirt, I think from SUSE?
 
 
  Yes, I'm slowly working on improving support for xen.org Xen via the libvirt
 driver and hope to have these improvements in for the Folsom release.
 
  Regards,
  Jim
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] Horizon: controlling table appearance

2012-08-16 Thread LifeOn2 Development
Hello All,

I am currently looking into how the appearance of tables in the
Horizon UI is controlled, more specifically the Instances table in
Project-Instances  Volumes. What I am trying to accomplish is to
control for which content combinations of the Status and Task
cells a certain row is rendered with the pale yellow background and
the spinner animation in the Task cell or not.

Reasonably information about row state (including when to show the
spinner and yellow or not) is passed in the Ajax data for the row sent
from nova. I have looked into the contents of the Ajax data sent, but
have not been able to distinguish any data that would seem to control
this row appearance.

So, if anybody could point me to the mechanism that regulates this
aspect of row appearance, it would be super!

Many Thanks,
Fredric

___
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 16th, 2012)

2012-08-16 Thread Nick Barcet
On 08/16/2012 03: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
- nijaba to write description of componet responsibility
- nijaba to do a second thouroughness check on API and report next week
 
  * 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 are the minutes:

==
#openstack-meeting: Ceilometer
==


Meeting started by nijaba at 16:00:25 UTC.  The full logs are available
at
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-16-16.00.log.html
.



Meeting summary
---

* LINK: http://wiki.openstack.org/Meetings/MeteringAgenda  (nijaba,
  16:00:25)
* actions from previous meeting  (nijaba, 16:01:43)

* jaypipes to create ceilometer cookbook  (nijaba, 16:01:58)
  * ACTION: jaypipes to create ceilometer cookbook  (nijaba, 16:02:38)

* nijaba to do a second thouroughness check on API and report next week
  (nijaba, 16:02:57)

* nijaba to write description of component responsibility  (nijaba,
  16:11:33)
  * ACTION: nijaba to write description of component responsibility
(nijaba, 16:11:43)

* Open Discusssion  (nijaba, 16:12:19)
  * ACTION: dhellmann and nijaba to work on sessions for summit via
email  (nijaba, 16:19:23)
  * ACTION: nijaba to give core reviewer rights to gmb  (nijaba,
16:21:55)
  * ACTION: dhellmann to ask jtrans about interest in reviewer status
(dhellmann, 16:23:28)



Meeting ended at 16:27:23 UTC.



Action items, by person
---

* dhellmann
  * dhellmann and nijaba to work on sessions for summit via email
  * dhellmann to ask jtrans about interest in reviewer status
* gmb
  * nijaba to give core reviewer rights to gmb
* nijaba
  * nijaba to write description of component responsibility
  * dhellmann and nijaba to work on sessions for summit via email
  * nijaba to give core reviewer rights to gmb
* jaypipes
  * jaypipes to create ceilometer cookbook



People present (lines said)
---

* nijaba (77)
* dhellmann (47)
* gmb (5)
* openstack (3)
* jgriffith (2)
* zul (2)



Generated by `MeetBot`_ 0.1.4



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] [heat] Heat 8-13-2012 Planning and Status Meeting

2012-08-16 Thread Steven Dake
=
#heat Meeting
=


Meeting started by asalkeld at 21:14:37 UTC. The full logs are available
at heat/2012/heat.2012-08-13-21.14.log.html .

The full logs are available at:
http://heat-api.org/heat-irc-meetings/heat.2012-08-13-21.14.log.html

All IRC meeting logs are available at:
http://heat-api.org/irclogs.html

Meeting summary
---
* rollcall  (sdake, 21:17:23)
  * zaneb, sdake, imain, asalkeld, shardy, funzo, jpeeler present
(sdake, 21:18:30)
  * shadower present too  (sdake, 21:19:07)

* v6 additional features  (sdake, 21:19:14)
  * shardy wrapped up openshift  (sdake, 21:23:54)
  * ACTION: shardy working on initial cloudwatch improvements - to
potentially merge into ceilometer later without much wasted effort
(sdake, 21:25:38)
  * ACTION: zaneb help wrap up integration testing and start cracking on
openstack orchestration rest api code  (sdake, 21:26:11)
  * additional features from returning from pto devs - openstack rest
orchestraition API and improved CloudWatch implementation  (sdake,
21:28:10)
  * ACTION: slower to investigate s3 integration support with swift
(sdake, 21:29:04)
  * 9/4 release target for v6  (sdake, 21:33:50)
  * zaneb to work on rest api for v6, sdake start sorting out quantum
integration plans in v6, then v7 shardy,sdake,zaneb work on quantum
vpc  (sdake, 21:45:33)

* open items  (sdake, 21:45:53)
  * ACTION: sdake to find out how tempest expects test cases  (sdake,
21:52:35)
  * LINK: https://github.com/openstack/tempest/   (asalkeld, 21:53:04)
  * unanimous vote to add tempest integration as roadmap item for future
versions  (sdake, 21:55:35)
  * as user base increases, add troubleshooting tips to troubleshooting
wiki based upon user feedback  (sdake, 21:58:49)

Meeting ended at 22:06:14 UTC.

Action Items

* shardy working on initial cloudwatch improvements - to potentially
  merge into ceilometer later without much wasted effort
* zaneb help wrap up integration testing and start cracking on openstack
  orchestration rest api code
* slower to investigate s3 integration support with swift
* sdake to find out how tempest expects test cases


Action Items, by person
---
* sdake
  * sdake to find out how tempest expects test cases
* shardy
  * shardy working on initial cloudwatch improvements - to potentially
merge into ceilometer later without much wasted effort
* zaneb
  * zaneb help wrap up integration testing and start cracking on
openstack orchestration rest api code
* **UNASSIGNED**
  * slower to investigate s3 integration support with swift


People Present (lines said)
---
* sdake (134)
* asalkeld (32)
* zaneb (26)
* shardy (24)
* Slower (12)
* jpeeler (7)
* mheat-bot (5)
* shadower (5)
* russellb (2)
* funzo (1)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot

___
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

2012-08-16 Thread jrd
From: j...@redhat.com
Date: Tue, 14 Aug 2012 20:23:52 -0400

From: Dan Wendlandt d...@nicira.com
Date: Tue, 14 Aug 2012 15:22:31 -0700


jrd, my feeling is that we'd need a patch for this under review this 
 week to understand the
magnitude of the changes if we want to consider if for a 
 feature-freeze exception.  Thanks. 

Got it.  



Update:  Dan and ttx, Gary has uploaded a patch set addressing the fix
of quantum-rootwrap for me, until I finish getting my credentials
sorted out so that I can push them myself.

See https://review.openstack.org/11472

There's a couple of review comments, which I will address.  What's
your inclination?  Have we come close enough to the deadline to
justify getting this in for f-3, or should we hold off and treat it
as a bug later?

___
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] Running multiple Glance instances?

2012-08-16 Thread Lars Kellogg-Stedman
Assuming some sort of shared filesystem, can I run multiple glance
indexes in order to distribute the i/o load across multiple systems?
Do I need to run both the registry and API service in each location?

We're running with an NFS-backed data store, and it seems that we
could eliminate some network i/o if we were to have each compute note
run the glance service locally (but all managing the same directory).

Does this make any sense?

-- 
Lars Kellogg-Stedman l...@seas.harvard.edu   |
Senior Technologist| http://ac.seas.harvard.edu/
Academic Computing | 
http://code.seas.harvard.edu/
Harvard School of Engineering and Applied Sciences |


___
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

2012-08-16 Thread Thierry Carrez
j...@redhat.com wrote:
 Update:  Dan and ttx, Gary has uploaded a patch set addressing the fix
 of quantum-rootwrap for me, until I finish getting my credentials
 sorted out so that I can push them myself.
 
 See https://review.openstack.org/11472
 
 There's a couple of review comments, which I will address.  What's
 your inclination?  Have we come close enough to the deadline to
 justify getting this in for f-3, or should we hold off and treat it
 as a bug later?

F3 branch was cut, so it's too late for that... But if you're close then
we should consider it a bug and fix it before RC1.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack] LBaaS IRC meeting notes

2012-08-16 Thread Eugene Kirpichov
Hi,

This time again Oleg Gelbukh and me were the sole participants, so let
me just repeat the news on our side here:

* Work is in progress on the F5 driver.
* A new scheduler (device allocator) similar to Nova's FilterScheduler
is ready for master (though not pushed to the public repo at the
moment)
* We had some communication with LB vendors and with Dan from Quantum
about LBaaS/Quantum integration, and identified some key questions.
Dan already sent a link to a wiki page about that (though there's not
much there now).
* There are going to be several design sessions on LBaaS and Quantum
integration at the Summit.
* We're going to provide the first Quantum integration proposal next
week on the ML, to start the discussion before the summit.

-- 
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


Re: [Openstack] Running multiple Glance instances?

2012-08-16 Thread Oleg Gelbukh
Lars,

I think it's possible if you set glance_api_servers option in nova.conf on
each compute node to something like:

glance_api_servers = localhost:9292

You don't have to run glance-registry service in every compute node. Just
make sure that glance-registry host configured properly in glance-api.conf
files on all compute nodes.

--
Best regards,
Oleg Gelbukh
Mirantis Inc

On Thu, Aug 16, 2012 at 10:42 PM, Lars Kellogg-Stedman 
l...@seas.harvard.edu wrote:

 Assuming some sort of shared filesystem, can I run multiple glance
 indexes in order to distribute the i/o load across multiple systems?
 Do I need to run both the registry and API service in each location?

 We're running with an NFS-backed data store, and it seems that we
 could eliminate some network i/o if we were to have each compute note
 run the glance service locally (but all managing the same directory).

 Does this make any sense?

 --
 Lars Kellogg-Stedman l...@seas.harvard.edu   |
 Senior Technologist|
 http://ac.seas.harvard.edu/
 Academic Computing |
 http://code.seas.harvard.edu/
 Harvard School of Engineering and Applied Sciences |


 ___
 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] LBaaS IRC meeting notes

2012-08-16 Thread Atul Jha
Hi,

Snip
Hi,

This time again Oleg Gelbukh and me were the sole participants, so let
me just repeat the news on our side here:

* Work is in progress on the F5 driver.
* A new scheduler (device allocator) similar to Nova's FilterScheduler
is ready for master (though not pushed to the public repo at the
moment)
* We had some communication with LB vendors and with Dan from Quantum
about LBaaS/Quantum integration, and identified some key questions.
Dan already sent a link to a wiki page about that (though there's not
much there now).
* There are going to be several design sessions on LBaaS and Quantum
integration at the Summit.
* We're going to provide the first Quantum integration proposal next
week on the ML, to start the discussion before the summit.
/snip

Is there a blueprint or project page LBaaS  where i can see ongoing development 
of the project.

Thanks,

Atul Jha
http://www.csscorp.com/common/email-disclaimer.php

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] LBaaS IRC meeting notes

2012-08-16 Thread Eugene Kirpichov
Hi,

Not yet. But I think we'll create one now that you've mentioned it :)

On Thu, Aug 16, 2012 at 3:11 PM, Atul Jha atul@csscorp.com wrote:
 Hi,

 Snip
 Hi,

 This time again Oleg Gelbukh and me were the sole participants, so let
 me just repeat the news on our side here:

 * Work is in progress on the F5 driver.
 * A new scheduler (device allocator) similar to Nova's FilterScheduler
 is ready for master (though not pushed to the public repo at the
 moment)
 * We had some communication with LB vendors and with Dan from Quantum
 about LBaaS/Quantum integration, and identified some key questions.
 Dan already sent a link to a wiki page about that (though there's not
 much there now).
 * There are going to be several design sessions on LBaaS and Quantum
 integration at the Summit.
 * We're going to provide the first Quantum integration proposal next
 week on the ML, to start the discussion before the summit.
 /snip

 Is there a blueprint or project page LBaaS  where i can see ongoing 
 development of the project.

 Thanks,

 Atul Jha
 http://www.csscorp.com/common/email-disclaimer.php



-- 
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


Re: [Openstack] LBaaS IRC meeting notes

2012-08-16 Thread Eugene Kirpichov
Created blueprint in Quantum:
https://blueprints.launchpad.net/quantum/+spec/lbaas

On Thu, Aug 16, 2012 at 3:30 PM, Eugene Kirpichov ekirpic...@gmail.com wrote:
 Hi,

 Not yet. But I think we'll create one now that you've mentioned it :)

 On Thu, Aug 16, 2012 at 3:11 PM, Atul Jha atul@csscorp.com wrote:
 Hi,

 Snip
 Hi,

 This time again Oleg Gelbukh and me were the sole participants, so let
 me just repeat the news on our side here:

 * Work is in progress on the F5 driver.
 * A new scheduler (device allocator) similar to Nova's FilterScheduler
 is ready for master (though not pushed to the public repo at the
 moment)
 * We had some communication with LB vendors and with Dan from Quantum
 about LBaaS/Quantum integration, and identified some key questions.
 Dan already sent a link to a wiki page about that (though there's not
 much there now).
 * There are going to be several design sessions on LBaaS and Quantum
 integration at the Summit.
 * We're going to provide the first Quantum integration proposal next
 week on the ML, to start the discussion before the summit.
 /snip

 Is there a blueprint or project page LBaaS  where i can see ongoing 
 development of the project.

 Thanks,

 Atul Jha
 http://www.csscorp.com/common/email-disclaimer.php



 --
 Eugene Kirpichov
 http://www.linkedin.com/in/eugenekirpichov



-- 
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


Re: [Openstack] LBaaS IRC meeting notes

2012-08-16 Thread Atul Jha

snip
Created blueprint in Quantum:
https://blueprints.launchpad.net/quantum/+spec/lbaas
/snip

Makes the project more visible IMHO. :)


Cheers!!


Atul Jha

http://www.csscorp.com/common/email-disclaimer.php

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Gold Member Election Update

2012-08-16 Thread Jonathan Bryce
Hi everyone,

The Gold Members completed their election today. DLA Piper administered the 
election and has passed along the results. The eight elected companies and the 
individuals they intend to appoint to the board are listed alphabetically below:

Cisco - Lew Tucker
Cloudscaling - Randy Bias
Dell - John Igoe
Dreamhost - Simon Anderson
ITRI/CCAT - Dr. Tzi-cker Chiueh
Mirantis - Boris Renski
Piston - Joshua McKenty
Yahoo! - Sean Roberts

Thanks,

Jonathan


On Aug 8, 2012, at 5:22 AM, john_i...@dell.com john_i...@dell.com wrote:

 Recently the gold member formation committee met to discuss the election of 
 directors for the gold members and agreed on the mechanics and timing of our 
 election. We will be holding our election using cumulative voting the week 
 before the individual member elections. There was some earlier discussion on 
 the list about the ordering of director selection, and this will make it 
 clear who will be the gold directors by the end of the week before the 
 individual member elections open.
 
 Because we have a small number of members, the election will be administered 
 by the Foundation's legal counsel at DLA Piper. There are a total of 11 gold 
 members at this point in time and 8 board members will be elected. They will 
 tally our votes and publish the results. We expect to complete the voting on 
 a single day during the week of August 13th, although the exact date has not 
 yet been set.
 
 Please let us know if you have any questions regarding this effort.
 
 Openstack Foundation Gold Member Formation Committee:
 
 Randy Bias
 Joshua McKenty
 Adam Waters
 Dale David
 Boris Renski
 Cliff Young
 John Igoe
 Lew Tucker
 Mark Collier
 Simon Anderson
 Sean Roberts
 Alan Clark
 Patrick Fu
 Winston Damarillo
 
 ___
 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] Help with meta-data

2012-08-16 Thread Eugene Kirpichov
Hi Anne,

On Wed, Aug 15, 2012 at 2:55 PM, Anne Gentle a...@openstack.org wrote:
 Hi Eugene -
 But I thought everyone was on the openstack list! :) Thanks for following 
 up.

 On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov ekirpic...@gmail.com 
 wrote:
 Hi Anne,

 I accidentally found this email of yours while looking for links to my post.
 I'd probably have found it earlier if you cc'd me on
 ekirpic...@gmail.com or ekirpic...@mirantis.com [yes, that's two
 different spellings...] :)

 I support the idea that this should be somehow integrated in the docs,
 but I'm not sure where exactly in the docs is a good place for
 information of this style. Would it help if I just linked to the posts
 from some wiki page or from the docs?

 I do like to put relevant blog posts on the wiki at
 http://wiki.openstack.org/BloggersTips, so you can certainly add to
 that page. If it's really missing information in the docs, though, it
 should be added to the docs. I know that's a tough judgement call but
 we all have to encourage that call.

Thanks. I added a link to the post to this wiki page and I'll now
spend some time picking what to integrate into the docs.


 Or would it only help if I (or
 somebody) actually merged the relevant parts of the posts into
 official documentation?

 I wouldn't say only help but I prefer that you merge the relevant
 parts of the posts. It's tougher for a doc team member to merge only
 parts in without violating the license of the content - you as content
 owner can certainly choose which parts to move into the official
 documentation though.

 Thanks for asking for clarifications - these are certainly gray areas
 that I'd like to shine light upon.
 Anne

 On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle a...@openstack.org wrote:
 All, sorry for top posting, but this is a fine example of why we
 really need bloggers to help with the documentation. These fragmented
 instructions are difficult to rely on - we need maintainable,
 process-oriented treatment of content.

 Mirantis peeps, you have added in your blog entries to the docs in the
 past, let's find ways to continually do that and maintain going
 forward.

 I'm not so interested in more install guides, but definitely
 interested in more configuration guides. So Kord, while I like the
 idea (and execution!) of the StackGeek 10-minute guide, it's not one
 to bring into the official docs. But we would definitely welcome your
 reviews of incoming updates to the docs!

 Thanks Simon for bringing your difficulties to the list - we
 continually work on improving the docs. What you learn now could help
 hundreds if not thousands of others, so I'd love for you to improve
 the official docs with your findings.
 Thanks,
 Anne

 On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter si...@gikaku.com wrote:

 On 08/09/2012 12:59 PM, Scott Moser wrote:

 On Aug 8, 2012, at 8:20 PM, Simon Walter si...@gikaku.com wrote:


 On 08/09/2012 06:45 AM, Jay Pipes
 I guess I'll have to build a VM from scratch, as I was relying on the ssh
 key to be able to ssh into the VM, which apparently is supplied by the
 meta-data service.

 use cirros.
 load an image, ssh on with 'cirros' user. pass is 'cubswin:)'


 Thank you. That was good advice.

 Somehow I was not able to connect via ssh. I managed to get novnc working
 and logged into the VM. I can't find anything about connecting via serial 
 or
 the like as you can with Xen. I need to read more about KVM I guess.

 Anyway, I think my networking setup is stuffed. I thought the 10 minutes
 install would be the quickest way to get and running. Now I find myself
 pouring over documentation trying to understand how best to setup
 FlatDHCPManager with two network interfaces. I understand many things have
 changed. So I don't want to go reading something out of date. I found these
 blog posts which explained a lot:
 http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
 http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
 But am I reading the wrong thing? I like the way Stackgeek had it set up:
 http://stackgeek.com/guides/gettingstarted.html

 But I think they are missing details or it's out dated. For example, with
 their setup the vnc console in horizon does not work because nova-vncproxy
 is installed rather than novnc.

 I'm pretty sure I can figure the networking out if I have the right
 documentation in the first place. Is there a clear instructions for this
 anywhere? Or would someone mind walking me through it again. So far I've
 followed the stackgeek setup above, but the networking is obviously 
 stuffed.

 Must I have the flat_interface in promiscuous mode?
 Or does it actually need an IP address?
 Why are my VMs picking up an IP address from the public_interface DHCP
 server and not from the flat_network_bridge?

 Too many questions to ask. So I thought I should just ask: what is missing
 or incorrect from Stackgeeks 10 minute scripts?

 Many thanks 

Re: [Openstack] Gold Member Election Update

2012-08-16 Thread Andrew Clay Shafer
Cisco - Lew Tucker
 Cloudscaling - Randy Bias
 Dell - John Igoe
 Dreamhost - Simon Anderson
 ITRI/CCAT - Dr. Tzi-cker Chiueh
 Mirantis - Boris Renski
 Piston - Joshua McKenty
 Yahoo! - Sean Roberts


Congratulations to the newly elected board members.

Do we have an oath of office?
___
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] Meeting notes

2012-08-16 Thread Vishvananda Ishaya
Hello Everyone,

We had another productive nova-meeting today. We granted a few feature freeze 
exeptions to stuff that just missed F-3 and we pushed a few features to 
Grizzly. Detailed (and slightly cleaned up notes are below.

Vish

Meeting summary
---

* Role Call  (vishy, 21:01:36)

* F3 milestone-critical bugs review  (vishy, 21:02:42)
  * LINK: https://launchpad.net/nova/+milestone/folsom-3  (vishy,
21:02:53)
  * LINK: https://review.openstack.org/11477 needs a +1 to get it over
the line (from vek or comstud?)  (eglynn, 21:09:27)

* Feature Freeze Decisions  (vishy, 21:10:38)
  * VOTE: Voted on Grant a Feature Freeze Exception to Hyper-v Driver?
Results are, yes: 9  (vishy, 21:19:38)
  * LINK:
https://blueprints.launchpad.net/nova/+spec/os-api-network-create
(vishy, 21:20:11)
  * FFE granted to Hyper-V driver  (vishy, 21:22:04)
  * FFE granted to os-api-network-create  (vishy, 21:22:23)
  * LINK:
https://blueprints.launchpad.net/nova/+spec/scheduler-resource-race
(vishy, 21:22:40)
  * returning to this one in a bit  (vishy, 21:28:00)
  * LINK:

https://blueprints.launchpad.net/nova/+spec/general-bare-metal-provisioning-framework
(vishy, 21:28:40)
  * FFE denied for general-bare-metal-provisioning-framework  (vishy,
21:30:43)
  * shuld be reworked for Grizzly  (vishy, 21:31:03)
  * LINK: https://blueprints.launchpad.net/nova/+spec/rebuild-for-ha
(vishy, 21:31:17)
  * FFE denied for rebuild-for-ha  (vishy, 21:34:17)
  * Great feature but not quite ready. Should be shrunk down so it is
easy for deployers to cherry pick it if needed.  (vishy, 21:34:47)
  * LINK:
https://blueprints.launchpad.net/nova/+spec/project-specific-flavors
(vishy, 21:35:00)
  * FFE granted to project-specific-flavors  (vishy, 21:40:00)
  * needs to merge ASAP. One week max.  (vishy, 21:40:11)
  * https://blueprints.launchpad.net/nova/+spec/per-user-quotas  (vishy,
21:40:30)
  * FFE denied for per-user-quotas  (vishy, 21:44:35)
  * needs to be fixed and reproposed for grizzly  (vishy, 21:44:45)
  * LINK:
https://blueprints.launchpad.net/nova/+spec/scheduler-resource-race
(vishy, 21:45:14)
  * scheduler-resource-race is a bug not a feature so it doesn't need a
specific FFE. Will be tracked in a bug  (vishy, 21:54:55)

* Exception Needed?  (vishy, 21:55:48)
  * small backwards compatible changes to rpcapi or drivers do not need
FFEs  (vishy, 21:59:39)

* XML support in Nova  (vishy, 21:58:12)
  * if anyone wants to help with xml support talk to dansmith or vishy
(vishy, 22:02:17)

* Bug Strategy  (vishy, 22:03:20)
  * nova-core: stop working on features and focus on bugs!  (vishy,
22:06:31)
  * LINK: http://wiki.openstack.org/FolsomReleaseSchedule  (markmc,
22:07:06)
  * Discuss when to open grizzly at next weeks meeting  (vishy,
22:09:31)



___
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] Snapshotting ephemeral disks?

2012-08-16 Thread Vishvananda Ishaya

On Aug 16, 2012, at 6:58 AM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:

 I have a system that I've booted using a live CD image (so
 .../instance-ID/disk points at the ISO file).  I've installed an OS
 onto /dev/vda (which is .../instance-ID/disk.local).
 
 Running 'nova image-create INSTANCE NAME` results in a traceback in
 the compute log:
 
  2012-08-16 09:48:56 TRACE nova.rpc.amqp ProcessExecutionError: Unexpected 
 error while running command.
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Command: qemu-img convert -f qcow2 
 -O iso -s 6966cceec946407eb12531ddbe7bb7ac 
 /virt/pools/openstack_2/instance-004c/disk 
 /tmp/tmpMJ9GuL/6966cceec946407eb12531ddbe7bb7ac
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Exit code: 1
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Stdout: ''
  2012-08-16 09:48:56 TRACE nova.rpc.amqp Stderr: qemu-img: Unknown file 
 format 'iso'\n
  2012-08-16 09:48:56 TRACE nova.rpc.amqp 
 
 And the image gets stuck in the SAVING state:
 
# nova image-list
...
| f269eebc-d86e-4cd0-aacc-8b0c53fb3bb2 | cloud-f17-x86_64  | 
 SAVING | 4b3fccf9-28ab-4c29-acdb-cc5c18c862af |
 
 Is there a way to do this properly?  Obviously I can just munge around
 in the filesystem to do what I want, but I was hoping for something
 more convenient.
 
 I guess another option would be...
 
 - Boot from the live CD
 - Create a new volume
 - Attach the volume
 - Install onto the volume
 
 Is it possible to snapshot an ephemeral disk?

This is not possible. Sounds like you really want a fix for this bug:

https://bugs.launchpad.net/nova/+bug/914484

The fix was reverted but hopefully it can be cleaned up and come back in.

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] Help with meta-data

2012-08-16 Thread Eugene Kirpichov
I added some documentation.
Submitted for review here https://review.openstack.org/#/c/11518/

On Thu, Aug 16, 2012 at 4:10 PM, Eugene Kirpichov ekirpic...@gmail.com wrote:
 Hi Anne,

 On Wed, Aug 15, 2012 at 2:55 PM, Anne Gentle a...@openstack.org wrote:
 Hi Eugene -
 But I thought everyone was on the openstack list! :) Thanks for following 
 up.

 On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov ekirpic...@gmail.com 
 wrote:
 Hi Anne,

 I accidentally found this email of yours while looking for links to my post.
 I'd probably have found it earlier if you cc'd me on
 ekirpic...@gmail.com or ekirpic...@mirantis.com [yes, that's two
 different spellings...] :)

 I support the idea that this should be somehow integrated in the docs,
 but I'm not sure where exactly in the docs is a good place for
 information of this style. Would it help if I just linked to the posts
 from some wiki page or from the docs?

 I do like to put relevant blog posts on the wiki at
 http://wiki.openstack.org/BloggersTips, so you can certainly add to
 that page. If it's really missing information in the docs, though, it
 should be added to the docs. I know that's a tough judgement call but
 we all have to encourage that call.

 Thanks. I added a link to the post to this wiki page and I'll now
 spend some time picking what to integrate into the docs.


 Or would it only help if I (or
 somebody) actually merged the relevant parts of the posts into
 official documentation?

 I wouldn't say only help but I prefer that you merge the relevant
 parts of the posts. It's tougher for a doc team member to merge only
 parts in without violating the license of the content - you as content
 owner can certainly choose which parts to move into the official
 documentation though.

 Thanks for asking for clarifications - these are certainly gray areas
 that I'd like to shine light upon.
 Anne

 On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle a...@openstack.org wrote:
 All, sorry for top posting, but this is a fine example of why we
 really need bloggers to help with the documentation. These fragmented
 instructions are difficult to rely on - we need maintainable,
 process-oriented treatment of content.

 Mirantis peeps, you have added in your blog entries to the docs in the
 past, let's find ways to continually do that and maintain going
 forward.

 I'm not so interested in more install guides, but definitely
 interested in more configuration guides. So Kord, while I like the
 idea (and execution!) of the StackGeek 10-minute guide, it's not one
 to bring into the official docs. But we would definitely welcome your
 reviews of incoming updates to the docs!

 Thanks Simon for bringing your difficulties to the list - we
 continually work on improving the docs. What you learn now could help
 hundreds if not thousands of others, so I'd love for you to improve
 the official docs with your findings.
 Thanks,
 Anne

 On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter si...@gikaku.com wrote:

 On 08/09/2012 12:59 PM, Scott Moser wrote:

 On Aug 8, 2012, at 8:20 PM, Simon Walter si...@gikaku.com wrote:


 On 08/09/2012 06:45 AM, Jay Pipes
 I guess I'll have to build a VM from scratch, as I was relying on the 
 ssh
 key to be able to ssh into the VM, which apparently is supplied by the
 meta-data service.

 use cirros.
 load an image, ssh on with 'cirros' user. pass is 'cubswin:)'


 Thank you. That was good advice.

 Somehow I was not able to connect via ssh. I managed to get novnc working
 and logged into the VM. I can't find anything about connecting via serial 
 or
 the like as you can with Xen. I need to read more about KVM I guess.

 Anyway, I think my networking setup is stuffed. I thought the 10 minutes
 install would be the quickest way to get and running. Now I find myself
 pouring over documentation trying to understand how best to setup
 FlatDHCPManager with two network interfaces. I understand many things have
 changed. So I don't want to go reading something out of date. I found 
 these
 blog posts which explained a lot:
 http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
 http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
 But am I reading the wrong thing? I like the way Stackgeek had it set up:
 http://stackgeek.com/guides/gettingstarted.html

 But I think they are missing details or it's out dated. For example, with
 their setup the vnc console in horizon does not work because nova-vncproxy
 is installed rather than novnc.

 I'm pretty sure I can figure the networking out if I have the right
 documentation in the first place. Is there a clear instructions for this
 anywhere? Or would someone mind walking me through it again. So far I've
 followed the stackgeek setup above, but the networking is obviously 
 stuffed.

 Must I have the flat_interface in promiscuous mode?
 Or does it actually need an IP address?
 Why are my VMs picking up an IP address from the public_interface DHCP
 

[Openstack] Openstack Folsom 2 or 3

2012-08-16 Thread Trinath Somanchi
Hi-

I want to download the Openstack Folsom 2 or 3. Is Version 3 downloadable.

My web search is not fruitful with the the link to the download of the
release.

Please guide me on downloading Openstack Folsom - 3 or 2 source code.

thanking you,

-- 
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #408

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/408/Project:quantal_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 12:31:50 -0400Build duration:2 min 23 secBuild cause:Started by user zulBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5077 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.'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 9904.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/tmpZjyQXd/novamk-build-deps -i -r -t apt-get -y /tmp/tmpZjyQXd/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208161232~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208161232~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Fixed: quantal_folsom_nova_trunk #409

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/409/Project:quantal_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 12:35:05 -0400Build duration:5 min 36 secBuild cause:Started by user zulBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 25591 lines...]deleting and forgetting pool/main/n/nova/nova-api-os-volume_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-api_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-cert_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-common_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-kvm_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-lxc_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-qemu_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-uml_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xcp_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xen_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-vncproxy_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2012.2+git201208151430~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2012.2+git201208151430~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/quantal-folsom']Pushed up to revision 429.INFO:root:Storing current commit for next build: e44751162b09c5b57557b89db27656b5bd23341cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/quantal-folsom-proposed /tmp/tmpAXal8y/novamk-build-deps -i -r -t apt-get -y /tmp/tmpAXal8y/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 574a78f066da5032c53069bc7a8be8fe14ea9d04..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208161235~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208161235~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208161235~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A nova_2012.2+git201208161235~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing nova_2012.2+git201208161235~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom nova_2012.2+git201208161235~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/quantal-folsom+ [ ! 0 ]+ jenkins-cli build quantal_folsom_deployEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: quantal_folsom_glance_trunk #115

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_glance_trunk/115/Project:quantal_folsom_glance_trunkDate of build:Thu, 16 Aug 2012 13:31:54 -0400Build duration:2 min 42 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesFix build_sphinx setup.py command.by bcwaldoneditglance/db/sqlalchemy/migrate_repo/manage.pyv2 Images API returns 201 on image data uploadby bcwaldoneditglance/tests/functional/v2/test_images.pyeditglance/api/v2/image_data.pyeditglance/tests/functional/test_cache_middleware.pyeditglance/tests/unit/v2/test_image_data_resource.pyConsole Output[...truncated 2159 lines...]Hunk #9 succeeded at 385 (offset 10 lines).Hunk #10 succeeded at 423 (offset 10 lines).Hunk #11 succeeded at 472 (offset 10 lines).Hunk #12 succeeded at 533 (offset 10 lines).Hunk #13 succeeded at 556 (offset 10 lines).Hunk #14 succeeded at 589 (offset 10 lines).Applying patch disable-network-for-docs.patchpatching file doc/source/conf.pyApplying patch fix-doc-build.patchpatching file glance/db/sqlalchemy/migrate_repo/manage.pyHunk #1 FAILED at 1.1 out of 1 hunk FAILED -- rejects in file glance/db/sqlalchemy/migrate_repo/manage.pyPatch fix-doc-build.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9a66c726-56c5-4352-b1ad-0a0153df400b', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9a66c726-56c5-4352-b1ad-0a0153df400b', '-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/glance/quantal-folsom-proposed /tmp/tmpY_tXzK/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpY_tXzK/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 85d8d7af5808a98bbae7b010595e08752d0c9bd0..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208161331~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208161331~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 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9a66c726-56c5-4352-b1ad-0a0153df400b', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-9a66c726-56c5-4352-b1ad-0a0153df400b', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: quantal_folsom_nova_trunk #410

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/410/Project:quantal_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 13:31:55 -0400Build duration:3 min 50 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesAdds Hyper-V support in nova-compute (with new network_info model), including unit testsby 

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_glance_trunk #111

2012-08-16 Thread openstack-testing-bot
Title: precise_folsom_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_trunk/111/Project:precise_folsom_glance_trunkDate of build:Thu, 16 Aug 2012 13:31:53 -0400Build duration:5 min 6 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix build_sphinx setup.py command.by bcwaldoneditglance/db/sqlalchemy/migrate_repo/manage.pyv2 Images API returns 201 on image data uploadby bcwaldoneditglance/tests/functional/test_cache_middleware.pyeditglance/tests/unit/v2/test_image_data_resource.pyeditglance/tests/functional/v2/test_images.pyeditglance/api/v2/image_data.pyConsole Output[...truncated 5563 lines...]gpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmp16t16A/glance_2012.2+git201208161331~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp16t16A/glance_2012.2+git201208161331~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading glance_2012.2+git201208161331~precise-0ubuntu1.dsc: done.  Uploading glance_2012.2+git201208161331~precise.orig.tar.gz: done.  Uploading glance_2012.2+git201208161331~precise-0ubuntu1.debian.tar.gz: done.  Uploading glance_2012.2+git201208161331~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-folsom', 'glance_2012.2+git201208161331~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2012.2+git201208121432~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-client_2012.2+git201208121432~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2012.2+git201208121432~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2012.2+git201208121432~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2012.2+git201208121432~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2012.2+git201208121432~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2012.2+git201208121432~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/glance/precise-folsom']Pushed up to revision 167.INFO:root:Storing current commit for next build: e818792d7624d7fd242d2e7d415b9293cc4a8f4cINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-folsom-proposed /tmp/tmp16t16A/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp16t16A/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 60576a5baedf910af16b26e0eedb4e487d308166..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208161331~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208161331~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2012.2+git201208161331~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A glance_2012.2+git201208161331~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing glance_2012.2+git201208161331~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom glance_2012.2+git201208161331~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/glance/precise-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #412

2012-08-16 Thread openstack-testing-bot
/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_reboot_shutil.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_detach_volume_shutil.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_live_migration_wmi.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_spawn_cow_image_os.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_live_migration_with_target_failure_time.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_boot_from_volume_shutil.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_power_off_shutil.p.gzaddnova/tests/hyperv/stubs/nova.tests.test_hypervapi.HyperVAPITestCase.test_boot_from_volume_uuid.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_destroy_shutil.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_detach_volume_time.p.gzaddnova/tests/hyperv/stubs/nova.tests.test_hypervapi.HyperVAPITestCase.test_live_migration_wmi.p.gzaddnova/tests/hyperv/stubs/nova.tests.test_hypervapi.HyperVAPITestCase.test_attach_volume_with_target_connection_failure_uuid.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_pause_already_paused_uuid.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_reboot_time.p.gzaddnova/tests/hyperv/stubs/nova.tests.test_hypervapi.HyperVAPITestCase.test_attach_volume_time.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_power_on_os.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_list_instances_shutil.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_resume_already_running_shutil.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_spawn_no_cow_image_time.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_pause_already_paused_shutil.p.gzaddnova/tests/hyperv/db_fakes.pyaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_detach_volume_wmi.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_get_info_wmi.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_spawn_no_vswitch_exception_wmi.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_pre_live_migration_cow_image_os.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_live_migration_with_target_failure_uuid.p.gzaddnova/tests/hyperv/stubs/test_hypervapi.HyperVAPITestCase.test_pause_os.p.gzConsole Output[...truncated 20191 lines...]Build-Time: 66Distribution: precise-folsomFail-Stage: buildInstall-Time: 40Job: nova_2012.2+git201208161332~precise-0ubuntu1.dscPackage: novaPackage-Time: 116Source-Version: 2012.2+git201208161332~precise-0ubuntu1Space: 67628Status: attemptedVersion: 2012.2+git201208161332~precise-0ubuntu1Finished at 20120816-1337Build needed 00:01:56, 67628k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161332~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161332~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpOAQ_FJ/novamk-build-deps -i -r -t apt-get -y /tmp/tmpOAQ_FJ/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ca950e7ea3909110fe05e3239975b7545423670a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208161332~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208161332~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208161332~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208161332~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-fo

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #411

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/411/Project:quantal_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 14:31:55 -0400Build duration:4 min 30 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesRemove unused variablesby zrzhiteditnova/db/sqlalchemy/migrate_repo/versions/090_modify_volume_id_datatype.pyeditnova/db/sqlalchemy/migrate_repo/versions/088_change_instance_id_to_uuid_in_block_device_mapping.pyeditnova/db/sqlalchemy/migrate_repo/versions/082_essex.pyConsole Output[...truncated 5285 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.'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 9929.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/tmpPlFHOc/novamk-build-deps -i -r -t apt-get -y /tmp/tmpPlFHOc/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e44751162b09c5b57557b89db27656b5bd23341c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208161432~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208161432~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #413

2012-08-16 Thread openstack-testing-bot
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/413/Project:precise_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 14:31:54 -0400Build duration:7 min 0 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove unused variablesby zrzhiteditnova/db/sqlalchemy/migrate_repo/versions/082_essex.pyeditnova/db/sqlalchemy/migrate_repo/versions/088_change_instance_id_to_uuid_in_block_device_mapping.pyeditnova/db/sqlalchemy/migrate_repo/versions/090_modify_volume_id_datatype.pyConsole Output[...truncated 20192 lines...]Build-Time: 65Distribution: precise-folsomFail-Stage: buildInstall-Time: 42Job: nova_2012.2+git201208161432~precise-0ubuntu1.dscPackage: novaPackage-Time: 119Source-Version: 2012.2+git201208161432~precise-0ubuntu1Space: 67632Status: attemptedVersion: 2012.2+git201208161432~precise-0ubuntu1Finished at 20120816-1438Build needed 00:01:59, 67632k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161432~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161432~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpMLU82O/novamk-build-deps -i -r -t apt-get -y /tmp/tmpMLU82O/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ca950e7ea3909110fe05e3239975b7545423670a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208161432~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208161432~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208161432~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208161432~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161432~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161432~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_nova_trunk #414

2012-08-16 Thread openstack-testing-bot
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/414/Project:precise_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 15:01:55 -0400Build duration:7 min 17 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAlways create the run_instance records locallyby vishvanandaeditnova/compute/api.pyeditnova/tests/scheduler/test_rpcapi.pyeditnova/scheduler/filter_scheduler.pyeditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyeditnova/scheduler/manager.pyeditnova/tests/scheduler/test_filter_scheduler.pyeditnova/scheduler/rpcapi.pyeditnova/scheduler/chance.pyConsole Output[...truncated 20195 lines...]Build-Time: 63Distribution: precise-folsomFail-Stage: buildInstall-Time: 41Job: nova_2012.2+git201208161502~precise-0ubuntu1.dscPackage: novaPackage-Time: 115Source-Version: 2012.2+git201208161502~precise-0ubuntu1Space: 67624Status: attemptedVersion: 2012.2+git201208161502~precise-0ubuntu1Finished at 20120816-1509Build needed 00:01:55, 67624k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161502~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161502~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpZCwNUB/novamk-build-deps -i -r -t apt-get -y /tmp/tmpZCwNUB/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ca950e7ea3909110fe05e3239975b7545423670a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208161502~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208161502~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208161502~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208161502~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161502~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208161502~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 #413

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/413/Project:quantal_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 15:31:50 -0400Build duration:2 min 34 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 5312 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.'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 9936.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/tmpK4AzGR/novamk-build-deps -i -r -t apt-get -y /tmp/tmpK4AzGR/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e44751162b09c5b57557b89db27656b5bd23341c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208161532~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208161532~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_deploy #39

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_deploy/39/Project:quantal_folsom_deployDate of build:Thu, 16 Aug 2012 15:31:11 -0400Build duration:20 minBuild cause:Started by user adamBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-05.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzlogs/test-12.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 3852 lines...]INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Setting up connection to test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_6.0p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-07.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-08.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-09.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-04.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-11.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-03.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-06.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-10.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-07.os.magners.qa.lexingtonINFO:root:Grabbing information from test-08.os.magners.qa.lexingtonINFO:root:Grabbing information from test-09.os.magners.qa.lexingtonINFO:root:Grabbing information from test-04.os.magners.qa.lexingtonINFO:root:Grabbing information from test-11.os.magners.qa.lexingtonINFO:root:Grabbing information from test-03.os.magners.qa.lexingtonINFO:root:Grabbing information from test-06.os.magners.qa.lexingtonINFO:root:Grabbing information from test-10.os.magners.qa.lexingtonINFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.INFO:paramiko.transport.sftp:[chan 1] sftp session closed.tar: Removing leading `/' from member names+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_nova_trunk #415

2012-08-16 Thread openstack-testing-bot
Title: precise_folsom_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/415/Project:precise_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 15:46:30 -0400Build duration:11 minBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 18749 lines...]deleting and forgetting pool/main/n/nova/nova-api-os-volume_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-api_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-cert_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-common_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-kvm_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-lxc_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-qemu_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-uml_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xcp_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute-xen_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-compute_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-console_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-consoleauth_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-doc_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-network_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-objectstore_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-scheduler_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-vncproxy_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-volume_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2012.2+git201208131210~precise-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2012.2+git201208131210~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-folsom']Pushed up to revision 383.INFO:root:Storing current commit for next build: 2f45636ead3aef36c276804372c382558ecf3fe1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/precise-folsom-proposed /tmp/tmpZozYYD/novamk-build-deps -i -r -t apt-get -y /tmp/tmpZozYYD/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ca950e7ea3909110fe05e3239975b7545423670a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208161547~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208161547~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208161547~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208161547~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing nova_2012.2+git201208161547~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom nova_2012.2+git201208161547~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/precise-folsom+ [ ! 0 ]+ jenkins-cli build precise_folsom_deployEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_nova_trunk #416

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/416/Project:quantal_folsom_nova_trunkDate of build:Thu, 16 Aug 2012 17:38:30 -0400Build duration:2 min 24 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 5276 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.'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 9892.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/tmp3TXsP6/novamk-build-deps -i -r -t apt-get -y /tmp/tmp3TXsP6/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e44751162b09c5b57557b89db27656b5bd23341c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208161738~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208161738~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp


[Openstack-ubuntu-testing-notifications] Build Failure: quantal_folsom_test #12

2012-08-16 Thread openstack-testing-bot
Title: quantal_folsom_test
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_test/12/Project:quantal_folsom_testDate of build:Thu, 16 Aug 2012 18:41:26 -0400Build duration:2 min 42 secBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 1774 lines...]help   Output help for one of the commands belowadd Adds a new image to Glanceupdate  Updates an image's metadata in Glancedelete  Deletes an image from Glanceindex   Return brief information about images in Glancedetails Return detailed information about images inGlanceshowShow detailed information about an image inGlanceclear   Removes all images and metadata from GlanceMember Commands:image-membersList members an image is shared withmember-imagesList images shared with a membermember-add   Grants a member access to an imagemember-deleteRevokes a member's access to an imagemembers-replace  Replaces all membership for an imageUnknown command: image-list=SKIP boot_from_volumeSKIP client-argsSKIP client-envSKIP quantumSKIP swiftPASS bundlePASS sec_groupsFAILED aggregatesFAILED eucaFAILED floating_ipsFAILED volumes=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