Ceph » CephFS

I'm not aware of any bugs open on this. Is there any background on the rgw-nfs map at all? I've not looked at the service map infrastructure, so I'm not at all familiar with it.

The service map is a librados resource consumed by ceph-mgr. It periodically gets perfcounters, for example. When librgw starts, it registers an "rgw-nfs" entry in the service map. I assume Patrick is doing that when nfs-ganesha mounts libcephfs?

Matt

Looking again at this, as I'm starting to look at how we'd populate fs_locations_info to handle clustered ganesha migration. I think we can probably have ganesha register itself with the service map so we can maintain a list of ganesha servers that are associated with this cluster, and have a k/v pair that indicates the public address(es) for that server.

From there, we should be able to allow ganesha to query the service map to get a list of servers and addresses. librados does not seem to have a way for daemons to query the service map as of yet, as I guess it's only intended to be consumed by the mgr. We'll also need a way for ganesha to reliably determine its public address, which may be non-trivial if we're running in some sort of containerized environment.

Patrick, you originally opened this bug -- what other info did you want to see stored in this map?

Jeff Layton wrote:

Looking again at this, as I'm starting to look at how we'd populate fs_locations_info to handle clustered ganesha migration. I think we can probably have ganesha register itself with the service map so we can maintain a list of ganesha servers that are associated with this cluster, and have a k/v pair that indicates the public address(es) for that server.

From there, we should be able to allow ganesha to query the service map to get a list of servers and addresses. librados does not seem to have a way for daemons to query the service map as of yet, as I guess it's only intended to be consumed by the mgr. We'll also need a way for ganesha to reliably determine its public address, which may be non-trivial if we're running in some sort of containerized environment.

Patrick, you originally opened this bug -- what other info did you want to see stored in this map?

What I envisioned was the service map to act as a mechanism for discovering Ganesha clusters but I'm not even sure anymore if that is an intended use of the ServiceMap.

I would table this for now until we're sure we need this.