Published on 22 December 2016 by

Editor’s note: This is one in a series of posts about using Puppet to automate your Windows servers. For a deep dive into managing Windows with Puppet, check out our white paper, Managing Windows with Puppet Enterprise.

It's easy to get started using Puppet and Microsoft Azure together. Microsoft has recently been working with open source communities to support a wide variety of platforms, allowing customers to deploy both open source and commercial offerings. Puppet is available through the Azure Marketplace, making it easy to deploy and manage your infrastructure with Puppet.

Deploying Puppet-managed virtual machines is now as easy as deploying any VM in Azure. And you can enjoy the advantage of managing your Azure VMs with the same platform you use for your physical infrastructure, including all your compute servers (regardless of platform — Puppet supports a wide range of *nix platforms), network devices and more.

Simply search for Puppet Enterprise 2016.1 Template in the Azure Marketplace to get started, as shown below.

The Puppet Enterprise template in Azure Marketplace

In the image below, you can see where to click on the Puppet Enterprise module to get started. Create and configure Puppet virtual machines through the Azure dashboard. Set your username and password, then select machine size. Standard D2 V2 Azure machine configurations are highly recommended — they're fast, inexpensive and run Puppet really well.

Create and configure Puppet virtual machines through Azure dashboard

A preconfigured system will be created to run and test Puppet. Storage, security ports and more will be prefilled with common settings, but can be changed to meet specific needs.

Creating a virtual Linux machine (using Ubuntu 14.04) takes about five minutes. Once the machine has been created, Puppet will run a set of install scripts for approximately 10 minutes.

Next, create a Windows Server 2012 R2 Datacenter image through the Azure resource manager. Under Extensions, install the Puppet extension to configure the Puppet master for each virtual machine. It's possible to connect hundreds of agents to a single Puppet master. For examples of this, please check out our sample template.

Once your Puppet network is set up, it's easy to visualize the network using the Azure Resource Manager Template Visualizer:

Visualize your network using the Azure Resource Manager Template Visualizer

Once you’ve configured and deployed your Azure network, you can manage it like any other Puppet cluster. For more detailed instructions, check out our white paper, Getting Started: Deploying Puppet Enterprise in Microsoft Azure.

Kenaz Kwa is a senior product manager at Puppet.

Learn more

  • You can learn a lot more about gaining visibility and situational awareness of your Windows environments — plus easier automation! — in our white paper, Managing Windows with Puppet Enterprise.
Share via:
Posted in:
Tagged:

So what is the default login to access the Puppet Master console? I know this article is a bit dated but I followed it using the latest deployment template available and I can't access the console. I found this documentation: https://puppet.com/docs/pe/2017.3/console_accessing.html but this is what I get when I follow those instructions:

[[email protected] ~]$ sudo /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/server/bin/set_console_admin_password.rb <replacement password>

-bash: [email protected]#$: event not found

The content of this field is kept private and will not be shown publicly.

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.