Continuing smooth migration to vRealize Automation 8, API control is next in line. In vRO 7, the vCAC and vCACCAFE plugins were used to manage vRA, in the 8th version, only the REST API was used. There is no package from VMware yet, but processes are needed right now. To save time at the start, I suggest starting with a small set of basic processes.
Continue readingTag Archives: automation
vRO: data from Kubernetes
With the advent of Kubernetes in the productive environment, automation is expanding from the level of hosts, clusters and virtual machines, including K8S objects: namespace , ingress , service , pod … Do you need to create another automation system specifically for Kubernetes or can you use vRealize Orchestrator, which is already integrated with your information systems?
Continue readingvRA 8: Integration with Polemarch
The previous two articles covered how vRealize Automation 8 works with Ansible Open Source. Our infrastructure already uses Polemarch to work with Ansible, but there is no integration with it in vRA 8. In order not to wait for the development of integration from VMware, we will do it ourselves using Custom Resources and Dynamic Types.
Continue readingvRA 8: Ansible + Kubernetes
The previous article vRA 8: Ansible Integration tested using Ansible to configure servers in vRealize Automation 8. Let’s see how this works on a real-world task – deploying a kubernetes cluster. There is a large selection of ready-made Ansible playbooks, one of the most advanced is Kubespray. Let’s develop a vRA blueprint to create a K8S cluster using Kubespray.
Continue readingvRA 8: Ansible Integration
Let’s start testing new features and preparing to migrate to vRealize Automition 8. Our vRA 7.x installation uses software components extensively to configure our servers. Therefore, the main question is how to configure the server if the software components are no longer there? vRA 8 offers several solutions: cloud-init, Ansible Tower and just Ansible (on a remote SSH server).
Continue readingvRA: package for Yandex.Cloud
The previous article describes the implementation of the basic interaction between vRealize Orchestrator and Yandex.Cloud. The new version of the package is aimed at managing Yandex instances from vRA through Dymamic Types objects. The necessary processes have been developed, a set of objects for vRA has been created: resources, actions, blueprints.
Continue readingvRO: integration with Yandex.Cloud
vRealize Automation and vRealize Orchestrator integrate seamlessly with a variety of public clouds to create a single enterprise cloud platform. Yandex.Cloud is a new player in this market, and it does not yet have ready-made plugins / packages for integration with many third-party cloud solutions. Therefore, we had to independently develop a package to integrate it with vRO.
Continue readingvRO: working with workflow
As vRealize Automation and vRealize Orchestrator are used, the scope of their tasks is constantly expanding. The number of processes supporting these tasks is growing even faster. Fortunately, any process is just another object that can also be automated.
Continue readingvRO: integration with Harbor
I recently wrote a review on working with Harbor via the REST API. Based on this material, the Harbor and vRealize Orchestrator integration package has been developed . Only a few basic operations are used in day-to-day administration tasks. This minimum set is implemented as a process package for the orchestrator.
Continue readingvRA: PKS automation
PKS uses the PKS CLI to manage clusters; another management option: register PKS with VMware Admiral, for example, built into vRealize Automation and manage clusters from it. However, Admiral will not allow automating work with clusters, this is just a GUI. What if you need the ability to make a single process, combining the creation of a cluster, registering it in DNS, setting monitoring in vROps, creating a project in Harbor and adding rights to users?
Continue reading