Merge pull request #266468 from rsgel/rigel-eventhub021524

Stacyrch140 · web-flow · commit cd71984dae82 · 2024-02-15T22:35:01.000-05:00
add event hub and provider roles
diff --git a/articles/chaos-studio/chaos-studio-fault-library.md b/articles/chaos-studio/chaos-studio-fault-library.md
@@ -12,9 +12,6 @@ ms.service: chaos-studio
 
 # Azure Chaos Studio fault and action library
 
-> [!CAUTION]
-> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
-
 The faults listed in this article are currently available for use. To understand which resource types are supported, see [Supported resource types and role assignments for Azure Chaos Studio](./chaos-studio-fault-providers.md).
 
 ## Time delay
@@ -51,7 +48,7 @@ The faults listed in this article are currently available for use. To understand
 | Target type | Microsoft-Agent |
 | Supported OS types | Windows, Linux. |
 | Description | Adds CPU pressure, up to the specified value, on the VM where this fault is injected during the fault action. The artificial CPU pressure is removed at the end of the duration or if the experiment is canceled. On Windows, the **% Processor Utility** performance counter is used at fault start to determine current CPU percentage, which is subtracted from the `pressureLevel` defined in the fault so that **% Processor Utility** hits approximately the `pressureLevel` defined in the fault parameters. |
-| Prerequisites | **Linux**: The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on Debian-based systems (including Ubuntu), Red Hat Enterprise Linux, CentOS, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
+| Prerequisites | **Linux**: The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on several operating systems including Debian-based (like Ubuntu), Red Hat Enterprise Linux, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
 | | **Windows**: None. |
 | Urn | urn:csci:microsoft:agent:cpuPressure/1.0 |
 | Parameters (key, value)  |
@@ -96,7 +93,7 @@ Known issues on Linux:
 | Target type | Microsoft-Agent |
 | Supported OS types | Windows, Linux. |
 | Description | Adds physical memory pressure, up to the specified value, on the VM where this fault is injected during the fault action. The artificial physical memory pressure is removed at the end of the duration or if the experiment is canceled. |
-| Prerequisites | **Linux**: The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on Debian-based systems (including Ubuntu), Red Hat Enterprise Linux, CentOS, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
+| Prerequisites | **Linux**: The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on several operating systems including Debian-based (like Ubuntu), Red Hat Enterprise Linux, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
 | | **Windows**: None. |
 | Urn | urn:csci:microsoft:agent:physicalMemoryPressure/1.0 |
 | Parameters (key, value) |  |
@@ -235,7 +232,7 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 | Target type | Microsoft-Agent |
 | Supported OS types | Linux |
 | Description | Uses stress-ng to apply pressure to the disk. One or more worker processes are spawned that perform I/O processes with temporary files. Pressure is added to the primary disk by default, or the disk specified with the targetTempDirectory parameter. For information on how pressure is applied, see the [stress-ng](https://wiki.ubuntu.com/Kernel/Reference/stress-ng) article. |
-| Prerequisites | The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on Debian-based systems (including Ubuntu), Red Hat Enterprise Linux, CentOS, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
+| Prerequisites | **Linux**: The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on several operating systems including Debian-based (like Ubuntu), Red Hat Enterprise Linux, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
 | Urn | urn:csci:microsoft:agent:linuxDiskIOPressure/1.1 |
 | Parameters (key, value) |  |
 | workerCount | Number of worker processes to run. Setting `workerCount` to 0 generated as many worker processes as there are number of processors. |
@@ -290,7 +287,7 @@ Currently, the Windows agent doesn't reduce memory pressure when other applicati
 | Target type | Microsoft-Agent |
 | Supported OS types | Linux |
 | Description | Runs any stress-ng command by passing arguments directly to stress-ng. Useful when one of the predefined faults for stress-ng doesn't meet your needs. |
-| Prerequisites | The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on Debian-based systems (including Ubuntu), Red Hat Enterprise Linux, CentOS, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
+| Prerequisites | **Linux**: The **stress-ng** utility needs to be installed. This happens automatically as part of agent installation, using the default package manager, on several operating systems including Debian-based (like Ubuntu), Red Hat Enterprise Linux, and OpenSUSE. For other distributions, you must install **stress-ng** manually. |
 | Urn | urn:csci:microsoft:agent:stressNg/1.0 |
 | Parameters (key, value) |  |
 | stressNgArguments | One or more arguments to pass to the stress-ng process. For information on possible stress-ng arguments, see the [stress-ng](https://wiki.ubuntu.com/Kernel/Reference/stress-ng) article. |
@@ -1819,3 +1816,42 @@ Currently, only virtual machine scale sets configured with the **Uniform** orche
 ### Limitations
 
 * A maximum of 1000 topic entities can be passed to this fault.
+
+## Change Event Hub State
+	
+| Property  | Value |
+| ---- | --- |
+| Capability name | ChangeEventHubState-1.0 |
+| Target type | Microsoft-EventHub |
+| Description | Sets individual event hubs to the desired state within an Azure Event Hubs namespace. You can affect specific event hub names or use “*” to affect all within the namespace. This can help test your messaging infrastructure for maintenance or failure scenarios. This is a discrete fault, so the entity will not be returned to the starting state automatically. |
+| Prerequisites | An Azure Event Hubs namespace with at least one [event hub entity](../event-hubs/event-hubs-create.md). |
+| Urn | urn:csci:microsoft:eventHub:changeEventHubState/1.0 |
+| Fault type | Discrete. |
+| Parameters (key, value) | |
+| desiredState | The desired state for the targeted event hubs. The possible states are Active, Disabled, and SendDisabled. |
+| eventHubs | A comma-separated list of the event hub names within the targeted namespace. Use "*" to affect all entities within the namespace. |
+
+### Sample JSON
+
+```json
+{
+  "name": "Branch1",
+    "actions": [
+        {
+            "selectorId": "Selector1",
+            "type": "discrete",
+            "parameters": [
+                {
+                    "key": "eventhubs",
+                    "value": "[\"*\"]"
+                },
+                {
+                    "key": "desiredState",
+                    "value": "Disabled"
+                }
+            ],
+            "name": "urn:csci:microsoft:eventHub:changeEventHubState/1.0"
+        }
+    ]
+}
+```
diff --git a/articles/chaos-studio/chaos-studio-fault-providers.md b/articles/chaos-studio/chaos-studio-fault-providers.md
@@ -14,17 +14,21 @@ ms.service: chaos-studio
 
 The following table lists the supported resource types for faults, the target types, and suggested roles to use when you give an experiment permission to a resource of that type.
 
+More information about role assignments can be found on the [Azure built-in roles page](../role-based-access-control/built-in-roles.md).
+
 | Resource type                                                    | Target name/type                          | Suggested role assignment                   |
 |-------------------------------------------------------------------|--------------------------------------------|----------------------------------------------|
-| Microsoft.Cache/Redis (service-direct)                           | Microsoft-AzureCacheForRedis              | Redis Cache Contributor                     |
-| Microsoft.ClassicCompute/domainNames (service-direct)            | Microsoft-DomainNames                     | Classic Virtual Machine Contributor         |
-| Microsoft.Compute/virtualMachines (agent-based)                  | Microsoft-Agent                           | Reader                                      |
-| Microsoft.Compute/virtualMachineScaleSets (agent-based)          | Microsoft-Agent                           | Reader                                      |
-| Microsoft.Compute/virtualMachines (service-direct)               | Microsoft-VirtualMachine                  | Virtual Machine Contributor                 |
-| Microsoft.Compute/virtualMachineScaleSets (service-direct)       | Microsoft-VirtualMachineScaleSet          | Virtual Machine Contributor                 |
-| Microsoft.ContainerService/managedClusters (service-direct)      | Microsoft-AzureKubernetesServiceChaosMesh | Azure Kubernetes Service Cluster Admin Role |
-| Microsoft.DocumentDb/databaseAccounts (CosmosDB, service-direct) | Microsoft-CosmosDB                        | Azure Cosmos DB Operator                          |
-| Microsoft.Insights/autoscalesettings (service-direct)            | Microsoft-AutoScaleSettings               | Web Plan Contributor                        |
-| Microsoft.KeyVault/vaults (service-direct)                       | Microsoft-KeyVault                        | Azure Key Vault Contributor                       |
-| Microsoft.Network/networkSecurityGroups (service-direct)         | Microsoft-NetworkSecurityGroup            | Network Contributor                         |
-| Microsoft.Web/sites (service-direct)                             | Microsoft-AppService                      | Website Contributor                         |
+| Microsoft.Cache/Redis (service-direct)                           | Microsoft-AzureCacheForRedis              | [Redis Cache Contributor](../role-based-access-control/built-in-roles.md#redis-cache-contributor)                     |
+| Microsoft.ClassicCompute/domainNames (service-direct)            | Microsoft-DomainNames                     | [Classic Virtual Machine Contributor](../role-based-access-control/built-in-roles.md#classic-virtual-machine-contributor)       |
+| Microsoft.Compute/virtualMachines (agent-based)                  | Microsoft-Agent                           | [Reader](../role-based-access-control/built-in-roles.md#reader)                                      |
+| Microsoft.Compute/virtualMachineScaleSets (agent-based)          | Microsoft-Agent                           | [Reader](../role-based-access-control/built-in-roles.md#reader)                                      |
+| Microsoft.Compute/virtualMachines (service-direct)               | Microsoft-VirtualMachine                  | [Virtual Machine Contributor](../role-based-access-control/built-in-roles.md#virtual-machine-contributor)                 |
+| Microsoft.Compute/virtualMachineScaleSets (service-direct)       | Microsoft-VirtualMachineScaleSet          | [Virtual Machine Contributor](../role-based-access-control/built-in-roles.md#virtual-machine-contributor)                 |
+| Microsoft.ContainerService/managedClusters (service-direct)      | Microsoft-AzureKubernetesServiceChaosMesh | [Azure Kubernetes Service Cluster Admin Role](../role-based-access-control/built-in-roles.md#azure-kubernetes-service-cluster-admin-role) |
+| Microsoft.DocumentDb/databaseAccounts (Cosmos DB, service-direct) | Microsoft-Cosmos DB                        | [Azure Cosmos DB Operator](../role-based-access-control/built-in-roles.md#cosmos-db-operator)                          |
+| Microsoft.Insights/autoscalesettings (service-direct)            | Microsoft-AutoScaleSettings               | [Web Plan Contributor](../role-based-access-control/built-in-roles.md#web-plan-contributor)                        |
+| Microsoft.KeyVault/vaults (service-direct)                       | Microsoft-KeyVault                        | [Azure Key Vault Contributor](../role-based-access-control/built-in-roles.md#key-vault-contributor)                       |
+| Microsoft.Network/networkSecurityGroups (service-direct)         | Microsoft-NetworkSecurityGroup            | [Network Contributor](../role-based-access-control/built-in-roles.md#network-contributor)                         |
+| Microsoft.Web/sites (service-direct)                             | Microsoft-AppService                      | [Website Contributor](../role-based-access-control/built-in-roles.md#website-contributor)                         |
+| Microsoft.ServiceBus/namespaces (service-direct)                 | Microsoft-ServiceBus                      | [Azure Service Bus Data Owner](../role-based-access-control/built-in-roles.md#azure-service-bus-data-owner)                         |
+| Microsoft.EventHub/namespaces (service-direct)                   | Microsoft-EventHub                        | [Azure Event Hubs Data Owner](../role-based-access-control/built-in-roles.md#azure-event-hubs-data-owner)                         |
diff --git a/articles/chaos-studio/chaos-studio-versions.md b/articles/chaos-studio/chaos-studio-versions.md
@@ -49,6 +49,7 @@ Chaos Studio currently tests with the following version combinations.
 
 | Chaos Studio fault version | Kubernetes version | Chaos Mesh version | Notes |
 |:---:|:---:|:---:|:---:|
+| 2.1 | 1.27 | 2.6.3 | |
 | 2.1 | 1.25.11 | 2.5.1 | |
 
 The *Chaos Studio fault version* column refers to the individual fault version for each AKS Chaos Mesh fault used in the experiment JSON, for example `urn:csci:microsoft:azureKubernetesServiceChaosMesh:podChaos/2.1`. If a past version of the corresponding Chaos Studio fault remains available from the Chaos Studio API (for example, `...podChaos/1.0`), it is within support.
