Hi, The docker image is a new bootstrapped system with all the binaries included. However, it's possible to let the docker have a whole device by specifying the --device parameter and then it will survive a reboot or even rebuild.
Regards, Josef On Tue, 5 Jul 2016, 12:28 Steffen Weißgerber, <[email protected]> wrote: > > > >>> Josef Johansson <[email protected]> schrieb am Donnerstag, 30. Juni > 2016 um > 15:23: > > Hi, > > > > Hi, > > > You could actually managed every osd and mon and mds through docker > swarm, > > since all just software it make sense to deploy it through docker where > you > > add the disk that is needed. > > > > Mons does not need permanent storage either. Not that a restart of the > > docker instance would remove the but rather that a remove would. > > > > Updates are easy as well, download the latest docker image and rebuild > the > > OSD/MON. > > > > And what about the data? Rebuilding an OSD's means dropping it from the > cluster, > doesn't it? > > Or do you change only the binaries and restart the new docker image on the > same > osd device? > > Otherwise it's a build up and tear down of cluster components. That's what > most ceph > admins try to avoid to keep the cluster performance stable. > > > All in all I believe you give the sysop exactly one control plane to > handle > > all of the environment. > > > > Regards, > > Josef > > > > Regards > > Steffen > > > On Thu, 30 Jun 2016, 15:16 xiaoxi chen, <[email protected]> > wrote: > > > >> It make sense to me to run MDS inside docker or k8s as MDS is stateless. > >> But Mon and OSD do have data in local , what's the motivation to run it > in > >> docker? > >> > >> > To: [email protected] > >> > From: [email protected] > >> > Date: Thu, 30 Jun 2016 08:36:45 -0400 > >> > Subject: Re: [ceph-users] Running ceph in docker > >> > >> > > >> > On 06/30/2016 02:05 AM, F21 wrote: > >> > > Hey all, > >> > > > >> > > I am interested in running ceph in docker containers. This is > extremely > >> > > attractive given the recent integration of swarm into the docker > >> engine, > >> > > making it really easy to set up a docker cluster. > >> > > > >> > > When running ceph in docker, should monitors, radosgw and OSDs all > be > >> on > >> > > separate physical nodes? I watched Sebastian's video on setting up > ceph > >> > > in docker here: https://www.youtube.com/watch?v=FUSTjTBA8f8. In the > >> > > video, there were 6 OSDs, with 2 OSDs running on each node. > >> > > > >> > > Is running multiple OSDs on the same node a good idea in production? > >> Has > >> > > anyone operated ceph in docker containers in production? Are there > any > >> > > things I should watch out for? > >> > > > >> > > Cheers, > >> > > Francis > >> > > >> > It's actually quite common to run multiple OSDs on the same physical > >> > node, since an OSD currently maps to a single block device. Depending > >> > on your load and traffic, it's usually a good idea to run monitors and > >> > RGWs on separate nodes. > >> > > >> > Daniel > >> > > >> > _______________________________________________ > >> > ceph-users mailing list > >> > [email protected] > >> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >> _______________________________________________ > >> ceph-users mailing list > >> [email protected] > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > >> > > > -- > Klinik-Service Neubrandenburg GmbH > Allendestr. 30, 17036 Neubrandenburg > Amtsgericht Neubrandenburg, HRB 2457 > Geschaeftsfuehrerin: Gudrun Kappich >
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
