Browse Author

admin

Upgrading SSC (SaltStack Config) to 8.11.1 using vRSLCM

In this post i will go over upgrading my 8.x SSC appliance to 8.11.1. As a pre requirement we do need to have vRSLCM (vRealize Lifecycle Manager) upgraded to 8.11.1. Instructions can be found here. The upgrade does not include the latest PSPACK that contains the 8.11.1 SaltStack Config release. Instructions to get the PSPACK can be found on my other blog post here.

To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware)

Click on Add Binaries under Product Binaries

Select My VMware and click on Discover

We can see a list of binaries that have been discovered. We can select what we need and click on Add

This will create a request and start downloading the package. To view the progress we can click on the Click Here hyperlink

Click on the in Progress button to view the details

We now have to wait for the download to complete

After the download is complete we can go to Environments -> View Details on the environment that includes SSC

Click on Upgrade

An Inventory sync is recommended if the environment has changed since LCM performed the last sync. We trigger the sync from the UI or click on Proceed to continue

Select product Version 8.11.1 and click Next. We can also review the compatibility matrix to make sure the environment is compatible.

We can automatically create and delete a snapshot part of the upgrade process

Run the Precheck to make sure there are no errors

Once the check is complete, click on Next. Review the upgrade details and click on Next. We are taken to the progress screen where we can follow the progress.

The system will get rebooted and once its back up we will be on 8.11

Here are a few additional blogs that might be useful post upgrade:

Error Code: LCMVSSC10018

SSC 8.8 sseapi_rpc_queue: could not connect to SSE server

SSC 8.8 urllib3 (1.25.11) or chardet (4.0.0) doesn’t match a supported version

Authentication failed: no Authorization header

Comparing vRealize Automation to Chef

vRealize Automation and Chef are both popular tools used in IT automation, but they approach automation in different ways. In this blog, we will compare vRealize Automation with Chef to help you understand their differences and similarities.

What is vRealize Automation?

vRealize Automation is an IT automation tool that enables the automation of the deployment and management of virtual infrastructure and applications. It helps organizations to streamline their IT processes and create more efficient workflows. vRealize Automation provides a single platform for IT teams to manage and automate the deployment of infrastructure and applications.

What is Chef?

Chef is an infrastructure automation tool that enables the automation of the entire IT infrastructure. It helps organizations to create consistent and reliable infrastructure that can be easily managed and maintained. Chef provides a single platform for IT teams to manage and automate the deployment of infrastructure and applications.

Comparison between vRealize Automation and Chef

  1. Automation approach: vRealize Automation and Chef have different approaches to automation. vRealize Automation uses a declarative approach to automation, where you define what you want to happen and vRealize Automation takes care of the how. Chef uses a procedural approach to automation, where you define how you want something to happen and Chef takes care of the what.
  2. Integration with other tools: Both vRealize Automation and Chef can integrate with other tools, but vRealize Automation has more out-of-the-box integrations with other VMware tools. Chef, on the other hand, has a wide range of integrations with other tools, including AWS, Azure, Google Cloud, and many more.
  3. Scalability: Both vRealize Automation and Chef are scalable and can be used to manage large and complex IT environments. However, vRealize Automation is more suited for managing virtual infrastructure and applications, while Chef is more suited for managing the entire IT infrastructure.
  4. Learning curve: Both vRealize Automation and Chef have a learning curve, but Chef may have a steeper learning curve for beginners. vRealize Automation has a more intuitive user interface, while Chef requires more knowledge of scripting languages like Ruby.
  5. Community support: Both vRealize Automation and Chef have a large community of users and support resources. However, Chef has a more active community and more extensive documentation, making it easier to find answers to questions.

Conclusion

In conclusion, vRealize Automation and Chef are both powerful automation tools, but they have different strengths and weaknesses. vRealize Automation is more suited for managing virtual infrastructure and applications, while Chef is more suited for managing the entire IT infrastructure. vRealize Automation is easier to learn and has more out-of-the-box integrations with other VMware tools, while Chef has a steeper learning curve but has more extensive integrations with other tools. Ultimately, the choice between vRealize Automation and Chef will depend on your organization’s specific needs and priorities.

Comparing vRealize Automation to Chef

vRealize Automation and Chef are both popular tools used in IT automation, but they approach automation in different ways. In this blog, we will compare vRealize Automation with Chef to help you understand their differences and similarities.

What is vRealize Automation?

vRealize Automation is an IT automation tool that enables the automation of the deployment and management of virtual infrastructure and applications. It helps organizations to streamline their IT processes and create more efficient workflows. vRealize Automation provides a single platform for IT teams to manage and automate the deployment of infrastructure and applications.

What is Chef?

Chef is an infrastructure automation tool that enables the automation of the entire IT infrastructure. It helps organizations to create consistent and reliable infrastructure that can be easily managed and maintained. Chef provides a single platform for IT teams to manage and automate the deployment of infrastructure and applications.

Comparison between vRealize Automation and Chef

  1. Automation approach: vRealize Automation and Chef have different approaches to automation. vRealize Automation uses a declarative approach to automation, where you define what you want to happen and vRealize Automation takes care of the how. Chef uses a procedural approach to automation, where you define how you want something to happen and Chef takes care of the what.
  2. Integration with other tools: Both vRealize Automation and Chef can integrate with other tools, but vRealize Automation has more out-of-the-box integrations with other VMware tools. Chef, on the other hand, has a wide range of integrations with other tools, including AWS, Azure, Google Cloud, and many more.
  3. Scalability: Both vRealize Automation and Chef are scalable and can be used to manage large and complex IT environments. However, vRealize Automation is more suited for managing virtual infrastructure and applications, while Chef is more suited for managing the entire IT infrastructure.
  4. Learning curve: Both vRealize Automation and Chef have a learning curve, but Chef may have a steeper learning curve for beginners. vRealize Automation has a more intuitive user interface, while Chef requires more knowledge of scripting languages like Ruby.
  5. Community support: Both vRealize Automation and Chef have a large community of users and support resources. However, Chef has a more active community and more extensive documentation, making it easier to find answers to questions.

Conclusion

In conclusion, vRealize Automation and Chef are both powerful automation tools, but they have different strengths and weaknesses. vRealize Automation is more suited for managing virtual infrastructure and applications, while Chef is more suited for managing the entire IT infrastructure. vRealize Automation is easier to learn and has more out-of-the-box integrations with other VMware tools, while Chef has a steeper learning curve but has more extensive integrations with other tools. Ultimately, the choice between vRealize Automation and Chef will depend on your organization’s specific needs and priorities.

Comparing vRealize Automation to Jenkins

In the world of DevOps, automation tools are essential for managing infrastructure, applications, and processes. Two popular tools for automation are vRealize Automation and Jenkins. Both tools are designed to simplify and streamline processes, but they have different strengths and weaknesses. In this blog, we’ll compare vRealize Automation and Jenkins to help you decide which tool is right for your automation needs.

What is vRealize Automation? vRealize Automation is a cloud automation tool developed by VMware. It is designed to automate the deployment and management of applications, infrastructure, and multi-cloud environments. vRealize Automation provides an end-to-end solution for automating infrastructure and application delivery across a hybrid cloud environment.

What is Jenkins? Jenkins is an open-source automation tool that provides a platform for building, testing, and deploying software. It is used for continuous integration (CI) and continuous delivery (CD) to automate the software development process. Jenkins provides a platform for developers to integrate code changes, run tests, and deploy applications to production.

Ease of Use vRealize Automation is designed for enterprise-level automation and can be complex to set up and use. It requires advanced technical skills to install and configure. In contrast, Jenkins is straightforward to set up and use, making it an ideal tool for smaller teams or individual developers.

Scalability vRealize Automation is designed to scale to meet the demands of large enterprises with multiple teams, environments, and applications. It provides a centralized view of infrastructure and applications across multiple clouds, making it easy to manage and scale. Jenkins is also scalable, but it requires additional plugins and customization to achieve enterprise-level automation.

Integration vRealize Automation is designed to integrate with other VMware tools, making it an ideal choice for organizations that use VMware software. It can also integrate with other third-party tools, such as Ansible, Terraform, and GitLab. Jenkins is an open-source tool that can integrate with a wide range of tools and technologies, including AWS, Azure, Docker, and Kubernetes.

Workflow Management vRealize Automation provides a graphical user interface (GUI) for managing workflows and automating tasks. It uses a drag-and-drop interface that makes it easy to design and manage workflows. Jenkins, on the other hand, provides a scripting language that requires developers to write code to manage workflows.

Security vRealize Automation is designed with enterprise-level security features, such as multi-factor authentication, role-based access control, and integration with security tools like VMware AppDefense. Jenkins is also secure, but it requires additional plugins and configuration to achieve enterprise-level security.

Cost vRealize Automation is a commercial tool that requires a license, making it more expensive than Jenkins. Jenkins is an open-source tool that is free to use and can be extended with plugins and customization.

Conclusion vRealize Automation and Jenkins are both powerful automation tools that can simplify and streamline the software development process. vRealize Automation is an ideal choice for large enterprises that require enterprise-level automation and security features. Jenkins, on the other hand, is a flexible and open-source tool that is easy to set up and use, making it an ideal choice for small teams and individual developers. When deciding between vRealize Automation and Jenkins, consider your organization’s size, automation needs, and technical skills.

SaltStack Config vs Terraform: A Comparison of Two Leading Infrastructure Management Tools

When it comes to automating and managing large-scale infrastructure, two popular tools are SaltStack Config and Terraform. While both tools offer valuable solutions, SaltStack Config stands out as the better choice for organizations looking for a comprehensive solution.

SaltStack Config is a configuration management tool that offers a unique combination of powerful configuration management and resource management features. Its master-minion architecture enables efficient communication between the master node and the minions, allowing for the enforcement of desired state configurations across a large number of servers. This makes SaltStack Config the ideal solution for organizations that need to manage and maintain a large number of servers.

In addition to its configuration management capabilities, SaltStack Config also offers resource management features that allow organizations to manage and automate the deployment of software and updates across their infrastructure. This saves time and reduces the risk of human error, making SaltStack Config a great choice for organizations looking to streamline and automate their infrastructure management processes.

SaltStack Config is also user-friendly and easy to understand. It uses Python as its primary language, which is a popular and widely used language in the technology industry. This makes it easier for organizations to find and hire skilled professionals who can work with SaltStack Config, and also makes it easier for organizations with large IT teams to understand and maintain the tool.

In conclusion, SaltStack Config is the better choice for organizations looking for a comprehensive solution for infrastructure management and automation. Its combination of powerful configuration management and resource management features, along with its ease of use and Python-based syntax, make it the ideal choice for organizations looking to streamline and automate their infrastructure management processes. Whether you need to manage a large number of servers or are simply looking for a more efficient way to manage your infrastructure, SaltStack Config has you covered.

Comparing vROps Workload Optimizations with CWOM

VMware vRealize Operations (vROps) is not the only tool available for managing the performance and capacity of virtual environments. Another solution that has gained popularity in recent years is the Cloud Workload Optimization Manager (CWOM). In this blog, we will compare vROps workload optimizations with CWOM to help organizations determine which solution is best suited for their needs.

  1. Functionality vROps provides a comprehensive set of features for managing the performance and capacity of virtual environments. It includes advanced performance analytics, customized workload optimizations, improved visibility, and cost savings. On the other hand, CWOM is a more specialized tool that focuses on optimizing resource utilization for cloud workloads. While CWOM has some similar features to vROps, it lacks the depth of functionality provided by vROps.
  2. Scalability vROps is designed to manage large, complex virtual environments and is highly scalable. It can support multiple vCenter servers, hundreds of thousands of virtual machines, and provide real-time performance data. CWOM, on the other hand, is designed for smaller cloud environments and may not be suitable for organizations with large virtual environments.
  3. Integration vROps integrates seamlessly with other VMware products and solutions, such as vCenter and NSX, to provide a unified view of the virtual environment. CWOM, on the other hand, is designed to work with specific cloud platforms and may not provide the same level of integration as vROps.
  4. Cost vROps is a premium solution that is typically more expensive than CWOM. However, the comprehensive set of features provided by vROps and its ability to manage large, complex virtual environments can make it a more cost-effective solution in the long run.

In conclusion, vROps workload optimizations provide a comprehensive solution for managing virtual environments, while CWOM is a specialized tool for optimizing resource utilization for cloud workloads. Organizations should consider their specific needs, the size and complexity of their virtual environment, and their budget when deciding between vROps and CWOM.

In general, organizations with large, complex virtual environments may find vROps to be the better choice, while smaller organizations with specific cloud optimization needs may prefer CWOM. However, both solutions can provide significant benefits and organizations should carefully consider their specific requirements before making a decision.

Benefits of Using vROps Workload Optimizations Over Regular DRS

VMware vRealize Operations (vROps) is a comprehensive solution for managing the performance and capacity of virtual environments. It offers several workload optimizations to help administrators balance resource utilization, meet SLAs, and ensure optimal performance. These optimizations go beyond what is possible with traditional Distributed Resource Scheduler (DRS) and can provide numerous benefits to organizations. In this blog, we will explore some of the advantages of using vROps workload optimizations over regular DRS.

  1. Advanced Performance Analytics vROps provides real-time performance analytics and capacity planning, which helps administrators make informed decisions about resource allocation. This can result in improved application performance and reduced downtime. vROps also provides detailed performance metrics for individual virtual machines and infrastructure components, making it easier to identify performance bottlenecks.
  2. Customized Workload Optimizations vROps provides workload optimizations that can be customized to meet the specific needs of an organization. This allows administrators to fine-tune resource utilization and balance performance and cost efficiency. With vROps, administrators can set custom policies to manage resource allocation, prioritize critical applications, and enforce SLAs.
  3. Improved Visibility vROps provides a unified view of the virtual environment, making it easier to manage and monitor resource utilization. This improved visibility helps administrators to quickly identify and resolve performance issues, improving the overall health of the virtual environment. vROps also provides real-time alerts, which can help administrators to quickly respond to critical issues before they become major problems.
  4. Cost Savings vROps provides several optimizations to help organizations save on costs. For example, vROps can help administrators to optimize resource utilization and reduce unnecessary overprovisioning. Additionally, vROps can help organizations to avoid licensing costs by providing detailed information on virtual machine usage, making it easier to determine which virtual machines can be decommissioned or consolidated.

In conclusion, vROps workload optimizations provide organizations with several benefits that go beyond what is possible with traditional DRS. With advanced performance analytics, customized workload optimizations, improved visibility, and cost savings, vROps provides a comprehensive solution for managing virtual environments. By using vROps, organizations can improve application performance, reduce downtime, and ensure optimal resource utilization.

Upgrading vIDM (VMware Identity Manager ) to 3.3.7 via vRSLCM

In this post i will go over upgrading my 3.3.6 vIDM appliance to 3.3.7 using vRSLCM (vRealize Suite Lifecycle Manager). If you want to upgrade to LCM 8.10 instructions can be found here. The upgrade does not include the latest PSPACK that contains the 3.3.7 vIDM release. Instructions to get the PSPACK can be found on my other blog post here.

To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware)

Click on Add Binaries under Product Binaries

Select My VMware and click on Discover

We can see a list of binaries that have been discovered. Make sure we select the upgrade package not the install package. We can select what we need and click on Add

This will create a request and start downloading the package. To view the progress we can click on the Click Here hyperlink

Click on the in Progress button to view the details

We now have to wait for the download to complete

After the download is complete we can go to Environments -> View Details on the environment that includes vIDM

Click on Upgrade

An Inventory sync is required when performing vIDM upgrades. We trigger the sync from the UI and click on Proceed once completed to continue

Select product Version 3.3.7 and click Next. We can also review the compatibility matrix to make sure the environment is compatible.

A new feature that was added was the capability to automatically create a snapshot prior to the upgrade and remove it after the upgrade. On this screen we also have the ability to chose if we want to keep the snapshots post upgrade for validation testing for example. Click next

Run the Precheck to make sure there are no errors or issues.

There`s a list of Manual Validations. Once verified click on I took care of the manual steps above and am ready to proceed check box and click on Run Precheck

Once the check is complete we can review the checks that were performed and we can continue by clicking Next.

Review the upgrade details and click on Submit. We are then taken to the progress screen where we can follow the progress.

The system will get rebooted and once its back up we will be on 3.3.7

Since we are doing a major upgrade i strongly recommend to clean the cache before using the new vIDM version.

Deploying vRA 8.11 using the Easy Installer

In this guide i will go over the deployment of vRA 8.11 using the Easy Installer. The reason i like the Easy Installer is because it deploys everything that i need. vIDM, Lifecycle Manager as well as vRA.

To get started we need to download the installer from here.

Once downloaded mount the iso as a drive using your favorite tool or extract it as a archive using something like 7-zip

Once mounted go to the CDROM in the vrlcm-ui-installer\Mac directory if on mac or vrlcm-ui-installer\win32 if you are on windows. In here run the installer file

We will be presented with the following window:

The migration option allows us to migrate from from vRSLCM 2.1 to 8.x, it can migrate Datacenter and vCenters, all existing environments, DNS, SNMP, NTP, My VMware, proxy details, migration of vIDM installation as well as Blackstone Content endpoints. For the purpose of this guide we will process with the Install option

Once we click Install we will be presented with an Introduction of what components will be included part on the installation. In my case i can see vRealize Automation 8.11, Lifecycle Manager 8.10, Identity Manager 3.3.6.

Click Next, Review, accept the agreement and click next

Provide the vCenter details and click next. In my case i used the administrator account. A detailed list of permissions needed for deployment can be found here

Sections 4, 5, 6 and 7 are straight forward so i will skip them

In section 8 select a password that will be used across all products for the local usernames. ex for LCM root and local admin, vIDM admin, sshuser, root etc

Select a VM name for the Lifecycle Manager appliance and its ip credentials. If you are expecting a large repository in lifecycle manager we can add additional disk under the Increase Disk Size in GB section.

The FIPS Mode compliance option enforces FIPS compliance, however keep in mind that with the FIPS mode enabled there are limitation on what the product can do. This can be disabled later and re enabled as needed.

Complete the fields and click next

The next portion is vIDM. In case there is an existing vIDM appliance in the environment we can also import and existing vIDM appliance. In my case i will deploy a new one.

One important option under vIDM is the Sync Group Members to the Directory When Adding Group. When enabled, members of the groups are synced when groups are added from Active Directory. When this is disabled, group names are synced to the directory, but members of the group are not synced until the group is entitled to an application or the group name is added to an access policy. Note: Post deployment this value cannot be changed from vRealize Suite Lifecycle Manager. To update this field post deployment, navigate to VMware Identity Manager

My configuration page looks like this:

The next section is the vRA Configuration. In here we have a couple of options. We can perform a standard 1 node deployment or a cluster deployment which includes 3 appliances. The FIPS Compliance mode enables FIPS compliance. Unlike LCM this mode cannot be disabled after the deployment. This disables a number of options in vRA from an LCM perspective. Please make sure that its only enabled if required.

The advanced configuration at the bottom of the page includes the option to change the internal Kubernetes cluster and Service ip range. This is useful if the default range is already in use on the internal network. We want to make sure we pick an ip range thats not used somewhere else in order to avoid routing issues. Once complete click next

The next page gives us a summary of our deployment and we can click submit to start the deployment.

Next we are presented with the installation process. We can follow it along, in my environment the full deployment took about 1.5 hrs

After the install is complete we are presented to links for the different services

Next i would recommend LCM certificate management found here

vRSLCM (vRealize Lifecycle Manager) Product Support Pack

In this guide i will go over the steps of getting an existing 8.x vRSLCM appliance to support the latest product releases available. Here is a great blog that goes in to the details about what the Product Support Pack is https://blogs.vmware.com/management/2019/01/vrslcm-pspak.html. Typically the newer Product Support Pack is included part of the upgrade for LCM, however sometimes there are product releases in between releases where product support packs come in handy.

The first step is to log in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section

Go to settings -> Product Support Pack

We can see that i recently upgraded to 8.10.0.0 however a new update is available 8.10.0.7. Based on what we can see in the details the new support pack adds support for vRA 8.11. If an update is not available click on the Check Support Packs Online button and refresh the screen within a few minutes

Click on Apply Version

Verify that a snapshot or a backup exists and click Submit

We can view the progress by clicking on the Click Here link after submitting the request

Once the process is complete the system will most likely reboot. To check the status we can go back to settings -> Product Support Pack. As we can see we are now at the updated patch level

If you get the below error clear the browser cache and try again