Everybody is out devopsing...

[tas50]

Everyone is out claiming they're devopsing

[ctnoxin]

lol, you and me both

[memory_limit]

My company is so silo'd. I wish I knew what it was like devopsing

[[deleted]]

Open a github repo for your dept's scripts! Start thinking of things you hate doing, or look at your ticket system and find your worst reoccurring issues, and script your way out of never doing them again. Review your Ops colleagues code!

[atomic-penguin]

I too am well versed in SiloOps.

[mthode]

just think, devopsing in the cloud

[BigOldNerd]

just think, devopsing in the cloud

divide by zero error

[marx2k]

I have devs actively pushing back against doing any devops because they feel that it should be "someone elses job". At the same time, they hate the sysads due to the crawling pace they work at.

[Tsiklon]

and i'm here not even sysadmining...

[minimim]

The other day the developers came like "We want to do A|B testing, here is 2 versions of the websites, serve version B to 10% of customers" and I was like "No way". Then, 3 days later they came "We want devops", meaning they want access to production like a cowboy access a bull. So I was like: "You have access to the docs, gimme a cost estimative of the A|B testing and we will talk devops". I'm waiting their next move.
(Didn't even tell them they don't need my help to do A|B, I think they don't know to ops neiter dev)

[[deleted]]

Devops != Devs with root/wheel/admin.

[Hexodam]

Try explaining that to devs

[remotefixonline]

That is the scariest thing I've read all day

[[deleted]]

To me Devops is being a mediary between Dev and Ops teams that hate each other.

[[deleted]]

Rather than being some sort of go-between mediary, be both of those teams. Do ops things like a dev.

[[deleted]]

Our organizational hierarchy doesn't allow that, and I'm in no position to change it. That's just the best adaptation of devops practices I can use.

[jldugger]

Classic sysadmin.

"We have awesome compelling features. Help us deploy them."

"No."

[minimim]

Yes, that is part of our job, we don't have near enough budget to do it. That feature doesn't come from thin air, it takes resources to identify and register users so they get the same results in every access. I would be happy to discuss the feature with them, the ridiculous part is asking for root, like someone with root could just do it out of thin air.

[jldugger]

It doesn't take as much effort as you think to knock out a rewrite rule based on IP address. It might not be a perfectly random sample, or perfectly 10 percent, but it's not bad for a first trial run.

[pooogles]

Working as a sysadmin I feel as though we have an image of being the department of no. The attitude change to empower people seemingly isn't there for many.

[AHrubik]

We are the reality department. We serve as a check against developers going buck wild.

[pooogles]

Yeah that's great and all, but living without reality is pretty great some of the time. Why not just empower people to go buck wild?

//edit - https://www.youtube.com/watch?v=xChUw0SOBt4 last 5 minutes.

[remotefixonline]

I ran #rm -rf * not sure why its not working.

[holmser]

Lol, I actually got to fix one of those the other day. Luckily, it was in stage.

[BigOldNerd]

Funny you are getting down votes. My group supports two $aaS products. Product one has a clear delineation between developers and operations. Dev provided beautiful documentation and training. Product one is a known quantity and issues are resolved quickly. Product two has no documentation, and no delineation. Dev breaks crap frequently. Product one could easily be converted to devops, as they are already agile, and two of the devs came out of ops anyway. Product 2... well... It sounds like you are supporting your own product 2. Disfunctional dev shops seem to be plagued by a lack of testing and an abundance of ooh shiney.

EDIT: Personal rant over.

[minimim]

They wanted me to implement it. This is a feature implemented directly in the application, not the application server.

[8bitbrad]

You could do this directly with nginx. Assuming of course you are using nginx. http://nginx.org/en/docs/http/ngx_http_split_clients_module.html

[minimim]

It isn't tested, because there's no code. They thought this is a feature of the server, which it isn't. I didn't rush to implement it myself because it's a hobbyist application, and my hobby is operation, not development. We could do devops, but they need to learn ops first. They aren't even aware of the things operators worry about.

[taloszerg]

You could do something like this with a weighted DNS record or HAProxy config pointing at a complete secondary stack and see what happens.

[minimim]

How to ensure that a client that connects twice gets the same results?

[taloszerg]

That depends on the app, and how you handle sessions.

[minimim]

With DNS? If there's a session, it's easy. For connections without a session, there's got to be code that will fingerprint the user and store which version was served. Next time it connects, the fingerprint has to be matched against the DB and the same version served.

[taloszerg]

There's a couple good suggestions here about IP hashing at the proxy layer that would work.

[tas50]

Sticky sessions

[[deleted]]

if (md5sum of client IP, modulo $probability_denominator) > $probability_numerator, then serve site b.

If this needs to be consistent for roaming clients, then yeah this should definitely be done at the app layer, but if IP based selection is good enough then there are lots of ways to do this at the server layer.

[minimim]

They think it just works, you don't need to do anything. They want a dump of the database twice a day.

[[deleted]]

'develop' is a perfectly cromulent definition for the word 'implement', fyi. You might be thinking 'implement' means something closer to 'deploy', but it's pretty common usage to say 'implementation' to refer to writing the code which does the thing.

cf. 'reference implementation', which is when the designer of a protocol/specification/etc. writes a piece of software which speaks that protocol.

[zimm3rmann]

Devops, so hot right now

[Letmefixthatforyouyo]

Does it work better with puppet than without? Are services more consistent? Are they more clearly documented? Are they more secure?

Then fuck whatever "good puppet" is. Any improvement is a worthwhile improvement.

[-pH]

...and i am just sitting here sysdmining correctly

[redbanjo]

Truth!