refactors directory and file structure

Signed-off-by: neelanjan00 <neelanjan.manna@harness.io>
This commit is contained in:
neelanjan00
2023-06-05 13:15:56 +05:30
parent 9bf371a651
commit ae8467237a
840 changed files with 6787 additions and 43442 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 73 KiB

View File

@@ -0,0 +1,28 @@
---
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
name: vmware-engine
namespace: default
spec:
engineState: 'active'
chaosServiceAccount: litmus-admin
experiments:
- name: vmware-vm-poweroff
spec:
components:
env:
# set chaos duration (in sec) as desired
- name: TOTAL_CHAOS_DURATION
value: '30'
# set chaos interval (in sec) as desired
- name: CHAOS_INTERVAL
value: '30'
# provide VM MOIDs as comma separated values
- name: APP_VM_MOIDS
value: ''
- name: SEQUENCE
value: 'parallel'

View File

@@ -0,0 +1,110 @@
---
apiVersion: litmuschaos.io/v1alpha1
description:
message: |
It poweroff the VMware instance for a certain chaos duration.
kind: ChaosExperiment
metadata:
name: vmware-vm-poweroff
labels:
name: vmware-vm-poweroff
app.kubernetes.io/part-of: litmus
app.kubernetes.io/component: chaosexperiment
app.kubernetes.io/version: ci
spec:
definition:
scope: Namespaced
permissions:
# Create and monitor the experiment & helper pods
- apiGroups: [""]
resources: ["pods"]
verbs: ["create", "delete", "get", "list", "patch", "update", "deletecollection"]
# Performs CRUD operations on the events inside chaosengine and chaosresult
- apiGroups: [""]
resources: ["events"]
verbs: ["create", "get", "list", "patch", "update"]
# Fetch configmaps details and mount it to the experiment pod (if specified)
- apiGroups: [""]
resources: ["configmaps"]
verbs: ["get", "list"]
# Track and get the runner, experiment, and helper pods log
- apiGroups: [""]
resources: ["pods/log"]
verbs: ["get", "list", "watch"]
# for creating and managing to execute commands inside target container
- apiGroups: [""]
resources: ["pods/exec"]
verbs: ["get", "list", "create"]
# deriving the parent/owner details of the pod(if parent is anyof {deployment, statefulset, daemonsets})
- apiGroups: ["apps"]
resources: ["deployments", "statefulsets", "replicasets", "daemonsets"]
verbs: ["list", "get"]
# deriving the parent/owner details of the pod(if parent is deploymentConfig)
- apiGroups: ["apps.openshift.io"]
resources: ["deploymentconfigs"]
verbs: ["list", "get"]
# deriving the parent/owner details of the pod(if parent is deploymentConfig)
- apiGroups: [""]
resources: ["replicationcontrollers"]
verbs: ["get", "list"]
# deriving the parent/owner details of the pod(if parent is argo-rollouts)
- apiGroups: ["argoproj.io"]
resources: ["rollouts"]
verbs: ["list", "get"]
# for configuring and monitor the experiment job by the chaos-runner pod
- apiGroups: ["batch"]
resources: ["jobs"]
verbs: ["create", "list", "get", "delete", "deletecollection"]
# for creation, status polling and deletion of litmus chaos resources used within a chaos workflow
- apiGroups: ["litmuschaos.io"]
resources: ["chaosengines", "chaosexperiments", "chaosresults"]
verbs: ["create", "list", "get", "patch", "update", "delete"]
image: "chaosnative/go-runner:ci"
imagePullPolicy: Always
args:
- -c
- ./experiments -name vm-poweroff
command:
- /bin/bash
env:
- name: TOTAL_CHAOS_DURATION
value: '30'
- name: CHAOS_INTERVAL
value: '10'
- name: RAMP_TIME
value: ''
- name: VCENTERSERVER
valueFrom:
secretKeyRef:
name: vcenter-secret
key: VCENTERSERVER
- name: VCENTERUSER
valueFrom:
secretKeyRef:
name: vcenter-secret
key: VCENTERUSER
- name: VCENTERPASS
valueFrom:
secretKeyRef:
name: vcenter-secret
key: VCENTERPASS
- name: APP_VM_MOIDS
value: ''
- name: SEQUENCE
value: 'parallel'
- name: DEFAULT_HEALTH_CHECK
value: 'false'
labels:
name: vmware-vm-poweroff
app.kubernetes.io/part-of: litmus
app.kubernetes.io/component: experiment-job
app.kubernetes.io/version: ci

View File

@@ -0,0 +1,29 @@
---
apiVersion: litmuschaos.io/v1alpha1
kind: ChartServiceVersion
metadata:
createdAt: 2022-07-19T10:28:08Z
name: vmware-vm-poweroff
version: 0.1.0
annotations:
categories: VMWare
vendor: Harness
spec:
displayName: VMware VM Power Off
categoryDescription: |
vm-poweroff fault Power-Offs the target VMs for a certain chaos duration and then bring back to Power-On state.
- This fault helps verify the resiliency of the process/application that are running on the target instance.
keywords:
- VMware
platforms:
- VMware
minKubeVersion: 1.12.0
labels:
app.kubernetes.io/component: chartserviceversion
app.kubernetes.io/version: ci
links:
- name: Documentation
url: https://docs.harness.io/category/kl0mxwpfw1-hce-category
icon:
- url:
mediatype: ""

View File

@@ -0,0 +1,24 @@
---
apiVersion: litmuschaos.io/v1alpha1
kind: ChartServiceVersion
metadata:
name: vmware
version: 0.1.0
annotations:
categories: VMware
chartDescription: Injects faults on VMware system
executionPlane: "kubernetes"
spec:
displayName: VMware
categoryDescription: >
VMware chaos contains different experiments for VMware platform. It uses VMware apis to carry out the fault logic for different components.
faults:
- name: vm-poweroff
description: It injects power-off chaos on VMware VMs.
displayName: "VMware VM Poweroff"
keywords:
- VMware
minKubeVersion: 1.12.0
icon:
- url: https://raw.githubusercontent.com/litmuschaos/charthub.litmuschaos.io/master/public/litmus.ico
mediatype: image/png

View File

@@ -0,0 +1,6 @@
---
packageName: vmware
faults:
- name: vm-poweroff
CSV: vm-poweroff.chartserviceversion.yaml
desc: "vm-poweroff"