From 781361d3e24dd0350c99c73ac7be506c35ca230b Mon Sep 17 00:00:00 2001 From: Jeremy Cline Date: Mar 13 2017 13:49:28 +0000 Subject: Merge #13 `Update the hotness SOP to use the upgrade playbook` --- diff --git a/docs/sysadmin-guide/sops/hotness.rst b/docs/sysadmin-guide/sops/hotness.rst index cfa760e..beccfb9 100644 --- a/docs/sysadmin-guide/sops/hotness.rst +++ b/docs/sysadmin-guide/sops/hotness.rst @@ -46,16 +46,15 @@ repository), you will need to build it into the :ref:`infra-repo`. 2. Consult the upstream changelog. If necessary, adjust the Ansible configuration for the-new-hotness. -3. Update the host. At the moment this is done with shell access to the host and running:: +3. Update the host. This is done with the manual upgrade playbook and can be used for both staging + and production deployments:: - $ sudo -i yum clean all - $ sudo -i yum update the-new-hotness + $ sudo rbac-playbook -l staging manual/upgrade/hotness.yml # remove the "-l staging" to update prod -4. Ensure the configuration is up-to-date by running this on batcave01:: +This will upgrade to the latest hotness package, apply the hotness role so the configuration is +up-to-date, and restart the necessary services. - $ sudo rbac-playbook -l staging groups/hotness.yml # remove the "-l staging" to update prod - -All done! +Congratulations, all done! Monitoring Activity