Johann, Thanks. One question for you - Referring to moving to daos.io. Currently, that's the user manual, and the placement readme is internals documentation. Is the intention to migrate away from

Hello Joel, As the shown in the output.log, there is only one version of libfabrics installed in my machine, and actually I don't nave other software which depends libfabraics installed. From you

Our developer documentation has some basic text describing redundancy groups: https://github.com/daos-stack/daos/blob/master/src/placement/README.md#ring-placement-map That being said, this is in

Yes, it would ultimately be restricted by the size of a single shard. From:<daos@daos.groups.io> on behalf of Colin Ngam <cngam@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date:

Thanks, Jeff - That seems reasonable. A related question for you: You used the term redundancy group. Is the concept of a redundancy group detailed a bit anywhere in the documentation/readmes? It's

Hi Jeff, Does that mean that the data of the Dkey is restricted by the size of a single Shard? Thanks. Colin From: <daos@daos.groups.io> on behalf of "Olivier, Jeffrey V"

Hi Patrick, There are no built in limits on how much data you can associate with a single dkey. There are practical limitations though since data under a dkey maps to a particular redundancy

Hi Shengyu, The debug output showed me that when daos_server is started via orterun, libfabric is not finding provider support for ofi_rxm at least. I'm still wondering if you have two different

Good afternoon, I am wondering about any limitations on the total amount of data that can be associated with a given individual DKey. Is there a limit on the number of AKeys that can be associated

Hello Joel, Please see those files in attachment. I have tried two machines, one have full provider shows in fi_info (verbs and rxm), another doesn't show verbs, but they are same can't start

Hi there, All slide decks presented at the user group have been uploaded to the wiki:https://wiki.hpdd.intel.com/display/DC/DUG19 Many thanks to all the presenters!

Hi Shengyu, Can you share your daos_server.yml so we can see how you enabled the provider? And, can you share the log files daos_control.log and server.log so we can see more context? Thank

So I just pushed the minimal PR #1459 which enables the CentOS and Ubuntu images to be used as the runtime, as in my scenario. The other Dockerfiles are not used (per the documentation) so I assume

Yes I think they probably need to be updated then, in our CI system I think they were originally created for distro build testing and possibly the packages weren’t available on all the target

Hi Tom,Well, according to:https://daos-stack.github.io/admin/installation/#running-daos-service-in-docker it is also for runtime. The instructions build DAOS and then run everything inside that same

Hello Alex, The Dockerfiles provided are for build, not runtime. The package dependencies you are referring to are enforced in the RPM daos.spec IIRC. Regards, Tom Nabarro – DCG/ESAD M:

I was trying to use the Docker build instructions to use that in a machine that has OptaneDC persistent memory modules, and I found that, at least the following packages seem to be

Hello, Thank you for your help Alex, Joel and Kevin, I have checked those steps that you provided: Ibstat: State: Active Physical state: LinkUp Ifconfig: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>

Since landing commit b17231aa88d84e5b733b2ea2a97be0038776de71 to upgrade the version of SPDK used by DAOS (to v19.04.1), when building from source please remove your SPDK external build directory

Hi Shengyu, To use supported verbs provider you need to have "ofi+verbs;ofi_rxm" in the provider string. ~~Alex.