—

As you may have noticed, our blog has undergone a recent transformation with a new UI theme based on the Clarity Design System. This change was motivated by the latest version of vCenter, which now uses HTML5 and offers a more modern and user-friendly interface. We wanted to keep up with the times and provide our readers with an equally enjoyable and accessible experience.

Clarity UI is an open-source design system initiated by VMware, which combines UX guidelines, HTML/CSS framework, and Angular components to create responsive and modern web interfaces. The best part is that it’s free to use and has a wealth of documentation available to help you get started.

One of the key reasons we chose Clarity UI is its focus on accessibility best practices. As a blog focused on cloud computing, virtualization, and infrastructure-as-code, we want to make sure that our content is accessible to all readers, regardless of their abilities or devices. Clarity UI’s emphasis on accessibility helps us achieve this goal.

Another reason we chose Clarity UI is its modern and responsive design. The new UI theme is designed to work seamlessly across different devices and screen sizes, ensuring that our readers can access our content regardless of the device they use. This is especially important for our mobile readers, who can now enjoy a more streamlined and user-friendly experience.

The transition to Clarity UI was not without its challenges, but we were able to overcome them thanks to the excellent documentation available from VMware. The reference guides for all available components made it easy for us to find what we needed and integrate it into our blog. We also want to give a special mention to @codyde’s post blog Redesigning My Blog With ClarityUI, which provided valuable insights and tips for implementing Clarity UI.

We hope that you enjoy the new look and feel of our blog as much as we do. We are committed to providing our readers with the best possible experience, and we believe that Clarity UI is a key part of achieving that goal. As always, we appreciate your feedback and suggestions for how we can continue to improve. Thank you for reading!

Cloud Computing: Understanding the Basics

Cloud computing has become a hot topic in the IT industry today. More and more businesses are moving their operations to the cloud, and as a result, there is a growing demand for professionals who understand how to implement the benefits of the public, private, and hybrid clouds. In this blog post, we will take a closer look at what cloud computing is, how it works, and what it does.

Defining Cloud Computing

Cloud computing is a model for delivering computing resources over the internet. Instead of storing data and applications on local servers, the cloud allows businesses to access these resources remotely through a network of servers. This means that companies can scale up or down their resources as needed, without having to worry about managing hardware and software updates.

How Does Cloud Computing Work?

Cloud computing works by using a combination of virtualization and distributed computing. Virtualization allows multiple operating systems and applications to run on a single physical server, while distributed computing enables the sharing of resources among multiple servers. This means that companies can access vast amounts of computing power and storage without having to invest in expensive hardware and software.

What Does Cloud Computing Do?

Cloud computing provides a range of benefits for businesses, including:

1. Scalability: Cloud computing allows companies to scale up or down their resources as needed, without having to worry about managing hardware and software updates.

2. Cost-effectiveness: By using the cloud, businesses can reduce their IT costs by avoiding the need for expensive hardware and software purchases.

3. Flexibility: Cloud computing provides a range of deployment options, including public, private, and hybrid clouds, allowing companies to choose the best fit for their needs.

4. Reliability: Cloud providers offer high levels of reliability and uptime, ensuring that businesses can access their data and applications whenever they need them.

5. Security: Cloud providers offer robust security measures to protect customer data and applications from unauthorized access and malicious attacks.

Conclusion

Cloud computing is a rapidly emerging field with a growing demand for professionals who understand how to implement the benefits of the public, private, and hybrid clouds. By understanding what cloud computing is, how it works, and what it does, businesses can make informed decisions about adopting cloud-based solutions that meet their specific needs. Whether you’re looking to boost scalability, reduce costs, or improve flexibility, the cloud has something to offer.

VMware vRealize Automation 8.6: Simplifying Cloud Management with ABX-Based Custom Resources

VMware has recently announced the upcoming release of VMware vRealize Automation 8.6, which introduces several enhancements and new features to streamline cloud management. One of the most significant additions is the ability to create and manage Custom Resources based on ABX actions. This feature allows for more flexibility in defining dynamic input fields within Cloud Templates and reusing them across multiple Property Groups.

In this blog post, we will delve into the new ABX-based Custom Resources capability and explore how it can simplify cloud management. We will also discuss how this feature can be used to execute Code Stream workspaces within Kubernetes environments, providing customers with more options for executing continuous integration pipeline containers.

ABX-Based Custom Resources: An Overview

With vRealize Automation 8.6, VMware is introducing the ability to create and manage Custom Resources based on ABX actions. This new capability allows you to define dynamic input fields within your Cloud Templates by directly interfacing with vRealize Orchestrator Actions. Previously, this could be accomplished by defining custom forms within Service Broker, but now the capability is integrated directly within Cloud Assembly.

The ABX-based Custom Resources include a Read operation, which replaces the functionality previously provided by the vRealize Orchestrator Dynamic Types. This means that you can pass local inputs as parameters into the vRealize Orchestrator Action, providing more flexibility in defining dynamic input fields within Cloud Templates.

Using ABX-Based Custom Resources: A Data Management Tanzu Use Case

One of the most significant benefits of the new ABX-based Custom Resources is their ability to simplify data management. With vRealize Automation 8.6, you can now define dynamic input fields within your Cloud Templates that are based on ABX actions. This allows you to pass local inputs as parameters into the vRealize Orchestrator Action, making it easier to manage your data.

For example, let’s say you have a Cloud Template that requires a parameter to be passed in from an external source. With the new ABX-based Custom Resources, you can now define this parameter as a dynamic input field within the Cloud Template. This allows you to easily pass the parameter into the vRealize Orchestrator Action, simplifying your data management processes.

Executing Code Stream Workspaces within Kubernetes Environments

Another significant addition in vRealize Automation 8.6 is the ability to execute Code Stream workspaces within Kubernetes environments. Previously, customers were required to use a standalone Docker host to execute continuous integration pipeline containers. However, this requirement was not well-liked by customers, and many requested that they be able to utilize existing Kubernetes environments to execute these pipeline containers.

With the new feature in vRealize Automation 8.6, customers can now execute Code Stream workspaces within Kubernetes. This works similarly to how the Docker capability worked, but with a few key differences. For example, you will define a Namespace where the container images will execute, whether to utilize a node port or a load balancer proxy to access this as well as persistent volume claims for data persistence.

Conclusion

VMware vRealize Automation 8.6 is a significant update that introduces several enhancements and new features to simplify cloud management. The ability to create and manage Custom Resources based on ABX actions is one of the most notable additions, providing more flexibility in defining dynamic input fields within Cloud Templates and reusing them across multiple Property Groups. Additionally, the ability to execute Code Stream workspaces within Kubernetes environments gives customers more options for executing continuous integration pipeline containers.

Overall, vRealize Automation 8.6 is a powerful tool that can help organizations streamline their cloud management processes and improve their data management capabilities. We recommend exploring these new features and seeing how they can benefit your organization.

The article discusses the current state of container operating systems and the growing trend of using containers in enterprise environments. The author highlights the benefits of using containers, such as improved portability, faster deployment, and better resource utilization. The article also mentions several popular container operating systems, including CoreOS, Photon, RHCOS, RancherOS, and Ubuntu Core.

The author notes that while these container operating systems have many features in common, they also have some key differences. For example, CoreOS and RHCOS are based on Linux, while Photon is based on FreeBSD. Additionally, RancherOS is designed specifically for Kubernetes environments, while Ubuntu Core is focused on providing a secure and reliable platform for cloud-native applications.

The article also touches on the topic of containerization in the enterprise, highlighting the challenges that IT teams face when adopting containers. These challenges include managing and orchestrating containers at scale, ensuring compatibility with existing infrastructure and tools, and providing adequate security and networking features.

Overall, the article provides a comprehensive overview of the current state of container operating systems and their growing adoption in enterprise environments. It highlights the key features and differences between popular container operating systems, and provides insights into the challenges and opportunities of containerization in the enterprise.

Replacing Certificates in a VMware vCloud Director Deployment

In a VMware vCloud Director deployment, it is essential to ensure that the certificates used for authentication and encryption are up-to-date and valid. This guide provides a step-by-step procedure for replacing the certificates of a single cell deployment, with modifications for multi-cell deployments. Please note that this procedure should only be performed by authorized personnel and with proper testing to ensure minimal downtime and disruption to the deployment.

Step 1: Backup the Existing Certificates

Before replacing the certificates, it is crucial to backup the existing ones to avoid any issues during the transition. You can use the following command to backup the certificates:

“`

vcloud-cmd –cell backup-certificate

“`

Step 2: Create a New Certificate Signing Request (CSR)

To create a new CSR, you will need to generate a new private key and certificate signing request file. You can use the following command to generate a new CSR:

“`

openssl req -x509 -newkey rsa:2048 -nodes -keyout cert.key -out cert.csr -subj “/CN=“

“`

Replace `` with the name of your cell. The generated CSR file will be located in the `cert.csr` file, and the private key will be located in the `cert.key` file.

Step 3: Send the CSR to Your CA for Signing

Once you have created the CSR, you need to send it to your Certificate Authority (CA) for signing. You can use the following command to send the CSR to your CA:

“`

openssl x509 -inform der -in cert.csr -out cert.pem -days 365 -CA ca.crt -CAkey ca.key -set_serial 1234567890

“`

Replace `ca.crt` and `ca.key` with the paths to your CA’s certificate and private key files, respectively. The `set_serial` option sets the serial number of the certificate to `1234567890`.

Step 4: Copy the Signed Certificate to Each Cell

Once your CA has signed the CSR, you need to copy the signed certificate to each cell in your deployment. You can use the following command to copy the signed certificate to a specific cell:

“`

vcloud-cmd –cell update-certificate cert.pem

“`

Replace `` with the name of the cell you want to update. The `update-certificate` command updates the certificate for the specified cell.

Step 5: Update the vCloud Director Configuration

After copying the signed certificate to each cell, you need to update the vCloud Director configuration to use the new certificates. You can use the following command to update the vCloud Director configuration:

“`

vcloud-cmd –config update-certificate

“`

This command updates the vCloud Director configuration to use the new certificates.

Step 6: Test the Certificates

After updating the vCloud Director configuration, you need to test the certificates to ensure that they are working correctly. You can use the following command to test the certificates:

“`

vcloud-cmd –cell certificate-test

“`

Replace `` with the name of the cell you want to test. The `certificate-test` command tests the certificates for the specified cell.

Multi-Cell Deployments

If you are using a multi-cell deployment, you need to extend the information in the `-ext “san=dns:…”` parameter of the certificate creation to include each cell DNS and IP, as well as the VIP FQDN at least. This ensures that the certificates are valid for all cells in the deployment.

Conclusion

In conclusion, replacing the certificates in a VMware vCloud Director deployment is a critical task that should be performed regularly to ensure the security and integrity of your deployment. By following the steps outlined in this guide, you can replace the certificates with minimal downtime and disruption to your deployment. Additionally, if you are using a multi-cell deployment, you need to extend the information in the `-ext “san=dns:…”` parameter of the certificate creation to include each cell DNS and IP, as well as the VIP FQDN at least.

The Evolution of Virtualization: vChat Episode 30 Recap

In the latest installment of vChat, Simon Seagrave, Eric Siebert, and I discussed some of the hottest topics in the virtualization world, including the London 2012 Olympics XXX, home lab upgrades, new TrainSignal courses, and plans for VMworld. As always, we had a blast discussing these topics and sharing our insights with the community.

First up, we talked about the London 2012 Olympics XXX and how it’s using virtualization to deliver a more efficient and cost-effective infrastructure. We discussed how virtualization is becoming increasingly popular in large-scale events like the Olympics, and how it can help organizations deliver more with less.

Next, we moved on to home lab upgrades and shared our thoughts on the best ways to upgrade your home lab. We talked about the importance of keeping your home lab current and how upgrading your hardware and software can help you stay ahead of the curve.

We also discussed some exciting new TrainSignal courses that are coming soon, including a course on VMware vSphere 5.1 and another on Windows Server 2012. These courses will help you learn the latest and greatest in virtualization and Windows server administration, so be sure to check them out.

Finally, we talked about our plans for VMworld, which is just around the corner. We shared our thoughts on some of the sessions we’re looking forward to attending, and how we’re planning to use the event as an opportunity to connect with other virtualization professionals and learn more about the latest trends and technologies in the industry.

As always, vChat was a blast and we had a great time discussing these topics with our audience. If you missed the live broadcast, be sure to check out the recording on YouTube or iTunes. And don’t forget to subscribe to our channel so you can stay up-to-date on all the latest virtualization news and trends.

Thanks for watching, and we’ll see you in the next vChat!

VMware’s vRealize True Visibility Suite: Enhancing Physical Infrastructure Monitoring

In its continued effort to provide customers with a comprehensive and integrated monitoring solution, VMware has announced an upcoming change in the licensing model for its vRealize True Visibility Suite. With this update, all vRealize Operations customers will be entitled to access the compute and storage management packs within the suite, without the need for an additional license key.

The included management packs will support monitoring of various compute and storage platforms such as Cohesity, Dell EMC Isilon, Dell EMC PowerMax & VMAX, Dell EMC VNX, Dell EMC XtremIO, HPE 3PAR StoreServ, HPE Nimble, IBM SVC & Storwize, NetApp E-Series, NetApp FAS/AFF, NetApp SolidFire, and Pure Storage FlashArray. These relationship-aware, agentless management packs will provide customers with the visibility they need into their physical infrastructure, enabling them to optimize performance and eliminate bottlenecks.

The new management packs will offer hundreds of key performance metrics for physical compute and storage, providing a deeper insight into the environment. This will enable customers to perform rapid root cause analysis, clear up alert storms with built-in policies, and deliver more value with a unified view from data center to applications.

With this update, vRealize True Visibility Suite will offer a comprehensive monitoring solution that covers both virtual and physical infrastructure. This integration will provide customers with a cohesive monitoring strategy, enabling them to monitor their entire IT environment from a single pane of glass.

The upcoming release of vRealize True Visibility Suite is expected to become generally available soon. Customers can access the management packs by visiting the Customer Connect portal and looking for the vRealize Operations Management Packs for Compute and Storage. For more information on this update, please check out the links provided below:

* vRealize True Visibility Suite Product Page

* What’s New in vRealize True Visibility

* What’s New in vRealize Operations 8.6

Search for related posts and articles to stay up-to-date with the latest developments in the world of IT monitoring and management. Follow us for timely updates and insights into the industry.

Upgrading to vRealize Automation 8.4.2: What You Need to Know

VMware has recently released vRealize Automation 8.4.2, a second minor update to the vRealize Automation 8.4 platform. This release includes several updates and bug fixes, but there is also a known issue that you should be aware of before upgrading. In this blog post, we’ll take a closer look at the new features and the known issue, as well as provide some guidance on how to resolve it.

New Features in vRealize Automation 8.4.2

—————————————–

vRealize Automation 8.4.2 introduces several new features, including:

* Installation/upgrades to vRealize Automation 8.4.2 require that you first deploy or upgrade vRealize Suite Lifecycle Manager to vRealize Suite Lifecycle Manager 8.4.1 Patch 1.

* This update to vRealize Suite Lifecycle Manager includes the following features and fixes:

+ API changes with apiVersion=2021-06-22.

+ Support for using a custom certificate for the vRealize Automation server.

+ Improved support for managing large numbers of virtual machines.

+ Several bug fixes and other improvements.

Known Issue in vRealize Automation 8.4.2

—————————————–

There is a known issue with upgrading to vRealize Automation 8.4.2. In the previous vRealize Automation 8.4.1 release, VMware made a change to the user permissions within vRealize Automation regarding the Migration Assistant service. Previously, Migration Assistant had its own service permissions, but in 8.4.1 these permissions were migrated into the Cloud Assembly service permissions. After upgrading to 8.4.1, a user would receive a “403 Forbidden” message when attempting to access the migration assistant. While the Migration Assistant service was still listed as a service that could be assigned to a user, assigning these service permissions had no effect.

To resolve the “403 Forbidden” error, the user’s permissions needed to be updated to include the permissions listed under the Cloud Assembly Service. However, in vRealize Automation 8.4.2, the Migration Assistant service was removed from the available services to be assigned to a user under Identity & Access Management. VMware did not take this change into account during the upgrade process to 8.4.2, which can result in an “403 Forbidden” error when attempting to access the migration assistant.

Workaround for the Known Issue

——————————-

To avoid the known issue with upgrading to vRealize Automation 8.4.2, you should ensure that no user is assigned these legacy Migration Assistant service permissions prior to starting the vRealize Automation 8.4.2 upgrade. If a user is still assigned these legacy permissions, the upgrade process will fail to initialize the pods after the virtual appliances reboot.

To resolve the issue, you can follow these steps:

1. Before upgrading to vRealize Automation 8.4.2, ensure that no user is assigned the legacy Migration Assistant service permissions.

2. If any users are still assigned these permissions, remove them prior to starting the upgrade process.

3. Once all users have been updated, you can begin the vRealize Automation 8.4.2 upgrade process.

Conclusion

———-

vRealize Automation 8.4.2 includes several new features and bug fixes, but there is also a known issue that you should be aware of before upgrading. To avoid this issue, ensure that no user is assigned legacy Migration Assistant service permissions prior to starting the upgrade process. By following these steps, you can successfully upgrade to vRealize Automation 8.4.2 and take advantage of the new features and improvements it offers.

VMware’s Photon OS: A Lightweight Container Operating System for the Cloud

In recent years, containerization has become a popular trend in the software industry, and Docker has emerged as one of the leading container runtimes. However, running containers on bare metal or virtual machines can be complex and require a lot of manual configuration. This is where Photon OS comes in, a lightweight container operating system developed by VMware that simplifies the process of deploying and managing containerized applications.

What is Photon OS?

Photon OS is an open-source, Linux-based operating system designed specifically for running containers. It is built on top of the Linux 4.19 kernel and uses the dnf package manager instead of yum or apt. The core idea behind Photon OS is to provide a lightweight, streamlined environment for containerized applications, eliminating unnecessary software and features that are not commonly used in containerized environments.

Photon OS 3.0: The Latest Version

The latest version of Photon OS is 3.0, which was released in October 2022. This version includes several new features and improvements over the previous version, including:

1. Improved Security: Photon OS 3.0 includes several security enhancements, such as improved SELinux policies and increased strictness for Docker permissions.

2. Enhanced Networking: The latest version of Photon OS includes improved networking capabilities, such as better support for IPv6 and the ability to configure the hostname and DNS settings.

3. Simplified Management: Photon OS 3.0 introduces a new command-line interface (CLI) called pmd-cli, which simplifies management tasks such as installing and updating software packages.

4. Better Support for Containers: The latest version of Photon OS includes improved support for Docker containers, including better resource isolation and improved networking.

How to Get Started with Photon OS?

If you’re interested in trying out Photon OS, there are several ways to get started:

1. Download the ISO: You can download the latest ISO file from the VMware Photon OS GitHub repository.

2. Install with dnf: Use the dnf package manager to install Photon OS on your system.

3. Run as a Container: You can also run Photon OS as a container using Docker.

Tips and Tricks for Using Photon OS

Here are some tips and tricks for getting the most out of Photon OS:

1. Use the pmd-cli: The new CLI included in Photon OS 3.0 is a great way to simplify management tasks such as installing and updating software packages.

2. Take Advantage of Containers: Photon OS is designed specifically for running containers, so take advantage of this by using containers for your applications.

3. Customize the System: Photon OS is highly customizable, so feel free to modify the system to suit your needs.

4. Stay Up-to-Date: Photon OS is actively developed, so be sure to stay up-to-date with the latest versions and releases.

Conclusion

Photon OS is a lightweight, open-source container operating system designed specifically for running containers in cloud environments. The latest version, 3.0, includes several new features and improvements over the previous version. Whether you’re looking to simplify your container management or just want a lightweight, streamlined operating system, Photon OS is definitely worth checking out.

As a DevOps engineer, I understand the importance of containerization and its impact on modern software development. In this blog post, I will be discussing the installation and configuration of Harbor, an open-source container registry, on a VMware infrastructure.

Before we dive into the installation process, let me give you a brief overview of what Harbor is and why it’s important. Harbor is an open-source container registry that provides a secure and scalable platform for managing container images. It supports a wide range of container runtimes, including Docker and rkt.

Now, let’s get started with the installation process. The first step is to download the Harbor installer from the official website. Once you have downloaded the installer, run it and follow the on-screen instructions to complete the installation.

After the installation is complete, you need to configure Harbor by editing the `harbor.yml` file in the install directory. This file contains all the configuration settings for Harbor, including the database connection information, authentication settings, and more.

Here are some of the key configuration options you will need to set:

* Database connection information (e.g., host, port, username, password)

* Authentication settings (e.g., enabled, type, realm, config)

* Server settings (e.g., listen address, listen port)

* Registry settings (e.g., repository format, storage driver)

Once you have configured Harbor, you can start using it to manage your container images. To do this, you will need to create a new registry and then upload your images to it.

Here are the basic steps for creating a new registry and uploading an image:

1. Log in to the Harbor web interface using your chosen authentication method (e.g., username and password).

2. Click on the “Registry” tab in the top menu bar.

3. Click on the “Create New Registry” button.

4. Enter a name for your new registry and select a location for the images to be stored.

5. Choose the appropriate storage driver for your registry (e.g., Docker, rkt).

6. Optionally, you can configure additional settings for your registry, such as authentication or server settings.

7. Click “Create Registry” to create the new registry.

8. Once the registry is created, you can upload images to it using the “Upload Image” button.

That’s it! With these basic steps, you should now be able to use Harbor to manage your container images on a VMware infrastructure. Of course, there are many more advanced features and configuration options available in Harbor, but this should give you a good starting point.

In conclusion, Harbor is an essential tool for any modern software development team using containers. With its support for multiple container runtimes and scalable architecture, it provides a secure and reliable platform for managing container images. By following the installation and configuration steps outlined in this blog post, you should now be able to use Harbor on your VMware infrastructure to manage your container images.