Matt Dietz wrote:
Ditto
On 9/12/11 2:10 PM, Sandy Walsh sandy.wa...@rackspace.com 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
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 rich
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
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:
hi
when i run the diablo-4 dashboard,Has the following error :
Unable to get usage info: (OperationalError) no such column: vm_state uselect
id,image_ref,project_id,user_id,vcpus,hostname,display_name,host,vm_state,instance_type_id,launched_at,terminated_at
from instances where
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 atk...@gmail.com wrote:
**
hi
when i run the diablo-4 dashboard,Has the following error :
Unable to get usage info:
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 :
Hello Stackers,
With swauth, Swift accounts are identified by reseller_prefix_hash. Under
Keystone (with swift_auth and Swift's lazy provisioning), I see the Swift
account now has the format reseller_prefix_tenantId. So, if we have
existing Swift account data with the old format, how would
Swift treats the hash or tenantid 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
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).
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 stored
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
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
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]
Jay Pipes wrote:
As for the API coordinator, I thought we had already voted yes on that?
My position on the API coordinator is that there is no need for
amending our governance and creating an official position for that.
I'm all in favor of a technical meritocracy where someone that cares
about
15 matches
Mail list logo
