If you’re reading this, there is a good chance that you do some sort of project work within your job. My blog doesn’t attact a lot of people outside of IT and the typical IT guy is working on project X, Y or Z and sometimes all 3 at the same time. If this isn’t you, I’ll save you some time and you can stop reading now.

Ok, so you are working with your boss and he/she has assigned you a project. Maybe its mapped out with all of the details or if you are like me, you will typically get a broad project goal and its your job to come up with the milestones and timeline.

In our first post, we gave you the overview of what puppet was and how to install the software so its available on your system. Now its time to get into the guts of the system and get your client connecting to your master server.

Configuration

By default, puppet really wants to look for a server at puppet.. If you need to change this to a different server name, you’ll want to edit the /etc/puppet/puppet.conf file and add in an entry such as this:

Back in January, I gave a presentation for the local LUG group (CIALUG) and while it was nice to put it all into one presentation, I’d like to go back and break down the various aspects of the presentation and show off what Puppet can do in your organization.

What is it?

Puppet is a tool designed to manage the configuration of Unix-like and Microsoft Windows systems declaratively. The user describes system resources and their state, either using Puppet or Ruby DSL (domain-specific language). This information is stored in files called “Puppet manifests”. Puppet discovers the system information via a utility called Facter, and compiles the Puppet manifests into a system-specific catalog containing resources and resource dependency, which are applied against the target systems and any actions taken to remediate the system to the desired state will be reported. (Source: WikiPedia)

Before VMworld, I laid out a few of my predictions of what I thought we’d see at the conference. Let’s see how I did…

• vRAM is dead. The rumors were true. This was kind of a gimme but I’ll take it. So long vRAM licensing!
• vCloud 2.0. Got this one too though its vCloud 5.1 to line up the numbering scheme with vSphere. We have snapshots and multiple disk levels supported within the provider vDCs. At the conference, I can’t say for sure that the vConsole app was new, but it worked in Chrome which is a huge step forward.
• Virtual Phone for iOS. Yup, but not in the same way that they are doing it for Android. But still a protected application that has some nice tricks like not allowing you to copy and paste from the protect app to another application running on the phone.
• One pane of glass to rule them all. You could argue that the purchase of DynamicOps makes this happen, but its not fully integrated yet. I think next year will be the real integration and we’ll get that one pane of glass feel to managing our environments.

3 out of 4 isn’t too bad.

Last day of VMworld!

Its been a good conference for me. Solid sessions and the labs that I’ve done have been good. Its my second year here so things are a bit different than they were last year. In Vegas in 2011, I loaded up my schedule with sessions upon sessions. This year, no where near as many sessions as they are all online and available after the fact. This year I tried to get into the labs more, but honestly, the labs had some issues. There were quite a few issues just getting the sessions to launch for me in the “traditional” route. Where I had the better luck was with the BYOD labs. Basically load up a web page, launch the lab and then fire up your view client. Slick! And the best part, there have been rumors and a wonderful lady that I spoke to yesterday pretty much confirmed they will offer the labs after the conference. Solid!