infra activities for eval 7 kickoff

[mwartell]

• update docx invitation
• release new armory-upload with eval7 s3 destination folder
• update AWS IAM perms to allow write-only to eval7 folder
• reconcile (adopt in toto?) Donizetti's master email list
• backup and clear DynamoDB
• create Armory v0.18.0 AMI for evalboxes
• figure out better model-weights mechanism
• implement create a serverless app to copy model_weights to destination directory #1962

[mwartell]

Armory-upload currently routes submitted model weights into an evalX folder (with everything else). But armory only knows to look for them under model-weights . I think in eval6 I sometimes copied the weights into model-weights so armory could find them easily. Going forward, what do you prefer: updating armory to search deeper (might be tricky to tell it which eval folder to look in), just having people download the weights themselves, or something else?

[swsuggs]

Hey that was my question . . .

But what if we just have armory-upload put them in both spots, then we can delete model-weights when no longer needed?

[mwartell]

We are making AWS Lambda copy from eval?/CODE/email/model-weights/foo.pt to model-weights/foo.pt upon upload under #1962

[swsuggs]

Eval 7 is completed.