Hi Edward,
Are you using Simple.Scheduler? I think it must be related to max_cores
option.
max_cores default value is 16, you can override it in nova.conf
max_cores = 24
cpu_allocation_ratio (vCPU/CPU ratio) default value is 1, if you want to
use more virtual cores:
cpu_allocation_ratio = ...
Dear Alberto:
Great!
It's workable. It occur nova-scheduler issue.
So change max_cores
Thank you!!
Edward
-Original Message-
From: openstack-bounces+edward_doong=wiwynn@lists.launchpad.net
[mailto:openstack-bounces+edward_doong=wiwynn@lists.launchpad.net] On
Behalf Of
hello,
sorry for the delay but after a restart i have to deal with another problem
and without being able to check the previous 'utf8' codec error.
2012-11-15 10:43:24ERROR [root] %d format: a number is required, not
dict
Traceback (most recent call last):
File
Hi folks ,
I'm testing the s3backer for swift via swift3.
It works fine.
For my environment , the swift-bench could handle 120MB/s .(each object for
1MB)
But while I'm using s3backer (block-size set to 1MB) , using dd to test the
speed . Result only 20~40MB/s.
Does anyone experience with the
Hello,
The Ceilometer team would like to have your input on how to prioritize
features in the next release. We need to sanity check our current plan
and while we cannot guarantee that the most popular feature will get
implemented (unless YOU implement it, of course), your point of view
does
On Tue, Nov 13 2012, Joe Warren-Meeks wrote:
Hi Joe,
When I use a floating IP in the 10.0.40.0/24 range, it is fine to speak to
that network and traffic goes out and back on the vlan40 interface, but for
all other networks it is routed out the 10.0.0.250 eth0 interface, rather
than vlan40.
On 11/15/2012 08:49 AM, G. Lekatsas wrote:
hello,
sorry for the delay but after a restart i have to deal with another problem and without
being able to check the previous 'utf8' codec error.
File /usr/lib/python2.6/site-packages/keystone/catalog/backends/sql.py,
line 169, in
Hi guys,
The blueprint is registered :
https://blueprints.launchpad.net/ceilometer/+spec/hbase-storage-backend, Any
idea what's the next step ? :)
Shengjie
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
No, it's optional.
Token validation returns what it normally does. The only thing belongs to does
is that you fail token validation if the given tenant is not covered by the
scope of the token.
-jOrGe W.
On Nov 14, 2012, at 11:18 PM, Yee, Guang wrote:
Is belongsTo mandatory? If not, what
On Thu, Nov 15 2012, shengjie_...@dell.com wrote:
The blueprint is registered :
https://blueprints.launchpad.net/ceilometer/+spec/hbase-storage-backend, Any
idea what's the next step ? :)
Implementing? :)
And eventually adding more blueprint to depends on if you can't
implement this one
Do you plan to implement it? Per my understanding, If yes, then begin
implementation, and don't forget to add something like for bp in your
patch. Otherwise, wait someone who has interests to work on it :)
Thanks
--jyh
-Original Message-
From:
Hi stackers,
Just like Nova does have the nova-manage service list to check on how
well the nova-services are running in all the nodes, i suggest that
quantum does the same. After all, we have the l3-agent, dhcp agent,
quantum server and many plugin agents running in different nodes and it
Hi All,
I am looking for a good guide to help me get started with Folsom and
Quantum for either 12.04 or 12.10.
I have been attempting to use: goo.gl/vIdcr but when I get to section
5 (openvswitch) I get an error (SIOCADDRT: no such process) when
trying to set the interface for the default
Implementing? :)
And eventually adding more blueprint to depends on if you can't implement
this one directly because of some missing stuff.
Two questions:
1. Does it need to be approved first, what's the process to get it
approved/assigned to a release? Btw, I was trying to add Julien in
On Thu, Nov 15 2012, shengjie_...@dell.com wrote:
1. Does it need to be approved first, what's the process to get it
approved/assigned to a release? Btw, I was trying to add Julien in the
approver list as well, didn't manage to do that.
I don't think we've been anything formal so far about
Hi Sam,here is an official guide to start withhttp://docs.openstack.org/trunk/openstack-compute/install/apt/content/ap_installingfolsomubuntuprecise.htmlNote that at the moment, the official quantum packages contain bugs - I'm thinking about the l3 agent for instance.Let us know how it's goingBest
Are you talking about this l3 bug ?
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/Tricks%26Ideas/modify_iptables_manager.rst
Le 15/11/2012 16:06, Razique Mahroua a crit:
Hi Sam,
here is an
Yup, exactly :)thanks man for the fix. I wasn't sure myself which line to update, since according to the commit there are much moreRaz
Nuage Co - Razique Mahrouarazique.mahr...@gmail.com
Le 15 nov. 2012 à 16:10, Skible OpenStack skible.openst...@gmail.com a écrit :
Are you
Hi,
A considerable effort has been made to close a number of problems in
the Folsom release.
The list of issues addressed can be seen at
https://review.openstack.org/#/q/status:merged+project:openstack/quantum+branch:stable/folsom,n,z
There are still a few bug fixes in
On 11/15/2012 04:30 PM, Samuel Winchenbach wrote:
Hi All,
I am looking for a good guide to help me get started with Folsom and
Quantum for either 12.04 or 12.10.
Please look at
http://docs.openstack.org/trunk/openstack-network/admin/content/index.html.
There is a demo section.
You can
I believe that the biggest problem is
not bug fixes, we are able to fix them out by our selves.
Instead, we do need that Dashboard able to communicate with
the quantum to allocate floating IP
Does anyone have an idea about the date ?
Le
Can you please tell me what type of networking are you using ? VLAN or GRE ?
Le 15/11/2012 16:16, Gary Kotton a écrit :
On 11/15/2012 04:30 PM, Samuel Winchenbach wrote:
Hi All,
I am looking for a good guide to help me get started with Folsom and
Quantum for either 12.04 or 12.10.
Please
On 11/15/2012 05:22 PM, Skible OpenStack wrote:
Can you please tell me what type of networking are you using ? VLAN or
GRE ?
In the examples we are using VLAN.
Le 15/11/2012 16:16, Gary Kotton a écrit :
On 11/15/2012 04:30 PM, Samuel Winchenbach wrote:
Hi All,
I am looking for a good
On 11/15/2012 05:17 PM, Skible OpenStack wrote:
I believe that the biggest problem is
not bug fixes, we are able to fix them out by our selves.
Instead, we do need that Dashboard able to communicate with
the quantum to allocate floating IP
Is it possible, in any version of openstack, to have multiple public
interfaces on a compute node, with separate floating ip pools per interface?
I want to use one per tenant. I can't find anything in any docs about it.
Kind regards
-- joe.
___
Yes, after recreating the endpoints i see with #keystone endpoint-list
+--+---+++-+
|id
Hello to all!
I have a problem with nova-compute daemon, start-up fails with following
error:
2012-11-15 19:14:34 INFO nova.compute.manager [-] Loading compute driver
'libvirt.LibvirtDriver'
2012-11-15 19:14:34 ERROR nova.compute.manager [-] Unable to load the
virtualization driver: Class
Hello,
I am following the document OpenStack Deploy and Install Guide to bring up a
OpenStack setup. Per the instructions in the document, is the controller node
also acting as the compute node. By that I mean when a VM is created, it
created on the controller node. Is that right? And
The controller node can not host vms. But an All-in-one node can, because
it is a combination of controller and compute.
On Thu, Nov 15, 2012 at 12:53 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:
Hello,
I am following the document OpenStack Deploy and Install Guide to bring
up a OpenStack
Is your statement based on the setup noted in the OpenStack Install and Deploy
Manual? I am question was more specific to the setup covered in the afore
mentioned document.
In general, does the answer not depend on what services are installed on the
controller node, to give it ability to be
On Thu, Nov 15, 2012 at 12:36 PM, Nikola Pajtic salge...@gmail.com wrote:
Hello to all!
I have a problem with nova-compute daemon, start-up fails with following
error:
2012-11-15 19:14:34 INFO nova.compute.manager [-] Loading compute driver
'libvirt.LibvirtDriver'
2012-11-15 19:14:34 ERROR
On Thu, Nov 15, 2012 at 1:40 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:
Is your statement based on the setup noted in the OpenStack Install and
Deploy Manual? I am question was more specific to the setup covered in
the afore mentioned document.
Specific to that guide, the controller node
Without belongsTo, you can still validate the tenant scope client-side, so
it's a bit redundant. However, if you're making a HEAD call to validate the
token, you obviously need the server to do that additional validation for
you.
-Dolph
On Thu, Nov 15, 2012 at 8:20 AM, Jorge Williams
Hi all,
I tried to add a third compute node to a running openstack platform
(composed of a head node and a compute node).
I use Ubuntu 12.04 + XCP + folsom (stable release). And, I use devstack to
install the compute node.
The first problem is that the 2nd (new) compute node is not able to see
Hi Anne,
Thank you very much for the clarification. I was thinking along the lines
of your explanation (since nova-compute is being installed on the
controller node per the doc), however your explanation solidified my
understanding.
As a suggestion, it would be good to incorporate this info
The first problem has been solved by synchronizing the 2 nodes.
But, I could not find a solution to the second one -- nova-compute does not
want to start
2012/11/15 Afef MDHAFFAR afef.mdhaf...@gmail.com
Hi all,
I tried to add a third compute node to a running openstack platform
(composed of
I was about to reply, but Anne covered it up perfectly :) (as usual)
Nuage Co - Razique Mahrouarazique.mahr...@gmail.com
Le 15 nov. 2012 à 20:49, Anne Gentle a...@openstack.org a écrit :On Thu, Nov 15, 2012 at 1:40 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:Is your statement based on the setup
On Thu, Nov 15, 2012 at 2:18 PM, Ahmed Al-Mehdi ah...@coraid.com wrote:
Hi Anne,
Thank you very much for the clarification. I was thinking along the lines
of your explanation (since nova-compute is being installed on the
controller node per the doc), however your explanation solidified my
(inline)
On Nov 15, 2012, at 2:06 PM, Dolph Mathews wrote:
Without belongsTo, you can still validate the tenant scope client-side, so it's
a bit redundant.
Not sure what you mean. Can you be more specific?
However, if you're making a HEAD call to validate the token, you obviously need
the
Following up on today's Nova meeting, I am checking to see if anyone is
still using the old (essex, folsom) baremetal driver. There has been a lot
of work done on replacing this driver by folks at NTT, ISI, HP, and
elsewhere, including both a talk and session at the Grizzly summit.
As far as I
Hello,
On the compute node (IP addr : 10.176.20.4) I am seeing the following error
message in /var/log/nova/nova-compute.log:
2012-11-15 14:11:12 INFO nova.openstack.common.rpc.common [-] Reconnecting to
AMQP server on localhost:5672
2012-11-15 14:11:12 ERROR nova.openstack.common.rpc.common
Trye to start your nova-compute with --config-file {your nova.conf}. and
look at the log at the beginning to see what options values are used truly.
On 11/16/2012 06:17 AM, Ahmed Al-Mehdi wrote:
Hello,
On the compute node (IP addr : 10.176.20.4) I am seeing the following
error message in
Yeah, that worked!!! Thanks a lot, Doug, for pointing me in right
direction!! Nova-compute finally up and running.
Although, I had some trouble with VIF driver. nova-compute.log threw an
error, saying it cannot find
nova.virt.libvirt.vif.LibvirtHybirdOVSBridgeDriver (even it had full module
path
Thank you for your help. Actually, I just restarted the service ( service
nova-compute restart ), I am not seeing the error anymore.
Do you know if there is a command to get a list of the current config values in
nova?
Does nova-compute running on the compute node register itself with the
I don't know there exists a such command. But these values will be
printed during nova-computer starting.
I think nova-compute is using db to report its existence, and using MQ
to reports its capabilities to nova-scheduler
On 11/16/2012 06:47 AM, Ahmed Al-Mehdi wrote:
Thank you for your help.
Hi Ahmed,
You can use the command nova-manage service list from the command line of
control node to get the list of compute nodes along with the nova-compute
service status.
Thanks
Krishnaprasad Narayanan
From:
Hi Ahmed,
and with nova host-xxx as assistance.
On 11/16/2012 07:29 AM, Narayanan, Krishnaprasad wrote:
Hi Ahmed,
You can use the command nova-manage service list from the command line of
control node to get the list of compute nodes along with the nova-compute service status.
Thanks
Yes, this has been suggested before and I think would be valuable. One
complication is that in quantum, there are multiple possible
implementations (e.g., some plugins require agents, others don't), but I
think it would be possible to abstract things in a way that are useful
(e.g., show the
Thanks for your comments. This is all good feedback. A couple of things to
mention:
1) The l3-agent rootwrap error mentioned earlier in the thread is in
stable/folsom and according to launchpad was added to the Ubuntu stable
release archive about a week ago. see:
I think we have already Bp for this:
https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler
also the quantum agents multi-hosts and multiple dhcp agents and l3
agents will depend on it.
On 11/16/2012 08:02 AM, Dan Wendlandt wrote:
Yes, this has been suggested before and I think
On Thu, Nov 15, 2012 at 4:11 PM, Dan Wendlandt d...@nicira.com wrote:
Thanks for your comments. This is all good feedback. A couple of things
to mention:
1) The l3-agent rootwrap error mentioned earlier in the thread is in
stable/folsom and according to launchpad was added to the Ubuntu
Hi Narayanan,
Awesome, thank you. There reason I was not seeing the nova-compute
listed is because it did not launch on the compute node. I did a manual
start of nova-compute on the compute node, and I do see it listed on the
control-node but with XXX State.
root@bodega:~/ahmed/new_guide#
The assessment criteria is clear, that IaaS provider measures the whole cloud
stack every time when it creates a new release, and then is compared to the
run-time measurements on the running stack on the hosts in so-called
attestation process. A failed attestation implicates the host is
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/101/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 03:31:23 -0500Build duration:6 min 12 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/102/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 04:01:24 -0500Build duration:6 min 23 secBuild cause:Started by an SCM changeBuilt
at 20121115-1035Build needed 00:01:39, 11208k disc spaceERROR:root:Error occurred
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/43/Project:precise_grizzly_quantum_trunkDate of build:Thu, 15 Nov 2012 12:01:21 -0500Build duration:1 min 38 secBuild cause:Started by an SCM changeBuilt
Output[...truncated 6839 lines...]Finished at 20121115-1208Build needed 00:04:40, 51780k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'quantum_2013.1+git201211151201~raring-0ubuntu1.dsc']' returned non-zero exit status
Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/11/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Thu, 15 Nov 2012 13:01:21 -0500Build duration:2 min 45
Title: raring_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/44/Project:raring_grizzly_quantum_trunkDate of build:Thu, 15 Nov 2012 13:03:28 -0500Build duration:7 min 37 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/103/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 13:31:24 -0500Build duration:7 min 45 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/19/Project:precise_grizzly_glance_trunkDate of build:Thu, 15 Nov 2012 14:31:22 -0500Build duration:1 min 47 secBuild cause:Started by an SCM changeBuilt
at 20121115-1604Build needed 00:01:34, 884k disc spaceERROR:root:Error
at 20121115-1605Build needed 00:01:58, 888k disc spaceERROR:root:Error
at 20121115
at 20121115-1634Build needed 00:01:47, 888k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild
at 20121115
Title: precise_grizzly_python-swiftclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-swiftclient_trunk/2/Project:precise_grizzly_python-swiftclient_trunkDate of build:Thu, 15 Nov 2012 17:01:21 -0500Build duration:2 min 53 secBuild
Title: precise_grizzly_python-swiftclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-swiftclient_trunk/3/Project:precise_grizzly_python-swiftclient_trunkDate of build:Thu, 15 Nov 2012 17:31:21 -0500Build duration:2 min 47 secBuild
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/104/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 17:33:56 -0500Build duration:3 min 7 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/106/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 17:34:09 -0500Build duration:4 min 18 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/45/Project:precise_grizzly_quantum_trunkDate of build:Thu, 15 Nov 2012 18:01:22 -0500Build duration:2 min 15 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/107/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 18:03:38 -0500Build duration:5 min 28 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/105/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 18:06:39 -0500Build duration:2 min 26 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_quantum_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/45/Project:raring_grizzly_quantum_trunkDate of build:Thu, 15 Nov 2012 18:01:24 -0500Build duration:9 min 52 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/107/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 21:04:09 -0500Build duration:3 min 6 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-keystoneclient_trunk/74/Project:quantal_folsom_python-keystoneclient_trunkDate of build:Thu, 15 Nov 2012 21:07:16 -0500Build duration:1 min 22
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/109/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 21:05:18 -0500Build duration:4 min 51 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/106/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 20:31:23 -0500Build duration:2 min 50 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/108/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 20:31:23 -0500Build duration:4 min 21 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/110/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 21:31:25 -0500Build duration:4 min 39 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/109/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 22:01:25 -0500Build duration:2 min 25 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/111/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 22:01:24 -0500Build duration:3 min 51 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/110/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 22:31:23 -0500Build duration:2 min 30 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/112/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 22:31:23 -0500Build duration:3 min 37 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-keystoneclient_trunk/75/Project:quantal_folsom_python-keystoneclient_trunkDate of build:Thu, 15 Nov 2012 23:01:21 -0500Build duration:1 min 13
Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/13/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Thu, 15 Nov 2012 23:01:21 -0500Build duration:2 min 45
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/113/Project:raring_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 23:03:50 -0500Build duration:3 min 44 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-keystoneclient_trunk/76/Project:quantal_folsom_python-keystoneclient_trunkDate of build:Thu, 15 Nov 2012 23:31:21 -0500Build duration:1 min 10
Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/14/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Thu, 15 Nov 2012 23:31:21 -0500Build duration:2 min 38
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/112/Project:precise_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 00:01:23 -0500Build duration:2 min 30 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/114/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 00:01:28 -0500Build duration:3 min 59 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/115/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 00:31:24 -0500Build duration:3 min 43 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/46/Project:precise_grizzly_quantum_trunkDate of build:Fri, 16 Nov 2012 01:01:21 -0500Build duration:2 min 5 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/116/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 01:05:46 -0500Build duration:3 min 29 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/115/Project:precise_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 01:31:23 -0500Build duration:2 min 24 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/117/Project:raring_grizzly_nova_trunkDate of build:Fri, 16 Nov 2012 01:31:23 -0500Build duration:3 min 46 secBuild cause:Started by an SCM changeBuilt
97 matches
Mail list logo
