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)"
"grades.Add(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
$Process.Count

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

Let's try another;
$Process.Contains("*Windows*")

^ 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.


Comments

Popular posts from this blog

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.



Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…

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.

Pre-reqs;
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…

Spinning up a Kubernetes cluster with Kubeadm

In today's world, we have several public cloud technologies that will ultimately help us with spinning up these infrastructures. This however comes with a price. Because a public cloud provider (like AWS or Azure) handles the API/master server and networking, you'll get something up quick, but miss some key lessons of spinning up a Kubernetes cluster. Today, I'll help you with that.

There are some pre-reqs for this blog:
1. At least 3 VM's. In my case, I'm using my ESXi 6.7 server at home.
2. Basic knowledge/understanding of what Kubernetes is utilized for.
3. Windows, Mac, or Linux desktop. For this blog, I am using Windows 10.

The first thing you want to do is spin up three virtual machines running Ubuntu18.04. You can use a RHEL based system, but the commands I show and run (including the repos I'm using) will be different.

I have already set up my 3 virtual machines. I gave them static IP addresses as I have found API/configuration issues if the VM shuts do…