I am proud to announce myself as a VMUG Leader in the Sweden Community! The journey has just started, and we’ve planned our first event in October! I’m super excited to be a part of the community and to lead the local group forward!
Read more about the event at the community event page.
Yesterday I received the welcome package from VMware, and I’m happy to share with you what I got!
When you’ve configured your vCenter Server Appliance to be a subordinate certificate authority, the VAMI interface at https://vcenter:5480 doesn’t use the new certificate, and it uses a self-signed certificate. In this post, I show you how to resolve this.
First, SSH into the vCSA and locate the certificate file you signed at your CA for the vCSA appliance, it should be named something like vmca.crt or vmca.cer.
Copy and rename that file:
Often when we set up vSphere environments, there are already some things running. Sometimes it may be an Active Directory domain with DNS, NTP, CA, and all that setup. However, if you’re setting up a completely new environment, none of that may exist. What should you do then? We’ll cover all of that in this post.
People often discard the importance of core services. For example, they install vSphere with static entries in the host file instead of using a DNS server. It may work, but it’s hell to operate and maintain. When shit hits the fan, and eventually it does, it helps to have followed the best practices described in this post.
I followed Dave Ceddias awesome guide on how to get a Gatsbyjs blog up and running, you’ll find the guide here.
My requirements was a minimal blog that was easy to manage. I needed to be able to write in markup syntax and have code higlighting.
Gatsbyjs is really aweseom, it lets med do all that and is lightning fast!
Wish me good luck!
