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

2017-02-17 Thread Steven Dake
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

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

2017-02-17 Thread Thierry Carrez
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

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

2017-02-16 Thread Fox, Kevin M
attractive. 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 Retr

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

2017-02-16 Thread Adam Heczko
> From: Joshua 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 > &

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

2017-02-16 Thread Tim Bell
arlow [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 OpenStack & Chef Alex Schultz wrote: On Thu

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

2017-02-16 Thread Sylvain Bauza
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,

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

2017-02-16 Thread Fox, Kevin M
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<e...@leafe.com> wrote: >> On Feb 16, 2017, at 10:07

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

2017-02-16 Thread Joshua Harlow
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

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

2017-02-16 Thread Alex Schultz
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

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

2017-02-16 Thread Doug Hellmann
at 10:13:51 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject:  Re: [openstack-dev] [chef] Making the Kitchen Great Again: A > Retrospective on OpenStack & Chef > > > On Feb 16, 2017, at 10:07 AM, Doug He

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

2017-02-16 Thread Monty Taylor
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

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

2017-02-16 Thread Ed Leafe
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

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

2017-02-16 Thread Ian Cordasco
s.openstack.org> 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 > > between pr

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

2017-02-16 Thread Ed Leafe
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.

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

2017-02-16 Thread Doug Hellmann
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

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

2017-02-16 Thread Ian Cordasco
t;openstack-dev@lists.openstack.org> Subject:  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

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

2017-02-16 Thread Monty Taylor
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

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

2017-02-16 Thread Dean Troyer
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

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

2017-02-16 Thread Ian Cordasco
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 >

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

2017-02-16 Thread Doug Hellmann
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)

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

2017-02-16 Thread Sylvain Bauza
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

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

2017-02-16 Thread Neil Jerram
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 >

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

2017-02-15 Thread Joshua Harlow
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

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

2017-02-15 Thread Samuel Cassiba
> 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

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

2017-02-15 Thread Alex Schultz
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

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

2017-02-15 Thread Samuel Cassiba
> 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

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

2017-02-15 Thread Thierry Carrez
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