Intro to the EaaS|EaaS Software Stack:
During this module, participants will learn about:
- What are the essential components of the Emulation-as-a-Service (EaaS) stack?
- How does the EaaSI platform build on EaaS?
- Where are EaaSI resources (Environments, Software, Content) stored relative to EaaS?
Questions for Discussion/Reflection
- In this module we mention a few advantages and limitations to running emulation in the cloud, as a service, rather than using local emulators. Can you think of more?
- If you manage or work with digital collections, where are they stored? Can they be directly accessed in the cloud, via a server, over a network? What would it take to connect them to a system like EaaS?
- Do you have a favorite organization or site where you go to view digital collections online? Could that site serve as an EaaS client? How?
The EaaSI program builds on previous work to apply the Emulation-as-a-Service (EaaS) framework for access and use of preserved software and digital objects. The project is focused on scaling the technological framework necessary for multiple institutions to configure, share, and access software and configured environments. EaaSI is focused on a distributed, community-driven architecture that sits on top of existing digital preservation infrastructure. This directly complements existing efforts by the Software Preservation Network and others to address key aspects of software preservation including legal advocacy, research about local software preservation needs, institutional capacity building for software preservation, collection development, professional development and training, and workflow recommendations.
About the EaaSI Training Module Series
Phase 2 of the EaaSI program of work (July 2020 – June 2022) will include a series of Training Modules, with one new Module to be released approximately every three months (a total of eight by the conclusion of Phase 2). These Training Modules are intended to supplement and expand on concepts alluded to in the EaaSI User Handbook, opening the design and functionality of the platform to wider feedback, comment, and discussion. Though particular features and elements of interface design may change between releases of the EaaSI platform, these Modules should remain consistent in elaborating on our infrastructure.
Each Module contains: a slideshow presenting a core piece of Emulation-as-a-Service functionality and its relationship to EaaSI goals and use cases; a set of questions for practitioners to discuss and/or reflect; and recommended resources from the EaaSI team for further exploration of the topic. Modules are intended to stand on their own but be easily adaptable to an in-person or virtual workshop session.