Puppet Blog - Page 48

If you read Max Martin’s fantastic DevOps December piece, Q: Are We Not Devs? A: We Are DevOps!, you were probably wondering two things: What’s with the funky title? (hint: it’s a nerdy DEVO reference) How do I set up my own Puppet + Vagrant development environment? Lucky for you, Max wrote a fantastic two-part […]

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 […]

Last week, I hosted a webinar titled the “Best Practices for Learning Puppet”. Although there are several ways that you can master the Puppet DSL, I chose specifically to discuss our Learning Puppet VM because I find it to be the fastest and easiest way you can learn Puppet. For those of you who don’t […]

It’s January, and with that comes the usual buzz of resolutions, goal-setting, and discussions around what to accomplish in 2013. Some will set personal goals, others will focus on professional goals, and organizations will look for ways to ensure they have the right staff working on all the right things that will enable them to […]

A few days ago, I left you with Part 1: Top Questions on Puppet and Windows. As I mentioned in that blog post, I received a ton of questions during a Puppet Enterprise and Windows webinar that I recently hosted — so many that I couldn’t get to all of them. In part 1, I answered […]

Last week, I hosted a webinar on Puppet and Puppet Enterprise on Windows. During the half-hour-long demo, I covered a number of items, including how to use Puppet Enterprise to manage Windows machines, and how to manage fundamental resources on Windows (in contrast with the same resources on Linux). I also dove deeper into Windows-specific resources, […]

Good testing of Puppet code involves different approaches and techniques that can be complex and time consuming. You can test your manifests’ syntax with puppet parser validate, verify their code style with puppet-lint, test modules logic and behaviour at catalog level with rspec-puppet, and check the actual effect of a Puppet run on dispensable virtual […]

How did Australian broadband network manage to roll out services as they were being built? Continuous delivery & DevOps.

Continuous integration begat continuous delivery; continuous delivery begat DevOps.

Today, we are launching the beta version of a new question and answer site where you can ask any Puppet questions or provide answers for questions from other Puppet users and developers. We have an active online community of open source and Puppet Enterprise users, and ask.puppetlabs.com is another great forum for answering Puppet questions, […]

Since 1999, my passion has been studying high performing IT organizations. This journey started off when I began keeping a list called “Gene’s list of people with good kung fu.” The people on the list talked differently about IT Operations, acted differently, and most importantly, had profoundly different results than your typical IT organization.

On this journey, I studied these high performers and benchmarked over 1,500 organizations. Our goal was to understand what enabled them to do what most organizations could only dream of. Our findings went into a book that we published in 2004 called The Visible Ops Handbook, which described how these organizations made their “good to great” transformation.

What I couldn’t have predicted was how this journey would take me straight into the heart of the DevOps movement. As my friend John Willis told me after I dismissed DevOps as just another marketing fad, “DevOps is the best chance at relevance that IT Operations has had in thirty years.” I immediately realized that he was right.

We’re excited to announce our second annual DevOps Survey, in conjunction with IT Revolution Press. Our last survey saw over 700 respondents and showed us how DevOps has evolved since the term was first coined in 2009 by Patrick Debois. A lot has changed in the last 18 months, and we want to know how […]

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.

The International Securities Exchange (ISE), a leading US options exchange, has just completed the first phase of its Puppet Enterprise deployment. For a company exceeding trading volumes of 2.5 million contracts per DAY, the decision to ‘puppetize’ their infrastructure not at random — it was carefully determined and deliberate. Trevor Pott, reporter from The Register, […]

Hi, I’m Eric Sorenson (eric0 on #puppet IRC), and in June 2012 I moved from being a community member and Puppet administrator in the field, to working at Puppet Labs as the Product Owner for our open source projects. At the time, my first goal was to help get a great release of the next major version of Puppet (code-named “Telly”) shipped to the world, which launched late last month. Now with the release of Puppet 3.0.1 — which addressed and fixed the biggest issues that our awesome community of early-adopters found in the 3.0.0 release — it seemed like a good time to blog from the rooftops.

I’m new to Puppet Labs, but I have been running Puppet in large-scale production operations since 2009 and, somewhat naïvely, felt like I had a good idea of what Puppet 3 was supposed to look like. There had been, after all, a few dozen bugs in Redmine over the past couple of years in which the “Target Release” field I’d seen James or Nigel set to “Telly” … it was going to fix all the bad behavior we’d all reported over the years, right? Well, not exactly.

The tough thing about major releases of popular products is that the burden of expectations becomes so great, there’s no way reality can measure up. In some cases (The Phantom Menace, Guns n’ Roses “Chinese Democracy”) when the release does come, it’s universally panned on its own merits; other times, the release might have been fantastic if it had come when it was promised, but the timing was such that it had already gone stale (Duke Nukem Forever).