[openstack-dev] [kolla][nova] Safe guest shutdowns with kolla?

Greetings! We've been deploying with Kolla on CentOS 7 now for a while, and we've recently noticed a rather troubling behavior when we shutdown hypervisors. Somewhere between systemd and libvirt's systemd-machined integration, we see that guests get killed aggressively by SIGTERM'ing all of the

Re: [openstack-dev] [tc][all] CD tangent - was: A culture change (nitpicking)

Quoting Sean McGinnis (2018-05-31 09:54:46) > On 05/31/2018 03:50 AM, Thierry Carrez wrote: > > Right... There might be a reasonable middle ground between "every > > commit on master must be backward-compatible" and "rip out all > > testing" that allows us to routinely revert broken feature

Re: [openstack-dev] [tripleo] storyboard evaluation

Excerpts from Thierry Carrez's message of 2018-01-17 11:51:52 +0100: > Emilien Macchi wrote: > > On Tue, Jan 16, 2018 at 8:29 AM, Jeremy Stanley wrote: > >>> - how do we deal milestones in stories and also how can we have a > >>> dashboard with an overview per milestone (useful

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Thomas Goirand's message of 2017-12-15 16:15:04 +0100: > On 12/14/2017 12:44 AM, Clint Byrum wrote: > > We can take stock of the intermediate releases over the last year, and make > > sure they all work together once a year. Chris Jones mentioned that we > >

Re: [openstack-dev] [all] Switching to longer development cycles

I feel like the thing not stated is that what we really don't like is that our users are falling behind. Sure, pressure in release time is definitely real. Multiple PTG's and forums feels like people are missing out. But what's really awful is that some of our users are stuck down in the bottom of

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Ed Leafe's message of 2017-12-13 22:55:43 -0600: > On Dec 13, 2017, at 4:38 PM, German Eichberger > wrote: > > > It looks like the implicit expectation is that devs also need to attend the > > Forums at the summit in addition to the PTG. The

Re: [openstack-dev] [all] Switching to longer development cycles

Dec. 2017 18:00, "Clint Byrum" <cl...@fewbar.com> wrote: > > > Excerpts from Blair Bethwaite's message of 2017-12-14 17:44:53 +1100: > > > On 14 December 2017 at 17:36, Clint Byrum <cl...@fewbar.com> wrote: > > > > The batch size for "upgrade

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Blair Bethwaite's message of 2017-12-14 17:44:53 +1100: > On 14 December 2017 at 17:36, Clint Byrum <cl...@fewbar.com> wrote: > > The batch size for "upgrade the whole cloud" is too big. Let's help our > > users advance components one at a time, and the

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Ed Leafe's message of 2017-12-13 23:02:11 -0600: > On Dec 13, 2017, at 5:44 PM, Clint Byrum <cl...@fewbar.com> wrote: > > > One thing I've always admired about Swift was how immune to the cadence > > Swift > > appears to be. > > As I've poin

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Ed Leafe's message of 2017-12-13 22:51:19 -0600: > On Dec 13, 2017, at 4:31 PM, Doug Hellmann wrote: > > > You're missing the key point that coupled with the change in the > > overall development cycle schedule we would be encouraging projects > > to release

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Thierry Carrez's message of 2017-12-13 17:17:26 +0100: > Hi everyone, > > Over the past year, it has become pretty obvious to me that our > self-imposed rhythm no longer matches our natural pace. It feels like we > are always running elections, feature freeze is always just around

Re: [openstack-dev] [all] Switching to longer development cycles

Excerpts from Chris Jones's message of 2017-12-13 19:25:03 +: > Hey > > On 13 December 2017 at 17:31, Thierry Carrez wrote: > > > See attached for the PDF strawman the release team came up with when > > considering how that change would roll out in practice... > > >

Re: [openstack-dev] [tc] [all] TC Report 49

Excerpts from Graham Hayes's message of 2017-12-07 17:08:55 +: > > On 06/12/17 23:33, James E. Blair wrote: > > Chris Dent writes: > > > >> The expansion of the Foundation was talked about at the summit in > >> Sydney, but having something happen this quickly was a

Re: [openstack-dev] Removing internet access from unit test gates

Excerpts from Jens Harbott's message of 2017-11-24 13:22:23 +: > 2017-11-21 15:04 GMT+00:00 Jeremy Stanley : > > On 2017-11-21 09:28:20 +0100 (+0100), Thomas Goirand wrote: > > [...] > >> The only way that I see going forward, is having internet access > >> removed from unit

Re: [openstack-dev] [nova] key_pair update on rebuild (a whole lot of conversations)

Excerpts from Ben Nemec's message of 2017-10-03 23:05:49 -0500: > > On 10/03/2017 03:16 PM, Sean Dague wrote: > > = Where I think we are? = > > > > I think with all this data we're at the following: > > > > Q: Should we add this to rebuild > > A: Yes, probably - after some enhancement to the

Re: [openstack-dev] Fwd: [Openstack-operators][tc] [keystone][all] v2.0 API removal

Excerpts from Jeremy Stanley's message of 2017-10-21 13:37:01 +: > On 2017-10-20 22:50:53 + (+), Fox, Kevin M wrote: > [...] > > Ideally, there should be an OpenStack overarching architecture > > team of some sort to handle this kind of thing I think. > > There was one for a while,

Re: [openstack-dev] Supporting SSH host certificates

And k8s has the benefit of already having been installed with certs that had to get there somehow.. through a trust bootstrap.. usually SSH. ;) Excerpts from Fox, Kevin M's message of 2017-10-09 17:37:17 +: > Yeah, there is a way to do it today. it really sucks though for most users. > Due

Re: [openstack-dev] Supporting SSH host certificates

Excerpts from Giuseppe de Candia's message of 2017-10-06 13:49:43 -0500: > Hi Clint, > > Isn't user-data by definition available via the Metadata API, which isn't > considered secure: > https://wiki.openstack.org/wiki/OSSN/OSSN-0074 > Correct! The thinking is to account for the MITM attack

Re: [openstack-dev] Supporting SSH host certificates

A long time ago, a few Canonical employees (Scott Moser was one of them, forget who else was doing it, maybe Dave Walker and/or Dustin Kirkland) worked out a scheme for general usage that doesn't require extra plumbing: * Client generates a small SSH host key locally and pushes it into user

Re: [openstack-dev] [nova] key_pair update on rebuild (a whole lot of conversations)

Excerpts from Sean Dague's message of 2017-10-03 16:16:48 -0400: > There is currently a spec up for being able to specify a new key_pair > name during the rebuild operation in Nova - > https://review.openstack.org/#/c/375221/ > > For those not completely familiar with Nova operations, rebuild

Re: [openstack-dev] [ptg] Simplification in OpenStack

Excerpts from Jonathan Proulx's message of 2017-09-26 16:01:26 -0400: > On Tue, Sep 26, 2017 at 12:16:30PM -0700, Clint Byrum wrote: > > :OpenStack is big. Big enough that a user will likely be fine with learning > :a new set of tools to manage it. > > New users in the st

Re: [openstack-dev] [ptg] Simplification in OpenStack

Excerpts from Samuel Cassiba's message of 2017-09-25 17:27:25 -0700: > > > On Sep 25, 2017, at 16:52, Clint Byrum <cl...@fewbar.com> wrote: > > > > Excerpts from Jonathan D. Proulx's message of 2017-09-25 11:18:51 -0400: > >> On Sat, Sep 23, 2017 at

Re: [openstack-dev] [ptg] Simplification in OpenStack

Excerpts from Jonathan D. Proulx's message of 2017-09-25 11:18:51 -0400: > On Sat, Sep 23, 2017 at 12:05:38AM -0700, Adam Lawson wrote: > > :Lastly, I do think GUI's make deployments easier and because of that, I > :feel they're critical. There is more than one vendor whose built and >

Re: [openstack-dev] [ptg] Simplification in OpenStack

Excerpts from Jeremy Stanley's message of 2017-09-21 16:17:00 +: > On 2017-09-20 17:39:38 -0700 (-0700), Clint Byrum wrote: > [...] > > Something about common use cases and the exact mix of > > projects + configuration to get there, and testing it? Help? > [...] >

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

Excerpts from Michael Still's message of 2017-09-20 10:25:17 -0600: > Dims, I'm not sure that's actually possible though. Many of these files > have been through rewrites and developed over a large number of years. > Listing all authors isn't practical. > > Given the horse has bolted on forking

Re: [openstack-dev] [ptg] Simplification in OpenStack

Wading in a bit late as I've been off-list for a while, but I have thoughts here. Excerpts from Jay Pipes's message of 2017-09-13 13:44:55 -0400: > On 09/12/2017 06:53 PM, Boris Pavlovic wrote: > > Mike, > > > > Great intiative, unfortunately I wasn't able to attend it, however I > > have some

Re: [openstack-dev] [glance] docs: architecture or hw_architecture

Excerpts from Dean Troyer's message of 2017-08-23 13:48:07 -0500: > On Wed, Aug 23, 2017 at 12:33 PM, Brian Rosmaita > wrote: > > My point is just that Glance went one way on this, Nova went a > > different way, and users are left hanging. My secondary point is that >

Re: [openstack-dev] [all][infra]Plan to support Python 3.6 ?

Ubuntu will ship Python 3.6 in the next LTS, Ubuntu 18.04 next April. AFAICT CentOS 7 still doesn't ship Python 3 in mainline. EPEL has 3.4 still. Excerpts from Doug Hellmann's message of 2017-08-09 09:31:37 -0400: > Excerpts from ChangBo Guo's message of 2017-08-09 21:25:07 +0800: > > We

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI

Excerpts from Matt Riedemann's message of 2017-08-07 14:33:22 -0500: > On 8/3/2017 1:39 PM, Boden Russell wrote: > > I think we have a gap in our OSC CLI for non-stadium plugin/driver > > projects (neutron plugin projects, nova driver projects) that implement > > RESTful resource API attribute

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Excerpts from Bogdan Dobrelya's message of 2017-07-14 18:14:42 +0200: > On 14.07.2017 17:55, Michał Jastrzębski wrote: > > Guys you just described Kolla-Kubernetes pretty much... how about > > we join effort and work towards this goal together? > > That's exactly that I'd like we all to do. >

Re: [openstack-dev] [congress] Using congress to improve the consistency of configuration files.

Excerpts from valentin.matton's message of 2017-07-04 15:29:25 +0200: > We would like to use congress to check the consistency of the > configuration files used by the various Openstack services on different > nodes. > > Although installers do a great job for ensuring that the initial >

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

This message makes a bunch of salient, valid points, none of which I wish to directly address. However, on the whole, I think the analysis stops short of pushing through to a root cause, and thus, the solution proposed is entirely focused on symptoms. The root cause of all of this until now has

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

tl;dr - I think Trove's successor has a future, but there are two conflicting ideas presented and Trove should pick one or the other. Excerpts from Amrith Kumar's message of 2017-06-18 07:35:49 -0400: > > We have learned a lot from v1, and the hope is that we can address that in > v2. Some of

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Excerpts from Jay Pipes's message of 2017-06-20 10:08:54 -0400: > On 06/20/2017 09:42 AM, Doug Hellmann wrote: > > Does "service VM" need to be a first-class thing? Akanda creates > > them, using a service user. The VMs are tied to a "router" which > > is the billable resource that the user

Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

Excerpts from Alexandre Lécuyer's message of 2017-06-19 11:36:15 +0200: > Hello Clint, > > Thanks for your feedback, replying in the email inline. > > On 06/16/2017 10:54 PM, Clint Byrum wrote: > > Excerpts from John Dickinson's message of 2017-06-16 11:35:39 -0700: > >

Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

Excerpts from John Dickinson's message of 2017-06-16 11:35:39 -0700: > > On 16 Jun 2017, at 10:51, Clint Byrum wrote: > > > This is great work. > > > > I'm sure you've already thought of this, but could you explain why > > you've chosen not to put the small

Re: [openstack-dev] [swift] Optimizing storage for small objects in Swift

This is great work. I'm sure you've already thought of this, but could you explain why you've chosen not to put the small objects in the k/v store as part of the value rather than in secondary large files? Excerpts from Alexandre Lécuyer's message of 2017-06-16 15:54:08 +0200: > Swift stores

Re: [openstack-dev] [all] etcd3 as base service - update

Excerpts from Lance Bragstad's message of 2017-06-08 16:10:00 -0500: > On Thu, Jun 8, 2017 at 3:21 PM, Emilien Macchi wrote: > > > On Thu, Jun 8, 2017 at 7:34 PM, Lance Bragstad > > wrote: > > > After digging into etcd a bit, one place this might be help

Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master

Excerpts from Jay Pipes's message of 2017-05-30 21:06:59 -0400: > On 05/30/2017 05:07 PM, Clint Byrum wrote: > > Excerpts from Jay Pipes's message of 2017-05-30 14:52:01 -0400: > >> Sorry for the delay in getting back on this... comments inline. > >> > >> O

Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master

Excerpts from Jay Pipes's message of 2017-05-30 14:52:01 -0400: > Sorry for the delay in getting back on this... comments inline. > > On 05/18/2017 06:13 PM, Adrian Turjak wrote: > > Hello fellow OpenStackers, > > > > For the last while I've been looking at options for multi-region > >

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

Excerpts from Clark Boylan's message of 2017-05-19 10:03:23 -0700: > On Fri, May 19, 2017, at 05:59 AM, Duncan Thomas wrote: > > On 19 May 2017 at 12:24, Sean Dague wrote: > > > > > I do get the concerns of extra logic in Nova, but the decision to break > > > up the working

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Excerpts from Michał Jastrzębski's message of 2017-05-15 10:52:12 -0700: > > Container images introduce some extra complexity, over the basic > > operating system style packages mentioned above. Due to the way > > they are constructed, they are likely to include content we don't > > produce

Re: [openstack-dev] [oslo][concurrency] lockutils lock fairness / starvation

Excerpts from Ben Nemec's message of 2017-05-15 15:48:33 -0500: > > On 05/15/2017 03:24 PM, Doug Hellmann wrote: > > Excerpts from Legacy, Allain's message of 2017-05-15 19:20:46 +: > >>> -Original Message- > >>> From: Doug Hellmann [mailto:d...@doughellmann.com] > >>> Sent: Monday,

Re: [openstack-dev] [architecture] Arch-WG, we hardly knew ye..

Excerpts from lebre.adrien's message of 2017-04-07 15:50:05 +0200: > Dear Clint, Dear all, > > It is indeed unfortunate that the WG ends. > > From our side (Inria folks from the Discovery initiative [1]), we had planned > to join the effort after the Boston Summit as we are currently

[openstack-dev] [architecture] Arch-WG, we hardly knew ye..

I'm going to be blunt. I'm folding the Architecture Working Group immediately following our meeting today at 2000 UTC. We'll be using the time to discuss continuity of the base-services proposal, and any other draw-down necessary. After that our meetings will cease. I had high hopes for the

Re: [openstack-dev] [kubernetes][go] External OpenStack Cloud Provider for Kubernetes

Excerpts from Chris Hoge's message of 2017-04-04 17:09:11 -0400: > > > On Apr 2, 2017, at 4:29 PM, Monty Taylor wrote: > > > > On 03/29/2017 03:39 PM, Steve Gordon wrote: > >> - Original Message - > >>> From: "Davanum Srinivas" > >>> To: "Chris

Re: [openstack-dev] [oslo][requirements][designate][cinder] Reverting eventlet version bump

Excerpts from Monty Taylor's message of 2017-04-04 12:19:36 -0500: > On 04/04/2017 09:19 AM, Jay S Bryant wrote: > > Monty, > > > > I agree with your approach. Think we should not break other projects > > with a change like this and the answer thus far has been to just patch > > each project

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Sean Dague's message of 2017-03-15 08:54:55 -0400: > On 03/15/2017 02:16 AM, Clint Byrum wrote: > > Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: > >> On 03/14/2017 06:04 PM, Davanum Srinivas wrote: > >>> Team, > >>> >

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Doug Hellmann's message of 2017-03-15 15:35:13 -0400: > Excerpts from Thomas Herve's message of 2017-03-15 09:41:16 +0100: > > On Wed, Mar 15, 2017 at 12:05 AM, Joshua Harlow > > wrote: > > > > > * How does reloading work (does it)? > > > > No. There is

Re: [openstack-dev] [infra][security] Encryption in Zuul v3

Excerpts from corvus's message of 2017-03-21 09:36:41 -0700: > Hi, > > In working on the implementation of the encrypted secrets feature of > Zuul v3, I have found some things that warrant further discussion. It's > important to be deliberate about this and I welcome any feedback. > Thanks for

Re: [openstack-dev] [infra][security] Encryption in Zuul v3

Excerpts from Matthieu Huin's message of 2017-03-21 18:43:49 +0100: > Hello James, > > Thanks for opening the discussion on this topic. I'd like to mention that a > very common type of secrets that are used in Continuous Deployments > scenarios are SSH keys. Correct me if I am wrong, but PKCS#1

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Excerpts from Adrian Otto's message of 2017-03-20 22:19:14 +: > I was unsure, so I found him on IRC to clarify, and he pointed me to the > openstack/service-types-authority repository, where I submitted patch 445694 > for review. We have three distinct identifiers in play: > > 1) Our

Re: [openstack-dev] [magnum][osc] What name to use for magnum commands in osc?

Excerpts from Adrian Otto's message of 2017-03-20 21:16:09 +: > Jay, > > On Mar 20, 2017, at 12:35 PM, Jay Pipes > > wrote: > > On 03/20/2017 03:08 PM, Adrian Otto wrote: > Team, > > Stephen Watson has been working on an magnum feature to add

Re: [openstack-dev] [dib][heat] dib-utils/dib-run-parts/dib v2 concern

Excerpts from Clark Boylan's message of 2017-03-16 10:16:37 -0700: > On Thu, Mar 16, 2017, at 09:46 AM, Steven Hardy wrote: > > On Thu, Mar 16, 2017 at 10:30:48AM -0500, Gregory Haynes wrote: > > > On Thu, Mar 16, 2017, at 05:18 AM, Steven Hardy wrote: > > > > On Wed, Mar 15, 2017 at 04:22:37PM

Re: [openstack-dev] [all][ironic] Kubernetes-based long running processes

Excerpts from Dean Troyer's message of 2017-03-16 12:19:36 -0500: > On Wed, Mar 15, 2017 at 5:28 PM, Taryma, Joanna > wrote: > > I’m reaching out to you to ask if you’re aware of any other use cases that > > could leverage such solution. If there’s a need for it in other

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Jay Pipes's message of 2017-03-15 15:06:26 -0400: > +Boris B > > On 03/15/2017 02:55 PM, Fox, Kevin M wrote: > > I think they are. If they are not, things will break if federation is used > > for sure. If you know that it is please let me know. I want to deploy > > federation at

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Excerpts from Clark Boylan's message of 2017-03-15 09:50:49 -0700: > On Wed, Mar 15, 2017, at 06:19 AM, Monty Taylor wrote: > > On 03/15/2017 11:37 AM, Davanum Srinivas wrote: > > > Monty, Team, > > > > > > Sorry for the top post: > > > > > > Support for etcd/tooz in devstack (with file driver

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Kristi Nikolla's message of 2017-03-15 12:35:45 -0400: > This might be related to the current discussion. > > In one of the keystone PTG sessions we started to talk about API keys. [0] > A spec is being written and discussed. [1] > > This would allow the user to provision API key

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Sean Dague's message of 2017-03-15 08:45:54 -0400: > On 03/13/2017 05:10 PM, Zane Bitter wrote: > > >> I'm not sure I agree. One can very simply inject needed credentials > >> into a running VM and have it interact with the cloud APIs. > > > > Demo please! > > > > Most Keystone

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Excerpts from Jay Pipes's message of 2017-03-14 22:13:32 -0400: > On 03/14/2017 05:01 PM, Clint Byrum wrote: > > Excerpts from Jay Pipes's message of 2017-03-14 15:30:32 -0400: > >> On 03/14/2017 02:50 PM, Julien Danjou wrote: > >>> On Tue, Mar 14 2017, Jay Pipe

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Monty Taylor's message of 2017-03-15 04:36:24 +0100: > On 03/14/2017 06:04 PM, Davanum Srinivas wrote: > > Team, > > > > So one more thing popped up again on IRC: > > https://etherpad.openstack.org/p/oslo.config_etcd_backend > > > > What do you think? interested in this work? > >

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Fox, Kevin M's message of 2017-03-15 00:10:24 +: > +1 for having the option. I think in general it is a great idea. > > I think there are some devils in the implementation. How do you prevent > a service from getting way more secrets then it strictly needs? Maybe > this is the

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

Excerpts from Doug Hellmann's message of 2017-03-14 20:05:54 -0400: > Excerpts from Doug Hellmann's message of 2017-03-14 19:20:08 -0400: > > Excerpts from Clint Byrum's message of 2017-03-13 13:49:22 -0700: > > > Excerpts from Doug Hellmann's message of 2017-03-13 15:12:42 -0400: > > > > Excerpts

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

Excerpts from Davanum Srinivas's message of 2017-03-14 13:04:37 -0400: > Team, > > So one more thing popped up again on IRC: > https://etherpad.openstack.org/p/oslo.config_etcd_backend > > What do you think? interested in this work? > > Thanks, > Dims > > PS: Between this thread and the other

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Excerpts from Jay Pipes's message of 2017-03-14 15:30:32 -0400: > On 03/14/2017 02:50 PM, Julien Danjou wrote: > > On Tue, Mar 14 2017, Jay Pipes wrote: > > > >> Not tooz, because I'm not interested in a DLM nor leader election library > >> (that's what the underlying etcd3 cluster handles for

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

Excerpts from Fox, Kevin M's message of 2017-03-14 00:09:55 +: > With my operator hat on, I would like to use the etcd backend, as I'm already > paying the cost of maintaining etcd clusters as part of Kubernetes. Adding > Zookeeper is a lot more work. > It would probably be a good idea to

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

Excerpts from Doug Hellmann's message of 2017-03-13 15:12:42 -0400: > Excerpts from Farr, Kaitlin M.'s message of 2017-03-13 18:55:18 +: > > Proposed library name: Rename Castellan to oslo.keymanager > > > > Proposed library mission/motivation: Castellan's goal is to provide a > > generic key

Re: [openstack-dev] [all] Small steps for Go

Excerpts from Davanum Srinivas's message of 2017-03-13 14:32:16 -0400: > Clint, > > There's some discussion on the etherpad, don't want to move that here. > Ok. I don't see much that explains why. But either way, IMO this is why an etherpad is a really bad place to have a discussion. Great for

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

t; Thats ok if those folks have no where else to go. They do now, and are > starting to do so as there are more options. > > Openstack needs to abandon that phylosophy. It can no longer afford it. > > Thanks, > Kevin > > > From: Clint

Re: [openstack-dev] [all] Small steps for Go

Excerpts from Davanum Srinivas's message of 2017-03-13 10:06:30 -0400: > Update: > > * We have a new git repo (EMPTY!) for the commons work - > http://git.openstack.org/cgit/openstack/golang-commons/ > * The golang-client has little code, but lot of potential - >

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Fox, Kevin M's message of 2017-03-12 16:54:20 +: > I totally agree that policy management is a major problem too. A much bigger > one then instance users, and something I was hoping to get to after instance > users, but never made it past the easier of the two. :/ > > > The

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Fox, Kevin M's message of 2017-03-11 21:31:40 +: > No, they are treated as second class citizens. Take Trova again as an > example. The underlying OpenStack infrastructure does not provide a good > security solution for Trove's use case. As its more then just IaaS. So they >

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Christopher Aedo's message of 2017-03-10 19:30:18 -0800: > On Fri, Mar 10, 2017 at 6:20 PM, Clint Byrum <cl...@fewbar.com> wrote: > > Excerpts from Fox, Kevin M's message of 2017-03-10 23:45:06 +: > >> So, this is the kind of thinking I'm talking

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Zane Bitter's message of 2017-03-10 19:09:42 -0500: > On 10/03/17 12:27, Monty Taylor wrote: > > On 03/10/2017 10:59 AM, Clint Byrum wrote: > You may be familiar with the Kuryr project, which integrates Kubernetes > deployments made by Magnum with Neutron networkin

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Fox, Kevin M's message of 2017-03-10 23:45:06 +: > So, this is the kind of thinking I'm talking about... OpenStack today is > more then just IaaS in the tent. Trove (DBaaS), Sahara (Hadoop,Spark,etc > aaS), Zaqar (Messaging aaS) and many more services. But they seem to be >

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Fox, Kevin M's message of 2017-03-10 20:47:55 +: > Just because the market hasn't immediately shifted from IaaS to containers > doesn't mean it won't happen eventually, and that google's wrong in their > push for containers over IaaS. It took a long time (still ongoing) to move

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Joshua Harlow's message of 2017-03-10 10:09:24 -0800: > Clint Byrum wrote: > > Excerpts from Joshua Harlow's message of 2017-03-09 21:53:58 -0800: > >> Renat Akhmerov wrote: > >>>> On 10 Mar 2017, at 06:02, Zane Bitter<zbit...@redhat.com > &

Re: [openstack-dev] [tc][appcat][murano][app-catalog] The future of the App Catalog

Excerpts from Thierry Carrez's message of 2017-03-10 16:48:02 +0100: > Christopher Aedo wrote: > > On Thu, Mar 9, 2017 at 4:08 AM, Thierry Carrez > > wrote: > >> Christopher Aedo wrote: > >>> On Mon, Mar 6, 2017 at 3:26 AM, Thierry Carrez > >>>

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

Excerpts from Joshua Harlow's message of 2017-03-09 21:53:58 -0800: > Renat Akhmerov wrote: > > > >> On 10 Mar 2017, at 06:02, Zane Bitter >> > wrote: > >> > >> On 08/03/17 11:23, David Moreau Simard wrote: > >>> The App Catalog, to me, sounds sort

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

Excerpts from Thierry Carrez's message of 2017-03-10 17:04:54 +0100: > Ben Swartzlander wrote: > > On 03/09/2017 12:10 PM, Jonathan Bryce wrote: > >> Putting that aside, I appreciate your providing your input. The most > >> consistent piece of feedback we received was around scheduling and > >>

Re: [openstack-dev] [all] Small steps for Go

Excerpts from Michał Jastrzębski's message of 2017-03-09 11:23:17 -0800: > Clint, I think it's good to find initial idea to work towards to > create stuff like infrastructure (testing and such) around golang, > code guidance, standards and so on. It takes first project to create > all that stuff

Re: [openstack-dev] [all] Some information about the Forum at the Summit in Boston

Excerpts from Ben Swartzlander's message of 2017-03-09 11:23:31 -0500: > I might be the only one who has negative feelings about the PTG/Forum > split, but I suspect the foundation is suppressing negative feedback > from myself and other developers so I'll express my feelings here. If > there's

Re: [openstack-dev] [all] Small steps for Go

Excerpts from Hayes, Graham's message of 2017-03-07 14:19:02 +: > On 07/03/2017 13:22, Davanum Srinivas wrote: > > Folks, > > > > Anyone interested? https://etherpad.openstack.org/p/go-and-containers > > > > Thanks, > > Dims > > > > The first thing that is required (according to the new

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Jonathan Bryce's message of 2017-03-01 11:49:38 -0600: > > > On Feb 28, 2017, at 4:25 AM, Thierry Carrez <thie...@openstack.org> wrote: > > > > Clint Byrum wrote: > >>>> So, I'll ask more generally: do you believe that the single opensta

Re: [openstack-dev] [barbican] Rolling upgrade in Barbican project

Excerpts from na...@vn.fujitsu.com's message of 2017-02-28 09:52:13 +: > Hi everyone, > > Recently, there are many emails to discuss a topic that "Why are projects > trying to avoid Barbican, still?" [0]. That is very an interesting topic. Now > I would like to make a new topic related to

[openstack-dev] [architecture] Pike PTG Architecture Working Group Recap

The Architecture Working Group was lucky enough to have a room allocated to us for all day Tuesday of the Pike PTG. We made good use of it to do what we are here to do: Facilitate the development of a shared architecture amongst OpenStack project teams. We had an etherpad[1] that is a bit of a

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Doug Hellmann's message of 2017-02-27 15:43:12 -0500: > Excerpts from Clint Byrum's message of 2017-02-27 09:35:21 -0800: > > Excerpts from Dean Troyer's message of 2017-02-27 09:32:09 -0600: > > > On Mon, Feb 27, 2017 at 3:31 AM, Clint Byrum <cl

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Matthew Treinish's message of 2017-02-27 13:03:56 -0500: > On Mon, Feb 27, 2017 at 06:18:10PM +0100, Thierry Carrez wrote: > > > Dean Troyer wrote: > > >> On Mon, Feb 27, 2017 at 3:31 AM, Clint Byrum <cl...@fewbar.com> wrote: > > >> This

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Dean Troyer's message of 2017-02-27 09:32:09 -0600: > On Mon, Feb 27, 2017 at 3:31 AM, Clint Byrum <cl...@fewbar.com> wrote: > > This is not for users who only want to see some projects. That is a well > > understood space and the mailman

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Luigi Toscano's message of 2017-02-27 03:02:45 -0500: > > - Original Message - > > Excerpts from Shamail Tahir's message of 2017-02-27 00:44:44 -0500: > > > Hi Clint, > > > > > > On Mon, Feb 27, 2017 at 12:25 AM, Clint Byrum <cl...@

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Shamail Tahir's message of 2017-02-27 00:44:44 -0500: > Hi Clint, > > On Mon, Feb 27, 2017 at 12:25 AM, Clint Byrum <cl...@fewbar.com> wrote: > > > Excerpts from Matt Riedemann's message of 2017-02-26 19:48:50 -0600: > > > On 2/26/2017 6:52 PM,

Re: [openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

Excerpts from Matt Riedemann's message of 2017-02-26 19:48:50 -0600: > On 2/26/2017 6:52 PM, Clint Byrum wrote: > > During some productive discussions in the Stewardship Working Group PTG > > room, the subject of the mailing list came up. The usual questions > > around whe

[openstack-dev] [all][swg] per-project "Business only" moderated mailing lists

During some productive discussions in the Stewardship Working Group PTG room, the subject of the mailing list came up. The usual questions around whether or not we should have per-project lists came up and the reasons we don't were re-affirmed. To recap those reasons: * Cross posting is the

Re: [openstack-dev] [keystone]PKI token VS Fernet token

Excerpts from Lance Bragstad's message of 2017-02-25 13:07:58 -0600: > Since both token formats rebuild the authorization context at validation > time, we can remove some revocation events that are no longer needed. This > means we won't be storing as many revocation events on role removal from >

Re: [openstack-dev] [keystone]PKI token VS Fernet token

Excerpts from joehuang's message of 2017-02-25 04:09:45 +: > Hello, Matt, > > Thank you for your reply, just as what you mentioned, for the slow changed > data, aync. replication should work. My concerns is that the impact of > replication delay, for example (though it's quite low chance to

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-21 00:50:35 +0100: > On 02/19/2017 08:43 PM, Clint Byrum wrote: > > Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100: > >> On 02/18/2017 07:59 AM, Clint Byrum wrote: > >>> Indeed, DPMT uses all the

Re: [openstack-dev] [architecture][nova][neutron][cinder][ceilometer][ironic] PTG stuff -- Arch-WG nova-compute-api fact-gathering session Tuesday 10:30 Macon

Excerpts from Dmitry Tantsur's message of 2017-02-18 18:54:59 +0100: > 2017-02-17 19:16 GMT+01:00 Clint Byrum <cl...@fewbar.com>: > > > Hello, I'm looking forward to seeing many of you next week in Atlanta. > > We're going to be working on Arch-WG topics all day Tuesda

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Jay Pipes's message of 2017-02-20 10:00:06 -0500: > On 02/17/2017 02:28 PM, Artom Lifshitz wrote: > > Early on in the inception of device role tagging, it was decided that > > it's acceptable that the device metadata on the config drive lags > > behind the metadata API, as long as it

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

Excerpts from Artom Lifshitz's message of 2017-02-20 08:23:09 -0500: > Config drive over read-only NFS anyone? > > > A shared filesystem so that both Nova and the guest can do IO on it at the > same time is indeed the proper way to solve this. But I'm afraid of the > ramifications in terms of

Re: [openstack-dev] The end of OpenStack packages in Debian?

Excerpts from Thomas Goirand's message of 2017-02-19 00:58:01 +0100: > On 02/18/2017 07:59 AM, Clint Byrum wrote: > > Indeed, DPMT uses all the worst choices for maintaining most of the > > python module packages in Debian. However, something will need to be > > do

  1   2   3   4   5   6   7   8   9   10   >