Thanks Alex!
But, it seems that Swift -V2 -A can not show
separate usage stat for differnt users in the
same account (tenant)? Is there any technical
difficulty/reason why the usage stat for a certian
user (under a tenant name) can not be shown by
Swift -V2 -A ? or there is no sense to do that?
I have tried it and it seems it doesn't
work at all !
Le 12/11/2012 16:31, logan_mcl...@dell.com a crit:
I
havent tried it yet, but yes. You should be able to add
internal network interfaces from
Hello,
i have installed openstack glance on a centos 6.3 server.
After running:
glance add name=f16-jeos is_public=true disk_format=qcow2
container_format=ovf copy_from=
http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-openstack-sda.qcow2
or
glance add name=tty-linux-kernel
On 11/10/2012 10:58 AM, David Chadwick wrote:
I agree with the vast majority of what Jorge says below. The idea I
would like to bounce around is that of the unscoped token.
What does it mean conceptually? What is its purpose? Why do we need
it? Why should a user be given an unscoped token to
Hello, Ning,
On the second question: Keystone 'tenant' maps to 'account' in Swift.
Keystone 'user' directly corresponds to Swift 'user'.
--
Best regards,
Oleg Gelbukh
Mirantis IT
On Tue, Nov 13, 2012 at 12:19 PM, ning2008wisc ning2008w...@gmail.comwrote:
Thanks Alex!
But, it seems that
Hi Adam
you have pointed out an important difference between an unscoped token
and a scoped one. The former can only be used with keystone, the latter
with a cloud service. This also implies that a scoped token can only
have the scope of a single service, and not multiple services. The user
Hi,
I agree that the use case of a trusted IaaS provider (with possibly
compromised nodes) is a valid one and should have support in the openstack
codebase, although it seems rather dicey to trust the IaaS provider which
does not trust it's own hosts.
And your understanding is correct, the idea
An unscoped token is basically implicitly scoped to Keystone service right?
One should be able to use an unscoped token to reset his password, and ask
Keystone for information pertaining to himself, such as what are his roles,
what services/endpoints are available to him, and what are his tenants,
Hi Guang
On 13/11/2012 16:14, Yee, Guang wrote:
An unscoped token is basically implicitly scoped to Keystone service right?
One should be able to use an unscoped token to reset his password, and ask
Keystone for information pertaining to himself, such as what are his roles,
what
I should add, that it looks like none of the iptables rules are being setup
for the floating IP. It is bound to the right interface in ip addr, but my
iptables look as follows:
(You'll note that 10.0.40.129 is conspicuous by its absence)
Ideas?
Chain INPUT (policy ACCEPT 47238 packets, 20M
I'm getting the same error!
I tried to run devstack with a simple localrc but still happening the same
error.
stack@cloud-controller:~/devstack$ glance image-list
Request returned failure status.
Invalid OpenStack Identity credentials.
On Fri, Nov 9, 2012 at 8:44 AM, Lu, Lianhao
So maintaining a token scoped to just the user, and a mechanism to scope it to
a tenant sound like all goodness. We can absolutely keep the API such that it
can provide either.
Right now, our auth_token middleware implicitly requires a tenant in that
scoping to work. If someone wanted to
seems like we need a clear design for next generation tokens that
everyone can agree on. But also an extensible design to cater for
outliers. In our federation design doc we show the Token Issuing Service
and Token Validation Service as plugin modules to Keystone that can be
replaces so that
On Nov 13, 2012, at 11:35 AM, heckj wrote:
So maintaining a token scoped to just the user, and a mechanism to scope it
to a tenant sound like all goodness. We can absolutely keep the API such that
it can provide either.
Right now, our auth_token middleware implicitly requires a tenant
It seems like unscoped is a total misnomer. Unscoped just means scoped to
keystone. The existence of 'unscoped' tokens seems completely orthogonal to
whether a token can be scoped to multiple services/endpoints.
Vish
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
On Nov 13, 2012, at 11:01 AM, Jorge Williams jorge.willi...@rackspace.com
wrote:
On Nov 13, 2012, at 11:35 AM, heckj wrote:
So maintaining a token scoped to just the user, and a mechanism to scope it
to a tenant sound like all goodness. We can absolutely keep the API such
that it can
On Mon, 12 Nov 2012 20:48:35 -0800
Ning Zhang n...@zmanda.com wrote:
Is there any Swift (GUI or command line) tool that can
retrieve the account-level and
container-level usage information (e.g. how large space
has been used under an account, how large space has been
used under a tenant) and
You could use a project like slogging (http://github.com/notmyname/slogging) to
run inside the cluster and aggregate that information from account dbs and logs.
--John
On Nov 13, 2012, at 12:15 PM, Pete Zaitcev zait...@redhat.com wrote:
On Mon, 12 Nov 2012 20:48:35 -0800
Ning Zhang
Will user-scoped token include the full service catalog?
Also, I thought the consensus was to allow the API contract to be flexible on
how many tenants we can scope the token to. The ref impl can enforce 1
tenant-scoped token. Are we diverging from this?
Thanks,
joe
-Original
Hey Joe:
Currently a user scoped token doesn't include a service catalog - mostly
because I think the service catalog generally requires tenant_id's to
interpolate into the values to provide it. That doesn't mean we can't put
in/include service catalog endpoints where that value doesn't need
Hello,
I am trying to test out nova installation per the instruction in OpenStack
Deploy and Install Manual. (
http://docs.openstack.org/trunk/openstack-compute/install/apt/content/configure-creds.html
). However, when I issue nova image-list, I get the prompt - password for
your new
I would see the major blocking issue on this:
However, imo an IaaS provider that claims to offer trusted hosts but hesitates
to reveal the software stack of it's hosts to an external auditor (CA in this
case) would have issues with credibility
every IaaS provide has its own software stack,
We upgraded our cloud from Essex - Folsom yesterday and had a major loss of
data that I thought I'd share.
With Essex the flag remove_used_base_images had a default of False, with Folsom
it was changed to True. We hadn't explicitly set this so we had whatever the
default was.
After the
On 11/14/2012 04:03 PM, Sam Morrison wrote:
After the upgrade which went relatively smoothly (a lot easier than
diablo - essex) almost all our base images were deleted by the image
cache clean up.
I can't explain how this happened. We lost a total of about 70 images
that affected ~200
Hi Neelakantam,
There refer to provider networks, which are quantum networks that are
mapped directory to a specific flat or VLAN network in your data center.
Please see this page in the Quantum Admin Guide (and its three
sub-sections):
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/37/Project:precise_grizzly_quantum_trunkDate of build:Tue, 13 Nov 2012 03:01:21 -0500Build duration:1 min 43 secBuild cause:Started by an SCM changeBuilt
at 20121113-0309Build needed
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/84/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 03:01:24 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/85/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 05:01:23 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/38/Project:precise_grizzly_quantum_trunkDate of build:Tue, 13 Nov 2012 07:31:22 -0500Build duration:1 min 36 secBuild cause:Started by an SCM changeBuilt
at 20121113-0738Build needed 00:04:21, 43536k disc spaceERROR:root:Error occurred during package
Title: precise_grizzly_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_horizon_trunk/10/Project:precise_grizzly_horizon_trunkDate of build:Tue, 13 Nov 2012 08:31:22 -0500Build duration:2 min 2 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/9/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Tue, 13 Nov 2012 13:01:21 -0500Build duration:3 min 49
at 20121113-1305Build needed 00:01:40, 17660k disc
at 20121113
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/19/Project:raring_grizzly_keystone_trunkDate of build:Tue, 13 Nov 2012 13:06:55 -0500Build duration:6 min 46 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/87/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 13:05:44 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_python-keystoneclient_trunk/72/Project:quantal_folsom_python-keystoneclient_trunkDate of build:Tue, 13 Nov 2012 16:01:27 -0500Build duration:1 min 17
Title: precise_grizzly_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_horizon_trunk/11/Project:precise_grizzly_horizon_trunkDate of build:Tue, 13 Nov 2012 16:31:22 -0500Build duration:2 min 57 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/88/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 16:34:19 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/14/Project:precise_grizzly_glance_trunkDate of build:Tue, 13 Nov 2012 17:01:22 -0500Build duration:1 min 41 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/89/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 20:01:24 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/39/Project:precise_grizzly_quantum_trunkDate of build:Tue, 13 Nov 2012 20:31:21 -0500Build duration:1 min 34 secBuild cause:Started by an SCM changeBuilt
at 20121113-2038Build needed 00:04:23, 43536k disc spaceERROR:root:Error occurred during package creation/build
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/15/Project:precise_grizzly_glance_trunkDate of build:Tue, 13 Nov 2012 22:31:22 -0500Build duration:2 min 9 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/90/Project:precise_grizzly_nova_trunkDate of build:Tue, 13 Nov 2012 22:31:24 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/40/Project:precise_grizzly_quantum_trunkDate of build:Wed, 14 Nov 2012 01:31:22 -0500Build duration:1 min 33 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/39/Project:raring_grizzly_quantum_trunkDate of build:Wed, 14 Nov 2012 01:31:21 -0500Build duration:6 min 58 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/41/Project:precise_grizzly_quantum_trunkDate of build:Wed, 14 Nov 2012 02:31:22 -0500Build duration:1 min 35 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/40/Project:raring_grizzly_quantum_trunkDate of build:Wed, 14 Nov 2012 02:31:22 -0500Build duration:7 min 13 secBuild cause:Started by an SCM changeBuilt
50 matches
Mail list logo
