Release v1.1.23
01/03/2024
======================================================================================================
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. 

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.

If you have an existing VM from v1.1.22, the third party packages are the same, only the RIAPS packages changed. To
upgrade the VM to v1.1.23, run the following commands:
    `sudo apt-get update`
    `sudo apt-get install riaps-pycom-dev`
    `sudo apt-get install riaps-timesync-amd64` 


The RIAPS platform consists of 2 packages:  riaps-pycom and riaps-timesync.  The riaps-pycom package is architecture 
independent, there is one for the development environment (riaps-pycom-dev) and the other for 
remote nodes (riaps-pycom).  Architecture specific packages are available for riaps-timesync(-<arch>). 

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 packages pre-installed.  The remote nodes images no longer contain default security 
keys.  Once the image is copied to an SD card, the user can connect the nodes with the development system using the instructions 
found at https://github.com/RIAPS/riaps-integration/blob/master/riaps-x86runtime/README.md#4-connect-the-vm-to-the-remote-nodes.
When all the nodes are connected, the RIAPS Platform can be install using "riaps_fab riaps.update". Note: The remote nodes needs 
to have access to the network during this installation step.  

====================================================================================================
V1.1.23 Release Notes
====================================================================================================
  
Fixes: 
======
riaps-pycom:
* double-start and dc / leader election problem.
* Remove ctrl.py from deplo folder (duplication)
* disco crashes (related to opendht)
* dht late joiner leads to undue delay
* multiple bootstraps for the same node (dbase_dht/peermon)


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.