Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DAOS-2615 docs: update README for some client APIs #4799

Merged
merged 1 commit into from
Feb 26, 2021
Merged

DAOS-2615 docs: update README for some client APIs #4799

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 4 additions & 14 deletions src/client/dfs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,20 +162,10 @@ directory containing the actual value of the symlink.
## Access Permissions

All DFS objects (files, directories, and symlinks) inherit the access
permissions of the DFS pool that they are created with. So when a user is trying
to access an object in the DFS namespace, their real/effective uid/gid are
compared against those of the pool's uid and gid, which are obtained when
connecting to the pool. The check then is done with the stored object mode and
depending on the type of access being requested (R, W, X) and the object mode,
access permission is determined. In the source code, this is implemented in the
function `check_access()`.
permissions of the DFS container that they are created with. So the permission
checks are done on dfs_mount(). If that succeeds and the user has access to the
container, then they will be able to access all objects in the DFS
namespace.

setuid(), setgid() programs, supplementary groups, ACLs are not supported in the
DFS namespace.

## DFUSE_HL

A simple high level fuse plugin (dfuse_hl) is implemented to use the DFS API
and functionality with existing POSIX tests and benchmarks (IOR, mdtest,
etc.). The DFS high level fuse exposes one mounpoint as a single DFS namespace
with a single pool and container.
3 changes: 2 additions & 1 deletion src/object/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,8 @@ bandwidth by allowing concurrent reads from different replicas.
#### Client-side Replication

Client replication is the mode that it is synchronous and fully in the client
stack, to provide high concurrency and low latency I/O for the upper layer.
stack, to provide high concurrency and low latency I/O for the upper layer. This
mode is not default and is only provided for testing purposes.
- I/O requests against replicas are directly issued via DAOS client; there is
no sequential guarantee on writes in the same epoch, and concurrent writes
for a same object can arrive at different replicas in an arbitrary order.
Expand Down