Setting Up Cache Services
In
Request a Connected Cache node from CCM IT, then review the local provisioning sequence. The source requires the hostname, cache mount path and size, plus scripts and a command supplied in response to the ticket.
Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
Configure a Node in Azure
- Submit a ticket to CCM IT requesting Microsoft Connected Cache node configuration. You must supply the following:
- Server Hostname
- Mount Path of the MCCData Disk. (e.g. /mnt/mccdata)
- Size in GB Cache Disk Size. (e.g. 500GB)
- A Zip file – <school code>_mccscripts.zip and a provisioning command to execute will be sent in response to the ticket.
Configure the Local Cache Server
- Copy the zip file to the cache server /tmp; it will not be needed after installation is complete.
- scp <path to downloaded zip file> <user@CacheServer_ip>:/tmp
- SSH to the local server
- ssh <user@CacheServer_ip>
- Unzip <school code>_mccscripts.zip. You will need to install unzip on a new server.
- sudo apt install unzip
- cd /tmp
- unzip mccscripts_duncc.zip
- It unzips to a new folder in /tmp called MccScripts.
- Make all scripts executable.
- Cd into MccScripts folder (case sensitive)
- sudo chmod +x *.sh
- Run the provisioning command provided in your ticket respone. E.g.
- sudo ./provisionmcc.sh customerid="customerid" cachenodeid="cachenodeid" customerkey="customerkey" registrationkey="registrationkey" drivepathandsizeingb="/mnt/mccdata,465"
- Wait at least 30 minutes for the system to fully download, install and configure the cache services.