SNAP containerization

[NRCgg]

Containerized SNAP

Advantages

By implementing SNAP in a container the following advantages would be realized:

• Removes the installation problems for the various platforms.
  • Many of the issue reports and request for assistance are related to installation of SNAP.
  • Installation issues frequently due to OS, java versions, and permissions related to environment.
• Distribution would be greatly simplified.
  • Groups of plugins could be placed in different containers and validated to function correctly.
  • Containers would be "ready to go". No (or very little) user setup!
  • Pre-built containers for:
    • "COMPLETE" - Everything SNAP supports and the user is licensed to use
    • "TRACE-PARCS" - All the plugins for TRACE, PARCS, UQ, Batch, Git, etc.
    • "MELCOR-MACCS" - All the plugins for MELCOR, MACCS, SecPop, UQ, Batch, Git, etc.

Disadvantages

• Container support is weak for Windows OS variants.
  • While there are Windows containers, they do not generally provide graphic interactions with the containerized application.
    • Could "noVNC" type of interface help this problem? See KASM container services. Also, see this NIH publication.

[NRCgg]

The "KASM" solution looks VERY attractive! Could we simply install SNAP in a KASM based container and provide links to a "SNAP container service" (maybe Kubernetes based?).