Launching the ARM template

Sections

The Puppet Enterprise ARM starting template launches the Puppet Enterprise Azure Image.

  1. Launch a Microsoft Azure PE VM from the Azure Portal's templatesPowershell, or SDKs: RubyPython, Go, or Java. To configure your Puppet master, select or create each of the following options:
    • Resource Group (required): Create a new group or reuse an existing group.

    • Location (required): If you use an existing resource group, the location must match the resource group's location.

    • Admin Password (required): The password for the Admin user. If you choose sshPublicKey as the authorisation for the VM, this password is used as a fallback.

    • VM Size: The minimum VM size capable of running Puppet Enterprise is Standard_D3_v2.

    • Admin User Name: The user name to use when logging into the VM with SSH.

    • Authentication Type: The supported types are sshPublicKey or password.

    • SSH Public Key: If your authentication type is sshPublicKey, this should contain your SSH public key.

    • Virtual Network New Or Existing: If this is set to existing, you do not need to enter an address prefix or subnet.

    • Public IP Address New Or Existing : Set to new and specify a static IP address. If the IP is dynamic and the VM is restarted, you won't be able to access the console, because the console uses the initial public IP address.

    • Public IP Address Domain Name Label: This label forms the prefix of the VM's fully qualified domain name.

    • Storage Account New Or Existing: If this is set to existing, you do not need to enter an account type.

  2. Connect to the Azure VM using the key pair created in step 1 and the user name puppetadmin by running:
    ssh -i ~/.ssh/id_rsa.pem puppetadmin@<Azure VM FQDN or public IP> 
    SSH keys are automatically provisioned based on the specified authentication type.

    Or, when connecting enter the admin password you defined previously:

    ssh puppetadmin@<Azure VM FQDN or public IP> 
  3. Wait for PE configuration, which begins automatically while booting the Azure VM, to complete. This takes about 8 minutes, and must finish before you connect and manage nodes. To determine when the PE services are fully configured, use the check_status.sh script.
    /opt/puppetlabs/azure/bin/check_status.sh --wait 
  4. As root, set the console password. Console access is disabled until the password is set.
    sudo /opt/puppetlabs/azure/bin/set_console_password.sh
    
    Puppet Enterprise console password: **********
    Note: You can run this script at any time to reset the console password.
  5. Using a web browser, connect to the console, accept the console's certificate, and login with user name admin and the password set in step 4.

    Once you are logged in, the console indicates that the master is actively managed by showing “1 Nodes run in enforcement”; the node it refers to is the master itself.

    For help accessing the console, see the PE documentation.

  6. Optional. Configure PE certificate auto-signing.
Results

The Puppet master is now ready to manage nodes, and for agents to connect to it.

Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.