Ask Your Question

How to use module msopentech-windowsazure to create Azure Windows VM and some other doubts

asked 2015-01-20 06:42:29 -0500

ravi032 gravatar image

I have one puppet master created using Puppet Enterprise image from VM gallery in Microsoft Azure. I have created 2 VMs, one Windows Server 2012 Datacenter and another Windows Server 2008 R2 and added Puppet master detail at the time of node VM creation using azure. I could see these 2 node VMs listed in the PE console.

Now, I have connected my puppet master using putty. I have installed module "msopentech-windowsazure" using command "puppet module install msopentech-windowsazure" and at that time I was at directory location "/home/xyzUser" location wher eassume xyzUser is my puppet master user id

I have check that, this module has been installed under directory location "/home/xyzUser/.puppet/modules/".

After that, I went to PE console to search that class (windowsazure), But this class is not available in class list.

I also went to "Live Management" => Control Puppet tab. There I am able to see only one node listed i.e. only master not and no child notes are listed. Child nodes should be listed there.

So, Questions are,

Have I installed module correctly?

Why module class is not showing on PE console in search result? Am I missing anything?

Why child nodes are not listed on Live Management tab?

Also, as per link I need to run commands. Kinldy do explain me, where and how do I run command to create a new node VM [windows] and delete existing VM?

Kindly provide your answer considering me beginner here. Thank you in advance.

edit retag flag offensive close merge delete


Have you downloaded this guide yet? I'm not an expert on Windows Azure, but I wonder if some of your questions might be answered in that document. Also, have your agent nodes generated certs, and do you have any pending cert requests in the console?

GregLarkin gravatar imageGregLarkin ( 2015-01-20 18:53:22 -0500 )edit

I have downloaded that book. Unfortunately, it does not have what I am looking here. :(

ravi032 gravatar imageravi032 ( 2015-01-20 23:09:23 -0500 )edit

What version of Puppet do you have? Have you approved the certs for your Windows agents, and have they invoked a Puppet run yet?

GregLarkin gravatar imageGregLarkin ( 2015-01-20 23:31:39 -0500 )edit

I am using version 3.x.x and don't go into certs approval as it was not required. I created puppet master and agents using wizard as per this link

ravi032 gravatar imageravi032 ( 2015-01-21 00:00:37 -0500 )edit

Please check page #9 of the guide - that's where it discusses approving the certificates generated by the agents. Did you skip that step, or why was it not required in your environment?

GregLarkin gravatar imageGregLarkin ( 2015-01-21 12:15:04 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2015-01-27 22:42:11 -0500

GregLarkin gravatar image

I checked with some folks at HQ, and I was told this about a possible reason for the problem reported using Windows Azure:

We have an issue on Azure with the VM, where networking is not configured properly - it hands out an internal DNS name when configuring the MCO plugin on agents, instead of a FQDN... and most of the time MCO agents are unable to resolve the name

A new Azure Gallery image is currently in the works, so please keep an eye out for a new release of it that will likely contain a fix to this problem.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2015-01-20 06:41:13 -0500

Seen: 244 times

Last updated: Jan 27 '15