Currently contint1001 stores all docker images on the root partition (which is only 50GB). It seems like this could cause trouble if we build one too many docker images and fill the whole disk (which seems like an easy thing to do in the current setup).
Not sure how difficult it would be to add storage to this machine, or reallocate the existing storage, filing this task to find out.
On T178663#3699074 @hashar wrote:
Looks like `profile::docker::storage` has the logic to setup a partition with parameters:
```
# list of physical volumes to use.
$physical_volumes = hiera('profile::docker::storage::physical_volumes'),
# Volume group to substitute.
$vg_to_remove = hiera('profile::docker::storage::vg_to_remove'),
```
It seems to create a new volume group `docker` with logical volumes `data` and `metadata`.
`profile::docker::storage::physical_volumes` would be the physical volume.
contint1001 has a 1TB disk and all the physical volume / volume group is allocated:
```
# pvdisplay
--- Physical volume ---
PV Name /dev/md2
VG Name contint1001-vg
PV Size 883.89 GiB / not usable 3.00 MiB
Allocatable yes (but full)
```
```
# vgdisplay
--- Volume group ---
VG Name contint1001-vg
Format lvm2
VG Status resizable
Cur LV 1
VG Size 883.89 GiB
```
```
root@contint1001:~# lvdisplay
--- Logical volume ---
LV Path /dev/contint1001-vg/data
LV Name data
VG Name contint1001-vg
LV Size 883.89 GiB
```
Seems to me we would have to shrink the logical volume `/dev/contint1001-vg/data` and the volume group `contint1001-vg`.
----
Usage as of January 25th 2019
```
$ df -h / /srv
Filesystem Size Used Avail Use% Mounted on
/dev/md0 46G 39G 5.0G 89% /
/dev/mapper/contint1001--vg-data 870G 544G 283G 66% /srv
```
`/` has Docker images (via /var/lib/docker) which is the concern: docker can fill the root partition.
`/srv` has Jenkins build results (large), zuul-merge repositories (~ 25GB), integration.wikimedia.org docroot (small)
We would want to shrink the volume group and create a new one for Docker images which would be at `/srv/docker`.