OGF 19, Raleigh NC

HPC Profile WG

Marty Humphrey, co-chair

Department of Computer ScienceUniversity of VirginiaCharlottesville, VA

OGF 19, Raleigh NC

HPC Profile WG Status

• HPC Basic Profile uploaded on Friday (v0.3)• New version already uploaded today (editor fixes)

• BES draft uploaded on Wed (v29)

• Changes since SC• Security section added to HPC Basic Profile (incl. X509)• Modifications to enhance interoperability

• Tooling issues, refactoring, etc.

OGF 19, Raleigh NC

Schedule

• 2:00 – 2:45: Overview of the HPC Basic Profile (Glenn Wasson)

• 2:45 – 3:00: “Attribute Matching” Extension (Chris Smith)

• 3:00 – 3:30: General Discussion• What to do next

OGF 19, Raleigh NC

“Activity Credential” Extension

• Aka “Delegation” Extension• Scope/Intent:

• “An ‘Activity Credential’ is not used for authentication to the HPC Basic Profile-compliant Web service; rather, such a credential is used for subsequent authentication e.g., to a data server or database, another HPC Basic Profile-compliant Web service, a credential-granting service, or an attribute service.”

• “Multiple of the “Common Cases” of [HPC-U] can require the ability to securely transmit an Activity Credential: 3.4 (“Types of Data Access”); 3.6 (“Multiple Organization Use Cases”); 3.12 (“Cycle Scavenging”).”

OGF 19, Raleigh NC

Use Cases of “Activity Credential”

1. Windows CCS: username/password to create a job

2. MyProxy

OGF 19, Raleigh NC

Approach

• “Such credentials are intended to be used by the activity described in the CreateActivity message JSDL. Consequently, this specification requires that the credentials also be conveyed within the CreateActivity message as a sibling element to the JSDL.”

OGF 19, Raleigh NC

Next Steps

• Additional use-cases?• Read the spec• Implement the spec• Improve the spec