5327904f54
* skeleton * configure portworx * destroy and redeploy mysql with data intact * rename all directories and references from persistent storage to stateful workloads * add considerations and remove references to StorageOS * update wording and headings * create portworx volume externally and modify jobfile to reflect that * fix typo * Update website/source/guides/stateful-workloads/portworx.html.md Co-Authored-By: Omar-Khawaja <Omar-Khawaja@users.noreply.github.com> * Update website/source/guides/stateful-workloads/portworx.html.md Co-Authored-By: Omar-Khawaja <Omar-Khawaja@users.noreply.github.com>
1.3 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| guides | Stateful Workloads | guides-stateful-workloads | It is possible to deploy and consume stateful workloads in Nomad. Nomad can integrate with various storage solutions such as Portworx and REX-Ray. |
Stateful Workloads
The Docker task driver's support for volumes enables Nomad to integrate with software-defined storage (SDS) solutions like Portworx to support stateful workloads. Please keep in mind that Nomad does not actually manage storage pools or replication as these tasks are delegated to the SDS providers. Please assess all factors and risks when utilizing such providers to run stateful workloads (such as your production database).
Nomad will be adding first class features in the near future that will allow a user to mount local or remote storage volumes into task environments in a consistent way across all task drivers and storage providers.
Please refer to the specific documentation links below or in the sidebar for more detailed information about using specific storage integrations.