Design

Gary,

Are the XSEDE Base Ansible configs that you are preparing designed to run against a pre-launched instance?

What base OS's will you support?

Are the Ansible configs ROLE based?

I'm a bit surprised that there's no additional recommended field in the data format for quantities.  For example, if the usage record is for a data transfer, wouldn't we want to know how much data was transferred?  If it's for a Kepler workflow, wouldn't we want some record of how much work (task

It isn't clear from the design doc, but it sounds like we're proposing to develop this from scratch as a set of Python scripts?  Are there really no existing software tools that we could re-purpose for this?  Something based on WebDAV or its successors?  Why not Globus Transfer?

Given that the requirements say that this service and the data it keeps needs to last through the current XSEDE period and most likely on to successors, are we certain that using Jetstream is a good idea? Have you confirmed that Jetstream's service lifetime extends as far as you need?

Section E.2.8 doesn't actually specify any protocols or credential requirements. Might as well say, "We don't currently have any requirements." 

Section E.2.2 says the system will only be used by XSEDE staff.

XCI-187_UsageCollectionService_Design-v0.1.pdf answers all my questions. Looks good!

-Jim

Section F.1 identifies two supporting documents that are included in the design.  The second one, the "XSEDE Identity Management Client Application Setup" document, should not be a Google Doc.

Version 1.1 looks good to me.  The revised login steps and workflow diagram from Lee are helpful.  My comments are below:

1) Remove the following text at the bottom of p.11: "The below flow diagram shows the typical flows:"

Sections E.2.2, E.2.5, and E.2.8 all seem to be saying that XSEDE shouldn't allow any other form of authentication in the XSEDE system (at least for non-admins) other than Web SSO.  This seems to exceed the authority of this document.  This is a design for XSEDE's Web SSO service, NOT a design fo