What is the content difference between them? IIRC
daemon-base has *just*
packages installed, while ceph/ceph has all the bash scripts needed by
ceph-nano and ansible.. is that still the case?
ceph/daemon-base has only packages installed
ceph/daemon is based from daemon-base and adds bash scripts and other tools.
ceph/ceph is actually an alias to ceph/daemon-base but with different tags
(based on ceph/ceph.git releases)
Can we simplify all of this to have a more
consistent/streamlined
approach, and/or reduce the # of images? It seems like we could have just
2 images:
ceph/daemon-base -- just the daemons + packages
ceph/ceph -- daemon-base + the extra scripts (just for compat w/ existing
users)
We could probably remove daemon-base and use ceph/ceph as a base image.
This requires to add ceph@master support to ceph/ceph build system.
and then have tags like
v14 - latest nautilus
v14.2 - latest stable nautilus (same as above unless we are
pre-release)
v14.2.3 - specific point release
We already have this tags (except the z release) on ceph/ceph
and then also
v14-tip - latest dev branch (daily)
...although the latter could actually come from quay.io/cephci if we fix
the stupid ceph-build issue that is making it *only* build containers for
wip-* branches. In cephci, there'd be tags like
There's probably something that can be improved [1]
When ceph-container.git updates, we could either do
nothing or push a big
button to rebuild everything? I'm unclear on how often older images
need to be rebuilt...
We already rebuild everything (ceph/daemon) when a commit in merged into
ceph-container.git
Regards,
Dimitri
[1]
https://github.com/ceph/ceph-container/commit/c84ba03c0c33cef88719638b32119…