Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Service Owner: Marina Adomeit
  • Member of the Technical Steering committee: Christos Kanellopoulos 
  • Member of the Governance Steering Committee: Klaas Wierenga
  • Lead Architect and member of the Technical Steering Committee: Leif Johanson
  • Development team: Fresia Perez Arriagada, Elena Rakhimova
  • Operations team: Erik Bergstörm, Maria Haide Haider (Sunet)
  • GEANT T&I operation support/Core team: Nicole Harris
  • Test team: WP9 - Marcin Wolski (ask what testing can be done)
  • IPR: Magdalena Rzaca
  • GDPR: Magdalena Rzaca GEANT GDPR team
  • WP5 leaders ultimately responsible for the T&I service portfolio delivered through the GEANT project: Licia Florio, Marina Adomeit

...

No

Work item

Responsible

Comment

Status

1Preparation of documentation





Service Description

-Development team prepares

-SO signs off

RA21 Discovery Service Seamless Access Description 

Marina to give a try to document - talk to Outreach person for SPs Laura Paglione. She will be working to adapt the documentation from the github into docs that SPs can use. Marina to peer with her, and give her direct feedback - include Heather in this conversation as well. 


Status
colourGreen
titledone

don

Service policy (Terms of use, SLA)

-Development team prepares

-SO signs off

RA21 Discovery Service Seamless Access Policy
Terms of use are out of scope for service delivered by GEANT. It is responsibility of seamlessaccess.org. Example from InAcademia https://inacademia.org/service-policy/, and eduroam https://www.eduroam.org/wp-content/uploads/2016/05/GN3-12-192_eduroam-policy-service-definition_ver28_26072012.pdf  Marina can check if there is something additional in the contract - especially about who responsibility it is to support the end-users. 
SLA should be defined between seamlesaccess.org and GEANT. The beta service should be best effort (there could be some tension with the publishers though )
For the beta service, there is an MoU which is being signed. (update from 16 July - orcid the last one to sign, it should be done this week)

Status
titleon HOLD

This should be done for the production service. The beta service is to test this out. 


Branding and Visibility

-Development team prepares

-SO signs off

This is probably not relevant to the part of the service delivered by GEANT. It is responsibility of seamlessaccess.org

Info from July 2019 from Heather: There will be a website soon - we now have a UX person contracted (Sean, Chicago), and that’s one of the things on his plate

Status
colourBlue
titleout of scope


Operational Requirements

-Development team prepares

-SO signs off

RA21 Discovery Seamless Access Operational Requirements

Marina to check if anything needs to be updated or what is missing. 

Status
colourGreen
titleDONE


OLA

-Development team prepares

-SO and GEANT T&I operation support/Core team sign off

RA21 Discovery Seamless Access Operational Level Agreements (- OLA)

This is between SUNET and GEANT.

Marina to set this up based on the InAcademia OLA. 

Operational documentation

Draft OLA was defined and is within SUNET NOC for approval

Status
colourYellow
titleIN PROGRESS


Deployment architecture 

-Development team prepares

-SO signs off

RA21 Discovery Operational DocumentationSeamless Access Deployment Architecture

Marina to set this up based on the OLA. 

Status
colourGreen
titleDONE


Operational documentation and processes

-Development team prepares

-SO signs off

RA21 Discovery Operational Processes

Change management, Incident response, ... 

Marina to find the TMF questionnaires to use them.

Seamless Access Operational Documentation

Status
colourGreen
titleDONE


User documentation

Who is responsible for this?

In scope for seamless access. 

Who are the users - also needs to be clearly defined. Seamless access provide service to the SPs, and they provide support to the users. 

Status
colourBlue
titleout of scope


User support

Who is responsible for this? 

In scope for seamless access. 

Status
colourBlue
titleout of scope


GDPR - data inventory, privacy notice, DPA

-GDPR team +SO + technical architect

-GDPR accountable and SO signs offWe should clarify the roles regarding the GDPR.  We thing that  GEANT and SUNET are data controller, and then probably no DPA is needed. CDNs are data processors. But we would to provide the privacy notice.  

GDPR evaluation was done and conclusion is that Seamless Access does not process any personal data.

 Seamless Access Data Processing

Status
colourGreen
titleDONE

2Test and validation



Make a test plan

Development team and Test team prepares

Pen/Security done by DFN cert. 

Additional testing could be done as well if skilled javascript testers can be found.

Status
colourGreen
titleDONE

Talk to Marcin and understand the requirements for testing first.

Code testing would be needed as well. - Marina to check with Marcin what can be done, and ask for the schedule. This is all Leifs code - we need to pull him in where he sees that testing is needed, when it will be available for testing.  

Pen/Security would be needed - Marina can check with the project if we can get somebody from carnet and DFN to do.

From the MoU:

Implement and test the Beta service to ensure its stability, functionality, security, usability, broad applicability, and fitness for purpose as described in this MoU. 

3IPR compliance checking



IPR compliance

IPR accountable + SO + technical architect 

Route the request through GEANT T&I operation support/Core team

GEANT IPR coordinator has signed off the IPR. Note that was given on 6th December 2019: "Update regarding the scanning of the code provided https://github.com/TheIdentitySelector in most of the files no source/binary files were detected, consequently no licence/vulnerabilities were detected…In the js-storage-master file there were 3 licences detected (MIT licences) – as this is permissive licence, there are no further issues with it."

Status
colourGreen
titleDONE

To whoom the IPR belongs to ? Needs discussion. 

Magda looked in the IPR - look to the MoU.  

4GDPR compliance checkingGDPR accountable


Data inventory and mapping

-GDPR team +SO + technical architect

-GDPR accountable and SO signs off

Seamless Access Data Processing

Conclusion is that SA doesn't process any personal data, so Data Inventory and Mapping are not needed. 

Status
colourGreen
titleDONE


Hopefully this will be easy as the service is privacy perserving. The only one could be the IP address. Marina will ask will start with the data inventory and reslove the ip address question as well.  Privacy notice and DPA

-GDPR team +SO + technical architect

-GDPR accountable and SO signs off

Not needed. 

Status
colourBlue
titleout of scope

5Operational team establishment



Appoint service ownerWP5 leadersDone. The service owner is responsible for service as delivered via GEANT project.

Status
colourGreen
titleDONE


Define roles, skills, manpower neededDevelopment teamWe need to check this with what seamlessaccess.org, but if we deliver a service then it is our internal matter.

Status
colourGreen
titleDONE


Appoint operational team members

Service Owner

Done

Status
colourGreen
titleDONE

6Operational team training



Training the operational team


Not needed

Status
colourGreen
titleDONE

7Support team establishment



Establish the support team

Will be provided by seamless access, out of scope for GEANT

Status
colourBlue
titleout of scope

8Support team training



Training of the support team


Will be provided by seamless access, out of scope for GEANT

Status
colourBlue
titleout of scope

9Deployment in production environment



Monitoring set up

Operations team based on the requirements from the technical lead and SO

SO signs off when implemented

Need to define which kind of metrics we can take so that we measure how much the service is used. Marina and Heather need to talk to Leif.

Can we do something in monitoring to support the MoU: 

Implement and test the Beta service to ensure its stability, functionality, security, usability, broad applicability, and fitness for purpose as described in this MoU.

Gather evidence on the utility of the Beta service and its impact in current access workflows with respect to the goals of the Coalition

Seamless Access Monitoring and Reporting

https://status.seamlessacccess.org  

Status
colourGreen
titleDONE


Back-up and restore

Operations team based on the requirements from the technical lead and SO

SO signs off when implemented

Not needed

Status
colourBlue
titleout of scope


VMs

Operations team based on the requirements from the technical lead and SO

SO signs off when implemented

One PoP is Two nodes are provided by SUNET.

Second PoP will be deployed Two nodes are operated on AWS, in two different regions. .

Status
colourGreen
titleDONE


Deployment

Operations team based on the requirements from the technical lead and SO

SO signs off when implemented

Deployment is completed on SUNET nodes.

In progress is deployment on AWS nodes.

Status
colourYellow
titleIN PROGRESS


CDN


Provided by Fastly.

The bill is currently picked up by SUNET, but this should move to GEANT. 

Status
colourYellow
titleIN PROGRESS

CDN

?

?

10Service Promotion



NA, responsibility of the seamless access

Will be provided by seamless access, out of scope for GEANT.

Outreach person for SPs Laura Paglione (laura@seamlessaccess.org). Feel free to reach out to her if you have questions or ideas.

Status
colourBlue
titleout of scope

11PLM Documentation



TBD if applicable

Status
colourBlue
titleout of scope


Other notes: the success criteria - what do we consider to be the success criteria for the project, from the GEANT side.