1 / 6

Service Request / Service Activation

Join us at the EGEE04 conference in Pisa, Italy, where Florian Scharinger from EPCC will address essential questions about Service Requests (SR) and Service Activations (SA). Key topics will include distinguishing between SR and SA, changing the BAR interface, and finding the correct SR for an SA automatically. We will explore authorization processes for users requesting SAs and discuss the implications of sub-net specifications versus exact IP addresses. This session aims to clarify operations and services related to SR and SA, ensuring seamless user experience.

sakina
Télécharger la présentation

Service Request / Service Activation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service Request / Service Activation • F2F, EGEE04 conference, Pisa, Italy • Florian Scharinger, EPCC

  2. Agenda • SA/SR main questions: • How to distinguish between SR and SA • How to change BAR interface • Can we find the correct SR for a SA automatically? • How to authorise user for SA

  3. Distinguish between SR and SA • Possibilities: • Source/Destination: SR specifies sub-net, SA specifies exact IP address • Separate operations • Separate (Web) services

  4. How to change BAR interface • Request, Cancel, Query for SR and SA? • Can we use same parameters for SR and SA? • Naming? • SaQuery, SaGdftRequestService, SaVllRequestService,... • SrQuery, SrGdftRequestService, SrVllRequestService,... • Adding source/destination port? • But optional?

  5. Map SA to SR automatically? • Map • SA source/destination IP to • SR source/destination sub-net • No overlapping SR possible • Or does the user has to pass the SR handle for each SA request? • Even so, how to validate that SA really belongs to passed SR handle?

  6. Authorise User for SA • Do we need to authorise that a certain user can request an SA for a specific SR? • If yes, how? • SR would need to contain a list of authorised users

More Related