Bump ws from 1.1.1 to 3.3.3

Bumps [ws](https://github.com/websockets/ws) from 1.1.1 to 3.3.3.
- [Release notes](https://github.com/websockets/ws/releases)
- [Commits](https://github.com/websockets/ws/compare/1.1.1...3.3.3)

Signed-off-by: dependabot[bot] <support@github.com>

README.md

@@ -48,9 +48,16 @@ Incidents are plain markdown files inside the `site/content/incidents` directory
 
 ### Creating new incidents
 
-Duplicate an existing incident from site/content/incidents. You can use one of the following severities:
+Adding incidents to your status page is as simple as adding a new document to the incidents collection.
+Create a new incident using npm:
 
-["under-maintenance", "degraded-performance", "partial-outage", "major-outage"] 
+```
+npm run new-incident
+```
+
+You'll be asked a series of questions about the incident, then Hugo will generate a new file pre-filled with your responses.
+
+After explaining the current situation in the incident, you can just push the file to GitHub. Netlify will deploy the indicent announcement for you in a matter of seconds.
 
 ### Resolving incidents
 

package.json

@@ -24,15 +24,15 @@
     "eslint": "^5.13.0",
     "eslint-plugin-import": "^2.16.0",
     "exports-loader": "^0.7.0",
-    "gulp": "^4.0.2",
+    "gulp": "^4.0.0",
     "gulp-babel": "^8.0.0-beta.2",
-    "gulp-postcss": "^9.0.1",
+    "gulp-postcss": "^8.0.0",
     "imports-loader": "^0.8.0",
     "inquirer": "^6.2.2",
     "lodash.kebabcase": "^4.1.1",
-    "postcss-import": "^15.1.0",
-    "postcss-loader": "^7.3.3",
-    "postcss-preset-env": "^9.2.0",
+    "postcss-import": "^12.0.1",
+    "postcss-loader": "^3.0.0",
+    "postcss-preset-env": "^6.5.0",
     "tomlify-j0.4": "^3.0.0",
     "tomljs": "^0.1.3"
   },
@@ -41,8 +41,8 @@
   },
   "devDependencies": {
     "babel-core": "^6.26.3",
-    "babel-loader": "^9.1.3",
+    "babel-loader": "^6.4.1",
     "babel-preset-env": "^1.7.0",
-    "webpack": "^5.89.0"
+    "webpack": "^1.15.0"
   }
 }

site/config.toml

@@ -13,4 +13,4 @@ title = "Spearhead Cloud Status"
 # You'll be able to change their status every time
 # you open or update an incident.
 # Replace these examples with your own system names.
-systems = ["EU-RO-1 DC", "CloudAPI", "CNS", "Docker API", "Customer Portal", "docs.spearhead.cloud", "Tenant Machines"]
+systems = ["EU-RO-1 DC", "CloudAPI", "DNS",  "Customer Portal", "docs.spearhead.cloud"]

site/content/incidents/1309 wedged node.md

@@ -1,13 +0,0 @@
-+++
-title = "Compute Node Network Connectivity"
-date = 2022-09-13T07:45:00.000Z
-severity = "partial-outage"
-affectedsystems = [
-  "Tenant Machines"
-]
-resolved = true
-
-+++
-One of our compute nodes entered into a faulty state. We have gathered logs and debug information to continue our analysis. 
-
-**Update**: Server reboot has completed succesfully and all systems are operational. {{< track "2022-09-13T08:00:00.000Z" >}}

site/content/incidents/16102023-upstream-network.md

@@ -1,18 +0,0 @@
-+++
-title = "Intermittent network connectivity"
-date = 2023-10-16T09:32:00.000Z
-severity = "partial-outage"
-affectedsystems = [
-  "EU-RO-1 DC",
-  "Tenant Machines"
-]
-
-resolved = true 
-
-+++
-Our upstream datacenter provider is experiencing a DDoS attack which has affected some of our prefixes. Bot partiees (Spearhead and our Datacenter operator) are working to mitigate the effects of this attack. We can expect intermittent access to the spearhead.cloud resources while we work with our providers to stop the attack of find other measures to bring stability back to the platform.
-
-**Update**: Network connectivity has stabilised and we are continuiing to monitor the situation. {{< track "2023-10-16T09:48:00.000Z" >}}
-
-
-**Update**: Our upstream network provider has confirmed that the large scale (90Gbps) DDoS attac has been mitigated. All network operations have resumed to normal operations and we do not expect any further issues. We apologise for the inconveniece. {{< track "2023-10-16T12:31:00.000Z" >}}

site/content/incidents/19.09.22 wedged node.md

@@ -1,13 +0,0 @@
-+++
-title = "Compute Node Network Connectivity"
-date = 2022-09-19T07:37:00.000Z
-severity = "partial-outage"
-affectedsystems = [
-  "Tenant Machines"
-]
-resolved = true
-
-+++
-One of our compute nodes entered into a faulty state. We have gathered logs and debug information to continue our analysis. This is a recurring issue that is under continuous investigation
-
-**Update**: Server reboot has completed succesfully and all systems are operational. {{< track "2022-09-10T04:00:00.000Z" >}}

site/content/incidents/23.09.22 wedged node.md

@@ -1,15 +0,0 @@
-+++
-title = "Compute Node Network Connectivity"
-date = 2022-09-23T14:35:00.000Z
-severity = "partial-outage"
-affectedsystems = [
-  "Tenant Machines"
-]
-resolved = true
-
-+++
-One of our compute nodes has entered into a faulty state. We are gathering logs and debug information to continue our analysis. This is a recurring issue that is under continuous investigation.
-
-**Update**: We are generating a crash dump for this incident and will schedule an immediate reboot of the server. {{< track "2022-09-23T14:38:00.000Z" >}}
-
-**Update**: We have obtained a crash dump and all systems are operating normally again. {{< track "2022-09-23T15:00:00.000Z" >}}

site/content/incidents/compute-node-networking.md

@@ -1,16 +0,0 @@
-+++
-title = "compute node network connectivity"
-date = 2022-08-29T10:35:00.000Z
-severity = "partial-outage"
-affectedsystems = [
-  "EU-RO-1 DC",
-  "Tenant Machines",
-]
-resolved = true
-
-+++
-Our monitoring has identified intermittent (flapping) network access to customer machines on one of our compute nodes. This is limited to a single compute node and the symptoms are intermittent network connectivity (resulting in dropped sessions).
-
-**Update**: A reboot of the compute node has restored all affected customer machines. {{< track "2022-08-18T14:34:00.000Z" >}}
-
-**Update**: As of our current understanding we cannot replicate this issue and therefore difficult to troubeleshoot. A reboot has been applied and the systems are behaving normally. We are continuing our efforts to reproduce this issue and threfore find a permanent solution. {{< track "2022-08-18T20:34:00.000Z" >}}

site/content/incidents/intermittent-network.md

@@ -1,14 +0,0 @@
-+++
-title = "intermittent network connectivity"
-date = 2020-11-18T18:15:00.000Z
-severity = "under-maintenance"
-affectedsystems = [
-  "EU-RO-1 DC",
-  "CloudAPI"
-]
-resolved = true
-
-+++
-One of our management servers requires a reboot in order to perform an OS update. The update is expect to last several minutes during which time our API's will be unavailable.
-
-**Update**: Server reboot has completed succesfully and all systems are operational. {{< track "2020-11-18T18:34:00.000Z" >}}