Recently I was in charge of designing and implementing a new vSphere and vSAN infrastructure for a customer.
Everything went just fine, except that we all have experienced many network outages due to misconfiguration of some Firewall Virtual Appliances where the whole infrastructure relies on.
As a result, all ESXi got disconnected from the vCenter and this happened many times!
Anyway, the network team in the end fixed the issue and the network was finally stable but I have to say that I’m not a fan of firewall virtual appliance as it brings some limitations and complexity. Unfortunately, those outages had a bad impact on the virtualization network as some warnings appeared showing some ESXi hosts out of sync with the distributed switch.
This could not be a big deal at the beginning but this kind of issue definitely needs to be addressed to avoid any network problem in the future.
Last month, I was happy to successfully pass my VCAP-DCV 6.5 Design exam that has also validated my VCIX-DCV 2019.
The exam was very challenging and tough from my point of view but I would say it was also fair. All the questions were from topics that you can find in the exam blueprint. So you know exactly what you have to study before taking the exam.
But I have to be honest with you, I didn’t pass on my first attempt. The thing is that I rushed to fast to take the exam thinking that I was ready but I wasn’t.
Hello the VMware community. VMware has released yesterday a small but important update to vRA 8.
So what’s new?
Well, in the very first release of vRA 8, it wasn’t possible yet to migrate from vRA 7.x , due to the major changes in the architecture. it was just a matter of time before VMware brings up the functionality.
But from now on, you can migrate your existing vRA 7.5 or 7.6 environnent to 8.0.1. VMware also says that a migration is possible by creating a brand new vRA 8 platform and then migrate all the configuration from an existing vRA 7.x environment.
I can imagine that a lot of people was waiting for this feature which is quite important and especially when it comes to a major release of a product. So guys let’s go to our homelabs or test environment and do some migrations.
VMware also developed a new migration assessment tool to collect “offline” data from your vRA, vRO or external vRO source environment. Then you can upload the collected data during the assessment phase of your new installation.
The new features below are part of vRA 8.0.1 as well:
Blueprint Properties Editor
API enhancements for Networking and Deployments
Extensibility VA and ABX resiliency enhancements
vRO based catalog services now support array/number as inputs parameters
vRealize Automation 8 was released last week and I wanted to share with you how to do the installation of that new version.
Like I stated in a previous blog post, vRA 8 comes in a brand new platform built on a container-based architecture running on Photon OS 2.0.
As you know, no more Windows machines is required but the vRA 8 appliance includes all the services such as Cloud Assembly, Service Broker, Code Stream, and vRealize Orchestrator that leverage the main product.
There are some prerequisites before installing vRA 8. You will have first to deploy the Lifecycle Manager and then the Identity Manager. Know that you can also migrate earlier version of LCM and IDM if you have older version running in your environment. However it is not possible to install each component by deploying their respective OVA files.
That was unexepected and many of you may have not heard about it, but it is here. vRealize Automation 8 was announced at VMworld 2019 US.
vRealize Automation 8 comes with a new and modern platform built on a container-based architecture that offers more scalability and performance than in previous versions.
No more Windows Server machine is required for the installation. Yes, you read right! Administrators and Engineers working on vRA 6 and 7 would be more than happy to hear that, as previous installations were a real pain and especially with vRA 6.
Only one VM can now run all vRA services but the infrastructure can also be extented to support a three nodes configuration if more scaling and high availability is required.