The v2021.10 EAASI codebase is no longer under active development and will only be supported for EAASI Research Alliance members until the “Next-Gen” version of EAASI is ready for production use. Since there will be no updates to the v2021.10 code - including bug fixes - we offer the following list of common concerns and known bugs from past use of v2021.10 to assist with current workflows.
-
UI terminology and some workflows reference outdated, experimental feature for sharing resources between EAASI servers (“networks”, “nodes”, “publishing”)
- Workaround: the EAASI User Handbook offers some historical context for these terms and functions but the EAASI team discourages their use
-
All “Computer Image” resources are Public, but can’t be deleted or added to Emulation Project
- Workaround: For users of spn-eaasi.cloud, we encourage the use of Template Environments and recommend ignoring the Publicly visible “Blank” Computer Image resources and discourage use of the Import Computer Image workflow
-
Environment resources can not be shared between accounts or Organizations without making them Public (accessible to all users in all Organizations)
- Workaround: For users of spn-eaasi.cloud, the EAASI team strongly encourages use of a single Admin account with shared credentials per-Organization, and redundantly importing Software resources and/or creating Environments in multiple accounts if necessary
-
Only the first file in multi-disk image Content objects are available in a corresponding Content Environment
- Workaround: Use the Emulation Project page to combine the original base Environment + Content object to start and run interactive sessions with the whole Content object on-demand rather using a saved, persistent Content Environment
-
On the first run after saving a Content Environment, changes or edits may appear to have “reverted”
- Workaround: Click “Restart Emulation” on the Emulation Access page; or Exit Emulation and then Run again
-
Single-file Content and Software uploads are limited to 5GB
- Workaround: Break up Software or Content objects into files < 5GB; if need be, load and copy data into an Environment over the course of multiple revisions
-
History tab on Environment resource details page does not show date of revisions
- Workaround: Manually include the date a revision or new Environment is saved in the Description field to help users re-trace or revert configuration history if necessary