Changes
Translation components API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/translations/debian-handbook/12_advanced-administration/de/changes/?format=api&page=8
{ "count": 772, "next": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/changes/?format=api&page=9", "previous": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/changes/?format=api&page=7", "results": [ { "unit": "https://hosted.weblate.org/api/units/82698193/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.359006+02:00", "action": 59, "target": "<primary>Installation</primary><secondary>Automatische Installation</secondary>", "old": "", "details": { "state": 10, "source": "<primary>virtualization</primary><secondary>guest</secondary>", "old_state": -1 }, "id": 34030530, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030530/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698193/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358974+02:00", "action": 30, "target": "<primary>virtualization</primary><secondary>guest</secondary>", "old": "<primary>installation</primary><secondary>automated installation</secondary>", "details": {}, "id": 34030529, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030529/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698192/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358941+02:00", "action": 59, "target": "<primary>Installation</primary><secondary>Automatische Installation</secondary>", "old": "", "details": { "state": 10, "source": "<primary>virtualization</primary><secondary>host</secondary>", "old_state": -1 }, "id": 34030528, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030528/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698192/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358910+02:00", "action": 30, "target": "<primary>virtualization</primary><secondary>host</secondary>", "old": "<primary>installation</primary><secondary>automated installation</secondary>", "details": {}, "id": 34030527, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030527/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698191/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358877+02:00", "action": 59, "target": "<primary>Verteilung</primary>", "old": "", "details": { "state": 10, "source": "<primary>domU</primary>", "old_state": -1 }, "id": 34030526, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030526/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698191/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358845+02:00", "action": 30, "target": "<primary>domU</primary>", "old": "<primary>deployment</primary>", "details": {}, "id": 34030525, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030525/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698190/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358812+02:00", "action": 59, "target": "<primary>Verteilung</primary>", "old": "", "details": { "state": 10, "source": "<primary>dom0</primary>", "old_state": -1 }, "id": 34030524, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030524/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698190/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358780+02:00", "action": 30, "target": "<primary>dom0</primary>", "old": "<primary>deployment</primary>", "details": {}, "id": 34030523, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030523/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698189/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358748+02:00", "action": 59, "target": "<primary>libvirt</primary>", "old": "", "details": { "state": 10, "source": "<primary>hypervisor</primary>", "old_state": -1 }, "id": 34030522, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030522/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698189/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358716+02:00", "action": 30, "target": "<primary>hypervisor</primary>", "old": "<primary>libvirt</primary>", "details": {}, "id": 34030521, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030521/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698188/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358683+02:00", "action": 59, "target": "<primary>Virtualizierung</primary>", "old": "", "details": { "state": 10, "source": "<primary>paravirtualization</primary>", "old_state": -1 }, "id": 34030520, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030520/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698188/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358652+02:00", "action": 30, "target": "<primary>paravirtualization</primary>", "old": "<primary>virtualization</primary>", "details": {}, "id": 34030519, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030519/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698187/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358616+02:00", "action": 59, "target": "", "old": "", "details": { "state": 0, "source": "If that is not the case, you can access the BIOS of your system and check for entries like “Intel Virtualization Technology”/“Intel VT-x” or “SVM mode” (AMD) - usually to be found in the CPU configuration in the Advanced section.", "old_state": -1 }, "id": 34030518, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030518/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698186/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358582+02:00", "action": 59, "target": "Für AMD-Prozessoren können Sie <command>grep svm /proc/cpuinfo</command> ausführen", "old": "", "details": { "state": 10, "source": "For AMD processors you can execute <command>grep svm /proc/cpuinfo</command> to check for AMD's Secure Virtual Machine.", "old_state": -1 }, "id": 34030517, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030517/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698186/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358550+02:00", "action": 30, "target": "For AMD processors you can execute <command>grep svm /proc/cpuinfo</command> to check for AMD's Secure Virtual Machine.", "old": "For AMD processors you can execute <command>grep svm /proc/cpuinfo</command>", "details": {}, "id": 34030516, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030516/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698185/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358517+02:00", "action": 59, "target": "Für Intel-Prozessoren können Sie <command>grep vmx /proc/cpuinfo</command> ausführen", "old": "", "details": { "state": 10, "source": "For Intel processors you can execute <command>grep vmx /proc/cpuinfo</command> to check for Intel's Virtual Machine Extensions.", "old_state": -1 }, "id": 34030515, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030515/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698185/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358485+02:00", "action": 30, "target": "For Intel processors you can execute <command>grep vmx /proc/cpuinfo</command> to check for Intel's Virtual Machine Extensions.", "old": "For Intel processors you can execute <command>grep vmx /proc/cpuinfo</command>", "details": {}, "id": 34030514, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030514/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698184/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358447+02:00", "action": 59, "target": "VirtualBox ist eine virtuelle Maschine, die größtenteils aus freier Software besteht (einige zusätzliche Komponenten sind unter einer proprietären Lizenz erhältlich). Unglücklicherweise befindet sie sich in Debians \"Contrib\"-Abschnitt, da sie einige vorkompilierte Dateien enthält, die ohne einen proprietären Compiler nicht neu kompiliert werden können und sie befindet sich derzeit nur in Debian Unstable, da Oracles Richtlinien es unmöglich machen, sie in einer stabilen Debian-Veröffentlichung sicher zu halten (siehe <ulink url=\"https://bugs.debian.org/794466\">#794466</ulink>). Obwohl es jünger als VMWare und auf die i386- und amd64-Architekturen beschränkt ist, enthält es immer noch einige Schnappschüsse und andere interessante Funktionen. <ulink type=\"block\" url=\"https://www.virtualbox.org/\" />", "old": "", "details": { "state": 10, "source": "VirtualBox is a virtual machine that is mostly free software (some extra components are available under a proprietary license). Unfortunately it is in Debian's “contrib” section because it includes some precompiled files that cannot be rebuilt without a proprietary compiler and it currently only resides in Debian Unstable as Oracle's policies make it impossible to keep it secure in a Debian stable release (see <ulink url=\"https://bugs.debian.org/794466\">#794466</ulink>). While younger than VMWare and restricted to the i386 and amd64 architectures, it still includes some “snapshotting“ and other interesting features. <ulink type=\"block\" url=\"https://www.virtualbox.org/\" />", "old_state": -1 }, "id": 34030513, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030513/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698184/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358415+02:00", "action": 30, "target": "VirtualBox is a virtual machine that is mostly free software (some extra components are available under a proprietary license). Unfortunately it is in Debian's “contrib” section because it includes some precompiled files that cannot be rebuilt without a proprietary compiler and it currently only resides in Debian Unstable as Oracle's policies make it impossible to keep it secure in a Debian stable release (see <ulink url=\"https://bugs.debian.org/794466\">#794466</ulink>). While younger than VMWare and restricted to the i386 and amd64 architectures, it still includes some “snapshotting“ and other interesting features. <ulink type=\"block\" url=\"https://www.virtualbox.org/\" />", "old": "VirtualBox is a virtual machine that is mostly free software (some extra components are available under a proprietary license). Unfortunately it is in Debian's “contrib” section because it includes some precompiled files that cannot be rebuilt without a proprietary compiler and it currently only resides in Debian Unstable as Oracle's policies make it impossible to keep it secure in a Debian stable release (see <ulink url=\"https://bugs.debian.org/794466\">#794466</ulink>). While younger than VMWare and restricted to the i386 and amd64 architectures, it still includes some snapshotting and other interesting features. <ulink type=\"block\" url=\"https://www.virtualbox.org/\" />", "details": {}, "id": 34030512, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030512/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698183/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358379+02:00", "action": 59, "target": "VMware ist ein proprietärer virtueller Rechner; da er einer der ältesten ist, ist er auch einer der bekanntesten. Er funktioniert nach ähnlichen Prinzipien wie QEMU. VMware bietet erweiterte Funktionen wie Schnappschüsse eines laufenden virtuellen Rechners. <ulink type=\"block\" url=\"https://www.vmware.com/\" />", "old": "", "details": { "state": 10, "source": "VMWare is a proprietary virtual machine; being one of the oldest out there, it is also one of the most widely-known. It works on principles similar to QEMU. VMWare proposes advanced features such as “snapshotting“ a running virtual machine. <ulink type=\"block\" url=\"https://vmware.com/\" />", "old_state": -1 }, "id": 34030511, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030511/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698183/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358328+02:00", "action": 30, "target": "VMWare is a proprietary virtual machine; being one of the oldest out there, it is also one of the most widely-known. It works on principles similar to QEMU. VMWare proposes advanced features such as “snapshotting“ a running virtual machine. <ulink type=\"block\" url=\"https://vmware.com/\" />", "old": "VMWare is a proprietary virtual machine; being one of the oldest out there, it is also one of the most widely-known. It works on principles similar to QEMU. VMWare proposes advanced features such as snapshotting a running virtual machine. <ulink type=\"block\" url=\"https://www.vmware.com/\" />", "details": {}, "id": 34030510, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030510/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698182/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358293+02:00", "action": 59, "target": "QEMU ist ein Software-Emulator eines vollständigen Rechners. Die Leistungen sind weit geringer als die Geschwindigkeit, die man mit einer Ausführung auf Hardware (\"native\") erreichen könnte, aber mit ihm ist es möglich, nicht modifizierte oder experimentelle Betriebssysteme auf der emulierten Hardware auszuführen. Mit ihm kann man auch eine andere Hardware-Architektur emulieren: so kann zum Beispiel ein <emphasis>amd64</emphasis>-System einen <emphasis>arm</emphasis>-Rechner emulieren. QEMU ist freie Software. <ulink type=\"block\" url=\"https://www.qemu.org/\" />", "old": "", "details": { "state": 10, "source": "QEMU is a software emulator for a full computer; performances are far from the speed one could achieve running natively, but this allows running unmodified or experimental operating systems on the emulated hardware. It also allows emulating a different hardware architecture: for instance, an <emphasis>amd64</emphasis> system can emulate an <emphasis>arm</emphasis> computer. QEMU is free software. <ulink type=\"block\" url=\"https://qemu.org/\" />", "old_state": -1 }, "id": 34030509, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030509/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698182/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358262+02:00", "action": 30, "target": "QEMU is a software emulator for a full computer; performances are far from the speed one could achieve running natively, but this allows running unmodified or experimental operating systems on the emulated hardware. It also allows emulating a different hardware architecture: for instance, an <emphasis>amd64</emphasis> system can emulate an <emphasis>arm</emphasis> computer. QEMU is free software. <ulink type=\"block\" url=\"https://qemu.org/\" />", "old": "QEMU is a software emulator for a full computer; performances are far from the speed one could achieve running natively, but this allows running unmodified or experimental operating systems on the emulated hardware. It also allows emulating a different hardware architecture: for instance, an <emphasis>amd64</emphasis> system can emulate an <emphasis>arm</emphasis> computer. QEMU is free software. <ulink type=\"block\" url=\"https://www.qemu.org/\" />", "details": {}, "id": 34030508, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030508/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698181/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358229+02:00", "action": 59, "target": "<primary>Virtualizierung</primary>", "old": "", "details": { "state": 10, "source": "<primary>VirtualBox</primary>", "old_state": -1 }, "id": 34030507, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030507/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698181/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358197+02:00", "action": 30, "target": "<primary>VirtualBox</primary>", "old": "<primary>virtualization</primary>", "details": {}, "id": 34030506, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030506/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698180/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358164+02:00", "action": 59, "target": "<primary>LVM</primary>", "old": "", "details": { "state": 10, "source": "<primary>QEMU</primary>", "old_state": -1 }, "id": 34030505, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030505/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698180/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358132+02:00", "action": 30, "target": "<primary>QEMU</primary>", "old": "<primary>LVM</primary>", "details": {}, "id": 34030504, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030504/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698179/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358099+02:00", "action": 59, "target": "<primary>Nagios</primary>", "old": "", "details": { "state": 10, "source": "<primary>Bochs</primary>", "old_state": -1 }, "id": 34030503, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030503/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698179/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358068+02:00", "action": 30, "target": "<primary>Bochs</primary>", "old": "<primary>Nagios</primary>", "details": {}, "id": 34030502, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030502/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698178/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358035+02:00", "action": 59, "target": "<primary>LVM</primary>", "old": "", "details": { "state": 10, "source": "<primary>VMWare</primary>", "old_state": -1 }, "id": 34030501, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030501/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698178/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.358002+02:00", "action": 30, "target": "<primary>VMWare</primary>", "old": "<primary>LVM</primary>", "details": {}, "id": 34030500, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030500/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698177/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357969+02:00", "action": 59, "target": "<primary>LXC</primary>", "old": "", "details": { "state": 10, "source": "<primary>Xen</primary>", "old_state": -1 }, "id": 34030499, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030499/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698177/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357937+02:00", "action": 30, "target": "<primary>Xen</primary>", "old": "<primary>LXC</primary>", "details": {}, "id": 34030498, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030498/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698176/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357898+02:00", "action": 59, "target": "Der Grund für die zweite Unterteilung (in <filename>md1</filename> und <filename>md2</filename>) ist weniger offensichtlich und hängt eher mit der Erkenntnis zusammen, dass die Zukunft unsicher ist. Wenn der Arbeitsplatzrechner erstmals eingerichtet wird, sind die genauen Speichererfordernisse nicht unbedingt mit absoluter Sicherheit bekannt; außerdem können sie sich im Laufe der Zeit verändern. In unserem Fall können wir den tatsächlichen Bedarf an Speicherplatz für Videoszenen und vollständige Videoclips nicht im Vorhinein kennen. Falls ein bestimmter Clip eine sehr hohe Anzahl an Szenen benötigt, und die VG für redundante Daten weniger als halb voll ist, können wir einen Teil ihres nicht genutzten Platzes anderweitig verwenden. Wir können einen der physischen Datenträger entfernen, zum Beispiel <filename>md2</filename> aus <filename>vg_raid</filename> und ihn entweder direkt <filename>vg_bulk</filename> zuordnen (falls die voraussichtliche Dauer des Einsatzes kurz genug ist, um den vorübergehenden Leistungsabfall in Kauf zu nehmen), oder die RAID-Anordnung auf <filename>md2</filename> auflösen und seine Komponenten <filename>sda6</filename> und <filename>sdc6</filename> in die Massen-VG integrieren (die damit um 200 GB statt um 100 GB anwächst). Der logische Datenträger <filename>lv_rushes</filename> kann dann nach Maßgabe des Bedarfs vergrößert werden.", "old": "", "details": { "state": 10, "source": "The rationale for the second split (<filename>md2</filename> vs. <filename>md3</filename>) is less clear-cut, and more related to acknowledging that the future is uncertain. When the workstation is first assembled, the exact storage requirements are not necessarily known with perfect precision; they can also evolve over time. In our case, we can't know in advance the actual storage space requirements for video rushes and complete video clips. If one particular clip needs a very large amount of rushes, and the VG dedicated to redundant data is less than halfway full, we can re-use some of its unneeded space. We can remove one of the physical volumes, say <filename>md3</filename>, from <filename>vg_raid</filename> and either assign it to <filename>vg_bulk</filename> directly (if the expected duration of the operation is short enough that we can live with the temporary drop in performance), or undo the RAID setup on <filename>md3</filename> and integrate its components <filename>sda5</filename> and <filename>sdc5</filename> into the bulk VG (which grows by 600 GB instead of 300 GB); the <filename>lv_rushes</filename> logical volume can then be grown according to requirements.", "old_state": -1 }, "id": 34030497, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030497/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698176/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357857+02:00", "action": 30, "target": "The rationale for the second split (<filename>md2</filename> vs. <filename>md3</filename>) is less clear-cut, and more related to acknowledging that the future is uncertain. When the workstation is first assembled, the exact storage requirements are not necessarily known with perfect precision; they can also evolve over time. In our case, we can't know in advance the actual storage space requirements for video rushes and complete video clips. If one particular clip needs a very large amount of rushes, and the VG dedicated to redundant data is less than halfway full, we can re-use some of its unneeded space. We can remove one of the physical volumes, say <filename>md3</filename>, from <filename>vg_raid</filename> and either assign it to <filename>vg_bulk</filename> directly (if the expected duration of the operation is short enough that we can live with the temporary drop in performance), or undo the RAID setup on <filename>md3</filename> and integrate its components <filename>sda5</filename> and <filename>sdc5</filename> into the bulk VG (which grows by 600 GB instead of 300 GB); the <filename>lv_rushes</filename> logical volume can then be grown according to requirements.", "old": "The rationale for the second split (<filename>md1</filename> vs. <filename>md2</filename>) is less clear-cut, and more related to acknowledging that the future is uncertain. When the workstation is first assembled, the exact storage requirements are not necessarily known with perfect precision; they can also evolve over time. In our case, we can't know in advance the actual storage space requirements for video rushes and complete video clips. If one particular clip needs a very large amount of rushes, and the VG dedicated to redundant data is less than halfway full, we can re-use some of its unneeded space. We can remove one of the physical volumes, say <filename>md2</filename>, from <filename>vg_raid</filename> and either assign it to <filename>vg_bulk</filename> directly (if the expected duration of the operation is short enough that we can live with the temporary drop in performance), or undo the RAID setup on <filename>md2</filename> and integrate its components <filename>sda6</filename> and <filename>sdc6</filename> into the bulk VG (which grows by 200 GB instead of 100 GB); the <filename>lv_rushes</filename> logical volume can then be grown according to requirements.", "details": {}, "id": 34030496, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030496/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698175/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357823+02:00", "action": 59, "target": "Die übrigen Partitionen, <filename>sda7</filename> und <filename>sdc7</filename> werden direkt als physische Datenträger benutzt und einer weiteren VG namens <filename>vg_bulk</filename> zugewiesen, die daher auch etwa 200 GB Speicherplatz bekommt.", "old": "", "details": { "state": 10, "source": "The remaining partitions, <filename>sda6</filename> and <filename>sdc6</filename>, are directly used as physical volumes, and assigned to another VG called <filename>vg_bulk</filename>, which therefore ends up with roughly 460 GB of space.", "old_state": -1 }, "id": 34030495, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030495/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698175/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357791+02:00", "action": 30, "target": "The remaining partitions, <filename>sda6</filename> and <filename>sdc6</filename>, are directly used as physical volumes, and assigned to another VG called <filename>vg_bulk</filename>, which therefore ends up with roughly 460 GB of space.", "old": "The remaining partitions, <filename>sda7</filename> and <filename>sdc7</filename>, are directly used as physical volumes, and assigned to another VG called <filename>vg_bulk</filename>, which therefore ends up with roughly 200 GB of space.", "details": {}, "id": 34030494, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030494/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698174/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357756+02:00", "action": 59, "target": "Die Partitionen <filename>sda5</filename> und <filename>sdc5</filename> wie auch <filename>sda6</filename> und <filename>sdc6</filename> werden zu zwei neuen RAID-1-Datenträgern namens <filename>md1</filename> und <filename>md2</filename> mit einer Größe von je 100 GB zusammengefasst. Diese beiden Spiegel werden als physische Datenträger für LVM initialisiert und der Volumengruppe <filename>vg_raid</filename> zugewiesen. Diese VG umfasst somit etwa 200 GB an sicherem Speicherplatz.", "old": "", "details": { "state": 10, "source": "The <filename>sda4</filename> and <filename>sdc4</filename> partitions, as well as <filename>sda5</filename> and <filename>sdc5</filename>, are assembled into two new RAID-1 volumes of about 300 GB each, <filename>md2</filename> and <filename>md3</filename>. Both these mirrors are initialized as physical volumes for LVM, and assigned to the <filename>vg_raid</filename> volume group. This VG thus contains about 600 GB of safe space.", "old_state": -1 }, "id": 34030493, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030493/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698174/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357725+02:00", "action": 30, "target": "The <filename>sda4</filename> and <filename>sdc4</filename> partitions, as well as <filename>sda5</filename> and <filename>sdc5</filename>, are assembled into two new RAID-1 volumes of about 300 GB each, <filename>md2</filename> and <filename>md3</filename>. Both these mirrors are initialized as physical volumes for LVM, and assigned to the <filename>vg_raid</filename> volume group. This VG thus contains about 600 GB of safe space.", "old": "The <filename>sda5</filename> and <filename>sdc5</filename> partitions, as well as <filename>sda6</filename> and <filename>sdc6</filename>, are assembled into two new RAID-1 volumes of about 100 GB each, <filename>md1</filename> and <filename>md2</filename>. Both these mirrors are initialized as physical volumes for LVM, and assigned to the <filename>vg_raid</filename> volume group. This VG thus contains about 200 GB of safe space.", "details": {}, "id": 34030492, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030492/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698173/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357689+02:00", "action": 59, "target": "Die Partitionen <filename>sda2</filename> und <filename>sdc2</filename> werden als Auslagerungspartitionen verwendet und stellen insgesamt 2 GB an Auslagerungsspeicher bereit. Zusammen mit 1 GB RAM hat der Arbeitsplatzrechner somit einen reichlichen Umfang an verfügbarem Speicher.", "old": "", "details": { "state": 10, "source": "The <filename>sda3</filename> and <filename>sdc3</filename> partitions are assembled into a RAID-0 volume, <filename>md1</filename>, and used as swap partition, providing a total 32 GB of swap space. Modern systems can provide plenty of RAM and our system won't need hibernation. So with this amount added, our system will unlikely run out of memory.", "old_state": -1 }, "id": 34030491, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030491/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698173/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357657+02:00", "action": 30, "target": "The <filename>sda3</filename> and <filename>sdc3</filename> partitions are assembled into a RAID-0 volume, <filename>md1</filename>, and used as swap partition, providing a total 32 GB of swap space. Modern systems can provide plenty of RAM and our system won't need hibernation. So with this amount added, our system will unlikely run out of memory.", "old": "The <filename>sda2</filename> and <filename>sdc2</filename> partitions are used as swap partitions, providing a total 2 GB of swap space. With 1 GB of RAM, the workstation has a comfortable amount of available memory.", "details": {}, "id": 34030490, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030490/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698172/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357622+02:00", "action": 59, "target": "Die ersten Partitionen beider Platten (etwa 1 GB) werden zu einem RAID-1-Datenträger namens <filename>md0</filename> zusammengefasst. Dieser Spiegel wird direkt dazu benutzt, das Wurzeldateisystem aufzunehmen.", "old": "", "details": { "state": 10, "source": "The next two partitions <filename>sda2</filename> and <filename>sdc2</filename> (about 48 GB) are assembled into a RAID-1 volume, <filename>md0</filename>. This mirror is directly used to store the root filesystem.", "old_state": -1 }, "id": 34030489, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030489/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698172/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357590+02:00", "action": 30, "target": "The next two partitions <filename>sda2</filename> and <filename>sdc2</filename> (about 48 GB) are assembled into a RAID-1 volume, <filename>md0</filename>. This mirror is directly used to store the root filesystem.", "old": "The first partitions of both disks (about 1 GB) are assembled into a RAID-1 volume, <filename>md0</filename>. This mirror is directly used to store the root filesystem.", "details": {}, "id": 34030488, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030488/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698171/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357556+02:00", "action": 59, "target": "", "old": "", "details": { "state": 0, "source": "The first partitions of both disks are BIOS boot partitions.", "old_state": -1 }, "id": 34030487, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030487/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698170/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357518+02:00", "action": 59, "target": "<computeroutput># </computeroutput><userinput>fdisk -l /dev/sda</userinput>\n<computeroutput>\nDisk /dev/sda: 300 GB, 300090728448 bytes, 586114704 sectors\nUnits: sectors of 1 * 512 = 512 bytes\nSector size (logical/physical): 512 bytes / 512 bytes\nI/O size (minimum/optimal): 512 bytes / 512 bytes\nDisklabel type: dos\nDisk identifier: 0x00039a9f\n\nDevice Boot Start End Sectors Size Id Type\n/dev/sda1 * 2048 1992060 1990012 1.0G fd Linux raid autodetect\n/dev/sda2 1992061 3984120 1992059 1.0G 82 Linux swap / Solaris\n/dev/sda3 4000185 586099395 582099210 298G 5 Extended\n/dev/sda5 4000185 203977305 199977120 102G fd Linux raid autodetect\n/dev/sda6 203977306 403970490 199993184 102G fd Linux raid autodetect\n/dev/sda7 403970491 586099395 182128904 93G 8e Linux LVM</computeroutput>", "old": "", "details": { "state": 10, "source": "<computeroutput># </computeroutput><userinput>sfdisk -l /dev/sda\n</userinput><computeroutput>Disk /dev/sda: 894.25 GiB, 960197124096 bytes, 1875385008 sectors\nDisk model: SAMSUNG MZ7LM960\nUnits: sectors of 1 * 512 = 512 bytes\nSector size (logical/physical): 512 bytes / 512 bytes\nI/O size (minimum/optimal): 512 bytes / 512 bytes\nDisklabel type: gpt\nDisk identifier: BB14C130-9E9A-9A44-9462-6226349CA012\n\nDevice Start End Sectors Size Type\n/dev/sda1 2048 4095 2048 1M BIOS boot\n/dev/sda2 4096 100667391 100663296 48G Linux RAID\n/dev/sda3 100667392 134221823 33554432 16G Linux RAID\n/dev/sda4 134221824 763367423 629145600 300G Linux RAID\n/dev/sda5 763367424 1392513023 629145600 300G Linux RAID\n/dev/sda6 1392513024 1875384974 482871951 230.3G Linux LVM\n</computeroutput>", "old_state": -1 }, "id": 34030486, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030486/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698170/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357486+02:00", "action": 30, "target": "<computeroutput># </computeroutput><userinput>sfdisk -l /dev/sda\n</userinput><computeroutput>Disk /dev/sda: 894.25 GiB, 960197124096 bytes, 1875385008 sectors\nDisk model: SAMSUNG MZ7LM960\nUnits: sectors of 1 * 512 = 512 bytes\nSector size (logical/physical): 512 bytes / 512 bytes\nI/O size (minimum/optimal): 512 bytes / 512 bytes\nDisklabel type: gpt\nDisk identifier: BB14C130-9E9A-9A44-9462-6226349CA012\n\nDevice Start End Sectors Size Type\n/dev/sda1 2048 4095 2048 1M BIOS boot\n/dev/sda2 4096 100667391 100663296 48G Linux RAID\n/dev/sda3 100667392 134221823 33554432 16G Linux RAID\n/dev/sda4 134221824 763367423 629145600 300G Linux RAID\n/dev/sda5 763367424 1392513023 629145600 300G Linux RAID\n/dev/sda6 1392513024 1875384974 482871951 230.3G Linux LVM\n</computeroutput>", "old": "<computeroutput># </computeroutput><userinput>fdisk -l /dev/sda</userinput>\n<computeroutput>\nDisk /dev/sda: 300 GB, 300090728448 bytes, 586114704 sectors\nUnits: sectors of 1 * 512 = 512 bytes\nSector size (logical/physical): 512 bytes / 512 bytes\nI/O size (minimum/optimal): 512 bytes / 512 bytes\nDisklabel type: dos\nDisk identifier: 0x00039a9f\n\nDevice Boot Start End Sectors Size Id Type\n/dev/sda1 * 2048 1992060 1990012 1.0G fd Linux raid autodetect\n/dev/sda2 1992061 3984120 1992059 1.0G 82 Linux swap / Solaris\n/dev/sda3 4000185 586099395 582099210 298G 5 Extended\n/dev/sda5 4000185 203977305 199977120 102G fd Linux raid autodetect\n/dev/sda6 203977306 403970490 199993184 102G fd Linux raid autodetect\n/dev/sda7 403970491 586099395 182128904 93G 8e Linux LVM</computeroutput>", "details": {}, "id": 34030485, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030485/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698169/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357449+02:00", "action": 59, "target": "Nehmen wir ein konkretes Beispiel: die Werbeabteilung bei Falcot Corp. benötigt einen Arbeitsplatzrechner für die Videobearbeitung, das Budget der Abteilung reicht aber nicht aus, um von Grund auf in Hochleistungsgeräte zu investieren. Es wird daher beschlossen, sich hierbei auf die Geräte zu beschränken, die für die grafische Art der Arbeit spezifisch sind (Bildschirm und Grafikkarte), und für die Speicherung bei normaler Hardware zu bleiben. Es ist jedoch allgemein bekannt, dass digitales Video einige besondere Ansprüche an die Speicherung stellt: der Umfang der zu speichernden Daten ist hoch, und die Durchsatzgeschwindigkeit für das Lesen und Schreiben dieser Daten ist für die Gesamtleistung des Systems wichtig (wichtiger als zum Beispiel die typische Zugriffszeit). Diese Anforderungen müssen mit der normalen Hardware erfüllt werden, in diesem Fall mit zwei 300 GB SATA-Festplatten. Die Systemdaten und einige Anwenderdaten müssen außerdem gegen Hardwareausfall beständig gemacht werden. Bearbeitete Videoclips müssen wirklich sicher sein, während dies bei Videoabschnitten, die noch nicht editiert wurden, weniger kritisch ist, da es sie noch auf den Videobändern gibt.", "old": "", "details": { "state": 10, "source": "Let's take a concrete example: the public relations department at Falcot Corp needs a workstation for video editing, but the department's budget doesn't allow investing in high-end hardware from the bottom up. A decision is made to favor the hardware that is specific to the graphic nature of the work (monitor and video card), and to stay with generic hardware for storage. However, as is widely known, digital video does have some particular requirements for its storage: the amount of data to store is large, and the throughput rate for reading and writing this data is important for the overall system performance (more than typical access time, for instance). These constraints need to be fulfilled with generic hardware, in this case two 300 GB SATA hard disk drives; the system data must also be made resistant to hardware failure, as well as some of the user data. Edited video clips must indeed be safe, but video rushes pending editing are less critical, since they're still on the videotapes.", "old_state": -1 }, "id": 34030484, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030484/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698169/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357417+02:00", "action": 30, "target": "Let's take a concrete example: the public relations department at Falcot Corp needs a workstation for video editing, but the department's budget doesn't allow investing in high-end hardware from the bottom up. A decision is made to favor the hardware that is specific to the graphic nature of the work (monitor and video card), and to stay with generic hardware for storage. However, as is widely known, digital video does have some particular requirements for its storage: the amount of data to store is large, and the throughput rate for reading and writing this data is important for the overall system performance (more than typical access time, for instance). These constraints need to be fulfilled with generic hardware, in this case two 300 GB SATA hard disk drives; the system data must also be made resistant to hardware failure, as well as some of the user data. Edited video clips must indeed be safe, but video rushes pending editing are less critical, since they're still on the videotapes.", "old": "Let's take a concrete example: the public relations department at Falcot Corp needs a workstation for video editing, but the department's budget doesn't allow investing in high-end hardware from the bottom up. A decision is made to favor the hardware that is specific to the graphic nature of the work (monitor and video card), and to stay with generic hardware for storage. However, as is widely known, digital video does have some particular requirements for its storage: the amount of data to store is large, and the throughput rate for reading and writing this data is important for the overall system performance (more than typical access time, for instance). These constraints need to be fulfilled with generic hardware, in this case two 300 GB SATA hard disk drives; the system data must also be made resistant to hardware failure, as well as some of the user data. Edited videoclips must indeed be safe, but video rushes pending editing are less critical, since they're still on the videotapes.", "details": {}, "id": 34030483, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030483/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698168/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357380+02:00", "action": 59, "target": "Wenn es auf die Schreib-/Lese-Geschwindigkeit ankommt, vor allem auf die Zugriffszeit, dann hat die Verwendung von LVM und/oder RAID in einer seiner vielen Ausprägungen möglicherweise Einfluss auf die Performance. Das kann die Entscheidung, welche Lösung gewählt werden soll, beeinflussen. Jedoch sind diese Unterschiede in der Perormance gering und nur in wenigen Fällen messbar. Wenn es auf Performance ankommt, kann man mit nicht drehenden Speichermedien die besten Resultate erzielen (<indexterm><primary>SSD</primary></indexterm><emphasis>solid-state drives</emphasis> or SSDs); Dabei sind die Kosten pro Megabyte höher als bei Standardplatten und ihre Kapazität ist üblicherweise geringer, aber sie bieten ausgezeichnete Performance bei zufällig verteilten Zugriffen. Wenn das Nutzungsprofil viele Lese-/Schreibzugriffe über das ganze Dateisystem verteilt beinhaltet, dann ist der Vorteil, wenn sie auf SSD ausgeführt werden, weit größer, als das, was Sie gewinnen können, wenn Sie LVM einem RAID vorziehen oder umgekehrt. In diesen Fällen, sollte die Entscheidung nach anderen Kriterien als der reinen Zugriffsgeschwindigkeit erfolgen, denn Geschwindigkeitsanforderungen werden am besten bei Verwendung von SSDs erfüllt.", "old": "", "details": { "state": 10, "source": "If input/output speed is of the essence, especially in terms of access times, using LVM and/or RAID in one of the many combinations may have some impact on performances, and this may influence decisions as to which to pick. However, these differences in performance are really minor, and will only be measurable in a few use cases. If performance matters, the best gain to be obtained would be to use non-rotating storage media (<emphasis>solid-state drives</emphasis> or SSDs); their cost per megabyte is higher than that of standard hard disk drives, and their capacity is usually smaller, but they provide excellent performance for random accesses. If the usage pattern includes many input/output operations scattered all around the filesystem, for instance for databases where complex queries are routinely being run, then the advantage of running them on an SSD far outweigh whatever could be gained by picking LVM over RAID or the reverse. In these situations, the choice should be determined by other considerations than pure speed, since the performance aspect is most easily handled by using SSDs.", "old_state": -1 }, "id": 34030482, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34030482/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82698168/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:35.357348+02:00", "action": 30, "target": "If input/output speed is of the essence, especially in terms of access times, using LVM and/or RAID in one of the many combinations may have some impact on performances, and this may influence decisions as to which to pick. However, these differences in performance are really minor, and will only be measurable in a few use cases. If performance matters, the best gain to be obtained would be to use non-rotating storage media (<emphasis>solid-state drives</emphasis> or SSDs); their cost per megabyte is higher than that of standard hard disk drives, and their capacity is usually smaller, but they provide excellent performance for random accesses. If the usage pattern includes many input/output operations scattered all around the filesystem, for instance for databases where complex queries are routinely being run, then the advantage of running them on an SSD far outweigh whatever could be gained by picking LVM over RAID or the reverse. In these situations, the choice should be determined by other considerations than pure speed, since the performance aspect is most easily handled by using SSDs.", "old": "If input/output speed is of the essence, especially in terms of access times, using LVM and/or RAID in one of the many combinations may have some impact on performances, and this may influence decisions as to which to pick. However, these differences in performance are really minor, and will only be measurable in a few use cases. If performance matters, the best gain to be obtained would be to use non-rotating storage media (<indexterm><primary>SSD</primary></indexterm><emphasis>solid-state drives</emphasis> or SSDs); their cost per megabyte is higher than that of standard hard disk drives, and their capacity is usually smaller, but they provide excellent performance for random accesses. If the usage pattern includes many input/output operations scattered all around the filesystem, for instance for databases where complex queries are routinely being run, then the advantage of running them on an SSD far outweigh whatever could be gained by picking LVM over RAID or the reverse. In these situations, the choice should be determined by other considerations than pure speed, since the performance aspect is most easily handled by using SSDs.", "details": {}, "id": 34030481, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34030481/?format=api" } ] }