lahirujayathilake opened a new pull request, #474:
URL: https://github.com/apache/airavata-custos/pull/474

   ACCESS uses the AMIE protocol to notify allocation sites about new projects, 
users, and changes to their HPC allocations. This PR wires that protocol into 
Custos. When ACCESS sends us an event, we now create or update the right 
records in Custos automatically.
   
   Addresses the Issue #466 
   And this PR changes depends on the changes
   * 
https://github.com/apache/airavata-custos/commit/231acfeb4c8862b88d7f36e68e5ab3f4ed7740a7
   * 
https://github.com/apache/airavata-custos/commit/50f03d8eeae366e018308576415c661dbc0e5dd8
   * 
https://github.com/apache/airavata-custos/commit/b5ef5142b7422ded45ef2659fbc5aec2aadd7269
   
     ## What's covered
   
     - **Project creation** -  when ACCESS awards a new project, we record the 
project, the allocation amount, the time window, and the principal investigator.
     - **User account creation** - when ACCESS adds a user to a project, we 
create their user record, their organization, and their cluster account.
     - **Supplements and renewals** - when ACCESS extends a project's 
allocation (more compute time, longer window, etc.), the change is recorded 
against the existing project.
     - **Project lifecycle** - inactivate / reactivate events from ACCESS 
propagate to the project and all its allocations and memberships.
     - **User lifecycle** - same for individual user accounts on a project.
     - **User profile updates** - name, email, organization, and certificate 
identities (DNs) stay in sync with what ACCESS sends.
     - **User merges** - when ACCESS merges two duplicate user records, we 
follow it to merge the users and keep the audit records.
   
     ## What's not in this PR (planned for follow-up)
   
     - **POSIX username generation policy.** Today we generate a temporary 
username placeholder when creating a cluster account. The actual username 
scheme, whether Custos picks it or whether comanage / a downstream identity 
system supplies it, is an open architectural choice that will be settled when 
we wire up the SLURM / comanage provisioner.
     - **Downstream provisioner.** This PR ensures Custos records every event 
ACCESS sends. The next step is the system that actually creates the posix 
accounts on the cluster (SLURM setup, COmanage account creation, etc.). 
     - **Automated tests for the AMIE handlers.** The previous test suite was 
tied to an older internal layout and didn't survive the consolidation. 
Rebuilding it against the current structure is a follow-up task.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to