(refactor): Changing name of cpu_hog experiment to node_cpu_hog (#129)

Signed-off-by: shubhamchaudhary <shubham.chaudhary@mayadata.io>

charts/generic/node-cpu-hog/experiment.yaml

@@ -0,0 +1,65 @@
+apiVersion: litmuschaos.io/v1alpha1
+description:
+  message: |
+    Give a cpu spike on a node belonging to a deployment
+kind: ChaosExperiment
+metadata:
+  name: node-cpu-hog
+  version: 0.1.8
+spec:
+  definition:
+    scope: Cluster
+    permissions:
+      - apiGroups:
+          - ""
+          - "batch"
+          - "apps"
+          - "litmuschaos.io"
+        resources:
+          - "daemonsets"
+          - "jobs"
+          - "pods"
+          - "pods/exec"
+          - "chaosengines"
+          - "chaosexperiments"
+          - "chaosresults"
+        verbs:
+          - "create"
+          - "list"
+          - "get"
+          - "patch"
+          - "update"
+          - "delete"
+      - apiGroups:
+          - ""
+        resources: 
+          - "nodes"
+        verbs :
+          - "get"
+          - "list"
+    image: "litmuschaos/ansible-runner:latest"
+    args:
+    - -c
+    - ansible-playbook ./experiments/generic/node_cpu_hog/node_cpu_hog_ansible_logic.yml -i /etc/ansible/hosts -vv; exit 0
+    command:
+    - /bin/bash
+    env:
+
+    - name: ANSIBLE_STDOUT_CALLBACK
+      value: 'default'
+
+    - name: TOTAL_CHAOS_DURATION
+      value: '60'
+
+    # Period to wait before injection of chaos in sec
+    - name: RAMP_TIME
+      value: ''
+
+    - name: PLATFORM
+      value: 'GKE'
+
+    - name: LIB
+      value: ''
+      
+    labels:
+      name: node-cpu-hog

charts/generic/node-cpu-hog/node-cpu-hog.chartserviceversion.yaml

@@ -0,0 +1,42 @@
+apiVersion: litmuchaos.io/v1alpha1
+kind: ChartServiceVersion
+metadata:
+  name: node-cpu-hog
+  version: 0.0.7
+  annotations:
+    categories: Kubernetes
+    vendor: CNCF
+    createdAt: 2019-08-12T10:28:08Z
+    support: https://slack.kubernetes.io/
+spec:
+  displayName: node-cpu-hog
+  categoryDescription: |
+    Node CPU hog contains chaos to disrupt state of kubernetes resources. Experiments can inject a cpu skipe on a node where the application pod is scheduled.
+    - Causes (forced/graceful) cpu hog on a perticular node where the application deployment is available.
+    - After test the recovery should be manual of the application pod and node in case they are not in appropriate state.
+ 
+  keywords:
+    - Kubernetes
+    - CPU
+    - State 
+  platforms:
+    - GKE
+  maturity: alpha
+  chaosType: infra
+  maintainers:
+    - name: ksatchit
+      email: karthik.s@mayadata.io
+  minKubeVersion: 1.12.0
+  provider:
+    name: Mayadata
+  links:
+    - name: Source Code
+      url: https://github.com/litmuschaos/litmus/tree/master/experiments/generic/node_cpu_hog
+    - name: Documentation
+      url: https://docs.litmuschaos.io/docs/node-cpu-hog/
+    - name: Video
+      url:
+  icon: 
+    - url: 
+      mediatype: ""
+  chaosexpcrdlink: https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/generic/node-cpu-hog/experiment.yaml