Hey folks, having a development environment that makes use of containers has at least two benefits compared to plain vstart etc.: * deploying miscellaneous on demand services is easier (e.g. monitoring stack) * Using containers makes the development environment more similar to future production environments. Turns out, we (as the developer community) already have plenty of different approaches for this problem: # We have two similar dashboard projects https://github.com/ricardoasmarques/ceph-dev-docker https://github.com/rhcs-dashboard/ceph-dev/ They're based on docker-compose and in addition to starting the core services, they also can deploy a monitoring stack. They differ in the detail that ceph-dev exclusively uses containers and ceph-dev-docker uses vstart for the core services. # cstart https://github.com/ceph/ceph/blob/master/src/cstart.sh Similar to ceph-dev, but uses `cephadm bootstrap` to setup the cluster. It builds a container image containing binaries from build/bin # kcli https://github.com/karmab/kcli-plans/tree/master/ceph Which is ceph-ansible based. # vstart --cephadm Which is similar to https://github.com/ricardoasmarques/ceph-dev-docker but uses cephadm to deploy additional services instead of docker-compose. # cephadm bootstrap --shared_ceph_folder Deploys a pure cephadm based cluster, but mounts different folders My questions are now: * Is this list complete or did I miss anything? * Are there use cases which are not possible right now? * As we have a lot of similar solutions here. Is there a possibility to reduce the maintenance overhead somehow? Best, Sebastian and we have plenty of them. -- SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg). Geschäftsführer: Felix Imendörffer
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
