Release v1.1.21
======================================================================================================
New VMs and Remote node images are available on the download page (https://riaps.isis.vanderbilt.edu/rdownloads.html).
This release includes SD card images for TI Beaglebone Black and Raspberry Pi 4.

New version of RIAPS DSML install on the VM to incorporate the latest group timing parameters available. 
The VM also includes a user friendly setup for using Node RED GUI and MQTT communications. Information on 
setting up the new VM can be found at https://github.com/RIAPS/riaps-integration/tree/master/riaps-x86runtime.

The RIAPS platform consists of 2 packages:  riaps-pycom and riaps-timesync

IMPORTANT NOTE ON REMOTE NODE IMAGES:  The remote node images are basic platform prepared image.  It includes
the needed third-party packages already installed and the environment configurations available for
the RIAPS platform.  It DOES NOT INCLUDE the RIAPS platform pre-installed.  Once you copy this image
to an SD card, the RIAPS Platform must be installed using the following script on each remote node:
riaps_install_node.sh (https://github.com/RIAPS/riaps-integration/blob/master/riaps-node-runtime/riaps_install_node.sh).
The remote node needs to have access to the network during this installation step.  If you have multiple remote nodes,
you can update one with the RIAPS packages and then copy that SD card to the other nodes.  Instructions
for transferring the SD card image to a location on a VM or a local Linux machine can be found at
https://github.com/RIAPS/riaps-integration/blob/master/riaps-node-creation/README.md#saving-image, then use
balenaEtcher to write that image to the other SD cards.

====================================================================================================
04/21/2023 Release Update
 
====================================================================================================
V1.1.21 Release Notes
====================================================================================================
>Note: No change to riaps-timesync, all changes are in riaps-pycom.

New Features:
* Group timing customization (riaps_lang, riaps_run.actor/device, riaps_run.dc): 
  heartbeat, electionMin, electionMax, peerTimeout, consensusTimeout
* Add cli `join` command (riaps_ctrl.cli) and updated Lang test, allows dns names

Improvements:
* Handle hanging socket (riaps_deplo.depm)
* Raft config, leader election initiation (riaps_run.dc)
* Group tests updated
* Discovery security improvements:
    * redis comm secured (same cert/key as platform). Requires redis w/ tls.
    * dht runs with a crypto identity (to protect housekeeping messages, if any, in opendht)
    * dht errors on fake values

Fixes:
* sudo install needed for apt-get installation (worked fine as is for dpkg)
* Issue w/ app verification - when it fails, app should be be started. Note for CLI: app must be installed (i app) before launch.
* Distributed coordination: duplicate leader 
* Loading app modules with the same name as another module in path -- force loading from app folder first.
* Disco caching problems (causing invalid updates)
* Checks on dc group parameters
* Increase timeout on devicereq (to allow slow device startups)


Suggestions for Transferring Eclipse Workspaces to a new VM
===========================================================
There are several ways to transfer your project work between VM.  Perhaps the easiest is to keep your
code in a code repository (such as SVN or GIT) and then create a new workspace from the retrieval of
the code from the repository.

Another way would be to use Eclipse to export an archive file that can be moved to a transfer site
(such as Dropbox or any other file sharing tool).  And then import that file into a new VM eclipse
workspace.  Here are some tips for doing this:
1) In the old VM, choose "File" --> "Export" from the drop-down menus and select the
   "General - Archive Files" option.
2) Select all the files you want to include in the archive.  You can unselect compiled files or even
   use the "Filter Types" tool to help with this.  Indicate the file name and location to place this
   archive ("To archive file:" box).
3) Copy the file to a transfer site (such as Dropbox) and then retrieve it on the new VM.
4) On the new VM, choose "File" --> "Import" from the drop-down menus and select the
   "General - Existing Projects into Workspace" option.
5) "Select the archive file" option and find the transferred file.
6) This should have the workspace back in place in the new VM.