On my Ceph Monitor (I assume this is the case with the MDS and OSD nodes too) nodes... I assign IP addresses using static dhcp entries... thus I do not define any net.eth* or whatever files for system boot (the only one is the stock factory net.lo). On these systems... the system starts the dhcp client since some network interfaces exist but there is no matchint net.* files for them. However, the system starts the ceph init script *before* the dhcp client is started, thus ceph fails to bind to the network port.... and I have to manually restart ceph. Now, I know the easy/quick-close solution is just to define net.* files... yada yada.. but I'm hoping someone can come up with a better solution where ceph won't be started until after the default dhcp client is started. Is this possible? Thanks! Reproducible: Always
(In reply to LeeL from comment #0) > On my Ceph Monitor (I assume this is the case with the MDS and OSD nodes > too) nodes... I assign IP addresses using static dhcp entries... thus I do > not define any net.eth* or whatever files for system boot (the only one is > the stock factory net.lo). > don't know how you start the network.. did you handle it manually? not leverage the gentoo init.d sctipt (through openrc)? > > Now, I know the easy/quick-close solution is just to define net.* files... > yada yada.. but I'm hoping someone can come up with a better solution where > ceph won't be started until after the default dhcp client is started. > > Is this possible? > the easiest ways is to provide net.eth* script or kind of similar (you can even write your own init.d script), and adding following code into it depend() { provide net } so ceph script will be started right after your network is up btw, why don't you setup static ip via init.d script (net.eth*)?
