Generally if you use virsh to restart the virtual machine,it seems to be
able to use some time before shutoff again。
$ date
Thu Dec 6 17:04:41 CST 2012
$ virsh start instance-006e
Domain instance-006e started
$ virsh list
Id Name State
are that all VMs shutting down at the same time?
such as '2012-12-04 06:54:27.150+: shutting down' or near this point?
if this is true, I guess it may be the host's problem.
2012-12-06
Wangpan
发件人:pyw
发送时间:2012-12-06 17:10
主题:Re: [Openstack] Why my vm often change into shut off status
Hello,
On Thu, 2012-12-06 at 17:09 +0800, pyw wrote:
We can see this two log:
...
2012-12-03 06:14:59.819+: starting up
...
2012-12-04 06:54:27.150+: shutting down
The vm shutoff after running one day.
Without being sure, I am going to guess that you have a morning cron
To Stephen Gran:
$ ps -ef|grep 1957
root 1957 1 0 Nov22 ?02:33:06 /usr/sbin/libvirtd -d
1957 is libvirtd...
other host info:
$ free -m
total used free sharedbuffers cached
Mem: 96675 55961 40713 0561
Individual virtual machines automatically shutoff occurs frequently, this
time all the virtual machines are automatic shutoff at the same time.
If the nova failed to delete the virtual machine will cause the virtual
machine is shut down?
2012/12/6 Wangpan hzwang...@corp.netease.com
**
are
qemu: terminating on signal 15 from pid 1957
this means the VM is shutted off by libvirtd/libvirt api, the log of my VM is
same as this,
so you should check who calls the libvirt to shut down your VMs.
I have no other ideas now, good luck, guy!
2012-12-06
Wangpan
发件人:pyw
发送时间:2012-12-06
Check this Trinathhttps://bugs.launchpad.net/keystone/+bug/860885Regards,
Razique Mahroua-Nuage Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15
Le 5 déc. 2012 à 12:08, Razique Mahroua razique.mahr...@gmail.com a écrit :HI Trinath,just add the right credentials into your .bashrc or any file the
Hi-
What is the significance of api-paste.ini file in the configuration of nova
and quantum and other modules of openstack?
How this configuration is parsed and used? by which api of the openstack
modules?
My quantum api-paste.ini looks this way.
[composite:quantum]
use = egg:Paste#urlmap
/:
Hi Stackers-
I have got a doubt about a new kind of setup with Folsom. Need your help on
the doubts i have.
Lets plan that we install nova, quantum, glance, keystone, mysql-database
and Horizon components of controller in individual machines.
How Horizon will be able to get the set the
On Thu, 2012-12-06 at 16:11 +0530, Trinath Somanchi wrote:
What is the significance of api-paste.ini file in the configuration of
nova and quantum and other modules of openstack?
How this configuration is parsed and used? by which api of the
openstack modules?
So, api-paste.ini is parsed
Hi Kevin-
Thanks for the reply..
But, few of my doubts are left ...
[1] What is the significance of the api-paste.ini file in the configuration
of nova/quantum and other modules of ipenstack?
[2] How do the modules use these API configuration options? How they are
used different from normal
Honestly, I don't understand your questions; I figured the documentation
I pointed you to would answer them, and the fact it doesn't suggests
that you're not asking what I thought you were asking. Maybe an
approach from the beginning:
Nova, Quantum, Glance, Keystone, etc. all have, as
It's probably best to ask these sorts of questions on the email list, as
it gives an opportunity to others to answer them, as well as allowing
others who may have similar questions to see the answers in the first
place.
On Thu, 2012-12-06 at 23:24 +0530, Trinath Somanchi wrote:
[1] In nova or
Hello Guys,
I'm trying to install OpenStack on Debian Wheezy, but i'm getting some
problems with keystone, when i try to create a user in a tenant using
the --tenant-id command, it returns the error: keystone: error:
unrecognized arguments: --service-id service-id number.
Does anybody knows if
Thanks a lot kevin..
Your explanation has cleared my doubts..
Keeping togethor what i understand...
Suppose, we have a resquest to Nova..
The following steps are performed...
1. The request is captured by webob and is authenticated by keystone and is
decorated to wsgi app
2. Nova-api maps the
On Thu, Dec 06, 2012 at 04:21:49PM -0200, Guilherme Russi wrote:
Hello Guys,
I'm trying to install OpenStack on Debian Wheezy, but i'm getting some
problems with keystone, when i try to create a user in a tenant using
the --tenant-id command, it returns the error: keystone: error:
Seems like a good start to a wiki page to me :)
Sent from my digital shackles
On Dec 6, 2012, at 11:27 AM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
Honestly, I don't understand your questions; I figured the documentation
I pointed you to would answer them, and the fact it
It sounds like you *could* start updating and submitting it, but with the
knowledge that you’ll have to continue to tweak it just as the JSON spec is
being tweaked during development. So your options are to maintain it as such or
wait until it’s declared FINAL and then do the work later on but
Hi Razique,
Following is the info you requested:
root@novato:~# pvdisplay
--- Physical volume ---
PV Name /dev/loop2
VG Name cinder-volumes
PV Size 10.00 GiB / not usable 4.00 MiB
Allocatable yes
PE Size 4.00 MiB
On Thu, 2012-12-06 at 23:58 +0530, Trinath Somanchi wrote:
Suppose, we have a resquest to Nova..
The following steps are performed...
1. The request is captured by webob and is authenticated by keystone
and is decorated to wsgi app
Not quite correct; webob decorates (some of) the
Hi Antonio,
It sounds like you might be using the wrong credentials. The S3 layer works
with the EC2 credentials.
On 6 December 2012 06:33, Antonio Messina arcimbo...@gmail.com wrote:
Hi all,
I'm trying to access SWIFT using the S3 API compatibility layer, but I
always get an
Hi Stackers-
I have a doubt with respect to the Quantum OVS Plugin.
[1] Do all the APIs of Quantum use the Quantum OVS plugin to get the data
from the database. or they directly contact the database.
Since, I have seen ovs_quantum_plugin.py code, it has create_network,
update_network methods
Hi Kevin-
Thanks for the reply and making me understand the data flow.
I have one more doubt in plate.
I see that in api-paste.ini, with respect to the online available
documentation
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/110/Project:precise_grizzly_quantum_trunkDate of build:Thu, 06 Dec 2012 07:01:01 -0500Build duration:1 min 42 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/112/Project:raring_grizzly_quantum_trunkDate of build:Thu, 06 Dec 2012 07:01:01 -0500Build duration:2 min 25 secBuild cause:Started by an SCM changeBuilt
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/1372/
--
Started by timer
Building remotely on pkg-builder
[cloud-archive_folsom_version-drift] $ /bin/bash -xe
/tmp/hudson508026125332658966.sh
+ OS_RELEASE=folsom
+
See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/1373/
--
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe :
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/111/Project:precise_grizzly_quantum_trunkDate of build:Thu, 06 Dec 2012 09:31:01 -0500Build duration:1 min 39 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/113/Project:raring_grizzly_quantum_trunkDate of build:Thu, 06 Dec 2012 09:31:00 -0500Build duration:2 min 23 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/115/Project:raring_grizzly_quantum_trunkDate of build:Thu, 06 Dec 2012 11:09:31 -0500Build duration:8 min 19 secBuild cause:Started by user james-pageBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/241/Project:precise_grizzly_nova_trunkDate of build:Thu, 06 Dec 2012 12:05:02 -0500Build duration:3 min 14 secBuild cause:Started by user james-pageBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/243/Project:raring_grizzly_nova_trunkDate of build:Thu, 06 Dec 2012 12:04:50 -0500Build duration:5 min 22 secBuild cause:Started by user james-pageBuilt
Title: precise_grizzly_keystone_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_keystone_trunk/48/Project:precise_grizzly_keystone_trunkDate of build:Thu, 06 Dec 2012 12:12:02 -0500Build duration:5 min 20 secBuild cause:Started by user
at 20121206
Title: raring_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/244/Project:raring_grizzly_nova_trunkDate of build:Thu, 06 Dec 2012 12:10:23 -0500Build duration:19 minBuild cause:Started by user james-pageBuilt
See http://10.189.74.7:8080/job/precise_folsom_coverage/336/
--
Started by command line
Building on master
No emails were triggered.
[workspace] $ /bin/bash -x /tmp/hudson4115235006440770384.sh
+
See http://10.189.74.7:8080/job/precise_folsom_coverage/337/
--
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
Title: raring_grizzly_python-cinderclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_python-cinderclient_trunk/13/Project:raring_grizzly_python-cinderclient_trunkDate of build:Thu, 06 Dec 2012 20:31:01 -0500Build duration:2 min 35 secBuild
at 20121206
39 matches
Mail list logo