Thanks a lot for the quick reply, Dan. It's good to know that _context is
expected to be a RequestContext. We do have some changes to nova, although
none are obviously in this area. I'll look there and file a bug if this is
from pure nova.
--
Noel
On Tue, Jun 24, 2014 at 3:33 PM, Dan Smith
Hello,
I am using Havana and every once in a while a VM fails to start and goes
into ERROR state. When I check the Nova compute logs, I find this error.
Note that this does not happen always. Can anybody shed light on why this
is happening? Is there any workaround? Thanks.
2014-06-25 02:09:58.53
chen: I just test it yesterday,and I think we can't do live-migration using
horizon.
walter Xu
From: Li, ChenDate: 2014-06-25 12:59To: openstackSubject: [Openstack]
[Horizon] Can I do live-migration using Dashboard ?
Hi list,
Is there a way to do live-migration using hor
Why ??
Is this a missing feature for horizon?
Would this be added in the future ??
Thanks.
-chen
From: walterxj [mailto:walte...@gmail.com]
Sent: Wednesday, June 25, 2014 1:17 PM
To: Li, Chen; openstack
Subject: Re: [Openstack] [Horizon] Can I do live-migration using Dashboard ?
chen:
I ju
Hi list,
Is there a way to do live-migration using horizon ?
I didn't find related button.
Thanks.
-chen
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http:/
Thanks for the reply walterxj.
The issue looks like is caused by the missing configurations in
/etc/nova/nova.conf for service nova-conductor.
The error message in api and compute indicates that they’re waiting for RPC
response from nova-conductor.
Then, in nova-conductor.log, we can get:
http:
Hi Thang Pham and all !
I am using KVM on OpenStack Havana , OpenStack Icehouse , And inject admin
password OK. SURE 100%
*Step 1* : Edit /etc/nova/nova.conf
[DEFAULT ]
libvirt_inject_password=True
enable_instance_password = True
*Step 22:*
If you use image cirros, ubuntu downlo
Hi Wangpan,
Injecting admin password is not implemented or supported in libvirt/kvm. I
believe only Xen supports it.
Regards,
Thang
On Tue, Jun 24, 2014 at 11:36 PM, Wangpan
wrote:
> Hi all,
>
> I want to inject admin password to a libvirt/kvm instance, and I enable
> the config libvirt_in
Hi all,
I want to inject admin password to a libvirt/kvm instance, and I enable the
config libvirt_inject_password=true on the compute node,
I also find the /etc/shadow file in the instance is changed, but when I use the
adminPass to login the instance from vnc, it is failed.
I find that the adm
I don't think so. Since you are doing PUT object request, it will have
network I/O operations b/w client/proxy server/object server
and disk I/O operations on object server to save the data. The latency of
sending data from client to proxy server should be affected
by their network latency. So the
Looks like your databases might be out
of sync, have you tried running 'keystone-manage db_sync' ?
Regards,
Steve Martinelli
Software Developer - Openstack
Keystone Core Member
Phone:
1-905-413-2851
E-mail: steve...@ca.ibm.com
8200 Warden Ave
Markham, ON L6G 1C7
Canada
From:
Mi
Hi Sushma,
Thanks for the reply.
Well, edit /etc/nova/policy.json do works for command "nova migrate".
But when I run command "nova live-migration", I still get errors, in
/var/log/nova/conductor.log:
2014-06-25 02:07:23.897 115385 INFO oslo.messaging._drivers.impl_qpid [-]
Connected to AMQ
Hitting an issue with icehouse when using python & the keystone api to
create a new user. Have tried both v2.0 and v3 of the api, both failing
with the same error. Specifically, the latter part of the exception
indicates the value of the domain given in the users.create method isn't
being passed o
On 06/23/2014 07:37 PM, Sam Morrison wrote:
Hi Adam,
Thanks for the advice, I’ve tested it out and it is possible to switch over
pretty seamlessly.
Here is what I did (spelt out in full for others reading):
1. Generate a new signing key
2. Generate a new certificate request
3. Sign this with
Sorry I should've been a little more verbose in my previous answers.
I don't have anything implemented yet. I'm only looking at designing the
solutions. All slideware so far :-).
We develop a filesystem backed by object stores including Openstack Swift.
We'd like to work with or without Keystone.
This error happens in Icehouse migrating a vm with floating ips. nova
tries to call save() on a floating_ip object, but the sqlalchemy context
appears broken:
In nova/nova/network/floating_ips.py, FloatingIP.migrate_instance_start()
floating_ip = floating_ip_obj.FloatingIP.get_by_address(context
We did load balancers in each logical region with affinity set on the
proxies per region. We use Keystone and I'm curious why you aren't but
that's not the end-all, just curious. You can control replication behavior
after storage policies are implemented (Juno or pre-Juno) but what you want
to do i
I don't see how there would be a problem if you still enforced a hard limit
of the number of instances a user can have. The proposal here is suspending
would release *only* vCPUs and memory, so the user could still potentially
exceed their quota by reaching their allotted amount of instances. Let's
Hi,
As per our discussions in the last meeting I have made an etherpad which
details different pool implementations and at the end comparison between the
approaches. Please go through it and be ready with any questions or opinions
for tomorrow's meeting. Here is the link for etherpad:
https:
So I believe, there are largely two options:
1) DNS Magic
2) Separate endpoints for separate regions.
Thanks everyone!
On Mon, Jun 23, 2014 at 8:58 PM, Michael Gale wrote:
> One more thing, do you read:
> https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/
>
>
>
Communication between proxy and object servers shouldn't be affected by the
latency between the proxy server and the client, right? Also, I'm using a
single node Swift cluster. So there should be only 1 copy of the object
(along with any other I/Os required for the container and accound DBs).
Ever
Hi all,
In
http://docs.openstack.org/icehouse/config-reference/content/vmware-vmdk-driver.html,
in "Data store selection" section, I saw some decription:
"If two or more data stores match the storage policy, the driver chooses a data
store that is connected to the maximum number of ho
hi:Robert Thank you for your reply.
About the CPU issue,I have switched my Comoute02's CPUs to Intel(R)
Xeon(R) CPU E5405 @ 2.00GHz *2, and now it works.
cheers!
walter Xu
From: Robert van LeeuwenDate: 2014-06-24 15:58To: walterxj; openstackSubject:
RE: [Openstack] com
Got it!
Thanks a lot !
-chen
-Original Message-
From: Robert van Leeuwen [mailto:robert.vanleeu...@spilgames.com]
Sent: Tuesday, June 24, 2014 4:32 PM
To: Li, Chen; openstack@lists.openstack.org
Subject: RE: How can I enable operation for non-admin user
> run command:
> nova migrate ${m
Hi Li,
As fas as I know to migrate an instance you'll need admin priviliges.
But if you want to allow this operation for normal user then might try editing
/etc/nova/policy.json file and give privileges.
File: /etc/nova/policy.json
change "compute_extension:admin_actions:migrate": "rule:admin_a
hi: first: yum install -y sysfsutils.x86_64 .
and then:follow the steps in:
https://lists.launchpad.net/openstack/msg24036.html
walterxj
From: Li, ChenDate: 2014-06-24 16:35To: openstack@lists.openstack.orgSubject:
[Openstack] Failed to migrate an instance
H
Hi list,
I'm working under CentOS + icehouse.
When I run command:
nova migrate ${instance}
I get error:
ERROR: The server could not comply with the request since it is either
malformed or otherwise incorrect. (HTTP 400) (Request-ID:
req-ecb2321b-aa4b-4684-92f7-9fd511918ec0)
Her
> run command:
> nova migrate ${my_instance}
> I get output:
> ERROR: Policy doesn't allow compute_extension:admin_actions:migrate to be
> performed. (HTTP 403)
> (Request-ID: req-698ad5b5-f1fe-48fc-b81f-a765020bf89f)
HI Chen,
The policy.json (in /etc/nova) defines which group is allowed what.
Hi list,
I'm working under CentOS + icehouse.
While, I have an non-admin user "demo", and I can work under this this user
with basic operations.
Everything works well.
But, I also hope this user can do some admin operations, such as migrate and so
on, because currently when I run command:
nova
> Hi,all
> Today when I test instance live migration in
> CLI (nova live-migration --block-migrate
> 0b30368a-2eaf-42e5-918a-f855bad91f63 Compute02) ,I encounterd the following
> error massages:
>
> But when I use dashboard
> to migrate the vm,it appears to success.I'm using Havana version.
On Wed, Jun 18, 2014 at 09:47:33PM +1200, Mark Kirkwood wrote:
> Hmmm - I'm looking hard at that 'almost' word in there - so *possibly* you
> might have some misconfiguration tripping you up. Essentially I followed
> http://docs.openstack.org/trunk/install-guide/install/apt/content/ and the
> basic
Hi,all Today when I test instance live migration in CLI (nova
live-migration --block-migrate 0b30368a-2eaf-42e5-918a-f855bad91f63 Compute02)
,I encounterd the following error massages:
2014-06-24 14:49:50.742 9819 ERROR nova.openstack.common.rpc.common
[req-8d766427-eb32-4bf8-985c-39
My guess is the object data need to be transmitted to Swift cluster before
the status code returned.
It can't be returned immediately before 2/3 I/O completed. Otherwise it is
not consistent to tell client
it succeed.
-Edward Zhang
Hi,
I have a single node swift cluster. I measured the time taken to
complete a PUT request that originated from three different client
machines. Each client was writing a single 256K byte object.
Note that the time measured was only the time taken on the Swift
cluster itself. I started the timer
Yeah~
This is a known bug and already been fixed by
https://review.openstack.org/#/c/90644/1
Thanks.
-chen
From: Li, Chen
Sent: Tuesday, June 24, 2014 3:02 PM
To: openstack@lists.openstack.org
Subject: [Cinder] Failed to create voume from an image
Hi list,
I'm working under CentOS + icehouse.
Hi,all Today when I test instance live migration in CLI (nova
live-migration --block-migrate 0b30368a-2eaf-42e5-918a-f855bad91f63 Compute02)
,I encounterd the following error massages:
2014-06-24 14:49:50.742 9819 ERROR nova.openstack.common.rpc.common
[req-8d766427-eb32-4bf8-985c-3969f65
Hi list,
I'm working under CentOS + icehouse.
I try to run command :
cinder create --image-id 5a1c0102-85f4-4867-819e-b87f97f4407e 1
While I get error:
ERROR: The server has either erred or is incapable of performing the requested
operation. (HTTP 500) (Request-ID: req-70a91249-6625-49a2-a40c-
37 matches
Mail list logo
