Continuing an extremely hectic month at CFEngine we are wrapping up the month by sponsoring DevOpsDays Silicon Valley which is being held at the Computer History Museum. With an impressive array of sponsors and many attendees this will hopefully be an event to remember. So what will CFEngine be doing at DevOpsDays? Well, after lots of hard work CFEngine 3.6.0 has finally been released so we’ll be showcasing that and explaining how we can help you in your DevOps journey. Mark Burgess will be presenting at the event. It’s my first time seeing Mark present at DevOpsDays as a CFEngine employee. I saw an awesome session by Mark at DevOpsDays London last year which certainly influenced my decision to join CFEngine. I hope Mark’s session leaves a lasting impression on those of you attending too! The real magic of DevOpsDays is the open space sessions, although for me the ignite sessions are also special because the content is so varied, although this time I have decided not to submit an ignite session, I need a break! I’m sure the open spaces will be enlightening as usual and I’m looking forward to Mark proposing an open space on the future of configuration management. There were many unanswered questions from his presentation of the SVDevOps meetup as well as some lively discussion making it perfect for an open space! Look forward to seeing you next week!
Big news today - I am happy to share the news that CFEngine Enterprise 3.6.0 has been released! This release is a huge step forward for our company and our customers, with a number of both new and enhanced features designed for providing a secure, scalable, and reliable foundation for IT automation. Customers and users are crucial when it comes to feedback and continuous improvement. The fact that CFEngine 3.6.0 leapfrogs the competition across many facets is testament to an innovative development team working in tandem with customers experiencing and solving real world IT issues together. With 3.6.0 we have addressed some key needs you put forth:
There is still time to register for our upcoming webinar with Forrester Research this Thursday! Please join CFEngine Co-Founder and CTO Mark Burgess and guest speaker Forrester Research, Inc. Vice President and Research Director Glenn O’Donnell for a fascinating look into the principles of continuous operations and service management - and how great service design combined with automation can empower your organization to survive and thrive in what is becoming know as “The Age of the Customer.”
Earlier this week CFEngine sponsored DockerCon. Let me start by congratulating Docker on an awesome show. The energy, and enthusiasm was contagious but more so sincere. The commitment to establishing open standards without locking in users to Docker is commendable. The CFEngine table had heavy traffic and the conversations were frequently in Depth. Attendees were not only wanting to know what value CFEngine adds on top of Docker but also what guidance on how others are using Docker. People we talked to understood the need to have a solution that could manage not only Docker containers but also their other physical and virtual infrastructure. We had very positive feedback on how we integrated Docker configurations into our CFEngine policies. For those of you who may be unaware Docker finally reached 1.0 status, which means the warning about running in production no longer applies, not that being pre 1.0 stopped the Docker community running Docker in production! Some key takeaways for me were
CFEngine are sponsoring DockerCon14. We’re excited to be able to show you how CFEngine and Docker can be used together to help manage your docker containers and make sure that you don’t go back down the path of golden images! If that isn’t enough to get your excited our very own Diego Zamboni is flying in from Mexico from the event. Stop by and have a chat with Diego about CFEngine, security or anything else. Diego will also be signing copies of Learning CFEngine 3. We look forward to seeing you there.
DevOpsDays events in Pittsburgh and Austin have both been awesome. It’s great to see the events maturing over time. While it was the first DevOpsDays event in Pittsburgh the organizers were familiar with DevOpsDays events and made sure that they built on top of other successes. The lack of “Idol worshipping” aka “we love Amazon, Etsy, Facebook, Netflix” was refreshing! We were treated to excellent sessions covering culture, PaaS, docker and other great topics. As long as you are in tech I’m certain there was plenty to interest you. The ignite sessions again were fun as always. There were some fun moments and some awkward moments! I presented my ignite session from DevOpsDays Austin on why DevOpsDays is failing horses and unicorns. Eventually I’ll track down a video of it and link to it, but it was well received. The awkward moment was that I presented after Nathan Harvey of Chef. He preached the familiar unicorn cry of “if you aren’t happy quit your job”. My ignite session has a slide that made fun of unicorns telling horses to quit their jobs and go work with unicorns because it really isn’t helpful at all. There was a great open space session on diversity in tech which could have gone on for hours. It was constructive and we all realize there is a problem. While DevOpsDays PGH wasn’t incredibly diverse it was heartening to see a significant number of women attending and presenting. In particular I’m looking forward to seeing Bridget Kromhout (@bridgetkromhout) and Cornelia Davis (@cdavisafc) present again. Awareness of CFEngine is growing, and we are getting recognition in presentations once again. People really seem pleased that we are still around and doing some awesome things. I can’t wait until DevOpsDays Silicon Valley when we can talk about some really cool stuff we have coming! June will be a very busy month for CFEngine. We’ll be at DockerCon, Velocity Santa Clara and DevOpsDays Silicon Valley.
This is a term often used today to acknowledge the extraordinary growth of the major web companies over a decade (social media, retailing, games, cloud etc) from handfuls of machines to the largest installations on the planet. The major web players today have datacenters with 10,000, 100,000 and even 1,000,000 computers serving their operations. Of course, this kind of growth is not appropriate for everyone. WebScale often goes together with quite singular or focused applications, by contrast with very complex industries that have to support thousands of applications for different lines of business. There is also a link to ideas of cloud computing. WebScale operations do not necessarily involve virtualisation, but typically there is a correlation between ideas of cloud computing and web scale. Some of the issues at web scale include:
We’ve already had fear-mongering about DevOps potentially killing off operations positions (thanks NoOps) and now it’s the turn of articles about DevOps killing off the developer. Terms like full stack developer are thrown around and other un-helpful terms that recruiters seem to love. Let me make one thing perfectly clear. I don’t believe DevOps is about training people so that people can do each other’s jobs equally well. That doesn’t make sense. There always needs to be specialists. The cultural changes encouraged by the DevOps movement should result in people in Dev and Ops having an appreciation of what the other groups do and the kind of decisions they have to make and why. All too often I have witnessed developers putting technology X into a product because it is new and hot and they want to use it, no matter what the consequences to QA, operations and so on. Dev and Ops should work together. Sure, that might mean that someone from operations spends some time in code working with developers getting an understanding of what’s going on and why, especially when it affects infrastructure design. The same goes for developers, spending some time doing some basic administration and maintenance of systems that traditionally fall outside of the developer role is a good thing. That said, having spent most of my time on the development side of the house and working very closely with operations I believe that developers should be involved in the consequences of their decisions. In fact the best developers I have worked with have cared about this and were extremely happy to work with operations teams if given the chance. Of course there has to be balance. If as a developer you are spending less time developing and more time playing with databases, infrastructure of whatever else you blame DevOps for I would guess there might be a couple of things going on: 1. The development team put something together than is hard to maintain once it is out of the hands of development and you are now being held accountable, or 2. You have a management problem. Either way I would say it’s not something DevOps should take the blame for. Perhaps this sounds like I am bashing developers! What I have said applies to Ops too. I’ve witnessed Ops being so resistant to change that developers feel like they are working with one or even both arms tied behind their backs due to constraints imposed on them. So no, DevOps isn’t killing off the developer, it’s not killing off operations or anyone else. It should be helping you collaborate and work effectively which will ultimately let you spend more time doing what you do best.
I’m really looking forward to DevOpsDays Pittsburgh this week. The first DevOpsDays event in a city is always special. I’m not sure what to expect, but I think it’s going to be great and at the very least I’ll get to have some great conversations about DevOps, configuration management and play some werewolf! I’m due to present an ignite session too, I have one lined up already but theres a good chance I might come up with something new based on conversations and presentations on the first day of the event. I’ll be at the event with Adi Aloni, so stop by and talk to us about CFEngine and some of the exciting things we are working on.
Introduction CFEngine users version their policies. It’s a reasonable, easy thing to do: you just put /var/cfengine/masterfiles under version control and… you’re done?
What do you think? How do you version your own infrastructure?
Problem statement It turns out everyone likes convenience and writing the versioning machinery is hard. So for CFEngine Enterprise 3.6.0 we set out to provide version control integration with Git out of the box, disabled by default. This allows users to use branches for separate hubs (which enables a policy release pipeline) and enables Design Center integration.
