In part 2 we automated the installation of our VMware Horizon agents, including AppVolumes and Dynamic Environment Manager. We also patched our template and applied optimization settings using the VMware OSOT fling. In this final part, we automate the entire solution from end-to-end using VMware CI/CD tool, Code Stream. In the end, with one-click, we will generate our template ready for use. Continue reading
In part 1 of this series, we built a Windows 10 desktop using HashiCorp Packer. Now we will script the installation of the VDI agents needed for our VMware Horizon environment. After this, we will patch the box with the latest updates, before applying the VMware OS Optimization Tool to produce a lean and clean image. In the last part, we will automate the solution using VMware Code Stream.
In previous consultancies I’ve worked, it was common practice to frequently patch corporate VDI templates. Whilst continuous patching is a good thing, it is quite often laborious. Any attempt to automate this is seen as difficult and organizations often give up and continue with manual processes. Here I will show how it can be done using Code Stream and HashiCorp Packer. Continue reading
Recently I have been deepening my learning of DevOps methodolgies, specifically around the vRealize Automation and Orchestrator platforms. I have been producing code for both in my development environment for a while and promoting it manually to test, staging and production. However, this is a very error-prone and laborious process that fails to take advantage of Continue reading
Recently a customer I was working with had the need to ensure that deployments of a certain service category had a lower lease time than others. So all blueprints would have no maximum lease time configured, but if a customer chose a “DevTest” catalog item, then the lease time is set to seven days. Continue reading
In HobbitCloud we have the ability to deploy vRealize Automation workloads to multiple sites. This enables us to leverage different technologies like NSX for vSphere and NSX-T, without having to mix both in the same site. It also means that if we have to scale up workloads for certain projects, we can utilise different clusters. Continue reading
Really short post, but this might stop you from going bat**** crazy…
Recently I needed to create some NSX Distributed Firewall Rules in vRealize Orchestrator for a complex micro-segmentation project. The layer 3 section already existed in NSX, I just needed to create the rules on the fly using the REST API. Continue reading
In part 1 of this short series we used vRO to create a bearer token for connecting to Microsoft Azure. Now we will create some new components and a master workflow for provisioning our AKS Cluster, to enable our developers to request public cloud Kubernetes straight from vRealize Automation. Continue reading
Kubernetes (k8s) is arguably one of the hottest technologies right now. Whether it’s building your own in the private cloud, leveraging vendor implementations to compliment your enterprise apps or consuming public cloud varieties like Amazon Web Service’s EKS – there’s no shortage of ways to deploy k8s.
A few days ago I had the strange need to capture a requester’s business group in a custom property whilst provisioning resources in vRealize Automation.
Whilst obtaining this information post-provisoning is simple enough, I couldn’t find an obvious way to do this at first. Then I sat down and thought about it. Continue reading