Updated Training Module: "Disk Images"

EAASI Research Alliance
1

This Training Module series introduces important concepts in emulation and key features of the EAASI platform. These modules are intended to supplement the EAASI User Handbook, opening the design and functionality of the platform to wider feedback and discussion among members of the EAASI Research Alliance and the Software Preservation Network, particularly in regard to the product roadmap.

Each module contains: a slideshow presenting a core piece of platform functionality and its relationship to EAASI development 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.

This module has been adapted from an equivalent resource originally developed in Phase 2 (July 2020 - June 2022) of the “Scaling Emulation-as-a-Service Infrastructure” grant program funded by the Mellon and Sloan foundations. It has been modified to reflect updated branding and supported use cases for the EAASI platform. Screenshots of the EAASI platform are used for illustration purposes and have been taken over a wide range of development and version history; they may not 100% reflect currently-supported functionality.

Please feel free to share, remix and re-use these modules as appropriate within your member organization (and within the bounds of the CC-BY-SA license)!

Disk Images

During this module, participants will learn about:

  • What is a disk image?
  • How do disk images relate to Software, Content, and Environment resources in EAASI?
  • What is the advantage of copy-on-write disk images?

Questions for Discussion/Reflection

  • Is disk imaging already a part of your organization or collection’s digital preservation workflow? Are there established policies, procedures, or guidance for creating or acquiring disk images in your collections?
  • In this module we discussed some of the advantages of “copy-on-write” disk image formats like QCOW2. Can you think of any drawbacks or tradeoffs with using this approach for resource storage?
  • What metadata would you need to know whether a disk image is compatible with a particular emulator or emulated Environment?

Recommended Resources