Backed up by 20 years of experience in the IT-Industry, not only with comdivision but also with various national and international companies, Matthias’ goal is to comprehensibly communicate complex solutions by using a clear, understandable language.
As a certified VMware architect, designer and trainer, Matthias holds various VMware certifications VCP3-6 DCV, VCP6-7 Cloud, VCP NV, VCIX-NV, VCIX-DCV, VCAP7-CMA Design and is also a VMware Certified Instructor (VCI) Level 2. He also teaches current and beta deliveries since 2009.
Matthias was invited into the selected group of mentors in 2012 and VMware honored him for his outstanding contribution in teaching new technologies.
Since 2012 he is also responsible for class development for Cloud Management and Automation products of VMware. In 2014 Matthias was invited into the selected group of NSX instructors. They rewarded him with the vExpert title for Datacenter, Cloud and NSX for his contribution to community regarding vRealize Automation extensibility with vCenter Orchestrator, Network Virtualization and Automation.
My recent blog posts:
This article focuses on the basics of automating NSX via the API and vRealize Orchestrator. Those two are a very powerful combination, automating NSX for certain use cases and workloads. Of course, you could use the provided workflows by the NSX plugin, but what if you would like to implement a use case not covered by the provided workflows. Furthermore, the built-in workflows are using the scripting objects instead of the native REST API. Thus, intended me to write this article.
Aside of vRO, Postman is a great tool to test single API calls. In many cases I use Postman to test the API call and transfer the body, used in Postman, into the API call structure in vRO.Read More
This article explains how to use the “Add connection” workflow from the vCD 9.7 vRO plugin, because it’s not obvious in first place.
After installing the vCD 9.7 plugin into vRO (installation is not part of this article), there are additional workflows in the library, including a folder called “Plug-in Configuration”. This contains the workflows to add, delete, and update the plugin connection to vCloud Director.
I am working as a VCI and teach a lot of trainings with vRO content and often get the question about JSON objects in vRealize Orchestrator and how they work and how they can be built easily. That’s the reason I decided to write an article about that topic with the approach, which helped me, understanding a JSON object.
It took me a while to figure out, how to use the vRO API explorer creating necessary code for workflows. Now is the time to share the knowledge. The API explorer, together with the MOB (Managed Object Browser) of the vCenter Server, provides a very powerful combination to develop code. Often you need to create specific objects to reconfigure virtual machines or hosts for example and you need to collect the information, how an object is created on the one hand and on the other hand how to manipulate an object.Read More
Me writing a blogpost about Horizon View, never thought that this is going to happen, but never say never.
Like many others, I migrated from Windows to Mac and using Mac OS natively. Some time ago we started using remote apps within the Horizon View Client, which is pretty cool. Instead of connecting to my View Desktop I can use an application direct on my Mac.Read More
Lately I had the issue that I needed to create custom XML objects based on variables. In first place it sounds simple, but in the end, there are a couple of different methods doing this. This article will discuss these options.
The first method is a simple string, but if the object gets a bit larger, this is not very useful.Read More
Two weeks ago, I had a problem connecting VMware vCloud Director to vRealize Orchestrator using Rabbit MQ as a message bus between those systems. The base configuration of Rabbit MQ was not a big deal, even clustering the message bus system for high availability, adding an exchange, queues, connecting vCD and vRO, everything was easy and straight forward, BUT: I didn’t get any messages into the right queues. This was my starting point.
As most of you guys know, I am a big fan of vRO (vRealize Orchestrator). I didn’t do any of the configuration in Rabbit MQ using the management interface, I configured everything using vRO but the graphical UI is very useful to verify what the workflows did.
After the installation of Rabbit MQ, I used the documentation (official RMQ documentation: https://www.rabbitmq.com/documentation.html) and some blogs I found, I needed to configure RMQ, but how? Now vRO comes into play, because it is shipped with a preinstalled AMQP plugin, containing all needed workflows to configure the message broker.
Watch Matthias Eisner explain how to customize the NSX controller sizing for a lab environment.
VMware KB with further information:
Watch Matthias Eisner present on a discovered vRealize Automation issue when FQDNs are containing _.
This is documented with VMware, but something we saw recently often during vRA implementations.Read More