Page MenuHomeDevCentral

Configure Docker direct-lvm storage
ClosedPublic

Authored by dereckson on Sep 18 2018, 21:48.
Tags
None
Referenced Files
F3749591: D1771.diff
Sat, Nov 16, 16:25
F3748234: D1771.id4495.diff
Sat, Nov 16, 07:23
F3747947: D1771.id4494.diff
Sat, Nov 16, 05:41
F3747866: D1771.id.diff
Sat, Nov 16, 05:11
F3747798: D1771.id4494.diff
Sat, Nov 16, 04:47
F3747003: D1771.id4494.diff
Sat, Nov 16, 00:11
F3746993: D1771.id4495.diff
Sat, Nov 16, 00:07
F3746990: D1771.id4494.diff
Sat, Nov 16, 00:06
Subscribers
None

Details

Summary

CentOS Docker engines currently use devicemapper. For production, to use a thinpool
instead of loopback devices is recommended.

This change takes care of the Docker configuration for the storage engine.

This change doesn't take care to create such lvm volume.

Reference: https://docs.docker.com/storage/storagedriver/device-mapper-driver/

Ref T1408

Test Plan

Tested on Equatower

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Passed
Unit
No Test Coverage
Branch
lvm-profile (branched from master)
Build Status
Buildable 2754
Build 3002: arc lint + arc unit

Event Timeline

dereckson created this revision.
This revision is now accepted and ready to land.Sep 18 2018, 21:49
This revision was automatically updated to reflect the committed changes.