3. Globus tells you how to do X
Our site tells you have to do X at Stanford
4. Example: Firewall
Globus provides ports
We provide rules
▸ We also provide ticket references
Records of past communications with MedIRT
Globus tells you how to do X
Our site tells you have to do X at Stanford
9. GitHub Pages
Limited hosting options
▸ Static sites in AFS (old, uncertain future)
▸ Cloud-based Drupal (limited, Stanford-only)
▸ Custom server (too much)
GitHub Pages
▸ Cloud-based
▸ Local development (using Ruby & Jekyll)
▸ Open to changes
10. GitHub Issues
Track Work
▸ Store notes for complex changes
▸ Positive feedback loop with clients
("Everyone" has a GitHub account)
MinSec Compliance
▸ Link changes back to requirements
▸ "n/a" requirements logged with reason
▸ Incomplete requirements noted
12. The Server Section
(aka Globus Connect Server)
The biggest section on the site
▸ Complete instructions vs.
"Read this, but change X"
We want email & department info
We want encryption, and TLS 1.1+
▸ MinSec Requirements for *aaS products
Guide through authentication methods
▸ Local Clusters sometimes means Local Logins
13. The Client Section
(aka Globus Connect Personal)
The smallest section on the site
▸ Complete instructions vs.
"Read this, but change X"
▸ Link to Globus for things like Sharing
We still want email & department info
Warn about data risk level
14. The Scenarios Section
(aka "How Do I…?")
The biggest page on the site
▸ Started as a task list
▸ Morphed into a general FAQ
Entries grouped by section
▸ Matched to site layout
New entries to be added over time
▸ Also includes support questions
16. THANKS!
Have a look, submit feedback
https://github.com/stanford-rc/globus.stanford.edu
Submit a GitHub Issue
Or reach out at akkornel@stanford.edu
17.
18. The Accounts Section
Some people don't run GCP/GCS
▸ Shared endpoint
administrators
▸ Pipeline/Workflow developers
Some people have existing accounts
▸ XSEDE Users