NoOps appears to be the word of the month, with AppFog (amongst others) posting a “controversy as marketing” blog post titled What is NoOps anyhow?, and stating that:

NoOps doesn’t mean that operations are dead and nobody will do them

What they end with though, is perhaps the most interesting point:

Ops guys despise the term NoOps and will try to drag it through the mud.

So, as an “Ops guy”, I wondered what actually does NoOps mean, and should I despise it?

The term wasn’t invented by AppFog, I think that credit (or not) belongs to Mike Gualtier, who said:

NoOps means that application developers will never have to speak with an operations professional again. NoOps will achieve this nirvana, by using cloud infrastructure-as-a-service and platform-as-a-service to get the resources they need when they need them.

So how does NoOps achieve this “nirvana”? By using IaaS and Paas offerings from service providers it seems. Using these services is a pretty good idea anyway, and I’m looking forward to CloudFoundry or an alternative gaining widespread adoption.

But this NoOps movement seems to ignore the hard parts of what “Operations” is.

Operations is made up of many tasks, just a few of them are listed below:

You might look at this list and say that using a hosted platform removes the need for all these tasks, and for some (building a new server, upgrading software), you’re probably right.

Beyond actually carrying out these tasks, there’s the hard decisions that need to be made around them.

Do we need constant synchronous replication to a second site for this application?

What kind of downtime can we tolerate on the main database?

These kinds of hard decisions, seemingly ignored by NoOps, are in reality the hardest part of operations.

It might surprise you to find that running a backup is pretty easy. It’s deciding what to backup and when that takes the time. And to AppFog? I don’t despise the term NoOps, but I do think it’s pretty naive.

Earlier this week I had the pleasure of attending Monkigras, a developer focused conference organised by the Redmonk analysts.

Sessions

There were some excellent sessions, and it’s hard to pick out 1 or 2 as stand-out ones, but Networks of Data by Matt Buddulph was fascinating and probably the most relevant for my current project, and Jason Hoffman and Bryan Cantrill from Joyent did an excellent CTO vs VP of Engineering talk, which really brought to life some of the issues of starting up, separation of responsibilities, and how to handle growing as an organisation.

John Appleby did a pretty brave talk, given that he was speaking to mostly a bunch of web geeks, discussing the importance of enterprise systems like SAP to large companies, and how we need to link these new technologies back to the core business systems to really make a difference to how companies operate. I certainly had no idea that SAP could talk to other systems using REST, RSS, etc, and I’m sure plenty of other people didn’t know either.

Socialising

The social aspect is a big part of these kind of conferences, I got a good chance to speak to some really interesting people, both those that I follow on Twitter, and those that I’m following now. Who knew that Cap Gemini are doing Drupal development?

Conclusion

I only got to spend one day at Monkigras before catching the last train home to Manchester, but it was an absolutely excellent conference, the best I’ve ever been too. Everything from the food, the venue, the sound quality, through to the speakers were absolutely top notch.

Well done to @monkchips and the other organisers and volunteers, and thanks very much to them all – here’s to next year!

I keep finding myself wanting to make a command sleep for slightly more than 1 second, so I’ve finally written a quick C program which sleeps for a passed number of milliseconds – exactly the same as the normal Linux “sleep” command, but called “sleepms”.

If you think it might be useful to you, the code (and a 32-bit Linux executable) are on github as SleepMS.