Adds sensu_agent state step to 100GB drive addition

Jira Notes.md

@@ -492,7 +492,7 @@ To cut over:
 1. Edit `/etc/init.d/jira`
 1. Change the path to the updated jira version
 1. `sudo systemctl daemon-reload`
-1. Run `sudo systemctl start jira && sudo tail -F /opt/atlassian/jira-8.13.8/logs/catalina.out`
+1. Run `sudo systemctl start jira && sudo tail -F /opt/atlassian/jira-VERSION/logs/catalina.out`
 
 You may have to restart jira a second time if it warns about files that weren't updated (they really were!).
 

New Customer Setup Notes - GovCloud.md

@@ -922,6 +922,11 @@ salt ${CUSTOMERPREFIX}-splunk-syslog-\* partition.list /dev/${CUSTOMERDRIVE}
 ```
 Add the syslog state to the highstate for the customer and apply highstate. syslog state will mount the drive and add to fstab.
 
+If you do not run the highstate in full, be sure to begin monitoring the new partition by running:
+```
+salt ${CUSTOMERPREFIX}-splunk-syslog-\* state.sls sensu_agent --output-diff
+```
+
 ## Configure the Customer LCP Git Repository 
 
 Add DS `serverclass.conf` and Apps. Be sure to name the server class to match the pillar value. 

VMRay Notes.md

@@ -92,6 +92,13 @@ To upgrade vmray:
 2) Upload into the S3 afs-xdr-binaries bucket.
 3) Update the version and the hashes in `msoc-infrastructure/salt/fileroots/vmray/init.sls`
 4) Run `salt vmray\* state.sls vmray --output-diff` from the salt master.
+5) Run `find /opt/vmray -type f -exec chmod g+r,o+r {} \;`
+5) Run `find /opt/vmray -type d -exec chmod g+rx,o+rx {} \;`
+6) log into the _worker_
+7) `cd /opt/vmray/bin/`
+8) `sudo -u vmray ./vm_setup.py`
+9) Choose option 6: "Update VMRay Tools"
+
 
 ## Handling Failed Upgrades
 If the upgrade fails, check `/usr/local/src/vmray-x.y.z/install.log` to find the reason. After fixing, delete the tarballs, zips, and directories for vmray and extended-kvm from `/usr/local/src/` on the vmray servers, and then rerun the state.