Got my first computing environment, job queue, and job running via AWS Batch.
AWS Batch has an API, and their docs are terrible.
Checked in with Marshall about remote life, what he's working on, what I'm working on, and what his hopes for his transition to the DevOps team look like.
His move to our team is essentially the worst kept secret.
Random CS tasks.
Lots of thinking about internal and external SLAs.
Daily To-Do List:
Get these example Jobs to actually run, adjusting minimum number of vCPUs because it's a requirement that Amazon just never states anywhere.
Be mad about anti-asia sentiments coming from fear of the coronavirus.
Issues/Questions:
What low-level jobs could be used to test AWS Batch with real data?
Do we have a situation where spot instances would be helpful?
I don't actually know if we could, but spot instances come up a lot in Batch documentation.
Ashley, do you have an overall vision for how Jobs would be split up?
Oh god, how does this API work?
I'm not sure why, but running the actual Jobs in Batch takes a really long time. I will have to investigate why.
Thoughts/Solutions:
We should go back through our infra docs and clean them up.
Where I left off yesterday:
Daily To-Do List:
Issues/Questions:
Thoughts/Solutions: