This option will completely shut down the Virtual Machine hosting the instance:

1. Obtain root access

   sudo dont-blame-hipchat

2. Shut down the virtual machine hosting the instance

   poweroff

This option leaves the machine up but stop all services:

1. Create a script in /home/admin/startup_scripts on the server named remove_hipchat_from_startup and add the following content:

   #!/bin/bash
   sudo dont-blame-hipchat -c 'update-rc.d -f hipchat remove'
   sudo dont-blame-hipchat -c 'update-rc.d -f monit remove'
   sudo dont-blame-hipchat -c 'upcate-rc.d -f crowd remove'
   sudo dont-blame-hipchat -c 'chmod -x /etc/cron.hourly/start_monit'

   
   The commands above will prevent init from bringing up the hipchat service, monit service, and crowd service should the nodes get restarted for any reason. 

2. Change the permissions on the script and run it:

   chmod +x /home/admin/startup_scripts/remove_hipchat_from_startup
   cd /home/admin/startup_scripts
   ./remove_hipchat_from_startup

3. Then, manually stop the services:

   service hipchat stop
   service monit stop
   service crowd stop

4. The hipchat service handles punjab, tetra, and coral. Stopping monit will keep the monit service from trying to restart those services behind the scenes.
   Having the script in /home/admin/startup_scripts will prevent those services from starting up whenever the system is rebooted.

If you choose to stop all services only, you can bring it up again by performing the steps below:

1. Remove /home/admin/startup_scripts/remove_hipchat_from_startup file

2. Run Chef using the command cs

3. Start Services again using:

   hup