Dropping VM

removing VM checklist

README.md

@@ -81,7 +81,6 @@ The aim of this project is to have a quick guide of what to do when an emergency
 * [Start a psql console in the staging environment](howto/staging-environment.md#run-a-psql-console-in-staging-environment)
 * [Force a failover with postgres or redis](howto/manage-pacemaker.md#force-a-failover)
 * [Use aptly](howto/aptly.md)
-* [Disable PackageCloud](howto/stop-or-start-packagecloud.md)
 ### Work with the Database
@@ -106,6 +105,7 @@ The aim of this project is to have a quick guide of what to do when an emergency
 * [Retrieve old values in a Chef vault](howto/retrieve-old-chef-vault-values.md)
 * [Manage Chef Cookbooks](howto/chef-documentation.md)
 * [Best practices and tips](howto/chef-best-practices.md)
+* [Delete node from the chef]()
 ### Work with CI Infrastructure
@@ -119,6 +119,7 @@ The aim of this project is to have a quick guide of what to do when an emergency
 * [Create a DO VM for a Service Engineer](howto/create-do-vm-for-service-engineer.md)
 * [Create VMs in Azure, add disks, etc](https://dev.gitlab.org/cookbooks/chef-repo/blob/master/doc/azure.md#managing-vms-in-azure)
 * [Bootstrap a new VM](https://dev.gitlab.org/cookbooks/chef-repo/blob/master/doc/new-vps.md)
+* [Remove VM](howto/remove-vm.md)
 ### Manually ban an IP or netblock
@@ -137,22 +138,21 @@ The aim of this project is to have a quick guide of what to do when an emergency
 * Confirm that it is actually an emergency, challenge this: are we losing data? Is GitLab.com not working?
 * [Tweet](howto/tweeting-guidelines.md) in a reassuring but informative way to let the people know what's going on
-* Join the `#infrastructure` channel
-* Define a _point person_ or _incident owner_, this is the person that will gather all the data and coordinate the efforts.
-* Organize:
-  * Establish who is the point person on the incident in the `#infrastructure` channel: "@here I'm taking point" and pin the message for the duration of the emergency.
-  * Start a war room using zoom if it will save time
-  * Share the link in the #infrastructure channel
-  * If the _point person_ needs someone to do something, give a direct command: _@someone: please run `this` command_
+* Join the `#alerts` channel
+* Organize
+  * Establish who is taking point on the emergency issue in the `#alerts` channel: "I'm taking point" and pin the message for the duration of the emergency.
+  * open a hangout if it will save time: https://plus.google.com/hangouts/_/gitlab.com?authuser=1
+  * share the link in the alerts channel
+* If the point person needs someone to do something, give a direct command: _@someone: please run `this` command_
 * Be sure to be in sync - if you are going to reboot a service, say so: _I'm bouncing server X_
 * If you have conflicting information, **stop and think**, bounce ideas, escalate
-* Gather information when the incident is done - logs, samples of graphs, whatever could help figuring out what happened
-* If we lack monitoring or alerting Open an issue and label as `monitoring`, even if you close issue immediately. See [handbook](https://about.gitlab.com/handbook/infrastructure/)
+* Fix first, ask questions later.
+* Gather information when the outage is done - logs, samples of graphs, whatever could help figuring out what happened
+* Open an issue and put `monitoring` label on it, even if you close issue immediately. See [handbook](https://about.gitlab.com/handbook/infrastructure/)
 ## Guidelines
 * [Tweeting Guidelines](howto/tweeting-guidelines.md)
-* [Production Incident Communication Strategy](howto/manage-production-incidents.md)
 ## Other Servers and Services

howto/remove-vm.md

+## Remove VM
+
+### Checklist for removing VM from the Azure
+
+1. Remove VM
+1. Cleanup all the related resources for the allocated VM (disks, network interfaces, etc)
+1. Delete VM from the chef serve
+
+### Removing the VM from the chef server
+
+1. Execute `knife node delete example.gitlap.com`, where is `example.gitlap.com` is the node name.
+1. Delete corresponding files from the chef-repo. Usually it is `nodes/example.gitlap.com.json` and related roles.