Introduction
This procedure explains how to share a volume between multiple edge applications running on the same node. Shared volumes are useful when multiple applications need access to the same dataset, such as sensor readings, log files, or configuration files. EVE-OS (Edge Virtualization Engine) implements shared volume access using the Plan 9 filesystem protocol. All applications that mount the volume can read from and write to a single, consistent data source. Virtual machine (VM) workloads must mount shared volumes manually inside the guest OS using the preferred method for that OS. Container-based applications mount the volume automatically at the path you specify during application configuration.Prerequisites
- EVE-OS 12.7.0 or later on the target node.
- You have the SysManager or SysAdmin role in your enterprise. See Manage Roles.
- At least one node onboarded to Edge Infrastructure Services.
Create an Image Volume
The shared block storage volume requires a base image volume to initialize from. Create the image volume first.- In the sidebar, click Infrastructure > Workloads > Volumes.
- Click the Add button (floating button in the lower right of the page).
- Select Image Volume and click Next.
- In the Identity section, enter a name, title, and optional description. Select the target node.
- In the Storage section, select the App Image you want to use as the base. Choose a container image if you plan to allow multiple applications to write to the shared volume. VM disk formats (QCOW2, RAW, ISO) support only read-only sharing across multiple applications.
- Click Create Volume.
Create a Block Storage Volume
Create the block storage volume on the same node and link it to the image volume created in the previous step.- In the sidebar, click Infrastructure > Workloads > Volumes.
- Click the Add button (floating button in the lower right of the page).
- Select Block Storage and click Next.
- In the Identity section, enter a name, title, and optional description. Select the same node where you created the image volume.
- In the Storage section:
- Set the Access Mode based on your sharing requirements:
- Read Only: All applications can read from the volume but cannot write to it.
- Read Write: All applications can read from and write to the volume.
- Multi Read / Single Write: Behaves the same as Read Write.
- Set the Max Size to a value larger than the size of the base container image.
- In the Image Volume field, select the image volume you created in the previous step. This initializes the block storage volume from the base image.
- Note the value you enter in the Name field. You will use it as the volume label when configuring application drives.
- Set the Access Mode based on your sharing requirements:
- Click Create Volume.
Create and Configure Edge Applications
For each application that will share the volume, configure the application’s drives to reference the block storage volume.- Create or edit the edge application definition. See Create and Manage an App Image for instructions.
- In the Drives section of the application, add an additional drive.
- In the Tag field for the additional drive, enter the Name of the block storage volume you created. This tag is how EVE-OS maps the drive definition to the actual volume instance on the node.
- In the Mount Path field, specify the path inside the application’s filesystem where the volume will be mounted (for example,
/data/shared). - Repeat these steps for each application that should share the volume.
Deploy the Application Instances
Deploy all application instances to the node where you created the volumes. See Deploy an Application Instance for the deployment wizard walkthrough. After deployment, all applications with the matching drive tag mount the volume at the path you specified. Applications can read from and write files to the mounted path, and those files are accessible to all other applications that share the volume.Verify the Configuration
After deployment, navigate to the volume detail page and click the Used by tab. Confirm that all expected application instances appear in the list. To verify that data sharing is working, check that a file written by one application is visible to the other applications mounting the same volume.Next Steps
Create Volumes
The full volume creation procedure.
Add Persistent Volumes
Prevent shared volume data from being erased during application updates.
Volumes Overview
An overview of volume types and how they work.