News for hackers. Stuff that matters.
Re:Configuration (mis)management or why I hate puppet, ansib... by Spooky23 on Friday August 05, 2016 @05:52PM (#12235973)
This summarizes the post:

> Why the fuck are build/ops folks making decisions about how the application should be deployed and configured?

The answer is really easy -- the build/ops team is configuring, deploying and running the application.

Config tools aren't perfect, but they are better than the old school manual configuration or letting individual developers cook up special snowflakes to do things the "right". Way.

You should be using as close to one configuration management tool as possible, and as a developer, you should learn how that tool works.

Re:Configuration (mis)management or why I hate puppet, ansib... by pbrb on Friday August 05, 2016 @06:05PM (#12236028)
I would also be willing the bet that the build/ops team wrote their puppet scripts to mirror the current way that the application was configured and deployed (shittily).

To really make configuration management work, you need to need to have sane process and architecture in place. Otherwise, you're just adding a layer of abstraction with a little automation sprinkled in, to an already shitty situation.

When configuration is done correctly, with an application that has solid architecture and configuration methodologies, configuration management can be incredibly beautiful. I've seen it done well, and it can be light yrs ahead of what basic bash or powershell scripting can do for you.

Re:Configuration (mis)management or why I hate puppet, ansib... by havetocharge on Friday August 05, 2016 @06:37PM (#12236163)
This is exactly right. Ops are making decisions about how the app runs because they are the ones get paged at 4 am when it suddenly does not.
Re:Configuration (mis)management or why I hate puppet, ansib... by CaptSpify on Friday August 05, 2016 @11:04PM (#12236829)
One of the best strategies I've seen with this is: put devs on call. As soon as they are woken up at 4 am, you can see entire teams turn around their attitude on how things are run.
Re:Configuration (mis)management or why I hate puppet, ansib... by seanp2k2 on Saturday August 06, 2016 @04:44PM (#12239826)
Yep, this. PagerDuty and Slack can help. Many alerting and monitoring services now work with these. Info / debug stuff goes to slack, urgent and important stuff goes to PD. Make a quadrant of how important and how time-sensitive each alert is to respond to and make them go to the respective mechanism. Email can stand in for Slack, but people tend to ignore emails and filter them if they start getting spammed with important-but-not-their-problem things, then they'll miss the important-and-their-problem alerts later because their filter matches those too.

Suddenly, everyone is writing tests, testing locally, deploying canaries, getting demos ready 2 days ahead of time, and not deploying at 6PM on Friday.

Re:Configuration (mis)management or why I hate puppet, ansib... by CaptSpify on Saturday August 06, 2016 @07:06PM (#12240296)
Sorry, but I fail to see how

A) That is exclusive/special to things like slack or pd. Seems like a lot of tools could handle this.

B) How those tools are related to being woken up. I exclusively use email for work notifications. Chat is purely for BS and chit-chat. The last thing I would do when woken up at 3 is check chat.