> Op 29 juni 2017 om 14:50 schreef Brenno Augusto Falavinha Martinez > <brenno.marti...@serpro.gov.br>: > > > What about moving just gateways to ipv6? is that possible?
I assume you mean the RGW? Yes, no problem! I have it running the other way around. The RGW has IPv4 and IPv6, but the Ceph cluster is IPv6-only. RGW/librados talks to Ceph ovre IPv6 and handles client traffic on both protocols. No problem to run the RGW dual-stacked. Wido > Brenno > > > Em 29/06/2017 03:13:26, Wido den Hollander escreveu: > > > Op 28 juni 2017 om 22:12 schreef Gregory Farnum > : > > > > > > On Wed, Jun 28, 2017 at 6:33 AM > wrote: > > > > > > I don't think either. I don't think there is another way then just > > > 'hacky' changing the MONMaps. There have been talks of being able to make > > > Ceph dual-stack, but I don't think there is any code in the source right > > > now. > > > > > > Yeah, that's what I'd like to know. What do the Ceph team think of > > > providing ways for switching? > > > We're not in any need to do so now but, it'd be good to know if the team > > > dual-stack support or at least to test and document a way to do it as > > > opposed to a "this should work but you're on your own" kind of deal. > > > > > > > My understanding is that sepia's current infrastructure hosting can't give > > us real IPv6, so we're not in any position to really make any promises > > about interoperability. Sorry. :( > > > > That said, I think Wido's list is the way to go — but I don't remember the > > problem with running mixed. Is it just that the messenger implementations > > don't handle it live, I think? Certainly shutting down, updating all the > > monmaps/configs (if you are setting monitor IP addresses instead of hosts), > > and then turning it all back on should work but you're on your own... ;) > > -Greg > > > > The problem with mixed is this: > - The OSDMap/MONMap can only contain ONE IP, eg, IPv4 or IPv6 > - Messengers can't talk dual-stacked > > So you have to shut down the whole cluster and update the MONMap. Afterwards > the OSDs will boot and 'up' themselves in the cluster with their IPv6 address > and that will be recorded in the OSDMap. > > Wido > > > > > > > > > > > > > ________________________________________ > > > > From: Wido den Hollander [w...@42on.com] > > > > Sent: 27 June 2017 19:19 > > > > To: Vasilakakos, George (STFC,RAL,SC); ceph-users@lists.ceph.com > > > > Subject: Re: [ceph-users] Ceph and IPv4 -> IPv6 > > > > > > > > > Op 27 juni 2017 om 19:00 schreef george.vasilaka...@stfc.ac.uk: > > > > > > > > > > > > > > > Hey Ceph folks, > > > > > > > > > > I was wondering what the current status/roadmap/intentions etc. are on > > > the possibility of providing a way of transitioning a cluster from IPv4 to > > > IPv6 in the future. > > > > > > > > > > My current understanding is that this not possible at the moment and > > > that one should deploy initially with the version they want long term. > > > > > > > > > > However, given the general lack of widespread readiness, I think lots > > > of us have deployed with IPv4 and were hoping to go to IPv6 when the rest > > > of our environments enabled it. > > > > > > > > > > Is adding such a capability to a future version of Ceph being > > > considered? > > > > > > > > > > > > > I think you can, but not without downtime. > > > > > > > > The main problem is the monmap which contains IPv4 addresses and you > > > want to change that to IPv6. > > > > > > > > I haven't tried this, but I think you should be able to: > > > > - Extract MONMap > > > > - Update the IPv4 addresses to IPv6 using monmaptool > > > > - Set noout flag > > > > - Stop all OSDs > > > > - Inject new monmap > > > > - Stop MONs > > > > - Make sure IPv6 is fixed on MONs > > > > - Start MONs > > > > - Start OSDs > > > > > > > > Again, this is from the top of my head, haven't tried it, but something > > > like that should probably work. > > > > > > > > Wido > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > George V. > > > > > _______________________________________________ > > > > > ceph-users mailing list > > > > > ceph-users@lists.ceph.com > > > > > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> > > > _______________________________________________ > > > ceph-users mailing list > > > ceph-users@lists.ceph.com > > > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> > > > > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> > > @stfc.ac.uk>> @redhat.com> > > > - > > > "Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa > pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada > exclusivamente a seu destinatário e pode conter informações confidenciais, > protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e > sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, > por gentileza, reenviá-la ao emitente, esclarecendo o equívoco." > > "This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a > government company established under Brazilian law (5.615/70) -- is directed > exclusively to its addressee and may contain confidential data, protected > under professional secrecy rules. Its unauthorized use is illegal and may > subject the transgressor to the law's penalties. If you're not the addressee, > please send it back, elucidating the failure." _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
