search

afewell / HOL-2563-01-TNZ-L

repo for assets used in preparation for HOL
0 stars 0 forks source link

HOL-2563-01-TNZ-L-v0.1 Release #1

Closed afewell closed 1 month ago

afewell commented 2 months ago

Release Notes

Features included in this release

  1. Built on base template "2024-HOL-Single-Site-Base-vPod-8.0U2-v0.4"
  2. Lab initialization process completed: a. Correct "2563" vpodrepo present on Manager VM b. /hol/vPod.txt created and configured with correct SKU on the Linux Main Console (LMC) c. LMC /hol/config.ini validated and copied to the Manager VM /vpodrepo/2025-labs/2563 folder d. LMC Desktop displays correct sku

Explicit steps to move from previous to current release

  1. Create new vApp named HOL-2563-01-TNZ-L-v0.1 based on the 2024-HOL-Single-Site-Base-vPod-8.0U2-v0.4.
  2. Power on ONLY the Main Console, the /hol/vPod.txt file was not present on this template, so I created it, the exact contents are detailed on a note on this ticket.
  3. Power Down the Main Console (to edit the vapp networking config, if done again the network config can be done before the vPod.txt config)
  4. Edit vApp Networking tab > 'vAppNet-vAppNet-single' > Connection, Selected the host network to connect vApp to external network.
  5. Edit vApp Networking tab > Services > Edit, change default firewall rule from deny to allow.
  6. I executed /hol/Tools/proxyfilteroff.sh to enable web access, I believe I will need to do this on each vApp power on but not certain ...
  7. The instructions say to access the vpodrepo on the manager vm and there should be a repo for my vpod sku, but this does not exist, accordingly I cannot edit the config.ini per the instructions. I asked on the hol-group-3 gchat channel, Mark McGill was able to fix this for me. There was no config.ini in the vpodrepo folder, and Mark clarified that this file exists in the main console /hol/ directory and I should copy this file to the vpodrepo folder for 2563. The config.ini on the main console was already configured correctly, so I copied it to the manager/vpodrepo/2025-labs/2563 folder.
  8. Per instructions, restarted the manager vm. I dont know what the "reset" option is in VCD so I used "shut down guest os" and then powered it back on.
  9. After Manager reboot, I verified that the sku on the main console desktop updated to show the correct sku
  10. Shut down the vapp following the shutdown guidelines and saved the template in the AllWorkInProgress catalog as HOL-2563-01-TNZ-L-v0.1
afewell commented 1 month ago

I found a note on following a specific startup sequence for the HOL, I am re-deploying the v0.1 template to conform to this startup procedure: https://tinyurl.com/45pxt6rs Initial Lab Deployments VATs will create the HOL Gitlab Project for your Lab SKU Deploy and wire up a fresh vPod from a 2024 HOL Template Power on ONLY the Main Console Use the VCD Web Console and edit the config.ini to be Correct and Complete Don’t add anything beyond HOL-25xx or your Lab will fail to go Ready LMC: /hol/vPod.txt WMC: C:\hol\vPod.txt Change HOL-BADSKU to reflect your vPod_SKU (i.e. HOL-2501) Power on the entire vPod

afewell commented 1 month ago

There are some additional details on the lab initialization sequence, including the instruction to enable guest vlans (not sure why but appears mandatory?) here: https://tinyurl.com/yfp7nyme

afewell commented 1 month ago

There are much better instructions on the working with the linux main console page, I will follow these instructions exactly and note any deviations or specifics in notes on this ticket.

https://tinyurl.com/3ppn4fzx

afewell commented 1 month ago

Following the steps in the instruction document, I powered on the main console to find there is no /hol/vPod.txt file present in this template, I also tried searching other locations on this hard drive but did not find this file anywhere. That makes me concerned there could be other problems in this template, but nonetheless I will proceed by making a /hol/vPod.txt file based on the screenshots in the instructions with the following contents:

vPod_SKU=HOL-2563
password=VMware123!
labtype=hol