Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 11:24 AM, Joshua Harlow wrote: > Alex Schultz wrote: > >> On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: >> >>> On Feb 16, 2017, at 10:07 AM, Doug Hellmann >>> wrote: >>> >>> When we signed off on the Big Tent changes we said competition between projects was desira

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Ed Leafe wrote: > On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > >> When we signed off on the Big Tent changes we said competition >> between projects was desirable, and that deployers and contributors >> would make choices based on the work being done in those competing >> projects. Basica

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

ctive. Tim From: Joshua Harlow [harlo...@fastmail.com<mailto:harlo...@fastmail.com>] Sent: Thursday, February 16, 2017 10:24 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenSt

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

ua Harlow [harlo...@fastmail.com] > Sent: Thursday, February 16, 2017 10:24 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [chef] Making the Kitchen Great Again: A > Retrospective on OpenStack & Chef > > Alex Schultz wrote: &g

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

lto:harlo...@fastmail.com>] Sent: Thursday, February 16, 2017 10:24 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef Alex Schultz wrote: On Thu, Feb 16, 2017 at 9:12 AM, E

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Le 16/02/2017 18:42, Alex Schultz a écrit : > On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: >> On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: >> >>> When we signed off on the Big Tent changes we said competition >>> between projects was desirable, and that deployers and contributors >>>

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef Alex Schultz wrote: > On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: >> On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: >> >

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Alex Schultz wrote: On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: When we signed off on the Big Tent changes we said competition between projects was desirable, and that deployers and contributors would make choices based on the work bein

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: > On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > >> When we signed off on the Big Tent changes we said competition >> between projects was desirable, and that deployers and contributors >> would make choices based on the work being done in th

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

not for usage questions) > > Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A > Retrospective on OpenStack & Chef > > > On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > > > > > When we signed off on the Big Tent changes we said competition

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On 02/16/2017 10:23 AM, Ed Leafe wrote: > On Feb 16, 2017, at 10:12 AM, Ed Leafe wrote: > >> We got much better at adding new things to OpenStack. We need to get better >> at letting go of old things. > > On re-reading that, it doesn’t sound like what I intended. By “old” I mean > things that

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Feb 16, 2017, at 10:12 AM, Ed Leafe wrote: > We got much better at adding new things to OpenStack. We need to get better > at letting go of old things. On re-reading that, it doesn’t sound like what I intended. By “old” I mean things that no longer have enough active support to keep them cu

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

-Original Message- From: Ed Leafe Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 10:13:51 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > When we signed off on the Big Tent changes we said competition > between projects was desirable, and that deployers and contributors > would make choices based on the work being done in those competing > projects. Basically, the market would de

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Excerpts from Dean Troyer's message of 2017-02-16 08:25:42 -0600: > On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: > > It seems like a lot of people view "developing OpenStack" as more > > attractive than "making it easy to deploy OpenStack" (via the > > deployment tools in the tent). Doing

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

-Original Message- From: Dean Troyer Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 08:27:12 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On 02/16/2017 08:25 AM, Dean Troyer wrote: > On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: >> It seems like a lot of people view "developing OpenStack" as more >> attractive than "making it easy to deploy OpenStack" (via the >> deployment tools in the tent). Doing both is really something p

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 7:54 AM, Ian Cordasco wrote: > It seems like a lot of people view "developing OpenStack" as more > attractive than "making it easy to deploy OpenStack" (via the > deployment tools in the tent). Doing both is really something project > teams should do, but I don't think shov

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

-Original Message- From: Doug Hellmann Reply: OpenStack Development Mailing List (not for usage questions) Date: February 16, 2017 at 07:06:25 To: openstack-dev Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef > Excerp

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Excerpts from Sylvain Bauza's message of 2017-02-16 10:55:14 +0100: > > Le 16/02/2017 10:17, Neil Jerram a écrit : > > On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow > > wrote: > > > > Radical idea, have each project (not libraries) contain a dockerfile > > t

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Le 16/02/2017 10:17, Neil Jerram a écrit : > On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow > wrote: > > Radical idea, have each project (not libraries) contain a dockerfile > that builds the project into a deployable unit (or multiple dockerfiles > for

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow wrote: > Radical idea, have each project (not libraries) contain a dockerfile > that builds the project into a deployable unit (or multiple dockerfiles > for projects with multiple components) and then it becomes the projects > responsibility for ensu

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

For the cookbooks, every core and non-core project that is supported has to be tracked. In addition to that, each platform that is supported must be tracked, for quirks and idiosyncrasies, because they always have them. Then, there are the cross-project teams that do the packaging, as well as the

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

> On Feb 15, 2017, at 08:49, Alex Schultz wrote: > > On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba wrote: >>> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: >>> >>> Samuel Cassiba wrote: [...] *TL;DR* if you don't want to keep going - OpenStack-Chef is not in a good place a

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba wrote: > >> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: >> >> Samuel Cassiba wrote: >>> [...] >>> *TL;DR* if you don't want to keep going - >>> OpenStack-Chef is not in a good place and is not sustainable. >>> [...] >> >> Thanks for sharing, Sa

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: > > Samuel Cassiba wrote: >> [...] >> *TL;DR* if you don't want to keep going - >> OpenStack-Chef is not in a good place and is not sustainable. >> [...] > > Thanks for sharing, Sam. > Thanks for taking the time to read and respond. This was

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

Samuel Cassiba wrote: > [...] > *TL;DR* if you don't want to keep going - > OpenStack-Chef is not in a good place and is not sustainable. > [...] Thanks for sharing, Sam. I think that part of the reasons for the situation is that we grew the number of options for deploying OpenStack. We originall