Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

On Thu, Sep 20, 2018 at 2:48 PM Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +: > > tl;dr: The openstack, openstack-dev, openstack-sigs and > > openstack-operators mailing lists (to which this is being sent) will > > be replaced by a new

[openstack-dev] [chef] fog-openstack 0.3

Ohai! fog-openstack 0.3 has been released upstream, but it also seems to be a breaking release by way of naming convention. At this time, it is advised to pin your client cookbook at '<0.3.0'. Changes to compensate for this change are being delivered to git and Supermarket, but the most

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

further the intent of openness in the community. I directly see the benefit in having a means to reach the greater community (hi! o/) but I do not directly see the correlation in defining a given social platform as being The Platform for

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On Mon, Sep 17, 2018 at 6:58 AM Sylvain Bauza wrote: > > > > Le lun. 17 sept. 2018 à 15:32, Jeremy Stanley a écrit : >> >> On 2018-09-16 14:14:41 +0200 (+0200), Jean-philippe Evrard wrote: >> [...] >> > - What is the problem joining Wechat will solve (keeping in mind the >> > language barrier)?

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On Fri, Sep 14, 2018 at 5:25 PM Rico Lin wrote: >> >> >> For the candidates who are running for tc seats, please reply to this email >> to indicate if you are open to use certain social media app in certain >> region (like Wechat in China, Line in Japan, etc.), in order to reach out to >> the

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

On Thu, Sep 13, 2018 at 9:14 AM, Fox, Kevin M wrote: > How about stated this way, > Its the tc's responsibility to get it done. Either by delegating the > activity, or by doing it themselves. But either way, it needs to get done. > Its a ball that has been dropped too much in OpenStacks

Re: [openstack-dev] [election][tc] Opinion about 'PTL' tooling

have ramifications immediately noticed. As distributed as things exist today, reducing the conversation to a few methods or people can damage intent, without humans talking to humans in a more direct manner. Best, Samuel Cassiba (scas) __

Re: [openstack-dev] [election] [tc] TC candidacy

On Fri, Sep 7, 2018 at 8:55 AM, Samuel Cassiba wrote: > On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: >> On 9/5/2018 2:49 PM, Samuel Cassiba wrote: >>> >>> Though my hands-on experience goes back several releases, I still view >>> things from the ou

Re: [openstack-dev] [election] [tc] TC candidacy

On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: > On 9/5/2018 2:49 PM, Samuel Cassiba wrote: >> >> Though my hands-on experience goes back several releases, I still view >> things from the outside-looking-in perspective. Having the outsider >> lens is cruci

[openstack-dev] [election] [tc] TC candidacy

in the overall conversations that drive so much of our daily lives. At the end of the day, we're all just groups of people trying to do our jobs. I view this as an opportunity to give back to a community that has given me so much. Thank you for your attention and consideration, Samuel Cassiba (scas) [0] https

[openstack-dev] [chef] State of the Kitchen: 7th Edition

hours, remove the steak from the water bath and pat very dry with paper towels. 6. Heat oil in a medium cast iron skillet over high heat until it shimmers. 7. Add steak and sear until well-browned, about 30 seconds per side. 8. Let rest for 5 minutes. 9. Enjoy. Your humble line cook, Samuel

Re: [openstack-dev] [chef] fog-openstack 0.2.0 breakage

On Fri, Aug 31, 2018 at 8:59 AM, Samuel Cassiba wrote: > Ohai! > > fog-openstack 0.2.0 was recently released, which had less than optimal > effects on Chef OpenStack due to the client cookbook's lack of version > pinning on the gem. > Currently, the client cookbook is pinned to

[openstack-dev] [chef] Retiring openstack/openstack-chef-repo

nger tests cleanly due to the detritus of time, so it will remain in its current state. The retirement festivities can be found at https://review.openstack.org/#/q/topic:retire-openstack-chef-repo If you have any questions or concerns, please don't hesitate to reach out. Best, Samuel Cas

[openstack-dev] [chef] fog-openstack 0.2.0 breakage

Ohai! fog-openstack 0.2.0 was recently released, which had less than optimal effects on Chef OpenStack due to the client cookbook's lack of version pinning on the gem. The crucial change is that fog-openstack itself now determines Identity API versions internally, in preparation for a

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

On Thu, Aug 30, 2018 at 4:24 PM, Doug Hellmann wrote: > Below is the list of project teams that have not yet started migrating > their zuul configuration. If you're ready to go, please respond to this > email to let us know so we can start proposing patches. > > Doug > > | adjutant| 3

[openstack-dev] [chef] State of the Kitchen: 6th Edition

stard 6. Serve with dippin' sause, or use it as drownin' sause 7. Enjoy Your humble line cook, Samuel Cassiba (scas) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.opensta

Re: [openstack-dev] [all] Ongoing spam in Freenode IRC channels

On Wed, Aug 1, 2018 at 5:21 AM, Andrey Kurilin wrote: > I can make an assumption that for marketing reasons, Slack Inc can propose > extended Free plan. > But anyway, even with default one the only thing which can limit us is > `10,000 searchable messages` which is bigger than 0 (freenode doesn't

[openstack-dev] [chef] PTL candidacy for Stein

Howdy! I am submitting my name to continue as PTL for Chef OpenStack. If you don't know me, I am scas on Freenode. I work for Workday, where I am an active operator and upstream developer. I have contributed to OpenStack since 2014, and joined the Chef core team in early 2015. Since then, I have

[openstack-dev] [chef] State of the Kitchen: 5th Edition

starch or flour if you're not super carb-conscious. Hit it with the immersion blender. 7. Return shredded meat to what could be misconstrued as gravy. Salt to taste and dig in. It gets better if you leave it overnight in the fridge to allow the flavors to redistribute. Your humb

Re: [openstack-dev] [all] [release] How to handle "stable" deliverables releases

On Mon, Jun 11, 2018 at 2:53 AM, Thierry Carrez wrote: > > 2bis/ Like 2, but only create the branch when needed > > Same as the previous one, except that rather than proactively create the > stable branch around release time, we'd wait until the branch is actually > needed to create it. > This

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

On Tue, May 29, 2018 at 4:26 PM, Ian Wells wrote: > On 29 May 2018 at 14:53, Jeremy Stanley wrote: > >> On 2018-05-29 15:25:01 -0500 (-0500), Jay S Bryant wrote: >> [...] >> > Maybe it would be different now that I am a Core/PTL but in the past I >> had >> > been warned to be careful as it

Re: [openstack-dev] [tc] Organizational diversity tag

of throughput and number of contributors is one thing, but the outcome of the measure needs to feed back into better maintainership for the overall health of OpenStack as a collection of open source projects. Some of the destined 'low-activity' projects would do quite well with an extra couple of part-timers i

[openstack-dev] [chef] State of the Kitchen: 4th Edition

he cream cheese in the microwave, add the cream and mix. Pour mixture over the casserole. 7. Mix ingredients until incorporated. Overmixing will give a more pate-like texture. 8. Bake @ 350F / 176C for 40 minutes. Your humble line cook, Samue

[openstack-dev] [chef] State of the Kitchen - 3rd Edition

food processor. Blend until desired consistency, or until you do not see pieces of jalapeno. Your humble line cook, Samuel Cassiba (scas) __ OpenStack Development Mailing List (not for usage questions) Unsubscrib

[openstack-dev] [chef] State of the Kitchen - 2nd Edition

th a fork. Your humble cook, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [chef] Pike cookbooks released

on Chef 13, with Chef 12 now being unsupported in master. If you need to use an older release of OpenStack with Chef 13, this will give you a blueprint for what needs to be backported. Prost! Your humble cook, Samuel Cassiba (sc` / scas

[openstack-dev] [chef] State of the Kitchen - 1st Edition

our cream to tame the heat. Apply baby wipes when appropriate. Gets hotter overnight. Your humble cook, Samuel Cassiba (sc` / scas) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstac

[openstack-dev] [chef][ptl] PTL candidacy for Rocky

elsewhere for an upstream. Thank you for reading. Delightfully, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.ope

[openstack-dev] [chef] Heads up - Chef 13 is incoming

is always open. Just keep in mind that the team is very distributed, so park a client for a while. -- Best, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] Upstream LTS Releases

mselves, and some are, but it's pretty damned daunting from the outside. The new contributors who want to contribute but don't see the way in, probably because we haven't said mellon, are left scratching their heads and eventually deem OpenStack as Not Ready. It

Re: [openstack-dev] [Openstack-operators] Upstream LTS Releases

On Fri, Nov 10, 2017 at 2:51 PM, John Dickinson wrote: > What I heard from ops in the room is that they want (to start) one release a > year who's branch isn't deleted after a year. What if that's exactly what we > did? I propose that OpenStack only do one release a year instead of

Re: [openstack-dev] Upstream LTS Releases

, as well, due to flipped solar flares and good old bitrot. > > Erik and some other folks from the session are going to need to > write up some policy and process change proposals so we can hash > out all of the details and

Re: [openstack-dev] Upstream LTS Releases

w that the proposition exists about making a Stable Release liaison derived from existing cores, I can't help but get the impression that, for active-but-quiet projects, it'll be yet another PTL responsibility to keep up with, in addition to the rigors that already come with the role

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

k.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best, Samuel Cassiba signature.

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

ent > tool to what I use." I would hope not! :) I don't mean having a tool means > the tool is required. Only that a user-friendly deployment tool is available. > Isn't that better than giving them nothing at all? > > //adam > > > Adam Lawson > > Princip

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

> On Sep 25, 2017, at 16:52, Clint Byrum wrote: > > 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

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

r lunch, but I encourage people at 13:30 >> > local time to meet >> > at the simplification room level b in the big thompson room. Thank you! >> > >> > — >> > Mike Perez >> >>

[openstack-dev] [chef] stable/ocata has been released

been beneficial. For any issues, or just to say hi, feel free to drop by #openstack-chef and idle. Onward to Pike! -- Best, Samuel Cassiba __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

Re: [openstack-dev] [chef] Proposing Lance Albertson (Ramareth) for openstack-chef-core

On Tue, Aug 8, 2017 at 7:24 PM, Samuel Cassiba <s...@cassiba.com> wrote: > Ohai! > > In openstack-chef-land, we generally don't use the ML very often, > being so few; thus, when there's an occasion to send something, it > better be worth it. > > I am proposing adding

[openstack-dev] [chef] Proposing Lance Albertson (Ramareth) for openstack-chef-core

, but the quirks of OpenStack and Python. However, we do what we can, when we can, how we can. Any feedback is welcome. If there are no reasons otherwise, Lance will be added to the core group in a few days. -- Best, Samuel Cassiba

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

b of being a PTL. We didn’t get that memo until the Big Tent was deemed too smothering. The fun part about being a PTL with effectively no team is that, when you or your counterpart isn’t actively marketing and spending more time making noise than working, pe

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

y those closer to upstream. “If it ain’t broke, don’t fix it” is still a strong force to contend with, whether we like it or not. Providing smooth, clear paths to a production-grade open cloud should be the aim, not what the definition of is, is, even if that is what comes naturally to groups of highly skilled,

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

or; and now those downstream Fuel users are out in the cold without an obvious path forward, save for “lol deal with it". From my point of view, we mustn’t lose sight of that just because a given project doesn’t have enough throughput, or enough developers, just because a vendor moves on to something newer and shinier. &g

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Tony, I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as well. Thanks! -- Best, Samuel Cassiba signature.asc Description: Message signed with OpenPGP __ OpenStack Development Mailing List

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

> On Feb 15, 2017, at 08:49, Alex Schultz <aschu...@redhat.com> wrote: > > On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba <s...@cassiba.com> wrote: >>> On Feb 15, 2017, at 02:07, Thierry Carrez <thie...@openstack.org> wrote: >>> >>> Samu

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

> On Feb 15, 2017, at 02:07, Thierry Carrez <thie...@openstack.org> 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

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

The HTML version is here: https://s.cassiba.com/2017/02/14/making-the-kitchen-great-again-a-retrospective-on-openstack-chef This was influenced by Graham Hayes' State of the Project for

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

> > On Dec 19, 2016, at 14:31, Tony Breeds <t...@bakeyournoodle.com> wrote: > > On Mon, Dec 19, 2016 at 09:18:20AM -0800, Samuel Cassiba wrote: > >> The Chef OpenStack cookbooks team is way late to the party. The cookbooks >> (openstack/cookbook-openstack

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev The Chef OpenStack cookbooks team is way late to the party. The cookbooks (openstack/cookbook-openstack-*, openstack/opensta

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

> On Dec 13, 2016, at 19:43, Ed Leafe wrote: > > On Dec 12, 2016, at 10:30 PM, Steven Dake (stdake) wrote: > >> The issue raised is they violate the 4 opens. > > Not necessarily. If you have regular planning meetings and discussions in an > open manner as

[openstack-dev] [chef] draft logo & sneak peek

. Since neither myself nor the other cores will be at the PTG, we’ll have to work out some way to get the final product distributed if interested. Have a great Summit! Best, Samuel Cassiba Project Team Lead, OpenStack Chef > Begin forwarded message: > > From: Heidi Joy Trethew

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

On Tue, Oct 11, 2016 at 11:32 AM, Alex Schultz wrote: > On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold wrote: >> Hi, >> >> On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote: >>> On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold

Re: [openstack-dev] [chef] Adding calbers to openstack-chef-core

ood, +1 from me. > > Cheers, > Jan > >> On 05 Oct 2016, at 05:44, Samuel Cassiba <s...@cassiba.com> wrote: >> >> Ohai Chefs! >> >> I would like to nominate Christoph Albers (irc: calbers) for >> openstack-chef-core. >> >> Christoph has

[openstack-dev] [chef] Adding calbers to openstack-chef-core

Ohai Chefs! I would like to nominate Christoph Albers (irc: calbers) for openstack-chef-core. Christoph has consistently provided great quality reviews over the Newton cycle. He has been instrumental in getting the cookbooks up to speed with Identity v3 and openstackclient. During Mitaka, his

[openstack-dev] [chef] Chef PTL candidacy

deploying OpenStack and hacking on cookbooks. I look forward to continuing to steer the OpenStack Chef cookbooks as well as collaborating with other projects within the greater OpenStack project. Yours, Samuel Cassiba [0] https://review.openstack.org/369027

Re: [openstack-dev] [all] Newton Summit: cross-project session for deployment tools projects

On Thu, Mar 31, 2016 at 2:40 PM, Emilien Macchi wrote: > Hi, > > OpenStack big tent has different projects for deployments: Puppet, > Chef, Ansible, Kolla, TripleO, (...) but we still have some topics in > common. > I propose we use the Cross-project day to meet and talk

Re: [openstack-dev] [chef] ec2-api cookbook

On Thu, Mar 24, 2016 at 11:25 AM, Ronald Bradford <m...@ronaldbradford.com> wrote: > Samuel, > > Could you detail when your IRC meeting is, [1] indicates it's on Tuesdays. > > [1] https://wiki.openstack.org/wiki/Meetings/EC2API > > Regards > > Ronald > >

Re: [openstack-dev] [chef] ec2-api cookbook

On Thu, Mar 24, 2016 at 3:33 AM, Anastasia Kravets wrote: > Hi, team! > > If you remember, we've created a cookbook for ec2-api service. After last > discussion I’ve refactored it, have added specs. > The final version is located on cloudscaling github: >

[openstack-dev] [chef] PTL Candidacy

and maintaining strong lines of communication. I would greatly appreciate your support for PTL, if you'll have me, and I'm looking forward to growing the Chef OpenStack team. The official elections review is here: https://review.openstack.org/#/c/291967/ Samuel Cassiba (sc

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

You can also use Chef for either a small-scale or production level deployment. Check out https://wiki.openstack.org/wiki/Chef/GettingStarted for a bit more context, or if you just want to jump in head-first https://github.com/openstack/openstack-chef-repo/blob/master/README.md On Thu, Mar 10,

Re: [openstack-dev] [Rdo-list] [TripleO] Should we rename "RDO Manager" to "TripleO" ?

+1 for this. Having already navigated the depths of RDO, this eliminates a big point of confusion. On Wed, Feb 17, 2016 at 8:27 AM, David Moreau Simard wrote: > Greetings, > > (Note: cross-posted between rdo-list and openstack-dev to reach a > larger audience) > > Today,

Re: [openstack-dev] [chef] deprecation and removal of old branches

I'm +1 on this idea. Looking at other OpenStack projects (Nova, Neutron, etc.) on GitHub, they only have stable/liberty and stable/kilo, with anything older dropped. We're already following this support model, so I think the cleanup should happen, that way there isn't any ambiguity on which

Re: [openstack-dev] [chef] Feedback to move IRC Monday meeting and time.

Hi, On Wed, May 6, 2015 at 10:11 AM, JJ Asghar jasg...@chef.io wrote: Hey everyone! As we move forward with our big tent move[1] Jan suggested we move from our traditional IRC meeting in our main channel #openstack-chef to one of the official OpenStack meeting channels[2]. +1 This has