Run rbd client in kernel space inside container with its own network identity

Question

jsong-oracle opened this issue 2 years ago · comments

Is this a bug report or feature request?

Feature Request

Are there any similar features already existing: not sure

What should the feature do:

Start a ceph container with network not shared with its host: --net=sth --ip=sth
Use the container as rbd client running in kernel space
rbd map/unmap device should work and return
Currently the command gets stuck though the deice is actually mapped or unmapped
The device status should display the host as the rbd client
Currently it shows the container as the rbd client.
It seems the client is split into two parts: the host kernel and the container (network host)
IO on the mapped device should be good when the container is stopped or restarted
Currently the IO is stuck
rbd status / shows no client info

If current behavior is desired, it will be nice to have an option for users to choose the host as the only rbd client.

Does this have an impact on existing features: No

Environment: Linux