Puppet 3.2.1 landed today. Though it’s a “patch” release, it’s the first public release of the Puppet 3.2 series, and it includes a taste of the Puppet DSL’s future in the form of an experimental parser that introduces some new features you’d expect to find in traditional programming languages.
Before I started at Puppet Labs, I was a tech writer at a large corporation (I won’t name them, but their initials are HP). The approach to tech writers there conformed to the traditional “huck it over the cube wall” model I’ve seen at other large enterprises. Anyone who has worked in tech for any time at all has encountered this model, which presents a new product to the writer as a fait accompli and which imagines tech writing as an after-the-fact act of taxonomy: “Here is a thing. The thing has five things stuck to it. Three of those things are red, one of them is made of feathers.” And, we’re done.
More often than not, the huck-it-over-the-wall method results in tech writing nobody reads because it does nothing useful (“I can plainly see that thing is made of feathers, what possible good is this manual going to do me? I’m going to put it back on top of the toilet tank and continue to ignore it.”).
2012 was a huge year for us—we more than doubled in size, tripled our PuppetConf attendance, and saw overwhelming demand for and consumption of all things Puppet (Puppet Enterprise, Puppet Forge modules, Puppet Camps, and more). We’re only three months in to 2013, but we predict another stellar year. Bolstered by VMware’s recent $30 million investment, we opened offices in London, Australia, and San Francisco to build awesome new products for our growing customer-base. We also tripled the office space of our headquarters in Portland, OR, and we’re hiring like crazy!
Today I’m excited to announce that Puppet Labs and VMware have formed a new strategic partnership, after more than a year of working closely together from VMware’s initial investment in our company. This partnership involves VMware investing $30 million in Puppet Labs, as well as a commercial agreement to jointly deliver, market, and sell great […]
In the wake of recent events on the East Coast of the United States, disaster recovery (DR) planning has reared its head again. Of course, it’s a bad time to think about disaster recovery right after an event with such a large impact. However, it’s even worse to never think about it.
Prior to working at Puppet Labs, I spent a lot of time on disaster recovery. For nearly two years, I led a team designing multi-site replication, creating reference architectures for availability and recovery, and selling our business partners on disaster recovery investments. This was for one of the top performing business units at a Fortune 100 company with seven and eight figure budgets for DR.
Disaster recovery is a huge proposition. It’s costly, time consuming, difficult to test correctly and often the first thing cut when doing budget reviews. DR planning is also never complete. You evolve. You change. Your plans need to as well.
The starting points for DR planning can be difficult to find. Infrastructure engineers often jump to technical solutions. Before you figure out the newest wizbang in storage replication technologies and failover, take a step back.
My name is Mateusz Lenik, I study at Technical University in Wrocław, Poland. For the past two months, I’ve been working on expanding features of the Ruby DSL for Puppet. I’m a Ruby programmer and I was looking for Google Summer of Code projects in Ruby, which is how I came to Puppet Labs. My […]
We’re excited to announce our second annual SysAdmin Appreciation Day contest! This year, instead of asking for your full-blown stories, we’re looking for a snapshot of your experiences—sysadmin life, distilled in animated gifs. There are an number of gif sites out there, but few that focus on the sysadmin.
Purpose Configures OpenStack Module puppetlabs/openstack Puppet Version 2.7.14+, Puppet Enterprise 2.5+ Platforms Ubuntu 12.04 (Precise), Debian 6 (Wheezy) In April, we announced Puppet’s support for OpenStack, a popular open source project that can be used to build private clouds. At that time, we posted the first OpenStack configuration module on Puppet Forge, which enabled you […]
Purpose Razor Provisioning Software Module puppetlabs/razor Puppet Version 2.7+ Platforms Ubuntu Precise Razor is next generation provisioning software that handles bare metal hardware and virtual server provisioning with inventory discovery and tagging, rule-based policy management, and extensible broker plugin integration. The usage of Razor for provisioning is discussed briefly in this blog, and additional information […]
PuppetDB is the next-generation open source storage service for Puppet-produced data. Today, this includes catalogs and facts, and will be extended in the near future. The initial release provides a drop-in replacement for both storeconfigs and inventory service. We’ve designed PuppetDB to empower Puppet deployments, and built it from the ground up with performance in […]
I’m proud to announce the release of Puppet Enterprise 2.5, downloadable right now and free to use on up to 10 nodes. Just over a year ago, in February of 2011, Puppet Labs released our first commercial product, Puppet Enterprise. We were about 25 people at the time, and our revenue up until then consisted […]
Getting Started With Puppet Weekly Webinar: Ask Your Puppet Enterprise Questions Get a Live Management demo, and ask your burning PE questions. Puppet Enterprise 2.0 How To: Cloud Provisioning Start provisioning in the public and private cloud today. VIDEO: AWS CloudFormation and Puppet Enterprise 2.0 How to build out Puppet Enterprise stacks with CloudFormation. Forge […]
The Puppet CloudFormation Face integrates Puppet Enterprise (PE) with CloudFormation so that users can reliably create entire Puppet Enterprise “stacks” in Amazon’s EC2 from their workstation. A “stack” refers to a collection of launched Amazon Web Services (AWS) “resources” that can be specified as a “template” in CloudFormation’s declarative json modeling language. Templates support a […]
Why do we want configuration management? There are plenty of reasons, but at the core of them is that we want to streamline the configuration and deployment of systems. We want this process to be repeatable, well-understood, and predictable. We want to make it deterministic. Determinism — the idea that a process should result in […]