Devops has always been about more than collaboration between developers and web operations and it’s great to see articles like the first one in this issue, in this case from deep within the network engineering community talking about the need to learn programming. At devops flavoured events talk often turns to how to get more people from networking or quality assurance or security backgrounds to join the community, it feels like that might be starting to happen.
Devops Weekly is sponsored by Brightbox Cloud - launch cloud servers in multiple UK datacentres in seconds…
A fantastic article, from a network engineers point of view on a network engineer site, about why network folk should learn programming. It doesn’t mention devops once. I still think one of the areas we’ll see interesting tools and conversations about in the next year or so will be networking.
It’s very common for web applications to be moving towards a continuous release process, rather than say releasing a numbered version every 6 months. This blog post talks about this in terms of openstack (and is relevant to other infrastructure software too I’d wager). Would you happily update your IaaS software every day?
Interesting summary of the recent Heroku performance issues. This is mainly interesting because it raises issues about who owns what when running under a PaaS, and more importantly how you instrument an application when you don’t own much of the stack.
As more and more folks implement deployment pipelines we’re discovering useful patterns. This post covers why just moving artefacts around between named repositories might not be the best approach, and why metadata is important too.
Assume you didn’t already have any preconceptions about PHP and you heard about a cool new language built for the web. PHP The Right Way is a actually quite impressive looking site aiming to improve the state of PHP documentation, and starts with things like xdebug, dependency management tools, built in web servers, vagrant and more.
Workshare in London are looking for a DevOps engineer to join their team. This will be their first full-time DevOps hire in an established and profitable business, with fresh VC investment and led by a CEO who did 3 IPOs before. The DevOps will be tasked with building out brand new infrastructure to support a PaaS product offering. You will be heavily involved in defining architecture, tooling and process for the organisation.
dotScale is an affordable upcoming conference in Paris, on June 7th with workshops on the June 8th. Som interesting folks down to speak, on everything from Hadoop and ElasticSearch to dotCloud and Heroku. The organisers have nicely offered a 15% discount to devops weekly readers too.
I mentioned the vagrant-omnibus tool last week for Chef and immediately wanted to the same thing for Puppet. The first step is a single installer, and puppet-omnibus is just that. It uses the tools from Opscode to make a single monolithic package.
Internal applications often have either no or bad authentication and authorisation schemes. Google Auth Proxy is a reverse proxy which authenticates all requests via Google OAuth provider. Fast and simple, at least if you’re already using an OAuth provider like Google Apps.
More Vagrant providers, this one covers the Joyent cloud. Nicely it also comes with a sample Vagrantfile in a hello world style project (including a Chef bootstrap trick) which should get you started quickly.
Chronos is an interesting cron replacement, with a distributed, fault tolerant model based on Mesos. You can specify jobs in iso8601, interact with a web interface or API and deal with failures gracefully. If you’re running a full Hadoop stack the dependencies shouldn’t be too scary.