[Feature] release repo

[xu-hao]

What problem(s) do you aim to solve?

Create a release repo containing submodules all pds related repos

What feature solves it and why?

Each maintainer of container releases their own container and send a pr.

What implementation(s) do you suggest?

Run integration test on Travis ci Anything else? Leave blank, as needed

[xu-hao]

RENCI/pds-release

[krobasky]

Create tickets for these next steps:

1. re-organize codes:
   • figure out how to get nested submodules
   • update install script to point at the right up.sh/down.sh
   • rename files under test.system, as needed
2. add tag&bag script to support an environment that has no git (secure enclave) The script should extract out the tags and roll everything together - design this
3. add testing
4. add more details to readme
5. add in other documentation

[krobasky]

Questions: a. if we move all the plugins from RENCI/pds to RENCI/pds-release, should we still make pds a separate repo, and have it be a sub-module to pds-release? b. if pds is a submodule to pds-release, should we rename it to pdspi-pds (to be consistent)? c. should we also move over AUTHORS, CHANGES, CODE_OF_CONDUCT, CONTRIBUTING?

[krobasky]

Regarding 2. above:

system.py creates the release by grabbing any existing tags from repos included under 'modules' directory; we want to reuse some of the source code in system.py (or maybe use travis) and create release.py to create a release that includes the docker image binaries so that an adopter can also just download and validate all the binaries and not have to build them on the secure enclave.

[krobasky]

...and we don't do the validation, the secure enclave people that download the binaries do the validation on those "blackboxes"

[krobasky]

update system testing with new API