Figure out how to handle custom docker/singularity images

[nmerket]

For some analyses (ComStock, I'm looking at you) we'll need to use a different image from the standard nrel/openstudio docker and singularity images. We should figure out a nice way to handle that.

[bonnema]

@nmerket https://github.com/NREL/ComStock/tree/develop/build

[nmerket]

@bonnema I don't have access to that repo.

[bonnema]

I think @rHorsey has to give you access. Ry and I are still working out some kinks...

[rHorsey]

@nmerket This'll be resolved through the process of merging #65 for eagle. Let's chat more about AWS when that's closer, and I'll think about local docker once we've made sure https://github.com/NREL/buildstockbatch/tree/rHorsey/enable-com is working on eagle.

[asparke2]

@nmerket for the singularity images on Eagle this hasn't been an issue.

Here's what we've been doing in the yml:

os_version: covid19v3
os_sha: 3472e8b799
sys_image_dir: /lustre/eaglefs/shared-projects/buildstock/singularity_images

and here's the singularity image name on shared-projects/buildstock/singularity_image:

OpenStudio-covid19v3.3472e8b799-Singularity.simg

Not sure how you'd want to handle AWS though... One option could be to use Amazon ECR to host a docker registry w/ our custom images, but that seems destined to be a lot of work to teach/maintain. Another option could be to pick a shared place on S3 and just upload the docker image files to there like we do for Eagle. If we used the same naming convention as for singularity images, then I think it would be something like allowing sys_image_dir to accept S3 paths.