[openstack-dev] [TripleO][Kolla] default docker storage backend for TripleO
inc007 at gmail.com
Thu May 18 00:33:02 UTC 2017
Be careful with overlay, I've seen it acting in a ways you don't want
it to act up. That was some time ago, but memories persist. To my
experience best option is btrfs. If you don't want to repartition
disk, btrfs on loopback isn't horrible too. deviemapper on loopback is
horrible, but that's different.
On 17 May 2017 at 17:24, Dan Prince <dprince at redhat.com> wrote:
> TripleO currently uses the default "loopback" docker storage device.
> This is not recommended for production (see 'docker info').
> We've been poking around with docker storage backends in TripleO for
> almost 2 months now here:
> For TripleO there are a couple of considerations:
> - we intend to support in place upgrades from baremetal to containers
> - when doing in place upgrades re-partitioning disks is hard, if not
> impossible. This makes using devicemapper hard.
> - we'd like to to use a docker storage backend that is production
> - our target OS is latest Centos/RHEL 7
> As we approach pike 2 I'm keen to move towards a more production docker
> storage backend. Is there consensus that 'overlay2' is a reasonable
> approach to this? Or is it too early to use that with the combinations
> Looking around at what is recommended in other projects it seems to be
> a mix as well from devicemapper to btrfs.
>  https://docs.openshift.com/container-platform/3.3/install_config/in
>  http://git.openstack.org/cgit/openstack/kolla/tree/tools/setup_RedH
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev