Marc Vef authored Feb 06, 2020 and Alberto Miranda committed Feb 06, 2020

--cluster argument has been removed for --config and instead uses predefined configs of a number of dependencies: mogon2, direct, all

--dependency overwrites --config and accepts multiple dependencies (space-separated)

CCI plugin have been tagged as deprecated in the Mercury library. We
where using it just for verbs, OFI+verbs can be used now as replecement.

Get rid of all the occurrences of old project name "adafs" from output
strings and documentation

Since mercury fixed the issue on their code [1], we can drop the
temporary patch we were using to avoid handles reset.

Due to the mercury fix The follwing two issues have been solved:
 - Mercury: https://github.com/mercury-hpc/mercury/issues/272
 - Margo: https://xgitlab.cels.anl.gov/sds/margo/issues/47

[1]: https://github.com/mercury-hpc/mercury/commit/9512b8b04c265645f95fd99f3b9c015e836c0347

They fixed a potential race condition:

https://github.com/mercury-hpc/mercury/commit/a421ea3072c79b2edb6d4d9d2bdaf179b5ef14f3

Changes have been merged upstream [1] with commit `acb8c296a694d7e3e06756e7a102a9d1c92df0c8`.
There is no more need to patch margo to expose enanched init function.

[1]: https://xgitlab.cels.anl.gov/sds/margo/merge_requests/9

`gflags` is an optional dependency of RocksDB, it is used only for cli
tools that we don't use.

As discussed here:
https://xgitlab.cels.anl.gov/sds/margo/issues/43

There is no more need to clone the fork repository of argobots. We could
directly use the original one because all the patches required for margo
have been merged upstream.

changelog for the new version:
https://github.com/facebook/rocksdb/releases/tag/v5.15.10

Mercury now support shared memory autorouting.

A single margo instance can be initialized and it will handle both
shared memory communication and remote ones.

If the endpoint of the RPC is local mercury will automatically use
shared memory.

Since there is only one margo instance all the duplicated code for
rpc/ipc have been unified and simplified considerably.

------

The way in which client contact the server has changed.

 - Server initializes its own margo instance and generate the endpoint
communication string using `HG_Addr_self`.
 - This endpoint description string is written on the pid file
 - When the client library loads it will fetch the server endpoint
description from the pid file and will use that to contact the server.