Educational Episodes: Hyperconverged Infrastructure (HCI)

Today we will look at one of them – Challenge Handshake Authentication Protocol or CHAP. Before we start, let me tell you a few words about CHAP. Challenge Handshake Authentication Protocol (CHAP) is a network login protocol that uses a challenge-response mechanism. You can use CHAP authentication to restrict iSCSI access to volumes and snapshots to hosts that supply the correct account name and password (or “secret”) combination. Using CHAP authentication can facilitate management of access controls because it restricts the access through account names and passwords, instead of IP addresses or iSCSI initiator names.

Talking about SQL Server 2016 features, it won’t be fair to leave Always Encrypted aside. This feature prevents your sensitive data from leaking out and enables to get more freedom for your data placement choices. Always Encrypted comes in handy, when, let’s say, you hire external vendors to administer your SQL server and do not want them to see your sensitive data, or when both your client and data are hosted in Azure. So, if you still do not use it, that’s high time to start! Read the full article by Mikhail Rodionov to learn more about SQL Server Always Encrypted benefits and why and when you need it.

Some month ago, Microsoft released a new Azure feature allowing to deploy service catalogs right in the public cloud. What is that thing for? To make teamwork in Azure a breath! Now, thanks to prebuilt templates and controlled parameters, your teams can deploy web apps or VMs so that they won’t break your budget (if you set everything right, of course). Learn how to deploy service catalogs in Azure in the full article by Florent Appointaire.

Microsoft Flow is a handy tool to create automated workflows between your favorite apps and services. It allows you to collect data, sync files, and automate all that boring jobs related to, let’s say, sending emails once a tweet with a buzzword is posted. Find out how to set Microsoft Flow in the full article by Florent Appointaire.

Let’s be honest, any system administrator may face the need of hot-adding the network interfaces to the guest VMs in his Microsoft Hyper-V environment one day. And that’s no problem as Windows Server 2016 brought in a whole set of useful features, one of which is the ability to add and remove network adapters on the running VMs. Moreover, you can do that in two ways – GUI, if you’re looking for a straightforward process and PowerShell if you are a fan of automation.

Today, I’ll talk about a thing that any sysadmin running Hyper-V VMs does (or still dreams about) while managing infrastructure resources: hot modifying assigned to VM memory amount. I’ll discuss not only the feature itself but also how it works on different OS and its impact on the environment stability. All of us keep an eye on resource consumption within our environments. If a VM needs extra RAM to have the job done, we provide it with some, right? And, we usually run many VMs on our servers each with own purpose and configuration. That’s, actually, why changing the amount of assigned to a VM memory without rebooting it may come in handy. Also, many guys run some parts of their environments on Windows while having other parts run on something from Linux family. Looks pretty hectic in terms of management, doesn’t it?

These days, businesses do not stick to one location anymore. Such trend pushes companies to build stretched clusters, IT infrastructures spanned across several locations. Such approach enables them to implement better disaster recovery strategies and achieve higher performance. To build such environments, you need fast connection and the solution to use resources of all your remote sites just as they were located in one place. Here, VSAN from StarWind comes into play – the solution for building high performing active-active replicated shared storage.

One day, any virtual infrastructure needs to be updated. That may be just due to admin’s wish to keep up with modern trends or the need for some cool features that are brought to life with the latest updates. And, speaking of updates, VMware has recently released their vSphere 6.5 U2. Find out more details about it in this document: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-feature-comparison-datasheet.pdf So, being a VMware fan, I decided to update my vSphere 6.5 and describe the entire update process from its planning through the installation itself.

In today’s topic, I’d like to talk about the Meltdown and Spectre vulnerabilities. But not about the harm they cause, this has been covered widely in numerous articles, but how Microsoft patches intended to protect you from the vulnerabilities, affect (if they do) the hardware performance. Before we take a deep dive into the tests and numbers, let me tell a few words about Meltdown and Spectre and outline the testing scope to make sure we speak one language.