Posts

In this vCAC (now renamed vRealize Automation) series, we’ve got access to some of our resources now after connecting our vCenter Endpoint, so now we want to create some policies to control how our new VMs will be deployed. Machine Prefixes We’ll be creating a lot of new virtual machines so we’ll want to put a prefix on all these machines so we can identify them. You can have more than one prefix so that you can have different prefixes by department, company, user or so on. ...

We’ve completed the vCAC (now rename to vRealize Automation) appliance deployment, installed IaaS components, setup tenants and identity stores. Now it’s time to get cracking on connecting to some resources that we can use for our applications. I would like to point out that for this section we’ll be logged in as a user that is both an infrastructure admin as well as a tenant admin. I’ve also chosen to complete this configuration under my newly created “Neighborhood Watch” tenant. When adding resources to your tenants, you can do this at the default tenant level and have the sub-tenants use them, or configure the resources at each tenant level. I would steer away from doing it in both places to make troubleshooting easier at a later date. I mean, what happens when you’re sharing the same vCenter at the default level as well as the sub-tenant level? That could get a bit tricky. ...

If you’ve followed the series this far, you’ve got your vCAC (now renamed vRealize Automation) appliance deployed and your IaaS components installed. The tricky parts are over with, and now the fun begins… configurations! What are you waiting for? Go login at the http://vcacapplaincename/shell-ui-app/ url. Add a Tenant Under Administration –> Tenants, you will see the default tenant which is vsphere.local. This is the context where you can create additional tenants and should probably be considered to be a “Do Not Touch” tenant. Even if you’re only going to have a single tenant, it would be a good idea to create a new one just in case. It’s pretty easy to create more tenants if you make a mistake, but tough to recreate the default tenant. Click the “+” to create a new tenant. ...

Deploying the vCAC (now renamed to vRealize Automation) appliance is only the first step towards getting your Infrastructure as a Service (IaaS) up and running. The next step is to get the IaaS components installed on a Windows machine. There are a number of prerequisites but luckily there is a powershell script that can take care of most of it for you. Find the script here. I must mention first that for vCAC 6 (at the time of this writing) .Net 4.5 is required. This does not mean that .Net 4.5 or higher needs to be installed. .Net 4.5 sp1 does not work with the IaaS components which also means that Server 2012 R2 is not a candidate to install the IaaS components on. Use a Server 2008R2 or Server 2012 with .Net 4.5 installed. (vRealize 6.1 fully supports .Net 4.5.1 according to the VMware rep I spoke with at VMworld) ...

In this day and age, almost all the programs we interact with are web pages. Many of the applications we deploy end up having a web front end and are configured with a default SSL Certificate. It’s much more secure to have your own trusted certificate and in previous posts I’ve gone over how to setup the Public Key Infrastructure (PKI) in a home lab, as well as deploying Web Certificate Templates for our applications. ...

The Array I know what you’re thinking, show me the product! What does it look like, how big is it. 4U storage shelf 2U Storage Controller (dual controllers) CIFSNFSiSCSI 48TB or 96 TB with additional 2.4TB or 4.8 TB SSD Homemade RAID that allows for 2 disk failures on the same storage pool Recovery Something out of the norm with DataGravity’s array is that they use a completely separate set of disks for snapshots. Disks are automatically assigned to different pools are nothing is required from the Administrator to set this up. This diverges from what the rest of the industry is typically does. There are two schools of thought here though: ...

 I got a chance to get a first hand look at Asigra at the Tech Field Day Extra sessions on the Monday of VMworld 2014. I went into the sessions thinking that his was just another backup company, but found that they have a very robust suite of backups and they’ve been around for a very long time. Asigra handles, Cloud Platform apps such as Office365, Salesforce, Google, storage array integration, vSphere snapshot integration, file level backups and the list went on. ...

Hey! You got your VMworld in my Tech Field Day! The makers of Tech Field Day are having an “Extra” set of sessions at VMworld 2014 this year in San Francisco. As you may already know, the Tech Field Day group gets together a set of delegates to engage with some vendors about a variety of solutions. These discussions are all streamed live, as well as posted for later viewing. The discussions are to be technical in nature and can be directed in a much different path than a normal “set” presentation. ...

 Congratulations, if you’ve made it this far, you’re almost done with the replacing of your VMware SSL Certificates! If you’ve followed the previous posts, you’ll know that this has been a long path to completing your goal. This post finishes installing those certificates on your vCenter server. If you missed a part please check out the previous posts to get caught up. Create a Home Lab Certificate Authority Deploy Root Certificates via Autoenrollment Create VMware-SSL Web Certificate Template Create VMware Services Certificate Requests ...

I’ve seen quite a few VMware environments where when you login, you get that silly error message about a certificate not being trusted. This is something we can fix and more importantly be sure that the connections are trusted and encrypted. Prerequisites Trusted root certificates deployed to workstations - Instructions for Lab Environment Web-Certificate Template Deployed - Instructions for Lab Environment Certificate Authority Web Enrollment server - (If you followed the Lab Environment setup this should be on your CA already) Download OpenSSL and install it. I used 1.01h as the version for my lab which worked fine on a Server 2012 R2 Server which is also my vCenter Server. Download and install the vCenter Certificate Automation Tool from VMware. This is also found in the vCenter install media for vSphere 5.5. I prefer to create my certificate requests right from the VMware vCenter Server, so I install both the SSL Automation Tool and OpenSSL directly on the vCenter Server. If you’re using the VMware vCenter Server Appliance you’ll need to do this someplace else and there are some additional steps not listed in this post. Please see this KB article for more info: vCSA SSL Certs ...