;just worked'.
>
>
> Cheers,
>
>
> Ben​
>
> --
>
> *From:* ceph-users on behalf of Jake
> Young
> *Sent:* Wednesday, August 30, 2017 11:37 PM
> *To:* Jeremy Hanmer; ceph-users
> *Subject:* Re: [ceph-users] Ceph re-ip of OSD node
>
> He
ubject: Re: [ceph-users] Ceph re-ip of OSD node
Hey Ben,
Take a look at the osd log for another OSD who's ip you did not change.
What errors does it show related the re-ip'd OSD?
Is the other OSD trying to communicate with the re-ip'd OSD's old ip address?
Jake
On Wed, Aug 30,
Hey Ben,
Take a look at the osd log for another OSD who's ip you did not change.
What errors does it show related the re-ip'd OSD?
Is the other OSD trying to communicate with the re-ip'd OSD's old ip
address?
Jake
On Wed, Aug 30, 2017 at 3:55 PM Jeremy Hanmer
wrote:
> This is simply not tru
This is simply not true. We run quite a few ceph clusters with
rack-level layer2 domains (thus routing between racks) and everything
works great.
On Wed, Aug 30, 2017 at 10:52 AM, David Turner wrote:
> ALL OSDs need to be running the same private network at the same time. ALL
> clients, RGW, OSD
Just curious why it wouldn't work as long as the IPs were reachable? Is
there something going on in layer 2 with Ceph that wouldn't survive a trip
across a router?
On Wed, Aug 30, 2017 at 1:52 PM, David Turner wrote:
> ALL OSDs need to be running the same private network at the same time.
> AL
ALL OSDs need to be running the same private network at the same time. ALL
clients, RGW, OSD, MON, MGR, MDS, etc, etc need to be running on the same
public network at the same time. You cannot do this as a one at a time
migration to the new IP space. Even if all of the servers can still
communic
