split up ephemeral

Author: khdownie

articles/storage/container-storage/TOC.yml

@@ -13,14 +13,20 @@
   items:
   - name: Create AKS cluster and install Azure Container Storage
     href: install-container-storage-aks.md
-- name: How-to guides
+- name: Storage options
   items:
   - name: Use with Azure Disks
     href: use-container-storage-with-managed-disks.md
-  - name: Use with Ephemeral Disk
-    href: use-container-storage-with-local-disk.md
   - name: Use with Azure Elastic SAN
     href: use-container-storage-with-elastic-san.md
+  - name: Use with local NVMe
+    href: use-container-storage-with-local-disk.md
+  - name: Use with local NVMe replication
+    href: use-container-storage-with-local-nvme-replication.md
+  - name: Use with temp SSD
+    href: use-container-storage-with-temp-ssd.md    
+- name: How-to guides
+  items:
   - name: Use volume snapshot and restore
     href: volume-snapshot-restore.md
   - name: Expand a persistent volume

articles/storage/container-storage/container-storage-aks-quickstart.md

@@ -4,7 +4,7 @@ description: Create a Linux-based Azure Kubernetes Service (AKS) cluster, instal
 author: khdownie
 ms.service: azure-container-storage
 ms.topic: quickstart
-ms.date: 03/21/2024
+ms.date: 06/19/2024
 ms.author: kendownie
 ms.custom: devx-track-azurecli, ignite-2023-container-storage, linux-related-content
 ---
@@ -74,7 +74,7 @@ To connect to the cluster, use the Kubernetes command-line client, `kubectl`. It
    
 ## Choose a data storage option for your storage pool
 
-Before deploying Azure Container Storage, you'll need to decide which back-end storage option you want to use to create your storage pool and persistent volumes. Three options are currently available:
+Before deploying Azure Container Storage, you'll need to decide which back-end storage option you want to use to create your storage pool and volumes. Three options are currently available:
 
 - **Azure Elastic SAN**: Azure Elastic SAN is a good fit for general purpose databases, streaming and messaging services, CI/CD environments, and other tier 1/tier 2 workloads. Storage is provisioned on demand per created volume and volume snapshot. Multiple clusters can access a single SAN concurrently, however persistent volumes can only be attached by one consumer at a time.
 
@@ -190,8 +190,10 @@ az aks update -n <cluster-name> -g <resource-group> --disable-azure-container-st
 
 ## Next step
 
-To create persistent volumes, select the link for the backing storage type you selected.
+To create volumes, select the link for the backing storage type you selected.
 
-- [Create persistent volume claim with Azure managed disks](use-container-storage-with-managed-disks.md#3-create-a-persistent-volume-claim)
-- [Create persistent volume claim with Ephemeral Disk](use-container-storage-with-local-disk.md#create-a-persistent-volume-claim)
-- [Create persistent volume claim with Azure Elastic SAN](use-container-storage-with-elastic-san.md#3-create-a-persistent-volume-claim)
+- [Create persistent volume with Azure managed disks](use-container-storage-with-managed-disks.md#3-create-a-persistent-volume-claim)
+- [Create persistent volume with Azure Elastic SAN](use-container-storage-with-elastic-san.md#3-create-a-persistent-volume-claim)
+- [Create generic ephemeral volume with local NVMe](use-container-storage-with-local-disk.md#create-and-attach-generic-ephemeral-volumes)
+- [Create generic ephemeral volume with temp SSD](use-container-storage-with-temp-ssd.md#create-and-attach-generic-ephemeral-volumes)
+- [Create persistent volume with local NVMe and volume replication](use-container-storage-with-local-nvme-replication.md#create-and-attach-persistent-volumes)

articles/storage/container-storage/install-container-storage-aks.md

@@ -223,8 +223,10 @@ Congratulations, you've successfully installed Azure Container Storage. You now
 
 ## Next step
 
-Now you can create a storage pool and persistent volume claim, and then deploy a pod and attach a persistent volume. Follow the steps in the appropriate how-to article.
+Now you can create a storage pool and volumes. Follow the steps in the appropriate article depending on the backing storage type you want to use.
 
-* [Use Azure Container Storage with Azure Elastic SAN](use-container-storage-with-elastic-san.md)
-* [Use Azure Container Storage with Azure Disks](use-container-storage-with-managed-disks.md)
-* [Use Azure Container Storage with Ephemeral Disk (local NVMe or temp SSD)](use-container-storage-with-local-disk.md)
+- [Use Azure managed disks](use-container-storage-with-managed-disks.md)
+- [Use Azure Elastic SAN](use-container-storage-with-elastic-san.md)
+- [Use local NVMe](use-container-storage-with-local-disk.md)
+- [Use temp SSD](use-container-storage-with-temp-ssd.md)
+- [Use local NVMe and volume replication](use-container-storage-with-local-nvme-replication.md)

articles/storage/container-storage/use-container-storage-with-local-disk.md

@@ -1,28 +1,28 @@
 ---
-title: Use Azure Container Storage Preview with Ephemeral Disk
-description: Configure Azure Container Storage for use with Ephemeral Disk using either local NVMe or temp SSD on the Azure Kubernetes Service (AKS) cluster nodes. Create a storage pool, select a storage class, create a persistent volume claim, and attach the persistent volume to a pod.
+title: Use Azure Container Storage Preview with local NVMe
+description: Configure Azure Container Storage for use with Ephemeral Disk using local NVMe on the Azure Kubernetes Service (AKS) cluster nodes. Create a storage pool, select a storage class, and deploy a pod with a generic ephemeral volume.
 author: khdownie
 ms.service: azure-container-storage
 ms.topic: how-to
-ms.date: 05/24/2024
+ms.date: 06/19/2024
 ms.author: kendownie
 ms.custom: references_regions
 ---
 
-# Use Azure Container Storage Preview with Ephemeral Disk
+# Use Azure Container Storage Preview with local NVMe
 
-[Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. This article shows you how to configure Azure Container Storage to use Ephemeral Disk as back-end storage for your Kubernetes workloads. At the end, you'll have a pod that's using either local NVMe or temp SSD as its storage.
+[Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. This article shows you how to configure Azure Container Storage to use Ephemeral Disk with local NVMe as back-end storage for your Kubernetes workloads. At the end, you'll have a pod that's using local NVMe as its storage.
 
 > [!IMPORTANT]
-> Local disks are ephemeral, meaning that they're created on the local virtual machine (VM) storage and not saved to an Azure storage service. Data will be lost on these disks if you stop/deallocate your VM. You can only create [Kubernetes generic ephemeral volumes](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes) from an Ephemeral Disk storage pool. If you want to create a persistent volume, you have to enable [replication for your storage pool](#create-storage-pool-with-volume-replication-nvme-only).
+> Local disks are ephemeral, meaning that they're created on the local virtual machine (VM) storage and not saved to an Azure storage service. Data will be lost on these disks if you stop/deallocate your VM. You can only create [Kubernetes generic ephemeral volumes](https://kubernetes.io/docs/concepts/storage/ephemeral-volumes/#generic-ephemeral-volumes) from an Ephemeral Disk storage pool. If you want to create a persistent volume, you have to [use local NVMe with volume replication](use-container-storage-with-local-nvme-replication.md).
 
 ## Prerequisites
 
 [!INCLUDE [container-storage-prerequisites](../../../includes/container-storage-prerequisites.md)]
 
-## Choose a VM type that supports Ephemeral Disk
+## Choose a VM type that supports local NVMe
 
-Ephemeral Disk is only available in certain types of VMs. If you plan to use Ephemeral Disk with local NVMe, a [storage optimized VM](../../virtual-machines/sizes-storage.md) such as **standard_l8s_v3** is required. If you plan to use Ephemeral Disk with temp SSD, a [Ev3 and Esv3-series VM](../../virtual-machines/ev3-esv3-series.md) is required.
+Ephemeral Disk is only available in certain types of VMs. If you plan to use local NVMe, a [storage optimized VM](../../virtual-machines/sizes-storage.md) such as **standard_l8s_v3** is required.
 
 You can run the following command to get the VM type that's used with your node pool.
 
@@ -40,19 +40,15 @@ nodepool1   standard_l8s_v3
 
 We recommend that each VM have a minimum of four virtual CPUs (vCPUs), and each node pool have at least three nodes.
 
-## Create a storage pool
+## Create and attach generic ephemeral volumes
 
-First, create a storage pool, which is a logical grouping of storage for your Kubernetes cluster, by defining it in a YAML manifest file.
-
-If you enabled Azure Container Storage using `az aks create` or `az aks update` commands, you might already have a storage pool. Use `kubectl get sp -n acstor` to get the list of storage pools. If you have a storage pool already available that you want to use, you can skip this section and proceed to [Display the available storage classes](#display-the-available-storage-classes).
+Follow these steps to create and attach a generic ephemeral volume.
 
-You have three options to create a storage pool that uses Ephemeral Disk:
+### 1. Create a storage pool
 
-- [Create storage pool with local NVMe](#create-a-storage-pool-with-nvme)
-- [Create storage pool with temp SSD](#create-a-storage-pool-with-temp-ssd)
-- [Create storage pool with local NVMe and replication](#create-storage-pool-with-volume-replication-nvme-only)
+First, create a storage pool, which is a logical grouping of storage for your Kubernetes cluster, by defining it in a YAML manifest file.
 
-### Create a storage pool with NVMe
+If you enabled Azure Container Storage using `az aks create` or `az aks update` commands, you might already have a storage pool. Use `kubectl get sp -n acstor` to get the list of storage pools. If you have a storage pool already available that you want to use, you can skip this section and proceed to [Display the available storage classes](#2-display-the-available-storage-classes).
 
 Follow these steps to create a storage pool using local NVMe.
 
@@ -91,49 +87,9 @@ Follow these steps to create a storage pool using local NVMe.
 
 When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`.
 
-### Create a storage pool with temp SSD
-
-Follow these steps to create a storage pool using temp SSD.
-
-1. Use your favorite text editor to create a YAML manifest file such as `code acstor-storagepool.yaml`.
-
-1. Paste in the following code and save the file. The storage pool **name** value can be whatever you want.
-
-   ```yml
-   apiVersion: containerstorage.azure.com/v1
-   kind: StoragePool
-   metadata:
-     name: ephemeraldisk
-     namespace: acstor
-   spec:
-     poolType:
-       ephemeralDisk:
-         diskType: temp
-   ```
-
-1. Apply the YAML manifest file to create the storage pool.
-   
-   ```azurecli-interactive
-   kubectl apply -f acstor-storagepool.yaml 
-   ```
-   
-   When storage pool creation is complete, you'll see a message like:
-   
-   ```output
-   storagepool.containerstorage.azure.com/ephemeraldisk created
-   ```
-   
-   You can also run this command to check the status of the storage pool. Replace `<storage-pool-name>` with your storage pool **name** value. For this example, the value would be **ephemeraldisk**.
-   
-   ```azurecli-interactive
-   kubectl describe sp <storage-pool-name> -n acstor
-   ```
-
-When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`.
-
-## Display the available storage classes
+### 2. Display the available storage classes
 
-When the storage pool is ready to use, you must select a storage class to define how storage is dynamically created when creating persistent volume claims and deploying persistent volumes.
+When the storage pool is ready to use, you must select a storage class to define how storage is dynamically created when creating and deploying volumes.
 
 Run `kubectl get sc` to display the available storage classes. You should see a storage class called `acstor-<storage-pool-name>`.
 
@@ -146,7 +102,7 @@ acstor-ephemeraldisk        containerstorage.csi.azure.com   Delete          Wai
 > [!IMPORTANT]
 > Don't use the storage class that's marked **internal**. It's an internal storage class that's needed for Azure Container Storage to work.
 
-## Deploy a pod with a generic ephemeral volume
+### 3. Deploy a pod with a generic ephemeral volume
 
 Create a pod using [Fio](https://github.com/axboe/fio) (Flexible I/O Tester) for benchmarking and workload simulation, that uses a generic ephemeral volume.
 
@@ -211,11 +167,15 @@ Create a pod using [Fio](https://github.com/axboe/fio) (Flexible I/O Tester) for
    kubectl exec -it fiopod -- fio --name=benchtest --size=800m --filename=/volume/test --direct=1 --rw=randrw --ioengine=libaio --bs=4k --iodepth=16 --numjobs=8 --time_based --runtime=60
    ```
 
-You've now deployed a pod that's using Ephemeral Disk as its storage, and you can use it for your Kubernetes workloads.
+You've now deployed a pod that's using local NVMe as its storage, and you can use it for your Kubernetes workloads.
+
+## Manage storage pools
 
-## Expand a storage pool
+Now that you've created your storage pool, you can expand or delete it as needed.
 
-You can expand storage pools backed by local NVMe or temp SSD to scale up quickly and without downtime. Shrinking storage pools isn't currently supported.
+### Expand a storage pool
+
+You can expand storage pools backed by local NVMe to scale up quickly and without downtime. Shrinking storage pools isn't currently supported.
 
 Because a storage pool backed by Ephemeral Disk uses local storage resources on the AKS cluster nodes (VMs), expanding the storage pool requires adding another node to the cluster. Follow these instructions to expand the storage pool.
 
@@ -229,178 +189,14 @@ Because a storage pool backed by Ephemeral Disk uses local storage resources on
 
 1. Run `kubectl get sp -A` and you should see that the capacity of the storage pool has increased.
 
-## Delete a storage pool
+### Delete a storage pool
 
 If you want to delete a storage pool, run the following command. Replace `<storage-pool-name>` with the storage pool name.
 
 ```azurecli-interactive
 kubectl delete sp -n acstor <storage-pool-name>
 ```
 
-## Create storage pool with volume replication (NVMe only)
-
-Applications that use local NVMe can leverage storage replication for improved resiliency. Replication isn't currently supported for temp SSD.
-
-Azure Container Storage currently supports three-replica and five-replica configurations. If you specify three replicas, you must have at least three nodes in your AKS cluster. If you specify five replicas, you must have at least five nodes.
-
-Follow these steps to create a storage pool using local NVMe with replication.
-
-> [!NOTE]
-> Because Ephemeral Disk storage pools consume all the available NVMe disks, you must delete any existing Ephemeral Disk local NVMe storage pools before creating a new storage pool with replication.
-
-1. Use your favorite text editor to create a YAML manifest file such as `code acstor-storagepool.yaml`.
-
-1. Paste in the following code and save the file. The storage pool **name** value can be whatever you want. Set replicas to 3 or 5.
-
-   ```yml
-   apiVersion: containerstorage.azure.com/v1
-   kind: StoragePool
-   metadata:
-     name: nvme
-     namespace: acstor
-   spec:
-     poolType:
-       ephemeralDisk:
-         diskType: nvme
-         replicas: 3
-   ```
-
-1. Apply the YAML manifest file to create the storage pool.
-   
-   ```azurecli-interactive
-   kubectl apply -f acstor-storagepool.yaml 
-   ```
-   
-   When storage pool creation is complete, you'll see a message like:
-   
-   ```output
-   storagepool.containerstorage.azure.com/nvme created
-   ```
-   
-   You can also run this command to check the status of the storage pool. Replace `<storage-pool-name>` with your storage pool **name** value. For this example, the value would be **nvme**.
-   
-   ```azurecli-interactive
-   kubectl describe sp <storage-pool-name> -n acstor
-   ```
-
-When the storage pool is created, Azure Container Storage will create a storage class on your behalf, using the naming convention `acstor-<storage-pool-name>`. Now you can [display the available storage classes](#display-the-available-storage-classes) and create a persistent volume claim.
-
-## Create a persistent volume claim
-
-A persistent volume claim (PVC) is used to automatically provision storage based on a storage class. Follow these steps to create a PVC using the new storage class.
-
-1. Use your favorite text editor to create a YAML manifest file such as `code acstor-pvc.yaml`.
-
-1. Paste in the following code and save the file. The PVC `name` value can be whatever you want.
-
-   ```yml
-   apiVersion: v1
-   kind: PersistentVolumeClaim
-   metadata:
-     name: ephemeralpvc
-   spec:
-     accessModes:
-       - ReadWriteOnce
-     storageClassName: acstor-ephemeraldisk-nvme # replace with the name of your storage class if different
-     resources:
-       requests:
-         storage: 100Gi
-   ```
-
-1. Apply the YAML manifest file to create the PVC.
-   
-   ```azurecli-interactive
-   kubectl apply -f acstor-pvc.yaml
-   ```
-   
-   You should see output similar to:
-   
-   ```output
-   persistentvolumeclaim/ephemeralpvc created
-   ```
-   
-   You can verify the status of the PVC by running the following command:
-   
-   ```azurecli-interactive
-   kubectl describe pvc ephemeralpvc
-   ```
-
-Once the PVC is created, it's ready for use by a pod.
-
-## Deploy a pod and attach a persistent volume
-
-Create a pod using [Fio](https://github.com/axboe/fio) (Flexible I/O Tester) for benchmarking and workload simulation, and specify a mount path for the persistent volume. For **claimName**, use the **name** value that you used when creating the persistent volume claim.
-
-1. Use your favorite text editor to create a YAML manifest file such as `code acstor-pod.yaml`.
-
-1. Paste in the following code and save the file.
-
-   ```yml
-   kind: Pod
-   apiVersion: v1
-   metadata:
-     name: fiopod
-   spec:
-     nodeSelector:
-       acstor.azure.com/io-engine: acstor
-     volumes:
-       - name: ephemeralpv
-         persistentVolumeClaim:
-           claimName: ephemeralpvc
-     containers:
-       - name: fio
-         image: nixery.dev/shell/fio
-         args:
-           - sleep
-           - "1000000"
-         volumeMounts:
-           - mountPath: "/volume"
-             name: ephemeralpv
-   ```
-
-1. Apply the YAML manifest file to deploy the pod.
-   
-   ```azurecli-interactive
-   kubectl apply -f acstor-pod.yaml
-   ```
-   
-   You should see output similar to the following:
-   
-   ```output
-   pod/fiopod created
-   ```
-
-1. Check that the pod is running and that the persistent volume claim has been bound successfully to the pod:
-
-   ```azurecli-interactive
-   kubectl describe pod fiopod
-   kubectl describe pvc ephemeralpvc
-   ```
-
-1. Check fio testing to see its current status:
-
-   ```azurecli-interactive
-   kubectl exec -it fiopod -- fio --name=benchtest --size=800m --filename=/volume/test --direct=1 --rw=randrw --ioengine=libaio --bs=4k --iodepth=16 --numjobs=8 --time_based --runtime=60
-   ```
-
-You've now deployed a pod that's using Ephemeral Disk as its storage, and you can use it for your Kubernetes workloads.
-
-## Detach and reattach a persistent volume
-
-To detach a persistent volume, delete the pod that the persistent volume is attached to.
-
-```azurecli-interactive
-kubectl delete pods <pod-name>
-```
-
-To reattach a persistent volume, simply reference the persistent volume claim name in the YAML manifest file as described in [Deploy a pod and attach a persistent volume](#deploy-a-pod-and-attach-a-persistent-volume).
-
-To check which persistent volume a persistent volume claim is bound to, run:
-
-```azurecli-interactive
-kubectl get pvc <persistent-volume-claim-name>
-```
-
 ## See also
 
 - [What is Azure Container Storage?](container-storage-introduction.md)