On Wed, 30 Oct 2019, Dimitri Savineau wrote: > > 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 Oh! Okay, that sounds like it's mostly what we want (except that having daemon-base around too is sort of confusing). I'll switch all the defaults to be ceph/ceph:v14 (or v15 or whatever). I think my only question/suggestion is whether we should have a default tag (does such a think exist? e.g., if you do podman pull ceph/ceph what do you get?) or maybe 'stable' tag that just tracks the latest stable release (v14 alias currently; would switch to v15 once octopus is out, etc.) > > 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] Aha... yeah, that's helpful, thanks! In my perfect world you'd be able to do cephci/ceph:$branch (e.g. cephci/ceph:master or cephci/ceph:nautilus). Right now those tag names have a bunch of other stuff in them too (and are only wip-*). Thanks! sage _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx