Skip to main content

[string]$My_New_Journey = 'Learning the back end of PowerShell' classes and methods

So, what will my first write-up be about? Learning the back-end of PowerShell. PowerShell calls on the .NET framework and allows you to access .NET API's. It also allows to to call in "classes". These classes hold valuable information of different types, methods, and how you interact with certain aspects of PowerShell. It's one thing to be able to use these classes (blueprints) and methods (actions). It's another to be able to CREATE them. With that, since PowerShell accesses a ton of C#, let's jump into C# (Please Note: I'm a total C# noob).

First, you start off with your application. I chose a standard console application.

On the top, you see "using". What is "using"? Using allows you to import certain libraries of the .NET framework in C#. What are libraries? In short, libraries hold a ton of classes. Those classes contain the methods that you will be calling. Often, folks call classes the "blueprint". So think of libraries as containing multiple blueprints.

Next, I'm going to specify my method.

I'll ask you to draw your attention to two things;
"public void AddGrade(float grade)"

Here, I am defining my method. For my class, I am defining my method as AddGrade with a value of float and a member of grade. My member/method can take a value of float. Float is a number, but it's not a [int] type.

Next, I am taking my list that I created (the list allows me to have multiple values for my method/member), using the Add method, and putting in my grade member.

Now, for my class called GradeBook, I can utilize my method AddGrade with a flat value.

Notice another line here. "GradeBook book = new GradeBook();". This is defining my variable value. It's asking to create a new instance of my class GradeBook and put that into my variable called book. After that, I can use my "AddGrade" method to call floating numbers.

Now, why is this important for a Sysadmin/Engineer you might add? Well, with the world of IT changing around us, many of us are using automation. If you're in a heavy Windows environment, you're most likely using PowerShell. If you're still using batch, I'm very sorry. When you're using PowerShell, you're using classes, members, methods etc. Give this example;

$Process = Get-Process

^ The above example you are using the MEMBER called count. Count tells you how many things are currently in processes.

Let's try another;

^ Here, I'm using a METHOD. This method is performing an action to search for any process with Windows.

Now, let me get to my point. We know HOW to use members and methods, but do we know WHAT they actually are? Or how they are created? Or what their true purpose is? This folks, is the beginning of "The New Life Of A Sysadmin". We aren't just pointing and clicking anymore. We are turning into a form of Developers and utilizing DevOps practices. We are in an exciting time where we ARE changing the way IT works from an infrastructure standpoint and a team standpoint. Welcome to my blog, and I hope you enjoy the ride as much as I will.


Popular posts from this blog

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …