date:20120814

balaji patnala wrote:
 Can we download Folsom branch codebase for understanding Quantum and
 other changes in Folsom release?

You definitely can. On Thursday we'll have our last development
milestone (folsom-3) which should contain almost all the features of the
upcoming release, so it's a great starting point to understand the
changes coming up in Folsom.

For Quantum, you can access the Folsom branch (master) at:
https://github.com/openstack/quantum

-- 
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] [Quantum] Removing quantum-rootwrap

Dan Wendlandt wrote:
 On Mon, Aug 13, 2012 at 12:51 PM, Vishvananda Ishaya
 vishvana...@gmail.com mailto:vishvana...@gmail.com wrote:
 
 This is up to dan, I suppose, but the rootwrap stuff seems like
 something worth granting a ffe to…
 
 
 I wasn't going to mention it, as the urgency of a nearby deadline can be
 helpful :) 
 
 But yes, I'd grant an ffe to something this important, especially
 because it applies across all uses of quantum.

On one hand it's a change that impacts almost all use cases, so
definitely not something that is simple or self-contained. On the other,
it's quite easy to trace back issues to this. In summary, if it's the
only exception in Quantum, it's not really a problem :)

[warning: a trick is included in the last paragraph]

-- 
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] [Dashboard] Multi-region support in Horizon?

2012-08-14 Thread Yufang Zhang

Hi all,

I'd like to use horizon to manage clusters in multiple data
centers(regions).  Currently, horizon supports multi-region by means of
deploying one keystone service for each region. Thus we have to manage
multiple keystone services for all the regions(creating users or projects,
etc.), which doesn't make sense. Should it be better to allow users to
choose service endpoints(nova or glance) according to region name? At
least, novaclient works as this way: you can provide region name(via
--os_region_name option) as a filter to select nova service endpoint to
access, so that we could deploy just one keystone service to manage
services on different regions. Or is there any better workaround?

Best Regards.

Yufang
___
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] Hyper-V meeting agenda

2012-08-14 Thread Peter Pouliot

Hello Everyone,

Today's Hyper-v meeting will discuss the following:


  *   Status of Code Submission:  We submitted yesterday and have passed 
through the Jenkins and Smokestack gates.
  *   Status of CI infrastructure.
  *   Documentation needs

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

Re: [Openstack] [Keystone] Quotas: LDAP Help

2012-08-14 Thread Ionut Artarisi


On 07/25/2012 05:32 PM, Adam Young wrote:

On 07/25/2012 10:19 AM, Ionuț Arțăriși wrote:


Hi,

I just wanted to add a bit to this thread. We're currently working on 
a hybrid backend between LDAP and SQL. I have a working version for a 
specific setup in which the user accounts are stored in LDAP, but 
tenants and roles are all stored in SQL together with other openstack 
user accounts such as the nova admin account.


I basically just Frankensteined the two backends together for user 
processing and left everything else to be handled by the SQL backend. 
I'd like to hear other people's opinion on this or alternative 
implementations.


Are tenants completely in the SQL DB?  If so, how to you list tenants 
for a given user?


Do you copy users from LDAP to SQL for anything?


Urgh, sorry for the late answer.

Tenats are all in the SQL DB and no users are copied from LDAP to SQL.

For listing tenants for a given user, right now we have a hacky 
get_tenants_for_user method which can be configured/rewritten by the 
sysadmin. We have a sample method which adds a pre-configured tenant to 
the existing list of tenants (from SQL) for usecases like: make all LDAP 
users part of tenant X.


-Ionuț


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

Re: [Openstack] Setting Expectations

Andrew Clay Shafer wrote:
 What is OpenStack?
 
 Clearly, OpenStack is many things to many people and organizations.
 
 What does it mean to contribute to OpenStack? What does it mean to
 deploy OpenStack? What does it mean to operate OpenStack?
 
 What do we mean when we say compatible? interoperable? community? branded?
 
 Is OpenStack a framework? a project? a product?
 
 Recent discussions make it clear that we have a lot of different ideas
 about all of these things.

These are important and difficult questions. As you say, OpenStack is
many different things to different people. So far we survived while
avoiding to answer clearly, mostly because we had no good way of coming
up with answers. That ultimately creates tension between participants in
our community when the different models clash.

My hope is that the formation of the Foundation will help providing a
forum for this discussion, and a mechanism to come with clearer answers.
I actually see that as the main mission of the Foundation for the first
year.

-- 
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] Best practices for non persistent vm management

2012-08-14 Thread Romain Vrignaud

Hello everybody,

I'm currently trying to find a more robust way to manage the virtualization
in my company than using
directly libvirt and kvm.

I'm following with great interest the Openstack development but there is
still a point that is very scary to
me : the non persistency of VM. I understand that is a very different way
than managing classical virtualisation
with persistent data like we could do with project live oVirt.

Is there any resource (white paper, blog, etc) that indicates best
practices to migrate from classical virtualisation
to cloud way ?
What does that impact really, the workflow changes. If this is to be handle
at system level or application level and so
on.

I realize that it is a very large question but I think that I'm not the
only one to be disturbed.

Thanks in advance.

Regards,

Romain
___
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] (no subject)

2012-08-14 Thread Alessio Ababilov

Hi!

I would like to discuss https://bugs.launchpad.net/nova/+bug/1036672 -
Unable to spawn instance after I delete and create same network

Steps to reproduce:

1. Create project and network
2. Spawn instance
3. Delete instance
4. Delete project and network
5. Create same network
6. Create project
7. Spawn instance
8. The instance will not be spawned, you will see that the deleted
network was not found in nova-network log

This bug reproduces for this reason.

When deleting a network, its record is removed from database and its
fixed_ips are marked as deleted.
During instance spawning, an IP address is chosen. Then
fixed_ip_get_by_address is called. It calls model_query passing
read_deleted=yes. The deleted fixed ip is chosen and it causes
NetworkNotFound. The same error will be during instance deletion while
disassociating fixed IP.

In folsom, fixed_ip_get_by_address does not pass read_deleted flag
anymore, however, its `context` parameter contains read_deleted=yes
when IP is being disassociated. So, NetworkNotFound is raised again.

I would like to ask several questions:

1) Is it really necessary to keep deleted fixed IPs in the database? A
network cannot be removed until it is not used, so, it should be safe
to remove its fixed IPs.
2) How control a code using database context? It could be too tricky
and it difficult to predict when its flags, e.g. read_deleted, are set
to some values.
3) Who actually uses objects that are marked as deleted in the
database? I know only one example - instance types that can be deleted
but are still referenced by running instances. Are there other
examples?


--
Alessio Ababilov
Software Engineer
Grid Dynamics

___
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 Summit Tracks Topics

Lauren Sell wrote:
 Speaking submissions for the conference-style content are
 live http://www.openstack.org/summit/san-diego-2012/call-for-speakers/ 
 (basically
 everything except the Design Summit working sessions which will open for
 submissions in the next few weeks), and the deadline is August 30.

A bit of explanation on the contents for the Design Summit track:

The Design Summit track is for developers and contributors to the next
release cycle of OpenStack (codenamed Grizzly). Each session is an
open discussion on a given technical theme or specific feature
to-be-developed in one of the OpenStack core projects.

Compared to previous editions, we'll run parallel to rest of the
OpenStack Summit and just be one of the tracks for the general event.
We'll run over 4 days, but there will be no session scheduled during the
general session of the OpenStack Summit (first hours in the morning on
Tuesday/Wednesday). Finally, all sessions will be 40-min long, to align
with the rest of the event.

Within the Design Summit we also used to have classic presentations
around Devops, ecosystem and related projects: those will now have their
own tracks in the OpenStack Summit (Operations Summit, Related OSS
Projects, Ecosystem, Security...), so they are no longer a subpart
of the Design Summit track. The Design Summit will be entirely
focused on the Grizzly cycle of official OpenStack projects, and
entirely made of open discussions. We'll also have some breakout rooms
available for extra workgroups and incubated projects.

The sessions within the design summit are now organized around Topics.
The topics for the Design Summit are the core projects,
openstack-common, Documentation and a common Process track to cover
the release cycle and infrastructure. Each topic content is coordinated
by the corresponding team lead(s).

Since most developers are focused on Folsom right now, we traditionally
open our call for sessions a bit later (should be opened first week of
September). Contributors will be invited to suggest a topic for design
summit sessions. After the Folsom release, each topic lead will review
the suggestions, merge some of them and come up with an agenda for
his/her topic. You can already see the proposed topic layout on the
Design Summit topics tab in the document linked in Lauren's email.

Comments/Feedback welcome !

-- 
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 Summit Tracks Topics

2012-08-14 Thread Sandy Walsh

Perhaps off topic, but ...

One of the things I've noticed at the last couple of summits are the number of 
new attendees that could really use an OpenStack 101 session. Many of them are 
on fact-finding missions and their understanding of the architecture is 
10,000'+. 

Usually when conf's get to this size there's a day beforehand for 
workshops/tutorials/getting-started stuff. I'm sure it's too late for this 
coming summit, but perhaps something to consider for later ones?

Hands-on, code-level, devstack, configuration, debug. I'd be happy to help out 
with this.

Thoughts?
-S


From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net 
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of 
Thierry Carrez [thie...@openstack.org]
Sent: Tuesday, August 14, 2012 12:19 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Summit Tracks  Topics

Lauren Sell wrote:
 Speaking submissions for the conference-style content are
 live http://www.openstack.org/summit/san-diego-2012/call-for-speakers/ 
 (basically
 everything except the Design Summit working sessions which will open for
 submissions in the next few weeks), and the deadline is August 30.

A bit of explanation on the contents for the Design Summit track:

The Design Summit track is for developers and contributors to the next
release cycle of OpenStack (codenamed Grizzly). Each session is an
open discussion on a given technical theme or specific feature
to-be-developed in one of the OpenStack core projects.

Compared to previous editions, we'll run parallel to rest of the
OpenStack Summit and just be one of the tracks for the general event.
We'll run over 4 days, but there will be no session scheduled during the
general session of the OpenStack Summit (first hours in the morning on
Tuesday/Wednesday). Finally, all sessions will be 40-min long, to align
with the rest of the event.

Within the Design Summit we also used to have classic presentations
around Devops, ecosystem and related projects: those will now have their
own tracks in the OpenStack Summit (Operations Summit, Related OSS
Projects, Ecosystem, Security...), so they are no longer a subpart
of the Design Summit track. The Design Summit will be entirely
focused on the Grizzly cycle of official OpenStack projects, and
entirely made of open discussions. We'll also have some breakout rooms
available for extra workgroups and incubated projects.

The sessions within the design summit are now organized around Topics.
The topics for the Design Summit are the core projects,
openstack-common, Documentation and a common Process track to cover
the release cycle and infrastructure. Each topic content is coordinated
by the corresponding team lead(s).

Since most developers are focused on Folsom right now, we traditionally
open our call for sessions a bit later (should be opened first week of
September). Contributors will be invited to suggest a topic for design
summit sessions. After the Folsom release, each topic lead will review
the suggestions, merge some of them and come up with an agenda for
his/her topic. You can already see the proposed topic layout on the
Design Summit topics tab in the document linked in Lauren's email.

Comments/Feedback welcome !

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

___
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 Summit Tracks Topics

2012-08-14 Thread Huang Zhiteng

On Tue, Aug 14, 2012 at 11:29 PM, Sandy Walsh sandy.wa...@rackspace.com wrote:
 Perhaps off topic, but ...

 One of the things I've noticed at the last couple of summits are the number 
 of new attendees that could really use an OpenStack 101 session. Many of them 
 are on fact-finding missions and their understanding of the architecture is 
 10,000'+.

 Usually when conf's get to this size there's a day beforehand for 
 workshops/tutorials/getting-started stuff. I'm sure it's too late for this 
 coming summit, but perhaps something to consider for later ones?

 Hands-on, code-level, devstack, configuration, debug. I'd be happy to help 
 out with this.
+1!

 Thoughts?
 -S

 
 From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net 
 [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf 
 of Thierry Carrez [thie...@openstack.org]
 Sent: Tuesday, August 14, 2012 12:19 PM
 To: openstack@lists.launchpad.net
 Subject: Re: [Openstack] OpenStack Summit Tracks  Topics

 Lauren Sell wrote:
 Speaking submissions for the conference-style content are
 live http://www.openstack.org/summit/san-diego-2012/call-for-speakers/ 
 (basically
 everything except the Design Summit working sessions which will open for
 submissions in the next few weeks), and the deadline is August 30.

 A bit of explanation on the contents for the Design Summit track:

 The Design Summit track is for developers and contributors to the next
 release cycle of OpenStack (codenamed Grizzly). Each session is an
 open discussion on a given technical theme or specific feature
 to-be-developed in one of the OpenStack core projects.

 Compared to previous editions, we'll run parallel to rest of the
 OpenStack Summit and just be one of the tracks for the general event.
 We'll run over 4 days, but there will be no session scheduled during the
 general session of the OpenStack Summit (first hours in the morning on
 Tuesday/Wednesday). Finally, all sessions will be 40-min long, to align
 with the rest of the event.

 Within the Design Summit we also used to have classic presentations
 around Devops, ecosystem and related projects: those will now have their
 own tracks in the OpenStack Summit (Operations Summit, Related OSS
 Projects, Ecosystem, Security...), so they are no longer a subpart
 of the Design Summit track. The Design Summit will be entirely
 focused on the Grizzly cycle of official OpenStack projects, and
 entirely made of open discussions. We'll also have some breakout rooms
 available for extra workgroups and incubated projects.

 The sessions within the design summit are now organized around Topics.
 The topics for the Design Summit are the core projects,
 openstack-common, Documentation and a common Process track to cover
 the release cycle and infrastructure. Each topic content is coordinated
 by the corresponding team lead(s).

 Since most developers are focused on Folsom right now, we traditionally
 open our call for sessions a bit later (should be opened first week of
 September). Contributors will be invited to suggest a topic for design
 summit sessions. After the Folsom release, each topic lead will review
 the suggestions, merge some of them and come up with an agenda for
 his/her topic. You can already see the proposed topic layout on the
 Design Summit topics tab in the document linked in Lauren's email.

 Comments/Feedback welcome !

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

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



-- 
Regards
Huang Zhiteng

___
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] Hyper-V meeting minutes

2012-08-14 Thread Peter Pouliot

Hi All,

Here are the minutes from today's meeting.  Please take questions to 
#openstack-hyper-v.

Meeting ended Tue Aug 14 15:52:35 2012 UTC.  Information about MeetBot at 
http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-15.00.html
Minutes (text): 
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-15.00.txt
Log:
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-14-15.00.log.html

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

Re: [Openstack] [openstack-dev] [nova] Disk attachment consistency

2012-08-14 Thread Scott Moser

On Mon, 13 Aug 2012, Vishvananda Ishaya wrote:

 Hey Everyone,

 Resulting Issues
 

 a) The device name only makes sense for linux. FreeBSD will select
 different device names, and windows doesn't even use device names. In
 addition xen uses /dev/xvda and kvm uses /dev/vda

 b) The device sent in kvm will not match where it actually shows up. We
 can consistently guess where it will show up if the guest kernel is =
 3.2, otherwise we are likely to be wrong, and it may change on a reboot
 anyway

 Long term solutions
 --

 We probably shouldn't expose a device path, it should be a device number. 
 This is probably the right change long term, but short term we need to make 
 the device name make sense somehow. I want to delay the long term until after 
 the summit, and come up with something that works short-term with our 
 existing parameters and usage.

 The first proposal I have is to make the device parameter optional. The 
 system will automatically generate a valid device name that will be accurate 
 for xen and kvm with guest kernel 3.2, but will likely be wrong for old kvm 
 guests in some situations. I think this is definitely an improvement and only 
 a very minor change to an extension api (making a parameter optional, and 
 returning the generated value of the parameter).

 (review at https://review.openstack.org/#/c/10908/)

 The second proposal I have is to use a feature of kvm attach and set the
 device serial number. We can set it to the same value as the device
 parameter. This means that a device attached to /dev/vdb may not always
 be at /dev/vdb (with old kvm guests), but it will at least show up at
 /dev/disk/by-id/virtio-vdb consistently.

This is the right way to do this.
Expose 'serial-number' (or some other name for it) in the API, attach the
device with that serial number and get out of the way.

If the user doesn't provide you one, then create a unique one (at least
for that guest) and return it.  For many use cases, a user attaches a
disk, ssh's in, finds the new disk, and uses it.  Don't burden them with
coming up with a naming/uuid scheme for this parameter if they dont want
to.

Does xen have anything like this?  Can you set the serial number of the
xen block device?

 (review coming soon)

 First question: should we return this magic path somewhere via the api?
 It would be pretty easy to have horizon generate it but it might be nice
 to have it show up. If we do return it, do we mangle the device to
 always show the consistent one, or do we return it as another parameter?
 guest_device perhaps?

From the api perspective, I think it makes most sense to call it what it
is.  Don't make any promises or allusions to what the guest OS will do
with it.

 Second question: what should happen if someone specifies /dev/xvda
 against a kvm cloud or /dev/vda against a xen cloud?
 I see two options:
 a) automatically convert it to the right value and return it
 b) fail with an error message

In EC2, this fails with an error message.  I think this is more correct.
The one issue here is that you really cannot, and should not attempt to
guess or know what the guest has named devices.  Thats why we're we have
this problem in the first place.

So, I dont have strong feelings either way on this.  Its broken to pass
'device=' and assume that means something.

 Third question: what do we do if someone specifies a device value to a
 kvm cloud that we know will not work. For example the vm has /dev/vda
 and /dev/vdb and they request an attach at /dev/vdf. In this case we
 know that it will likely show up at /dev/vdc. I see a few options here
 and none of them are amazing:

 a) let the attach go through as is.
   advantages: it will allow scripts to work without having to manually find 
 the next device.
   disadvantages: the device name will never be correct in the guest
 b) automatically modify the request to attach at /dev/vdc and return it
   advantages: the device name will be correct some of the time (kvm guests 
 with newer kernels)
   disadvantages: sometimes the name is wrong anyway. The user may not expect 
 the device number to change
 c) fail and say, the next disk must be attached at /dev/vdc:
   advantages: explicit
   disadvantages: painful, incompatible, and the place we say to attach may be 
 incorrect anyway (kvm guests with old kernels)

I vote 'a'.
Just be stupid. Play it simple, don't believe that you can understand what
device naming convention the guest kernel and udev have decided upon.

Heres an example.  Do you know what happens if I attach 26 devices?
/dev/vd[a-z], then what?  I'm pretty sure it goes to /dev/vd[a-z][a-z],
but its not worth you trying to know that.  That convention may not be
followed for xen block devices.  At one point (maybe only with scsi
attached disks, letters were never re-used, so an attach, detach, attach
would end up going /dev/vdb, dev/vdc, /dev/vdd).

There is no binary api that linux and udev promise on this, so

Re: [Openstack] OpenStack Summit Tracks Topics

Sandy Walsh wrote:
 Perhaps off topic, but ...
 
 One of the things I've noticed at the last couple of summits are the number 
 of new attendees that could really use an OpenStack 101 session. Many of them 
 are on fact-finding missions and their understanding of the architecture is 
 10,000'+. 
 
 Usually when conf's get to this size there's a day beforehand for 
 workshops/tutorials/getting-started stuff. I'm sure it's too late for this 
 coming summit, but perhaps something to consider for later ones?
 
 Hands-on, code-level, devstack, configuration, debug. I'd be happy to help 
 out with this.

Note that there are workshops planned on the Monday, so that's still
doable... But it's in parallel with the Design Summit track, so you need
to practice your Clone spell.

-- 
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] [Nova] How common is user_data for instances?

2012-08-14 Thread Jay Pipes

On 08/13/2012 07:38 PM, Michael Still wrote:
 On 14/08/12 08:54, Jay Pipes wrote:
 
 I was *going* to create a random-data table with the same average row
 size as the instances table in Nova to see how long the migration would
 take, and then I realized something... The user_data column is already
 of column type MEDIUMTEXT, not TEXT:

 jpipes@uberbox:~$ mysql -uroot nova -e DESC instances | grep user_data
 user_datamediumtext  YES NULL

 So the column can already store data up to 2^24 bytes long, or 16MB of
 data. So this might be a moot issue already? Do we expect user data to
 be more than 16MB?
 
 The bug reports truncation at 64kb. The last schema change I can see for
 that column is Essex version 82, which has:
 
 $ grep user_data *.py
 082_essex.py:Column('user_data', Text),
 
 http://docs.sqlalchemy.org/en/latest/dialects/mysql.html says that Text
 is MySQL TEXT type, for text up to 2^16 characters.
 
 Am I misunderstanding something here?

No, I read the exact same thing in the SQLAlchemy docs and was surprised
to see the column type was MEDIUMTEXT. But I assure you it is :) Just
run devstack and verify!

-jay

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

[Openstack] [Swift] Where do we go from here?

2012-08-14 Thread John Dickinson

Swift has many exciting features coming in the OpenStack Folsom
Release this fall, but where do we go from here? What's next for Swift
in grizzly?

I've got some ideas. I'd like to mention them and see where you the
community will take them. I've written up most of them into quick one-
line blueprints in Launchpad. If you'd like to contribute, grab the
blueprint and jump in.

- Optimize the many small writes workload. Swift actually handles
  many small concurrent writes very well. However, many small writes
  generally also implies that the cardinality of a single container
  gets very large. There are two ways this use case can be improved:

- Implement transparent container sharding
  https://blueprints.launchpad.net/swift/+spec/container-sharding

- Provide better listing traversal abstractions. Listing a few
  billion objects ten thousand at a time is somewhat impractical.

- Solve globally distributed clusters. How can I have servers in
  London and servers in San Jose in the same logical swift cluster
  with three replicas total, but guaranteed to have at least one
  replica in each cluster?
  https://blueprints.launchpad.net/swift/+spec/multi-region

- Support a single logical swift cluster with tiers of storage (eg
  cheap spinning disks and expensive high IOPS SSD arrays). Can, for
  example, a user choose to have a container and its objects be served
  from a particular tier of storage?
  https://blueprints.launchpad.net/swift/+spec/storage-tiers

- Some deployers have implemented metadata searching by intercepting
  write requests and sending the metadata to another system. Can
  metadata searching be implemented in swift itself? One possible
  implementation would be to dynamically generate indexes on the
  container DB.
  https://blueprints.launchpad.net/swift/+spec/searchable-metadata

- Support PUTs with unlimited size. Implement server-side large object
  splitting.
  https://blueprints.launchpad.net/swift/+spec/large-single-uploads

- Support the full HTTP spec for range requests
  https://blueprints.launchpad.net/swift/+spec/multi-range-support

- There are a few things that could be done to simplify installation

- Create or refactor existing code into a single swift binary or
  startup script. Would it be possible, for example, to install
  swift and run one command with the data drives listed and swift
  just works?

- Build a ring server that automatically discovers devices
  https://blueprints.launchpad.net/swift/+spec/ring-builder-server

- Provide a simple, intuitive way to test a deployment after install
  https://blueprints.launchpad.net/swift/+spec/post-deploy-test

- Support concurrent reads to objects to support a read-heavy workload
  https://blueprints.launchpad.net/swift/+spec/concurrent-reads

If you are in the San Francisco area, we will have a swift meetup on
August 30 at Citizen Space SF at 6:30 pm.
http://www.meetup.com/openstack/events/77706042/

We will have a swift team meeting on Monday October 1 in
#openstack-meeting at 8pm UTC to discuss the plans for swift over the
next six months and the sessions for the design summit. If you are
interested in participating in swift development, please attend.

If you are a new contributor to swift, please read
http://wiki.openstack.org/HowToContribute.

--John



smime.p7s
Description: S/MIME cryptographic signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

2012-08-14 Thread Richard W.M. Jones

On Wed, Aug 08, 2012 at 11:08:48AM +0100, Daniel P. Berrange wrote:
 Also note that current work is being done to make libguestfs use
 libvirt to launch its appliance VMs, at which point libguestfs VMs
 will be strongly confined by sVirt (SELinux/AppArmour), and also
 able to run as a separate user ID.

Thanks for the advert Dan :-)

If you've got libguestfs = 1.19.25, then you can in fact already use
libvirt to manage the appliance.  You just need to set the environment
variable LIBGUESTFS_ATTACH_METHOD=libvirt before running the
libguestfs-using tool.

SELinux confinement is nearly working too.  I'm just waiting on a
change to the SELinux policy before it's done.

Fedora 18 will have all the necessary bits.

Rich.

-- 
Richard Jones
Red Hat

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

Re: [Openstack] Setting Expectations

2012-08-14 Thread Andrew Clay Shafer

 These are important and difficult questions. As you say, OpenStack is
 many different things to different people. So far we survived while
 avoiding to answer clearly, mostly because we had no good way of coming
 up with answers. That ultimately creates tension between participants in
 our community when the different models clash.


Yes, these are difficult questions.

I'm don't agree with the assertion that there was no good way of coming up
with answers, but for a variety of reasons, we did not.

You say OpenStack has survived, but I believe we may have compounded and
multiplied the challenges OpenStack faces by collectively neglecting to
resolve this. Without going into all the technical necessity and political
complexity, I would argue we allowed OpenStack fragmentation at the project
level. Without a unified conscience of purpose, the fragmentation only gets
magnified at the point users are interacting with different deployments.

I want to also respond to the idea that OpenStack can be seen like the
Linux kernel. This is a point I made and articulated early in the OpenStack
discussion.

The artifacts of my using that analogy date back to the Fall of 2010:
http://www.slideshare.net/littleidea/open-stack-sdforum/44
http://www.slideshare.net/littleidea/openstack-summit-a-community-of-service-providers/27

I don't believe that the kernel is a perfect analogy, but even if it was
this one sentence 'OpenStack is like the Linux kernel' will not make it so.

Linus Torvalds provides both technical oversight and the kind of conscience
I keep referring to.

What is the OpenStack equivalent of this?
https://lkml.org/lkml/2012/3/8/495

I suggest everyone read the whole email from Linus at that link.

On some level, this attitude is what prevents a preponderance of the
tension we have recently seen in OpenStack mailing lists. Granted, it
implies other more pointed conflict, but some of that is Linus being Linus.
The very real choice in these types of projects is between resolving open
conflict early and often or sublimated conflicts that tend to erupt with a
vengeance later.


 My hope is that the formation of the Foundation will help providing a
 forum for this discussion, and a mechanism to come with clearer answers.
 I actually see that as the main mission of the Foundation for the first
 year.


I share this hope, but I also don't think we should abdicate all
responsibility for this to the Foundation.

We are all ostensibly individual members of the foundation, if not
corporate members.

OpenStack will be what we collectively make it.

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

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

I have to ask.  Wasn't FUSE designed to do alot of this stuff?  It is
userspace and it doesn't do nasty stuff to file systems.  Why aren't we
going that route?

-Matt

On Tue, Aug 14, 2012 at 11:05 AM, Richard W.M. Jones r...@annexia.orgwrote:

 On Wed, Aug 08, 2012 at 11:08:48AM +0100, Daniel P. Berrange wrote:
  Also note that current work is being done to make libguestfs use
  libvirt to launch its appliance VMs, at which point libguestfs VMs
  will be strongly confined by sVirt (SELinux/AppArmour), and also
  able to run as a separate user ID.

 Thanks for the advert Dan :-)

 If you've got libguestfs = 1.19.25, then you can in fact already use
 libvirt to manage the appliance.  You just need to set the environment
 variable LIBGUESTFS_ATTACH_METHOD=libvirt before running the
 libguestfs-using tool.

 SELinux confinement is nearly working too.  I'm just waiting on a
 change to the SELinux policy before it's done.

 Fedora 18 will have all the necessary bits.

 Rich.

 --
 Richard Jones
 Red Hat

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

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

Re: [Openstack] OpenStack Summit Tracks Topics

2012-08-14 Thread Jacob Walcik

I would be happy to work with Sandy (or anyone else who might be
interested) on an intro session (or two) for Nova.

-- 
Jacob Walcik
Enterprise Architect
Rackspace Cloud Builders
Direct: 512-539-1051
Toll Free: 800-961-4454x5061051




On 8/14/12 12:05 PM, John Dickinson m...@not.mn wrote:

SwiftStack would like to do an intro session on swift on Monday. We'll
also be signing up for several workshops.

--John


On Aug 14, 2012, at 9:57 AM, Lauren Sell lau...@openstack.org wrote:

 We have space available Monday if someone wants to run a getting
started track in the morning (or all day), but it would run alongside
Design Summit sessions.
 
 I'm sure we could also set up something informal Sunday evening if that
works better.
 
 On Aug 14, 2012, at 10:41 AM, Huang Zhiteng wrote:
 
 On Tue, Aug 14, 2012 at 11:29 PM, Sandy Walsh
sandy.wa...@rackspace.com wrote:
 Perhaps off topic, but ...
 
 One of the things I've noticed at the last couple of summits are the
number of new attendees that could really use an OpenStack 101
session. Many of them are on fact-finding missions and their
understanding of the architecture is 10,000'+.
 
 Usually when conf's get to this size there's a day beforehand for
workshops/tutorials/getting-started stuff. I'm sure it's too late for
this coming summit, but perhaps something to consider for later ones?
 
 Hands-on, code-level, devstack, configuration, debug. I'd be happy to
help out with this.
 +1!
 
 Thoughts?
 -S
 
 
 From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on
behalf of Thierry Carrez [thie...@openstack.org]
 Sent: Tuesday, August 14, 2012 12:19 PM
 To: openstack@lists.launchpad.net
 Subject: Re: [Openstack] OpenStack Summit Tracks  Topics
 
 Lauren Sell wrote:
 Speaking submissions for the conference-style content are
 live 
http://www.openstack.org/summit/san-diego-2012/call-for-speakers/
(basically
 everything except the Design Summit working sessions which will open
for
 submissions in the next few weeks), and the deadline is August 30.
 
 A bit of explanation on the contents for the Design Summit track:
 
 The Design Summit track is for developers and contributors to the next
 release cycle of OpenStack (codenamed Grizzly). Each session is an
 open discussion on a given technical theme or specific feature
 to-be-developed in one of the OpenStack core projects.
 
 Compared to previous editions, we'll run parallel to rest of the
 OpenStack Summit and just be one of the tracks for the general
event.
 We'll run over 4 days, but there will be no session scheduled during
the
 general session of the OpenStack Summit (first hours in the morning
on
 Tuesday/Wednesday). Finally, all sessions will be 40-min long, to
align
 with the rest of the event.
 
 Within the Design Summit we also used to have classic presentations
 around Devops, ecosystem and related projects: those will now have
their
 own tracks in the OpenStack Summit (Operations Summit, Related OSS
 Projects, Ecosystem, Security...), so they are no longer a
subpart
 of the Design Summit track. The Design Summit will be entirely
 focused on the Grizzly cycle of official OpenStack projects, and
 entirely made of open discussions. We'll also have some breakout rooms
 available for extra workgroups and incubated projects.
 
 The sessions within the design summit are now organized around
Topics.
 The topics for the Design Summit are the core projects,
 openstack-common, Documentation and a common Process track to cover
 the release cycle and infrastructure. Each topic content is
coordinated
 by the corresponding team lead(s).
 
 Since most developers are focused on Folsom right now, we
traditionally
 open our call for sessions a bit later (should be opened first week of
 September). Contributors will be invited to suggest a topic for design
 summit sessions. After the Folsom release, each topic lead will review
 the suggestions, merge some of them and come up with an agenda for
 his/her topic. You can already see the proposed topic layout on the
 Design Summit topics tab in the document linked in Lauren's email.
 
 Comments/Feedback welcome !
 
 --
 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
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 
 
 
 -- 
 Regards
 Huang Zhiteng
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe :

[Openstack] RedHAt * OPenSTack

2012-08-14 Thread Frans Thamura

hi all

Redhat just post in his wall

openstack..

http://www.redhat.com/openstack/?sc_cid=7016000TmB8AAK


--
Frans Thamura (曽志胜)
Shadow Master and Lead Investor
Meruvian.
Integrated Hypermedia Java Solution Provider.

Mobile: +628557888699
Blog: http://blogs.mervpolis.com/roller/flatburger (id)

FB: http://www.facebook.com/meruvian
TW: http://www.twitter.com/meruvian / @meruvian
Website: http://www.meruvian.org

We grow because we share the same belief.

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

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

2012-08-14 Thread Eric Windisch

On Tuesday, August 14, 2012 at 14:30 PM, Matt Joyce wrote:
 I have to ask.  Wasn't FUSE designed to do alot of this stuff?  It is 
 userspace and it doesn't do nasty stuff to file systems.  Why aren't we going 
 that route?
Fuse was really designed for the opposite scenario. Fuse modules run as 
daemons, they're not libraries.  These daemons attach to a character device and 
map userspace code into the VFS.  Instead, we want to access a filesystem from 
userspace code.  It is a shame, however, because you're right… there is plenty 
of code there that knows how to read filesystems in userspace.  Unfortunately, 
the FUSE design really doesn't do us any favors.

That said, there are some crazy options to fix that. One could theoretically 
replace the FUSE character device with one that spoke to userspace processes, 
instead of interacting with the VFS.  There has even been work into creating 
user-space character devices.  One could also make FUSE work with Unix sockets 
as an alternative to character devices…

None of this is out of the box, tested, or even in existence...

Regards,
Eric Windisch


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

Re: [Openstack] RedHAt * OPenSTack

2012-08-14 Thread Joshua Harlow

Are signups taking a while??

Anyone else got the email yet, I think they lost mine, sad++

On 8/14/12 11:57 AM, Frans Thamura fr...@meruvian.org wrote:

hi all

Redhat just post in his wall

openstack..

http://www.redhat.com/openstack/?sc_cid=7016000TmB8AAK


--
Frans Thamura (曽志胜)
Shadow Master and Lead Investor
Meruvian.
Integrated Hypermedia Java Solution Provider.

Mobile: +628557888699
Blog: http://blogs.mervpolis.com/roller/flatburger (id)

FB: http://www.facebook.com/meruvian
TW: http://www.twitter.com/meruvian / @meruvian
Website: http://www.meruvian.org

We grow because we share the same belief.

___
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] [Dashboard] Multi-region support in Horizon?

In the short term you might be able to setup something with a horizon
customization module...

http://docs.openstack.org/developer/horizon/topics/customizing.html

In the long term I think federation should be a concern for grizzly
planning in horizon.  But maybe I am just being a little too optimistic.

-Matt

On Tue, Aug 14, 2012 at 3:28 AM, Yufang Zhang yufang521...@gmail.comwrote:

 Hi all,

 I'd like to use horizon to manage clusters in multiple data
 centers(regions).  Currently, horizon supports multi-region by means of
 deploying one keystone service for each region. Thus we have to manage
 multiple keystone services for all the regions(creating users or projects,
 etc.), which doesn't make sense. Should it be better to allow users to
 choose service endpoints(nova or glance) according to region name? At
 least, novaclient works as this way: you can provide region name(via
 --os_region_name option) as a filter to select nova service endpoint to
 access, so that we could deploy just one keystone service to manage
 services on different regions. Or is there any better workaround?

 Best Regards.

 Yufang

 ___
 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] RedHAt * OPenSTack

2012-08-14 Thread Andrew Clay Shafer

First you fill out that form, then you have to have a Redhat login, so
either make one or login, then you have to fill out another form, then you
get on a wait list, then you get an email that the subscription is active.
I received that email.

You can't do anything unless you have running Redhat licenses, even then
there isn't really any instructions in that path of forms and emails. (that
or they were not obvious and I totally missed them) You have to know Redhat
and how the subscriptions work.

The way it works now acts as a filter for existing RedHat customers more
than a generic install of OpenStack.


On Tue, Aug 14, 2012 at 3:16 PM, Joshua Harlow harlo...@yahoo-inc.comwrote:

 Are signups taking a while??

 Anyone else got the email yet, I think they lost mine, sad++

 On 8/14/12 11:57 AM, Frans Thamura fr...@meruvian.org wrote:

 hi all
 
 Redhat just post in his wall
 
 openstack..
 
 http://www.redhat.com/openstack/?sc_cid=7016000TmB8AAK
 
 
 --
 Frans Thamura (曽志胜)
 Shadow Master and Lead Investor
 Meruvian.
 Integrated Hypermedia Java Solution Provider.
 
 Mobile: +628557888699
 Blog: http://blogs.mervpolis.com/roller/flatburger (id)
 
 FB: http://www.facebook.com/meruvian
 TW: http://www.twitter.com/meruvian / @meruvian
 Website: http://www.meruvian.org
 
 We grow because we share the same belief.
 
 ___
 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] [Dashboard] Multi-region support in Horizon?

2012-08-14 Thread Gabriel Hurley

More than happy to discuss it! If we can do things to support it that don't 
rely on other projects (e.g. Keystone) all the better. Otherwise we should 
discuss it as a community and work together towards a federated federation 
solution. ;-)


-  Gabriel

From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net 
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On 
Behalf Of Matt Joyce
Sent: Tuesday, August 14, 2012 12:18 PM
To: Yufang Zhang
Cc: j...@ansolabs.com; openstack@lists.launchpad.net
Subject: Re: [Openstack] [Dashboard] Multi-region support in Horizon?

In the short term you might be able to setup something with a horizon 
customization module...

http://docs.openstack.org/developer/horizon/topics/customizing.html

In the long term I think federation should be a concern for grizzly planning in 
horizon.  But maybe I am just being a little too optimistic.

-Matt
On Tue, Aug 14, 2012 at 3:28 AM, Yufang Zhang 
yufang521...@gmail.commailto:yufang521...@gmail.com wrote:
Hi all,

I'd like to use horizon to manage clusters in multiple data centers(regions).  
Currently, horizon supports multi-region by means of deploying one keystone 
service for each region. Thus we have to manage multiple keystone services for 
all the regions(creating users or projects, etc.), which doesn't make sense. 
Should it be better to allow users to choose service endpoints(nova or glance) 
according to region name? At least, novaclient works as this way: you can 
provide region name(via --os_region_name option) as a filter to select nova 
service endpoint to access, so that we could deploy just one keystone service 
to manage services on different regions. Or is there any better workaround?

Best Regards.

Yufang

___
Mailing list: 
https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe : 
https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
More help   : https://help.launchpad.net/ListHelp

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

Re: [Openstack] [openstack] [horizon] Adding quota information to horizon.usage.base ?

2012-08-14 Thread Gabriel Hurley

Go for it. I assume this is related to 
https://bugs.launchpad.net/horizon/+bug/1018560 ?

If you need to add stuff feel free. Were you thinking the end result would be 
to display those bars on the overview screen for the project?


-  Gabriel

From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net 
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On 
Behalf Of Matt Joyce
Sent: Tuesday, August 14, 2012 12:24 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] [openstack] [horizon] Adding quota information to 
horizon.usage.base ?

Is anyone opposed to me adding quota information to usage.base.  ?

I'd like to add the graph bars from _launch_details_help.html to provide a 
quick heads up on where you are in terms of current allocation of resources 
against quotas.

Maybe later we can provide some graphing of deltas in resource use against 
quota.  In that, I don't know if we even track past quotas anywhere.  So I am 
going to avoid jumping into that any time soon.  Maybe that's a job for 
ceilometer.

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

Re: [Openstack] Setting Expectations

2012-08-14 Thread Dean Troyer

On Tue, Aug 14, 2012 at 1:06 PM, Andrew Clay Shafer
a...@parvuscaptus.com wrote:
 You say OpenStack has survived, but I believe we may have compounded and
 multiplied the challenges OpenStack faces by collectively neglecting to
 resolve this. Without going into all the technical necessity and political
 complexity, I would argue we allowed OpenStack fragmentation at the project
 level. Without a unified conscience of purpose, the fragmentation only gets
 magnified at the point users are interacting with different deployments.

This fragmentation with projects and goals is a real threat to the
long-term viability of OpenStack as a cloud standard.

 I don't believe that the kernel is a perfect analogy, but even if it was
 this one sentence 'OpenStack is like the Linux kernel' will not make it so.

Honestly, I HATE this analogy.  OpenStack has no BDFL, it has now a
foundation that is governed by Corporate interests that have a history
of working on common standards and tweaking them to add 'value'
('differentiation' I think is the buzzword for that).  The
organization of the foundation is partially designed to prevent any
one or two of these interests from pushing the whole in their
particular direction.  The foundation will have to prove itself
capable of pulling the projects forward. Together.

 What is the OpenStack equivalent of this?
 https://lkml.org/lkml/2012/3/8/495

The problem we have is that people in Linus' position are not created,
they grow and the position, respect and authority is earned.  The TC
may be able to earn some of that over time, but without unifying
leadership it will be tough going.  Hopefully their separation from
the rest of the board can give them a chance to provide the technical
leadership and direction needed even if it stubs a few toes along the
way.

It kills me that the acronym for OpenStack Foundation is OSF.  While I
don't think we can really be the Linux of the cloud any time soon, we
will have to really work to NOT be the UNIX of the cloud...

dt

-- 

Dean Troyer
dtro...@gmail.com

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

[Openstack] Installed OpenStack on Ubuntu but don't know how to incorporate XenServer

2012-08-14 Thread Landon Stewart

Hello,

I installed OpenStack using the guide at
http://stackgeek.com/guides/gettingstarted.html.  I'm stumped now though
because I can't figure out how to get it to connect to XenServer and setup
VMs.

I have a small test pool of two XenServers with shared NFS storage (it is
the default SR).  Each XenServer compute node has 3 NICs (1 x 100Mbps
Public IP for management of the actual HW nodes, 1 x  GigE Private IP for
File System and 1 x 100 Mbps trunking for VLAN).  VMs will be given IP
addresses from a VLAN on the third NIC in the end.  Incidentally my NFS
storage is GlusterFS accross 4 separate machines and can be scaled of
course.

I tried following what it said on
http://wiki.openstack.org/XenServer/PostInstall but nothing changed in
OpenStack.  I don't see XenServer listed in Services on the OpenStack UI or
anything else.

Does anyone know what I must do at this point or where to start with
documentation?  Ultimately the objective here is to create VMs in the pool
with shared storage using the default SR (a shared NFS storage).

Thanks for reading - any information is welcomed and appreciated.

-- 
Landon Stewart lstew...@superb.net
Sr. Administrator
Systems Engineering
Superb Internet Corp - 888-354-6128 x 4199
Web hosting and more Ahead of the Rest: http://www.superbhosting.net
___
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-14 Thread Kurt Scholtens

Any takers?

I am looking for guidance on my current deployment.   Let me start by
saying, it works.  That being said, I want to ensure what I am doing makes
sense because I'm slightly confused by the networking.  Specifically, the
bridging doesn't make sense at all.  If you look at my bridging below, it
appears both my public network (192.168.12.x) and my host to host management
network (10.0.5.x) are getting bridged on br100.  More precisely it appears
my FIXED_NETWORK (11.0.4.x) as well as my public network aka FLOATING_RANGE
are getting bridged to  br100.  I do access my openstack hosts on
192.168.12.x as well as my openstack instances on this network.  I just am
not understanding the networking for this set up, even though it works.

What would be considered best practices for this case?  Any help is
appreciated.

A few more details:
I am running a two-node installation under devstack on the essex branch.  I
don't want to overtly complicate things by saying its a virtual
installation, but I feel it's worth mentioning.  I've had to do some crafty
things to get KVM to play nicely with networking.  The eth0 interface is
pretty much unused below.

My cluster configuration node is configured as follows:

convirt@convirt-r01:~/devstack$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
address 10.0.5.2
netmask 255.255.255.0

auto eth2
iface eth2 inet static
address 192.168.12.104
netmask 255.255.255.0
gateway 192.168.12.1

convirt@convirt-r01:~/devstack$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
0.0.0.0 192.168.12.10.0.0.0 UG0 0  0
br100
10.0.4.00.0.0.0 255.255.255.0   U 0 0  0
eth0
10.0.5.00.0.0.0 255.255.255.0   U 0 0  0
eth1
11.0.4.00.0.0.0 255.255.255.0   U 0 0  0
br100
192.168.12.00.0.0.0 255.255.255.0   U 0 0  0
br100
192.168.122.0   0.0.0.0 255.255.255.0   U 0 0  0
virbr0

convirt@convirt-r01:~/devstack$ brctl show
bridge name bridge id STP enabled interfaces
br100 8000.00163e098238 no eth2
vnet0
virbr0 8000. yes

convirt@convirt-r01:~/devstack$ cat localrc
HOST_IP=192.168.12.104
SWIFT_REPLICAS=1
SWIFT_DATA_DIR=$DEST/data
# FORCE QEMU
CONNECTION_TYPE=libvirt
LIBVIRT_TYPE=qemu
FLOATING_RANGE=192.168.12.64/27
FIXED_RANGE=11.0.4.0/24
FIXED_NETWORK_SIZE=256
FLAT_INTERFACE=eth2
MULTI_HOST=1

My comp node is configured as follows:
HOST_IP=192.168.12.105
FLAT_INTERFACE=eth2
FIXED_RANGE=11.0.4.0/24
FIXED_NETWORK_SIZE=256
FLOATING_RANGE=192.168.12.64/27

# FORCE QEMU
CONNECTION_TYPE=libvirt
LIBVIRT_TYPE=qemu

MULTI_HOST=1
SERVICE_TOKEN=c0nv1rt
MYSQL_HOST=10.0.5.2
RABBIT_HOST=10.0.5.2
GLANCE_HOSTPORT=10.0.5.2:9292
ENABLED_SERVICES=n-cpu,n-net,n-api,n-vol

convirt@convirt-r02:~/devstack$ brctl show
bridge name bridge id STP enabled interfaces
br100 8000.00163e04fdd9 no eth2
vnet0
virbr0 8000. yes

convirt@convirt-r02:~/devstack$ cat /etc/network/interfaces
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
address 10.0.5.3
netmask 255.255.255.0

auto eth2
iface eth2 inet static
address 192.168.12.105
netmask 255.255.255.0
gateway 192.168.12.1

convirt@convirt-r02:~/devstack$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags   MSS Window  irtt
Iface
0.0.0.0 192.168.12.10.0.0.0 UG0 0  0
br100
10.0.4.00.0.0.0 255.255.255.0   U 0 0  0
eth0
10.0.5.00.0.0.0 255.255.255.0   U 0 0  0
eth1
11.0.4.00.0.0.0 255.255.255.0   U 0 0  0
br100
192.168.12.00.0.0.0 255.255.255.0   U 0 0  0
br100
192.168.122.0   0.0.0.0 255.255.255.0   U 0 0  0
virbr0


___
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] * Review required * general-bare-metal-provisioning-framework

2012-08-14 Thread Mikyung Kang

Hi All,

[REMINDER] Please review *general-bare-metal-provisioning-framework* (Folsom 
Release).

- REVIEW SYSTEM (w/ dependencies among patch sets)

 (1) Added separate bare-metal MySQL DB: https://review.openstack.org/10726

 (2) Added bare-metal documents: https://review.openstack.org/11088

 (3) Updated bare-metal provisioning framework: 
https://review.openstack.org/11354

 (4) Added bare-metal host manager: https://review.openstack.org/11357

 (5) Scripts for bare-metal node management: 
https://review.openstack.org/#/c/11366/

- BLUEPRINT

 
https://blueprints.launchpad.net/nova/+spec/general-bare-metal-provisioning-framework

- WIKI

 http://wiki.openstack.org/GeneralBareMetalProvisioningFramework

Thanks  Regards,
Mikyung

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

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

I get what you are saying.  And for the sake of compatibility with other
clouds and their images obviously that's the way to go, but my inner nerd
is screaming Well, about that...  and wanting me to rally people to the
idea of putting the logic inside the images rather than inside of the
cloud.   Let init negotiate the api access and produce the filesystems it
needs to get booted up properly.

=/  first world problems.

On Tue, Aug 14, 2012 at 12:06 PM, Eric Windisch e...@cloudscaling.comwrote:

 On Tuesday, August 14, 2012 at 14:30 PM, Matt Joyce wrote:

 I have to ask.  Wasn't FUSE designed to do alot of this stuff?  It is
 userspace and it doesn't do nasty stuff to file systems.  Why aren't we
 going that route?

 Fuse was really designed for the opposite scenario. Fuse modules run as
 daemons, they're not libraries.  These daemons attach to a character device
 and map userspace code into the VFS.  Instead, we want to access a
 filesystem from userspace code.  It is a shame, however, because you're
 right… there is plenty of code there that knows how to read filesystems in
 userspace.  Unfortunately, the FUSE design really doesn't do us any favors.

 That said, there are some crazy options to fix that. One could
 theoretically replace the FUSE character device with one that spoke to
 userspace processes, instead of interacting with the VFS.  There has even
 been work into creating user-space character devices.  One could also make
 FUSE work with Unix sockets as an alternative to character devices…

 None of this is out of the box, tested, or even in existence...

 Regards,
 Eric Windisch



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

Re: [Openstack] Setting Expectations

+1 to everything dean said.

On Tue, Aug 14, 2012 at 12:58 PM, Dean Troyer dtro...@gmail.com wrote:

 On Tue, Aug 14, 2012 at 1:06 PM, Andrew Clay Shafer
 a...@parvuscaptus.com wrote:
  You say OpenStack has survived, but I believe we may have compounded and
  multiplied the challenges OpenStack faces by collectively neglecting to
  resolve this. Without going into all the technical necessity and
 political
  complexity, I would argue we allowed OpenStack fragmentation at the
 project
  level. Without a unified conscience of purpose, the fragmentation only
 gets
  magnified at the point users are interacting with different deployments.

 This fragmentation with projects and goals is a real threat to the
 long-term viability of OpenStack as a cloud standard.

  I don't believe that the kernel is a perfect analogy, but even if it was
  this one sentence 'OpenStack is like the Linux kernel' will not make it
 so.

 Honestly, I HATE this analogy.  OpenStack has no BDFL, it has now a
 foundation that is governed by Corporate interests that have a history
 of working on common standards and tweaking them to add 'value'
 ('differentiation' I think is the buzzword for that).  The
 organization of the foundation is partially designed to prevent any
 one or two of these interests from pushing the whole in their
 particular direction.  The foundation will have to prove itself
 capable of pulling the projects forward. Together.

  What is the OpenStack equivalent of this?
  https://lkml.org/lkml/2012/3/8/495

 The problem we have is that people in Linus' position are not created,
 they grow and the position, respect and authority is earned.  The TC
 may be able to earn some of that over time, but without unifying
 leadership it will be tough going.  Hopefully their separation from
 the rest of the board can give them a chance to provide the technical
 leadership and direction needed even if it stubs a few toes along the
 way.

 It kills me that the acronym for OpenStack Foundation is OSF.  While I
 don't think we can really be the Linux of the cloud any time soon, we
 will have to really work to NOT be the UNIX of the cloud...

 dt

 --

 Dean Troyer
 dtro...@gmail.com

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

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

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

2012-08-14 Thread Daniel P. Berrange

On Tue, Aug 14, 2012 at 11:30:29AM -0700, Matt Joyce wrote:
 I have to ask.  Wasn't FUSE designed to do alot of this stuff?  It is
 userspace and it doesn't do nasty stuff to file systems.  Why aren't we
 going that route?

If you read earlier in this thread, you'll see that FUSE is what Nova
already uses, and is why we have this CVE.  From a non-security POV,
FUSE is actually quite inefficient since its operations have to map
strictly to POSIX compliant filesystem APIs. Using the libguestfs API
directly gives you better performance and more flexible APIs for
accomplishing many tasks.

Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

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

Re: [Openstack] [openstack] [horizon] Adding quota information to horizon.usage.base ?

Yeah I was going to grab the code from the instance launch helper template
and just fill in the variables from usage.base rather than usages.

I think that's quick and easy.  I just a quick test, and I think it should
work fine.

-Matt

On Tue, Aug 14, 2012 at 12:52 PM, Gabriel Hurley
gabriel.hur...@nebula.comwrote:

  Go for it. I assume this is related to
 https://bugs.launchpad.net/horizon/+bug/1018560 ?

 ** **

 If you need to add stuff feel free. Were you thinking the end result would
 be to display those bars on the overview screen for the project?

 ** **

 **-  **Gabriel

 ** **

 *From:* 
 openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
 openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
 Behalf Of *Matt Joyce
 *Sent:* Tuesday, August 14, 2012 12:24 PM
 *To:* openstack@lists.launchpad.net
 *Subject:* [Openstack] [openstack] [horizon] Adding quota information to
 horizon.usage.base ?

 ** **

 Is anyone opposed to me adding quota information to usage.base.  ?

 I'd like to add the graph bars from _launch_details_help.html to provide a
 quick heads up on where you are in terms of current allocation of resources
 against quotas.

 Maybe later we can provide some graphing of deltas in resource use against
 quota.  In that, I don't know if we even track past quotas anywhere.  So I
 am going to avoid jumping into that any time soon.  Maybe that's a job for
 ceilometer.

 -Matt

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

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

2012-08-14 Thread Eric Windisch




On Tuesday, August 14, 2012 at 16:41 PM, Matt Joyce wrote:

 I get what you are saying.  And for the sake of compatibility with other 
 clouds and their images obviously that's the way to go, but my inner nerd is 
 screaming Well, about that...  and wanting me to rally people to the idea 
 of putting the logic inside the images rather than inside of the cloud.   Let 
 init negotiate the api access and produce the filesystems it needs to get 
 booted up properly.  
 
Are we having the same conversation? :-)  You were arguing for FUSE, I simply 
said that particular user-space solution isn't very viable due.  Otherwise, I 
believe you and I agree.

I agree that the the approach being taken here isn't ideal. However, I also 
advocate that if this path is going to be traveled, it should be done in the 
safest way possible - in userspace, and write-once-read-never, if at all 
possible.  However, I'm not too confident of libguestfs, but I understand why 
it is attractive in absence of good userspace filesystem tools.  Several have 
pointed to mtools as one, and I'll also add debug2fs to this list, for those of 
strong conviction.

Regards,
Eric Windisch




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

Re: [Openstack] [OSSA 2012-011] Compute node filesystem injection/corruption (CVE-2012-3447)

2012-08-14 Thread Richard W.M. Jones

On Tue, Aug 14, 2012 at 11:30:29AM -0700, Matt Joyce wrote:
I have to ask. Wasn't FUSE designed to do alot of this stuff? It is
userspace and it doesn't do nasty stuff to file systems. Why aren't we
going that route?

FUSE is not really related to this issue. It's just the API.

You can use libguestfs over FUSE. Indeed that's how OpenStack works
right now, albeit using the external 'guestmount' program, whereas
with libguestfs = 1.18 you'll be able to use the much cleaner
'mount-local' core API.

http://libguestfs.org/guestmount.1.html
http://libguestfs.org/guestfs.3.html#mount-local

The issue is what thing, underneath the API, is actually accessing the
filesystem. If you're mounting stuff directly on the host, then that
thing is the host kernel, which is really the worst scenario from a
security p.o.v.

If (as some have suggested) you're using a userspace program on the
host, then you've got a userspace program which can be exploited that
then has direct access to the host.

With libguestfs, accessed either via the libguestfs native API or over
FUSE, you've got the regular qemu/KVM process buffering you from any
exploits. In essence, this is the same situation as when you're
running any VM, so it's just as safe (or unsafe) as Nova is already.

http://libguestfs.org/guestfs.3.html#architecture
http://libguestfs.org/guestfs.3.html#api-overview
http://libguestfs.org/guestfs.3.html#security

With libguestfs *and* libvirt (in libguestfs = 1.19.25), you've got
not just the qemu wrapper, but also SELinux controlling exactly what
the qemu process can see and do in the host, ie. sVirt.

http://selinuxproject.org/page/SVirt

https://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-sVirt.html

Rich.

--
Richard Jones
Red Hat

___
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-14 Thread Dan Wendlandt

On Tue, Aug 14, 2012 at 1:54 AM, Thierry Carrez thie...@openstack.orgwrote:

 Dan Wendlandt wrote:
  On Mon, Aug 13, 2012 at 12:51 PM, Vishvananda Ishaya
  vishvana...@gmail.com mailto:vishvana...@gmail.com wrote:
 
  This is up to dan, I suppose, but the rootwrap stuff seems like
  something worth granting a ffe to…
 
 
  I wasn't going to mention it, as the urgency of a nearby deadline can be
  helpful :)
 
  But yes, I'd grant an ffe to something this important, especially
  because it applies across all uses of quantum.

 On one hand it's a change that impacts almost all use cases, so
 definitely not something that is simple or self-contained. On the other,
 it's quite easy to trace back issues to this. In summary, if it's the
 only exception in Quantum, it's not really a problem :)

 [warning: a trick is included in the last paragraph]


ttx, I caught it I'm on to your project management jedi mind tricks :)

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.

dan



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




-- 
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Quantum] Removing quantum-rootwrap

2012-08-14 Thread jrd

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

On Tue, Aug 14, 2012 at 1:54 AM, Thierry Carrez thie...@openstack.org 
 wrote:

Dan Wendlandt wrote:
 On Mon, Aug 13, 2012 at 12:51 PM, Vishvananda Ishaya
 vishvana...@gmail.com mailto:vishvana...@gmail.com wrote:

     This is up to dan, I suppose, but the rootwrap stuff seems like
     something worth granting a ffe to…

 I wasn't going to mention it, as the urgency of a nearby deadline 
 can be
 helpful :)

 But yes, I'd grant an ffe to something this important, especially
 because it applies across all uses of quantum.

On one hand it's a change that impacts almost all use cases, so
definitely not something that is simple or self-contained. On the 
 other,
it's quite easy to trace back issues to this. In summary, if it's the
only exception in Quantum, it's not really a problem :)

[warning: a trick is included in the last paragraph]

ttx, I caught it I'm on to your project management jedi mind tricks :) 

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.  

I apologise that this is taking longer than I hoped.  I'm still
spending more time on learning curve than getting real productive
stuff done.  I suppose some of that's to be expected, but still.

I spent most of today getting my test env up to snuff, getting more
unit test infra written, and then trying to work out how to debug the
unit tests.  My python-debugging techniques are rusty, so I have to
feel my way through.

I'll work with the local RH contingent tomorrow.  If I can get my new
unit tests to behave, I *hope* to be able to run the rest of the suite
through in relatively short time.  cross fingers  If you (Dan and
ttx) start feeling like we're just too tight, please say so, and we'll
work out plan B.  Until then, I'm going to keep banging on this to
pull it together.

___
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] multi_host sample nova.conf files?

2012-08-14 Thread Lorin Hochstein


On Jul 6, 2012, at 6:46 AM, Marnus van Niekerk m...@mjvn.net wrote:

 Hi, is anybody prepared to share a set of working nova.conf files for a 
 multi_host installation?
 For both the controller node and a compute node.  And please tell me what 
 services you are running on the compute node.
 
 I have been over this 100s of times now and even recreated the nova database 
 and no success.


Marnus:

You need multi_host=True in your nova.conf, and you need to run the following 
services on the compute node:

nova-compute
nova-network
nova-api-metadata

See: 
http://docs.openstack.org/essex/openstack-compute/admin/content/existing-ha-networking-options.html#d6e6509



Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com


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

Re: [Openstack] multi_host sample nova.conf files?

2012-08-14 Thread Shake Chen

http://www.chenshake.com/wp-content/uploads/2012/07/openstack_config.zip

it is my config. hope can help you.

mutilhost=true flatdhcp



On Fri, Jul 6, 2012 at 6:46 PM, Marnus van Niekerk m...@mjvn.net wrote:

  Hi, is anybody prepared to share a set of working nova.conf files for a
 multi_host installation?
 For both the controller node and a compute node.  And please tell me what
 services you are running on the compute node.

 I have been over this 100s of times now and even recreated the nova
 database and no success.

 Tx

 Marnus

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




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

Re: [Openstack] inter-tenant and VM-to-bare-metal communication policies/restrictions.

2012-08-14 Thread Lorin Hochstein

On Jul 5, 2012, at 11:47 AM, Christian Parpart tra...@gmail.com wrote:

 Hi all,
 
 I am running multiple compute nodes and a single nova-network node, that is 
 to act
 as a central gateway for the tenant's VMs.
 
 However, since this nova-network node (of course) knows all routes, every VM 
 of
 any tenant can talk to each other, including to the physical nodes, which
 I highly disagree with and would like to restrict that. :-)
 

If you add this to nova.conf:

allow_same_net_traffic=false

It should prevent the VMs from communicating with each other. From 

http://docs.openstack.org/essex/openstack-compute/admin/content/compute-options-reference.html#d6e3133


Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com


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

Re: [Openstack] [Swift] Where do we go from here?

2012-08-14 Thread 朱荣泽

It is cool!

2012/8/15 John Dickinson m...@not.mn

 Swift has many exciting features coming in the OpenStack Folsom
 Release this fall, but where do we go from here? What's next for Swift
 in grizzly?

 I've got some ideas. I'd like to mention them and see where you the
 community will take them. I've written up most of them into quick one-
 line blueprints in Launchpad. If you'd like to contribute, grab the
 blueprint and jump in.

 - Optimize the many small writes workload. Swift actually handles
   many small concurrent writes very well. However, many small writes
   generally also implies that the cardinality of a single container
   gets very large. There are two ways this use case can be improved:

 - Implement transparent container sharding
   https://blueprints.launchpad.net/swift/+spec/container-sharding

 - Provide better listing traversal abstractions. Listing a few
   billion objects ten thousand at a time is somewhat impractical.

 - Solve globally distributed clusters. How can I have servers in
   London and servers in San Jose in the same logical swift cluster
   with three replicas total, but guaranteed to have at least one
   replica in each cluster?
   https://blueprints.launchpad.net/swift/+spec/multi-region

 - Support a single logical swift cluster with tiers of storage (eg
   cheap spinning disks and expensive high IOPS SSD arrays). Can, for
   example, a user choose to have a container and its objects be served
   from a particular tier of storage?
   https://blueprints.launchpad.net/swift/+spec/storage-tiers

 - Some deployers have implemented metadata searching by intercepting
   write requests and sending the metadata to another system. Can
   metadata searching be implemented in swift itself? One possible
   implementation would be to dynamically generate indexes on the
   container DB.
   https://blueprints.launchpad.net/swift/+spec/searchable-metadata

 - Support PUTs with unlimited size. Implement server-side large object
   splitting.
   https://blueprints.launchpad.net/swift/+spec/large-single-uploads

 - Support the full HTTP spec for range requests
   https://blueprints.launchpad.net/swift/+spec/multi-range-support

 - There are a few things that could be done to simplify installation

 - Create or refactor existing code into a single swift binary or
   startup script. Would it be possible, for example, to install
   swift and run one command with the data drives listed and swift
   just works?

 - Build a ring server that automatically discovers devices
   https://blueprints.launchpad.net/swift/+spec/ring-builder-server

 - Provide a simple, intuitive way to test a deployment after install
   https://blueprints.launchpad.net/swift/+spec/post-deploy-test

 - Support concurrent reads to objects to support a read-heavy workload
   https://blueprints.launchpad.net/swift/+spec/concurrent-reads

 If you are in the San Francisco area, we will have a swift meetup on
 August 30 at Citizen Space SF at 6:30 pm.
 http://www.meetup.com/openstack/events/77706042/

 We will have a swift team meeting on Monday October 1 in
 #openstack-meeting at 8pm UTC to discuss the plans for swift over the
 next six months and the sessions for the design summit. If you are
 interested in participating in swift development, please attend.

 If you are a new contributor to swift, please read
 http://wiki.openstack.org/HowToContribute.

 --John


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


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

Re: [Openstack] [nova] Disk attachment consistency

2012-08-14 Thread Wangpan

How about using the pci address as the UUID of target devices in one VM?
the pci address is generated by libvirt and we can see it in VM by cmd ls -la 
/sys/block/,
and it has no dependency with the kernel version, I can see it in 2.6.32*
when an user attached a disk to VM, we find a free target dev such as vdd(the 
user doesn't need to assign one) to attach and return the pci address to user,
the disk is consistent when user see it on horizon and in VM(by cmd ls -la 
/sys/block/).

libvirt:address type='pci' domain='0x' bus='0x00' slot='0x04' 
function='0x0'/
ls -la /sys/block/:vda - ../devices/pci-:00/:00:04.0/virtio1/block/vda

Hey Everyone, 

Overview 
 

One of the things that we are striving for in nova is interface consistency, 
that is, we'd like someone to be able to use an openstack cloud without 
knowing or caring which hypervisor is running underneath. There is a nasty bit 
of inconsistency in the way that disks are hot attached to vms that shows 
through to the user. I've been debating ways to minimize this and I have some 
issues I need feedback on. 

Background 
-- 

There are three issues contributing to the bad user experience of attaching 
volumes. 

1) The api we present for attaching a volume to an instance has a parameter 
called device. This is presented as where to attach the disk in the guest. 

2) Xen picks minor device numbers on the host hypervisor side and the guest 
driver follows instructions 

3) KVM picks minor device numbers on the guest driver side and doesn't expose 
them to the host hypervisor side 

Resulting Issues 
 

a) The device name only makes sense for linux. FreeBSD will select different 
device names, and windows doesn't even use device names. In addition xen uses 
/dev/xvda and kvm uses /dev/vda 

b) The device sent in kvm will not match where it actually shows up. We can 
consistently guess where it will show up if the guest kernel is = 3.2, 
otherwise we are likely to be wrong, and it may change on a reboot anyway 


Long term solutions 
-- 

We probably shouldn't expose a device path, it should be a device number. This 
is probably the right change long term, but short term we need to make the 
device name make sense somehow. I want to delay the long term until after the 
summit, and come up with something that works short-term with our existing 
parameters and usage. 

The first proposal I have is to make the device parameter optional. The system 
will automatically generate a valid device name that will be accurate for xen 
and kvm with guest kernel 3.2, but will likely be wrong for old kvm guests in 
some situations. I think this is definitely an improvement and only a very 
minor change to an extension api (making a parameter optional, and returning 
the generated value of the parameter). 

(review at https://review.openstack.org/#/c/10908/) 

The second proposal I have is to use a feature of kvm attach and set the 
device serial number. We can set it to the same value as the device parameter. 
This means that a device attached to /dev/vdb may not always be at /dev/vdb 
(with old kvm guests), but it will at least show up at 
/dev/disk/by-id/virtio-vdb consistently. 

(review coming soon) 

First question: should we return this magic path somewhere via the api? It 
would be pretty easy to have horizon generate it but it might be nice to have 
it show up. If we do return it, do we mangle the device to always show the 
consistent one, or do we return it as another parameter? guest_device perhaps? 

Second question: what should happen if someone specifies /dev/xvda against a 
kvm cloud or /dev/vda against a xen cloud? 
I see two options: 
a) automatically convert it to the right value and return it 
b) fail with an error message 

Third question: what do we do if someone specifies a device value to a kvm 
cloud that we know will not work. For example the vm has /dev/vda and /dev/vdb 
and they request an attach at /dev/vdf. In this case we know that it will 
likely show up at /dev/vdc. I see a few options here and none of them are 
amazing: 

a) let the attach go through as is. 
  advantages: it will allow scripts to work without having to manually find 
 the next device. 
  disadvantages: the device name will never be correct in the guest 
b) automatically modify the request to attach at /dev/vdc and return it 
  advantages: the device name will be correct some of the time (kvm guests 
 with newer kernels) 
  disadvantages: sometimes the name is wrong anyway. The user may not expect 
 the device number to change 
c) fail and say, the next disk must be attached at /dev/vdc: 
  advantages: explicit 
  disadvantages: painful, incompatible, and the place we say to attach may be 
 incorrect anyway (kvm guests with old kernels) 

The second proposal earlier will at least give us a consistent name to find 
the volume in all these cases, although b) means we have to check the return 
value to find out

Re: [Openstack] Devstack multinode Installation network configuration help and bridging explanation

2012-08-14 Thread Vishvananda Ishaya


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

 Any takers?
 
 I am looking for guidance on my current deployment.   Let me start by saying, 
 it works.  That being said, I want to ensure what I am doing makes sense 
 because I'm slightly confused by the networking.  Specifically, the bridging 
 doesn't make sense at all.  If you look at my bridging below, it appears both 
 my public network (192.168.12.x) and my host to host management network 
 (10.0.5.x) are getting bridged on br100.  More precisely it appears my 
 FIXED_NETWORK (11.0.4.x) as well as my public network aka FLOATING_RANGE are 
 getting bridged to  br100.  I do access my openstack hosts on 192.168.12.x as 
 well as my openstack instances on this network.  I just am not understanding 
 the networking for this set up, even though it works.  

If you want the floating ips on a different interface (say eth1) you can use:

PUBLIC_INTERFACE=eth1

devstack defaults PUBLIC_INTERFACE to br100 because that is the only way to 
make it work if you have a single interface and you don't set up vlans. with 
multiple interfaces and vlans, generally you put public_interface and 
flat_interface on different devices.

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

Re: [Openstack] [nova] Disk attachment consistency

2012-08-14 Thread Vishvananda Ishaya


On Aug 14, 2012, at 7:55 PM, Wangpanhzwang...@corp.netease.com wrote:

 How about using the pci address as the UUID of target devices in one VM?
 the pci address is generated by libvirt and we can see it in VM by cmd ls 
 -la /sys/block/,
 and it has no dependency with the kernel version, I can see it in 2.6.32*
 when an user attached a disk to VM, we find a free target dev such as vdd(the 
 user doesn't need to assign one) to attach and return the pci address to user,
 the disk is consistent when user see it on horizon and in VM(by cmd ls -la 
 /sys/block/).
  
 libvirt:address type='pci' domain='0x' bus='0x00' slot='0x04' 
 function='0x0'/
 ls -la /sys/block/:vda - 
 ../devices/pci-:00/:00:04.0/virtio1/block/vda

This is definitely another solution, although it seems less usable than the 
device serial number which can be an arbitrary string. If this works for xen 
though, that would be a plus.

Vish

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

Re: [Openstack] [nova] Disk attachment consistency

2012-08-14 Thread Wangpan


 This is definitely another solution, although it seems less usable than the 
 device serial number which can be an arbitrary string. If this works for xen 
 though, that would be a plus.


 Vish

I don't have a Xen hypervisor in hand, so anybody else can try it on Xen ? 
thanks___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [openstack-dev] [nova] Disk attachment consistency

2012-08-14 Thread Chuck Thier

Hey Vish,

First, thanks for bringing this up for discussion.  Coincidentally a
similar discussion had come up with our teams, but I had pushed it
aside at the time due to time constraints.  It is a tricky problem to
solve generally for all hypervisors.  See my comments inline:

On Mon, Aug 13, 2012 at 10:35 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:


 Long term solutions
 --

 We probably shouldn't expose a device path, it should be a device number. 
 This is probably the right change long term, but short term we need to make 
 the device name make sense somehow. I want to delay the long term until after 
 the summit, and come up with something that works short-term with our 
 existing parameters and usage.

I totally agree with delaying the long term discussion, and look
forward to discussing these types of issues more at the summit.


 The first proposal I have is to make the device parameter optional. The 
 system will automatically generate a valid device name that will be accurate 
 for xen and kvm with guest kernel 3.2, but will likely be wrong for old kvm 
 guests in some situations. I think this is definitely an improvement and only 
 a very minor change to an extension api (making a parameter optional, and 
 returning the generated value of the parameter).

I could get behind this, and was was brought up by others in our group
as a more feasible short term solution.  I have a couple of concerns
with this.  It may cause just as much confusion if the api can't
reliably determine which device a volume is attached to.  I'm also
curious as to how well this will work with Xen, and hope some of the
citrix folks will chime in.  From an api standpoint, I think it would
be fine to make it optional, as any client that is using old api
contract will still work as intended.


 (review at https://review.openstack.org/#/c/10908/)

 The second proposal I have is to use a feature of kvm attach and set the 
 device serial number. We can set it to the same value as the device 
 parameter. This means that a device attached to /dev/vdb may not always be at 
 /dev/vdb (with old kvm guests), but it will at least show up at 
 /dev/disk/by-id/virtio-vdb consistently.

 (review coming soon)

 First question: should we return this magic path somewhere via the api? It 
 would be pretty easy to have horizon generate it but it might be nice to have 
 it show up. If we do return it, do we mangle the device to always show the 
 consistent one, or do we return it as another parameter? guest_device perhaps?

 Second question: what should happen if someone specifies /dev/xvda against a 
 kvm cloud or /dev/vda against a xen cloud?
 I see two options:
 a) automatically convert it to the right value and return it

I thought that it already did this, but I would have to go back and
double check.  But it seemed like for xen at least, if you specify
/dev/vda, Nova would change it to /dev/xvda.

 b) fail with an error message


I don't have a strong opinion either way, as long as it is documented
correctly.  I would suggest thought that if it has been converting it
in the past, that we continue to do so.

 Third question: what do we do if someone specifies a device value to a kvm 
 cloud that we know will not work. For example the vm has /dev/vda and 
 /dev/vdb and they request an attach at /dev/vdf. In this case we know that it 
 will likely show up at /dev/vdc. I see a few options here and none of them 
 are amazing:

 a) let the attach go through as is.
   advantages: it will allow scripts to work without having to manually find 
 the next device.
   disadvantages: the device name will never be correct in the guest
 b) automatically modify the request to attach at /dev/vdc and return it
   advantages: the device name will be correct some of the time (kvm guests 
 with newer kernels)
   disadvantages: sometimes the name is wrong anyway. The user may not expect 
 the device number to change
 c) fail and say, the next disk must be attached at /dev/vdc:
   advantages: explicit
   disadvantages: painful, incompatible, and the place we say to attach may be 
 incorrect anyway (kvm guests with old kernels)

I would choose b, as it tries to get things in the correct state.  c
is a bad idea as it would change the overall api behavior, and current
clients wouldn't expect it.

There are also a couple of other interesting tidbits, that may be
related, or at least be worthwhile to know while discussing this.

Xen Server 6.0 has a limit of 16 virtual devices per guest instance.
Experimentally it also expects those to be /dev/xvda - /dev/xvdp.  You
can't for example attach a device to /dev/xvdq, even if there are no
other devices attached to the instance.  If you attempt to do this,
the volume will go in to the attaching state, fail to attach, and then
fall back to the available state (This can be a bit confusing to new
users who try to do so).  Does anyone know if there are similar
limitations for KVM?

Also if you attempt

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_essex_horizon_stable #18

Title: precise_essex_horizon_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/18/Project:precise_essex_horizon_stableDate of build:Tue, 14 Aug 2012 04:01:59 -0400Build duration:2 min 32 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesFixed validation check for ICMP rulesby cthieledithorizon/tests/test_data/nova_data.pyedithorizon/dashboards/nova/access_and_security/security_groups/tests.pyedithorizon/static/horizon/js/forms.jseditopenstack_dashboard/static/dashboard/css/style.cssedithorizon/dashboards/nova/access_and_security/security_groups/forms.pyConsole Output[...truncated 1665 lines...]Looking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmp8CgbEAbzr: ERROR: An error (1) occurred running quilt: Applying patch fix-dashboard-django-wsgi.patchpatching file openstack_dashboard/wsgi/django.wsgiApplying patch fix-dashboard-manage.patchpatching file manage.pyApplying patch fix-coverage-binary-name.patchpatching file run_tests.shHunk #1 FAILED at 271.1 out of 1 hunk FAILED -- rejects in file run_tests.shPatch fix-coverage-binary-name.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-fb28ceb9-877a-4c2c-a2ff-5230535891d6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-fb28ceb9-877a-4c2c-a2ff-5230535891d6', '-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/horizon/precise-essex-proposed /tmp/tmp8CgbEA/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmp8CgbEA/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log b0d6f54d79ff1c200b5988e2bbd4fbb0b189029f..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/horizon/precise-essex-stable --forcedch -b -D precise --newversion 2012.1.2+git201208140402~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.1.2+git201208140402~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-fb28ceb9-877a-4c2c-a2ff-5230535891d6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'precise-amd64-fb28ceb9-877a-4c2c-a2ff-5230535891d6', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/383/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 04:01:59 -0400Build duration:6 min 54 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesChange time.sleep to greenthread.sleepby yunmaoeditnova/virt/libvirt/driver.pyConsole Output[...truncated 5450 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10337.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/tmpuK8Lc5/novamk-build-deps -i -r -t apt-get -y /tmp/tmpuK8Lc5/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208140405~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208140405~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_essex_horizon_stable #19

Title: precise_essex_horizon_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/19/Project:precise_essex_horizon_stableDate of build:Tue, 14 Aug 2012 04:31:53 -0400Build duration:3 min 27 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesBump version to 2012.1.3by markmcedithorizon/version.pyConsole Output[...truncated 1561 lines...]hard linking openstack_dashboard/static/dashboard/img/spinner.gif -> horizon-2012.1.3/openstack_dashboard/static/dashboard/imghard linking openstack_dashboard/static/qunit/qunit.css -> horizon-2012.1.3/openstack_dashboard/static/qunithard linking openstack_dashboard/static/qunit/qunit.js -> horizon-2012.1.3/openstack_dashboard/static/qunithard linking openstack_dashboard/templates/403.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/404.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/500.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/_footer.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/_header.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/_scripts.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/_stylesheets.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/base.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/qunit.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/splash.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/templates/switch_tenants.html -> horizon-2012.1.3/openstack_dashboard/templateshard linking openstack_dashboard/wsgi/django.wsgi -> horizon-2012.1.3/openstack_dashboard/wsgihard linking tools/install_venv.py -> horizon-2012.1.3/toolshard linking tools/pip-requires -> horizon-2012.1.3/toolshard linking tools/rfc.sh -> horizon-2012.1.3/toolshard linking tools/test-requires -> horizon-2012.1.3/toolshard linking tools/with_venv.sh -> horizon-2012.1.3/toolsWriting horizon-2012.1.3/setup.cfgcreating distCreating tar archiveremoving 'horizon-2012.1.3' (and everything under it)ERROR:root:Error occurred during package creation/build: [Errno 2] No such file or directory: '/tmp/tmpMWalYh/git/horizon/dist/horizon-2012.1.2.tar.gz'ERROR:root:[Errno 2] No such file or directory: '/tmp/tmpMWalYh/git/horizon/dist/horizon-2012.1.2.tar.gz'INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/precise-essex-proposed /tmp/tmpMWalYh/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmpMWalYh/horizon/debian/controlpython setup.py sdistTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpMWalYh/git/horizon/dist/horizon-2012.1.2.tar.gz'Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise eIOError: [Errno 2] No such file or directory: '/tmp/tmpMWalYh/git/horizon/dist/horizon-2012.1.2.tar.gz'Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Failure: quantal_folsom_quantum_trunk #99

Title: quantal_folsom_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_quantum_trunk/99/Project:quantal_folsom_quantum_trunkDate of build:Tue, 14 Aug 2012 08:31:53 -0400Build duration:3 min 22 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesUpdates pip requirementsby gkottonedittools/pip-requiresConsole Output[...truncated 513 lines...]Hit http://archive.ubuntu.com quantal-updates/multiverse SourcesHit http://archive.ubuntu.com quantal-updates/main amd64 PackagesHit http://archive.ubuntu.com quantal-updates/restricted amd64 PackagesHit http://archive.ubuntu.com quantal-updates/universe amd64 PackagesHit http://archive.ubuntu.com quantal-updates/multiverse amd64 PackagesHit http://archive.ubuntu.com quantal-updates/main i386 PackagesHit http://archive.ubuntu.com quantal-updates/restricted i386 PackagesHit http://archive.ubuntu.com quantal-updates/universe i386 PackagesHit http://archive.ubuntu.com quantal-updates/multiverse i386 PackagesHit http://archive.ubuntu.com quantal-updates/main Translation-enHit http://archive.ubuntu.com quantal-updates/multiverse Translation-enHit http://archive.ubuntu.com quantal-updates/restricted Translation-enHit http://archive.ubuntu.com quantal-updates/universe Translation-enFetched 23.6 MB in 2min 32s (155 kB/s)W: Failed to fetch bzip2:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_quantal_universe_binary-i386_Packages  Hash Sum mismatchE: Some index files failed to download. They have been ignored, or old ones used instead.ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-a5e763da-1c1f-476c-9dc1-04163e0ff42a', '-u', 'root', '--', 'apt-get', 'update']' returned non-zero exit status 100ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-a5e763da-1c1f-476c-9dc1-04163e0ff42a', '-u', 'root', '--', 'apt-get', 'update']' returned non-zero exit status 100INFO:root:Complete command log:INFO:root:Destroying schroot.git archive master --format tar --prefix quantum-2012.2-201208140832/git archive master --format tar --prefix quantum-2012.2-201208140832/git log -n1 --no-merges --pretty=format:%Hgit log ce1638c283f894547fee7ccc83c66a54aa502c7e..HEAD --no-merges --pretty=format:[%h] %sbzr branch lp:~openstack-ubuntu-testing/quantum/quantal-folsom-proposed quantumbzr merge lp:~openstack-ubuntu-testing/quantum/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208140832~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208140832~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-a5e763da-1c1f-476c-9dc1-04163e0ff42a', '-u', 'root', '--', 'apt-get', 'update']' returned non-zero exit status 100Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-a5e763da-1c1f-476c-9dc1-04163e0ff42a', '-u', 'root', '--', 'apt-get', 'update']' returned non-zero exit status 100Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_cinder_trunk #42

Title: quantal_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/42/Project:quantal_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 09:31:53 -0400Build duration:2 min 55 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdds new volume API extensionsby unmesh.gurjareditcinder/tests/policy.jsoneditcinder/tests/api/openstack/volume/test_volumes.pyeditcinder/utils.pyaddcinder/tests/image/__init__.pyeditcinder/api/openstack/__init__.pyeditcinder/api/openstack/extensions.pyeditcinder/flags.pyaddcinder/api/openstack/volume/contrib/image_create.pyeditcinder/tests/api/openstack/fakes.pyeditcinder/api/openstack/volume/contrib/volume_actions.pyeditcinder/api/openstack/volume/volumes.pyeditcinder/api/openstack/volume/__init__.pyaddcinder/image/glance.pyaddcinder/image/__init__.pyeditcinder/volume/driver.pyeditcinder/tests/api/openstack/volume/contrib/test_volume_actions.pyeditcinder/volume/manager.pyeditcinder/tests/test_volume.pyeditcinder/tests/api/openstack/volume/test_router.pyaddcinder/tests/image/fake.pyeditetc/cinder/rootwrap.d/volume.filterseditcinder/volume/api.pyConsole Output[...truncated 1843 lines...]Looking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmpxxoMosbzr: ERROR: An error (1) occurred running quilt: Applying patch 0001-Use-setuptools-git.patchpatching file MANIFEST.inHunk #1 FAILED at 1.1 out of 1 hunk FAILED -- rejects in file MANIFEST.inpatching file setup.pyHunk #1 FAILED at 31.1 out of 1 hunk FAILED -- rejects in file setup.pypatching file tools/test-requiresHunk #1 FAILED at 9.1 out of 1 hunk FAILED -- rejects in file tools/test-requiresPatch 0001-Use-setuptools-git.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8ece7b22-6986-4fe0-b316-5700ec3233a8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8ece7b22-6986-4fe0-b316-5700ec3233a8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/quantal-folsom-proposed /tmp/tmpxxoMos/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpxxoMos/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208140932~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208140932~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8ece7b22-6986-4fe0-b316-5700ec3233a8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-8ece7b22-6986-4fe0-b316-5700ec3233a8', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/384/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 10:01:55 -0400Build duration:6 min 27 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesEnforce quota limitations for instance resize.by eglynneditnova/tests/scheduler/test_scheduler.pyeditnova/tests/compute/test_rpcapi.pyeditnova/compute/manager.pyeditnova/scheduler/filter_scheduler.pyeditnova/scheduler/driver.pyeditnova/compute/rpcapi.pyeditnova/scheduler/manager.pyeditnova/compute/api.pyeditnova/scheduler/rpcapi.pyeditnova/scheduler/chance.pyeditnova/tests/compute/test_compute.pyeditnova/tests/scheduler/test_rpcapi.pyConsole Output[...truncated 5456 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10344.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/tmpVaVQEM/novamk-build-deps -i -r -t apt-get -y /tmp/tmpVaVQEM/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141005~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141005~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/393/Project:precise_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 10:01:54 -0400Build duration:9 min 4 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesEnforce quota limitations for instance resize.by eglynneditnova/scheduler/rpcapi.pyeditnova/scheduler/filter_scheduler.pyeditnova/tests/scheduler/test_rpcapi.pyeditnova/compute/rpcapi.pyeditnova/scheduler/manager.pyeditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyeditnova/scheduler/driver.pyeditnova/tests/compute/test_rpcapi.pyeditnova/scheduler/chance.pyeditnova/tests/scheduler/test_scheduler.pyeditnova/compute/api.pyConsole Output[...truncated 18909 lines...]Build-Time: 61Distribution: precise-folsomFail-Stage: buildInstall-Time: 40Job: nova_2012.2+git201208141005~precise-0ubuntu1.dscPackage: novaPackage-Time: 115Source-Version: 2012.2+git201208141005~precise-0ubuntu1Space: 63400Status: attemptedVersion: 2012.2+git201208141005~precise-0ubuntu1Finished at 20120814-1010Build needed 00:01:55, 63400k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141005~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141005~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/tmpIq4672/novamk-build-deps -i -r -t apt-get -y /tmp/tmpIq4672/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ed80ed615762e0ff24235b7d57fa8b356c659e11..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208141005~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141005~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208141005~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208141005~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141005~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141005~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 Fixed: quantal_folsom_quantum_trunk #100

Title: quantal_folsom_quantum_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_quantum_trunk/100/Project:quantal_folsom_quantum_trunkDate of build:Tue, 14 Aug 2012 12:01:53 -0400Build duration:3 min 58 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesAdd quota per-tenant.by gongysheditquantum/api/v2/base.pyeditquantum/wsgi.pyeditquantum/extensions/providernet.pyeditquantum/tests/unit/extensions/v2attributes.pyaddquantum/extensions/_quotav2_driver.pyeditquantum/common/exceptions.pyeditetc/quantum.confeditquantum/quota.pyaddquantum/extensions/_quotav2_model.pyaddquantum/extensions/quotasv2.pyaddquantum/tests/unit/test_quota_per_tenant_ext.pyeditquantum/extensions/extensions.pyConsole Output[...truncated 4272 lines...]Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading quantum_2012.2+git201208141202~quantal-0ubuntu1.dsc: done.  Uploading quantum_2012.2+git201208141202~quantal.orig.tar.gz: done.  Uploading quantum_2012.2+git201208141202~quantal-0ubuntu1.debian.tar.gz: done.  Uploading quantum_2012.2+git201208141202~quantal-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'quantal-folsom', 'quantum_2012.2+git201208141202~quantal-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/q/quantum/python-quantum_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-common_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-cisco_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-linuxbridge-agent_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-linuxbridge_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-nicira_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-openvswitch-agent_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-openvswitch_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-ryu-agent_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-plugin-ryu_2012.2+git201208140702~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/q/quantum/quantum-server_2012.2+git201208140702~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/quantum/quantal-folsom']Pushed up to revision 47.INFO:root:Storing current commit for next build: 46cac19852b7879daa36962a8643727264a42ff5INFO:root:Complete command log:INFO:root:Destroying schroot.git archive master --format tar --prefix quantum-2012.2-201208141202/git archive master --format tar --prefix quantum-2012.2-201208141202/git log -n1 --no-merges --pretty=format:%Hgit log ce1638c283f894547fee7ccc83c66a54aa502c7e..HEAD --no-merges --pretty=format:[%h] %sbzr branch lp:~openstack-ubuntu-testing/quantum/quantal-folsom-proposed quantumbzr merge lp:~openstack-ubuntu-testing/quantum/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141202~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141202~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucmk-build-deps -i -r -t apt-get -y /tmp/tmpuG6vd9/quantum/debian/controlbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2012.2+git201208141202~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A quantum_2012.2+git201208141202~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing quantum_2012.2+git201208141202~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom quantum_2012.2+git201208141202~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/quantum/quantal-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/385/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 12:05:14 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAllow stop API to be called in Errorby yunmaoeditdoc/source/devref/vmstates.rstValidate that min_count  max_count parameters are numeric.by ed.bak2editnova/tests/api/openstack/compute/test_servers.pyeditnova/api/openstack/compute/servers.pyConsole Output[...truncated 5468 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10358.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/tmp6rXuze/novamk-build-deps -i -r -t apt-get -y /tmp/tmp6rXuze/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141213~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141213~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/394/Project:precise_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 12:05:13 -0400Build duration:12 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAllow stop API to be called in Errorby yunmaoeditdoc/source/devref/vmstates.rstValidate that min_count  max_count parameters are numeric.by ed.bak2editnova/api/openstack/compute/servers.pyeditnova/tests/api/openstack/compute/test_servers.pyConsole Output[...truncated 18913 lines...]Build-Time: 61Distribution: precise-folsomFail-Stage: buildInstall-Time: 41Job: nova_2012.2+git201208141213~precise-0ubuntu1.dscPackage: novaPackage-Time: 115Source-Version: 2012.2+git201208141213~precise-0ubuntu1Space: 63416Status: attemptedVersion: 2012.2+git201208141213~precise-0ubuntu1Finished at 20120814-1217Build needed 00:01:55, 63416k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141213~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141213~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/tmp8FFYO4/novamk-build-deps -i -r -t apt-get -y /tmp/tmp8FFYO4/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ed80ed615762e0ff24235b7d57fa8b356c659e11..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208141213~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141213~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208141213~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208141213~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141213~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141213~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_cinder_trunk #41

Title: precise_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/41/Project:precise_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 12:31:56 -0400Build duration:6 min 20 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesReplace deprecated client with python-glanceclientby josh.durginedittools/pip-requireseditcinder/tests/image/fake.pyeditcinder/image/glance.pyrbd: implement create_volume_from_snapshotby josh.durgineditcinder/volume/driver.pyConsole Output[...truncated 2492 lines...]Build-Time: 48Distribution: precise-folsomFail-Stage: buildInstall-Time: 60Job: cinder_2012.2+git201208141232~precise-0ubuntu1.dscPackage: cinderPackage-Time: 124Source-Version: 2012.2+git201208141232~precise-0ubuntu1Space: 10752Status: attemptedVersion: 2012.2+git201208141232~precise-0ubuntu1Finished at 20120814-1238Build needed 00:02:04, 10752k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141232~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141232~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/precise-folsom-proposed /tmp/tmpeEVWgu/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpeEVWgu/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208141232~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141232~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208141232~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2+git201208141232~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141232~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141232~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_cinder_trunk #43

Title: quantal_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/43/Project:quantal_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 12:36:33 -0400Build duration:2 min 18 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesReplace deprecated client with python-glanceclientby josh.durginedittools/pip-requireseditcinder/image/glance.pyeditcinder/tests/image/fake.pyrbd: implement create_volume_from_snapshotby josh.durgineditcinder/volume/driver.pyConsole Output[...truncated 1855 lines...]Looking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmpFjP1sHbzr: ERROR: An error (1) occurred running quilt: Applying patch 0001-Use-setuptools-git.patchpatching file MANIFEST.inHunk #1 FAILED at 1.1 out of 1 hunk FAILED -- rejects in file MANIFEST.inpatching file setup.pyHunk #1 FAILED at 31.1 out of 1 hunk FAILED -- rejects in file setup.pypatching file tools/test-requiresHunk #1 FAILED at 9.1 out of 1 hunk FAILED -- rejects in file tools/test-requiresPatch 0001-Use-setuptools-git.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-1ba4bc93-7b08-4fe8-9d3e-df150050a110', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-1ba4bc93-7b08-4fe8-9d3e-df150050a110', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/quantal-folsom-proposed /tmp/tmpFjP1sH/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpFjP1sH/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141236~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141236~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-1ba4bc93-7b08-4fe8-9d3e-df150050a110', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-1ba4bc93-7b08-4fe8-9d3e-df150050a110', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/386/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 13:02:13 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesvolumes: fix check_for_export() in non-exporting volume driversby josh.durgineditnova/volume/driver.pyRevert task_state on failed instance actionsby danmseditnova/compute/manager.pyeditnova/tests/compute/test_compute.pyConsole Output[...truncated 5480 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10372.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/tmpMIAtDx/novamk-build-deps -i -r -t apt-get -y /tmp/tmpMIAtDx/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141308~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141308~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_cinder_trunk #44

Title: quantal_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/44/Project:quantal_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 13:32:02 -0400Build duration:3 min 49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesDriver for IBM XIV storage.by avishayaddcinder/tests/test_xiv.pyeditcinder/tests/fake_flags.pyaddcinder/volume/xiv.pyConsole Output[...truncated 1863 lines...]Looking for a way to retrieve the upstream tarballUsing the upstream tarball that is present in /tmp/tmpfZ5_qIbzr: ERROR: An error (1) occurred running quilt: Applying patch 0001-Use-setuptools-git.patchpatching file MANIFEST.inHunk #1 FAILED at 1.1 out of 1 hunk FAILED -- rejects in file MANIFEST.inpatching file setup.pyHunk #1 FAILED at 31.1 out of 1 hunk FAILED -- rejects in file setup.pypatching file tools/test-requiresHunk #1 FAILED at 9.1 out of 1 hunk FAILED -- rejects in file tools/test-requiresPatch 0001-Use-setuptools-git.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f9ba47d4-5388-4573-b459-3d7b813963e0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f9ba47d4-5388-4573-b459-3d7b813963e0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/quantal-folsom-proposed /tmp/tmpfZ5_qI/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpfZ5_qI/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141332~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141332~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f9ba47d4-5388-4573-b459-3d7b813963e0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-r', '-c', 'quantal-amd64-f9ba47d4-5388-4573-b459-3d7b813963e0', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_cinder_trunk #42

Title: precise_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/42/Project:precise_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 13:32:02 -0400Build duration:6 min 26 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesDriver for IBM XIV storage.by avishayeditcinder/tests/fake_flags.pyaddcinder/volume/xiv.pyaddcinder/tests/test_xiv.pyConsole Output[...truncated 2515 lines...]Build-Time: 46Distribution: precise-folsomFail-Stage: buildInstall-Time: 47Job: cinder_2012.2+git201208141332~precise-0ubuntu1.dscPackage: cinderPackage-Time: 119Source-Version: 2012.2+git201208141332~precise-0ubuntu1Space: 10768Status: attemptedVersion: 2012.2+git201208141332~precise-0ubuntu1Finished at 20120814-1338Build needed 00:01:59, 10768k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141332~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141332~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/precise-folsom-proposed /tmp/tmpGBTjju/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpGBTjju/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208141332~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141332~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208141332~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2+git201208141332~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141332~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141332~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_cinder_trunk #45

Title: quantal_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/45/Project:quantal_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 13:59:36 -0400Build duration:3 min 2 secBuild cause:Started by user zulBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 3138 lines...]Build-Time: 3Distribution: quantal-folsomFail-Stage: buildInstall-Time: 44Job: cinder_2012.2+git201208141359~quantal-0ubuntu1.dscPackage: cinderPackage-Time: 67Source-Version: 2012.2+git201208141359~quantal-0ubuntu1Space: 18068Status: attemptedVersion: 2012.2+git201208141359~quantal-0ubuntu1Finished at 20120814-1402Build needed 00:01:07, 18068k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208141359~quantal-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208141359~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/quantal-folsom-proposed /tmp/tmpwZ2AIA/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpwZ2AIA/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141359~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141359~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208141359~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A cinder_2012.2+git201208141359~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208141359~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'cinder_2012.2+git201208141359~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: quantal_folsom_cinder_trunk #46

Title: quantal_folsom_cinder_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/46/Project:quantal_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 14:17:20 -0400Build duration:5 min 14 secBuild cause:Started by user zulBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 5040 lines...]gpg: Signature made Tue Aug 14 14:19:55 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpzWgb27/cinder_2012.2+git201208141417~quantal-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpzWgb27/cinder_2012.2+git201208141417~quantal-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading cinder_2012.2+git201208141417~quantal-0ubuntu1.dsc: done.  Uploading cinder_2012.2+git201208141417~quantal.orig.tar.gz: done.  Uploading cinder_2012.2+git201208141417~quantal-0ubuntu1.debian.tar.gz: done.  Uploading cinder_2012.2+git201208141417~quantal-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'quantal-folsom', 'cinder_2012.2+git201208141417~quantal-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/quantal-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/c/cinder/cinder-api_2012.2+git201208101132~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-common_2012.2+git201208101132~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-scheduler_2012.2+git201208101132~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-volume_2012.2+git201208101132~quantal-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/python-cinder_2012.2+git201208101132~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/cinder/quantal-folsom']Pushed up to revision 31.2 tags updated.INFO:root:Storing current commit for next build: ff45e32b97a7b87a611715ba61f0ebab5185edc3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/quantal-folsom-proposed /tmp/tmpzWgb27/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpzWgb27/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141417~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141417~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208141417~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A cinder_2012.2+git201208141417~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing cinder_2012.2+git201208141417~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom cinder_2012.2+git201208141417~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/cinder/quantal-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/389/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 16:01:55 -0400Build duration:7 min 43 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesReturn values from wrapped functions in decoratorsby vishvanandaeditnova/compute/manager.pyConsole Output[...truncated 5498 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10393.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/tmp_OkqZ1/novamk-build-deps -i -r -t apt-get -y /tmp/tmp_OkqZ1/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141606~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141606~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_cinder_trunk #43

Title: precise_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/43/Project:precise_folsom_cinder_trunkDate of build:Tue, 14 Aug 2012 17:01:55 -0400Build duration:9 min 10 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesAdd C-mode driver for NetApp.by bswartzeditcinder/tests/test_netapp.pyeditcinder/volume/netapp.pyConsole Output[...truncated 2517 lines...]Build-Time: 49Distribution: precise-folsomFail-Stage: buildInstall-Time: 151Job: cinder_2012.2+git201208141702~precise-0ubuntu1.dscPackage: cinderPackage-Time: 269Source-Version: 2012.2+git201208141702~precise-0ubuntu1Space: 10792Status: attemptedVersion: 2012.2+git201208141702~precise-0ubuntu1Finished at 20120814-1710Build needed 00:04:29, 10792k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141702~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141702~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/precise-folsom-proposed /tmp/tmpiUff0C/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpiUff0C/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 69aa04d1f89c838d2ea1c96e715e175fb26f0883..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208141702~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141702~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2+git201208141702~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2+git201208141702~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141702~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'cinder_2012.2+git201208141702~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 #390

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/390/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 17:01:59 -0400Build duration:11 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changescontinue config-drive-v2, add openstack metadata apiby smosereditnova/virt/netutils.pyeditnova/api/metadata/base.pyeditnova/tests/test_metadata.pyeditnova/tests/test_libvirt.pyeditnova/virt/configdrive.pyeditnova/virt/libvirt/driver.pyConsole Output[...truncated 5504 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10400.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/tmp9oBUgl/novamk-build-deps -i -r -t apt-get -y /tmp/tmp9oBUgl/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141706~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141706~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/398/Project:precise_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 17:02:01 -0400Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changescontinue config-drive-v2, add openstack metadata apiby smosereditnova/virt/netutils.pyeditnova/virt/libvirt/driver.pyeditnova/virt/configdrive.pyeditnova/tests/test_metadata.pyeditnova/tests/test_libvirt.pyeditnova/api/metadata/base.pyConsole Output[...truncated 19170 lines...]Build-Time: 117Distribution: precise-folsomFail-Stage: buildInstall-Time: 68Job: nova_2012.2+git201208141706~precise-0ubuntu1.dscPackage: novaPackage-Time: 209Source-Version: 2012.2+git201208141706~precise-0ubuntu1Space: 63428Status: attemptedVersion: 2012.2+git201208141706~precise-0ubuntu1Finished at 20120814-1717Build needed 00:03:29, 63428k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141706~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141706~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/tmpn38Kq_/novamk-build-deps -i -r -t apt-get -y /tmp/tmpn38Kq_/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ed80ed615762e0ff24235b7d57fa8b356c659e11..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/precise-folsom --forcedch -b -D precise --newversion 2012.2+git201208141706~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141706~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2012.2+git201208141706~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A nova_2012.2+git201208141706~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141706~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'nova_2012.2+git201208141706~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_glance_trunk #107

Title: precise_folsom_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_trunk/107/Project:precise_folsom_glance_trunkDate of build:Tue, 14 Aug 2012 18:01:59 -0400Build duration:5 min 22 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesMark bin/glance as deprecatedby bcwaldoneditglance/client.pyeditbin/glanceConsole Output[...truncated 3347 lines...]Build-Time: 5Distribution: precise-folsomFail-Stage: buildInstall-Time: 66Job: glance_2012.2+git201208141802~precise-0ubuntu1.dscPackage: glancePackage-Time: 101Source-Version: 2012.2+git201208141802~precise-0ubuntu1Space: 9716Status: attemptedVersion: 2012.2+git201208141802~precise-0ubuntu1Finished at 20120814-1807Build needed 00:01:41, 9716k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'glance_2012.2+git201208141802~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'glance_2012.2+git201208141802~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/precise-folsom-proposed /tmp/tmptYhtkC/glancemk-build-deps -i -r -t apt-get -y /tmp/tmptYhtkC/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+git201208141802~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 2012.2+git201208141802~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2012.2+git201208141802~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A glance_2012.2+git201208141802~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'glance_2012.2+git201208141802~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'glance_2012.2+git201208141802~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 #391

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/391/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 19:01:56 -0400Build duration:8 min 19 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSet task_state=None when finished snapshotting.by dprinceeditnova/compute/manager.pyConsole Output[...truncated 5510 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10407.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/tmpo0QteA/novamk-build-deps -i -r -t apt-get -y /tmp/tmpo0QteA/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208141907~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208141907~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/393/Project:quantal_folsom_nova_trunkDate of build:Tue, 14 Aug 2012 21:32:00 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImplement network association in OS APIby anneeditnova/db/sqlalchemy/api.pyeditnova/db/api.pyeditnova/api/openstack/compute/contrib/networks.pyeditnova/tests/api/openstack/compute/contrib/test_networks.pyeditnova/network/quantumv2/api.pyeditnova/network/manager.pyeditnova/network/api.pyxenapi: Support live migration without poolsby renuka.apteeditnova/tests/xenapi/stubs.pyeditnova/virt/xenapi/fake.pyeditnova/virt/driver.pyeditnova/virt/fake.pyeditnova/tests/scheduler/test_scheduler.pyeditnova/tests/test_xenapi.pyeditnova/virt/libvirt/driver.pyeditnova/scheduler/driver.pyeditnova/virt/xenapi/driver.pyeditnova/virt/xenapi/vmops.pyeditnova/compute/manager.pyeditnova/compute/rpcapi.pyeditnova/tests/compute/test_rpcapi.pyConsole Output[...truncated 5528 lines...]* Automated Ubuntu testing build:* [c5a9c75] Ensure that the dom0 we're connected to is the right one* [2dcd825] Pass context to notification drivers when we can.* [b841b6a] Fix innodb tests again* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [ac21815] Allow blank adminPass on server create* [03a331c] Log instance consistently.* [2511f01] Use additional task states during resize* Automated Ubuntu testing build:* [29dc47b] Use save_and_reraise_exception() from common.* [b841b6a] Fix innodb tests again* [ca2bb06] Remove unused images* [d14ac4b] Adding 'host' info to volume-compute connection  information.* [524bfb8] Update common.importutils from openstack-common.' --fixes 'lp:1002111'Can't exec "bzr": Argument list too long at /usr/bin/debcommit line 484,  line 10428.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/tmpNBaJCp/novamk-build-deps -i -r -t apt-get -y /tmp/tmpNBaJCp/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0e6fc4f4ddca1ea76f9f03ef03d960cad888c810..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/nova/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201208142136~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201208142136~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 140, in raise esubprocess.CalledProcessError: Command '['debcommit']' returned non-zero exit status 7Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_nova_trunk #401