In my experience 'Endpoint for object-store not found - have you specified a
region?' can be returned by swift client if:
(a) You have specified a region that isn't found among the service endpoints
e.g.
% swift --os-auth-url http://example:5000/v2.0 --os-password=testing stat
--os-username=te
We have a change [1] under review in Swift to make access control lists
compatible with migration to keystone v3 domains. The change makes two
assumptions that I'd like to double-check with keystone folks:
1. That a project can never move from one domain to another.
2. That the under
AM, Coles, Alistair
mailto:alistair.co...@hp.com>> wrote:
We have a change [1] under review in Swift to make access control lists
compatible with migration to keystone v3 domains. The change makes two
assumptions that I’d like to double-check with keystone folks:
1. That a proje
I've been looking at the implications of applying oslo.config in Swift, and I
have a question about the best pattern for registering options.
Looking at how keystone uses oslo.config, the pattern seems to be to have all
options declared and registered 'up-front' in a single place
(keystone/comm
We've just committed a first set of patches to gerrit that address this
blueprint:
https://blueprints.launchpad.net/swift/+spec/cluster-federation
Quoting from that page: "The goal of this work is to enable account contents to
be dispersed across multiple clusters, motivated by (a) accounts tha
Thai,
(repeating some of what we have discussed in private for others' benefit)
The Swift docs state "Be sure to use Keystone UUIDs rather than names in
container ACLs" [1]. The guidance is re-iterated here [2] "...names must no
longer be used in cross-tenant ACLs...". They then go on to explai
> -Original Message-
> From: Jamie Lennox [mailto:jamielen...@redhat.com]
> Sent: 18 June 2015 07:02
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [glance] V3 Authentication for swift store
>
> Hey everyone,
>
> TL;DR: glance_store require
Jamie - thanks for the link to your blog.
I remember the Paris discussion :) And also noted the Vancouver discussion re.
SDK not necessarily being targeted at service-service interactions. I sense
there is renewed desire to maintain & improve swiftclient, and a few of us are
interested in looki
Account ACL in Swift is not supported with keystoneauth. It is not described in
the keystone auth section of [1]. You can probably achieve similar by assigning
the appropriate roles to users in keystone.
[1] http://docs.openstack.org/developer/swift/overview_auth.html
Alistair
From: Sampath,
> -Original Message-
> From: Flavio Percoco [mailto:fla...@redhat.com]
> Sent: 08 February 2017 13:49
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all][tc][swift][designate] New language addition
> process has been approved
>
> On 19/01/17 11:59 +0100, Flavio Pe
On 22 November 2016 18:56, John Dickinson wrote:
>
> On 22 Nov 2016, at 10:47, Andreas Jaeger wrote:
>
> > When we (infra) changed the unit test jobs to not set up databases by
> > default, we created special python-db and tox-db jobs that set up both
> > MySQL and PostgreSQL databases. And tha
11 matches
Mail list logo
