Re: [openstack-dev] [all][tc] establishing project-wide goals

Excerpts from Jay Pipes's message of 2016-08-01 10:23:57 -0400: > On 08/01/2016 08:33 AM, Sean Dague wrote: > > On 07/29/2016 04:55 PM, Doug Hellmann wrote: > >> One of the outcomes of the discussion at the leadership training > >> session earlier this year was the idea that the TC should set some

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Fox, Kevin M's message of 2016-07-27 22:56:56 +: > I think that would be true, if the container api was opinionated. for > example, trying to map only a subset of the openstack config options to > docker environment variables. This would make the containers specific to what >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Fox, Kevin M's message of 2016-07-27 21:51:15 +: > Its a standard way of launching a given openstack service container with > specified config regardless if its backed with a redhat or ubuntu or source > based package set that the Operator can rely on having a standardized >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Excerpts from Ed Leafe's message of 2016-07-27 10:59:06 -0500: > On Jul 27, 2016, at 10:51 AM, Joshua Harlow wrote: > > >> Whether to have competing projects in the big tent was debated by the TC > >> at the time and my recollection is that we decided that was a good thing

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Fox, Kevin M's message of 2016-07-20 20:12:48 +: > And maybe this raises an interesting defininition mismatch in the > conversation. > > There is archetectural stuff like, do we support 7 different web frameworks, > or do we standardize on flask... python vs go. > Yeah meh,

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from James Bottomley's message of 2016-07-20 08:31:34 -0700: > So this is where the Open Source method takes over. Change is produced > by those people who most care about it because they're invested. To > take your Cinder example, you're unlikely to find them within Cinder > because

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Fox, Kevin M's message of 2016-07-19 21:59:29 +: > Yeah. I'm not saying any project has done it out of malice. Everyone's just > doing whats best for their project. But it does not seem like there is an > overarching entity watching over the whole or (pushing, encouraging, >

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Julien Danjou's message of 2016-07-19 09:30:36 +0200: > On Mon, Jul 18 2016, Joshua Harlow wrote: > > > Thus why I think the starting of the architecture working group is a good > > thing; because I have a believe that people are forgetting among all of this > > that such a group

Re: [openstack-dev] [grenade] upgrades vs rootwrap

Excerpts from Matthew Treinish's message of 2016-07-06 11:55:53 -0400: > On Wed, Jul 06, 2016 at 10:34:49AM -0500, Matt Riedemann wrote: > > On 6/27/2016 6:24 AM, Sean Dague wrote: > > > On 06/26/2016 10:02 PM, Angus Lees wrote: > > > > On Fri, 24 Jun 2016 at 20:48 Sean Dague > >

Re: [openstack-dev] New Python35 Jobs coming

Excerpts from Henry Gessau's message of 2016-07-03 15:26:23 -0400: > Clark Boylan wrote: > > The infra team is working on taking advantage of the new Ubuntu Xenial > > release including running unittests on python35. The current plan is to > > get

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Mike Perez's message of 2016-06-30 14:10:30 -0700: > On 09:02 Jun 30, Clint Byrum wrote: > > Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > > > On 11:31 Jun 20, Clint Byrum wrote: > > > > Excerpts from Joshua Harlow's messag

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Mike Perez's message of 2016-06-30 07:50:42 -0700: > On 11:31 Jun 20, Clint Byrum wrote: > > Excerpts from Joshua Harlow's message of 2016-06-17 15:33:25 -0700: > > > Thanks for getting this started Clint, > > > > > > I'm happy and excited to

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Thanks everyone for participating and remaining positive and focused on improving OpenStack. I've posted a review, and I'd like to encourage everyone to move any future discussion of the Architecture Working group to that review. https://review.openstack.org/335141 Excerpts from Clint Byrum's

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Zhipeng Huang's message of 2016-06-24 18:15:30 +0200: > Hi Clint and Amrith, > > Are you guys already working on the proposal ? Is there any public access > to see the first draft ? > I've started writing something up, and I hope to submit it for review next week.

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: > > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Thursday, June 23, 2016 5:16 PM > > To: openstack-dev > > Subject: Re: [openstack-dev] [all]

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Excerpts from Doug Hellmann's message of 2016-06-23 08:37:04 -0400: > Excerpts from Doug Hellmann's message of 2016-06-13 15:11:17 -0400: > > I'm trying to pull together some information about contributions > > that OpenStack community members have made *upstream* of OpenStack, > > via code, docs,

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Amrith Kumar's message of 2016-06-22 13:15:03 +: > Clint, > > In your original email, you proposed "So, with that, I'd like to propose the > creation of an Architecture Working Group. This group's charge would not be > design by committee, but a place for architects to share

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

Excerpts from Joshua Harlow's message of 2016-06-21 15:12:09 -0700: > Agreed, it appears supported right-now (whether intentional or not), > > So the question at that point is what can we do to make it better... > > I think we all agree that the config-drive probably shouldn't have the >

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Jay Pipes's message of 2016-06-21 14:20:07 -0400: > On 06/21/2016 02:01 PM, Andre Florath wrote: > > Hello Jay, > > > > Yes - the partition alignment is a problem: > > grub2 needs at least 63 blocks between the MBR and the first > > partition. Here for you the partition directly

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jay Pipes's message of 2016-06-21 12:47:46 -0400: > On 06/21/2016 04:25 AM, Chris Dent wrote: > > However, I worry deeply that it could become astronauts with finger > > paints. > > Yes. This. > > I will happily take software design suggestions from people that > demonstrate with

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jay Pipes's message of 2016-06-21 13:29:32 -0400: > On 06/21/2016 12:53 PM, Doug Wiegley wrote: > > Don’t get me wrong, I welcome this initiative. I find it mildly > > disconcerting that the folks that I thought we were electing to fill > > this role will instead be filled by others,

Re: [openstack-dev] [all] Proposal: Architecture Working Group

; Date: June 21, 2016 at 10:18:25 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject:  Re: [openstack-dev] [all] Proposal: Architecture Working Group > > > On Mon, Jun 20, 2016 at 10:59 AM Clint Byrum wrote: >

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Chris Dent's message of 2016-06-21 09:25:44 +0100: > On Mon, 20 Jun 2016, Doug Wiegley wrote: > > > So, it sounds like you’ve just described the job of the TC. And they > > have so far refused to define OpenStack, leading to a series of > > derivative decisions that seem …

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: > On 06/21/2016 07:39 AM, Jay Pipes wrote: > > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: > >> Le 21/06/2016 10:04, Chris Dent a écrit : > >>> On Mon, 20 Jun 2016, Jay Pipes wrote: > >>> > Flask seems to be the most widely

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 09:10:00 -0400: > The amount of wsgi glue above Routes / Paste is pretty minimal (after > you get rid of all the extensions facilities). > > Templating and Session handling are things we don't need. We're not a > webapp, we're a REST service.

Re: [openstack-dev] Version header for OpenStack microversion support

Excerpts from Edward Leafe's message of 2016-06-20 20:41:56 -0500: > On Jun 18, 2016, at 9:03 AM, Clint Byrum <cl...@fewbar.com> wrote: > > > Whatever API version is used behind the compute API is none of the user's > > business. > > Actually, yeah, it is. &g

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Gregory Haynes's message of 2016-06-20 17:24:28 -0500: > On Mon, Jun 20, 2016, at 03:52 PM, Jay Pipes wrote: > > Hi dib-gurus, > > > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd >

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Ahh derp, that's not an ARM CPU. I read "A8" and "APU" and my brain immediately lept to that. Ignore me. Excerpts from Clint Byrum's message of 2016-06-20 15:12:23 -0700: > Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: > > Hi dib-gurus, > > > > I'm trying to build a simple

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Jay Pipes's message of 2016-06-20 16:52:38 -0400: > Hi dib-gurus, > > I'm trying to build a simple ubuntu VM image on a local Gigabyte BRIX > with a AMD A8-5557M APU with Ubuntu 16.04 installed and getting an odd > error. Hoping someone has some ideas... > > The command I am

Re: [openstack-dev] [all] Proposal: Architecture Working Group

p://specs.openstack.org/openstack/openstack-specs/specs/chronicles-of-a-dlm.html > -Josh > > Clint Byrum wrote: > > ar·chi·tec·ture > > ˈärkəˌtek(t)SHər/ > > noun > > noun: architecture > > > > 1. > > > > the art or practice of d

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jesse Cook's message of 2016-06-20 16:58:48 +: > +1 > > The points about the PWG and TC are worth some consideration. > > From my perspective, I think it would make sense for the PWG to define the > expected behaviors of the system, which would be an input to the > architecture

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Michael Krotscheck's message of 2016-06-20 15:26:20 +: > I like the idea in principle, but am bullish on the implementation. > As you should be, and we all must be. It's not going to happen if we just dream it. That's kind of the point. Let's write down a design _for the group

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56 -0600: > So, it sounds like you’ve just described the job of the TC. And they have so > far refused to define OpenStack, leading to a series of derivative decisions > that seem … inconsistent over time. > > How is this body going to be

Re: [openstack-dev] Version header for OpenStack microversion support

Excerpts from Henry Nash's message of 2016-06-18 13:14:17 +0100: > > On 18 Jun 2016, at 11:32, Jamie Lennox wrote: > > > > Quick question: why do we need the service type or name in there? You > > really should know what API you're talking to already and it's just > >

[openstack-dev] [all] Proposal: Architecture Working Group

ar·chi·tec·ture ˈärkəˌtek(t)SHər/ noun noun: architecture 1. the art or practice of designing and constructing buildings. synonyms:building design, building style, planning, building, construction; formalarchitectonics "modern architecture" the style in which a

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

Excerpts from Steven Hardy's message of 2016-06-09 15:03:51 +0100: > Also, while reviewing the core group[2] I noticed the following members who > are no longer active and should probably be removed: > > - Radomir Dopieralski > - Martyn Taylor > - Clint Byrum > > I know

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

Excerpts from Dolph Mathews's message of 2016-06-13 20:11:57 +: > On Fri, Jun 10, 2016 at 12:20 PM Clint Byrum <cl...@fewbar.com> wrote: > > > Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > > > On further reflection, it seems to me that

Re: [openstack-dev] [keystone] Changing the project name uniqueness constraint

Excerpts from Henry Nash's message of 2016-06-10 14:37:37 +0100: > On further reflection, it seems to me that we can never simply enable either > of these approaches in a single release. Even a v4.0 version of the API > doesn’t help - since presumably a sever supporting v4 would want to be able

Re: [openstack-dev] Reasoning behind my vote on the Go topic

Excerpts from Michael Barton's message of 2016-06-09 15:59:24 -0500: > On Thu, Jun 9, 2016 at 2:49 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > > Agreed it isn't done in uvloop. But it is done in libuv and the uvloop > > devs agree it should be done. So this

Re: [openstack-dev] Reasoning behind my vote on the Go topic

Excerpts from Michael Barton's message of 2016-06-09 14:01:11 -0500: > On Thu, Jun 9, 2016 at 9:58 AM, Ben Meyer wrote: > > > > > uvloop (first commit 2015-11-01) is newer than Swift's hummingbird > > (2015-04-20, based on > > > >

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Excerpts from Joshua Harlow's message of 2016-06-07 08:46:28 -0700: > Clint Byrum wrote: > > Excerpts from Kris G. Lindgren's message of 2016-06-06 20:44:26 +: > >> Hi ironic folks, > >> As I'm trying to explore how GoDaddy can use ironic I've created the &

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

Excerpts from Kris G. Lindgren's message of 2016-06-06 20:44:26 +: > Hi ironic folks, > As I'm trying to explore how GoDaddy can use ironic I've created the > following in an attempt to document some of my concerns, and I'm wondering if > you folks could help myself identity ongoing work to

Re: [openstack-dev] [keystone][all] Incorporating performance feedback into the review process

Excerpts from Brant Knudson's message of 2016-06-03 15:16:20 -0500: > On Fri, Jun 3, 2016 at 2:35 PM, Lance Bragstad wrote: > > > Hey all, > > > > I have been curious about impact of providing performance feedback as part > > of the review process. From what I understand,

Re: [openstack-dev] [TripleO][diskimage-builder] Proposing Stephane Miller to dib-core

Excerpts from Gregory Haynes's message of 2016-06-01 12:50:19 -0500: > Hello everyone, > > I'd like to propose adding Stephane Miller (cinerama) to the > diskimage-builder core team. She has been a huge help with our reviews > for some time now and I think she would make a great addition to our >

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

(Top posting as a general reply to the thread) Bugs are precious data. As much as it feels like the bug list is full of cruft that won't ever get touched, one thing that we might be missing in doing this is that the user who encounters the bug and takes the time to actually find the bug tracker

Re: [openstack-dev] [ironic][neutron] bonding?

Excerpts from Jim Rollenhagen's message of 2016-05-24 07:51:21 -0400: > Hi, > > There's rumors floating around about Neutron having a bonding model in > the near future. Are there any solid plans for that? > > For context, as part of the multitenant networking work, ironic has a > portgroup

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Excerpts from Geoff O'Callaghan's message of 2016-05-24 15:31:28 +1000: > > > On 24 May 2016, at 3:13 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > > > [snip] > > > those other needs. Grab a python developer, land some code, and your > > fea

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Excerpts from Geoff O'Callaghan's message of 2016-05-24 14:34:46 +1000: > > > On 24 May 2016, at 2:04 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > > Excerpts from Geoff O'Callaghan's message of 2016-05-24 10:59:13 +1000: > >> Surely openstack is defined

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Excerpts from Geoff O'Callaghan's message of 2016-05-24 10:59:13 +1000: > Surely openstack is defined by it’s capabilities and interfaces rather than > it’s internals. Given the simplistic view that openstack is a collection of > micro services connected by well defined api’s does it really

Re: [openstack-dev] 答复: [Heat][Glance] Can't migrate to glance v2 completely

Excerpts from Erno Kuvaja's message of 2016-05-20 13:20:11 +0100: > > The only reliable way to create Glance images for consumption in general > manner is to make sure that we use the normal workflows (currently > uploading the image to Glance and in future the supported manners of Image >

Re: [openstack-dev] [tc] supporting Go

Excerpts from Thomas Goirand's message of 2016-05-20 12:42:09 +0200: > On 05/11/2016 04:17 PM, Dean Troyer wrote: > > The big difference with Go here is that the dependency work happens at > > build time, not deploy/runtime in most cases. That shifts much of the > > burden to people

Re: [openstack-dev] [tc][ansible][ironic] Reusing Ansible code in OpenStack projects

Excerpts from Pavlo Shchelokovskyy's message of 2016-05-19 15:28:03 +0300: > Hi all, > > I have a question re FOSS licenses interplay. I am pretty sure that > OpenStack community (e.g. openstack-ansible) has already faced such > questions and I would really appreciate any advice. > > We are

Re: [openstack-dev] [tc] [all] [glance] Answers to some questions about Glance

Excerpts from Nikhil Komawar's message of 2016-05-18 11:03:45 -0400: > > On 5/18/16 2:15 AM, Clint Byrum wrote: > > Excerpts from Robert Collins's message of 2016-05-18 14:57:05 +1200: > >> On 18 May 2016 at 00:54, Brian Rosmaita <brian.rosma...@rackspace.com> >

Re: [openstack-dev] [tc] [all] [glance] Answers to some questions about Glance

Excerpts from Robert Collins's message of 2016-05-18 14:57:05 +1200: > On 18 May 2016 at 00:54, Brian Rosmaita wrote: > > >> Couple of examples: > >> 1. switching from "is_public=true" to "visibility=public" > > > > > > This was a major version change in the Images

Re: [openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

I missed your reply originally, so sorry for the 2 week lag... Excerpts from Mike Bayer's message of 2016-04-30 15:14:05 -0500: > > On 04/30/2016 10:50 AM, Clint Byrum wrote: > > Excerpts from Roman Podoliaka's message of 2016-04-29 12:04:49 -0700: > >> > > > >

Re: [openstack-dev] [tc] [all] [glance] On operating a high throughput or otherwise team

Excerpts from Nikhil Komawar's message of 2016-05-14 17:42:16 -0400: > Hi all, > > > Lately I have been involved in discussions that have resulted in giving > a wrong idea to the approach I take in operating the (Glance) team(s). > While my approach is consistency, coherency and agility in

Re: [openstack-dev] [tc] supporting Go

Excerpts from Dieterly, Deklan's message of 2016-05-14 01:18:20 +: > Python 2.x will not be supported for much longer, and let¹s face it, > Python is easy, but it just does not scale. Nor does Python have the > performance characteristics that large, distributed systems require. Maybe > Java

Re: [openstack-dev] [tc] supporting Go

Excerpts from Dmitry Tantsur's message of 2016-05-13 01:14:02 -0700: > On 05/11/2016 09:50 PM, Eric Larson wrote: > > To contrast that, the go POC was able to use a well tested go DNS > > library and implement the same documented interface that was then > > testable via the same functional tests.

Re: [openstack-dev] [tc] supporting Go

Excerpts from Rayson Ho's message of 2016-05-10 07:19:23 -0700: > On Tue, May 10, 2016 at 2:42 AM, Tim Bell wrote: > > I hope that the packaging technologies are considered as part of the TC > evaluation of a new language. While many alternative approaches are > available, a

Re: [openstack-dev] [tc] supporting Go

Excerpts from Edward Leafe's message of 2016-05-09 12:17:40 -0700: > On May 9, 2016, at 1:58 PM, Hayes, Graham wrote: > > > This is not a "Go seems cool - lets go try that" decision from us - we > > know we have a performance problem with one of our components, and we > >

Re: [openstack-dev] [tc] supporting Go

Excerpts from Hayes, Graham's message of 2016-05-09 11:58:38 -0700: > On 09/05/2016 19:39, Ben Swartzlander wrote: > > On 05/09/2016 02:15 PM, Clint Byrum wrote: > >> Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > >>> On Mon, 9 May 2016

Re: [openstack-dev] [tc] supporting Go

Excerpts from Pete Zaitcev's message of 2016-05-09 08:52:16 -0700: > On Mon, 9 May 2016 09:06:02 -0400 > Rayson Ho wrote: > > > Since the Go toolchain is pretty self-contained, most people just follow > > the official instructions to get it installed... by a one-step: > >

Re: [openstack-dev] [tc] supporting Go

Excerpts from Hayes, Graham's message of 2016-05-05 07:26:26 -0700: > On 04/05/2016 00:32, Hayes, Graham wrote: > > On 03/05/2016 17:03, John Dickinson wrote: > >> TC, > >> > >> In reference to > >> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html > >> and Thierry's reply,

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mark Doffman's message of 2016-05-03 17:05:54 -0700: > This thread has been a depressing read. > First, I apologize if any of my actions have caused you any undue stress. > I understand that the content is supposed to be distributed databases > but for me it has become an

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Andrew Laski's message of 2016-05-03 14:46:08 -0700: > > On Mon, May 2, 2016, at 01:13 PM, Edward Leafe wrote: > > On May 2, 2016, at 10:51 AM, Mike Bayer wrote: > > > > >> Concretely, we think that there are three possible approaches: > > >> 1) We can use

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Morgan Fainberg's message of 2016-05-03 11:13:38 -0700: > On Tue, May 3, 2016 at 10:28 AM, Monty Taylor <mord...@inaugust.com> wrote: > > > On 05/03/2016 11:47 AM, Clint Byrum wrote: > > > >> Excerpts from Monty Taylor's message of 2016-05-03 07:59:2

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mike Bayer's message of 2016-05-03 09:04:00 -0700: > > On 05/02/2016 01:48 PM, Clint Byrum wrote: > >> > > > > FWIW, I agree with you. If you're going to use SQLAlchemy, use it to > > take advantage of the relational model. > > > > How

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Adam Young's message of 2016-05-03 07:21:52 -0700: > On 05/03/2016 09:55 AM, Clint Byrum wrote: > > When the operator has configured a new token format to emit, they should > > also be able to allow any previously emitted formats to be validated to > > allow user

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Lance Bragstad's message of 2016-05-03 07:42:43 -0700: > If we were to write a uuid/fernet hybrid provider, it would only be > expected to support something like stable/liberty to stable/mitaka, right? > This is something that we could contribute to stackforge, too. > If done the

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Monty Taylor's message of 2016-05-03 07:59:21 -0700: > On 05/03/2016 08:55 AM, Clint Byrum wrote: > > > > Perhaps we have different perspectives. How is accepting what we > > previously emitted and told the user would be valid sneaky or wrong? > > S

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Edward Leafe's message of 2016-05-03 08:20:36 -0700: > On May 3, 2016, at 6:45 AM, Miles Gould wrote: > > >> This DB could be an RDBMS or Cassandra, depending on the deployer's > >> preferences > > AFAICT this would mean introducing and maintaining a layer that

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Steve Martinelli's message of 2016-05-02 19:56:15 -0700: > Comments inline... > > On Mon, May 2, 2016 at 7:39 PM, Matt Fischer <m...@mattfischer.com> wrote: > > > On Mon, May 2, 2016 at 5:26 PM, Clint Byrum <cl...@fewbar.com> wrote: > > >

Re: [openstack-dev] [keystone] Token providers and Fernet as the default

Excerpts from Matt Fischer's message of 2016-05-02 16:39:02 -0700: > On Mon, May 2, 2016 at 5:26 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > Hello! I enjoyed very much listening in on the default token provider > > work session last week in Austin, so thanks ev

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Jay Pipes's message of 2016-05-02 10:43:21 -0700: > On 05/02/2016 11:51 AM, Mike Bayer wrote: > > On 05/02/2016 07:38 AM, Matthieu Simonin wrote: > >> As far as we understand the idea of an ORM is to hide the relational > >> database with an Object oriented API. > > > > I actually

[openstack-dev] [keystone] Token providers and Fernet as the default

Hello! I enjoyed very much listening in on the default token provider work session last week in Austin, so thanks everyone for participating in that. I did not speak up then, because I wasn't really sure of this idea that has been bouncing around in my head, but now I think it's the case and we

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mike Bayer's message of 2016-05-02 08:51:58 -0700: > > Well IMO that's actually often a problem. My goal across Openstack > projects in general is to allow them to make use of SQL more effectively > than they do right now; for example, in Neutron I am helping them to > move a

Re: [openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

Excerpts from Roman Podoliaka's message of 2016-04-29 12:04:49 -0700: > Hi Bogdan, > > Thank you for sharing this! I'll need to familiarize myself with this > Jepsen thing, but overall it looks interesting. > > As it turns out, we already run Galera in multi-writer mode in Fuel > unintentionally

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Matt Riedemann's message of 2016-04-29 05:38:17 -0700: > > So, we're all here in person this week (with 1 day left). The Nova team > has a meetup session all day (Salon A in the Hilton). Clint/Ed, can you > guys show up to that and bring these issues up in person so we can >

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Mike Bayer's message of 2016-04-28 22:16:54 -0500: > > On 04/28/2016 08:25 PM, Edward Leafe wrote: > > > Your own tests showed that a single RDBMS instance doesn’t even break a > > sweat > > under your test loads. I don’t see why we need to shard it in the first > > place,

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Jay Pipes's message of 2016-04-28 13:09:29 -0500: > On 04/28/2016 08:44 AM, Edward Leafe wrote: > > On Apr 24, 2016, at 3:28 PM, Robert Collins > > wrote: > >> For instance, the things I think are essential for a distributed > >> database based datastore:

Re: [openstack-dev] [nova] Distributed Database

Excerpts from Andrew Laski's message of 2016-04-22 14:32:59 -0700: > > On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote: > > OK, so I know that Friday afternoons are usually the worst times to > > write a blog post and start an email discussion, and that the Friday > > immediately before a

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Chivers, Doug's message of 2016-04-22 10:17:45 -0700: > The Vancouver core party was a fantastic opportunity to meet some very smart > people and learn a lot about the projects they worked on. It was probably one > of the most useful parts of the summit, certainly more so than the

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Thierry Carrez's message of 2016-04-21 09:22:53 -0700: > Michael Krotscheck wrote: > > So, HPE is seeking sponsors to continue the core party. The reasons are > > varied - internal sponsors have moved to other projects, the Big Tent > > has drastically increased the # of cores, and

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Thomas Goirand's message of 2016-04-19 05:59:19 -0700: > On 04/19/2016 01:01 PM, Chris Dent wrote: > > We also, however, need to consider what the future might look like and > > at least for some people and situations > > I agree. > > > the future does not involve > > debs or rpms

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Matthew Thode's message of 2016-04-18 11:22:38 -0700: > On 04/18/2016 12:33 PM, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2016-04-18 10:23:37 -0500: > >> On 04/18/2016 08:24 AM, Hayes, Graham wrote: > >>> On 18/04/2016 13:51, Sean Dague wrote: > On

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Michał Jastrzębski's message of 2016-04-18 10:29:20 -0700: > What I meant is if you have liberty Nova and liberty Cinder, and you > want to upgrade Nova to Mitaka, you also upgrade Oslo to Mitaka and > Cinder which was liberty either needs to be upgraded or is broken, > therefore

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Excerpts from Clayton O'Neill's message of 2016-04-13 07:37:16 -0700: > On Wed, Apr 13, 2016 at 10:26 AM, rezroo wrote: > > Hi Kevin, > > > > I understand that this is how it is now. My question is how bad would it be > > to wrap the Barbican client library calls in another

Re: [openstack-dev] [magnum][keystone][all] Using Keystone /v3/credentials to store TLS certificates

Excerpts from Douglas Mendizábal's message of 2016-04-13 10:01:21 -0700: > Hash: SHA512 > > Hi Reza, > > The Barbican team has already abstracted python-barbicanclient into a > general purpose key-storage library called Castellan [1] > > There are a few OpenStack projects that have planned to

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

Excerpts from Morgan Fainberg's message of 2016-04-10 16:47:28 -0700: > On Sun, Apr 10, 2016 at 4:37 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > > > There is also disincentive in +1ing a chang

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: > There is also disincentive in +1ing a change that you don't understand > and is wrong and then a core comes along and -1s it (you get dinged for > the disagreement). And there is disincentive in -1ing a change for the >

Re: [openstack-dev] [TripleO] FreeIPA integration

Excerpts from Adam Young's message of 2016-04-05 19:02:58 -0700: > On 04/05/2016 11:42 AM, Fox, Kevin M wrote: > > Yeah, and they just deprecated vendor data plugins too, which > > eliminates my other workaround. :/ > > > > We need to really discuss this problem at the summit and get a viable >

Re: [openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

Excerpts from Nikhil Komawar's message of 2016-04-06 10:46:28 -0700: > Need a inline clarification. > > On 4/6/16 10:58 AM, Flavio Percoco wrote: > > On 06/04/16 08:26 -0400, Sean Dague wrote: > >> On 04/06/2016 04:13 AM, Markus Zoeller wrote: > >>> +1 for deprecation and removal > >>> > >>> To

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are we ready?

Excerpts from Samuel Bercovici's message of 2016-03-02 07:06:30 -0800: > 2. HEAT Support - will it be ready in Mitaka? Side note, please remember, Heat is not an acronym. __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [all] A proposal to separate the design summit

Excerpts from Eoghan Glynn's message of 2016-03-01 02:08:00 -0800: > > > > Current thinking would be to give preferential rates to access the > > > main > > > summit to people who are present to other events (like this new > > > separated contributors-oriented event, or Ops

Re: [openstack-dev] [heat] convergence cancel messages

Excerpts from Anant Patil's message of 2016-02-23 23:08:31 -0800: > Hi, > > I would like the discuss various approaches towards fixing bug > https://launchpad.net/bugs/1533176 > > When convergence is on, and if the stack is stuck, there is no way to > cancel the existing request. This feature

Re: [openstack-dev] [heat] convergence cancel messages

Excerpts from Anant Patil's message of 2016-02-24 00:56:34 -0800: > On 24-Feb-16 13:12, Clint Byrum wrote: > > Excerpts from Anant Patil's message of 2016-02-23 23:08:31 -0800: > >> Hi, > >> > >> I would like the discuss various approaches towards fixing bug >

Re: [openstack-dev] [heat] convergence cancel messages

Excerpts from Anant Patil's message of 2016-02-23 23:08:31 -0800: > Hi, > > I would like the discuss various approaches towards fixing bug > https://launchpad.net/bugs/1533176 > > When convergence is on, and if the stack is stuck, there is no way to > cancel the existing request. This feature

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

Excerpts from Jay Pipes's message of 2016-02-23 16:10:46 -0800: > On 02/22/2016 04:23 AM, Sylvain Bauza wrote: > > I won't argue against performance here. You made a very nice PoC for > > testing scaling DB writes within a single python process and I trust > > your findings. While I would be

Re: [openstack-dev] [all] A proposal to separate the design summit

Excerpts from Eoghan Glynn's message of 2016-02-22 15:06:01 -0800: > > > Hi everyone, > > > > TL;DR: Let's split the events, starting after Barcelona. > > > > Long long version: > > > > In a global and virtual community, high-bandwidth face-to-face time is > > essential. This is why we made

Re: [openstack-dev] [all] A proposal to separate the design summit

Excerpts from Sean McGinnis's message of 2016-02-22 11:48:50 -0800: > On Mon, Feb 22, 2016 at 05:20:21PM +, Amrith Kumar wrote: > > Thierry and all of those who contributed to putting together this write-up, > > thank you very much. > > > > TL;DR: +0 > > > > Longer version: > > > > While I

<    1   2   3   4   5   6   7   8   9   10   >