WilliamLam.com

Quick Tip - vSphere Permission to view vSphere with Tanzu Namespaces

by // 6 Comments

If you wish to create a custom vSphere Role that has the ability to view vSphere Namespaces which is part of vSphere with Tanzu, you will need to add the user to the following vSphere Single Sign-On Group: ServiceProviderUsers, which is located under Single Sign On->Users and Groups->Groups (2nd page) within the vSphere UI.


Once added, you can logout and log back in and the user should now see the vSphere Namespaces as shown in the screenshot below. In my example, I have a user named william which is created in the default vsphere.local domain and has been assigned the user the vSphere Read Only role along with this additional SSO group. They will be able to view all resources but will not have permission to make any changes to the infrastructure. If you are using Active Directory, the exact same process works and just make sure you log out and log back in for the changes to take effect.

How to modernize your vSphere Alarm actions using the VMware Event Broker Appliance (VEBA)?

by // Leave a Comment

The VMware Event Broker Application/Appliance (VEBA) solution makes it extremely easy for customers to build Event-Driven Automation that can react to over 1800+ vSphere-based Events using your favorite scripting or programming language of choice that includes PowerCLI, PowerShell, Python and Go to just name a few.

The benefits of VEBA can extend beyond just vSphere Events and can also be used with both new and existing vSphere Alarms. In fact, vSphere Alarms is just another a type of vSphere Event, which then makes it super easy to work with if you are already familiar with VEBA. Similar to the "triggers" that are supported with vSphere Events, the available options for extensibility in vCenter Server is super limited.


In addition to the limited options for extending vCenter Server, there are also valid security concerns with resource utilization and opening up access to run arbitrary scripts directly on the VCSA, which we all know is a bad practice for so many reasons. What if we could easily extend the actions to a vSphere Alarm to send notifications to Slack or Microsoft Teams, automatically file an IT Ticket or run specific automation or remediations tasks!?

[Read more...]

AlmaLinux OS 8.4 on ESXi-Arm

by // 2 Comments

I came across this Reddit thread yesterday, announcing the release of AlmaLinux OS 8.4 for Arm and I knew I had to give it a go on ESXi-Arm!

After downloading the ISO, simply create a new Other 4.x Linux VM (1  vCPU/4GB memory) and then boot the ISO to begin the installation. One thing that threw me off the first time I performed the installation was that I forgot to setup networking. It turns out the network interface is actually disabled by default and users must manually toggle the enable button, which I find quite annoying from user experience standpoint. After enabling the networking interface, the rest of the installation went smooth without any issues.


Complete the installation by rebooting and you will now have AlmaLinux OS 8.4 for Arm running on ESXi-Arm 😀


For those interested in setting up Gnome desktop for AlmaLinux, you can follow this tutorial which I used myself.

Note: Thanks to Cyprien, VMware Tools can be installed it looks like an additional repo must be configured by running the following:

dnf config-manager --set-enabled powertools
dnf -y update
dnf install -y git make rpm-build autoconf automake libtool gcc-c++ doxygen fuse-devel gdk-pixbuf2-xlib-devel glib2-devel gtkmm30-devel gtk3-devel libdnet-devel libicu-devel libmspack-devel libtirpc-devel libtool-ltdl-devel libX11-devel libXext-devel libXi-devel libXinerama-devel libXrandr-devel libXrender-devel libXtst-devel openssl-devel pam-devel rpcgen xmlsec1-devel xmlsec1-openssl-devel valgrind-devel libdrm-devel systemd-devel
git clone https://github.com/vmware/open-vm-tools.git
cd open-vm-tools/open-vm-tools/
autoreconf -i
./configure
make
make install

Next, we need to create a new systemd unit file so that we can manage the VMware Tools service, do to so, run the following command:

cat > /etc/systemd/system/vmtoolsd.service << EOF
[Unit]
Description=
Description=Open VM Tools
After=
After=network-online.target

[Service]
ExecStart=
ExecStart=/usr/local/bin/vmtoolsd
Restart=always
RestartSec=1sec

[Install]
WantedBy=multi-user.target
EOF

Finally enable and start the VMware Tools service by running the following command:

systemctl enable vmtoolsd.service
systemctl start vmtoolsd.service