OpenJun 20, 2017
Overdue by 8 year(s)
•Due by June 30, 2017
•Last updated Picking the nits in EC2 fleet management that we either didn't have time for before the Deloitte workshop, or discovered during it.
Success condition:
- The EC2 fleet management automation has a pleasant administrative UI with no glaring easily-fixed problems;
- Everyone waiting to use the probcomp stack on the cloud has a machine; and
- Everyone using the probcomp stack on the cloud is migrated to cloudformation-managed instances.
Explicitly out of scope:
- Cost management;
- Auto-scaling;
- Cluster computing;
- Making it easy for someone to run the stack on their infrastructure or their AWS account; and
- Rearranging the fleet to work around weird AWS resource limits (instead, ask for those limits to be raised).
14% complete
List view
0 issues of 6 selected
- Status: Open.#22 In probcomp/probcomp-stack;
- Status: Open.#23 In probcomp/probcomp-stack;
- Status: Open.#24 In probcomp/probcomp-stack;
- Status: Open.#21 In probcomp/probcomp-stack;
- Status: Open.#25 In probcomp/probcomp-stack;
- Status: Open.#1 In probcomp/probcomp-stack;