Entries filed under: General News

Back to Index

R.I. Pienaar Joins Puppet Labs

Posted on
By
Jason
in
Blog, Company, General News, MCollective
Responses
4 Comments »

I am very pleased to announce that R.I. Pienaar, founder and lead developer of the widely used Marionette Collective (MCollective) orchestration tools, has joined Puppet Labs as a Software Architect. R.I.’s message-based orchestration tools have become some of the most widely used tools in systems management, and have literally changed the way that people handle ad-hoc command and control, orchestration, and parallel job management. Having R.I. join the Puppet Labs team is a significant milestone for us, as R.I. will help shape product efforts in MCollective, Puppet, and Puppet Enterprise.

Puppet Labs acquired MCollective from R.I. in late 2010. Since then, MCollective has become a critical piece of the Puppet infrastructure with direct integration in Puppet Enterprise for Live Management, as well as standard orchestration functionality. R.I.’s efforts in this regard have had significant impact on product for the company including Puppet Enterprise 2.0.

R.I. will continue to work on MCollective (since MCollective is now directly integrated into our products), but will also work on some of our new projects to be announced in the future. We are very glad to have R.I.’s considerable creativity and industry experience on the team helping with new products that will give sysadmins new tools and delight Puppet users.

In R.I.’s own words:

I’m really excited to finally be part of the Puppet Labs team. I’ve been part time member for over a year and it’s great to finally be a full time team member. I look forward to the opportunities this new venture brings in helping me further the DevOps eco-system.

Puppet Triage-A-Thon: The Results are In!

Posted on
By
James Turnbull
in
Blog, Community, General News, Open Source, Users
Responses
1 Comment »

The first Puppet Triage-a-thon was a huge success. Thank you so much to everyone who attended and contributed! Some of our favorite stats from the event:

  • We started the day with 2292 open tickets. Over the course of the day 565 tickets were triaged. We also closed 115 tickets. That’s almost 25% of the open tickets triaged and 5% closed!
  • Seventeen community patches were submitted! (And many of these were merged during the day.) Several patches were from people who’ve never contributed before, which is awesome.
  • We had about 50 people involved globally. Individuals and teams participated from Germany, Mexico, Australia, United Kingdom, France, and across the United States. And a big shout-out to the Atlanta Puppet Users group who had a team of five people!  We also had about 10 community members onsite in the Puppet Labs offices locally in Portland.

Our top contributors from the community were:

  1. Dominic Cleal
  2. Devon Peters
  3. Patrick Otto
  4. Oliver Hookins

They’ll be the recipients of $100 Amazon gift vouchers. The full list of participants is here, along with the tally of tickets triaged: http://triageathon.puppetlabs.com/

Everyone who contributed will receive a Puppet Labs t-shirt. If you participated you’ll receive an email shortly asking you for your preferred t-shirt size and where you’d like us to send it.

We’re going to continue to run these events in the future to keep the ticket database fresh and up-to-date.

Thanks again to everyone who came along and contributed and made it such a great success and an awesome amount of fun!

Newsletter – January 2012

Posted on
By
michelle
in
Blog, Company, Conferences and Workshops, DevOps, General News, How to, Open Source, Puppet Enterprise, Tips
Responses
0 Comments

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 Module of the Month: Jenkins
One of 200+ freely downloadable modules to help you get started.

The Next Generation of Example42 Puppet Modules
Updated module collection for version 2.6 and later.

 


Puppet Master Power-Ups

Puppetizing OpenNebula
Provision a virtualized infrastructure.

“Stop Writing Puppet Modules That Suck”
…With these helpful steps!

Use it: Tim Sharpe’s Puppet Profiler
“Find out what’s making your Puppet runs so bloody slow!”

Puppet Internals: The Parser
Learn how Puppet translates code into configuration catalogs.

Taking Puppet Enterprise deployment automation one step further
Deploy a server with a single command.

 


Graphic of the Month
Read the blog and watch the video to build out Puppet Enterprise stacks with AWS CloudFormation.
 

 


DevOps In Action

Puppet + Gephi: Visualizing Infrastructure as Code
Use your resource graph for DevOpsy goodness.

DevOps Process Consulting
Get a jumpstart on your DevOps environment.

 


Puppet In The News

Services ANGLE: “5 Open Source Startups to Watch in 2012″
Reading the newsletter is a good start.

Services ANGLE: Top 10 Dev & Eng Skills Employers will be Looking for Going into 2012
Check the full list before making your New Year’s resolutions.


In Case You Missed It

From Luke: Looking Forward to 2012
Design, Big Data in the Infrastructure, and DevOps.

Thank You, O.S.S. for P.E. 2.0
Puppet Enterprise didn’t come out of nowhere.

Portland Business Journal names Top Forty Under 40
Big thanks to the PBJ.

 

Puppet Camps

Atlanta
Feb 3

Edinburgh
March 23

Stockholm
March 28

Upcoming Events

Puppet Enterprise 2.0 Q&A webinars
Fri, Jan 13

SCALE 10X – Los Angeles
Fri, Jan 20 – Sun, Jan 22

Puppet Triage-A-Thon
Sat, Jan 21

FOSDEM – Brussels
Sat, Feb 4 – Sun, Feb 5


 

Upcoming Trainings
San Jose
Mon, Jan 16 – Wed, Jan 18

London
Tue, Jan 24 – Thu, Jan 26

Sponsored by Netways – Nuremberg
Wed, Dec 7 – Fri, Dec 9

Sao Paulo
Mon, Jan 30 – Wed, Feb 1

Atlanta
Tue, Jan 31 – Thu, Feb 2


 

New Open Source

puppet-puppetdoc
By James Fryman


 

Job Openings
Release Intern

Community Manager

Sr. Professional Services Engineer (USA)

Technical Writer


 

User Groups

Silicon Valley
Los Angeles
New York City
Seattle
Atlanta
Switzerland
Italy

 

Connect With Us
 
RSSFacebookTwitterLinkedIn
SlideShareYouTubeflickrIRC
Puppet Enterprise users list
Puppet users list
Puppet dev list

 
…or contact us directly

Puppet Triage-a-Thon

Posted on
By
jose
in
Blog, Community, General News, Puppet Camp, PuppetConf
Responses
0 Comments

The Puppet community has grown quickly, and a lot of you have logged tickets and issues. We’ve tried to give those tickets as much love as we could but some slip through the cracks, and sometimes we get overwhelmed. We’ve recognised this and want to get a handle on the backlog of tickets. But we need your help.

Enter Triage-a-thon, hosted locally in our offices, virtually on IRC (#puppethack) and the Web. We’re going to review all the open tickets in the Puppet project with a view to:

  • Update and confirm that issues are still relevant
  • Ensure tickets are in the right status and all the right information is present to help us resolve it
  • Close any invalid or no longer relevant tickets

We’ll assign blocks of tickets to every participant, have documentation explaining what you need to do and provide people on the ground to help you make decisions and answer questions.

We’ll also provide pizza, snacks and a venue locally in our Portland, Oregon offices. Virtually we’ll provide an IRC channel (#puppethack), IM, and rewards (t-shirts, patches, stickers, badges, and books) for people who triage tickets and get involved.


Register

Puppet Labs at SCALE 10x

Posted on
By
jose
in
Blog, Community, General News, Puppet Camp, PuppetConf
Responses
0 Comments

If you’re headed to SCALE 10x this weekend in Los Angeles, here’s a brief schedule to help you find us at the event:

  • Register using our discount code PUP12 for 40% discount!
  • Join us for a half-day training session on Friday 1/20 at SCALE University
  • Come by booth #42 for a Puppet Enterprise demo, t-shirts, and stickers
  • Stop by our BOF Friday 1/20 at 7pm for an informal Puppet discussion
  • See Professional Service Engineer Carl Caum speak about AWS and Puppet at 4:30 on Sunday

Hope to see you there!

Puppet Camp Atlanta, Feb. 3rd

Posted on
By
jose
in
Blog, Community, General News, Puppet Camp, PuppetConf
Responses
0 Comments

Puppet Camp Atlanta is only a few weeks away! If you’re in the Atlanta area or nearby region, this event is for you! Puppet Camps are local, 1-day events that feature a mix Puppet Labs engineers, local speakers, and unconference talks generated by the audience. We’d like to thank our Sponsor MomentumSI for helping make Puppet Camp Atlanta possible!

Registration is now open and the nearly-finalized schedule is available.

We hope you’ll join us for Puppet Camp Atlanta, the first of many new Puppet Camps sprouting up worldwide.

Check out the tentative schedule below—much of the afternoon will be devoted to unconference talks (ie, you can lead the charge on a topic you care about).

Speaker Presentation Time
Kelsey Hightower

Puppet Labs

There’s a Module for That!

An in depth look at the Puppet Forge and it’s companion, the Puppet Module Tool. During this talk a Puppet module will be created from the ground up and released on the Puppet Forge.

9 AM
Gary Larizza*

Puppet Labs

Examples for Separating Data from Puppet Code

One of the first, and biggest, hurdles that Puppet users encounter is ‘How do I make this Puppet code work across all my environments?’ There are several ways to solve this problem, and Gary will give examples of many of the popular methods. He’ll also introduce you to Hiera: the next-generation data lookup system that will be bundled with the next major release of Puppet.

10 AM
Clint Savage

Shadow-Soft

Centralized Authentication with Puppet, LDAP and Linux

This talks about using Active Directory or LDAP as the authentication source, using puppet to update when a new user is added and setting up proper authentications with pam, sssd, ssh and /etc/security/access.conf, among other considerations.

11 AM
Tom Hite

VP Solutions for MomentumSI

Using Puppet to Automate Amazon Deployments

As Amazon continues to grow market share in the public cloud, users are deploying more sophisticated multi-tiered applications. This presents a DevOps challenge related to consistent provisioning, configuring, scaling and locking down resources. This session will discuss the use of Puppet and CloudFormation to automate cloud deployments and system upgrades.

1 PM
Kenn Hussey

Cloudsmith

Geppetto – tooling for Puppet development

This talk will provide both an overview of current approaches to developing Puppet modules, as well as a look forward toward an expanded vision that includes publishing and consuming modules with the Puppet Forge.
We’ll review the current state of the art in tooling for working with modules, with a particular emphasis on Geppetto, a recently introduced “Puppet IDE” that simplifies the process of creating and editing manifests and modules. We’ll also demonstrate Geppetto’s key features and also show how Geppetto supports module development, publishing and consumption in an integrated workflow.

2 PM

*Gary is also teaching the Atlanta Puppet Master course. A ticket to this course is also good for admission to Puppet Camp Atlanta.
Hope to see you there! Register today.

Using CloudFormation to Build out Fully Functional Stacks of Puppet Enterprise

Posted on
By
Dan Bode
in
Blog, Cloud, Extending Puppet, General News, How to, Tips
Responses
2 Comments »

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 wide range of AWS resources, including: EC2 instances, security groups, credentials, as well as a host of other resources.

EC2 meta-data and user data can be associated with AWS resources in a CloudFormation template. This meta-data allows CloudFormation to not only provision EC2 instances, but also to bootstrap those instances into a functioning application stack.

The CloudFormation Face is a command line tool that can use this meta-data to specify all of the required information to bootstrap an entire Puppet Enterprise stack, including: modules to be downloaded from the Puppet Forge, groups to be created in the Enterprise Console, Puppet Agents to be provisioned, as well as security groups and classification information to be associated with those agents.

Pre-requisites

The following things need to be setup before the Puppet CloudFormation Face can be installed:

  1. AWS credentials are required. These credentials must be associated with an account that has full administrative rights. Instructions for how to sign up for Amazon Web Services (AWS) can be found here.
  2. Requires that a keypair exist within the region in which resources will be launched. This keypair is used to refer to user public keys that can be injected into created EC2 instances. We recommend us-west-1. Remember what region you made a keypair for, you’ll need it later.

Installation

These tools can be easily evaluated with the Learning Puppet VM, or you can follow the manual installation instructions in the README on GitHub.

  1. Download the Learning Puppet VM, follow instructions to boot the virtual machine and log-in as root. Note: You may want to ssh into your running Learning Puppet VM for easy copying and pasting.
  2. Once logged in, use the following command string to download the CloudFormation Face from the Puppet Forge, unpack it to Puppet’s module path and rename it to cloudformation.
    cd /etc/puppetlabs/puppet/modules && curl http://forge.puppetlabs.com/system/releases/p/puppetlabs/puppetlabs-cloudformation-v0.0.1.tar.gz | tar -xz && mv puppetlabs-cloudformation-0.0.1 cloudformation
  3. Export the ec2 region you created your keypair for in the prerequisites section.
    example: export EC2_REGION=us-west-1
  4. Make sure time on the virtual machine is up to date.
    ntpdate pool.ntp.org
  5. CD into the cloudformation directory and edit examples/install.pp to include your AWS credentials and insert your java home. It will look something like this:
      class { 'cloudformation':
        aws_access_key => '< your key here >',
        aws_secret_key => '< your secret key here >',
        java_home =>/usr/lib/jvm/jre-1.6.0-openjdk’,
      }
  6. Apply the modified manifest:
     	puppet apply examples/install.pp

    This will install the CloudFormation client tools and create the file: bashrc_cfn

  7. Source the bashrc_cfn file to set up all of the necessary environment variables.
      	source bashrc_cfn
  8. Verify that the CloudFormation client tools were successfully installed and configured by running the following:
    	cfn-describe-stacks

    A return of ‘No Stacks found’, validates that the client tools are correctly configured.

  9. Verify that the CloudFormation Face is properly configured by running:
    	puppet help cloudformation deploy

    Basic usage information should be returned.

Creating a Puppet Enterprise environment from scratch

Since puppetlabs-cloudformation can reliably build out fully functional Puppet Enterprise environments, it is an ideal tool for evaluation or experimentation in EC2. Let’s build an example stack.

The ‘puppet cloudformation deploy’ action can be used to build out complete stacks of PE. The command below shows how to build out an prepared Puppet Enterprise evaluation environment. Supply your own ‘keyname’ and ‘stack-name’ to the above command.

	puppet cloudformation deploy \
		--stack-name DemoStack \
		--config config/pedemo.config \
		--disable-rollback \
		--master-type m1.small \
		--keyname <your-ec2-key-name>

Once the stack has successfully launched, use:

cfn-describe-stacks

and

	cfn-describe-stack-events <StackName>

to check the current state of this stack.

Once you see the state of CREATE_COMPLETE, you’ll also receive the public dns name of your new Puppet Master. You can open your web browser and browse to https:// and log in with the user name cfn_user and cfn_password to visit the Puppet Enterprise Console. Check out the video below to see this in action.

config:pedemo.config

  • install_modules – List of modules that should be downloaded from the Puppet Forge. The modules are downloaded to the modulepath of the master and all classes contained in these modules are populated into the Enterprise Console.
  • dashboard_groups – Specifies a list of groups that should be added to the Enterprise Console. Groups are specified as hashes with the following keys:
    • classes – list of classes that should be contained in the group
    • parameters – hash of parameters to be contained in the group
    • parent_groups – list of parent groups
  • puppet_agents – List of PE Agents that should be provisioned along with their classification information. Agents are specified as a hash with the following keys:
    • groups – Groups from the dashboard that should be applied to the agent.
    • classes – Classes that should be applied to the agent.
    • parameters – Node specific parameters to be added
    • ports – Creates a security group

The configuration file and its settings specify all required information to compose a stack. The information is sufficient for bootstrapping environments of PE from scratch. Although no information about a Puppet master has been specified in the configuration file, one is always created by default. This Puppet master installation includes the Puppet Enterprise Console and a security group to allow tcp access from agents to ports: 443, 8140, and 61613. It also allows tcp access on port 22 from any address.

Related Content:

Thank You, O.S.S., for P.E. 2.0

Posted on
By
Randall Hansen
in
Blog, Community, General News, Open Source, Puppet Enterprise
Responses
0 Comments

With the launch of Puppet Enterprise 2.0, it’s easy to get lost in the scale of what we’ve enabled sysadmins to do. Besides shipping a world-class configuration management tool, we now make it easy to create managed servers from thin air. In addition, we’re providing command line tools that take fresh OS installs directly to production-ready application servers with no manual intervention, monitoring and reporting for when your configuration drifts, and a web interface that allows you to inspect the current state of resources across your entire population—fast.

For all the things that we’ve done with our software, there’s a much longer list of things that we just didn’t have to do thanks to the open source community at large. So, we’d like to acknowledge some of the open source software that have helped make P.E. 2.0 a great product.

Batman

batman.js

We made the decision early in the development cycle for live management that we wanted to build an application that was as lively and responsive as possible. Our search for an appropriate browser-based-site framework led us to several options, but Batman (who showed up fashionably late to the investigation) impressed us immediately.

Applications written against Batman were reasonably familiar to most of the live management team (including those who had little prior Javascript experience), but the real stars are the hard-working members of the Batman development team. From day one, the core developers were engaged, gracious, and actively involved in helping make our product the best it could be, even as we took Batman down roads they never expected anyone would. Our own Pieter van de Bruggen has made many contributions to Batman’s core.

Fog

fog

When we were building our first pass of cloud provisioning, we began with the single target of Amazon’s EC2 cloud. Fog provided an accessible way to interface with that target (in addition to a number of future targets), so the decision felt fairly obvious up front. After building our first prototype, we discovered we had also built a tool for installing Puppet Enterprise on real hardware with only an SSH connection. With a few small tweaks, it could also work on Rackspace, OpenStack, and a large number of other providers (coming soon, we promise!). Combined with the developer’s responsiveness and guidance, Fog has been an amazing asset to us. At Puppet, Jeff McCune, Kelsey Hightower, Carl Caum, and Pieter van de Bruggen have made many contributions to Fog.

Sinatra

sinatra

Sinatra’s not exactly an unknown in the Ruby web development community, but it has been fundamental to us in our live management development. With all of our presentation logic hidden away in a lightweight frontend application, we wanted to build the backend against a similarly lightweight framework. Sinatra gave us just the right balance between power and simplicity on a well-known, stable platform.

LESS

Less is a CSS abstraction tool, helping us make the Puppet Enterprise console CSS much lighter and more maintainable.

CoffeeScript

A browser-side language, compiling to Javascript, used extensively throughout live management. Batman.js is written in CoffeeScript.

ActiveMQ

A message queue, used by MCollective to distribute work to your entire infrastructure.

Puppet, Dashboard, MCollective, and Facter

Puppet Enterprise wasn’t developed in a vacuum: the core tools themselves are open source software, and have for years received significant contribution from the community outside our doors.

And so many others…

We don’t have the words or the space to properly say “thank you” to every project whose open source work has helped us reach this release. So let me just say once, to every contributor on every project that’s touched our work: thank you. Your work has not gone unnoticed nor unappreciated, and I hope that our own contributions to open source software can serve to pay the kindness forward.

Looking Forward to 2012: Design, Big Data in the Infrastructure, and DevOps

Posted on
By
luke
in
Blog, Company, DevOps, General News
Responses
3 Comments »

2011 has been an amazing year, although I always find it a bit awkward living through a prime year. In the startup world, just continuing to survive another year sometimes feels like an accomplishment, but we’ve done so much more than that. Puppet Enterprise has been the spine of 2011 for us, with a first release in February and the 2.0 release in November. We’ve managed to be both broad and deep, with PE running across the majority of server platforms and also providing a few new capabilities in 2.0 that support specific activities like compliance and reducing arbitrary infrastructure variation.

In some ways, the biggest change at Puppet Labs was the shift to being design focused. Our development process has been wrapped around a tight focus on you, our users, and we’re building our plans and stories around who we’re building products for and what problems we’re helping them with. To make sure it’s not just our designers and developers who think in design, everyone at the company was given a copy of The Design of Everyday Things.

Finally, there was the investment at the end of the year, which will be the foundation for our future in many ways. Look for interesting partnership activity with VMware, Cisco, and Google Ventures in 2012, and for our product to grow and develop with their input and customer knowledge.

As interesting and challenging as 2011 was, however, 2012 looks even better. As Greg Lemond said, it never gets easier, you just go faster. We aren’t resting on our laurels—we still wake up scared every day—but there is still far more to do than is already done. Gartner says less than 20% of companies use any kind of server automation, and someone has to help those people. This is especially the case as companies try to adopt new technologies like private clouds or bring in new culture with devops—can you imagine trying to replace traditional infrastructure with self-serve, on-demand provisioning but no server automation? Inconceivable.

Data is a major area we’ll be looking to help people in 2012. Companies have huge amounts of data trapped within their infrastructure and few ways to extract value out of it, and there is a direct relationship between the efficiency and agility of a company and its usage of this data. Companies like New Relic and Nodeable are building businesses around helping people extract meaning from their operations data, and Puppet is one of their critical data sources. It produces vast amounts of data as a natural off-shoot of the work you’re using it for anyway, and we’re working to help you get more value out of that data. We’ve got one customer whose Puppet infrastructure—that’s just Puppet, not the services maintained by Puppet — is producing 750GB of data a day. One one hand, it’s expensive to do much with that volume of data without a clear business driver, but on the other hand, it makes clear how much more you could know about what’s going on in your world.

We like to think of our efforts in this area as Big Data in the Infrastructure. Big Data projects are already a popular way for companies to start using Puppet, but here we’re talking about getting more from your Puppet data, not just managing Hadoop. Puppet already knows what you’re managing, what it’s related to, and how it’s changing, because it needs that to do its job. We’re working on giving you a clearer picture of all of this data, and some great levers and knobs on that data so you can take action based on this new-found information.

Outside of Puppet itself, I think 2012 will be an interesting year, too. We’re a bit isolated from it up here in Portland, but there’s an interesting tech/cloud bubble going on in Silicon Valley, and I’ve got a lot of friends who see a cloud winter on the way. Personally, I think we’re finally leaving the world of pure-hype clouds and 2012 is when real-world companies start figuring out how to invest practically in the cloud, and it’s also when the cloud vendors will start to separate. Hopefully we won’t see any more “Enabling the Cloud for Business!” banners, but I’m not getting my hopes up.

I think 2011 has been a critical year for devops. Almost no one I talked to had heard of it in 2010, but this year it seems to have taken over. I can think of three long-standing conferences that had a major focus on devops, and it has gained visibility up and down the organization. The only downside is there’s still a lot of disagreement on what it means and how people can take advantage of it, but great tech movements are powered by passion and vagueness, and devops looks to be the driver for innovation in operations in the next ten years or so.

Here’s looking forward to another scary, great, fast, tedious, invigorating, draining, and amazing year.

Upcoming Events: Puppet Camps, Save the Date for PuppetConf, and More

Posted on
By
jose
in
Blog, Community, Conferences and Workshops, General News, Puppet Camp, PuppetConf
Responses
0 Comments

Join us for an upcoming Puppet Camp:

Atlanta, GA – Friday, February 3rd – Register

Edinburgh, Scotland – Friday March 23rd – Register

(Click on “Booking“)

Puppet Camps are one-day, regional events held 6-8 times per year. Puppet Camp features 4 to 5 talks followed by a few sessions of unconference. Registration costs, co-located events, and speakers will vary from event to event.

If you’d like to speak at or sponsor a Puppet Camp please contact us.

We are aiming to organize Puppet Camps in New York City and in Stockholm in March or early April, more information will be posted as it becomes available on the PuppetCamp Community page.

PuppetConf will persist as a multi-day user and community conference. We have a ton of changes coming to PuppetConf ’12 to look forward to, so mark your calendar for PuppetConf 2012: September 27-28 at the Mission Bay Conference Center in San Francisco, CA.

We also look forward to seeing you at SCALE 10X for Puppet Training at Scale University (use our discount code “PUP12″ for 40% off registration to SCALE and Puppet training), and at the Configuration Management Room at FOSDEM.