I fail to restart the quantum-server recently without any error log output.
root@controller:~# service quantum-server restart
stop: Unknown instance:
quantum-server start/running, process 3763
root@controller:~# service quantum-server restart
stop: Unknown instance:
quantum-server start/running,
Hi all,
Problem Description:
When a VM is launched, it cannot get a IP address. If I configure a IP
address by myself, it still cannot ping to virtual net gateway. Also,
the metadata server(169.254.169.254) is unreachable.
What the strange is, in network node, I can see dnsmasq is offering IP
Hi all,
I have set up multi-host openstack env. It works well, except for cinder.
When I create new volume, it is successful. But when attach it to one VM,
it stuck and I can not found any error in the log file. Who can give me
some advise or help about how to address this issue.
Here is the
I am using Ubuntu 12.04 Precise Pangolin with multi compute node environment
running on KVM / libvirt. The nova command that I use is nova live-migrate
instanceID hostID and via API, I am passing the same information in the
request body.
I haven't modified any configuration in the libvirt. Can
Hi Lei,
I was facing a similar issue with nova-volume on essex, so I'm not
sure if this can be useful to you ...
Where are you looking for errors? I found volume attach errors at
nova-compute.log of node where instance is running
I hope this help you
Alberto
Hi again!
Do not take into account my previous post where I'm getting an error from
glance credentials.
I found which was the problem. It was my own fault.
I was using YAML for populating Keystone and I made a mistake by replacing
with sed command.
Sorry. All is well!
Thanks!
JuanFra.
Hi all,
I would like to introduce a project I started few days ago.
The goal is to quickly build OpenStack environment with many servers,
network and storage on Amazon Web Services. It will only use templates for
Cloudformation/Heat. It can be interesting if you have to test something on
a
Thomas Goirand wrote:
[No pun intended, but it'd be nice if stackers had a bit more
consideration for our work in Debian, and stop thinking only with
Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, ... in mind.]
There is nothing Ubuntu-specific in this. And nothing bzr-specific
either. Fedora
Hello,
I allocate 2 public ips to instances, the first one becomes accessible
almost immediately, but the second one
always take a long time to be pingable. It doesn't matter which specific
IP is assigned first or second, it's always
the second one that is slow to be reachable, although the
Hi,
I got this error too but I cannot remember what did it.
Do you get this when you try and use the web interface?
Thanks,
Andrew
On Dec 17, 2012, at 6:05 PM, JuanFra Rodriguez Cardoso wrote:
Hi guys:
I've re-installed and re-configured again my deployment according to
suggested
Hi All,
I am following the high availability guide provided by openstack as seen
here: http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html
I currently have mysql and rabbitmq setup with pacemaker and corosync.
Everything seems to be working fine.
I am now adding in the
Hi,
I suggest you to read a series of our blogposts on H/A in openstack (in
this order):
http://www.mirantis.com/blog/intro-to-openstack-in-production/
http://www.mirantis.com/blog/ha-platform-components-mysql-rabbitmq/
Eugene Kirpichov wrote:
I suggest you to read a series of our blogposts on H/A in openstack (in this
order):
http://www.mirantis.com/blog/intro-to-openstack-in-production/
http://www.mirantis.com/blog/ha-platform-components-mysql-rabbitmq/
Right, you only need HA for swift-proxy where a simple load balancer suffices.
On Dec 17, 2012, at 12:42 PM, Caitlin Bestler caitlin.best...@nexenta.com
wrote:
Eugene Kirpichov wrote:
I suggest you to read a series of our blogposts on H/A in openstack (in this
order):
Hi,
For the others OpenStack components please follow:
http://www.sebastien-han.fr/blog/2012/06/28/openstack-glance-keystone-ha/
http://www.hastexo.com/blogs/martin/2012/04/03/bringing-high-availability-openstack-keystone-and-glance
Great links
thanks for these Seb :)
Le 17 déc. 2012 à 22:48, Sébastien Han han.sebast...@gmail.com a écrit :
Hi,
For the others OpenStack components please follow:
http://www.sebastien-han.fr/blog/2012/06/28/openstack-glance-keystone-ha/
Hi Andrew:
I got this error by accessing web dashboard, i.e. I introduce correctly
user/password and then I get a Internal error server in my screen
(related to traceback from my previous post).
I'm planning to use another previous version (2012.2 or 2012.1.3). Now, I'm
using 2012.2.1.
I guess
Hi, JuanFra. This usually occurs if the auth info is invalid in the authtoken
section. You can use glance --debug index ,then checkout the debug output and
watch glance-api and keystone log .
At 2012-12-17 21:52:11,JuanFra Rodriguez Cardoso
juanfra.rodriguez.card...@gmail.com wrote:
Hi
hi:
If you want to use live migration, you need a shared storage, for your
environment, NFS make be the best choice, simple and enough, keep the
instances data stored in the space, that means, instance data should
have the same absolute path between the migration machines, the start
and
On Dec 17, 2012 2:05 PM, Xin Zhao xz...@bnl.gov wrote:
Hello,
I allocate 2 public ips to instances, the first one becomes accessible
almost immediately, but the second one
always take a long time to be pingable. It doesn't matter which specific
IP is assigned first or second, it's always
the
On 18 December 2012 14:45, Hanyu Xiao hanyu.x...@eayun.com wrote:
If you want to use live migration, you need a shared storage
Not so, if you are using KVM then block migration is also an option, and it
seems to be documented in the trunk docs now too. See:
I've just finished importing the content from the MoinMoin wiki into the
MediaWiki instance. Please check the content:
https://wiki-staging.openstack.org/wiki/Main_Page
We're using a self-signed certificate for now. We are ordering a proper
certificate, but eve that cert will still appear
Hemanth ,
This would be option you would be specifying in /etc/nova/dnsmasq.conf
dhcp-option=6,dns-server
Then just kill the dnsmasq process and restart the nova-network service ,
even sometimes , you need to restart the vms, on just login into those vms
and run dhclient -v .
On Mon,
Hi Alberto,
I found the error message from computer.log on the node. Did you meet this
before?
2012-12-18 00:57:42 DEBUG nova.openstack.common.rpc.amqp [-] unpacked
context: {'project_name': u'admin', 'user_id':
u'9e0e905b3305477587d5f85889b43955', 'roles': [u'admin'], 'timestamp':
Hi Alberto,
I have fix this issue already. The root cause is that the controller(where
the cinder service located) block the 8776 port and the node can not access
the cinder service. After enable the port on the IPtables, it works.
thanks you.
On Tue, Dec 18, 2012 at 2:00 PM, Lei Zhang
Hello, list.
I've used precise-server-cloudimg-amd64-disk1.img.
And I've launched instance with keypair.
Ping is good but ssh can't access. As below log, I think due to cloud-init is
failed.
What's the problem?
$ quantum floatingip-create --port-id 413fd335-fb30-47fd-bd5e-6e3646924d52
On 12/18/2012 01:32 AM, andi abes wrote:
I've hit a similar issue when I updated from essex to folsom.
That advice to check the migration guide is wise ;).
Specifically for me, the local_settings.py file in folsom is
considerably different that it was in Essex. I'm not sure how rpm
behaves
Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/55/Project:raring_grizzly_glance_trunkDate of build:Mon, 17 Dec 2012 06:15:03 -0500Build duration:12 minBuild cause:Started by user james-pageBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/57/Project:precise_grizzly_glance_trunkDate of build:Mon, 17 Dec 2012 06:15:01 -0500Build duration:8 min 28 secBuild cause:Started by user james-pageBuilt
Title: precise_essex_deploy_proposed
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_deploy_proposed/50/Project:precise_essex_deploy_proposedDate of build:Mon, 17 Dec 2012 06:19:20 -0500Build duration:3.3 secBuild cause:Started by user yolandaBuilt
Title: precise_essex_deploy_proposed
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_deploy_proposed/55/Project:precise_essex_deploy_proposedDate of build:Mon, 17 Dec 2012 07:07:29 -0500Build duration:14 minBuild cause:Started by user james-pageBuilt
Title: precise_essex_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_deploy/18360/Project:precise_essex_deployDate of build:Mon, 17 Dec 2012 07:45:09 -0500Build duration:14 minBuild cause:Started by user yolandaBuilt on:masterHealth
Title: precise_essex_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_deploy/18361/Project:precise_essex_deployDate of build:Mon, 17 Dec 2012 08:58:28 -0500Build duration:13 minBuild cause:Started by command lineBuilt on:masterHealth
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/305/Project:precise_grizzly_nova_trunkDate of build:Mon, 17 Dec 2012 12:31:04 -0500Build duration:6 min 7 secBuild cause:Started by an SCM changeBuilt
at 20121217-2039Build needed 00:04:35, 101540k disc spaceERROR:root:Error occurred during package creation/build
35 matches
Mail list logo
