I recently came across an extremely useful PowerShell script to manage images and extensions within the Azure Stack marketplace thanks to this post by Kris Turner: https://kristopherjturner.com/2018/12/14/azure-stack-marketplace-management-powershell-script/
This script will download all current Microsoft virtual machine extensions from the marketplace. It also downloads Ubuntu Server and Windows Server images as well. Once all have been downloaded, it will compare versions and prompt you to remove older versions if desired.
The goal of this post to help fill in the gaps from the Microsoft Azure Stack User Documentation on deploying a secured service fabric cluster using the Azure Stack Developer Kit (ASDK). The same steps could easily be used on the Azure Stack integrated system.
Issue: When updating from 1.1805.7.57 (1805 hotfix) you may encounter an issue with Alerts displayed that are not actually true. The alerts, upon further investigation, appear to be false, but they cannot be closed from the portal.
Version Impacted: 1.1807.0.76 (only seems to be present when upgrading from 1.1805.7.57)
Microsoft Response: Being unable to clear the alerts after updating to 1807 is currently a known issue and fixes are under investigation. There is no resolution at this time.
The two alerts I received specifically were the following:
- Azure Stack update stopped with errors – Critical – Capacity
- Activation Required – Warning – Azure Bridge
In this learning puppet series, you will see my thoughts and notes as I work to teach myself puppet within my own home lab. Any issues I come across will be documented here along with any notes I wish to save to document my journey.
I hope find this series helpful and I challenge you to take on this task with me as well! I have absolute zero experience with using puppet as a configuration management tool. In the past, I have used various shell scripts or powershell scripts to automate configuration tasks. Puppet provides an easier and better way to standardize configuration across your infrastructure.
I will be using the Puppet Learning VM along with a book “Puppet 4.10 Beginner’s Guide” by John Arundel. The book is fairly dated, but after reading several reviews I feel this is a good place to start and then we catch up to the latest release (5.x) from there.
To begin, let’s discuss the lab configuration. My initial thought is to start small with the Learning VM and a small local instance. Once I’m comfortable enough, I would like to test out a larger instance using AWS. Puppet has a Pay As You Go enterprise instance on AWS that is free for 1 – 10 nodes. Even though that may be free, the compute/storage in the lab to run it won’t be which is why I will want to refer to AWS much later.
Home lab configuration:
- Puppet Master
- Ubuntu 16.04.2 LTS (Xenial)
- 6GB RAM
- 2 x CPU
- 100GB storage
- Puppet nodes
- Ubuntu 16.04.2 LTS (Xenial)
- DNS1 – DNS server for the home lab
- WEB1 – Apache/PHP server for testing
- DB1 – MySQL DB server for testing