Educational Episodes: Hyperconverged Infrastructure (HCI)

This series of articles will guide you through the basic deployment of Microsoft Windows Server 2016 Core version, covering all the steps from an initial installation to the deployment of Hyper-V role and Failover Cluster configuration. The first and the main thing you need to double-check before installing the Windows Server 2016 Core is whether your hardware meets the system requirements of WS 2016. This also is very important in the process of planning your environment, in order to be sure that you have enough amount of compute resources for running your production workload.

Orchestrator is a workflow management solution for the data center. Orchestrator lets you automate the creation, monitoring, and deployment of resources in your environment. Orchestrator is also known as “SCORCH” or “SCO”. Orchestrator uses a drag and drop graphical interface to allow admins to define runbooks. A runbook is a compilation of routine procedures and operations that Orchestrator will run depending on your scheduling. Finally, Orchestrator is capable of managing multiple operating systems. After reading this guide, you should have a basic understanding of how to upgrade/install Orchestrator.

I recently looking for Azure Automation, from top to bottom. It’s why, in the next 2 articles, we will see how to use this tool, from A to Z: [Azure Automation] Interface discovery – Part 1 (this post) [Azure Automation] Migrate your scripts to Azure – Part 2 Start with the first article.

Very often, VMware vSphere administrators have to find the reasons of performance issues by analyzing the historical data of various metrics on the VMware vCenter Server. However, sometimes the default set of metrics is not enough if you view performance data for the previous night or the end of the past week – in this case, you need to change the level of collected metrics and, possibly, the frequency of their collection and retention. In the VMware vCenter Server settings, you can set the data collection levels, different collection intervals and the time period that the data will be stored on the Server. In addition, you can set an approximate size of the virtual infrastructure in the host servers and virtual machines, which will allow to roughly estimate the size of the vCenter database. Let’s take a closer look at these settings.

As we referenced several times, security is one of the main topics for cloud providers looking to guarantee privacy for their customers’ data and information. Microsoft just announced the public availability for Storage Service Encryption (SSE) for Azure Managed Disks, with no additional cost.

VMDK file to LUN storage architecture has been the most usable scenario for years until VMware released Virtual Volumes in vSphere 6.0. In the case of an array with block access, own VMware file system – VMFS  – was used -, and NFS was used for file storage. The array capacity was divided into LUNs or NFS-shares and presented ESXi hosts in the datastore form. Frequently, datastore is a large capacity storage housing numerous VMs. In fact, allocating a separate datastore for each VM is quite inconvenient and time-consuming in terms of administration.

Many IT administrators or virtualization guys run their homelabs at home. It is a good way to learn new technologies, be able to break things in a lab to get stronger skills. It is sometimes a challenge, to squeeze as much RAM as possible from it. The main challenge is always a memory utilization. VMware VMs are getting memory hungry all the time and they are not “optimized” for Homelab use, but rather for production environments. Yes, it is the main purpose of those VMs after all.

The fast-paced world of system administration is growing on a large scale and picking up steam all the time. The migration of business to the cloud we can see these days is a good example of the above said. Thus, the continuous pursuit of a tool that would simplify the life of a system administrator constantly stays on the agenda of the IT world. The main goal behind the development of the Storage Management Initiative (SMI) is eliminating the long journey of finding the right solution. To simplify the life of system administrators to an even greater extent, the StarWind team has decided to additionally complete the feature set by developing the StarWind Swordfish Provider.

We all already know the two biggest Public Cloud providers are Amazon Web Services (AWS) and Microsoft Azure and, unless a catastrophic event occurs, these two will be leading the market in the next couple of years. A recent study between 550 companies showed some interesting results: AWS is the most preferred vendor in SMBs; Microsoft the “most known” in enterprises; AWS has been reviewed the most between all companies but Azure is the most used.