Hi All,
I'm rying to install OpenStack Essex and when I run the nova-manage db
sync from this doc's part
http://docs.openstack.org/essex/openstack-compute/install/apt/content/compute-db-sync.html,
it
returs these errors:
2012-12-10 10:56:57 DEBUG nova.utils [-] backend from
(pid=6208) __get_bac
Hi:
It's simply a warning message.
I guess that next releases (Folsom, Grizzly...) will not use this
deprecated argument.
Regards,
2012/12/10 Guilherme Russi
> Hi All,
>
> I'm rying to install OpenStack Essex and when I run the nova-manage db
> sync from this doc's part
> http://docs.openst
Hi Lei,
I could spend some more time looking at my "no route to host" issue today.
I could be very well that the iptables on VM is the root of the problem.
Here is what it looks like.
*$ sudo iptables -L*
*Chain INPUT (policy ACCEPT)*
*target prot opt source destination
Maybe you need to enable the following flag in nova.conf:
resume_guests_state_on_host_boot=True
The default is False it seems (Didn't confirm it), so if you expect the
machines to be in running state when you reboot the host, you should enable
that flag. Although it seems your problem seems to be
Hi again guys,
I'm sorry for all these questions, but when I learn how to install it I'll
help people with these same problems, well, I'm trying to run a VM instance
on Essex, a ubuntu image, but when I try to boot it the OS-EXT-STS:vm_state
is error.
What am I missing?
Thank you all again.
Gu
Hi,
The simplest way to check is to have a look at /var/log/nova/nova-compute.log
Regards,
Gabriel
From: Guilherme Russi
To: openstack@lists.launchpad.net
Sent: Monday, December 10, 2012 6:15 PM
Subject: [Openstack] Problem hen running VM instances
Hi aga
Hello.
I've been "playing" around with OpenStack, when I noticed a section in the
Dashboard where you can create/delete volume types. The problem is, I
didn't understand their purpose, as when you create a new type, you only
specify its name. Can anyone tell me what are volume types used for?
Tha
Ooops... I got it. Thought nova-compute has responsibilities in local
iptables settings.
I guess I was misled by the fact that I have default iptables rules setup
at boot time in my VM which looks like rules defined in security group but
it's just a coincidence.
Thanks
Patrick
2012/12/10 Patrick
Hi,
I cannot start the nova-api service.
[root@blade02 07-openstack-controller]# nova list
ERROR: ConnectionRefused: '[Errno 111] Connection refused'
I followed this guide very carefully:
https://github.com/beloglazov/openstack-centos-kvm-glusterfs/#07-openstack-controller-controller
Here is a
On Mon, Dec 10, 2012 at 10:05 AM, Daniel Oliveira wrote:
> Hello.
>
> I've been "playing" around with OpenStack, when I noticed a section in the
> Dashboard where you can create/delete volume types. The problem is, I
> didn't understand their purpose, as when you create a new type, you only
> spec
Odd. This looks remarkably like it is trying to start osapi_volume even though
you don't have it specified in enabled apis. Your enabled_apis setting looks
correct to me.
Vish
On Dec 10, 2012, at 9:24 AM, Andrew Holway wrote:
> Hi,
>
> I cannot start the nova-api service.
>
> [root@blade02
Check if you have any space in the instances dir in the filesystem. I've seen
this happen when the drive gets full and libvirt gets an io error trying to
write to disk so it shuts off the vms.
Vish
On Dec 5, 2012, at 6:59 PM, pyw wrote:
> My virtual machine created, often in the absence of in
Awesome.Feel free to file a blueprint for it. I also discussed with some people the other day the idea of allowing some additions to the config drive api to allow you to specify an unattend.xml when booting an instance that would put it in the proper place on the config drive. We could create an ex
Hi,
maybe this will shed some light on it..?
Thanks,
Andrew
[root@blade02 init.d]# cat /etc/nova/api-paste.ini
# Metadata #
[composite:metadata]
use = egg:Paste#urlmap
/: meta
[pipeline:meta]
pipeline = ec2faultwrap logrequest metaapp
[app:metaapp]
paste.app_factory
On Dec 5, 2012, at 7:19 PM, Lei Zhang wrote:
> thank you very much, Vishvananda.
> But I am still confused about the 192.168.0.0/24 and the 10.0.0.0/8 ip. What
> means by "The addresses will be moved on to the bridge". It means the
> 192.168.0.0/8 will be disappear? In my opinion, the bridged
It gets the endpoint configuration from keystone. Everything has to know where
the keystone server is and it can use the service catalog to talk to the other
services.
Vish
On Dec 6, 2012, at 3:20 AM, Trinath Somanchi wrote:
> Hi Stackers-
>
> I have got a doubt about a new kind of setup wit
Nope. Best i can think of is to throw some log statements into nova/service.py
right before the exception gets thrown. See which api it is trying to start and
what it thinks the value of enabled_apis is. Etc.
Vish
On Dec 10, 2012, at 10:24 AM, Andrew Holway wrote:
> Hi,
>
> maybe this will s
Hallo All,
I am trying to use the Nova API (POST call) for changing the flavor information
(to resize) from m1.tiny to m1.medium. Even though the API is successful (202
Status code), on the Horizon GUI I could see that the Status is Error and the
task state is Resize Prep. I am passing the Auth
Hi,
I have actually no idea how do do that. But the service opts look vaguely
relevant:
Does anyone have a working installation on Centos 6.3?
Thanks,
Andrew
service_opts = [
cfg.IntOpt('report_interval',
default=10,
help='seconds between nodes reporting st
I just realized the problem. Your issue is actually the metadata api since you
have something listening on 8775. If you are running nova-api-metadata
separately then you can remove it from your list of enabled apis:
enabled_apis=ec2,osapi_compute
Alternatively just kill nova-api-metadata and al
2 requirements:
1) hostname for compute hosts resolve properly
2) passwordless ssh works between compute hosts.
Vish
On Dec 10, 2012, at 10:37 AM, "Narayanan, Krishnaprasad"
wrote:
> Hallo All,
>
> I am trying to use the Nova API (POST call) for changing the flavor
> information (to resize
Hi Vish,
Thanks for the quick reply. I have passwordless ssh between the compute hosts
but could you explain me the first option. When I resize, will the instance
redeploy on a different compute node?
Do I need to specify this flag allow_resize_to_same_host=true in nova.conf of
the compute no
Hey,
Thanks, That seems to have done it!
Now I have some whole new errors to work on :)
2012-12-10 20:08:44 ERROR keystone.middleware.auth_token [-] HTTP connection
exception: [Errno 1] _ssl.c:490: error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol
2012-12-10 20:08:44 WARNING
If you mean different types like block or file-oriented volume, there was a
thread about that (http://markmail.org/message/ptwohhhaltcbqii2)
Briefly, you had to code a volume driver matches your needs (
http://docs.openstack.org/developer/nova/api/nova.volume.driver.htmlI)
Regards,
JuanFra.
2012/
Hi,
Please excuse dumb questions. Im very new to openstack.
So I have just managed to get the nova-api service running (thanks virsh) but
it seems to be having a little problem with auth.
[root@blade02 07-openstack-controller]# nova list
ERROR: n/a (HTTP 401)
[root@blade02 07-openstack-control
Hi,
Any plan to support HA (High Availability) in glance api service? I noticed in
Folsom it comes with a tool to facilitate the replication of glance api service
(see the following link),
http://docs.openstack.org/trunk/openstack-compute/admin/content/replicating-images.html
But to automatica
The code scps the backing file for the instance to the new node via something
along the lines of:
scp /var/lib/nova/instances/instance-xxx/disk
:/var/lib/nova/instances/instance-xxx/disk
So the hostname has to properly resolve to the ip of the target machine. You
should see messages in the compu
It was this little fella in my nova.conf :)
On Dec 10, 2012, at 8:35 PM, Andrew Holway wrote:
> #[keystone_authtoken]
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~
I don't see any errors in your network log. are nova-network and nova-compute
running on the same host with the same config file? It looks like it isn't
recieving a message. Are you running another nova-network that is picking up
the message on another host?
Vish
On Dec 10, 2012, at 12:18 PM,
Hello,
I have a Dashboard install.
/dashboard/syspanel/volumes/ & /dashboard/nova/volumes/ causes a 500 error.
The 500 goes away when I run
$nova-api-os-volume
I also have a
$/etc/init.d/openstack-nova-volume start
Which doesn't make the 500 error go away.
Can someone tell me what nova-a
Check rabbitmqctl list_queues and see if there are queues that have nonzero
entries. That means messages are being sent but not picked up by the nodes. If
the nova-networks are hanging they are probably stuck waiting on a lock files.
I believe the lock files are in /var/lock/nova by default. You
The recommended way is to run cinder. The config that you showed before was not
running osapi_volume as one of your enabled apis.
Prior to folsom the way was to enable osapi_volume or run nova-api-volume. The
worker that processes commands is called nova-volume (similar to nova-compute
on the c
As you had mentioned I went through the logs and I could see an error message
with the "Host Key Verification Failed with exit code 255 on Command: ssh IP
address mkdir -p /var/lib/nova/instances/instance-00155". If I get it
correctly, this means that the key on the compute nodes that was ca
Thanks for the advice. Actually Im not planning on using block volumes at all
but its nice to know how everything plugs together.
Could you tell me what would be the best way to attach NFS filers as shared
storage? I am planning on running glusterfs on the hypervisors and then sharing
that back
2012/12/10 Vishvananda Ishaya
> Check rabbitmqctl list_queues and see if there are queues that have
> nonzero entries. That means messages are being sent but not picked up by
> the nodes.
>
Here is the output of the command -- there some non zero values for glance
info. Is there any way to clear
You could just turn off notifications in glance but that isn't causing an
issue. So it seems pretty clear that your compute and network nodes are
listening properly on 05, 07, 08. Is it possible that your network got
configured as multi_host=False somehow? Or that you have multiple rabbits
runn
Hi guys!
After looking for in the mailing list and docs, I honestly still don't
understand what really is nova-api-metadata.
it's a mandatory service in a multi-host deployment? it's only related to
EC2?
Thanks!
Regards,
JuanFra.
___
Mailing list: http
Its really just a binary that activates
https://github.com/openstack/nova/blob/master/nova/api/metadata/handler.py#L100
Its a way to allow for a VM to get metadata about itself and any userdata (of
which users may have provided) on boot.
Said feature is not just connected to ec2, but provides a
Understood. Thanks guys.
On Tue, Dec 11, 2012 at 2:26 AM, Vishvananda Ishaya
wrote:
>
> On Dec 5, 2012, at 7:19 PM, Lei Zhang wrote:
>
> thank you very much, Vishvananda.
> But I am still confused about the 192.168.0.0/24 and the 10.0.0.0/8 ip.
> What means by "The addresses will be moved on to
Try rm pem files under /var/cache/nova/ and /var/cache/glance/ , then
./stash.sh again.
I just reported a bug: https://bugs.launchpad.net/devstack/+bug/1088497
2012/11/14 Gui Maluf
> I'm getting the same error!
>
> I tried to run devstack with a simple localrc but still happening the same
> err
Hi all,
I have a question about swift configuration for NWR policy. According to
some documents of Swift, NWR is configurable. The general configuration is:
N=3, W=2, R=1 or 2.
Swift can provide both models of consistency: strong and eventual. But I
can't find where to configure this option.
Any
Hi, Zhang,
Just add 'X-Newest: Ture' in the HTTP GET request.
2012/12/11 Hua ZZ Zhang
> Hi all,
>
> I have a question about swift configuration for NWR policy. According to
> some documents of Swift, NWR is configurable. The general configuration is:
> N=3, W=2, R=1 or 2.
> Swift can provide bo
Alex, that make sense to me. thanks a lot. :-)
Best Regards,
Edward Zhang(张华)
Hi-
Thanks for the reply Gary..
But with respect to the Quantum_plugin_base_v2.py code, which is the base
class for the plugins, We can see the create/update/delete network methods
only in the quantum plugin. But then How about create/update/delete ports
and subnet methods. These methods do exis
It is not a necessity, but it is very useful. Also look at config drive.
-Matt
On Mon, Dec 10, 2012 at 5:33 PM, Joshua Harlow wrote:
> Its really just a binary that activates
> https://github.com/openstack/nova/blob/master/nova/api/metadata/handler.py#L100
>
> Its a way to allow for a VM to get
Does any of our documentation say NRW are directly configurable? It's not
really quite that simple.
N is a property of the cluster, chosen when you build the ring.
W is always a simple majority of N.
R is generally 1 (eventually consisten reads), but the client can request
it be bumped to N (> hi
On Mon, Dec 10, 2012 at 4:17 AM, Adam Young wrote:
> As a Keystone core developer, I have to say that I don't see it as a huge
> burden to keep it in place. We want to maintain API backward
> compatability, and removing it would break that. We should deprecate it
> and get people to sign off on
Mike,
Thanks for you clarification. I'm interested in how to enable the following
combinations.
for case 1, can we do it without sending the HTTP head 'X-Newest'?
for case 2, how to enable it?
N=3, W=2, R=2 (Strong Consistence Mode)
N=3, W=3, R=1 (Strict Consistence Mode)
Best Regards,
Hello,
nova-api-metada service is an optional nova daemon that implements an HTTP
interface for retrieving metadata you associate to an instance at boot time
(see --user-data parameter).
Provided that you have installed and correctly configured it, try the
following sequence for better understand
Hi-
I have the following first set of doubts regarding the Folsom Quantum
[1] With regard of Quantum Plug-in, How does the RPC communication take
place between the Agent and the plug-n ? In the source code,
ovs_quantum_plugin.py, I find the setup_rpc method and AgentRPCAPI class
what does the rev
50 matches
Mail list logo
