- Tanzu Homelab: Overview
- Tanzu Homelab: Storage Policy and Content Library
- Tanzu Homelab: Network Planning
- Tanzu Homelab: Deploy pfSense
- Tanzu Homelab: Deploy HAProxy
- Tanzu Homelab: Deploy Tanzu
- Tanzu Homelab: Final Configurations
This post references the QuickStart guide heavily. The Quickstart guide also has some scripts for some of these sections to speed up the deployment process.
Wanting to become familiar with the whole deployement process, I elected to skip the scripted deployment and do the steps manually.
The first thing we will be deploying is the Storage Policy.
Let’s start by creating a tag on the datastore we will be using. Right Click the datastore – Tags & Custom Attributes – Assign Tag
Because there are no Tags currently created. I select ADD TAG to create my own tag.
There are currently no categories created, so click Create New Category to create one.
I am very creative here, and my category is TanzuCat for the category. All the other options can stay the default.
My tag name is TanzuStorage, then click Create to create the tag.
Now both the tag and category have been created we are back to assigning this newly created tag to our storage. Select the tag, and click Assign.
The tag has been created, but we need to do something with this tag. Let’s create a storage profile for this tag. We need to start by navigating to Policies and Profiles.
Then VM Storage Policies -> Create
Create a storage policy name that makes sense for you. My originality is coming through again here.
For Policy Structure, we only need to have “Enable tag based placement rules” selected.
Select the usage option for “Use storage tagged with”, and select the category and tag you recently created.
Select the datastore you would like which has this tag. Finish the wizard and you are done!
We need to create a user for us to use for Tanzu later.
Navigate to Administration
Then Users and Groups
For my homelab, I am using the vsphere.local domain for this new user. You can also use your own domain if you have vSphere integrated with Active Directory. Select Add to create the new user.
Following the Tanzu QuickStart guide, I am also using devops for the username here.
This user will come back up later on after we have stood up our Tanzu cluster.
Navigate to Content Libraries
Choose a name, and if not already chosen, select your vCenter.
Select Subscribed content library and enter this subscript url: “http://wp-content.vmware.com/v2/latest/lib.json“. I am also going to differ from the quickstart guide a bit here, and suggest selecting “when needed” under Download content.
For me, when I originally created the content library and had “immediately” selected the content library downloaded a LOT of data. This ended up being a couple hundred GBs of data. For a smaller homelab this seemed a bit excessive. I ended up needing to redo the content library later on and decided to only download the content when needed which is working out much better in my homelab.
There is nothing to do on the security policy page. Click Next
Choose which datastore you would like the content library to be stored.
Congratulations! On to Network Planning!