Merge pull request #12 from kianaharris4/esa-pp

bash cmd incorrect + updating EE instructions

Author: sethmanheim

articles/azure-arc/edge-storage-accelerator/attach-app.md

@@ -10,12 +10,12 @@ zone_pivot_groups: attach-app
 
 # Attach your application (preview)
 
-This article assumes you created a Persistent Volume (PV) and a Persistent Volume Claim (PVC). For information about creating a PV, see [Create a persistent volume](create-pv.md). For information about PVCs, see [Create a Persistent Volume Claim](create-pvc.md).
+This article assumes you created a Persistent Volume (PV) and a Persistent Volume Claim (PVC). For information about creating a PV, see [Create a persistent volume](create-pv.md). For information about creating a PVC, see [Create a Persistent Volume Claim](create-pvc.md).
 
 ::: zone pivot="attach-iot-op"
 ## Configure the Azure IoT Operations data processor
 
-When you use Azure IoT Operations (AIO), the data processor is spawned without any mounts for Edge Storage Accelerator. You can perform the following tasks:
+When you use Azure IoT Operations (AIO), the Data Processor is spawned without any mounts for Edge Storage Accelerator. You can perform the following tasks:
 
 - Add a mount for the Edge Storage Accelerator PVC you created previously.
 - Reconfigure all pipelines' output stage to output to the Edge Storage Accelerator mount you just created.  
@@ -152,7 +152,7 @@ These pods are part of a **statefulSet**. You can't edit the statefulSet in plac
 1. Run the following command and replace `POD_NAME_HERE` with your copied value from the previous step:
 
    ```bash
-   kubectl exec -it POD_NAME_HERE bash
+   kubectl exec -it POD_NAME_HERE -- bash
    ```
 
 1. Change directories into the `/mnt/blob` mount path as specified from your `configPod.yaml`.

articles/azure-arc/edge-storage-accelerator/create-pvc.md

@@ -34,8 +34,8 @@ This size does not affect the ceiling of blob storage used in the cloud to suppo
                storage: 5Gi 
        storageClassName: esa
        volumeMode: Filesystem
-       ### This name is from your PV config ###
-       volumeName: INSERT_NAME_FROM_PV
+       ### This name references your PV name in your PV config ###
+       volumeName: INSERT_YOUR_PV_NAME
    status: 
        accessModes: 
            - ReadWriteMany 

articles/azure-arc/edge-storage-accelerator/multi-node-cluster.md

@@ -33,21 +33,20 @@ This section describes how to prepare Linux with AKS Edge Essentials if you run
 1. On each node in your cluster, set the number of **HugePages** to 512 using the following command:
 
    ```bash
-   HUGEPAGES_NR=512
-   echo $HUGEPAGES_NR | sudo tee /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
-   echo "vm.nr_hugepages=$HUGEPAGES_NR" | sudo tee /etc/sysctl.d/99-hugepages.conf
+   Invoke-AksEdgeNodeCommand -NodeType "Linux" -Command 'echo 512 | sudo tee /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages'
+   Invoke-AksEdgeNodeCommand -NodeType "Linux" -Command 'echo "vm.nr_hugepages=512" | sudo tee /etc/sysctl.d/99-hugepages.conf'
    ```
 
-1. Install the specific kernel using:
+1. On each node in your cluster, install the specific kernel using:
 
    ```bash
-   sudo apt install linux-modules-extra-`uname -r`
+   Invoke-AksEdgeNodeCommand -NodeType "Linux" -Command 'sudo apt install linux-modules-extra-`uname -r`'
    ```
 
    > [!NOTE]
    > The minimum supported version is 5.1. At this time, there are known issues with 6.4 and 6.2.
 
-1. Increase the maximum number of files using the following command:
+1. On each node in your cluster, increase the maximum number of files using the following command:
 
    ```bash
    Invoke-AksEdgeNodeCommand -NodeType "Linux" -Command 'echo -e "LimitNOFILE=1048576" | sudo tee -a /etc/systemd/system/containerd.service.d/override.conf'

articles/azure-arc/edge-storage-accelerator/overview.md

@@ -38,10 +38,6 @@ Edge Storage Accelerator (ESA) serves as a native persistent storage system for
 - **Write** - Your file is processed locally and saved in the cache. When the file doesn't change within 3 seconds, ESA automatically uploads it to your chosen blob destination.
 - **Read** - If the file is already in the cache, the file is served from the cache memory. If it isn't available in the cache, the file is pulled from your chosen blob storage target.
 
-The following diagram shows the end-to-end flow of the Edge Storage Accelerator configuration and installation experience.
-
-:::image type="content" source="media/arc-connected-aks-on-azure.png" alt-text="Diagram showing the flow of Edge Storage Accelerator." lightbox="media/arc-connected-aks-on-azure.png":::
-
 ## Supported Azure Regions
 
 Edge Storage Accelerator is only available in the following Azure regions:

articles/azure-arc/edge-storage-accelerator/single-node-cluster.md

@@ -28,7 +28,7 @@ This section describes how to prepare Linux with AKS enabled by Azure Arc if you
 
    ```json
    {
-     "feature.storageClass": "default",
+     "feature.diskStorageClass": "default",
      "acstorController.enabled": false
    }
    ```
@@ -134,7 +134,7 @@ This section describes how to prepare Linux with AKS Edge Essentials if you run
    ```json
    {
      "acstorController.enabled": false,
-     "feature.storageClass": "local-path"
+     "feature.diskStorageClass": "local-path"
    }
    ```
 
@@ -169,7 +169,7 @@ This section describes how to prepare Linux with Ubuntu if you run a single-node
    ```json
    {
      "acstorController.enabled": false,
-     "feature.storageClass": "local-path"
+     "feature.diskStorageClass": "local-path"
    }
    ```