In our last post, we created a business group that we will use now to create a reservation of resources for. A vRealize Automation reservation is a means to allocate resources in a fabric group (CPU, RAM, Storage, etc.) to a specific business group. To begin, we need to navigate to Infrastructure > Reservations and click Reservations.
Our next step in the initial setup of vRA 7 after creating our fabric group, is to create a business group. A business group associates a set of services and resources to a set of users, often corresponding to a line of business, department, or other organizational unit. Business groups are used when creating reservations and entitling users to items in the service catalog. Before a user can even begin to request catalog items, they must belong to a business group. But before we get into creating the business group, we might want to go ahead and create a machine prefix as this will be one of the options that we set when we create the business group. You use machine prefixes to generate the names of provisioned machines. To create a machine prefix navigate to Infrastructure > Administration >Machine Prefixes. Click New and enter in the the prefix name, number of digits and next number. In this case, the first computer name will be DEV-000 since the number of digits is set to 3 and the next number is 0. The next machine would be DEV-001 and so on and so forth.
Now that we have setup our endpoint and a data collection has ran to discover our vCenter resources, its time to start carving those resource up for use…and fabric groups are the starting point. An IaaS administrator can organize compute resources into fabric groups by type and intent. One or more fabric administrators manage the resources in each fabric group. Fabric administrators are responsible for creating reservations on the compute resources in their groups to allocate resources to specific business groups. Fabric groups are created in a specific tenant, but their resources can be made available to users who belong to business groups in all tenants. To begin with creating our fabric group, we need to login as the IaaS administrator and navigate to Infrastructure > Endpoint > Fabric Groups. Click New
So far, we’ve created our tenant and we got the tenant setup with Active Directory authentication. The next step we want to take is to create a vSphere endpoint that will allow vRealize Automation to communicate with the vSphere environment and discover compute resources, collect data, and provision machines. To begin, we must first login to our tenant as a IaaS administrator. Once we have done that, we want to navigate to Infrastructure > Credentials to enter in the credentials that the endpoint will use to login in order to see the available resources. Click New.
After we have created our first tenant the next step will be to integrate user authentication via Active Directory. To being doing so, we must first log in to our default tenant as our tenant administrator. Navigate to https:// FQDN of vRA Appliance/vcac/org/vsphere.local. Enter in the username and password of the tenant administrator.
After the initial deployment of your vCenter Server Appliance and Platform Services Controller, one of the first things that you want to do if you are using Active Directory is to join your PSC to the domain. In this blog post we are going to walk through doing just that. Like Active Directory domain controllers, the PSC really depends on time being synchronized within your network. The easiest thing to do would be to point all of your devices to the same NTP source. So before beginning, make sure the time is the same on all your devices. Once you have verified that, log into the PSC web UI as the admin account.
Over the past few months, I’ve been searching for a good home lab server to replace the ones I had been using that were decommissioned and given to me by my previous employer…3 HP DL385 G6 rack servers with 64GB each. Well anyone that knows servers, know that these are not ideal from a home lab. Not only are they big, bulky and heavy, but they suck electricity like a newborn baby sucks a warm bottle (I can attest to this, being a new dad to a healthy,hungry boy) and on top of that, they can make a room HOT…really fast! I knew this was not a long term solution for me and there was only so much that I could do with VMware’s online HOL. I needed something that I could not only have to test out all the latest products from VMware without a 2hr or so limit, but also something that I could continue to use to prepare for advanced certifications and create content to share on the blog.
What I Wanted In A Server
First of all…it needed to be small. I have a office at home…not a dedicated server room. I wanted something no bigger than a desktop tower PC. To me, the smaller, the better. I also wanted something that would provide me with enough resources to run two of VMware’s most resource intensive products, NSX and vRealize Automation. Those two products alone would need about 50GB of RAM to install all the components to get up and running. I first began looking into the SuperMicro SYS-E200-8D and SYS-E300-8D servers. I was drawn first to their size and then to the fact that they could max out at a whooping 128GB of RAM. However, I didn’t like the idea of only have 2 options for storage, one 2.5 HDD and one M.2 slot. Then I stumbled across Paul Braren from TinkerTry on Twitter and I that’s when I discovered what would soon be my next home lab server.
What I Got
I ended up purchasing a SuperMicro SYS-5028D-TN4T server bundle from WiredZone and added two additional 32GB DIMMs to have a total of 128GB of RAM.