Gatekeeper configured in its storage subsystem. If one is found, the Core Server asks the Gatekeeper for its monitor types by calling the gk_GetMonitorTypes function which calls the locally implemented gk_site_GetMonitorTypes function which determines which types of requests to monitor. This query by the Core Server occurs each time the Core Server connects to the Gatekeeper, which occurs whenever the Core Server or Gatekeeper is restarted. Therefore, if a site wants to change the types of requests to be monitored, the Core Server and Gatekeeper must be restarted.
For each type of request being monitored, the Core Server calls the appropriate Gatekeeping Service API (gk_Create, gk_Open, gk_Stage) passing along information pertaining to the request. This information includes:
Table 5. Gatekeeping Call Parameters
Name | Description | create | open | stage |
|
|
|
|
|
|
|
|
|
|
AuthorizedCaller | Whether or not the request | Y | Y | Y |
| is from an authorized caller. |
|
|
|
| These requests cannot be |
|
|
|
| delayed or denied by the site |
|
|
|
| policy. |
|
|
|
|
|
|
|
|
BitFileID | The unique identifier for the | N/A | Y | Y |
| file. |
|
|
|
|
|
|
|
|
ClientConnectId | The end client’s connection | Y | Y | Y |
| uuid. |
|
|
|
|
|
|
|
|
RealmId | The HPSS realm identifier | Y | Y | Y |
| for the user. |
|
|
|
|
|
|
|
|
GroupId | The user’s group identifier | Y | Y | Y |
|
|
|
|
|
HostAddr | Socket information for | Y | Y | Y |
| originating host. |
|
|
|
|
|
|
|
|
OpenInfo | Open file status flag | N/A | Y | N/A |
| (Oflag). |
|
|
|
|
|
|
|
|
StageInfo | Information specific to stage | N/A | N/A | Y |
| (flags, length, offset, and |
|
|
|
| storage level). |
|
|
|
|
|
|
|
|
UserId | The user’s identifier. | Y | Y | Y |
|
|
|
|
|
Each Gatekeeping Service API will then call the appropriate Site Interface passing along the information pertaining to the request. If the request had AuthorizedCaller set to TRUE, then the Site "Stat" Interface will be called (gk_site_CreateStats, gk_site_OpenStats, gk_site_StageStats) and the Site Interface will not be permitted to return any errors on these requests. Otherwise, if AuthorizedCaller is set to FALSE, then the normal Site Interface will be called (gk_site_Create, gk_site_Open, gk_site_Stage) and the Site Interface will be allowed to return no error or return an error to either retry the request later or deny the request. When the request is being completed or aborted the appropriate Site Interface will be called (gk_site_Close, gk_site_CreateComplete, gk_site_StageComplete). Examples of when a request gets aborted are when the Core Server goes
HPSS Installation Guide | July 2008 |
Release 6.2 (Revision 2.0) | 100 |
