jgeiger
Web Developer II · Account member
jgeiger's latest activity
Monday, February 02 2009
Friday, January 30 2009
-
- Tag set to analysis, data, performance
- State changed from new to open
This is basing the assumption that you're running on a single node. It does give you the instance id and process id of the worker that processed the chunk. It w...
Thursday, January 29 2009
-
jgeiger created the ticket
It seems that AWS can throw an error if you try to create a node and it doesn't have capacity.
The user will see the default 500 error page, but going forward i...
-
- Milestone set to 1.x
- State changed from new to resolved
I've moved the "show" links for anything that has a show option to the name or ID of that item.
When the job is finished, the download link will appear next to ...
-
- Milestone set to 1.x
- State changed from new to resolved
added a meta refresh tag for the job index and show pages which will refresh the pages every 15 seconds.
-
- Milestone set to 1.x
- State changed from new to resolved
The new build has graphics for the "new" links.
Wednesday, January 28 2009
-
- State changed from new to resolved
The system will now check if the access and secret keys are part of the user data. If not, it will symlink an error page as the index informing the user of the ...
-
jgeiger created the ticket
If the user doesn't enter the proper information in the user data section, we need to inform them of this issue since the instance they launched will not work.
-
- State changed from new to hold
Based on the performance of SimpleDB this far, I would not suggest using it as the database backend.
Also, the use of a common database backend will be an issue...
-
- Tag changed from access, keys to access, documentation, keys
Brian will be updating the documentation when he collects screenshots for the paper. I'll confirm this with him.