Atomic: Docker Storage

Managing Docker storage is an important feature for Atomic.

Notes:

• We want sane best practice and tools
  • https://trello.com/c/sBJogVoU/27-new-partitioning-defaults-for-atomic
  • http://www.projectatomic.io/docs/docker-storage-recommendation/
  • "it is not recommended to use Atomic Host before attaching an external volume"
• Do you need to restart all over if you setup storage wrong?
• Atomic needs better partitioning defaults
• Perhaps by default use a VG which we can add volumes too?
  • Can we remove volumes from a VG?
• How do we manage Docker data volumes?

Stories:

Need to build the user stories and workflows that will drive design.

User stories: Robert works at a small IT shop. For one reason or another, he got tossed the sysadmin hat at the company. They have a server running Atomic, acting as a samba file server (perhaps running this https://registry.hub.docker.com/u/svendowideit/samba/). If the container is running short on space, he needs to know sooner than later.

Peter works at a company where they have a machine running Atomic and 5 main services served by containers. The server has 4 disks set up in a pool. The five main services are: Database server, AD server, Print server, Web server, Owncloud. There have been complains that the database data transfer is not fast enough. Peter identified the bottleneck is not in the network, but in the spinning hard drive. He therefore wants to add a SSD disk to the machine and use that as the storage for the database container instead.