Get desktop application:
View/edit binary Protocol Buffers messages
* Selected address type for a medium.
Used in: ,
ID is entry path (e.g. for imported tapes). */
ID hashing, implementation 1. */
Opaque identifier provided by the backend. */
* Configure operations.
Used in:
Set a configuration element
Retrieve a configuration element
* Selected filesystem type for a medium.
Used in: , ,
POSIX filesystem (no specific feature).
LTFS (Linear Tape File System).
RADOS fake filesystem.
* Notify operation.
Used in:
Device add operation.
Device lock operation.
Device unlock operation.
Medium was updated in the DSS.
* Target allocation operation. For now, those allocations are named 'READ' allocations.
Used in:
Read allocation.
Delete allocation.
* LRS protocol request, emitted by layout modules.
Request ID to match its future
response.
Greater means high-priority.
QOS is more important than priority. We first consider QOS to order request, and then priority.
Greater means high-priority.
Only exactly one of these fields is expected.
Write allocation body.
Read allocation body.
Release body.
Format body.
Notify body.
Is the request a ping request ?
Monitor body.
Configure body.
Stat body.
Used in:
Type of the request
JSON format containing
* Body of the format request.
Used in:
ID of the medium to format.
Medium file system.
True if the medium needs to be
unlocked after format.
True if we do not care about
* Body of the monitor request.
Used in:
* Body of the notify request.
Used in:
ID of the notified resource.
Notification operation.
Whether the client requires the
* Body of read allocation request, request n_required media among the provided med_ids (n_required <= n_med_ids).
Used in:
Number of media to actually
allocate among the ones specified in med_ids.
IDs of the requested media.
Operation done on the allocation.
* Body of the release request.
Used in:
Description of the media to release.
Whether the client requires the LRS to
perform only a sync without releasing the medium.
Kind of release:
* Release request for one medium.
Used in:
ID of the medium to release.
Outcome of the performed IO
(0 or -errno).
Amount of bytes written
on this medium (0 if the medium was only read).
Number of objects written on this medium (0 if the medium was only read).
Whether the client requires
the LRS to perform a sync or not.
Targeted grouping
* Body of the stats request
Used in:
Filter for stats namespace Notice protobuff does not leave 'namespace' as field name.
filter for stat name
filters on tags
* Body of write allocation request.
Used in:
Write allocation requests.
Requested resource family.
True if the client does not
want a medium it already allocated
Targeted library
Whether the client requires
to put all the data on the same medium.
Targeted grouping
* Request for one write accessible medium.
Used in:
Amount of data to be written
on the medium.
Tags to be satisfied.
Whether the client requires an
* LRS request kind (used in PhoResponse).
Used in: , ,
Media allocation with write ability.
Media allocation with read ability.
Read Media release and flush. The IO is considered
complete once the release and flush are done.
Write Media release and flush. The IO is considered
complete once the release and flush are done.
Medium format.
LRS notification to refresh device/medium
information.
Query information about the current status of the
LRS.
Get/Set configuration information from the LRS
Retrieve stats from the LRS
* Resource family.
Used in: , ,
Tape.
Directory.
RADOS Pool.
* Resource identifier.
Used in: , , , , , , , ,
Family type.
Resource name.
Resource library.
* LRS protocol response, emitted by the LRS.
Request ID, to be matched with
Only exactly one of these fields is expected.
Write allocation body.
Read allocation body.
Release body.
Format body.
Notify body.
Error body.
Is the response a ping response ?
Monitor body.
Configure body.
Stat body.
Used in:
JSON format containing
* Body of the error response.
Used in:
Error code,
-errno for homogeneity.
Kind of request that
* Body of the format response.
Used in:
ID of formatted medium.
* Body of the monitor response
Used in:
JSON str containing status information.
* Body of the notify response.
Used in:
ID of notified resource.
* Body of the read allocation response.
Used in:
Description of allocated media.
* Read allocation response for one medium.
Used in:
ID of the allocated
medium.
Mount point.
Filesystem type.
Address type.
* Body of the release response.
Used in:
IDs of released media.
Is a partial release ?
Kind of release:
* Body of the stat response
Used in:
JSON str containing stats.
* Body of the write allocation response.
Used in:
Description of allocated
media.
LRS sync threshold.
* Write allocation response for one medium.
Used in:
ID of the allocated
medium.
Size available on this
medium (potentially less than requested).
Mount point.
Filesystem type.
Address type.
* LRS sync threshold
Used in:
Number of requests threshold.
Written size threshold.
Time threshold in seconds.
Time threshold in nanoseconds.
* TLC protocol request, emitted by layout modules.
Request ID to match its future response.
Is the request a ping one ?
Drive lookup body
Load body
Unload body
Status body
Is the request a refresh one ?
Stat body
* Body of drive lookup request
Used in:
Serial number of the drive to lookup
* Body of the tlc load request
Used in:
Serial number of the target drive
Medium label to load
* Body of the stats request
Used in:
Filter for stats namespace
filter for stat name
filters on tags
* Body of the tlc status request
Used in:
If true, status cache is refreshed before
* Body of the tlc unload request
Used in:
Serial number of the target drive
Medium label to unload from drive
* TLC protocol response, emitted by the TLC.
Request ID, to be matched with
Ping body
Drive lookup response body
Error body
Load body
Unload body
Status body
This response is a successful refresh one
Stat body
* Body of drive lookup response.
Used in:
Address of the drive in lib
Address of the first drive in
lib
Loaded medium name (if any)
* Body of error response
Used in:
Error code, -errno for homogeneity.
JSON message describing the error
* Body of load response
Used in:
JSON message describing the load
* Body of the ping response.
Used in:
True if the TLC could successfully
Body of the stat response
Used in:
JSON str containing stats.
Body of status response
Used in:
JSON array describing the library
JSON message describing the status
* Body of unload response
Used in:
Unloaded tape label
Library addr where tape was unloaded
JSON message describing the unload