On 07/10/2015 08:21 AM, kefu chai wrote:
> can we
> - have another package named "ceph-base" which packages whatever ceph
> currently has now.
> - make the "ceph" a meta package which only offers the dependencies to
> ceph-mon, ceph-osd, ceph-mds? and let ceph-{mon,osd,mds} Depends on
> "ceph-base" instead?
I was hoping to avoid this route because it seemed complex, but the
further I dig on this, I think your suggestion is going to be the best
way forward.
So to re-state the plan: Files that are shared between multiple servers
will move into "ceph-base", and then:
For RPMs:
- "ceph-{mon,osd,mds}" Require: ceph-base.
- "ceph" will become a metapackage that Requires: ceph-{mon,osd,mds}.
For DEBs:
- "ceph-{mon,osd,mds}" will Depends: ceph-base.
- "ceph" will become a metapackage that Depends: ceph-{mon,osd}.
- "ceph" will continue to Recommends: ceph-mds
I've done some testing with a dummy package and this works. "apt-get
upgrade" kept the update back, since there were new packages introduced,
but "apt-get dist-upgrade" worked. Is that expected? (... newbie Debian
user here :D )
I've pushed this approach to
https://github.com/ceph/ceph/tree/wip-10587-split-servers.
- Ken
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
