Key choices in Docker enclosure storage deployment

Naturally, regulating outmost storage introduces a advantages of resilience and persistence. If a enclosure dies, a volume can be re-attached. If a horde dies, a LUN/volume can be changed and mounted to another host. Performance can be practical during a LUN level, where systems offer facilities such as QoS (quality of service).

Implementing confidence is a bit some-more tricky. An outmost volume can be mapped to a specific enclosure host, though there is no unique confidence to allot a volume to a container, other than that supposing by a horde and enclosure adaptation software. So Kubernetes or Swarm needs to get a assignment correct.

Supplier support comes in a form of Docker plugins. Most of a vital storage array suppliers offer plugin support, including: Pure Storage, NetApp, HPE (3PAR and Nimble) and EMC by Rex-Ray and a EMC Code project.

There are also plugins from startups such as Portworx and StorageOS, that have platforms privately designed for enclosure storage. Platform suppliers such as Red Hat yield support by GlusterFS.

There are also some third-party plugins that yield entrance to internal storage and NFS resources. A list can be found on a Docker plugins page, nonetheless this is not updated really often.

Kubernetes is quick apropos a customary for enclosure deployments. The Kubernetes ecosystem provides volume support that does not have to be tied to Docker. A Kubernetes volume exists for a lifetime of a pod, that encompasses mixed containers used to report an application.

Today, Kubernetes volume support includes general NFS, iSCSI and Fibre Channel support, as good as cloud-specific offerings such as Microsoft Azure and retailer support, including Portworx, ScaleIO, GlusterFS and StorageOS.