VMware Windows Blackhole Chaos

VMware Windows Blackhole Chaos simulates a network blackhole scenario on Windows OS based VMware VM.

• It checks the performance of the application running on the VMware Windows VMs under network blackhole conditions.

Use cases

• VMware Windows Blackhole Chaos determines the resilience of an application when a network blackhole scenario is simulated on a VMware Windows virtual machine.
• VMware Windows Blackhole Chaos simulates the situation of network isolation for processes running on the application, which degrades their performance.
• It also helps verify the application's ability to handle network failures and its failover mechanisms.

note

• Kubernetes > 1.16 is required to execute this fault.
• Execution plane should be connected to vCenter and host vCenter on port 443.
• VMware tool should be installed on the target VM with remote execution enabled.
• Adequate vCenter permissions should be provided to access the hosts and the VMs.
• Ensure the firewall is active and permissions to modify its rules are granted. Consider using the built-in Administrator user. Learn how to enable it in Windows.
• The VM should be in a healthy state before and after injecting chaos.
• Kubernetes secret has to be created that has the Vcenter credentials in the CHAOS_NAMESPACE.
• VM credentials can be passed as secrets or as a chaos enginer environment variable.

apiVersion: v1
kind: Secret
metadata:
  name: vcenter-secret
  namespace: litmus
type: Opaque
stringData:
    VCENTERSERVER: XXXXXXXXXXX
    VCENTERUSER: XXXXXXXXXXXXX
    VCENTERPASS: XXXXXXXXXXXXX

Fault tunables

Mandatory fields

Variables	Description	Notes
VM_NAME	Name of the target VM.	For example, win-vm-1
VM_USER_NAME	Username of the target VM.	For example, vm-user.
VM_PASSWORD	User password for the target VM.	For example, 1234. Note: You can take the password from secret as well.

<h3>Optional fields</h3>
<table>
  <tr>
    <th> Variables </th>
    <th> Description </th>
    <th> Notes </th>
  </tr>
  <tr>
    <td> DESTINATION_HOSTS </td>
    <td> Comma separated list of destination hosts to block. </td>
    <td> For example, <code>github.com,harness.io</code> </td>
  </tr>
  <tr>
    <td> IP_ADDRESSES </td>
    <td> Comma separated list of IP addresses to block. </td>
    <td> For example, <code>10.0.0.1,10.0.0.2</code> </td>
  </tr>
  <tr>
    <td> TOTAL_CHAOS_DURATION </td>
    <td> Duration that you specify, through which chaos is injected into the target resource (in seconds).</td>
    <td> Default: 60s. </td>
  </tr>
  <tr>
    <td> RAMP_TIME </td>
    <td> Period to wait before and after injecting chaos (in seconds). </td>
    <td> Default: 0s. </td>
  </tr>
  <tr>
    <td> SEQUENCE </td>
    <td> Sequence of chaos execution for multiple instances. </td>
    <td> Default: parallel. Supports serial sequence as well. </td>
  </tr>
</table>

Destination Hosts

The DESTINATION_HOSTS environment variable specifies the destination hosts to block on the target Windows VM.

Use the following example to specify destination hosts:

apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: vmware-windows-blackhole-chaos
    spec:
      components:
        env:
        # Name of the VM
        - name: VM_NAME
          value: 'test-vm-01'
       # Destination hosts to block
        - name: DESTINATION_HOSTS 
          value: 'github.com'

IP Addresses

The IP_ADDRESSES environment variable specifies the IP addresses to block on the target Windows VM.

Use the following example to specify IP addresses:

apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: vmware-windows-blackhole-chaos
    spec:
      components:
        env:
        # Name of the VM
        - name: VM_NAME
          value: 'test-vm-01'
       # IP addresses to block
        - name: IP_ADDRESSES 
          value: '10.0.0.1,10.0.0.2'