For swauth there is provision to change account_id using
swauth-set-account-service, it could be changed to the tenant_id, but since
account_id is part of the hashing, old data in that account won't be
accessible, i am not familiar with keystone, is there any such service in
keystone to change tena
Without changing the account id, how do I map the uuid of the old account to a
Keystone tenant Id? For a given tenantId, I would like to be able to reference
both the corresponding Swift account and Nova project, right?
Liem
-Original Message-
From: John Dickinson [mailto:m...@not.mn]
Swift uses the entire account string as part of the lookup. Therefore a
different account string means that everything associated with that account
(account, containers, and objects) would have to be rehashed. That's basically
a fancy way of saying "copy the data from the old account to the new
If there is an existing swift customer with swift account 'foo' and nova
project 'bar', there is no way to have them belong to the same Keystone
tenant. I think that is the data migration issue.
Jason
-Original Message-
From: openstack-bounces+jason.rouault=hp@lists.launchpad.net
[
Why would the account need to change? Can the swift account reference in
keystone be set to the old value? If not, then yes you will have 2 swift
accounts.
On Sep 13, 2011, at 3:48 PM, Nguyen, Liem Manh wrote:
> Thanks, John, for pointing out the uuid thing :).
>
> So, let's say I have stor
Thanks, John, for pointing out the uuid thing :).
So, let's say I have stored data into a Swift account with a UUID. When I
switch to using Keystone, I would like to continue using my "old" account,
since I have a bunch of data in it. However, the account format has changed
(under Keystone)
John,
If you migrate a user's account ID from uuid to _, dhw
would you find an object that was stored in the ring based on is (uuid,
container, object) tuple?
Or maybe you are suggesting that is bad idea?
b
>-Original Message-
>From: openstack-bounces+bob.souza=hp@lists.launchpad.n
Swift treats the or part of the account as an opaque string.
(Technically, the first one isn't a hash but a uuid.) I don't think there is
any migration path because there is nothing to migrate.
But I may be missing something.
--John
On Sep 13, 2011, at 2:55 PM, Nguyen, Liem Manh wrote:
> H
Hello Stackers,
With swauth, Swift accounts are identified by _. Under
Keystone (with swift_auth and Swift's lazy provisioning), I see the Swift
account now has the format _. So, if we have
existing Swift account data with the old format, how would one go about
migrating from the old format
It may help you to know that the issue you are having is a Nova issue, not a
Dashboard issue. You should open a question on launchpad.net/nova and paste
your full stack trace.
On Sep 13, 2011, at 9:21 AM, atkisc wrote:
> hi
> when i run the diablo-4 dashboard,Has the following error :
>
I do not recommend trying to run the Diablo dashboard against the Cactus nova
release. There are a number of API extensions added to nova during the Diablo
release cycle that the dashboard relies on. So you may be able to stand it up
eventually but you will have a lot of issues getting it runn
vm_state was added to the instance model in d4 - if you are upgrading, you
will need to migrate:
nova-manage db sync
A
On Tue, Sep 13, 2011 at 9:21 AM, atkisc wrote:
> **
> hi
> when i run the diablo-4 dashboard,Has the following error :
>
>
> Unable to get usage info: (OperationalError) no
hi
when i run the diablo-4 dashboard,Has the following error :
Unable to get usage info: (OperationalError) no such column: vm_state u"select
id,image_ref,project_id,user_id,vcpus,hostname,display_name,host,vm_state,instance_type_id,launched_at,terminated_at
from instances where (terminate
done
From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of
Thierry Carrez [thie...@openstack.org]
Sent: Tuesday, September 13, 2011 6:57 AM
To: openstack@lists.
Hello everyone,
Our team meeting will take place at 21:00 UTC this Tuesday in
#openstack-meeting on IRC. PTLs, if you can't make it, please name a
substitute on [2].
We are one week before Diablo final release, so I'd like us to focus on
release-critical bugs for Nova and Glance. We'll therefore
Alle martedì 13 settembre 2011, Rasika Karunathilaka ha scritto:
> Hi Team,
> I have successfully configured Openstack Nova Cactus release on Ubuntu
> 11.04 and it is working fine on my two node cluster. However I would like
> to integrate latest dashboard into Cactus nova deployment and get ri
Matt Dietz wrote:
> Ditto
>
> On 9/12/11 2:10 PM, "Sandy Walsh" wrote:
>
>> From: Jay Pipes [jaypi...@gmail.com]
>>
>>> Can we discuss pulling novaclient into Nova's source tree at the design
>>> summit?
>>
>> +1
Someone should file it at summit.openstack.org, then :)
--
Thierry Carrez (ttx)
Hi, Roman Sokolkov:
thanks a lot that solve my problem, I manually update row "nova" in
mysql CLI:
update endpoint_templates set public_url="
http://nova.publicinternets.com/v1.1/%tenant_id%"; where id=3;
update endpoint_templates set admin_url="
http://127.0.0.1:8774/v1.1/%tenant_id%
Thanks a lot that solve my problem!but I manually update row "nova" in
sqlite CLI.
2011/9/13 Anthony Young
> Another thing to check - the os1.1 keystone endpoints have been modified in
> d4 to include a tenant prefix. If you are upgrading an existing install,
> you may need to update your keyst
19 matches
Mail list logo
