Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://l10n.opensuse.org/api/translations/packages-i18n/t-master/en/?format=api",
    "source": [
        "LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical  units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel.\n\nThe TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each  userspace handler having to write boilerplate code.\n\ntcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called \"TCMU handlers\". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like."
    ],
    "previous_source": "",
    "target": [
        "LIO is the SCSI target in the Linux kernel. It is entirely kernel code, and allows exported SCSI logical  units (LUNs) to be backed by regular files or block devices. But, if we want to get fancier with the capabilities of the device we're emulating, the kernel is not necessarily the right place. While there are userspace libraries for compression, encryption, and clustered storage solutions like Ceph or Gluster, these are not accessible from the kernel.\n\nThe TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. But since the kernel-user interface that TCMU provides must be fast and flexible, it is complex enough that we'd like to avoid each  userspace handler having to write boilerplate code.\n\ntcmu-runner handles the messy details of the TCMU interface -- UIO, netlink, pthreads, and DBus -- and exports a more friendly C plugin module API. Modules using this API are called \"TCMU handlers\". Handler authors can write code just to handle the SCSI commands as desired, and can also link with whatever userspace libraries they like."
    ],
    "id_hash": 289978043506699656,
    "content_hash": 289978043506699656,
    "location": "",
    "context": "",
    "note": "leap/tcmu-runner/description",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 310,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 176,
    "source_unit": "https://l10n.opensuse.org/api/units/12620231/?format=api",
    "priority": 100,
    "id": 12620231,
    "web_url": "https://l10n.opensuse.org/translate/packages-i18n/t-master/en/?checksum=8406357e83e12d88",
    "url": "https://l10n.opensuse.org/api/units/12620231/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2016-12-01T17:22:32Z"
}