At thetrainline.com we have been using Opscode Chef since 2012 for automation of parts of our server infrastructure, particularly the build (CI) machines. We recently had several days of intensive Chef training with Chef expert Stephen Nelson-Smith (@LordCope on Twitter) of Atalanta Systems, spread over a few weeks, in preparation for scaling up our use of Chef. Here are some details of how we structured the Chef training, and what we got out of it (and why).
We needed to replicate a Subversion artifacts repository to a remote location, but we found svnsync to be unreliable, and WanDisco’s offering was out of our budget range. We therefore developed a simple Subversion replication mechanism using post-commit hooks, message queues, and rsync; this has proven highly reliable and meets our needs well. Here is how we did it.
We in the engineering team at thetrainline.com hold an ‘open day’ every six months to share what we do with other (less ‘techy’) teams in the company. The most recent Engineering Day, in February 2013, saw members of the HR, Legal, Commercial, Marketing, Finance, and other teams (plus our Exec) attend presentations and demonstrations from members of our tech teams covering: web performance, service versioning, deployments, infrastructure automation, testing, ticket retailing, and even a workshop on ‘How to build your own website‘. Continue reading
This is a report back from Cloud Expo Europe 2013 where keynote talks from IBM, eBay, EasyJet to Morgan Stanley gave a view of how far the cloud has been adopted. In short, the cloud has ‘landed’; it is no longer hype or on the bleeding edge but is being used in organisations both large and small. For some businesses it is still early days but many are carrying out implementations to understand the tools and processes they need in order to use the cloud, as well as the organisation changes required.
At thetrainline.com we recently transformed our software release process by rebuilding our problematic test and integration environments on a private (on-premise) PaaS cloud platform. The outcome of the 8 month project was a fully automated and repeatable infrastructure and software build process that reduced the environment build time from 12 weeks down to 4.5 hours, achieving ROI within 8 months. In this post we’ll share the rationale behind why we chose private cloud over the readily available public cloud offerings, details of the components, what we’ve learnt, and how we were able to use the experience to improve our other environments and processes.