Re: [openstack-dev] Optional Dependencies

On Tue, Sep 29, 2015 at 9:38 AM, Douglas Mendizábal < douglas.mendiza...@rackspace.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi openstack-dev, > > I was wondering what the correct way of handling optional dependencies > is? I'm specifically talking about libraries that ar

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

On Thu, Oct 15, 2015 at 5:52 AM, Victor Stinner wrote: > Hi, > > I propose that changes must now be documented in Oslo libraries. If a > change is not documented, it must *not* be approved. > > IMHO it's very important to document all changes. Otherwise, it becomes > really hard to guess if a spe

Re: [openstack-dev] [pbr] 1.0.1 released

On Thu, May 21, 2015 at 2:22 AM, YAMAMOTO Takashi wrote: > hi, > > can you explain why you want to use pbr 1.0.1 in the first place? > what's wrong with requiring pbr<1.0 ? > > Global requirements currently has "pbr>=0.11,<2.0"[1], and keystonemiddleware has the updated requirement which conflict

Re: [openstack-dev] [pbr] 1.0.1 released

On Thu, May 21, 2015 at 10:17 AM, Robert Collins wrote: > On 22 May 2015 at 05:14, Brant Knudson wrote: > > > > On Thu, May 21, 2015 at 2:22 AM, YAMAMOTO Takashi < > yamam...@valinux.co.jp> > > wrote: > >> > >> hi, > >> > >>

Re: [openstack-dev] [Ironic] [TC] Discussion: changing Ironic's release model

On Fri, May 29, 2015 at 8:11 AM, Thomas Goirand wrote: > On 05/28/2015 06:41 PM, Devananda van der Veen wrote: > > Hi all, > > > > tl;dr; > > > > At the summit, the Ironic team discussed the challenges we've had with > > the current release model and came up with some ideas to address them. > > I

Re: [openstack-dev] [keystone]Why not common definition about normal HTTP status code like 2xx and 3xx?

On Tue, Jun 2, 2015 at 4:32 AM, Chenhong Liu wrote: > There is keystone/exception.py which contains Exceptions defined and used > inside keystone provide 4xx and 5xx status code. And we can use it like: > exception.Forbidden.code, exception.forbiddent.title > exception.NotFound.code, exce

Re: [openstack-dev] [nova][security] Enable user password complexity verification

On Wed, Jun 3, 2015 at 6:49 AM, David Stanek wrote: > > On Wed, Jun 3, 2015 at 6:04 AM liusheng wrote: > >> Thanks for this topic, also, I think it is similar situation when >> talking about keystone users, not only the instances's password. >> >> > In the past we've talked about having more ad

Re: [openstack-dev] Specify a domain in mapping rules

You might need these changes, which are proposed but not merged: https://review.openstack.org/#/q/status:open+project:openstack/keystone+branch:stable/kilo+topic:bug/1442787,n,z Salut, Brant On Thu, Jun 18, 2015 at 6:04 AM, J. Pablo Martín Cobos wrote: > Hi all, > > I'm a Python/Django software

Re: [openstack-dev] [api] [all] To changes-since or not to changes-since

Keystone also has a resource that provides changes since[1], the query parameter used is "since". [1] http://specs.openstack.org/openstack/keystone-specs/api/v3/identity-api-v3-os-revoke-ext.html#list-revocation-events Ciao, Brant On Fri, Jun 19, 2015 at 3:25 PM, Sean Dague wrote: > On 06/19

Re: [openstack-dev] [ceilometer] can we get ceilometermiddleware to use a config file instead of transport_url?

On Mon, Jun 22, 2015 at 2:43 PM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2015-06-22 13:30:44 -0400: > > On 06/22/2015 01:15 PM, Michael Krotscheck wrote: > > > Having _just_ done this, a couple of suggestions. > > > > > > - If the middleware is NOT optional - that is, it prov

Re: [openstack-dev] [devstack] apache wsgi application support

On Wed, Jun 17, 2015 at 1:21 PM, Sean Dague wrote: > On 06/16/2015 05:25 PM, Chris Dent wrote: > > On Tue, 16 Jun 2015, Sean Dague wrote: > > > >> I was just looking at the patches that put Nova under apache wsgi for > >> the API, and there are a few things that I think are going in the wrong > >

Re: [openstack-dev] [devstack] apache wsgi application support

On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent wrote: > On Wed, 24 Jun 2015, Sean Dague wrote: > >> On 06/24/2015 07:57 AM, Chris Dent wrote: >> >>> If the primary reason is so that we can rely on the console_scripts >>> entry point to handle getting the application somewhere useful then >>> that to

Re: [openstack-dev] [all] tenant vs. project

On Fri, Feb 12, 2016 at 7:42 AM, Sean Dague wrote: > On 02/12/2016 08:30 AM, Dean Troyer wrote: > > On Fri, Feb 12, 2016 at 6:01 AM, Sean Dague > > wrote: > > > > OpenStack is wildly inconsistent in it's use of tenant vs. project. > As > > someone that wasn't here

Re: [openstack-dev] [Nova] Should we signal backwards incompatible changes in microversions?

On Tue, Feb 16, 2016 at 1:04 PM, Dean Troyer wrote: > > > On Tue, Feb 16, 2016 at 12:17 PM, Sean Dague wrote: > >> Honestly, doing per API call version switching is probably going to end >> in tears. HTTP is stateless, so it's allowed, but it will end in tears >> of complexity as you need to sel

Re: [openstack-dev] [all] audience for release notes

On Fri, Feb 26, 2016 at 6:34 AM, Doug Hellmann wrote: > I've had a few conversations recently about "appropriate" content for > release notes, so I thought it was worth starting a separate thread here > to clarify. > > We have 3 potential audiences for release notes: > > 1. Developers consuming l

Re: [openstack-dev] [all][zaqar][cloudkitty] Default ports list

On Thu, Mar 10, 2016 at 8:10 AM, Thomas Herve wrote: > On Thu, Mar 10, 2016 at 2:55 PM, Sean Dague wrote: > > On 03/10/2016 08:40 AM, Thomas Herve wrote: > >> On Thu, Mar 10, 2016 at 2:28 PM, Chris Dent > wrote: > >>> +many. It would be great if we just got rid of the runnable web > >>> servers

Re: [openstack-dev] [stable] Stable* wiki updates

Since there's no gerrit, I'll leave my comment here: +1 Thanks! On Fri, Mar 11, 2016 at 1:54 AM, Alan Pevec wrote: > Hi stable-maints, > > FYI I've updated https://wiki.openstack.org/wiki/StableBranch and > https://wiki.openstack.org/wiki/StableBranchRelease now that all > policy and team inform

Re: [openstack-dev] [all][zaqar][cloudkitty] Default ports list

On Thu, Mar 10, 2016 at 10:43 AM, Brant Knudson wrote: > > > On Thu, Mar 10, 2016 at 8:10 AM, Thomas Herve wrote: > >> On Thu, Mar 10, 2016 at 2:55 PM, Sean Dague wrote: >> > On 03/10/2016 08:40 AM, Thomas Herve wrote: >> >> On Thu, Mar 10, 2016 at 2:28

Re: [openstack-dev] Which projects support wsgi / python3 in mitaka?

On Fri, Mar 25, 2016 at 9:54 AM, Matthew Thode wrote: > I'm updating the packaging for openstack in preparation for the release > and need some info to update correctly. I'm specifically looking at the > following services. > > I don't know if any of these services support python3 fully as a ser

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Thu, Jan 29, 2015 at 11:41 AM, Sean Dague wrote: > Correct. This actually came up at the Nova mid cycle in a side > conversation with Ironic and Neutron folks. > > HTTP error codes are not sufficiently granular to describe what happens > when a REST service goes wrong, especially if it goes wr

Re: [openstack-dev] [oslo.db] PyMySQL review

On Thu, Jan 29, 2015 at 11:05 AM, Roman Podoliaka wrote: > Mike, > > I can't agree more: as far as we are concerned, every service is yet > another WSGI app. And it should be left up to operator, how to deploy > it. > > So 'green thread awareness' (i.e. patching of the world) should go to > separ

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Thu, Jan 29, 2015 at 5:01 PM, Jay Faulkner wrote: > > On Jan 29, 2015, at 2:52 PM, Kevin Benton wrote: > > Oh, I understood it a little differently. I took "parsing of error > messages here is not the way we’d like to solve this problem" as meaning > that parsing them in their current ad-ho

Re: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat

On Fri, Jan 30, 2015 at 4:20 AM, Steven Hardy wrote: > On Thu, Jan 29, 2015 at 12:31:17PM -0500, Zane Bitter wrote: > > On 29/01/15 12:03, Steven Hardy wrote: > > >On Thu, Jan 29, 2015 at 11:41:36AM -0500, Zane Bitter wrote: > > >>>IIUC keystone now allows you to add users to a domain that is > o

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Mon, Feb 2, 2015 at 4:35 PM, Jay Pipes wrote: > On 01/29/2015 12:41 PM, Sean Dague wrote: > >> Correct. This actually came up at the Nova mid cycle in a side >> conversation with Ironic and Neutron folks. >> >> HTTP error codes are not sufficiently granular to describe what happens >> when a R

Re: [openstack-dev] [Keystone] Proposing Marek Denis for the Keystone Core Team

+1 On Tue, Feb 10, 2015 at 11:51 AM, Morgan Fainberg wrote: > Hi everyone! > > I wanted to propose Marek Denis (marekd on IRC) as a new member of the > Keystone Core team. Marek has been instrumental in the implementation of > Federated Identity. His work on Keystone and first hand knowledge of

Re: [openstack-dev] [keystone] SPFE: Authenticated Encryption (AE) Tokens

We get a lot of complaints about problems caused by persistent tokens, so this would be great to see in K. Given the amount of work required to get it done, which includes taking care of some other issues, like getting revocation events working and refactoring the token code (things which could hav

Re: [openstack-dev] [oslo] oslo.concurrency runtime dependency on fixtures/testtools

On Thu, Mar 12, 2015 at 7:20 AM, Davanum Srinivas wrote: > Alan, > > We are debating this on: > https://review.openstack.org/#/c/157135/ > > Please hop on :) > -- dims > > On Thu, Mar 12, 2015 at 5:28 AM, Alan Pevec wrote: > > Hi, > > > > hijacking this thread to point out something that feels w

Re: [openstack-dev] [keystone] What's Up Doc? March 26, 2015 [all]

On Thu, Mar 26, 2015 at 7:37 PM, Anne Gentle wrote: > Here's the latest news installment from docsland. > > Install Guides updates > - > We've got a spec ready for the changes to the Install Guides now published > at: > > http://specs.openstack.org/openstack/docs-specs

Re: [openstack-dev] [Openstack-operators][keystone] Security around enterprise credentials and OpenStack API

On Wed, Apr 1, 2015 at 1:17 AM, Daniel Comnea wrote: > + developers mailing list, hopefully a developer might be able to chime in. > > > > On Wed, Apr 1, 2015 at 3:58 AM, Marc Heckmann > wrote: > >> Hi all, >> >> I was going to post a similar question this evening, so I decided to just >> bounce

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On Thu, Apr 2, 2015 at 4:52 PM, Boris Pavlovic wrote: > Hi stackers, > > Recently, I started working on speeding up Rally cli. > > What I understand immediately is that I don't understand why it takes > 700-800ms > to just run "rally version" command and it is impossible hard task to find > what

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On Sun, Apr 5, 2015 at 5:41 PM, Boris Pavlovic wrote: > Brant, > > I run profimp with and without patch > https://review.openstack.org/#/c/164066/: > And it really works well: > > before 170ms: > http://boris-42.github.io/keystone/before.html > > after 76ms: > http://boris-42.github.io/keystone/a

Re: [openstack-dev] [docs] [End User Guide] [Keystone] keyring support for python-keystoneclient and python-openstackclient

On Tue, Apr 7, 2015 at 3:52 AM, Olena Logvinova wrote: > Good day to everyone! > > My name is Olena, I am new in OpenStack (working as a tech writer). And > I'm stuck on a bug https://launchpad.net/bugs/1419990 (patch > https://review.openstack.org/#/c/163503/). > > I have 2 questions, please: >

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

On Wed, Apr 8, 2015 at 7:59 AM, Doug Hellmann wrote: > Excerpts from Robert Collins's message of 2015-04-07 10:43:30 +1200: > > On 7 April 2015 at 05:11, Joe Gordon wrote: > > > > > > > > > On Mon, Apr 6, 2015 at 8:39 AM, Dolph Mathews > > > > wrote: > > >> > > >> > > >> On Mon, Apr 6, 2015 at

[openstack-dev] [all] Problems with keystoneclient stable branch (and maybe yours too)

There were several problems with the keystoneclient stable/juno branch that have been or are in the process of being fixed since its creation. Hopefully this note will be useful to other projects that create stable branches for their libraries. 1) Unit tests didn't pass with earlier packages The

Re: [openstack-dev] [all] Problems with keystoneclient stable branch (and maybe yours too)

On Mon, Apr 13, 2015 at 9:33 PM, gordon chung wrote: > > > >> 2) Incorrect cap in requirements.txt > >> > >> python-keystoneclient in stable/juno was capped at <=1.1.0, and 1.1.0 is > >> the version tagged for the stable branch. When you create a review in > >> stable/juno it installs python-keys

[openstack-dev] [keystone] keystonemiddleware stable/juno broken

Ever since the stable/juno branch was created for keystonemiddleware it's been broken and there are several changes piling up there. The fix for bug 1408838 "Tests fail with new oslo.utils 1.2.1" allows the tests to pass. I cherry-picked the fix here[1]. Based on the title of the bug, you'd think

[openstack-dev] [keystone] keystoneclient stable/icehouse broken

Ever since the stable/icehouse branch was created for python-keystoneclient it's been broken. There are a couple of issues: 1) The gate-python-keystoneclient-python34 job is failing with the error "ERROR: InterpreterNotFound: python3.4". I don't know why it's not available. Maybe python3 needs to

Re: [openstack-dev] [keystone] keystoneclient stable/icehouse broken

On Sun, Apr 19, 2015 at 3:07 PM, Brant Knudson wrote: > > Ever since the stable/icehouse branch was created for > python-keystoneclient it's been broken. There are a couple of issues: > > 1) The gate-python-keystoneclient-python34 job is failing with the error > &quo

Re: [openstack-dev] [keystone] keystonemiddleware stable/juno broken

On Sun, Apr 19, 2015 at 2:21 PM, Brant Knudson wrote: > > Ever since the stable/juno branch was created for keystonemiddleware it's > been broken and there are several changes piling up there. The fix for bug > 1408838 "Tests fail with new oslo.utils 1.2.1" allows th

Re: [openstack-dev] [keystone] keystonemiddleware stable/juno broken

> broken > > > > > > > > On Sun, Apr 19, 2015 at 2:21 PM, Brant Knudson > > mailto:b...@acm.org>> wrote: > > > > Ever since the stable/juno branch was created for keystonemiddleware > > it's been broken and there are several changes pilin

Re: [openstack-dev] [oslo] eventlet 0.17.3 is now fully Python 3 compatible

On Thu, Apr 23, 2015 at 4:41 AM, Thomas Goirand wrote: > > > On 04/10/2015 09:41 AM, Thierry Carrez wrote: > >> Victor Stinner wrote: >> >>> I fixed 4 issues with monkey-patching in Python 3 (importlib, os.open(), >>> threading.RLock, threading.Thread). Good news: the just released eventlet >>> 0

Re: [openstack-dev] Please stop reviewing code while asking questions

On Fri, Apr 24, 2015 at 3:14 AM, Julien Danjou wrote: > Hi there, > > This is now happening weekly to me now, probably because I write too > many patches touching almost all OpenStack projects once a cycle, and > I'm really tired of that behavior, so PLEASE: > > *Stop sending Code-Review-1 when

Re: [openstack-dev] Please stop reviewing code while asking questions

On Fri, Apr 24, 2015 at 10:06 AM, Salvatore Orlando wrote: > > > On 24 April 2015 at 16:50, Chris Friesen > wrote: > >> On 04/24/2015 07:26 AM, Salvatore Orlando wrote: >> >> If you think it might be beneficial to adjust tooling to that these >>> "contributions" get counted this is fine by me.

Re: [openstack-dev] [Neutron][Keystone] [Nova] How to validate teanant-id for admin operation

On Fri, Apr 24, 2015 at 11:53 AM, Eichberger, German < german.eichber...@hp.com> wrote: > All, > > Following up from the last Neutron meeting: > > If Neutron is performing an operation as an admin on behalf of a user that > user's tenant-id (or project-id) isn't validated - in particular an admin

Re: [openstack-dev] [oslo] Deprecation path?

On Fri, Apr 24, 2015 at 2:21 PM, Robert Collins wrote: > I think it needs a three-step dance. > > 1) Commit the intent to deprecate but don't signal it programmatically. > Python's warnings package has a PendingDeprecationWarning for this -- https://docs.python.org/2.6/library/warnings.html#warn

Re: [openstack-dev] [Congress] [Murano] Congress devstack installation is failing in murano gate job

On Wed, Apr 29, 2015 at 9:11 AM, Sean Dague wrote: > On 04/29/2015 10:05 AM, Sean Dague wrote: > > On 04/29/2015 09:29 AM, Filip Blaha wrote: > >> Hi Serg > >> > >> I checked devstack log [1] and it seems that stevedore==1.4.0 was > >> installed due to congress > >> > >> 2015-04-29 11:12:16.120 >

Re: [openstack-dev] [CI] gate wedged by tox >= 2.0

On Thu, May 14, 2015 at 9:41 AM, Matt Riedemann wrote: > > > On 5/14/2015 5:46 AM, Sean Dague wrote: > >> On 05/14/2015 04:16 AM, Robert Collins wrote: >> >>> Tox 2.0 just came out, and it isolates environment variables - which >>> is good, except if you use them (which we do). So everything is >

Re: [openstack-dev] [nova][cinder][neutron][security] Rootwrap discussions at OSSG mid-cycle

On Thu, May 14, 2015 at 2:48 AM, Angus Lees wrote: > On Wed, 13 May 2015 at 02:16 Thierry Carrez wrote: > >> Lucas Fisher wrote: >> > We spent some time at the OSSG mid-cycle meet-up this week discussing >> root wrap, looking at the existing code, and considering some of the >> mailing list disc

[openstack-dev] [keystone][api] Changing devstack to not set up keystone on :5000 and :35357

At the PTG there was some discussion about changing services to not listen on ports[0]. I'd been working on this for devstack keystone off and on for some time[1], so I thought I'd dust off that work again to see what the problems were. Turns out things must have been fixed since, after rebasing an

Re: [openstack-dev] [keystone][api] Changing devstack to not set up keystone on :5000 and :35357

eting that I didn't know about until later. - Brant > On Fri, Feb 24, 2017 at 9:24 AM, Brant Knudson wrote: > >> >> At the PTG there was some discussion about changing services to not >> listen on ports[0]. I'd been working on this for devstack keystone off and

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On Wed, Mar 8, 2017 at 1:03 PM, Matthew Thode wrote: > So, pycrypto upstream is dead and has been for a while, we should look > at moving off of it for both bugfix and security reasons. > > Currently it's used by the following. > > barbican, cinder, trove, glance, heat, keystoneauth, keystonemidd

Re: [openstack-dev] [oslo][barbican][castellan] Proposal to rename Castellan to oslo.keymanager

On Wed, Mar 15, 2017 at 5:18 AM, Thierry Carrez wrote: > Julien Danjou wrote: > > On Tue, Mar 14 2017, Clint Byrum wrote: > > > >> +1 for just pulling it under the oslo umbrella but not renaming it. As > >> much as I like the uniformity oslo.keymanager would bring, I think it's > >> already adopt

Re: [openstack-dev] [Keystone][Mistral][Devstack] Confusion between auth_url and auth_uri in keystone middleware

On Thu, Jun 15, 2017 at 5:14 AM, Mikhail Fedosin wrote: > Recently I decided to remove deprecated parameters from keystone_authtoken > mistral config and replace them with recommended function of devstack [1]. > In doing so, I discovered a strange behavior of configuration mechanism, > and specif

Re: [openstack-dev] [Keystone][Mistral][Devstack] Confusion between auth_url and auth_uri in keystone middleware

On Thu, Jun 15, 2017 at 1:12 PM, Harry Rybacki wrote: > On Thu, Jun 15, 2017 at 1:57 PM, Brant Knudson wrote: > > > > > > On Thu, Jun 15, 2017 at 5:14 AM, Mikhail Fedosin > wrote: > >> > >> Recently I decided to remove deprecated parameters from &g

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On Thu, Jul 20, 2017 at 8:02 PM, Zane Bitter wrote: > > * If Keystone supported either a public-key or a Kerberos-style > authentication mechanism to get a token Keystone (via support for accepting authentication from the web server hosting it) can be configured to accept X.509 and kerberos, se

Re: [openstack-dev] [api] [tc] Nominatimg Eric Fried for service-types-authority core

> > > If you don't like this idea but would like to say so privately, > > please contact me. Otherwise I'll give a few days and make it so. > > +1 for adding Eric. > > > > > The [tc] tag is on here because the repo is considered "owned by the > > techn

Re: [openstack-dev] [nova][keystone] keystoneauth1 and keystonemiddle setting

On Mon, Aug 14, 2017 at 2:48 AM, Chen CH Ji wrote: > In fixing bug 1704798, there's a proposed patch > https://review.openstack.org/#/c/485121/7 > but we stuck at http_connection_timeout and timeout value in keystoneauth1 > and keystonemiddle repo > > basically we want to reuse the keystone_auth

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

On Wed, Jul 20, 2016 at 12:29 PM, Rob Crittenden wrote: > Rob Crittenden wrote: > >> Andrey Pavlov wrote: >> >>> Hi, >>> >>> When I ran devstack with SSL I found a bug and tried to fix it - >>> https://review.openstack.org/#/c/242812/ >>> But no one agree with me. >>> Try to apply this patch - it

Re: [openstack-dev] [all][infra] Binary Package Dependencies - not only for Python

On Fri, Aug 12, 2016 at 2:53 PM, Jeremy Stanley wrote: > On 2016-08-12 21:20:34 +0200 (+0200), Julien Danjou wrote: > [...] > > If bindep.txt is present, are the "standard" packages still installed? > > If yes, this is going to be more challenging to get bindep.txt right, as > > a missing entry w

Re: [openstack-dev] [keystone] new core reviewer (rderose)

On Thu, Sep 1, 2016 at 9:44 AM, Steve Martinelli wrote: > I want to welcome Ron De Rose (rderose) to the Keystone core team. In a > short time Ron has shown a very positive impact. Ron has contributed > feature work for shadowing LDAP and federated users, as well as enhancing > password support f

Re: [openstack-dev] [congress][oslo.config][keystone] NoSuchOptError: no such option project_domain_name in group [keystone_authtoken]

On Thu, Jan 12, 2017 at 4:31 PM, Eric K wrote: > On a freshly stacked devstack (Jan 12), attempting to access > `cfg.CONF.keystone_authtoken.project_domain_name` gave the > error: NoSuchOptError: no such option project_domain_name in group > [keystone_authtoken] > > I’m a little confused because

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco wrote: > Hi everyone, > > I've seen a few nascent projects wanting to implement their own secret > storage to either replace Barbican or avoid adding a dependency on it. > When I've pressed the developers on this point, the only answer I've > received

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

On Wed, Jan 18, 2017 at 9:58 AM, Dave McCowan (dmccowan) wrote: > > On Mon, Jan 16, 2017 at 7:35 AM, Ian Cordasco > wrote: > >> Hi everyone, >> >> I've seen a few nascent projects wanting to implement their own secret >> storage to either replace Barbican or avoid adding a dependency on it. >> W

Re: [openstack-dev] [keystone] Do we really need two listening ports ?

On Wed, Feb 1, 2017 at 3:54 AM, Attila Fazekas wrote: > Hi all, > > Typically we have two keystone service listening on two separate ports > 35357 and 5000. > > Historically one of the port had limited functionality, but today I do not > see why we want > to have two separate service/port from th

Re: [openstack-dev] [keystone] gate-keystoneclient-dsvm-functional-ubuntu-xenial is broken

On Wed, Sep 21, 2016 at 8:59 AM, Rodrigo Duarte wrote: > After some investigation I've found the possible issue: the functional > tests run in parallel, some of them create and delete roles and others use > tokens to perform the creation/update/delete of other types of fixtures. > The problem is

Re: [openstack-dev] [oslo] Adding ozamiatin to oslo-core

On Mon, Oct 3, 2016 at 12:42 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Oleksii Zamiatin[1] to the oslo-core[2] team. > > Oleksii has been actively contributing to oslo for a while now, both in > helping make oslo better via code contribution(s) and by helping wi

Re: [openstack-dev] [oslo] Adding gdavoian to oslo-core

On Mon, Oct 3, 2016 at 12:40 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Gevorg Davoian[1] to the oslo-core[2] team. > > Gevorg has been actively contributing to oslo for a while now, both in > helping make oslo better via code contribution(s) and by helping with

Re: [openstack-dev] Endpoint structure: a free-for-all

On Wed, Oct 19, 2016 at 2:27 PM, Brian Curtin wrote: ... > > This started back in August when it came up that we didn't know where > that Keystone v3 endpoint was. After talking with a few people, Steve > Martinelli mentioned that at least as of then, hitting the unversioned > endpoint was the wa

Re: [openstack-dev] [all][i18n] how to indicate non-translatable identifiers in translatable strings?

On Wed, Nov 2, 2016 at 11:34 AM, Brian Rosmaita < brian.rosma...@rackspace.com> wrote: > This issue came up during a code review; I've asked around a bit but > haven't been able to find an answer. > > Some of the help output for utility scripts associated with Glance aren't > being translated, so

<    1   2