My Smart Home. Step by step from start to… Part 3. Implementation based on Home Assistant. The first steps. Software Add-0n, Configuration File, Update

The Next Step


Greetings to all who read the series of publications “My smart home. From the beginning, step by step to… ”. In a previous article, I described the process of installing Home Assistant and its first settings.

Today we will describe how to add and configure additional software components – File Editor, Terminal. Make the first changes to the main configuration file: configuration.yaml. Let’s update Home Assistant to the current version.

So, let’s move on!

Software add-on: File editor


In Home Assistant, many parameters can be configured through the user interface, but there are enough of them, which are in the .yaml configuration files. So we need a tool to edit them.

You can find and install this official Home Assistant component by selecting the Add-on Store tab in the Supervisor section and entering the word File in the search field:

Figure 1: Search for the Text Editor component in the Supervisor section, Add-on Store tab.

Next, select Install:

Figure 2: Read the description of the component and start the installation.

Next, check the Start on boot option. It must be on. Optionally, we can enable the Show in sidebar option – display the File Editor menu in the Navigator on the left. We start the component:

Figure 3: Set the necessary options and start the component.

If the start is successful, this will be indicated by the corresponding green indicator at the top right. There will also be indicators to monitor the load of this component of the processor and memory:

Figure 4: Checking the successful start of the component.

When the File Editor component is successfully installed, open it via the link in the left navigator. Select the shortcut Browse Filesystem, and open the main configuration file: configuration.yaml:

Figure 5: Open the File Editor.
Figure 6: Open the main configuration file: configuration.yaml.

This file now contains the default settings. There are not many of them. And we will gradually make our parameters there.

Figure 7: Configuration file – configuration.yaml. Default values.

Configuration file: configuration.yaml


Let’s start editing the configuration.yaml file. Enter the following parameters:

homeassistant:
# Name of the location where Home Assistant is running
 name: Elephant Home
# Location required to calculate the time the sun rises and sets
 latitude: 50.724928
 longitude: 30.380581
# Impacts weather/sunrise data (atitude above sea level in meters)
 elevation: 109
# metric for Metric, imperial for Imperial
 unit_system: metric
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
 time_zone: Europe/Kiev

The green indicator indicates no syntax errors. Do not forget to save the configuration through the appropriate graphic menu item:

Figure 8: Enter the following parameters in the configuration.yaml file. Save the file.

After saving successfully, this graphic element will disappear:

Figure 9: Сonfiguration.yaml file saved successfully.

And to apply these added parameters, you must restart the OS Home Assistant. This can be done through the Configuration – Server Controls section:

Figure 10: Configuration and status management section of Home Assistant OS.

Select the Restart option:

Figure 11: Restart OS Home Assistant to work with new parameters.

Communication with Home Assistant will be lost for a while. After restarting and reconnecting to web services, you can perform a small check of the added settings. To do this, go to the Maps section and see the location of your smart home on the map of OpenStreetMap:

Figure 12: Location of your smart home on the map of OpenStreetMap according to the entered parameters.

Software add-on: Terminal


Before proceeding to configure various integrations, we need another software application: a Terminal.

But before you can proceed, you must enable the Advanced Mode in user profile:

Figure 13: Enable the advanced control mode of the Home Assistant OS.

Now, Find and install this official Home Assistant component is similar to how we installed File Editor, only in the search box by entering Terminal:

Figure 14: Search for the Terminal component in the Supervisor section, Add On Store tab.

Additionally, enable the option Auto update. We start a component:

Figure 15: Set the necessary parameters for this component and start it.

Similarly, after starting the component, the CPU and memory monitor indicators will appear:

Figure 16: Checking the successful start of the component.

You can check the operation of the installed application in the Terminal menu:

Figure 17: Terminal functionality in the web interface of Home Assistant OS.

Upgrading Home Assistant components


Some time has passed since the establishment of Home Assistant. Updates to this platform are released regularly. So it’s time to upgrade the system.

The whole sequence of steps can be performed in two ways – through the graphical user interface and through commands in the terminal. I will perform these actions using the console commands of OS Home Assistant.

● ● ●

Step One: System Backup.

To backup the state of the system before performing the update, use the functionality of snapshots.

We open the session of the terminal.

First, let’s learn about the list of existing snapshots:

ha snapshot list

Let’s create a new snapshot:

ha snapshot new --name snapbeforeupdate

Again, ask for a list of snapshots to see its properties:

Figure 18: Request a list of existing snapshots. Creating a new and view its properties.

● ● ●

Step Two: Check the configuration.

For a successful update, it is recommended to check the configuration of the Home Assistant OS:

ha core check
Figure 19: Check the configuration of the Home Assistant OS.

● ● ●

Step Three: Update the Home Assistant OS.

First we learn about the version number of our system:

ha os info
Figure 20: Get version number of our system.

Next, perform the update:

ha os update

After the upgrade, the system will automatically reboot. We will be informed about this by the lost connection:

Figure 21: Succesfully update OS Home Assistant and automatically Reboot system.

After reconnecting, we will receive up-to-date information about the updated version:

Figure 22: View information about the updated version Home Assistant OS.

● ● ●

Step Four: Update Home Assistant Core.

Similar to the previous step, we first learn about the number of our version:

ha core info
Figure 23: Get version number of our system and latest version number of Home Assistant Core.

Next, perform the update:

ha core update

Similarly, after the upgrade, the system will reboot. The connection will be lost for a while. Also, after rebooting, we will be forced to go through the login process again.

Figure 24: Update Home Assistant Core and automatically Reboot system.

After rebooting, run the command again:

ha core info
Figure 25: Get version number of our system Home Assistant Core.

Congratulations! This completes the update to the current version!

What’s next?


So at this point in time we already have the ability to work with configuration files, monitor the work of Home Assistant using commands in the terminal and we have updated the system to the latest version.

At this stage we will pause, and in the next publication we will tell about:

  • Sensors for monitoring system parameters: Raspberry Pi Power Quality and Processor Temperature Control Sensors; Processor, Memory, Disk, Network Monitoring Sensors;
  • Home Assistant Database Size monitoring;
  • Integration: Internet connection monitoring;
  • Add-On and Integration with external devices: Uninterruptible power supply monitoring.

But about this in the next post!

See you,
Sincerely, AIRRA!

Posted in Smart Home, Technology | Tagged , , , , , , , , , , , , , | Leave a comment

My Smart Home. Step by step from start to… Part 2. Implementation based on Home Assistant. The first steps. Software. Basic settings.

The Next Step


Hello everyone who reads the series of publications “My Smart Home. From the beginning, step by step to…”. In the previous story, I described the necessary equipment to start implementation.

Now that all the components have arrived and are available, let’s move on to the software part. So we need any computer with Windows (x86 / x64), macOS, Linux x64 (64-bit) / x86 (32-bit), with the ability to work with an SD Card adapter and Internet access.

Let’s get started!

List of Software


The list for downloading software components is as follows:

Software Component NameFile NameSizeLinks
1.Etcher for Windows (x86|x64) (Installer), v.1.5.121balenaEtcher-Setup-1.5.121.exe140 MB
2.Home Assistant image for Raspberry Pi 4 64-bit, v.5.8hassos_rpi4-5.8.img.xz230 MB

Importantly! Other versions balenaEtcher and Home Assistant image will be required for other hardware platforms.

Figure 1: Select the required balenaEtcher software on the download page.
Figure 2: Select the required Home Assistant OS software on the download page.

Image burning


When all the software is available, you can start writing the image to the SD card. Three small steps.

The procedure is as follows:

  1. Run balenaEtcher. Select the option “Flash from file”:
Figure 3: Step One: Select the option “Flash from file” in balenaEtcher application:
  1. Choose the SD card that we will use to run the Home Assistant OS on the Raspberry Pi 4 platform:
Figure 4: Step Two: Select SD Card in balenaEtcher application.
  1. Select “Flash!” to start recording an image. When balenaEtcher finishes recording the image and checks the result of the recording with the original, we will receive a confirmation:
Figure 5: BalenaEtcher application: Image recording completed successfully!

Start Up Your Raspberry Pi


So the SD card with the image of Home Assistant is ready! The following sequence of steps is as follows:

  • Insert the newly created installation media (SD card) into the Raspberry Pi 4 slot;
  • Connect the Ethernet cable to the network;
  • Connect the power supply;
  • In a few minutes we will be able to access the Home Assistant page at http: //X.X.X.X: 8123, where X.X.X.X is the address that Raspberry Pi received from the DHCP server:
Figure 6: Within a few minutes after starting the Raspberry Pi, we will get access to the OS Home Assistant and then make the first settings.

The first settings


So, Home Assistant OS is installed, it’s time to start setting it up.

At this stage, the web interface Home Assistant itself will offer to configure the basic parameters.

  1. Create a Home Assistant owner account. This account will be an administrator and will always be able to change any settings. Enter the name, username, password:
Figure 7: Create a Home Assistant owner account. Enter the name, username, password.
  1. Specify the name and location parameters of the house, time zone:
Figure 8: Set your location, time zone, and unit system.
  1. If you want to share information with developers about the work of your copy of Home Assistant in terms of analytics, integration, statistics or diagnostic data – select the necessary items:
Figure 9: If want, set sharing information with developers.
  1. The integration setup phase can now be postponed. We will return to this direction later:
Figure 10: List of integrations found by the Home Assistant setup wizard.
  1. Finish, we get the configured start web interface of Home Assistant:
Figure 11: Home Assistant Starting Page.

Congratulations! And this important stage has been successfully completed!

Testing environment


We will need a test site to test the changes that will be made in the productive environment of Home Assistant. It is not necessary to allocate separate equipment for this task, so we will use the virtualization platform for this purpose.

As a cloud architect, I have my own test demo environment. It works on the basis of VMware vSphere 5.x and 6.x. Home Assistant OS can be successfully run in this virtualization platform, although with some features.

Since we will do such actions periodically, I decided to write a small script in Powershell (PowerCli). It is designed to automate the process of creating a test environment Home Assistant in the form of a virtual machine VMware vSphere 5.x, 6.x.

The script consists of 15 steps:

  1. Define variables;
  2. Download HASS OS vmdk.xz;
  3. Extract HASS OS vmdk, rename from .tar, delete .xz;
  4. Connect to VMware Infrastucture;
  5. Set Datastore properties;
  6. Create HASS OS Virtual Machine;
  7. Copy HASS OS vmdk to Virtual Machine Datastore Folder;
  8. Create Configuration Specification HASS OS Virtual Machine;
  9. Check if there is an IDE COntroller present;
  10. Add IDE harddisk to VM configuration;
  11. Set VM EFI firmware;
  12. Reconfigure HASS OS Virtual Machine;
  13. Start HASS OS Virtual Machine;
  14. Get Ip Address HASS OS Virtual Machine;
  15. Open Web Browser and go to Home Assistant Start Web page.

The script code is below:

<#
.SYNOPSIS
    Automate create Home Assistant test Virtual Machine in VMware vSphere.
.DESCRIPTION
    This script is designed to automate the process of creating
    a test environment Home Assistant in the VMware virtual machine.
.NOTES
    File Name      : HassVmwareTestEnv.ps1
    Author         : AIRRA (roman@airra.net)
    Prerequisite   : PowerShell V2 over Vista and upper, 
                     7zip4powershell module,
                     VMware.VimAutomation.Core snap-in.

    Copyright 2021 - AIRRA
.LINK
    Script posted over:
    http://blogs.airra.net
#>

# Step 1: Define variables
$HassVMDKUrl = "https://github.com/home-assistant/operating-system/releases/download/5.8/hassos_ova-5.8.vmdk.xz" # Home Assitant git download Release Path
$HassVMDKDownloadPath = $env:TEMP # Path to download Folder
$HassVMDKArchiveName = "hassos_ova-5.8" # Home Assitant VMDK Archive Name

$VIServer = "_" # Address of VMware Vcenter Server
$VIServerUser = "_" # User with admin permissions
$VIServerUserPassword = "_" # Password

$VIHost = "_" # Address of of VMware Esxi
$VIDatastoreName = "_" # Datasore Name
$VINetwork = "_" # Network Name
$HassVMName = "hassio.test" # Virtual Machine Name

$HassVMDKSourcePath = $env:TEMP
$HassVMDKSourceFile = "hassos.vmdk"
$HassVMDK = $HassVMDKSourcePath + "\" + $HassVMDKSourceFile
$PathDisk = "[" + $VIDatastoreName + "] " + $HassVMName + "/" + $HassVMDKSourceFile

# Step 2: Download HASS OS vmdk.xz.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Invoke-WebRequest -Uri $HassVMDKUrl -OutFile ($HassVMDKDownloadPath + "/" + $HassVMDKArchiveName + ".vmdk.xz")

# Step 3: Extract HASS OS vmdk, rename from .tar, delete .xz.
Expand-7Zip -ArchiveFileName ($HassVMDKDownloadPath + "/" + $HassVMDKArchiveName + ".vmdk.xz") -TargetPath $HassVMDKDownloadPath
Remove-Item -Path ($HassVMDKDownloadPath + "/" + $HassVMDKArchiveName + ".vmdk.xz")
Get-Item -Path ($HassVMDKDownloadPath + "/" + $HassVMDKArchiveName + ".vmdk.tar") | Rename-Item -NewName $HassVMDKSourceFile

# Step 4: Connect to VMware Infrastucture.
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls,[System.Net.SecurityProtocolType]::Tls11,[System.Net.SecurityProtocolType]::Tls12
Connect-VIServer -Server $VIServer -User $VIServerUser -Password $VIServerUserPassword

# Step 5: Set Datastore properties.
$Datastore = Get-Datastore $VIDatastoreName
New-PSDrive -Location $Datastore -Name vids -PSProvider VimDatastore -Root ""
Set-Location vids:

# Step 6: Create HASS OS Virtual Machine.
New-VM -Name $HassVMName -VMHost $VIHost -Datastore $VIDatastoreName -MemoryMB 1024 -NumCPU 1 -DiskMB 1 -NetworkName $VINetwork -GuestID debian6_64Guest
Get-HardDisk -VM $HassVMName -Name 'Hard disk 1' | Remove-HardDisk -Confirm:$false -DeletePermanently:$true

# Step 7: Copy HASS OS vmdk to Virtual Machine Datastore Folder.
Copy-DatastoreItem -Item $HassVMDK -Destination vids:$HassVMName

# Step 8: Create Configuration Specification HASS OS Virtual Machine.
$vm = Get-VM -Name $HassVMName
$spec = New-Object VMware.Vim.VirtualMachineConfigSpec

# Step 9: Check if there is an IDE COntroller present.
$ideCtrl = $vm.ExtensionData.Config.Hardware.Device | where {$_.GetType().Name -eq "VirtualIDEController"} | select -First 1 
if(!$ideCtrl){
    $ctrl = New-Object VMware.Vim.VirtualDeviceConfigSpec
    $ctrl.Operation = "add"
    $ctrl.Device = New-Object VMware.Vim.VirtualIDEController
    $ideKey = -1
    $ctrl.Device.ControllerKey = $ideKey
    $spec.deviceChange += $ctrl
}
else{
    $ideKey = $ideCtrl.Key
}

# Step 10: Add IDE harddisk to VM configuration.
$dev = New-Object VMware.Vim.VirtualDeviceConfigSpec 
$dev.Operation = "add"
$dev.Device = New-Object VMware.Vim.VirtualDisk
$dev.Device.backing = New-Object VMware.Vim.VirtualDiskFlatVer2BackingInfo
$dev.Device.backing.DiskMode = "persistent"
$dev.Device.Backing.FileName = $PathDisk
$dev.Device.ControllerKey = $ideKey
$dev.Device.UnitNumber = -1
$spec.deviceChange += $dev

# Step 11: Set VM EFI firmware.
$spec.Firmware = [VMware.Vim.GuestOsDescriptorFirmwareType]::efi

# Step 12: Reconfigure HASS OS Virtual Machine.
$vm.ExtensionData.ReconfigVM($spec)

# Step 13: Start HASS OS Virtual Machine.
Start-VM -VM $HassVMName

# Step 14: Get Ip Address HASS OS Virtual Machine.
$Ip = (Get-VM -Name $HassVMName).Guest.IpAddress | ?{$_ -notmatch ':'}
Do {
    Start-Sleep -s 10
    }
While ($Ip -eq "" -or $Ip -eq $null)

# Step 15: Open Web Browser and go to Home Assistant Start Web page.
Invoke-Expression "cmd.exe /C start http://$Ip[1]:8123"

Important: The script uses the following components:

  • 7zip4powershell module,
  • VMware.VimAutomation.Core snap-in.

What’s next?


So, at this point we have a deployed and initially set up Home Assistant.

At this stage we will pause, and in the future we will talk about:

  • Software add-on: Text config editor, Terminal;
  • Configuration file: configuration.yaml;
  • Upgrading Home Assistant components to the latest version.

But about this in the next post!

See you,
Sincerely, AIRRA!

Posted in Smart Home, Technology | Tagged , , , , , , , , , , , | Leave a comment

My Smart Home. Step by step from start to… Part 1. Implementation based on Home Assistant. The first steps. Hardware.

Introduction


Congratulations to everyone who periodically reads my blog. This time it will be about my attempt to implement the smart home model.

It all started down to the banal simple, with the purchase of a small townhouse. And while the main construction work was going on, experiments with different platforms of the Smart Home core began in parallel. Among the candidates were Home Assistant, MajorDoMo, OpenHUB and many others. After testing in a virtual environment, there is one candidate left – Home Assistant, about whom I want to tell you. And also about options of its integration with other systems.

This step-by-step review may be useful to some readers, because it will save the most important thing in our lives, it’s time. Much of what will be described was born of many successful and not-so-successful attempts.

So let’s get started!

Hardware


Let’s start with the hardware. At the first stage, the set of devices is not large, so you will fit into the mini budget.

● ● ●

Raspberry Pi 4 Model B

Figure 1: Raspberry Pi 4 Model B appearance.

This is the fourth generation of the main line of minicomputers from the Raspberry Pi Foundation.

Figure 2: Raspberry Pi 4 Model B placement of components and ports.

The technical characteristics of the board are as follows:

  • Processor: Broadcom BCM2711, Quad-core Cortex-A72 (ARM v8), 64-bit, 1.5 GHz core clock speed.
  • Memory: A choice of three hardware implementations – 2GB, 4GB or 8GB LPDDR4-3200 SDRAM.
  • Network: Gigabit Ethernet port, 2.4 GHz and 5.0 GHz IEEE 802.11ac Wireless Adapter, Bluetooth 5.0, BLE.
  • Storage Devices: Micro-SD card slot for booting the operating system and storing data.
  • Ports:
    • Multimedia:
      • 2 micro-HDMI ports (up to 4k resolution and 60p frames per second supported);
      • 2-line MIPI DSI display port;
      • 2-line port of the MIPI CSI camera;
      • 4-pole stereo port and composite video port;
      • Hardware coding of H.265 (4kp60 decoding), H264 (1080p60 decoding, 1080p30 coding);
      • Implementation of OpenGL ES 3.1, Vulkan 1.0 specifications.
    • Input, output:
      • 2 USB 3.0 ports;
      • 2 USB 2.0 ports;
      • Standard 40-pin GPIO Raspberry Pi connector (fully backwards compatible with previous boards).
  • Power:
    • 5V DC via USB-C connector (minimum 3A);
    • 5V DC via GPIO connector (minimum 3A).
  • Dimensions:
    • Height / Width / Depth – 2.22 in (56.5 mm) / 3.37 in (85.6 mm) / 0.43307 in (11 mm).
  • Weight: 1.62 oz (46 g).
Figure 3: Raspberry Pi 4 Model B GPIO Connector Pinout.
Figure 4: Raspberry Pi 4 Model B Physical Specifications.

● ● ●

Power Supply

Figure 5: Official Raspberry Pi USB-C power supply for Raspberry Pi 4 appearance.

Official Raspberry Pi USB-C power supply for Raspberry Pi 4 specifications:

  • The output direct current is 5.1 V / 3.0 A;
  • Operating range of input AC current – 96-264 V;
  • Built-in protection against short circuit, overload and overheating;
  • 1.5 m 18 AWG cable with USB-C output connector.

Subsequently, after the initial start-up and adjustment, this power supply was replaced by Mean Well on a DIN rail 15W 3A 5V HDR-30-5.

Figure 6: Mean Well on a DIN rail 15W 3A 5V HDR-30-5 appearance.

● ● ●

Micro SD Card

You will also need a class SD card no worse than A1 to work as a Home Assistant services.

Figure 7: SanDisk 32 GB microSDHC memory card UHS-I U3 Extreme Pro A1 + SD Adapter Kit appearance.

SanDisk 32 GB microSDHC memory card UHS-I U3 Extreme Pro A1 + SD Adapter specifications:

  • Type – microSDHC;
  • Capacity – 32 GB;
  • Speed class – 10;
  • UHS Class – UHS-I Class 3 (U3);
  • Video recording class – V30;
  • Class for applications – A1;
  • Data read speed – 90 MB / s;
  • Data write speed – 60 MB / s;
  • Adapter included.

● ● ●

Case for Raspberry Pi 4 Model B

In its design of a smart home, it was decided to place its control components as much as possible in electrical switchboards. So we will need a housing for the Raspberry Pi 4 Model B on a DIN rail.

Figure 8: The DIN rail case for Raspberry Pi 4 Model B appearance.

The DIN rail case for Raspberry Pi 4 Model B specifications:

  • Length – 88 mm;
  • Width – 90 mm;
  • Height – 58 mm;
  • The base material is plastic;
  • Material type – Polycarbonate;
  • Color – Gray.

● ● ●

Bill of materials


So the starting list for purchasing components is as follows:

Component NamePart NumberPrice, USD
1.Raspberry Pi 4 Model B, 2Gb~75$
2.Official Raspberry Pi USB-C power supply for Raspberry Pi 4~15$
3.SanDisk 32 GB microSDHC memory card UHS-I U3 Extreme Pro A1 + SD AdapterSDSQXCG-032G-GN6MA~13$
4.The DIN rail case for Raspberry Pi 4 Model B~19$
Total:122$

Prices for components are given in $, based on data from online stores in Kyiv, Ukraine. In your area, they can vary to a greater or lesser extent.

My set of starter components:

Figure 9: Raspberry Pi 4 Model B.
Figure 10: Official Raspberry Pi USB-C power supply for Raspberry Pi 4.
Figure 11: SanDisk 32 GB microSDHC memory card UHS-I U3 Extreme Pro A1 + SD Adapter Kit.
Figure 12: The DIN rail case for Raspberry Pi 4 Model B.

● ● ●

The next step


The components have been ordered and are expected to arrive. So what do we do next? Download the necessary software and start the installation phase.

But about this in the next post!

See you,
Sincerely, AIRRA!

Posted in Smart Home, Technology | Tagged , , , , , , , , , | Leave a comment

VMware vExpert 2021 Award!

Hi to all!

“Hello and welcome to the 2021 vExpert program” – a letter with this message I just received!

More than ten years from the first exam and certificate to this award! Thanks to VMware and everyone who helped me with this. There is still a lot of work ahead!

Sincerely,
Andriy Romanenko

Posted in Technology, VMware | Tagged , , | Leave a comment

VMware Practice. Year 2020. Part 2. Hands-on Labs: Lightning Labs.

Introduction


Hello to all readers of the blog about IT Architecture and Learning!

We recently launched a new series of articles, “Practice VMware. Year 2020.” in which we plan to talk about VMware Hands-on Labs.

As promised, today we will talk about the so-called Lightning Labs.

Let me remind you that Lightning Labs are the fastest and easiest way to test VMware solutions in 30 minutes or less. They help you evaluate the capabilities of VMware products in a short amount of time. Learn about the basic functions of the product!

Let’s take a look at the main Lightning Labs of the 2020 season.

vSphere Labs


● HOL-2011-91-SDC. VMware vSphere – Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Simple & Efficient Management at Scale.
  • Documentation: English [HTML] [PDF]

In this Lab, you will explore vSphere improvements and new features in ESXi and vCenter Server management and lifecycle including, Lifecycle Management, Getting Started with Update Manager, and Operations Enhanced Linked Mode.

● HOL-2013-01-ISM. vSphere 7 with Kubernetes – Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Introduction and Overview of Supervisor clusters;
    • Guest Clusters.
  • Documentation: English [HTML] [PDF]

vSphere 7 with Kubernetes is the new generation of vSphere for modern applications and it is available only through VMware Cloud Foundation. This interactive simulation shows a pre-release version of the product (to be updated later to reflect GA environment) and it will walk you through the steps to enable vSphere with Kubernetes on your VMware Cloud Foundation environment using vCenter Server tools of vSphere. The developers can now consume the newly introduced VMware Cloud Foundation Services that includes Tanzu Kubernetes Grid Service.

● HOL-2010-91-SDC. vSphere Distributed Switch – Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Build, explore, manage a Virtual distributed Switch.
  • Documentation: English [HTML] [PDF]

Explore the features of the vSphere Distributed Switch (vDS) by creating a new vDS and migrating a running virtual machine from an existing vSphere Standard Switch.

● HOL-2047-91-ISM. Using Bitfusion GPU virtualization in vSphere Lightning Lab.

  • Duration: 15 mins.
  • Modules:
    • Using Bitfusion GPU virtualization in vSphere.
  • Documentation: English [HTML] [PDF]

In this lab, you will learn about Bitfusion FlexDirect and how a VM without a GPU can use the GPU on another VM.

● HOL-2048-01-EMT. Launch Your Machine Learning Workloads in Minutes on VMware vSphere.

  • Duration: 15 mins.
  • Modules:
    • Deploy a Machine Learning Workload.
  • Documentation: English [HTML] [PDF]

Machine Learning workloads are becoming pervasive in data centers. VMware vSphere is a great platform for end-to-end machine learning from training to deployment. This lightning lab teaches you how you can launch machine learning workloads on VMware vSphere. TensorFlow is the most popular Machine Learning framework. We will use a community version of docker to launch TensorFlow Container. We explore Neural Network based Text Classification using Internet Movie Database (IMDB). We will build a docker image of a machine learning application and launch it to build, train and evaluate a neural network.

vSAN Labs


● HOL-1908-91-HCI. vSAN 6.7 Lightning Hands-on Lab.

  • Duration: 30 mins.
  • Modules:
    • vSAN 6.7 Lightning Lab.
  • Documentation: English [HTML] [PDF]

Get an introduction to VMware vSAN. We will cover the vSAN features and show you how to enable vSAN using the new vSphere Client (HTML5 UI).

● HOL-2008-91-HCI. vSAN Quick Start – Lightning Lab.

  • Duration: 60 mins.
  • Modules:
    • What’s New with vSAN 6.7 U1;
    • vSAN Sizing.
  • Documentation: English [HTML] [PDF]

Explore how easy it is to deploy vSAN using VMware’s “QuickStart” guided cluster creation wizard! QuickStart provides an easy to use, step-by-step configuration wizard that makes streamlines the creation a production-ready vSAN cluster to support your VMs.

● HOL-2008-92-HCI. vSAN Sizing, Setup and Enablement – Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • vSAN Sizing, Setup and Enablement.
  • Documentation: English [HTML] [PDF]

Get an introduction to VMware vSAN. Learn the vSAN features and how to enable vSAN using the new vSphere Client (HTML5 UI)

NSX Labs


● HOL-1903-99-NET. VMware NSX – Lightning Lab.

  • Duration: 60 mins.
  • Modules:
    • Logical Switching;
    • Logical Switching.
  • Documentation: English [HTML] [PDF]

Explore Module 2 of NSX Data Center, gain insight in to the power of NSX by learning about the NSX Controller cluster, how to create a logical switch and attach virtual machines to this newly created logical switch.

● HOL-2003-91-NET. VMware NSX for vSphere Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Operations and Visibility.
  • Documentation: English [HTML] [PDF]

Come along on a quick tour of some of the tools you can use to gain operational visibility into your NSX for vSphere Infrastructure including Flow Monitoring and Traceflow.

● HOL-2037-91-NET. VMware NSX Advanced Load Balancer (Avi Networks) Lightning Lab.

  • Duration: 45 mins.
  • Modules:
    • Load balancing an Application (Creating a Virtual Service);
    • Scaling Out a Virtual Service;
    • Modifying Application Behavior using Profiles and Policies.
  • Documentation: English [HTML] [PDF]

Introduction to the core capabilities of VMware NSX Advanced Load Balancer (Avi Networks) in a vSphere environment. Gain hands-on experience with Infrastructure and Application components.

NSX-T Labs


● HOL-2026-91-NET. VMware NSX-T Distributed Firewalling Lightning Lab.

  • Duration: 15 mins.
  • Modules:
    • Distributed Firewall and Tools.
  • Documentation: English [HTML] [PDF]

In this Lightning Lab, you will learn how to configure the Distributed Firewall, Spoof Guard, and use various tools within NSX-T.

vRealize Labs


● HOL-2021-91-ISM. vRealize Automation 8 – What’s New – Lightning Lab.

  • Duration: 45 mins.
  • Modules:
    • What’s New in vRealize Automation 8.0.
  • Documentation: English [HTML] [PDF]

vRealize Automation 8.0, a completely new codebase, with new integrations, and many new capabilities. vRealize Automation 8.0 is built on a modern container-based microservices architecture, with improved scalability and performance. In this lab you will work with blueprints to deploy workloads and learn how this is done across a multi-cloud environment. Deployment and management of application and infrastructure resources across a VMware Software Defined Datacenter and public cloud services has never been this comprehensive or straightforward.

● HOL-2001-91-ISM. vRealize Operations 8 – What’s New – Lightning Lab.

  • Duration: 45 mins.
  • Modules:
    • Highlights of What’s New in vRealize Operations 8.0;
    • What’s New with Troubleshooting in vRealize Operations 8.0;
    • What’s New with Capacity and Costing in vRealize Operations 8.0.
  • Documentation: English [HTML] [PDF]

In 30 minutes or less explore what’s new in the latest version of vRealize Operations Manager with this interactive demo.

● HOL-2002-92-CMP. A Quick Introduction to VMware Network Insight – Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • A Quick Introduction to vRealize Network Insight.
  • Documentation: English [HTML] [PDF]

Quickly learn the most important features of vRealize Network Insight. If you’re interested in application security, troubleshooting physical network devices, managing and securing networks in the private and public clouds then this lab is for you.

vCloud Director Labs


● HOL-2083-91-HBD. VMware vCloud Director Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • vCloud Director – A User Perspective.
  • Documentation: English [HTML] [PDF]

Brief exploration of vCloud Director 9.7 multi-tenancy features including using the Tenant UI for consumption of vCloud Director services.

Horizon Labs


● HOL-1951-92-VWS. Horizon 7 Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Horizon Components and Architecture.
  • Documentation: English [HTML] [PDF]

Get an introduction to Horizon with user environment manager and App Volumes.

● HOL-2051-91-VWS. VMware Horizon 7 Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Create a Desktop Pool.
  • Documentation: English [HTML] [PDF]

See how quick and easy it is to create and entitle a Horizon Desktop Pool in this Lightning Lab.

Workspace ONE Labs


● HOL-1951-91-VWS. Workspace ONE Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Advanced Integration.
  • Documentation: English [HTML] [PDF]

You will explore Workspace ONE integration with SaaS applications and Workspace ONE Unified Endpoint Management.

Cloud Solutions Labs


● HOL-1984-01-HBD. CloudHealth – Getting Started.

  • Duration: 60 mins.
  • Modules:
    • Navigation and Dashboards;
    • Pulse Reports;
    • Reporting Basics.
  • Documentation: English [HTML] [PDF]

This lab will show you how to navigate through the platform to learn about the key areas of functionality and how they will benefit you. It also highlights the power of CloudHealth’s reporting and walks through creating customized reports.

● HOL-1987-91-HBD. VMware on AWS Lightning Hands-on Lab.

  • Duration: 30 mins.
  • Modules:
    • Deploying a SDDC.
  • Documentation: English [HTML] [PDF]

In this Lab, with the HTML5 user interface, deploy and configure SDDCs on VMware Cloud on AWS.

● HOL-2014-01-ISM. VMware Cloud on Dell EMC – Lightning Lab.

  • Duration: 30 mins.
  • Modules:
    • Order & Configure VMware Cloud on Dell EMC.
  • Documentation: English [HTML] [PDF]

Walk through the process of ordering a VMware Cloud on Dell EMC SDDC, configuring uplinks to connect to the data center networks through the included top-of-rack switches, enabling access to the SDDC vCenter, configuring workload networks, deploying VMs to the SDDC and protecting those workloads with Distributed Firewall.

● HOL-2015-91-SDC. VMware Skyline Lightning Lab.

  • Duration: 15 mins.
  • Modules:
    • Immediate Results with Proactive Findings.
  • Documentation: English [HTML] [PDF]

In this lab, we highlight one of the key capabilities of VMware Skyline, the Proactive Findings feature. You will explore the various findings identified by Skyline for all monitored environments along with the details of each.

● HOL-2040-91-NET. Getting Started with VeloCloud Lightning Lab.

  • Duration: 15 mins.
  • Modules:
    • Features and Product Tour.
  • Documentation: English [HTML] [PDF]

Brief exploration of VMware SD-WAN by VeloCloud including the key components and architecture in a simulated product tour.

● HOL-2087-91-HBD. VMware Cloud on AWS Lightning Lab.

  • Duration: 15 mins.
  • Modules:
    • VMware Cloud on AWS Lightning Lab.
  • Documentation: English [HTML] [PDF]

Walkthrough of setting up a native AWS VPC and subnets to connect to VMware Cloud on AWS Software Defined Datacenter (SDDC). Also, deploy a 3-host SDDC, add users to the SDDC and scale up the SDDC to 4 hosts.

Brief Summary


So, from this post, you learned about VMware’s “Lightning” Hands-on Labs, 2020 season. Let me remind you that this resource is absolutely free, and only a modern browser is required for access, so I advise you to add the address of the resource to the bookmarks “VMware Hands-on Labs”, quickly register and start mastering VMware technologies with “Lightning” Hands-on Labs.

In the next publication we will talk about the main laboratory work in the areas of Comprehensive Hands-on Labs to deepen knowledge.

Follow the news until the meeting is on air in a few days.
Sincerely, AIRRA.

Posted in Education, Practice, Technology, Training, Virtualization, VMware | Tagged , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | Leave a comment