Ibm plugin node scenario (krkn-chaos#417)

* Node scenarios for ibmcloud * adding openshift check info
chaitanyaenr · May 9, 2023 · 16ea18c · 16ea18c
1 parent 1ab9475
commit 16ea18c
Show file tree

Hide file tree

Showing 12 changed files with 2,598 additions and 41 deletions.
diff --git a/config/config.yaml b/config/config.yaml
@@ -17,6 +17,7 @@ kraken:
             - scenarios/openshift/etcd.yml
             - scenarios/openshift/regex_openshift_pod_kill.yml
             - scenarios/openshift/vmware_node_scenarios.yml
+            - scenarios/openshift/ibmcloud_node_scenarios.yml
             - scenarios/openshift/network_chaos_ingress.yml
         -   node_scenarios:                                # List of chaos node scenarios to load
             -   scenarios/openshift/node_scenarios_example.yml

diff --git a/docs/cloud_setup.md b/docs/cloud_setup.md
@@ -1,11 +1,12 @@
 Supported Cloud Providers:
 
-* [AWS](#aws)
-* [GCP](#gcp)
-* [Openstack](#openstack)
-* [Azure](#azure)
-* [Alibaba](#alibaba)
-* [VMware](#vmware)
+- [AWS](#aws)
+- [GCP](#gcp)
+- [Openstack](#openstack)
+- [Azure](#azure)
+- [Alibaba](#alibaba)
+- [VMware](#vmware)
+- [IBMCloud](#ibmcloud)
 
 ## AWS
 
@@ -65,4 +66,24 @@ Set the following environment variables
 
 3. ```export VSPHERE_PASSWORD=<vSphere_client_password>```
 
-These are the credentials that you would normally use to access the vSphere client.
+These are the credentials that you would normally use to access the vSphere client.
+
+
+## IBMCloud
+If no api key is set up with proper VPC resource permissions, use the following to create: 
+* Access group
+* Service id with the following access
+  * With policy **VPC Infrastructure Services**
+  * Resources = All
+  * Roles: 
+    * Editor
+    * Administrator 
+    * Operator  
+    * Viewer
+* API Key
+
+Set the following environment variables
+
+1. ```export IBMC_URL=https://<region>.iaas.cloud.ibm.com/v1```
+
+2. ```export IBMC_APIKEY=<ibmcloud_api_key>```
diff --git a/docs/node_scenarios.md b/docs/node_scenarios.md
@@ -76,6 +76,42 @@ How to set up Alibaba cli to run node scenarios is defined [here](cloud_setup.md
 #### VMware
 How to set up VMware vSphere to run node scenarios is defined [here](cloud_setup.md#vmware)
 
+This cloud type uses a different configuration style, see actions below and [example config file](../scenarios/openshift/vmware_node_scenarios.yml)
+
+*vmware-node-terminate, vmware-node-reboot, vmware-node-stop, vmware-node-start*
+
+#### IBMCloud
+How to set up IBMCloud to run node scenarios is defined [here](cloud_setup.md#ibmcloud)
+
+This cloud type uses a different configuration style, see actions below and [example config file](../scenarios/openshift/ibmcloud_node_scenarios.yml)
+
+*ibmcloud-node-terminate, ibmcloud-node-reboot, ibmcloud-node-stop, ibmcloud-node-start
+*
+
+
+#### IBMCloud and Vmware example 
+
+
+```
+- id: ibmcloud-node-stop
+  config:
+    name: "<node_name>"        
+    label_selector: "node-role.kubernetes.io/worker"    # When node_name is not specified, a node with matching label_selector is selected for node chaos scenario injection 
+    runs: 1                             # Number of times to inject each scenario under actions (will perform on same node each time)                                                           
+    instance_count: 1                   # Number of nodes to perform action/select that match the label selector                                             
+    timeout: 30                        # Duration to wait for completion of node scenario injection
+    skip_openshift_checks: False       # Set to True if you don't want to wait for the status of the nodes to change on OpenShift before passing the scenario 
+- id: ibmcloud-node-start
+  config:
+    name: "<node_name>" #Same name as before       
+    label_selector: "node-role.kubernetes.io/worker"    # When node_name is not specified, a node with matching label_selector is selected for node chaos scenario injection 
+    runs: 1                             # Number of times to inject each scenario under actions (will perform on same node each time)                                                           
+    instance_count: 1                   # Number of nodes to perform action/select that match the label selector                                             
+    timeout: 30                        # Duration to wait for completion of node scenario injection
+    skip_openshift_checks: False       # Set to True if you don't want to wait for the status of the nodes to change on OpenShift before passing the scenario 
+    ```
+
+
 
 #### General
 

diff --git a/kraken/plugins/__init__.py b/kraken/plugins/__init__.py
@@ -7,8 +7,8 @@
 
 from arcaflow_plugin_sdk import schema, serialization, jsonschema
 from arcaflow_plugin_kill_pod import kill_pods, wait_for_pods
-
-import kraken.plugins.vmware.vmware_plugin as vmware_plugin
+import kraken.plugins.node_scenarios.vmware_plugin as vmware_plugin
+import kraken.plugins.node_scenarios.ibmcloud_plugin as ibmcloud_plugin
 from kraken.plugins.run_python_plugin import run_python_file
 from kraken.plugins.network.ingress_shaping import network_chaos
 
@@ -182,7 +182,25 @@ def json_schema(self):
             ]
         ),
         PluginStep(
-            network_chaos,
+            ibmcloud_plugin.node_start,
+            [
+                "error"
+            ]
+        ),
+        PluginStep(
+            ibmcloud_plugin.node_stop,
+            [
+                "error"
+            ]
+        ),
+        PluginStep(
+            ibmcloud_plugin.node_reboot,
+            [
+                "error"
+            ]
+        ),
+        PluginStep(
+            ibmcloud_plugin.node_terminate,
             [
                 "error"
             ]