[Openstack] Openstack+Quantum+OVS Internals - Doubts

[Trinath Somanchi]

Hi-

I'm now viewing the code of Openstack from a top level to understand the
process flow of the commands and messages in the system.

I have the following doubts.

[1] What is the role of Quantum-Agent in Controller and Node. How will the
gw- and tap- interface and ports are created in Controller and Host
integration bridge of ovs.

This is how I understand from my study.

*[Trinath] *The flow as follows


   1. Upon receiving an REST call from Horizon, Nova API collected the
   Networking information from the nova_network and prepares an JSON formatted
   request and update the AMQP Queue.
   2. AMQP sends an Async cast to Nova Compute. Upon receiving the cast,
   Nova Compute issues _create_instance and updates the AMQP queue. AMQP queue
   sends an Async cast to Scheduler.
   3. Upon receiving the cast, Scheduler selects the Compute Node and send
   an async cast to the node. Node using the info in the queue using libvirt
   brings up the instance.
   4. Quantum-Agent at NODE updates the DB at controller with the Vlan
   tagged Port-Vif details.
   5. Quantum-Agent at Controller upon reading the DB on Vlan tagged
   Port-Vif details creates Gateway interfaces in the OVS integration bridge
   so that controller can access the VM's present in remote host.

Please update/correct with the pitfalls in my understanding outlined above.


[2] How AMQP (using RabbitMQ server) work, mean to say. How Controller
communicates with the Node for creating an Virtual instance in view of
AMQP. Wanted to be more clear on what Messages do Controller and Node
exchange to create an Virtual Instance.

*[Trinath]* I'm not good at AMQP. Can you kindly describe on how this works.

[3] I have created a Public and Tenant specific network using nova-manage
network  command.

For each Virtual Instance, I have seen a Public IP addr, and Tenant
Specific IP Addr. For both IP addrs I'm unable to ping from NODE machine.

Rather for the Tenant specific IP Addrs I'm able to ping from Controller
but not the Public IP Addrs..

Can any one guide me on what has happened in the way...

Thanking you...

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

Re: [Openstack] Hiding complexity of paste config files from operators

[Thierry Carrez]

Lorin Hochstein wrote:
 I wanted to discuss the usability of the paste config files from an
 operator's point of view. The paste config files are opaque to
 administrators who are trying to stand an OpenStack cloud for the first
 time, since they expose a lot of implementation details about the
 middleware. I can follow the instructions in the Install and Deploy
 guide, but I have no idea what the options I don't edit are, and if the
 documentation has deviated from the implementation, I'm pretty much stuck.
 [...]

This was mentioned in the Making configuration easier session on the
DevOps track at the last design summit. You can find the notes at:

http://etherpad.openstack.org/FolsomMakingConfigurationEasier

In particular, it was identified that paste configs were evil, failing
to properly separate service/code configuration from end-user configuration.

 Assuming that the *-paste.ini files always need to be there, is there some 
 way we could avoid requiring admins to edit these files, and instead make it 
 more like editing the .conf files? For example, could the paste.ini files be 
 generated from the corresponding .conf file as needed?

I would not assume that *-paste.ini files always need to be there...
Paste is a pain point if we are to support Python 3 one day, so it's
also on the black list of the (still inexistant) OpenStack Python3
advocacy group.

So I'd rather investigate a solution that solves our two problems,
rather than adding a layer on top of the current broken solution... That
said I'm not really a specialist of Paste alternatives.

-- 
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+Quantum+OVS Internals - Doubts

[Trinath Somanchi]

Hi Guys-


I have found the solution to my Second Doubt

Link: http://docs.openstack.org/developer/nova/devref/rpc.html

and Thanks Emilien for clearing my 3rd Doubt.

But still in need of help.

Can you any one validate my understanding with the data flow in
Nova+Quantum scenario for bringing up the VM instances.

*[Trinath] *The flow as follows


   1. Upon receiving an REST call from Horizon, Nova API collected the
   Networking information from the nova_network and prepares an JSON formatted
   request and update the AMQP Queue.
   2. AMQP sends an Async cast to Nova Compute. Upon receiving the cast,
   Nova Compute issues _create_instance and updates the AMQP queue. AMQP queue
   sends an Async cast to Scheduler.
   3. Upon receiving the cast, Scheduler selects the Compute Node and send
   an async cast to the node. Node using the info in the queue using libvirt
   brings up the instance.
   4. Quantum-Agent at NODE updates the DB at controller with the Vlan
   tagged Port-Vif details.
   5. Quantum-Agent at Controller upon reading the DB on Vlan tagged
   Port-Vif details creates Gateway interfaces in the OVS integration bridge
   so that controller can access the VM's present in remote host.



On Mon, Jul 30, 2012 at 11:52 AM, Trinath Somanchi 
trinath.soman...@gmail.com wrote:

 Hi-

 I'm now viewing the code of Openstack from a top level to understand the
 process flow of the commands and messages in the system.

 I have the following doubts.

 [1] What is the role of Quantum-Agent in Controller and Node. How will the
 gw- and tap- interface and ports are created in Controller and Host
 integration bridge of ovs.

 This is how I understand from my study.

 *[Trinath] *The flow as follows


1. Upon receiving an REST call from Horizon, Nova API collected the
Networking information from the nova_network and prepares an JSON formatted
request and update the AMQP Queue.
2. AMQP sends an Async cast to Nova Compute. Upon receiving the cast,
Nova Compute issues _create_instance and updates the AMQP queue. AMQP queue
sends an Async cast to Scheduler.
3. Upon receiving the cast, Scheduler selects the Compute Node and
send an async cast to the node. Node using the info in the queue using
libvirt brings up the instance.
4. Quantum-Agent at NODE updates the DB at controller with the Vlan
tagged Port-Vif details.
5. Quantum-Agent at Controller upon reading the DB on Vlan tagged
Port-Vif details creates Gateway interfaces in the OVS integration bridge
so that controller can access the VM's present in remote host.

 Please update/correct with the pitfalls in my understanding outlined above.


 [2] How AMQP (using RabbitMQ server) work, mean to say. How Controller
 communicates with the Node for creating an Virtual instance in view of
 AMQP. Wanted to be more clear on what Messages do Controller and Node
 exchange to create an Virtual Instance.

 *[Trinath]* I'm not good at AMQP. Can you kindly describe on how this
 works.

 [3] I have created a Public and Tenant specific network using nova-manage
 network  command.

 For each Virtual Instance, I have seen a Public IP addr, and Tenant
 Specific IP Addr. For both IP addrs I'm unable to ping from NODE machine.

 Rather for the Tenant specific IP Addrs I'm able to ping from Controller
 but not the Public IP Addrs..

 Can any one guide me on what has happened in the way...

 Thanking you...

 --
 Regards,
 --
 Trinath Somanchi,
 +91 9866 235 130




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

Re: [Openstack] qpid_heartbeat...doesn't?

[Ravi Jagannathan]

Registering  service heartbeat into the subsystem might alleviate the need
to restart certain items . This subsystem is the one that monitors what
services are up and running .

Ravi.

On Sun, Jul 29, 2012 at 9:58 PM, Lars Kellogg-Stedman l...@seas.harvard.edu
 wrote:

 On Sun, Jul 29, 2012 at 09:49:25PM -0400, Lars Kellogg-Stedman wrote:
  And indeed, if I run a packet trace on this connection, I can verify
  that packets are only showing up at five-minute intervals.

 Horrors!  It may be that nova-volume didn't get restarted when I
 restarted everything else.  After explicitly restarting nova-volume it
 now seems to be emitting heartbeat traffic that correspond with what
 the other processes are doing.

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

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

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

Re: [Openstack] Keyring support in openstack

[Doug Hellmann]

On Sun, Jul 29, 2012 at 1:37 AM, Bhuvaneswaran A bhu...@apache.org wrote:

 Team,

 As per patch https://review.openstack.org/#/c/9497/ we are adding
 keyring support for openstack client.  If password is not specified
 in command line or environment variable, the user is prompted to enter
 password. During this time, the password is stored in keyring. During
 next time, the password is read from keyring, instead of prompt. It is
 true, if password is not specified in command line or environment
 variable.

 This behavior is documented in this wiki page:
   http://wiki.openstack.org/KeyringSupport

 If you have any comments, please let us know.


You've already answered several of my questions on the ticket, but I still
have some usability concerns.

How does the keyring system support a single person logging in using
multiple user accounts? For example, if I have an admin account and a
regular user, how do I switch between them based on the operations I need
to perform?

Is there a way to disable the behavior of having a password saved to a
keyring for a particular user, without uninstalling the python-keyring
package (and therefore disabling keyring support for all users)?

The wiki mentions the password being saved
using keyring.backend.UncryptedFileKeyring. Does that mean the password is
saved in cleartext? Is the file protected in some way besides filesystem
permissions?

The mention of one backend implies that there are others. Should we give
users a way to choose the backend, in case they have a preference?

How does the use of the keyring affect scripting using the command line
tool? Can a script access the keyring, or does it need to use the other
options?

In one review comment you mention a few desktop apps that know how to
manipulate the keyring to manage its contents. What about remote access via
ssh, where a desktop environment is not available? Does the keyring library
include tools for manipulating the file, or do we need to build our own? If
so, what tools would be needed?

Doug
___
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] Hiding complexity of paste config files from operators

[Adam Young]

On 07/30/2012 05:12 AM, Thierry Carrez wrote:

Lorin Hochstein wrote:

I wanted to discuss the usability of the paste config files from an
operator's point of view. The paste config files are opaque to
administrators who are trying to stand an OpenStack cloud for the first
time, since they expose a lot of implementation details about the
middleware. I can follow the instructions in the Install and Deploy
guide, but I have no idea what the options I don't edit are, and if the
documentation has deviated from the implementation, I'm pretty much stuck.
[...]

This was mentioned in the Making configuration easier session on the
DevOps track at the last design summit. You can find the notes at:

http://etherpad.openstack.org/FolsomMakingConfigurationEasier

In particular, it was identified that paste configs were evil, failing
to properly separate service/code configuration from end-user configuration.


Assuming that the *-paste.ini files always need to be there, is there some way 
we could avoid requiring admins to edit these files, and instead make it more 
like editing the .conf files? For example, could the paste.ini files be 
generated from the corresponding .conf file as needed?

I would not assume that *-paste.ini files always need to be there...
Paste is a pain point if we are to support Python 3 one day, so it's
also on the black list of the (still inexistant) OpenStack Python3
advocacy group.

So I'd rather investigate a solution that solves our two problems,
rather than adding a layer on top of the current broken solution... That
said I'm not really a specialist of Paste alternatives.

It seems to me that there is nothing that you can do in Paste that you 
cannot do in straight python.  THe advantage of Paste is hat it is 
viewed as a Config file, not as code and thus is a file that end 
system administrators can use.



A paste file is nothing more than an assignment to a variable name from 
a string that is  done at run time.  For example,   the Keystone config 
file has a paste fragment in it:


[app:public_version_service]
paste.app_factory = keystone.service:public_version_app_factory



This same code could be performed inside the Python code base with 
pretty much the same code interpred as Python.  The issue is that we 
would then want to allow a value such as this to be overridden:


For example, specifying the driver for the token api is done:

[token]
 driver = keystone.token.backends.kvs.Token

Since most of these cases have reasonable defaults,  they should be left 
out of the paste files.  What needs to be available is solid 
documentation of the values that can be overridden this way.  Any keys 
that are not defaulted,  but are not really designed to be overloaded 
should be modified so that they are defaulted, and then the keys removed 
from the paste file.






___
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] Performing HPCC Benchmark on OpenStack Cloud

[Reza Bakhshayeshi]

Hi

I want to run HPCC benchmark on OpenStack cloud, I want you to help me to
make the results more real.
How can we impute the results to OpenStack and not to my computers?
Do I really need a server farm to perform the test?
And I think I have to run for example HPL on running instances and not on
the main servers, is this correct?

Please suggest me more rules and conditions.

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

Re: [Openstack] Keyring support in openstack

[David Kranz]

I share Doug's concerns but would state some more strongly. IMO, it is 
simply unacceptable to modify user-visible behavior based on whether 
some package that happens to be used in an implementation is installed 
or not. This package is installed on Ubuntu by default and may be used 
by other applications that have nothing to do with OpenStack at all.


The proposed behavior is biased towards a very simple use case of a 
single user with a password manually invoking commands at the shell. It 
is really up to the administrator of a machine with the client installed 
what the security policy should be. As Doug suggested, this change is a 
very small piece of an overall security architecture which is not well 
spelled out here.


If we really want to go down this road there should be an environment 
variable that can be set to turn off this behavior for applications that 
do not want it.


 -David

On 7/30/2012 9:31 AM, Doug Hellmann wrote:



On Sun, Jul 29, 2012 at 1:37 AM, Bhuvaneswaran A bhu...@apache.org 
mailto:bhu...@apache.org wrote:


Team,

As per patch https://review.openstack.org/#/c/9497/ we are adding
keyring support for openstack client.  If password is not specified
in command line or environment variable, the user is prompted to enter
password. During this time, the password is stored in keyring. During
next time, the password is read from keyring, instead of prompt. It is
true, if password is not specified in command line or environment
variable.

This behavior is documented in this wiki page:
http://wiki.openstack.org/KeyringSupport

If you have any comments, please let us know.


You've already answered several of my questions on the ticket, but I 
still have some usability concerns.


How does the keyring system support a single person logging in using 
multiple user accounts? For example, if I have an admin account and a 
regular user, how do I switch between them based on the operations I 
need to perform?


Is there a way to disable the behavior of having a password saved to a 
keyring for a particular user, without uninstalling the python-keyring 
package (and therefore disabling keyring support for all users)?


The wiki mentions the password being saved 
using keyring.backend.UncryptedFileKeyring. Does that mean the 
password is saved in cleartext? Is the file protected in some way 
besides filesystem permissions?


The mention of one backend implies that there are others. Should we 
give users a way to choose the backend, in case they have a preference?


How does the use of the keyring affect scripting using the command 
line tool? Can a script access the keyring, or does it need to use the 
other options?


In one review comment you mention a few desktop apps that know how to 
manipulate the keyring to manage its contents. What about remote 
access via ssh, where a desktop environment is not available? Does the 
keyring library include tools for manipulating the file, or do we need 
to build our own? If so, what tools would be needed?


Doug



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


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

[Openstack] Suspend/Stop VM

[George Reese]

I must be missing something, but I can't find any docs on how to suspend or 
stop a VM via API.

Any pointers, please? :)

-George

--
George Reese - Chief Technology Officer, enStratus
e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: 
+1.207.956.0217
enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com
To schedule a meeting with me: http://tungle.me/GeorgeReese

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

Re: [Openstack] Suspend/Stop VM

[Pengjun Pan]

I never tried to stop a VM using api. But run a nova help, it has
pause, reboot, resume, etc.

To bypass nova api, you can use virsh to stop instances. Do a sudo
virsh list --all, it will list all the running instances even if nova
cannot see it for some reason. And then you can kill all the ghost
instances by sudo virsh shutdown id.

Hope this helps.

PJ


On Mon, Jul 30, 2012 at 10:50 AM, George Reese
george.re...@enstratus.com wrote:
 I must be missing something, but I can't find any docs on how to suspend or
 stop a VM via API.

 Any pointers, please? :)

 -George

 --
 George Reese - Chief Technology Officer, enStratus
 e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
 +1.207.956.0217
 enStratus: Enterprise Cloud Management - @enStratus -
 http://www.enstratus.com
 To schedule a meeting with me: http://tungle.me/GeorgeReese


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


___
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] Suspend/Stop VM

[George Reese]

Thanks, but I am looking for how this is done via API.

-George

On Jul 30, 2012, at 11:11 AM, Pengjun Pan panpeng...@gmail.com wrote:

 I never tried to stop a VM using api. But run a nova help, it has
 pause, reboot, resume, etc.
 
 To bypass nova api, you can use virsh to stop instances. Do a sudo
 virsh list --all, it will list all the running instances even if nova
 cannot see it for some reason. And then you can kill all the ghost
 instances by sudo virsh shutdown id.
 
 Hope this helps.
 
 PJ
 
 
 On Mon, Jul 30, 2012 at 10:50 AM, George Reese
 george.re...@enstratus.com wrote:
 I must be missing something, but I can't find any docs on how to suspend or
 stop a VM via API.
 
 Any pointers, please? :)
 
 -George
 
 --
 George Reese - Chief Technology Officer, enStratus
 e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
 +1.207.956.0217
 enStratus: Enterprise Cloud Management - @enStratus -
 http://www.enstratus.com
 To schedule a meeting with me: http://tungle.me/GeorgeReese
 
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 

--
George Reese - Chief Technology Officer, enStratus
e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: 
+1.207.956.0217
enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com
To schedule a meeting with me: http://tungle.me/GeorgeReese

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

[Openstack] python 3 advocacy (was Re: Hiding complexity of paste config files from operators)

[Doug Hellmann]

On Mon, Jul 30, 2012 at 5:12 AM, Thierry Carrez thie...@openstack.orgwrote:


  Assuming that the *-paste.ini files always need to be there, is there
 some way we could avoid requiring admins to edit these files, and instead
 make it more like editing the .conf files? For example, could the paste.ini
 files be generated from the corresponding .conf file as needed?

 I would not assume that *-paste.ini files always need to be there...
 Paste is a pain point if we are to support Python 3 one day, so it's
 also on the black list of the (still inexistant) OpenStack Python3
 advocacy group.


We exist, we're just not organized, yet. :-)

Who else is interested in contributing to Python 3 support in a future
version of OpenStack? Should we start planning for some discussions at the
Grizzly summit?

Doug
___
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] Suspend/Stop VM

[Mark Moseley]

On Mon, Jul 30, 2012 at 8:50 AM, George Reese
george.re...@enstratus.com wrote:
 I must be missing something, but I can't find any docs on how to suspend or
 stop a VM via API.

 Any pointers, please? :)

I think this works (see http://api.openstack.org/) but haven't tested
it in a while:

Stop: Encode this python dict with json.dumps:

params = { suspend: None, }

and POST it as the body to v2/{tenant_id}/servers/{server_id}/action

The None really needs to be a None. To start back up, use resume
instead of suspend.

___
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-network and corosync

[Alessandro Tagliapietra]

Dear Steven,

it seems that nova-network breaks the network also on the interface it doesn't 
use, I've just done another fresh install using flat_interface eth1, and i get 
the issue of packets being sent with the public address.
I think the effects of nova-network should be restricted to some interfaces, so 
it doesn't breaks other services.

Best

Alessandro

Il giorno 19/lug/2012, alle ore 11:53, Alessandro Tagliapietra 
tagliapietra.alessan...@gmail.com ha scritto:

 
 Il giorno 19/lug/2012, alle ore 09:55, Alessandro Tagliapietra ha scritto:
 
 
 Il giorno 19/lug/2012, alle ore 09:40, Alessandro Tagliapietra ha scritto:
 
 
 Il giorno 19/lug/2012, alle ore 00:52, Steven Dake ha scritto:
 
 On 07/18/2012 06:51 AM, Alessandro Tagliapietra wrote:
 Hi Steve,
 
 the problem is not that it's not listening on the correct interface, as 
 lsof shows
 
 corosync 1485 root9u  IPv4  14890  0t0   UDP 
 226.94.1.1:5405 
 corosync 1485 root   10u  IPv4  14891  0t0   UDP 
 server1:5404 
 corosync 1485 root   11u  IPv4  14892  0t0   UDP 
 server1:5405
 
 where server1 is 10.8.0.1, which is correct because it's the eth1 address.
 
 The problem is that for some reason, the packets it sends to eth1 has as 
 source ip the ip of eth0, which is the public internet connected 
 interface, so like:
 
 15:44:34.135411 IP 5.9.x.x.5404  226.94.1.1.5405: UDP, length 82
 15:44:34.238762 IP 5.9.x.x.5404  226.94.1.1.5405: UDP, length 82
 
 which is wrong. my ip r is this:
 
 default via 5.9.x.x dev eth0  metric 100 
 5.9.x.x/27 via 5.9.x.x dev eth0 
 5.9.x.x/27 dev eth0  proto kernel  scope link  src 5.9.x.x 
 10.0.0.0/16 dev eth2  proto kernel  scope link  src 10.0.0.1 
 10.8.0.0/16 dev eth1  proto kernel  scope link  src 10.8.0.1 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
 
 As you can see packets to eth1 should have 10.8.0.1 as source, not eth0 
 ip.
 
 
 Odd - Are you using udpu mode?  Which version?  Can you subscribe to the
 corosync list and we can follow-up there?
 
 
 When starting this discussion i was using ubuntu 12.04 repositories so 
 1.4.2, today i've installed 2.0.1, i've added corosync mailing list in cc. 
 I have to specify that this problem happens only when i've installed nova 
 network on both nodes (i'm using multi-host).
 
 I've tried with udpu mode specifying the nodelist and it works fine. I'm 
 going to switch back to 1.4.2 to use regular ubuntu packages and updates and 
 see if that works too.
 
 
 An update, i've removed eth2 (which was just a virtual interface) and set 
 back flat_interface to eth1, now after a reboot i've got the same issue as 
 before, packets are sent using public ip, but if a do a corosync restart 
 after loggin in it works normally. Maybe it needs some delay to work?
 
 Regards
 
 
 Regards
 
 Let me paste some configs:
 
 nova.conf: http://pastie.org/private/c5tcutro6tp0s1te5yq (i've tried with 
 flat_interface eth1 and eth2)
 ifconfig: http://pastie.org/private/7li8gwodr0ulgbafsi4edw
 corosync.conf: http://pastie.org/private/cjrtqx9bspgmff7rlye6ew (tried with 
 10.8.0.0 also as bindnetaddr)
 ip r: http://pastie.org/private/ckqhy0vqoiwzewuj17v7g
 iptables-save: http://pastie.org/private/yvypgi5ovs2rtcingrq5iw (all 
 generated by nova-network)
 
 If you need any other things just ask.
 
 Btw, i'm going to try with udpu now.
 
 Regards
 
 http://lists.corosync.org/mailman/listinfo/discuss
 
 thanks
 -steve
 
 Regards
 
 Il giorno 18/lug/2012, alle ore 15:18, Steven Dake ha scritto:
 
 On 07/18/2012 03:50 AM, Alessandro Tagliapietra wrote:
 Hello,
 
 i've 2 machines, running ubuntu 12.04, i've installed corosync +
 pacemaker and it was working fine.
 
 Corosync is using eth1 with 10.8.0.1 and 10.8.0.2 as ip of the hosts,
 i've got keystone, glance, nova api-cert-scheduler, mysql, rabbitmq
 working in HA with pacemaker.
 
 The problem comes after installing nova-network and nova-compute, i've
 used this nova.conf:
 
 http://pastie.org/private/ddwva8kvaypqrxk7rifvba
 
 and after nova-compute started and hosts rebooted i can't get to work
 corosync,
 
 the problem seems that when hosts send packets in eth1 to multicast
 address, the source ip is the public one, not the 10.8.0.x one. After
 disabling nova-network on boot everything works.
 
 I've also tried to create a virtual eth2 device and set flat_interface
 to eth2, but it seems that still nova-network break the configuration as
 corosync still uses public ip for private lan.
 
 Any idea?
 
 
 Corosync goes to great pains to route packets across the interface
 identified in the corosync.conf file.  If you are using a subnet
 definition ie:
 bindnetaddr: 10.8.0.0, it may be that the interface's netmask is causing
 a rebind to the new interface when nova network starts.
 
 One way to force binding to a specific interface when your network is
 not configured in a typical fashion is to identify the bindnetaddr 
 exactly:
 
 ie: bindnetaddr: 

Re: [Openstack] Suspend/Stop VM

[Mark McLoughlin]

On Mon, 2012-07-30 at 10:50 -0500, George Reese wrote:
 I must be missing something, but I can't find any docs on how to suspend or 
 stop a VM via API.
 
 Any pointers, please? :)

Try 'nova --debug pause $instance'

Shows e.g.

  POST /v2/$tenant/servers/$instance/action HTTP/1.1
  Host: $host:8774
  Accept: application/json
  Content-Length: application/json
  Content-Type: text/html
  x-auth-project-id: demo
  x-auth-token: $token

  {pause: null}'

  HTTP/1.1 202 Accepted

It's an API extension, not part of the core API, and AFAIK they're not
so well documented.

Mark.


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

Re: [Openstack] Suspend/Stop VM

[Eric Windisch]

I'm not sure where the actions are documented, but you can infer them from here:
https://github.com/openstack/python-novaclient/blob/master/novaclient/v1_1/servers.py
 

Below, I've pasted a few of the methods related to this thread.  These are 
POST'ed to the action URI, as Mark suggested. 

Regards,
Eric Windisch

def stop(self, server):

Stop the server.

return self._action('os-stop', server, None)

def start(self, server):

Start the server.

self._action('os-start', server, None)

def pause(self, server):

Pause the server.

self._action('pause', server, None)

def unpause(self, server):

Unpause the server.

self._action('unpause', server, None)

def lock(self, server):

Lock the server.

self._action('lock', server, None)

def unlock(self, server):

Unlock the server.

self._action('unlock', server, None)

def suspend(self, server):

Suspend the server.

self._action('suspend', server, None)

def resume(self, server):

Resume the server.

self._action('resume', server, None)



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

[Openstack] Instance stuck in deleting state with error

[Jonathan Proulx]

Hi All,

I have an instance that has been in this state for a couple days:

| OS-EXT-STS:power_state  | 0|
| OS-EXT-STS:task_state   | deleting|
| OS-EXT-STS:vm_state | error |

with this fault:

| fault | {u'message': u'ProcessExecutionError', u'code': 500,
u'created': u'2012-07-30T16:51:34Z'} |

sending more delete requests seem to have no effect and the node it
thinks it is on doesn't seem to have any state about it.

How to I clean this up, do I just need to muck out the DB and if so
what parts of it?

Thanks,
-Jon

___
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 Foundation] Individual Member Elections

[Lloyd Dewolf]

On Sat, Jul 28, 2012 at 11:18 PM, Jonathan Bryce jonat...@openstack.org wrote:

 We've learned that someone may have violated the basic principles that hold 
 this community together by trying to affect the nominations for the 
 Individual Member elections.

For clarity, my understanding as it played out publicly, of the
accusation is someone was inappropriately discouraging another person
from running for nomination to the board.

Best regards,
--
@lloyddewolf
http://www.pistoncloud.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] Suspend/Stop VM

[Anne Gentle]

As I noted on Twitter, there's an open doc bug at
https://bugs.launchpad.net/openstack-manuals/+bug/1029560 noting this
gap. Thanks George for clicking through to say it impacts you.

I'm sending a second email to the mailing list next to discuss this
unfortunate gap in reality in the API docs, what I believe the causes
to be, and how I'd like to move forward.

Thanks,
Anne



On Mon, Jul 30, 2012 at 11:13 AM, George Reese
george.re...@enstratus.com wrote:
 Thanks, but I am looking for how this is done via API.

 -George

 On Jul 30, 2012, at 11:11 AM, Pengjun Pan panpeng...@gmail.com wrote:

 I never tried to stop a VM using api. But run a nova help, it has
 pause, reboot, resume, etc.

 To bypass nova api, you can use virsh to stop instances. Do a sudo
 virsh list --all, it will list all the running instances even if nova
 cannot see it for some reason. And then you can kill all the ghost
 instances by sudo virsh shutdown id.

 Hope this helps.

 PJ


 On Mon, Jul 30, 2012 at 10:50 AM, George Reese
 george.re...@enstratus.com wrote:

 I must be missing something, but I can't find any docs on how to suspend or
 stop a VM via API.

 Any pointers, please? :)

 -George

 --
 George Reese - Chief Technology Officer, enStratus
 e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
 +1.207.956.0217
 enStratus: Enterprise Cloud Management - @enStratus -
 http://www.enstratus.com
 To schedule a meeting with me: http://tungle.me/GeorgeReese


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


 --
 George Reese - Chief Technology Officer, enStratus
 e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
 +1.207.956.0217
 enStratus: Enterprise Cloud Management - @enStratus -
 http://www.enstratus.com
 To schedule a meeting with me: http://tungle.me/GeorgeReese


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


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

[Openstack] API docs - spec and dev guide split proposal

[Anne Gentle]

Hi again all, your friendly doc coordinator here.

I'd like to get a big push towards documenting reality instead of
relying only on the specs stored in the compute-api repository. As an
example, recently a Rackspace writer inserted min_count and max_count
to the compute-api repository but the change was reversed after a
request by Brian Waldon and Jorge Williams to leave the spec as-is. I
agree that the spec has value but I believe we need to push towards
reality and creating developer guides.

So what I'd like to propose here is that we govern these repos as
specs and change the titles of those documents to API specification:

compute-api
image-api
identity-api
object-api
netconn-api

At the same time, we'd start new developer guides in the
openstack-manuals repository that document reality. We can track the
work needed through the openstack-manuals bug and blueprint system.

I went up to Brian Aker after his keynote at OSCon seeking contacts at
HP who are interested in doing this type of work, and I have started
some one-on-one meetings, but I'd like to find more interested
collaborators. Anyone at Rightscale or Enstratus interested? Also are
there other API implementers who are experts in how the APIs really
work? Please join in finding the right solution here.

Does this proposal sound like a workable solution? Any tweaks or other
suggestions?

Thanks,
Anne

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

Re: [Openstack] Suspend/Stop VM

[George Reese]

Thanks, this bit is perfect.

-George

On Jul 30, 2012, at 11:57 AM, Eric Windisch e...@cloudscaling.com wrote:

 I'm not sure where the actions are documented, but you can infer them from 
 here:
 https://github.com/openstack/python-novaclient/blob/master/novaclient/v1_1/servers.py
 
 Below, I've pasted a few of the methods related to this thread.  These are 
 POST'ed to the action URI, as Mark suggested.
 
 Regards,
 Eric Windisch
 
 def stop(self, server):
 
 Stop the server.
 
 return self._action('os-stop', server, None)
 
 def start(self, server):
 
 Start the server.
 
 self._action('os-start', server, None)
 
 def pause(self, server):
 
 Pause the server.
 
 self._action('pause', server, None)
 
 def unpause(self, server):
 
 Unpause the server.
 
 self._action('unpause', server, None)
 
 def lock(self, server):
 
 Lock the server.
 
 self._action('lock', server, None)
 
 def unlock(self, server):
 
 Unlock the server.
 
 self._action('unlock', server, None)
 
 def suspend(self, server):
 
 Suspend the server.
 
 self._action('suspend', server, None)
 
 def resume(self, server):
 
 Resume the server.
 
 self._action('resume', server, None)

--
George Reese - Chief Technology Officer, enStratus
e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: 
+1.207.956.0217
enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com
To schedule a meeting with me: http://tungle.me/GeorgeReese

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

Re: [Openstack] Performing HPCC Benchmark on OpenStack Cloud

[Matt Joyce]

I think for HPCC you will need a significant physical system deployment
using matched configurations.  Likely your concerns will be providing
specific hardware constratins where I/O is a factor that match with what
HPCC users would use.  IE 10 gig or infiniband in networking.  Lots of
ram.  Full system instances.  SSD?  At the very least fast disks.

When we've benchmarked openstack in the past against super computing units
one of the problems we ran into was that openstack was originally designed
to run on top of commodity hardware.  Which meant that out of the gate
there was already a severe handicap unless that was taken into account.
IE.  Cost comparison.  For x dollars you get x machines.  Unless that is
taken into account it exacerbates the issues at play.

I would also focus on ensuring that painpoints that exist in existing HPCC
are tested for against openstack and vice versa.  Example... hypervisors
introduce latency in memory allocations and cpu queries.  Example...
hypervisors make deploying new configurations to the cluster simple fast
and userfriendly.

Also make sure your work loads are diverse.  Map Reduce obviously lends
itself to cloud technologies.  While some other methods do not.  More to
the point existing software for super computing applications in many cases
have no immediate corollary outside of their own custom architectures.  The
diversity of options for users would be important data as well.

It would be nice to see a more formal methodology agreed to by HPCC users.
However, most HPCC users have such unique environments and demands that
that has not been much of a priority.

-Matt

On Mon, Jul 30, 2012 at 7:22 AM, Reza Bakhshayeshi reza.b2...@gmail.comwrote:

 Hi

 I want to run HPCC benchmark on OpenStack cloud, I want you to help me to
 make the results more real.
 How can we impute the results to OpenStack and not to my computers?
 Do I really need a server farm to perform the test?
 And I think I have to run for example HPL on running instances and not on
 the main servers, is this correct?

 Please suggest me more rules and conditions.

 Best Regards

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


___
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] API docs - spec and dev guide split proposal

[Doug Hellmann]

+1 to separating specifications from documentation for API users

On Mon, Jul 30, 2012 at 1:09 PM, Anne Gentle a...@openstack.org wrote:

 Hi again all, your friendly doc coordinator here.

 I'd like to get a big push towards documenting reality instead of
 relying only on the specs stored in the compute-api repository. As an
 example, recently a Rackspace writer inserted min_count and max_count
 to the compute-api repository but the change was reversed after a
 request by Brian Waldon and Jorge Williams to leave the spec as-is. I
 agree that the spec has value but I believe we need to push towards
 reality and creating developer guides.

 So what I'd like to propose here is that we govern these repos as
 specs and change the titles of those documents to API specification:

 compute-api
 image-api
 identity-api
 object-api
 netconn-api

 At the same time, we'd start new developer guides in the
 openstack-manuals repository that document reality. We can track the
 work needed through the openstack-manuals bug and blueprint system.

 I went up to Brian Aker after his keynote at OSCon seeking contacts at
 HP who are interested in doing this type of work, and I have started
 some one-on-one meetings, but I'd like to find more interested
 collaborators. Anyone at Rightscale or Enstratus interested? Also are
 there other API implementers who are experts in how the APIs really
 work? Please join in finding the right solution here.

 Does this proposal sound like a workable solution? Any tweaks or other
 suggestions?

 Thanks,
 Anne

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

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

Re: [Openstack] Instance stuck in deleting state with error

[Kevin L. Mitchell]

On Mon, 2012-07-30 at 13:03 -0400, Jonathan Proulx wrote:
 I have an instance that has been in this state for a couple days:
 
 | OS-EXT-STS:power_state  | 0|
 | OS-EXT-STS:task_state   | deleting|
 | OS-EXT-STS:vm_state | error 
 |

If you're using the Xen driver on trunk, I recently cleaned up a few
bugs that might have lead to this problem.  Make sure you're updated and
try again…
-- 
Kevin L. Mitchell kevin.mitch...@rackspace.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] Instance stuck in deleting state with error

[Jonathan Proulx]

Well for posterity or so people can tell me what I did wrong here's
how I seemed to convince the database that  the instance was really
deleted:

UPDATE instances SET
vm_state='deleted',task_state='deleted',deleted=1,deleted_at=now()
WHERE uuid=FOO

And here's what I had to do to the volume:

 UPDATE volumes SET
attach_status='detached',instance_id=NULL,mountpoint=NULL,status='available'
WHERE id=FOO

Any insight into how I might determine what when wrong here (essex on
ubuntu 12.04 rabbitmq mysql) or if I missed any pieces that will bite
me are appreciated.

-Jon

On Mon, Jul 30, 2012 at 1:03 PM, Jonathan Proulx j...@jonproulx.com wrote:
 Hi All,

 I have an instance that has been in this state for a couple days:

 | OS-EXT-STS:power_state  | 0|
 | OS-EXT-STS:task_state   | deleting|
 | OS-EXT-STS:vm_state | error 
 |

 with this fault:

 | fault | {u'message': u'ProcessExecutionError', u'code': 500,
 u'created': u'2012-07-30T16:51:34Z'} |

 sending more delete requests seem to have no effect and the node it
 thinks it is on doesn't seem to have any state about it.

 How to I clean this up, do I just need to muck out the DB and if so
 what parts of it?

 Thanks,
 -Jon

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

Re: [Openstack] Instance stuck in deleting state with error

[Jonathan Proulx]

Thanks but I'm using KVM so not that bug...figures that's the part of
my stack I left out.

-Jon

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

Re: [Openstack] Instance stuck in deleting state with error

[Chris Behrens]

You may still have to reset the instance's task_state to NULL in the DB 
(instances table) to delete ones already in this state.

- Chris


On Jul 30, 2012, at 1:48 PM, Kevin L. Mitchell wrote:

 On Mon, 2012-07-30 at 13:03 -0400, Jonathan Proulx wrote:
 I have an instance that has been in this state for a couple days:
 
 | OS-EXT-STS:power_state  | 0
 |
 | OS-EXT-STS:task_state   | deleting|
 | OS-EXT-STS:vm_state | error
  |
 
 If you're using the Xen driver on trunk, I recently cleaned up a few
 bugs that might have lead to this problem.  Make sure you're updated and
 try again…
 -- 
 Kevin L. Mitchell kevin.mitch...@rackspace.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] Instance stuck in deleting state with error

[Kevin L. Mitchell]

On Mon, 2012-07-30 at 14:25 -0500, Chris Behrens wrote:
 You may still have to reset the instance's task_state to NULL in the
 DB (instances table) to delete ones already in this state.

No, I fixed the state problem with soft_delete(); as long as he updates,
delete should work fine.

That said, be aware that there is a reset-state command to novaclient,
so that you can do Chris's recommended reset without having to muck
around with the database directly.
-- 
Kevin L. Mitchell kevin.mitch...@rackspace.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] Keyring support in openstack

[Bhuvaneswaran A]

On Mon, Jul 30, 2012 at 6:31 AM, Doug Hellmann
doug.hellm...@dreamhost.com wrote:

 You've already answered several of my questions on the ticket, but I still
 have some usability concerns.

 How does the keyring system support a single person logging in using
 multiple user accounts? For example, if I have an admin account and a
 regular user, how do I switch between them based on the operations I need
 to perform?

The password is stored in keyring, for a given user. It also support
multiple users. The password is stored against the user specified in
command line, --os-username or environment variable OS_USERNAME.

The sample content of the keyring file ~/.openstack-keyring.cfg is as follows:
[openstack]
bhuvan = dG4wN2FjxA==
test = xYwN2FjxA==

 Is there a way to disable the behavior of having a password saved to a
 keyring for a particular user, without uninstalling the python-keyring
 package (and therefore disabling keyring support for all users)?

The simplest alternative is to specify password using other mechanism,
in command line or environment variable. It's not possible to prevent
using keyring, if password is not specified in any of these 2
mechanisms. The purpose of this patch is, to prevent password prompt.

 The wiki mentions the password being saved using
 keyring.backend.UncryptedFileKeyring. Does that mean the password is saved
 in cleartext? Is the file protected in some way besides filesystem
 permissions?

As mentioned in wiki page, the password is stored in base64 format.

 The mention of one backend implies that there are others. Should we give
 users a way to choose the backend, in case they have a preference?

python-keyring also support several other backends:
  1.CryptedFileKeyring
  2. GnomeKeyring
  3. KDEKWallet
  4. OSXKeychain
  5. Win32CryptoKeyring
  6. ... and more.

The behaviour of these backends vary for each desktop. For instance,
GnomeKeyring may prompt for keyring password, once per login session.
CryptedFileKeyring may prompt for keyring password, every time. It's
as good as not using keyring.

 How does the use of the keyring affect scripting using the command line
 tool? Can a script access the keyring, or does it need to use the other
 options?

Yes. The script could be managed with any python script, using the
same methods exposed in keyring python module.
  -- get_password() -- to get the password for given user.
  -- set_password() -- to set the password in keyring.

 In one review comment you mention a few desktop apps that know how to
 manipulate the keyring to manage its contents. What about remote access via
 ssh, where a desktop environment is not available? Does the keyring library
 include tools for manipulating the file, or do we need to build our own? If
 so, what tools would be needed?

This was applicable for older patch, wherein we rely on
desktop/environment specific backend. With older patch, if GNOME
desktop is used, GnomeKeyring backend is used; if no desktop is used,
CryptedFileKeyring backend is used. With new patch, irrespective of
whether desktop is enabled, UncryptedFileKeyring backend is used. With
this patch, the keyring behaviour is uniform across all systems in
which we deploy openstack.

In summary, the primary goal of this patch is to reuse the password
entered in the prompt once, and prevent the user from entering the
password again. Ultimately, the password is not exposed in environment
or command line (ps). It also facilitate the automated script wherein
the openstack client might be used. In such case, the password is
not read from prompt, but from keyring.
-- 
Regards,
Bhuvaneswaran A
www.livecipher.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] Keyring support in openstack

[Matt Joyce]

I like making it optional with a default of off.  At least for now.
___
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] Keyring support in openstack

[Kevin L. Mitchell]

On Mon, 2012-07-30 at 13:50 -0700, Bhuvaneswaran A wrote:
  The wiki mentions the password being saved using
  keyring.backend.UncryptedFileKeyring. Does that mean the password is
 saved
  in cleartext? Is the file protected in some way besides filesystem
  permissions?
 
 As mentioned in wiki page, the password is stored in base64 format. 

Which means it's stored in cleartext.  That is Not Good(tm) :)
-- 
Kevin L. Mitchell kevin.mitch...@rackspace.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] Keyring support in openstack

[Doug Hellmann]

On Mon, Jul 30, 2012 at 4:50 PM, Bhuvaneswaran A bhu...@apache.org wrote:

 On Mon, Jul 30, 2012 at 6:31 AM, Doug Hellmann
 doug.hellm...@dreamhost.com wrote:

  You've already answered several of my questions on the ticket, but I
 still
  have some usability concerns.
 
  How does the keyring system support a single person logging in using
  multiple user accounts? For example, if I have an admin account and a
  regular user, how do I switch between them based on the operations I
 need
  to perform?

 The password is stored in keyring, for a given user. It also support
 multiple users. The password is stored against the user specified in
 command line, --os-username or environment variable OS_USERNAME.

 The sample content of the keyring file ~/.openstack-keyring.cfg is as
 follows:
 [openstack]
 bhuvan = dG4wN2FjxA==
 test = xYwN2FjxA==


OK, that's good to know.



  Is there a way to disable the behavior of having a password saved to a
  keyring for a particular user, without uninstalling the python-keyring
  package (and therefore disabling keyring support for all users)?

 The simplest alternative is to specify password using other mechanism,
 in command line or environment variable. It's not possible to prevent
 using keyring, if password is not specified in any of these 2
 mechanisms. The purpose of this patch is, to prevent password prompt.


We're going to need to include a way in the openstack cli to disable the
use of the keyring. There will be times when users won't want passwords
saved to a keyring, or where the password that is in the keyring is wrong
or shouldn't be used for some reason. It seems like an environment variable
and a command line switch would cover all of the ways to turn the keyring
off, don't you think?



  The wiki mentions the password being saved using
  keyring.backend.UncryptedFileKeyring. Does that mean the password is
 saved
  in cleartext? Is the file protected in some way besides filesystem
  permissions?

 As mentioned in wiki page, the password is stored in base64 format.


That doesn't seem any more secure than an environment variable set from a
user's login script. What benefit does keyring give us with this
configuration?



  The mention of one backend implies that there are others. Should we give
  users a way to choose the backend, in case they have a preference?

 python-keyring also support several other backends:
   1.CryptedFileKeyring
   2. GnomeKeyring
   3. KDEKWallet
   4. OSXKeychain
   5. Win32CryptoKeyring
   6. ... and more.

 The behaviour of these backends vary for each desktop. For instance,
 GnomeKeyring may prompt for keyring password, once per login session.
 CryptedFileKeyring may prompt for keyring password, every time. It's
 as good as not using keyring.


On the other hand, different users will be running in different
configurations. Maybe they *do* have a desktop environment, and want to use
one of those real keyring managers, instead of the simple INI file
described above. Does the keyring library have some way to detect which
backends are available at runtime? Or does the application (or user) have
to specify one explicitly?



  How does the use of the keyring affect scripting using the command line
  tool? Can a script access the keyring, or does it need to use the other
  options?

 Yes. The script could be managed with any python script, using the
 same methods exposed in keyring python module.
   -- get_password() -- to get the password for given user.
   -- set_password() -- to set the password in keyring.


I was not clear. I meant could a shell script running the new cli access
the keyring. It sounds like that is not an issue, based on what you say
below.



  In one review comment you mention a few desktop apps that know how to
  manipulate the keyring to manage its contents. What about remote access
 via
  ssh, where a desktop environment is not available? Does the keyring
 library
  include tools for manipulating the file, or do we need to build our own?
 If
  so, what tools would be needed?

 This was applicable for older patch, wherein we rely on
 desktop/environment specific backend. With older patch, if GNOME
 desktop is used, GnomeKeyring backend is used; if no desktop is used,
 CryptedFileKeyring backend is used. With new patch, irrespective of
 whether desktop is enabled, UncryptedFileKeyring backend is used. With
 this patch, the keyring behaviour is uniform across all systems in
 which we deploy openstack.


That resolves my concern, but does not seem to give us any useful features.
We could achieve the same effect using just the environment variable. It
seems like we want to use the best keyring method available, if we're
going to use one at all.



 In summary, the primary goal of this patch is to reuse the password
 entered in the prompt once, and prevent the user from entering the
 password again. Ultimately, the password is not exposed in environment
 or command line (ps). It also facilitate the 

Re: [Openstack] Keyring support in openstack

[Adam Young]

On 07/30/2012 05:17 PM, Kevin L. Mitchell wrote:

On Mon, 2012-07-30 at 13:50 -0700, Bhuvaneswaran A wrote:

The wiki mentions the password being saved using
keyring.backend.UncryptedFileKeyring. Does that mean the password is

saved

in cleartext? Is the file protected in some way besides filesystem
permissions?

As mentioned in wiki page, the password is stored in base64 format.

Which means it's stored in cleartext.  That is Not Good(tm) :)
Can Keyring be used to store a token instead?  That would A)  be better 
than password and B)  avoid a Keystone hit.



___
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] Security Questons

[Briggs, Cordell A]

Hello All:

As a newbie to OpenStack, I have some concerns in regard to OpenStack security 
vulnerabilities in an HPCC environment. I am hoping that someone will be able 
to provide me with information on some security analysis that have been done on 
OpenStack.

Thanks,
Cordell
___
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] Performing HPCC Benchmark on OpenStack Cloud

[Adam Young]

On 07/30/2012 10:22 AM, Reza Bakhshayeshi wrote:

Hi

I want to run HPCC benchmark on OpenStack cloud, I want you to help me 
to make the results more real.

How can we impute the results to OpenStack and not to my computers?
Do I really need a server farm to perform the test?
And I think I have to run for example HPL on running instances and not 
on the main servers, is this correct?


Please suggest me more rules and conditions.

Best Regards


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
You need to to an apples-to-apples comparison.  Using the same hardware, 
and a different deployment mechanism, perhaps Rocks.

https://wiki.rocksclusters.org/wiki/index.php/Main_Page

You need a low latency interconnect, like Infiniband in order for the 
results to really mean much more than Yes it runs.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Nova] First nova team meeting

[Vishvananda Ishaya]

Hello Everyone,

It was recently suggested that we start a weekly nova team meeting. We used to 
use the release meeting to discuss nova issues, but due to the proliferation of 
projects, there isn't time to get deeply into nova. Also, it seems that 
nova-core could communicate a bit more, so we are holding our first nova team 
meeting on Thursday at 21:00 UTC. I apologize if this is a bad time for some of 
you, we will try to come to a consensus on meeting times there.

I've posted an agenda for things I think we need to discuss on the wiki[1]. If 
you have anything you'd like to add to the agenda, please let me know. If you 
are a nova-core member (or just do a lot of nova work), please try to be there. 
I especially want to discuss our strategy for solving some inconsistency in the 
nova api. I look forward to seeing you all on Thursday,

Vish

[1] http://wiki.openstack.org/Meetings/Nova
___
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] Security Questons

[Matt Joyce]

I have read a few master thesis' written concerning openstack's overall
security issues.  I would suggest however that openstack has been changing
drastically to date and getting a handle on its security issues is
something of a highly volatile moving target.



-Matt

Quick refs:

http://www.slideshare.net/oldbam/security-issues-in-openstack

http://nordsecmob.aalto.fi/en/programme/publications/nordsecmob_thesis_2011/thesis_slipetskyy.pdf

http://nordsecmob.aalto.fi/en/programme/publications/nordsecmob_thesis_2011/thesis_rasib_khan.pdf


On Mon, Jul 30, 2012 at 2:48 PM, Briggs, Cordell A cbri...@lanl.gov wrote:

  Hello All:

  As a newbie to OpenStack, I have some concerns in regard to OpenStack
 security vulnerabilities in an HPCC environment. I am hoping that someone
 will be able to provide me with information on some security analysis that
 have been done on OpenStack.

  Thanks,
 Cordell

 ___
 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] Keyring support in openstack

[Adam Young]

On 07/30/2012 06:00 PM, Doug Hellmann wrote:



On Mon, Jul 30, 2012 at 5:30 PM, Adam Young ayo...@redhat.com 
mailto:ayo...@redhat.com wrote:


On 07/30/2012 05:17 PM, Kevin L. Mitchell wrote:

On Mon, 2012-07-30 at 13:50 -0700, Bhuvaneswaran A wrote:

The wiki mentions the password being saved using
keyring.backend.UncryptedFileKeyring. Does that mean
the password is

saved

in cleartext? Is the file protected in some way
besides filesystem
permissions?

As mentioned in wiki page, the password is stored in
base64 format.

Which means it's stored in cleartext.  That is Not Good(tm) :)

Can Keyring be used to store a token instead?  That would A)  be
better than password and B)  avoid a Keystone hit.


Don't tokens expire?



Yes, they do, but that is no reason not to put them in the keyring,

With the PKI tokens,  you will be able to query a token's expiry without 
going across the wire.






Doug



___
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] Is reddwarf for OpenStack is dead now?

[guo lijing]

Hi ALL:

 I'm plan to do something for openstack, and I have experience of building
a database services(MySQL/Mongodb/Redis) over IaaS, so I try to find some
project like RDS for openstack,
  but I found the code of reddwarf in github haven't update for two months?
What happened to reddwarf, is the team of reddwarf decided not going to do
this project?
  I'm new guy to openstack, is anyone can tell me about reddwarf?

-- 
---
Best Regards
Lijing Guo
MSN:hua...@hotmail.com
GTALK: guolij...@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

Re: [Openstack] Instance stuck in deleting state with error

[Wolfgang Hennerbichler]

On 07/30/2012 09:35 PM, Kevin L. Mitchell wrote:


That said, be aware that there is a reset-state command to novaclient,
so that you can do Chris's recommended reset without having to muck
around with the database directly.


where?
nova help | grep reset
yields nothing.
I think this is one of openstack worst weaknesses, that if the status of 
an instance is in error-state and one has to wade through a couple of 
logfiles (scheduler, nova-network, nova-compute) in order to find out 
what really happened. I would be superior if the error itself would be 
reported back to the database.


Wolfgang

___
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] [Quantum][Nova] requested_id and port spec

[Nati Ueno]

Hi  Matt, Yong, Dan and folks

 Matt
Thank you for your comment in launchpad
https://bugs.launchpad.net/nova/+bug/1031096

Quantum team get consensus in a Netstack meeting today to propose
 port-id for requested networks. I took the job.
At first, i thought i can write extension for this. But as you say
 we should add port-id for the core API which is only used for quantum API 2.0.
My WIP code is like [1]. This change keep backward compatibility.

 Yong, Dan
Matt said you'd be breaking API compatibility and thus the API spec.

This work will change API, so some consensus in community is needed to
add port_id.
I wanna discuss about the spec in this thread.
If the community rejects this addition, I'll implement fixed_ip one
 ( see previous my message )

[1] WIP code for adding port_id ( Not tested)

+def _get_port(self, port_id):
+if FLAGS.network_api_class !=
+nova.network.quantumv2.api.API:
+msg = _(Unknown argment : port_id)
+raise exc.HTTPBadRequest(explanation=msg)
+
+if port_id and not utils.is_uuid_like(port_id):
+msg = _(Bad port format: port uuid is 
+not in proper format 
+(%s)) % port_id
+raise exc.HTTPBadRequest(explanation=msg)
+try:
+port = quantumv2.get_client(context).list_networks(**search_opts)
+if port.device_id:
+raise Exception(Port id %s is already used % port_id)
+return port
+except Exception as e:
+msg = _(This port_id can't used 
+(%s)) % port_id
+raise exc.HTTPBadRequest(explanation=msg)
+
 def _get_requested_networks(self, requested_networks):
 Create a list of requested networks from the networks attribute.
 networks = []
 for network in requested_networks:
 try:
+port_id = network.get('port_id', None)
+if port_id:
+port = self._get_port()
+network['uuid'] = port.network_id
+network['fixed_ip'] = port.fixed_ip
+

Thank you in advance
Nachi Ueno

 Hi Nachi,
 It is seemingly a way to make it work, but I think we are thinking to
 provide 'port-id' or just 'port' to specify the top resource in quantum API.
 fix ip is not one.

 Besides, Port can be assigned to more than one fixed IP.

Ah, It it true.
OK I'll implement port id version.

 Imagine in horizon, we created many networks, ports and subnets, but when
 booting a VM, we use a fixed_ip to specify our resource indirectly.

 By the way, we should use openstack-...@list.openstack.org

Sorry, I changed my mail address recently. But  launchpad rejects new
mail to receive.
I'll find way to fix this.

Thanks


Nachi

 Thanks
 Yong Sheng Gong

 -netstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -
 To: openst...@lists.openstack.org, netst...@lists.launchpad.net
 From: Nachi Ueno
 Sent by: netstack-bounces+gongysh=cn.ibm@lists.launchpad.net
 Date: 07/31/2012 08:33AM
 Subject: [Netstack] [Quantum][Nova] requested_id and port spec

 Hi Dan,folks

 As we talked in netstack IRC meetins, I submit this as bug.
 https://bugs.launchpad.net/nova/+bug/1031096

 I tried to write this, but  the code looks very ugly in order to keep
 backward compatibility.
 So I wanna propose an alternative design.
 In this design, we will use fixed_ip as a temporary identifier of the port.

 1. create port
fixed_ip assigned

 2. specify  the fixed_ip in nova boot

 3. If the fixed_ip is specified,
   nova.network.quantumv2.api.API will check existing port who use the
 fixed_ip.

   if there are existing port and device_id is None
   use the port_id.

   if there are no existing port.
create new port with the fixed_ip

 This approach needs no client side change.

 Thank you in advance
 Nachi Ueno

 --
 Mailing list: https://launchpad.net/~netstack
 Post to : netst...@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~netstack
 More help   : https://help.launchpad.net/ListHelp

--
Nachi Ueno
email:nati.u...@gmail.com
twitter:http://twitter.com/nati

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

[Openstack-ubuntu-testing-notifications] Build Failure: precise_folsom_deploy #140

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/140/Project:precise_folsom_deployDate of build:Mon, 30 Jul 2012 11:15:24 -0400Build duration:1 min 2 secBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 418 lines...]{u'glance': {u'glance-release': u'qa-precise-folsom'}, u'keystone': {u'admin-password': u'openstack',   u'admin-token': u'ubuntutesting',   u'keystone-release': u'qa-precise-folsom'}, u'nova-cloud-controller': {u'config-flags': u'quota_instances=1000,quota_cores=20,quota-ram=20,quota_volumes=1000,quota_gigabytes=1,quota_floating_ips=1000',u'network-manager': u'FlatDHCPManager',u'nova-release': u'qa-precise-folsom'}, u'nova-compute': {u'config-flags': u'auto_assign_floating_ip=True',   u'nova-release': u'qa-precise-folsom'}, u'nova-volume': {u'nova-release': u'qa-precise-folsom',  u'overwrite': u'true'}}DEBUG: Calling 'juju status'...DEBUG: Deploying with timeout 2700 sec.DEBUG: Calling: juju deploy --config=/tmp/tmpdBWXSt --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computeDEBUG: Calling: juju deploy --config=/tmp/tmpdBWXSt --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumeERROR: Juju command returned non-zero: juju deploy --config=/tmp/tmpdBWXSt --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volume- Deploying nova-compute in group 1/1- Deploying nova-volume in group 1/1Traceback (most recent call last):  File "/var/lib/jenkins/tools/juju-deployer/deployer.py", line 202, in juju_call(cmd)  File "/var/lib/jenkins/tools/juju-deployer/utils.py", line 142, in juju_callraise ExceptionException+ rc=1+ echo 'Deployer returned: 1'Deployer returned: 1+ [[ 1 != 0 ]]+ echo 'Collating logs...'Collating logs...+ /var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py -o logs2012-07-30 11:16:20,296 INFO Connecting to environment...2012-07-30 11:16:21,276 INFO Connected to environment.2012-07-30 11:16:21,640 INFO 'status' command finished successfullyINFO:root:Setting up connection to test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.tar: Removing leading `/' from member names+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: quantal_folsom_python-novaclient_trunk #33

[openstack-testing-bot]

Title: quantal_folsom_python-novaclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-novaclient_trunk/33/Project:quantal_folsom_python-novaclient_trunkDate of build:Mon, 30 Jul 2012 11:47:26 -0400Build duration:2 min 9 secBuild cause:Started by user zulBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 2152 lines...]Finished at 20120730-1149Build needed 00:00:47, 2380k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/folsom-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/folsom-trunk-testing', 'python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1_source.changes']gpg: Signature made Mon Jul 30 11:48:40 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Mon Jul 30 11:48:39 2012 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmp8cCsI4/python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp8cCsI4/python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1.dsc: done.  Uploading python-novaclient_2.6.10.24+git201207301147~quantal.orig.tar.gz: done.  Uploading python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1.debian.tar.gz: done.  Uploading python-novaclient_2.6.10.24+git201207301147~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', 'python-novaclient_2.6.10.24+git201207301147~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/p/python-novaclient/python-novaclient_2.6.10.24+git201207250027~quantal-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/python-novaclient/quantal-folsom']Pushed up to revision 50.INFO:root:Storing current commit for next build: 85d591b1d88b7e6d174c8eabd41dda14162a8bbcINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-novaclient/quantal-folsom-proposed /tmp/tmp8cCsI4/python-novaclientmk-build-deps -i -r -t apt-get -y /tmp/tmp8cCsI4/python-novaclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/python-novaclient/quantal-folsom --forcedch -b -D quantal --newversion 1:2.6.10.24+git201207301147~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1:2.6.10.24+git201207301147~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include quantal-folsom python-novaclient_2.6.10.24+git201207301147~quantal-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/python-novaclient/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 Failure: quantal_folsom_keystone_trunk #19

[openstack-testing-bot]

/configuration.rst.by dce3062editdoc/source/configuration.rstConsole Output[...truncated 4745 lines...]Build-Time: 74Distribution: quantal-folsomFail-Stage: buildInstall-Time: 50Job: keystone_2012.2+git201207301404~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 142Source-Version: 2012.2+git201207301404~quantal-0ubuntu1Space: 8444Status: attemptedVersion: 2012.2+git201207301404~quantal-0ubuntu1Finished at 20120730-1408Build needed 00:02:22, 8444k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207301404~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmpwI_VeQ/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmpwI_VeQ/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207301404~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207301404~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201207301404~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201207301404~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207301404~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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207301404~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_swift_trunk #33

[openstack-testing-bot]

Title: quantal_folsom_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/33/Project:quantal_folsom_swift_trunkDate of build:Mon, 30 Jul 2012 15:39:21 -0400Build duration:2 min 34 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesNo ChangesConsole Output[...truncated 2641 lines...]Build-Space: 19028Build-Time: 15Distribution: quantal-folsomFail-Stage: buildInstall-Time: 27Job: swift_1.6.1+git201207301539~quantal-0ubuntu1.dscPackage: swiftPackage-Time: 60Source-Version: 1.6.1+git201207301539~quantal-0ubuntu1Space: 19028Status: attemptedVersion: 1.6.1+git201207301539~quantal-0ubuntu1Finished at 20120730-1541Build needed 00:01:00, 19028k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.6.1+git201207301539~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/quantal-folsom-proposed /tmp/tmpa5OZP0/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpa5OZP0/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/swift/quantal-folsom --forcedch -b -D quantal --newversion 1.6.1+git201207301539~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1.6.1+git201207301539~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.6.1+git201207301539~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.6.1+git201207301539~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.6.1+git201207301539~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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.6.1+git201207301539~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_keystone_trunk #21

[openstack-testing-bot]

Title: quantal_folsom_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_trunk/21/Project:quantal_folsom_keystone_trunkDate of build:Mon, 30 Jul 2012 17:01:55 -0400Build duration:4 min 33 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesSet default signing_dir based on os USER.by dprinceeditkeystone/middleware/auth_token.pyConsole Output[...truncated 4756 lines...]Build-Time: 75Distribution: quantal-folsomFail-Stage: buildInstall-Time: 49Job: keystone_2012.2+git201207301702~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 139Source-Version: 2012.2+git201207301702~quantal-0ubuntu1Space: 8444Status: attemptedVersion: 2012.2+git201207301702~quantal-0ubuntu1Finished at 20120730-1706Build needed 00:02:19, 8444k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207301702~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmp05cVZt/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmp05cVZt/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207301702~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207301702~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201207301702~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201207301702~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207301702~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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207301702~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: precise_folsom_deploy #149

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/149/Project:precise_folsom_deployDate of build:Mon, 30 Jul 2012 20:03:58 -0400Build duration:15 minBuild cause:Started by user adamBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 2708 lines...]  -> Relation: nova-cloud-controller:identity-service <-> keystone:identity-service  -> Relation: glance:shared-db <-> mysql:shared-db  -> Relation: glance:identity-service <-> keystone:identity-service  -> Relation: nova-volume:shared-db <-> mysql:shared-db  -> Relation: nova-volume:amqp <-> rabbitmq:amqp  -> Relation: openstack-dashboard:identity-service <-> keystone:identity-service  -> Relation: nova-compute:shared-db <-> mysql:shared-db  -> Relation: nova-compute:amqp <-> rabbitmq:amqp  -> Relation: nova-compute:image-service <-> glance:image-service  -> Relation: nova-compute:network-manager <-> nova-cloud-controller:network-manager  -> Relation: nova-compute:identity-service <-> keystone:identity-service- Ensuring relation state- Deployment complete in 881 seconds.- Juju command log:juju deploy --config=/tmp/tmpzftgyE --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computejuju deploy --config=/tmp/tmpzftgyE --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumejuju deploy --config=/tmp/tmpzftgyE --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-cloud-controller nova-cloud-controllerjuju deploy --config=/tmp/tmpzftgyE --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystonejuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:rabbitmq rabbitmqjuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:mysql mysqljuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:openstack-dashboard openstack-dashboardjuju deploy --config=/tmp/tmpzftgyE --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:glance glancejuju add-relation keystone:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:amqp rabbitmq:amqpjuju add-relation nova-cloud-controller:image-service glance:image-servicejuju add-relation nova-cloud-controller:identity-service keystone:identity-servicejuju add-relation glance:shared-db mysql:shared-dbjuju add-relation glance:identity-service keystone:identity-servicejuju add-relation nova-volume:shared-db mysql:shared-dbjuju add-relation nova-volume:amqp rabbitmq:amqpjuju add-relation openstack-dashboard:identity-service keystone:identity-servicejuju add-relation nova-compute:shared-db mysql:shared-dbjuju add-relation nova-compute:amqp rabbitmq:amqpjuju add-relation nova-compute:image-service glance:image-servicejuju add-relation nova-compute:network-manager nova-cloud-controller:network-managerjuju add-relation nova-compute:identity-service keystone:identity-service+ rc=0+ echo 'Deployer returned: 0'Deployer returned: 0+ [[ 0 != 0 ]]+ jenkins-cli build precise_folsom_coverage+ exit 0Archiving artifactsEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #152

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/152/Project:precise_folsom_deployDate of build:Mon, 30 Jul 2012 22:13:40 -0400Build duration:34 secBuild cause:Started by user adamBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 402 lines...] u'nova-cloud-controller': {u'config-flags': u'quota_instances=1000,quota_cores=20,quota-ram=20,quota_volumes=1000,quota_gigabytes=1,quota_floating_ips=1000',u'network-manager': u'FlatDHCPManager',u'nova-release': u'qa-precise-folsom'}, u'nova-compute': {u'config-flags': u'auto_assign_floating_ip=True',   u'nova-release': u'qa-precise-folsom'}, u'nova-volume': {u'nova-release': u'qa-precise-folsom',  u'overwrite': u'true'}}DEBUG: Calling 'juju status'...DEBUG: Deploying with timeout 2700 sec.DEBUG: Calling: juju deploy --config=/tmp/tmpFBUI33 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computeDEBUG: Calling: juju deploy --config=/tmp/tmpFBUI33 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumeDEBUG: Calling: juju deploy --config=/tmp/tmpFBUI33 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-cloud-controller nova-cloud-controllerDEBUG: Calling: juju deploy --config=/tmp/tmpFBUI33 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystoneERROR: Juju command returned non-zero: juju deploy --config=/tmp/tmpFBUI33 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystone- Deploying nova-compute in group 1/1- Deploying nova-volume in group 1/1- Deploying nova-cloud-controller in group 1/1- Deploying keystone in group 1/1Traceback (most recent call last):  File "/var/lib/jenkins/tools/juju-deployer/deployer.py", line 202, in juju_call(cmd)  File "/var/lib/jenkins/tools/juju-deployer/utils.py", line 142, in juju_callraise ExceptionException+ rc=1+ echo 'Deployer returned: 1'Deployer returned: 1+ [[ 1 != 0 ]]+ echo 'Collating logs...'Collating logs...+ /var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py -o logs2012-07-30 22:14:07,495 INFO Connecting to environment...2012-07-30 22:14:08,481 INFO Connected to environment.2012-07-30 22:14:09,121 INFO 'status' command finished successfullyINFO:root:Setting up connection to test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.tar: Removing leading `/' from member names+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_folsom_deploy #153

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/153/Project:precise_folsom_deployDate of build:Mon, 30 Jul 2012 22:44:26 -0400Build duration:36 secBuild cause:Started by user adamBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 404 lines...]u'nova-release': u'qa-precise-folsom'}, u'nova-compute': {u'config-flags': u'auto_assign_floating_ip=True',   u'nova-release': u'qa-precise-folsom'}, u'nova-volume': {u'nova-release': u'qa-precise-folsom',  u'overwrite': u'true'}}DEBUG: Calling 'juju status'...DEBUG: Deploying with timeout 2700 sec.DEBUG: Calling: juju deploy --config=/tmp/tmpRTvHWO --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computeDEBUG: Calling: juju deploy --config=/tmp/tmpRTvHWO --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumeDEBUG: Calling: juju deploy --config=/tmp/tmpRTvHWO --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-cloud-controller nova-cloud-controllerDEBUG: Calling: juju deploy --config=/tmp/tmpRTvHWO --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystoneDEBUG: Calling: juju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:rabbitmq rabbitmqERROR: Juju command returned non-zero: juju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:rabbitmq rabbitmq- Deploying nova-compute in group 1/1- Deploying nova-volume in group 1/1- Deploying nova-cloud-controller in group 1/1- Deploying keystone in group 1/1- Deploying rabbitmq in group 1/1Traceback (most recent call last):  File "/var/lib/jenkins/tools/juju-deployer/deployer.py", line 202, in juju_call(cmd)  File "/var/lib/jenkins/tools/juju-deployer/utils.py", line 142, in juju_callraise ExceptionException+ rc=1+ echo 'Deployer returned: 1'Deployer returned: 1+ [[ 1 != 0 ]]+ echo 'Collating logs...'Collating logs...+ /var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py -o logs2012-07-30 22:44:55,289 INFO Connecting to environment...2012-07-30 22:44:56,248 INFO Connected to environment.2012-07-30 22:44:57,099 INFO 'status' command finished successfullyINFO:root:Setting up connection to test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-02.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-02.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.tar: Removing leading `/' from member names+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_deploy #154

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/154/Project:precise_folsom_deployDate of build:Mon, 30 Jul 2012 22:48:10 -0400Build duration:15 minBuild cause:Started by user adamBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 2721 lines...]  -> Relation: nova-cloud-controller:identity-service <-> keystone:identity-service  -> Relation: glance:shared-db <-> mysql:shared-db  -> Relation: glance:identity-service <-> keystone:identity-service  -> Relation: nova-volume:shared-db <-> mysql:shared-db  -> Relation: nova-volume:amqp <-> rabbitmq:amqp  -> Relation: openstack-dashboard:identity-service <-> keystone:identity-service  -> Relation: nova-compute:shared-db <-> mysql:shared-db  -> Relation: nova-compute:amqp <-> rabbitmq:amqp  -> Relation: nova-compute:image-service <-> glance:image-service  -> Relation: nova-compute:network-manager <-> nova-cloud-controller:network-manager  -> Relation: nova-compute:identity-service <-> keystone:identity-service- Ensuring relation state- Deployment complete in 889 seconds.- Juju command log:juju deploy --config=/tmp/tmpI2uem5 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computejuju deploy --config=/tmp/tmpI2uem5 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumejuju deploy --config=/tmp/tmpI2uem5 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-cloud-controller nova-cloud-controllerjuju deploy --config=/tmp/tmpI2uem5 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystonejuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:rabbitmq rabbitmqjuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:mysql mysqljuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:openstack-dashboard openstack-dashboardjuju deploy --config=/tmp/tmpI2uem5 --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:glance glancejuju add-relation keystone:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:amqp rabbitmq:amqpjuju add-relation nova-cloud-controller:image-service glance:image-servicejuju add-relation nova-cloud-controller:identity-service keystone:identity-servicejuju add-relation glance:shared-db mysql:shared-dbjuju add-relation glance:identity-service keystone:identity-servicejuju add-relation nova-volume:shared-db mysql:shared-dbjuju add-relation nova-volume:amqp rabbitmq:amqpjuju add-relation openstack-dashboard:identity-service keystone:identity-servicejuju add-relation nova-compute:shared-db mysql:shared-dbjuju add-relation nova-compute:amqp rabbitmq:amqpjuju add-relation nova-compute:image-service glance:image-servicejuju add-relation nova-compute:network-manager nova-cloud-controller:network-managerjuju add-relation nova-compute:identity-service keystone:identity-service+ rc=0+ echo 'Deployer returned: 0'Deployer returned: 0+ [[ 0 != 0 ]]+ jenkins-cli build precise_folsom_coverage+ exit 0Archiving artifactsEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_folsom_swift_trunk #27

[openstack-testing-bot]

Title: precise_folsom_swift_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/27/Project:precise_folsom_swift_trunkDate of build:Tue, 31 Jul 2012 00:01:54 -0400Build duration:4 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFixes regression with format=somethingelseby z-launchpadedittest/unit/account/test_server.pyedittest/unit/container/test_server.pyeditswift/container/server.pyeditswift/account/server.pyConsole Output[...truncated 3575 lines...]gpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpuG4kM1/swift_1.6.1+git201207310001~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpuG4kM1/swift_1.6.1+git201207310001~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading swift_1.6.1+git201207310001~precise-0ubuntu1.dsc: done.  Uploading swift_1.6.1+git201207310001~precise.orig.tar.gz: done.  Uploading swift_1.6.1+git201207310001~precise-0ubuntu1.debian.tar.gz: done.  Uploading swift_1.6.1+git201207310001~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'precise-folsom', 'swift_1.6.1+git201207310001~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/s/swift/python-swift_1.5.1+git201207231801~precise-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-account_1.5.1+git201207231801~precise-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-container_1.5.1+git201207231801~precise-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-doc_1.5.1+git201207231801~precise-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-object_1.5.1+git201207231801~precise-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-proxy_1.5.1+git201207231801~precise-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift_1.5.1+git201207231801~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/swift/precise-folsom']Pushed up to revision 103.INFO:root:Storing current commit for next build: de9b81baee2b9cbd87c28812ae85bc5020b06774INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/precise-folsom-proposed /tmp/tmpuG4kM1/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpuG4kM1/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 0da1b4f82d105e89729e41e45a22cf5ddc3d719a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-folsom --forcedch -b -D precise --newversion 1.6.1+git201207310001~precise-0ubuntu1 Automated Ubuntu testing build:dch -b -D precise --newversion 1.6.1+git201207310001~precise-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.6.1+git201207310001~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.6.1+git201207310001~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-trunk-testing swift_1.6.1+git201207310001~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom swift_1.6.1+git201207310001~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/swift/precise-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_keystone_trunk #22

[openstack-testing-bot]

Title: quantal_folsom_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_keystone_trunk/22/Project:quantal_folsom_keystone_trunkDate of build:Tue, 31 Jul 2012 00:31:54 -0400Build duration:6 min 3 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesAssert adminness on token validation (bug 1030968)by dolph.mathewseditkeystone/token/backends/sql.pyeditkeystone/service.pyConsole Output[...truncated 4762 lines...]Build-Time: 102Distribution: quantal-folsomFail-Stage: buildInstall-Time: 64Job: keystone_2012.2+git201207310032~quantal-0ubuntu1.dscPackage: keystonePackage-Time: 181Source-Version: 2012.2+git201207310032~quantal-0ubuntu1Space: 8444Status: attemptedVersion: 2012.2+git201207310032~quantal-0ubuntu1Finished at 20120731-0037Build needed 00:03:01, 8444k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207310032~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/keystone/quantal-folsom-proposed /tmp/tmp00CEfO/keystonemk-build-deps -i -r -t apt-get -y /tmp/tmp00CEfO/keystone/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log f648819f02135b86c4532758972769fdcb01be5e..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/keystone/quantal-folsom --forcedch -b -D quantal --newversion 2012.2+git201207310032~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 2012.2+git201207310032~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC keystone_2012.2+git201207310032~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A keystone_2012.2+git201207310032~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207310032~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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'keystone_2012.2+git201207310032~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: quantal_folsom_swift_trunk #35

[openstack-testing-bot]

Title: quantal_folsom_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/35/Project:quantal_folsom_swift_trunkDate of build:Tue, 31 Jul 2012 01:01:54 -0400Build duration:4 min 20 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesCleaner fix to format regression fixby z-launchpadeditswift/common/constraints.pyeditswift/container/server.pyeditswift/account/server.pyConsole Output[...truncated 2650 lines...]Build-Time: 18Distribution: quantal-folsomFail-Stage: buildInstall-Time: 33Job: swift_1.6.1+git201207310101~quantal-0ubuntu1.dscPackage: swiftPackage-Time: 76Source-Version: 1.6.1+git201207310101~quantal-0ubuntu1Space: 19032Status: attemptedVersion: 1.6.1+git201207310101~quantal-0ubuntu1Finished at 20120731-0106Build needed 00:01:16, 19032k disc spaceERROR:root:Error occurred during package creation/buildERROR:root:Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.6.1+git201207310101~quantal-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/quantal-folsom-proposed /tmp/tmpQ8aA5o/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpQ8aA5o/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log ceaf7606fe25f77cf31deb2946a16ae7a6fec05c..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/quantal-folsom --forcedch -b -D quantal --newversion 1.6.1+git201207310101~quantal-0ubuntu1 Automated Ubuntu testing build:dch -b -D quantal --newversion 1.6.1+git201207310101~quantal-0ubuntu1 Automated Ubuntu testing build:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.6.1+git201207310101~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.6.1+git201207310101~quantal-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.6.1+git201207310101~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 135, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.6.1+git201207310101~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: precise_folsom_deploy #158

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/158/Project:precise_folsom_deployDate of build:Tue, 31 Jul 2012 01:44:10 -0400Build duration:14 minBuild cause:Started by command lineBuilt on:masterHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 2471 lines...]  -> Relation: nova-cloud-controller:identity-service <-> keystone:identity-service  -> Relation: glance:shared-db <-> mysql:shared-db  -> Relation: glance:identity-service <-> keystone:identity-service  -> Relation: nova-volume:shared-db <-> mysql:shared-db  -> Relation: nova-volume:amqp <-> rabbitmq:amqp  -> Relation: openstack-dashboard:identity-service <-> keystone:identity-service  -> Relation: nova-compute:shared-db <-> mysql:shared-db  -> Relation: nova-compute:amqp <-> rabbitmq:amqp  -> Relation: nova-compute:image-service <-> glance:image-service  -> Relation: nova-compute:network-manager <-> nova-cloud-controller:network-manager  -> Relation: nova-compute:identity-service <-> keystone:identity-service- Ensuring relation state- Deployment complete in 832 seconds.- Juju command log:juju deploy --config=/tmp/tmpsoue2P --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-compute nova-computejuju deploy --config=/tmp/tmpsoue2P --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-volume nova-volumejuju deploy --config=/tmp/tmpsoue2P --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:nova-cloud-controller nova-cloud-controllerjuju deploy --config=/tmp/tmpsoue2P --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:keystone keystonejuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:rabbitmq rabbitmqjuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:mysql mysqljuju deploy --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:openstack-dashboard openstack-dashboardjuju deploy --config=/tmp/tmpsoue2P --repository=/var/lib/jenkins/jobs/precise_folsom_deploy/workspace local:glance glancejuju add-relation keystone:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:shared-db mysql:shared-dbjuju add-relation nova-cloud-controller:amqp rabbitmq:amqpjuju add-relation nova-cloud-controller:image-service glance:image-servicejuju add-relation nova-cloud-controller:identity-service keystone:identity-servicejuju add-relation glance:shared-db mysql:shared-dbjuju add-relation glance:identity-service keystone:identity-servicejuju add-relation nova-volume:shared-db mysql:shared-dbjuju add-relation nova-volume:amqp rabbitmq:amqpjuju add-relation openstack-dashboard:identity-service keystone:identity-servicejuju add-relation nova-compute:shared-db mysql:shared-dbjuju add-relation nova-compute:amqp rabbitmq:amqpjuju add-relation nova-compute:image-service glance:image-servicejuju add-relation nova-compute:network-manager nova-cloud-controller:network-managerjuju add-relation nova-compute:identity-service keystone:identity-service+ rc=0+ echo 'Deployer returned: 0'Deployer returned: 0+ [[ 0 != 0 ]]+ jenkins-cli build precise_folsom_coverage+ exit 0Archiving artifactsEmail 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