achlysproject / achlys Goto Github PK

As described by Almeida et al. in Delta State Replicated Data Types, the system model requires the following :

Nodes have access to durable storage; they can crash but will eventually recover with the content of the durable storage just before the crash occurred. Durable state is written atomically at each state transition.

• Investigate possible use of the Lasp DETS storage backend
• Mitigate DETS file corruption due to hardware shutdowns on GRiSP boards during execution (DETS files are empty after hard reset -> not_a_dets_file error is thrown when the Lasp storage backend attempts to open it)

https://twitter.com/chris_mccord/status/1110948008613548032?s=19

• Deployment guide
• Lasp API usage examples
• Task model API edocs
• Local testing guide

Add OTP behavior capturing the sensor worker interface with mandatory callbacks

Context

This feature needs documentation, either in the README or on the wiki.

Originally posted by @eproxus in grisp/grisp#41 (comment)

Hostname resolution

DNS service equivalent with default configuration must be used instead of manual entries for each host

MAC addresses

Per device unique identification must be used for mapping

• DNS service through inet_dns
• Retrieve hardware address in EEPROM

Enable API functions for gathering data from available drivers

• Add configuration parameters to set sliding windows to preserve only N most recent ETS entries when collecting raw data streams.
• Purge tables periodically based on configuration

Stress

Overall "stress" seems to correlate with the intervals between requests in general.
process heap growth is probably observed above a certain threshold of updates per unit of time.

• 2 nodes cluster aggregates temperatures with stable memory footprint
• 4 nodes
• 8 nodes

• Installation guide
• Test environment configuration
• GRiSP deployment configuration
• API documentation on Hex

• silent Erlang shell and RTEMS shell access
• Access Erlang Remote Shell while RTEMS shell option is selected
• Clusterize nodes exposing different shells
• Combine all possibile configurations in a single cluster and deploy Achlys

Wiki

• The Wiki needs to be completed with at least a basic application example and the necessary steps for deployment.

for minimal deployments

• Check for existing variables and members in the cluster instead of automatic full bidirectional joins and declarations

API call description

The framework must be able to provide a function such as :

achlys:memory(remaining)

That returns the exact amount of memory that is usable by the application at any point in time. The feature will possibly be implemented in a separate library that would be included as a dependency.

• Write scenario that can easily reproduce the same crash dump
• Collect sufficient information regarding the following memory management common issues :

1. Detailed report on fragmentation status
2. Detailed report about existence of leakage

• Implement API function that computes the best estimate possible of usable memory w.r..t previously collected information. The behavior that should be adopted regarding GC is not yet defined. Example : If called during garbing, the available memory would appear lower due to copies being made before fullsweep. The program would not be aware that much more space is free immediately after the GC completion. Possible workaround would be to perform manual GC when function is called, but this heavily limits the usability of the function as calling it very frequently would cause overhead.
• Validate correctness of returned values
• Optional : integration in a monitoring dashboard such a Prometheus

make shell causes an error on on WSL (Kali Linux)

Here is the output of the terminal :

user@VivoBook:~/achlys$ cat /etc/os-release
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2019.4"
VERSION_ID="2019.4"
VERSION_CODENAME="kali-rolling"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
user@VivoBook:~/achlys$ make shell
Launching shell node
Using long names
===> Verifying dependencies...
===> Compiling achlys
src/achlys.erl:176: Warning: variable 'F' is unused
src/achlys.erl:184: Warning: variable 'F' is unused
src/achlys.erl:188: Warning: variable 'Elem' is unused
src/achlys.erl:200: Warning: variable 'Minimum' is unused

src/achlys_cleaner.erl:51: Warning: type gc_config() is unused
src/achlys_cleaner.erl:238: Warning: variable 'TimerRef' is unused

src/achlys_task_worker.erl:165: Warning: variable 'Info' is unused

src/achlys_util.erl:61: Warning: variable 'Func' is unused
src/achlys_util.erl:125: Warning: variable 'T' is unused
src/achlys_util.erl:184: Warning: variable 'T' is unused

src/achlys_pmod_als_worker.erl:68: Warning: type crdt() is unused
src/achlys_pmod_als_worker.erl:235: Warning: variable 'T' is unused
src/achlys_pmod_als_worker.erl:245: Warning: variable 'C2' is unused

src/achlys_pmod_nav_worker.erl:245: Warning: variable 'C2' is unused
src/achlys_pmod_nav_worker.erl:274: Warning: variable 'C3' is unused

Erlang/OTP 22 [erts-10.4] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [hipe]

===> {bad_term_file,"./config/test.config.src",
               {41,erl_parse,["syntax error before: ","'}'"]}}
make: *** [Makefile:71: shell] Error 1

Same for this configuration (VM)

user@kali:~/achlys$ cat /etc/os-release
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2018.4"
VERSION_ID="2018.4"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"