Re: [ceph-users] In a High Avaiability setup, MON, OSD daemon take up the floating IP

2018-06-28 Thread Дробышевский , Владимир
Rahul, if you are using the whole drives for OSDs then ceph-deploy is a good option in most cases. 2018-06-28 18:12 GMT+05:00 Rahul S : > Hi Vlad, > > Have not thoroughly tested my setup but so far things look good. Only > problem is that I have to manually activate the osd's using the

Re: [ceph-users] In a High Avaiability setup, MON, OSD daemon take up the floating IP

2018-06-28 Thread Rahul S
Hi Vlad, Have not thoroughly tested my setup but so far things look good. Only problem is that I have to manually activate the osd's using the ceph-deploy command. Manually mounting the osd partition doesnt work. Thanks for replying. Regards, Rahul S On 27 June 2018 at 14:15, Дробышевский,

Re: [ceph-users] In a High Avaiability setup, MON, OSD daemon take up the floating IP

2018-06-27 Thread Дробышевский , Владимир
Hello, Rahul! Do you have your problem during initial cluster creation or on any reboot\leadership transfer? If the first then try to remove floating IP while creating mons and temporarily transfer the leadership from the server your going to create OSD on. We are using the same

Re: [ceph-users] In a High Avaiability setup, MON, OSD daemon take up the floating IP

2018-06-27 Thread Rahul S
I have an OpenNebula HA setup which requires a floating ip to function. For testing purposes, I also have my ceph cluster co-located on the OpenNebula cluster. While I have configured my mon daemons to take the actual ips. On installation one of the mon daemons takes its IP from outside the

Re: [ceph-users] In a High Avaiability setup, MON, OSD daemon take up the floating IP

2018-06-27 Thread Paul Emmerich
Mons have only exactly one fixed IP address. A mon cannot use a floating IP, otherwise it couldn't find its peers. Also, the concept of a floating IP makes no sense for mons - you simply give your clients a list of mon IPs to connect to. Paul 2018-06-26 10:17 GMT+02:00 Rahul S : > Hi! In my