|
|
@@ -1,44 +1,53 @@
|
|
|
+# MDR Patching Notes.md
|
|
|
|
|
|
+# Patching Process
|
|
|
|
|
|
+Each month the environment must be patched to comply with FedRAMP requirements. This wiki page outlines the process for patching the environment.
|
|
|
|
|
|
------------
|
|
|
-Date: Wednesday, November 13, 2019 at 3:53 PM
|
|
|
-To: "Leonard, Wesley A." <wesley.a.leonard@accenturefederal.com>, "Waddle, Duane E." <duane.e.waddle@accenturefederal.com>
|
|
|
-Subject: November Patching for MDR
|
|
|
-
|
|
|
-Again, we are going to attempt to do much of the patching during business hours during the week. Everything - including Customer POPs - needs patches this time. We will be doing the servers in 2 waves.
|
|
|
+Email Template that needs to be sent out prior to patching and email addresses of individuals who should get the email.
|
|
|
+```
|
|
|
+Leonard, Wesley A. <wesley.a.leonard@accenturefederal.com>; Waddle, Duane E. <duane.e.waddle@accenturefederal.com>; Nair, Asha A. <asha.a.nair@accenturefederal.com>; Middleton, S. <s.middleton@accenturefederal.com>; Crawley, Angelita <angelita.crawley@accenturefederal.com>; Rivas, Gregory A. <gregory.a.rivas@accenturefederal.com>
|
|
|
+```
|
|
|
+SUBJECT: December Patching
|
|
|
+***
|
|
|
+
|
|
|
+It is time for monthly patching again. Patching is going to occur during business hours within the next week or two. Everything - including Customer POPs - needs patching. We will be doing the servers in 2 waves.
|
|
|
|
|
|
-Wave 1 is hot patching of all systems; this will fix the sudo and stage the kernel patches.
|
|
|
+Wave 1 is hot patching of all systems.
|
|
|
|
|
|
Wave 2 will be the needed reboots; as this is where we see the customer impact.
|
|
|
|
|
|
-In the slack channel, #mdr-patching. You can join that to get real-time announcements on what is going down and when.
|
|
|
-
|
|
|
-Rough preliminary plans are:
|
|
|
-
|
|
|
+For real-time patching announcements, join the slack channel #mdr-patching. Announcements will be posted in that channel on what is going down and when.
|
|
|
|
|
|
-Wed Nov 13:
|
|
|
-Moose and Internal infrastructure
|
|
|
-Wave 1
|
|
|
+Here is the proposed patching schedule:
|
|
|
+
|
|
|
+Wednesday Dec 11:
|
|
|
+* Moose and Internal infrastructure
|
|
|
+ * Wave 1
|
|
|
|
|
|
-Thursday Nov 14:
|
|
|
-Moose and Internal
|
|
|
-Wave 2
|
|
|
-All Customer PoP
|
|
|
-Wave 1 (AM)
|
|
|
-Wave 2 (PM)
|
|
|
-Monday Nov 18:
|
|
|
-All Customer MDR Cloud
|
|
|
-Wave 1
|
|
|
-All Search heads
|
|
|
-Wave 2 (PM)
|
|
|
-Tuesday Nov 19:
|
|
|
-All Remaining MDR Cloud
|
|
|
-Wave 2 (AM)
|
|
|
+Thursday Dec 12:
|
|
|
+* Moose and Internal
|
|
|
+ * Wave 2
|
|
|
+* All Customer PoP
|
|
|
+ * Wave 1 (AM)
|
|
|
+ * Wave 2 (PM)
|
|
|
+
|
|
|
+Monday Dec 16:
|
|
|
+* All Customer MDR Cloud
|
|
|
+ * Wave 1
|
|
|
+* All Search heads
|
|
|
+ * Wave 2 (PM)
|
|
|
+
|
|
|
+Tuesday Dec 17:
|
|
|
+* All Remaining MDR Cloud
|
|
|
+ * Wave 2 (AM)
|
|
|
|
|
|
-The Customer // User impact will be darning the reboots that is why I am doing them in batches so our total downtime is less.
|
|
|
+The customer and user impact will be during the reboots so they will be done in batches to reduce our total downtime is less.
|
|
|
+
|
|
|
+***
|
|
|
|
|
|
-----------------------
|
|
|
+
|
|
|
+```
|
|
|
|
|
|
|
|
|
|
|
|
@@ -94,7 +103,7 @@ salt -C 'nga*indexer-1*' cmd.run 'shutdown -r now'
|
|
|
#Ensure all have been restarted. Then done with NGA
|
|
|
salt -C '*nga*' cmd.run 'uptime'
|
|
|
|
|
|
-
|
|
|
+```
|
|
|
|
|
|
-------------------------------------------------
|
|
|
|
Brad Poulton