| 1 |
# |
| 2 |
# AUTHOR <EMAIL@ADDRESS>, YEAR. |
| 3 |
# Ryuunosuke Ayanokouzi <[email protected]>, 2015-2019. |
| 4 |
# Kenshi Muto <[email protected]>, 2015. |
| 5 |
# Yoichi Chonan <[email protected]>, 2015. |
| 6 |
# YABUKI Youichi <[email protected]>, 2015. |
| 7 |
# Osamu Aoki <[email protected]>, 2016. |
| 8 |
# |
| 9 |
msgid "" |
| 10 |
msgstr "" |
| 11 |
"Project-Id-Version: 0\n" |
| 12 |
"POT-Creation-Date: 2022-07-30 18:23+0200\n" |
| 13 |
"PO-Revision-Date: 2019-02-03 09:00+0900\n" |
| 14 |
"Last-Translator: AYANOKOUZI, Ryuunosuke <[email protected]>\n" |
| 15 |
"Language-Team: Japanese <https://github.com/l/debian-handbook/tree/master/translation/ja_JP/push>\n" |
| 16 |
"Language: ja\n" |
| 17 |
"MIME-Version: 1.0\n" |
| 18 |
"Content-Type: application/x-publican; charset=UTF-8\n" |
| 19 |
"Content-Transfer-Encoding: 8bit\n" |
| 20 |
|
| 21 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 22 |
msgid "RAID" |
| 23 |
msgstr "RAID" |
| 24 |
|
| 25 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 26 |
msgid "LVM" |
| 27 |
msgstr "LVM" |
| 28 |
|
| 29 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 30 |
msgid "FAI" |
| 31 |
msgstr "FAI" |
| 32 |
|
| 33 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 34 |
msgid "Preseeding" |
| 35 |
msgstr "Preseed" |
| 36 |
|
| 37 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 38 |
msgid "Monitoring" |
| 39 |
msgstr "監視" |
| 40 |
|
| 41 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 42 |
msgid "Virtualization" |
| 43 |
msgstr "仮想化" |
| 44 |
|
| 45 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 46 |
msgid "Xen" |
| 47 |
msgstr "Xen" |
| 48 |
|
| 49 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 50 |
msgid "LXC" |
| 51 |
msgstr "LXC" |
| 52 |
|
| 53 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 54 |
msgid "Advanced Administration" |
| 55 |
msgstr "高度な管理" |
| 56 |
|
| 57 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 58 |
msgid "This chapter revisits some aspects we already described, with a different perspective: instead of installing one single computer, we will study mass-deployment systems; instead of creating RAID or LVM volumes at install time, we'll learn to do it by hand so we can later revise our initial choices. Finally, we will discuss monitoring tools and virtualization techniques. As a consequence, this chapter is more particularly targeting professional administrators, and focuses somewhat less on individuals responsible for their home network." |
| 59 |
msgstr "この章では、前章までに説明した一部の側面を異なる視点からもう一度取り上げます。すなわち、1 台のコンピュータにインストールするのではなく、大規模な配備システムについて学びます。さらに、初回インストール時に RAID や LVM ボリュームを作成するのではなく、手作業でこれを行う方法について学びます。こうすることで初回インストール時の選択を訂正することが可能です。最後に、監視ツールと仮想化技術について議論します。その結果として、この章はより熟練した管理者を対象にしており、ホームネットワークに責任を負う個人を対象にしていません。" |
| 60 |
|
| 61 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 62 |
msgid "RAID and LVM" |
| 63 |
msgstr "RAID と LVM" |
| 64 |
|
| 65 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 66 |
msgid "<primary>RAID</primary>" |
| 67 |
msgstr "<primary>RAID</primary>" |
| 68 |
|
| 69 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 70 |
msgid "<primary>LVM</primary>" |
| 71 |
msgstr "<primary>LVM</primary>" |
| 72 |
|
| 73 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 74 |
#, fuzzy |
| 75 |
#| msgid "<primary>Logical Volume Manager</primary>" |
| 76 |
msgid "<primary>Logical Volume Manager</primary><see>LVM</see>" |
| 77 |
msgstr "<primary sortas=\"ロンリボリュームマネージャ\">論理ボリュームマネージャ</primary>" |
| 78 |
|
| 79 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 80 |
#, fuzzy |
| 81 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 82 |
msgid "<primary>volume</primary><secondary>logical volume</secondary>" |
| 83 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 84 |
|
| 85 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 86 |
#, fuzzy |
| 87 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 88 |
msgid "<primary>volume</primary><secondary>raid volume</secondary>" |
| 89 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 90 |
|
| 91 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 92 |
#, fuzzy |
| 93 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 94 |
msgid "<primary>filesystem</primary><secondary>redundancy</secondary>" |
| 95 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 96 |
|
| 97 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 98 |
#, fuzzy |
| 99 |
#| msgid "<xref linkend=\"installation\" /> presented these technologies from the point of view of the installer, and how it integrated them to make their deployment easy from the start. After the initial installation, an administrator must be able to handle evolving storage space needs without having to resort to an expensive reinstallation. They must therefore understand the required tools for manipulating RAID and LVM volumes." |
| 100 |
msgid "<xref linkend=\"installation\" /> presented these technologies from the point of view of the installer, and how it integrated them to make their deployment easy from the start. After the initial installation, an administrator must be able to handle evolving storage space needs without having to resort to an expensive re-installation. They must therefore understand the required tools for manipulating RAID and LVM volumes." |
| 101 |
msgstr "<xref linkend=\"installation\" />ではインストーラの視点から RAID と LVM の技術を説明し、インストーラを使って初回インストール時に RAID や LVM を簡単に配備する方法について説明しました。初回インストールが終わったら、管理者は再インストールという手間のかかる最終手段を行使することなく、より大きなストレージ領域の要求に対処しなければいけません。すなわち、管理者は RAID と LVM ボリュームを操作するために必要なツールを理解しなければいけません。" |
| 102 |
|
| 103 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 104 |
#, fuzzy |
| 105 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 106 |
msgid "<primary>volume</primary><secondary>management</secondary>" |
| 107 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 108 |
|
| 109 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 110 |
#, fuzzy |
| 111 |
#| msgid "RAID and LVM are both techniques to abstract the mounted volumes from their physical counterparts (actual hard-disk drives or partitions thereof); the former secures the data against hardware failure by introducing redundancy, the latter makes volume management more flexible and independent of the actual size of the underlying disks. In both cases, the system ends up with new block devices, which can be used to create filesystems or swap space, without necessarily having them mapped to one physical disk. RAID and LVM come from quite different backgrounds, but their functionality can overlap somewhat, which is why they are often mentioned together." |
| 112 |
msgid "RAID and LVM are both techniques to abstract the mounted volumes from their physical counterparts (actual hard-disk drives or partitions thereof); the former ensures the security and availability of the data in case of hardware failure by introducing redundancy, the latter makes volume management more flexible and independent of the actual size of the underlying disks. In both cases, the system ends up with new block devices, which can be used to create filesystems or swap space, without necessarily having them mapped to one physical disk. RAID and LVM come from quite different backgrounds, but their functionality can overlap somewhat, which is why they are often mentioned together." |
| 113 |
msgstr "RAID と LVM は両方ともマウントされたボリュームを物理的に対応する物 (実際のハードディスクドライブまたはそのパーティション) から抽象化する技術です。さらに、RAID は冗長性を導入することでデータをハードディスク障害から守り、LVM はボリューム管理をより柔軟にしてディスクの実サイズに依存しないようにします。どちらの場合であっても、最終的にシステムには新しいブロックデバイスが追加されます。追加されたブロックデバイスはファイルシステムやスワップ領域を作成するために使われますが、必ずしも単独の物理ディスクに対応付けられるものではありません。RAID と LVM は全く異なる生い立ちを持っていますが、両者の機能は多少重複しています。このため、両者は一緒に言及されることが多いです。" |
| 114 |
|
| 115 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 116 |
msgid "<emphasis>PERSPECTIVE</emphasis> Btrfs combines LVM and RAID" |
| 117 |
msgstr "<emphasis>PERSPECTIVE</emphasis> Btrfs が LVM と RAID を結び付ける" |
| 118 |
|
| 119 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 120 |
#, fuzzy |
| 121 |
#| msgid "<primary><command>xm</command></primary>" |
| 122 |
msgid "<primary><command>mount</command></primary><secondary>Btrfs</secondary>" |
| 123 |
msgstr "<primary><command>xm</command></primary>" |
| 124 |
|
| 125 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 126 |
# Tag: L-CFMD; |
| 127 |
#, fuzzy |
| 128 |
#| msgid "<primary>preseed</primary>" |
| 129 |
msgid "<primary>Btrfs</primary>" |
| 130 |
msgstr "<primary>preseed</primary>" |
| 131 |
|
| 132 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 133 |
#, fuzzy |
| 134 |
#| msgid "While LVM and RAID are two distinct kernel subsystems that come between the disk block devices and their filesystems, <emphasis>btrfs</emphasis> is a new filesystem, initially developed at Oracle, that purports to combine the featuresets of LVM and RAID and much more. It is mostly functional, and although it is still tagged “experimental” because its development is incomplete (some features aren't implemented yet), it has already seen some use in production environments. <ulink type=\"block\" url=\"http://btrfs.wiki.kernel.org/\" />" |
| 135 |
msgid "While LVM and RAID are two distinct kernel subsystems that come between the disk block devices and their filesystems, <emphasis>btrfs</emphasis> is a filesystem, initially developed at Oracle, that purports to combine the feature sets of LVM and RAID and much more. <ulink type=\"block\" url=\"https://btrfs.wiki.kernel.org/\" />" |
| 136 |
msgstr "LVM と RAID は 2 種類の全く別のカーネルサブシステムで、どちらもディスクブロックデバイスとそのファイルシステムの間のやり取りを担当します。<emphasis>btrfs</emphasis> は最初 Oracle で開発された新しいファイルシステムで、LVM と RAID の機能を結び付けると主張しています。<emphasis>btrfs</emphasis> は開発がまだ完了していない (一部の機能がまだ実装されていない) ため「実験中」とタグ付けされていますが、ほとんどうまく機能し、既に本番環境で使われています。<ulink type=\"block\" url=\"http://btrfs.wiki.kernel.org/\" />" |
| 137 |
|
| 138 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 139 |
msgid "Among the noteworthy features are the ability to take a snapshot of a filesystem tree at any point in time. This snapshot copy doesn't initially use any disk space, the data only being duplicated when one of the copies is modified. The filesystem also handles transparent compression of files, and checksums ensure the integrity of all stored data." |
| 140 |
msgstr "<emphasis>btrfs</emphasis> の特筆すべき機能に、任意の時点におけるファイルシステムツリーのスナップショットを取る機能があります。このスナップショットコピーは初期状態ではいかなるディスク領域も使いません、コピー内容の 1 つが修正された際にデータが複製されます。また、このファイルシステムはファイルを透過的に圧縮することが可能で、さらにチェックサムを用いて保存されているデータの完全性を保証します。" |
| 141 |
|
| 142 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 143 |
#, fuzzy |
| 144 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 145 |
msgid "<primary>filesystem</primary><secondary>snapshot</secondary>" |
| 146 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 147 |
|
| 148 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 149 |
# Tag: PTAL; |
| 150 |
msgid "In both the RAID and LVM cases, the kernel provides a block device file, similar to the ones corresponding to a hard disk drive or a partition. When an application, or another part of the kernel, requires access to a block of such a device, the appropriate subsystem routes the block to the relevant physical layer. Depending on the configuration, this block can be stored on one or several physical disks, and its physical location may not be directly correlated to the location of the block in the logical device." |
| 151 |
msgstr "RAID と LVM のどちらの場合も、カーネルはハードディスクドライブやパーティションに対応するブロックデバイスファイルとよく似たブロックデバイスファイルを提供します。アプリケーションやカーネルの別の部分がそのようなデバイスのあるブロックにアクセスを要求する場合、適切なサブシステムが要求されたブロックを物理層のブロックに対応付けます。設定に依存して、アプリケーション側から見たブロックは単独か複数の物理ディスクに保存されます。このブロックの物理的場所は論理デバイス内のブロックの位置と直接的に対応するものではないかもしれません。" |
| 152 |
|
| 153 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 154 |
msgid "Software RAID" |
| 155 |
msgstr "ソフトウェア RAID" |
| 156 |
|
| 157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 158 |
#, fuzzy |
| 159 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 160 |
msgid "<primary>RAID</primary><secondary>Software RAID</secondary>" |
| 161 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 162 |
|
| 163 |
msgid "<primary>Redundant Array of Independent Disks</primary><see>RAID</see>" |
| 164 |
msgstr "" |
| 165 |
|
| 166 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 167 |
#, fuzzy |
| 168 |
#| msgid "RAID means <emphasis>Redundant Array of Independent Disks</emphasis>. The goal of this system is to prevent data loss in case of hard disk failure. The general principle is quite simple: data are stored on several physical disks instead of only one, with a configurable level of redundancy. Depending on this amount of redundancy, and even in the event of an unexpected disk failure, data can be losslessly reconstructed from the remaining disks." |
| 169 |
msgid "RAID means <emphasis>Redundant Array of Independent Disks</emphasis>. The goal of this system is to prevent data loss and ensure availability in case of hard disk failure. The general principle is quite simple: data are stored on several physical disks instead of only one, with a configurable level of redundancy. Depending on this amount of redundancy, and even in the event of an unexpected disk failure, data can be losslessly reconstructed from the remaining disks." |
| 170 |
msgstr "RAID は <emphasis>Redundant Array of Independent Disks</emphasis> を意味します。RAID システムの目標はハードディスク障害の際にデータ損失を防ぐことです。一般原則は極めて単純です。すなわち、データは設定できる冗長性のレベルに基づいて単独ではなく複数のディスクに保存されます。冗長性の度合いに依存して、たとえ予想外のディスク障害が起きた場合でも、データを残りのディスクから損失なく再構成することが可能です。" |
| 171 |
|
| 172 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 173 |
msgid "<emphasis>CULTURE</emphasis> <foreignphrase>Independent</foreignphrase> or <foreignphrase>inexpensive</foreignphrase>?" |
| 174 |
msgstr "<emphasis>CULTURE</emphasis> <foreignphrase>independent</foreignphrase> それとも <foreignphrase>inexpensive</foreignphrase>?" |
| 175 |
|
| 176 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 177 |
#, fuzzy |
| 178 |
#| msgid "The I in RAID initially stood for <emphasis>inexpensive</emphasis>, because RAID allowed a drastic increase in data safety without requiring investing in expensive high-end disks. Probably due to image concerns, however, it is now more customarily considered to stand for <emphasis>independent</emphasis>, which doesn't have the unsavory flavour of cheapness." |
| 179 |
msgid "The I in RAID initially stood for <emphasis>inexpensive</emphasis>, because RAID allowed a drastic increase in data safety without requiring investing in expensive high-end disks. Probably due to image concerns, however, it is now more customarily considered to stand for <emphasis>independent</emphasis>, which doesn't have the unsavory flavor of cheapness." |
| 180 |
msgstr "当初、RAID の I は <emphasis>inexpensive</emphasis> を意味していました。なぜなら、RAID は高価な高性能ディスクへ投資することなくデータの安全性を劇的に高めることが可能だったからです。しかしながらおそらく心証的な懸念から、現在 RAID の I は通例 <emphasis>independent</emphasis> を意味するものとされます。<emphasis>independent</emphasis> には安価であることに対する悪い印象がないからです。" |
| 181 |
|
| 182 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 183 |
#, fuzzy |
| 184 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 185 |
msgid "<primary>RAID</primary><secondary>Hardware RAID</secondary>" |
| 186 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 187 |
|
| 188 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 189 |
#, fuzzy |
| 190 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 191 |
msgid "<primary>RAID</primary><secondary>degraded</secondary>" |
| 192 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 193 |
|
| 194 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 195 |
#, fuzzy |
| 196 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 197 |
msgid "<primary>RAID</primary><secondary>reconstruction</secondary>" |
| 198 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 199 |
|
| 200 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 201 |
msgid "RAID can be implemented either by dedicated hardware (RAID modules integrated into SCSI or SATA controller cards) or by software abstraction (the kernel). Whether hardware or software, a RAID system with enough redundancy can transparently stay operational when a disk fails; the upper layers of the stack (applications) can even keep accessing the data in spite of the failure. Of course, this “degraded mode” can have an impact on performance, and redundancy is reduced, so a further disk failure can lead to data loss. In practice, therefore, one will strive to only stay in this degraded mode for as long as it takes to replace the failed disk. Once the new disk is in place, the RAID system can reconstruct the required data so as to return to a safe mode. The applications won't notice anything, apart from potentially reduced access speed, while the array is in degraded mode or during the reconstruction phase." |
| 202 |
msgstr "RAID は専用ハードウェア (SCSI や SATA コントローラカードに統合された RAID モジュール) またはソフトウェア抽象化 (カーネル) を使って実装することが可能です。ハードウェアかソフトウェアかに関わらず、十分な冗長性を備えた RAID システムはディスク障害があっても利用できる状態を透過的に継続することが可能です。従って、スタックの上層 (アプリケーション) はディスク障害にも関わらず、引き続きデータにアクセスできます。もちろん「信頼性低下状態」は性能に影響をおよぼし、冗長性を低下させます。このため、もう一つ別のディスク障害が起きるとデータを失うことになります。このため実践的には、管理者は信頼性低下状態を障害の起きたディスクが交換されるまでの間だけに留めるように努力します。新しいディスクが配備されると、RAID システムは要求されたデータを再構成することが可能です。こうすることで信頼性の高い状態に戻ります。信頼性低下状態か再構成状態にある RAID アレイのアクセス速度は低下する可能性がありますが、この点を除けばアプリケーションがディスク障害に気が付くことはないでしょう。" |
| 203 |
|
| 204 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 205 |
msgid "When RAID is implemented by hardware, its configuration generally happens within the BIOS setup tool, and the kernel will consider a RAID array as a single disk, which will work as a standard physical disk, although the device name may be different (depending on the driver)." |
| 206 |
msgstr "RAID がハードウェアで実装された場合、その設定は通常 BIOS セットアップツールによってなされます。カーネルは RAID アレイを標準的な物理ディスクとして機能する単一のディスクとみなします。RAID アレイのデバイス名は (ドライバに依存して) 違うかもしれません。" |
| 207 |
|
| 208 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 209 |
msgid "We only focus on software RAID in this book." |
| 210 |
msgstr "本書ではソフトウェア RAID だけに注目します。" |
| 211 |
|
| 212 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 213 |
msgid "Different RAID Levels" |
| 214 |
msgstr "さまざまな RAID レベル" |
| 215 |
|
| 216 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 217 |
#, fuzzy |
| 218 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 219 |
msgid "<primary>RAID</primary><secondary>level</secondary>" |
| 220 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 221 |
|
| 222 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 223 |
msgid "RAID is actually not a single system, but a range of systems identified by their levels; the levels differ by their layout and the amount of redundancy they provide. The more redundant, the more failure-proof, since the system will be able to keep working with more failed disks. The counterpart is that the usable space shrinks for a given set of disks; seen the other way, more disks will be needed to store a given amount of data." |
| 224 |
msgstr "実際のところ RAID の種類は 1 種類だけではなく、そのレベルによって識別される複数の種類があります。すなわち、設計と提供される冗長性の度合いが異なる複数の RAID レベルが存在します。より冗長性を高くすれば、より障害に強くなります。なぜなら、より多くのディスクで障害が起きても、システムを動かし続けることができるからです。これに応じて、与えられた一連のディスクに対して利用できる領域が小さくなります。すなわち、あるサイズのデータを保存するために必要なディスク領域のサイズが多くなります。" |
| 225 |
|
| 226 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 227 |
msgid "Linear RAID" |
| 228 |
msgstr "リニア RAID" |
| 229 |
|
| 230 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 231 |
#, fuzzy |
| 232 |
#| msgid "Even though the kernel's RAID subsystem allows creating “linear RAID”, this is not proper RAID, since this setup doesn't involve any redundancy. The kernel merely aggregates several disks end-to-end and provides the resulting aggregated volume as one virtual disk (one block device). That's about its only function. This setup is rarely used by itself (see later for the exceptions), especially since the lack of redundancy means that one disk failing makes the whole aggregate, and therefore all the data, unavailable." |
| 233 |
msgid "Even though the kernel's RAID subsystem allows creating “linear RAID”, this is not proper RAID, since this setup doesn't involve any redundancy. The kernel merely aggregates several disks end-to-end and provides the resulting aggregated volume as one virtual disk (one block device). That is about its only function. This setup is rarely used by itself (see later for the exceptions), especially since the lack of redundancy means that one disk failing makes the whole aggregate, and therefore all the data, unavailable." |
| 234 |
msgstr "カーネルの RAID サブシステムを使えば「リニア RAID」を作ることも可能ですが、「リニア RAID」は適切な RAID ではありません。なぜなら、「リニア RAID」には冗長性が一切ないからです。カーネルはただ単純に複数のディスク端同士を統合し、統合されたボリュームを 1 つの仮想ディスク (1 つのブロックデバイス) として提供するだけです。これが「リニア RAID」のすべてです。「リニア RAID」を使うのは極めてまれな場合に限られます (後から使用例を説明します)。なぜなら、冗長性がないということは 1 つのディスクの障害が統合されたボリューム全体を駄目にすること、ひいてはすべてのデータを駄目にすることを意味するからです。" |
| 235 |
|
| 236 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 237 |
#, fuzzy |
| 238 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 239 |
msgid "<primary>RAID</primary><secondary>linear</secondary>" |
| 240 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 241 |
|
| 242 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 243 |
msgid "RAID-0" |
| 244 |
msgstr "RAID-0" |
| 245 |
|
| 246 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 247 |
msgid "This level doesn't provide any redundancy either, but disks aren't simply stuck on end one after another: they are divided in <emphasis>stripes</emphasis>, and the blocks on the virtual device are stored on stripes on alternating physical disks. In a two-disk RAID-0 setup, for instance, even-numbered blocks of the virtual device will be stored on the first physical disk, while odd-numbered blocks will end up on the second physical disk." |
| 248 |
msgstr "同様に RAID-0 にも冗長性がありません。しかしながら、RAID-0 は順番通り単純に物理ディスクを連結する構成ではありません。すなわち、物理ディスクは<emphasis>ストライプ状</emphasis>に分割され、仮想デバイスのブロックは互い違いになった物理ディスクのストライプに保存されます。たとえば 2 台のディスクから構成されている RAID-0 セットアップでは、偶数を付番されたブロックは最初の物理ディスクに保存され、奇数を付番されたブロックは 2 番目の物理ディスクに保存されます。" |
| 249 |
|
| 250 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 251 |
#, fuzzy |
| 252 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 253 |
msgid "<primary>RAID</primary><secondary>stripes</secondary>" |
| 254 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 255 |
|
| 256 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 257 |
#, fuzzy |
| 258 |
#| msgid "This system doesn't aim at increasing reliability, since (as in the linear case) the availability of all the data is jeopardized as soon as one disk fails, but at increasing performance: during sequential access to large amounts of contiguous data, the kernel will be able to read from both disks (or write to them) in parallel, which increases the data transfer rate. However, RAID-0 use is shrinking, its niche being filled by LVM (see later)." |
| 259 |
msgid "This system doesn't aim at increasing reliability, since (as in the linear case) the availability of all the data is jeopardized as soon as one disk fails, but at increasing performance: during sequential access to large amounts of contiguous data, the kernel will be able to read from both disks (or write to them) in parallel, which increases the data transfer rate. The disks are utilized entirely by the RAID device, so they should have the same size not to lose performance." |
| 260 |
msgstr "RAID-0 システムを使っても信頼性は向上しません。なぜなら、システムの信頼性すなわちデータの可用性は (リニア RAID と同様に) ディスク障害があればすぐに脅かされるからです。しかしながら、RAID-0 システムを使うことで性能は向上します。すなわち隣接した巨大なデータにシーケンシャルアクセスする場合、カーネルは両方のディスクから並行して読み込む (書き込む) ことが可能です。これによりデータの転送率が増加します。とは言うものの、RAID-0 が使われる機会は減り、代わりに LVM (後から説明します) が使われるようになっています。" |
| 261 |
|
| 262 |
msgid "RAID-0 use is shrinking, its niche being filled by LVM (see later)." |
| 263 |
msgstr "" |
| 264 |
|
| 265 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 266 |
#, fuzzy |
| 267 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 268 |
msgid "<primary>RAID</primary><secondary>0</secondary>" |
| 269 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 270 |
|
| 271 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 272 |
msgid "RAID-1" |
| 273 |
msgstr "RAID-1" |
| 274 |
|
| 275 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 276 |
msgid "This level, also known as “RAID mirroring”, is both the simplest and the most widely used setup. In its standard form, it uses two physical disks of the same size, and provides a logical volume of the same size again. Data are stored identically on both disks, hence the “mirror” nickname. When one disk fails, the data is still available on the other. For really critical data, RAID-1 can of course be set up on more than two disks, with a direct impact on the ratio of hardware cost versus available payload space." |
| 277 |
msgstr "RAID-1 は「RAID ミラーリング」としても知られ、最も簡単で最も広く使われています。RAID-1 の標準的な構成では、同じサイズの 2 台の物理ディスクを使い、物理ディスクと同じサイズの論理ボリュームが利用できるようになります。データを両方のディスクに保存するため、「ミラー」と呼ばれています。一方のディスクに障害があっても、他方のディスクからデータを利用することが可能です。もちろん、非常に重要なデータ用に RAID-1 を 2 台以上の構成にすることも可能ですが、これはハードウェア費用と利用できる保存領域の比率に直接的な影響をおよぼします。" |
| 278 |
|
| 279 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 280 |
#, fuzzy |
| 281 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 282 |
msgid "<primary>RAID</primary><secondary>1</secondary>" |
| 283 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 284 |
|
| 285 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 286 |
#, fuzzy |
| 287 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 288 |
msgid "<primary>RAID</primary><secondary>mirror</secondary>" |
| 289 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 290 |
|
| 291 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 292 |
msgid "<emphasis>NOTE</emphasis> Disks and cluster sizes" |
| 293 |
msgstr "<emphasis>NOTE</emphasis> ディスクとクラスタサイズ" |
| 294 |
|
| 295 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 296 |
msgid "If two disks of different sizes are set up in a mirror, the bigger one will not be fully used, since it will contain the same data as the smallest one and nothing more. The useful available space provided by a RAID-1 volume therefore matches the size of the smallest disk in the array. This still holds for RAID volumes with a higher RAID level, even though redundancy is stored differently." |
| 297 |
msgstr "異なるサイズの 2 台のディスクをミラーでセットアップする場合、サイズの大きい側のディスクは完全に利用されません。なぜなら、大きい側のディスクに含まれるデータは最も小さいディスクに含まれるデータと同じデータだからです。このため RAID-1 ボリュームで提供される利用できる領域のサイズは RAID アレイの最も小さなディスクのサイズと同じになります。冗長性を異なる方法で確保しているより高い RAID レベルの RAID ボリュームに対しても同じことが言えます。" |
| 298 |
|
| 299 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 300 |
msgid "It is therefore important, when setting up RAID arrays (except for RAID-0 and “linear RAID”), to only assemble disks of identical, or very close, sizes, to avoid wasting resources." |
| 301 |
msgstr "それ故、(RAID-0 と「リニア RAID」以外の) RAID アレイをセットアップする場合、資源の無駄を防ぐためにアレイを構成するディスクはそのサイズが完全に同じか近いものを使うことが重要です。" |
| 302 |
|
| 303 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 304 |
msgid "<emphasis>NOTE</emphasis> Spare disks" |
| 305 |
msgstr "<emphasis>NOTE</emphasis> 予備ディスク" |
| 306 |
|
| 307 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 308 |
# Tag: L-CFMD; |
| 309 |
#, fuzzy |
| 310 |
#| msgid "<primary>preseed</primary>" |
| 311 |
msgid "<primary>spare disk</primary>" |
| 312 |
msgstr "<primary>preseed</primary>" |
| 313 |
|
| 314 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 315 |
msgid "RAID levels that include redundancy allow assigning more disks than required to an array. The extra disks are used as spares when one of the main disks fails. For instance, in a mirror of two disks plus one spare, if one of the first two disks fails, the kernel will automatically (and immediately) reconstruct the mirror using the spare disk, so that redundancy stays assured after the reconstruction time. This can be used as another kind of safeguard for critical data." |
| 316 |
msgstr "冗長性を持たせた RAID レベルでは、必要なディスク数よりも多くのディスクで RAID アレイを構成させることが可能です。追加的ディスクは主要ディスクに障害が起きた場合に予備として使われます。たとえば、2 台のディスクと 1 台の予備ディスクのミラー構成では、最初の 2 台のうちの 1 台に障害が起きた場合、カーネルは自動的に (そして素早く) 予備ディスクを使ってミラーを再構成し、再構成の完了後に冗長性が再確保されます。すなわち、重要なデータに対するもう一つの安全装置として予備ディスクを使うことが可能ということです。" |
| 317 |
|
| 318 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 319 |
msgid "One would be forgiven for wondering how this is better than simply mirroring on three disks to start with. The advantage of the “spare disk” configuration is that the spare disk can be shared across several RAID volumes. For instance, one can have three mirrored volumes, with redundancy assured even in the event of one disk failure, with only seven disks (three pairs, plus one shared spare), instead of the nine disks that would be required by three triplets." |
| 320 |
msgstr "この方式が単純に 3 台のディスクに対して最初からミラーリングを行うよりも優れているとされることに疑問を持つかもしれません。「予備ディスク」を設定する利点は複数の RAID ボリュームで予備ディスクを共有することが可能という点です。たとえば、1 台のディスク障害に対する冗長性を確保した 3 つのミラーされたボリュームを構成するには、ディスクを 7 台 (3 つのペアと 1 台の共有された予備) 用意するだけですみます。これに対して各ボリュームに 3 台のディスクを用意する場合には 9 台のディスクが必要です。" |
| 321 |
|
| 322 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 323 |
msgid "This RAID level, although expensive (since only half of the physical storage space, at best, is useful), is widely used in practice. It is simple to understand, and it allows very simple backups: since both disks have identical contents, one of them can be temporarily extracted with no impact on the working system. Read performance is often increased since the kernel can read half of the data on each disk in parallel, while write performance isn't too severely degraded. In case of a RAID-1 array of N disks, the data stays available even with N-1 disk failures." |
| 324 |
msgstr "RAID-1 は高価であるにも関わらず (良くても物理ストレージ領域のたった半分しか使えないにも関わらず)、広く実運用されています。RAID-1 は簡単に理解でき、簡単にバックアップできます。なぜなら両方のディスクが全く同じ内容を持っているため、片方を一時的に取り外しても運用システムに影響をおよぼさないからです。通常 RAID-1 を使うことで、読み込み性能は好転します。なぜなら、カーネルはデータの半分をそれぞれのディスクから並行して読むことができるからです。これに対して、書き込み性能はそれほど悪化しません。N 台のディスクからなる RAID-1 アレイの場合、データは N-1 台のディスク障害に対して保護されます。" |
| 325 |
|
| 326 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 327 |
#, fuzzy |
| 328 |
#| msgid "<emphasis>TIP</emphasis> RAID, disks and partitions" |
| 329 |
msgid "<emphasis>CAUTION</emphasis> RAID is not Backup" |
| 330 |
msgstr "<emphasis>TIP</emphasis> RAID、ディスク、パーティション" |
| 331 |
|
| 332 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 333 |
#, fuzzy |
| 334 |
#| msgid "<primary>debian-cd</primary>" |
| 335 |
msgid "<primary>backup</primary>" |
| 336 |
msgstr "<primary>debian-cd</primary>" |
| 337 |
|
| 338 |
msgid "RAID systems are not backup mechanisms. While RAID increases the redundancy - and therefore the availability of a system - and protects against disk failures, backups are done to protect data from being altered, deleted, getting corrupted, etc., and to be able to restore them if necessary. To demonstrate this: If you remove one or all files by accident, a RAID will mirror this change, but it will not provide the means to restore the file(s). So while there is clearly an overlap, they are not the same and should be used in conjunction with each other." |
| 339 |
msgstr "" |
| 340 |
|
| 341 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 342 |
msgid "RAID-4" |
| 343 |
msgstr "RAID-4" |
| 344 |
|
| 345 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 346 |
msgid "This RAID level, not widely used, uses N disks to store useful data, and an extra disk to store redundancy information. If that disk fails, the system can reconstruct its contents from the other N. If one of the N data disks fails, the remaining N-1 combined with the “parity” disk contain enough information to reconstruct the required data." |
| 347 |
msgstr "RAID-4 は広く使われていません。RAID-4 は実データを保存するために N 台のディスクを使い、冗長性情報を保存するために 1 台の「パリティ」ディスクを使います。「パリティ」ディスクに障害が起きた場合、システムは他の N 台からデータを再構成することが可能です。N 台のデータディスクのうち、最大で 1 台に障害が起きた場合、残りの N-1 台と「パリティ」ディスクには、要求されたデータを再構成するために十分な情報が含まれます。" |
| 348 |
|
| 349 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 350 |
#, fuzzy |
| 351 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 352 |
msgid "<primary>RAID</primary><secondary>4</secondary>" |
| 353 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 354 |
|
| 355 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 356 |
#, fuzzy |
| 357 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 358 |
msgid "<primary>RAID</primary><secondary>parity</secondary>" |
| 359 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 360 |
|
| 361 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 362 |
msgid "RAID-4 isn't too expensive since it only involves a one-in-N increase in costs and has no noticeable impact on read performance, but writes are slowed down. Furthermore, since a write to any of the N disks also involves a write to the parity disk, the latter sees many more writes than the former, and its lifespan can shorten dramatically as a consequence. Data on a RAID-4 array is safe only up to one failed disk (of the N+1)." |
| 363 |
msgstr "RAID-4 は高価過ぎるというわけではありません。なぜならディスク 1 台につきたった N 分の 1 台分の追加費用で済むからです。また RAID-4 を使うと読み込み性能が大きく低下するというわけでもありません。しかしながら、RAID-4 は書き込み性能に深刻な影響をおよぼします。加えて、N 台の実データ用ディスクのどのディスクに書き込んでもパリティディスクに対する書き込みが発生するので、パリティディスクは実データ用ディスクに比べて書き込み回数が増えます。その結果、パリティディスクは極めて寿命が短くなります。RAID-4 アレイのデータは (N+1 台のディスクのうち) 1 台の障害に対して保護されます。" |
| 364 |
|
| 365 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 366 |
msgid "RAID-5" |
| 367 |
msgstr "RAID-5" |
| 368 |
|
| 369 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 370 |
msgid "RAID-5 addresses the asymmetry issue of RAID-4: parity blocks are spread over all of the N+1 disks, with no single disk having a particular role." |
| 371 |
msgstr "RAID-5 は RAID-4 の非対称性問題を対処したものです。すなわち、パリティブロックは N+1 台のディスクに分散して保存され、特定のディスクが特定の役割を果たすことはありません。" |
| 372 |
|
| 373 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 374 |
#, fuzzy |
| 375 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 376 |
msgid "<primary>RAID</primary><secondary>5</secondary>" |
| 377 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 378 |
|
| 379 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 380 |
msgid "Read and write performance are identical to RAID-4. Here again, the system stays functional with up to one failed disk (of the N+1), but no more." |
| 381 |
msgstr "読み込みと書き込み性能は RAID-4 と同様です。繰り返しになりますが、RAID-5 システムは (N+1 台のディスクのうち) 最大で 1 台までに障害が起きても動作します。" |
| 382 |
|
| 383 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 384 |
msgid "RAID-6" |
| 385 |
msgstr "RAID-6" |
| 386 |
|
| 387 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 388 |
msgid "RAID-6 can be considered an extension of RAID-5, where each series of N blocks involves two redundancy blocks, and each such series of N+2 blocks is spread over N+2 disks." |
| 389 |
msgstr "RAID-6 は RAID-5 の拡張と考えられます。RAID-6 では、N 個の連続するブロックに対して 2 個の冗長性ブロックを使います。この N+2 個のブロックは N+2 台のディスクに分散して保存されます。" |
| 390 |
|
| 391 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 392 |
#, fuzzy |
| 393 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 394 |
msgid "<primary>RAID</primary><secondary>6</secondary>" |
| 395 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 396 |
|
| 397 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 398 |
msgid "This RAID level is slightly more expensive than the previous two, but it brings some extra safety since up to two drives (of the N+2) can fail without compromising data availability. The counterpart is that write operations now involve writing one data block and two redundancy blocks, which makes them even slower." |
| 399 |
msgstr "RAID-6 は RAID-4 と RAID-5 に比べて少し高価ですが、RAID-6 を使うことで安全性はさらに高まります。なぜなら、(N+2 台中の) 最大で 2 台までの障害に対してデータを守ることが可能だからです。書き込み操作は 1 つのデータブロックと 2 つの冗長性ブロックを書き込むことに対応しますから、RAID-6 の書き込み性能は RAID-4 と RAID-5 に比べてさらに悪化します。" |
| 400 |
|
| 401 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 402 |
msgid "RAID-1+0" |
| 403 |
msgstr "RAID-1+0" |
| 404 |
|
| 405 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 406 |
#, fuzzy |
| 407 |
#| msgid "This isn't strictly speaking, a RAID level, but a stacking of two RAID groupings. Starting from 2×N disks, one first sets them up by pairs into N RAID-1 volumes; these N volumes are then aggregated into one, either by “linear RAID” or (increasingly) by LVM. This last case goes farther than pure RAID, but there's no problem with that." |
| 408 |
msgid "This isn't strictly speaking, a RAID level, but a stacking of two RAID groupings. Starting from 2×N disks, one first sets them up by pairs into N RAID-1 volumes; these N volumes are then aggregated into one, either by “linear RAID” or (increasingly) by LVM. This last case goes farther than pure RAID, but there is no problem with that." |
| 409 |
msgstr "厳密に言えば RAID-1+0 は RAID レベルではなく、2 種類の RAID 分類を積み重ねたものです。RAID-1+0 を使うには 2×N 台のディスクが必要で、最初に 2 台ずつのペアから N 台の RAID-1 ボリュームを作ります。N 台の RAID-1 ボリュームは「リニア RAID」か LVM (次第にこちらを選ぶケースが増えています) のどちらか一方を使って 1 台に統合されます。LVM を使うと純粋な RAID ではなくなりますが、LVM を使っても問題はありません。" |
| 410 |
|
| 411 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 412 |
#, fuzzy |
| 413 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 414 |
msgid "<primary>RAID</primary><secondary>1+0</secondary>" |
| 415 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 416 |
|
| 417 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 418 |
msgid "RAID-1+0 can survive multiple disk failures: up to N in the 2×N array described above, provided that at least one disk keeps working in each of the RAID-1 pairs." |
| 419 |
msgstr "RAID-1+0 は複数のディスク障害を乗り切ることが可能です。具体的に言えば、上に挙げた 2×N アレイの場合、最大で N 台までの障害に耐えます。ただし、各 RAID-1 ペアを構成するディスクの両方に障害が発生してはいけません。" |
| 420 |
|
| 421 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 422 |
msgid "<emphasis>GOING FURTHER</emphasis> RAID-10" |
| 423 |
msgstr "<emphasis>GOING FURTHER</emphasis> RAID-10" |
| 424 |
|
| 425 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 426 |
#, fuzzy |
| 427 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 428 |
msgid "<primary>RAID</primary><secondary>10</secondary>" |
| 429 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 430 |
|
| 431 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 432 |
msgid "RAID-10 is generally considered a synonym of RAID-1+0, but a Linux specificity makes it actually a generalization. This setup allows a system where each block is stored on two different disks, even with an odd number of disks, the copies being spread out along a configurable model." |
| 433 |
msgstr "通常 RAID-10 は RAID-1+0 の同意語と考えられますが、Linux では特別に RAID-10 をより一般的な構成を可能にするものとして定めています。RAID-10 では、システムが各ブロックを 2 種類の異なるディスクに保存することが可能です。奇数台のディスク構成の場合でも、ブロックのコピーは設定可能なモデルに従って分散して保存されます。" |
| 434 |
|
| 435 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 436 |
msgid "Performances will vary depending on the chosen repartition model and redundancy level, and of the workload of the logical volume." |
| 437 |
msgstr "RAID-10 の性能は選択した再分割モデルと冗長性の度合い、そして論理ボリュームの作業負荷に依存して変化します。" |
| 438 |
|
| 439 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 440 |
msgid "Obviously, the RAID level will be chosen according to the constraints and requirements of each application. Note that a single computer can have several distinct RAID arrays with different configurations." |
| 441 |
msgstr "RAID レベルを選ぶ際には、各用途からの制限および要求を考慮する必要があるのは明らかです。1 台のコンピュータに異なる設定を持つ複数の RAID アレイを配置することが可能である点に注意してください。" |
| 442 |
|
| 443 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 444 |
msgid "Setting up RAID" |
| 445 |
msgstr "RAID の設定" |
| 446 |
|
| 447 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 448 |
msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 449 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 450 |
|
| 451 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 452 |
#, fuzzy |
| 453 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 454 |
msgid "<primary>RAID</primary><secondary>create</secondary>" |
| 455 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 456 |
|
| 457 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 458 |
msgid "Setting up RAID volumes requires the <emphasis role=\"pkg\">mdadm</emphasis> package; it provides the <command>mdadm</command> command, which allows creating and manipulating RAID arrays, as well as scripts and tools integrating it to the rest of the system, including the monitoring system." |
| 459 |
msgstr "RAID ボリュームを設定するには <emphasis role=\"pkg\">mdadm</emphasis> パッケージが必要です。<emphasis role=\"pkg\">mdadm</emphasis> パッケージには RAID アレイを作成したり操作するための <command>mdadm</command> コマンド、システムの他の部分に RAID アレイを統合するためのスクリプトやツール、監視システムが含まれます。" |
| 460 |
|
| 461 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 462 |
msgid "Our example will be a server with a number of disks, some of which are already used, the rest being available to setup RAID. We initially have the following disks and partitions:" |
| 463 |
msgstr "以下の例では、多数のディスクを持つサーバをセットアップします。ディスクの一部は既に利用されており、残りは RAID をセットアップするために利用できるようになっています。最初の状態で、以下のディスクとパーティションが存在します。" |
| 464 |
|
| 465 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 466 |
msgid "the <filename>sdb</filename> disk, 4 GB, is entirely available;" |
| 467 |
msgstr "<filename>sdb</filename> ディスク (4 GB) は全領域を利用できます。" |
| 468 |
|
| 469 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 470 |
msgid "the <filename>sdc</filename> disk, 4 GB, is also entirely available;" |
| 471 |
msgstr "<filename>sdc</filename> ディスク (4 GB) は全領域を利用できます。" |
| 472 |
|
| 473 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 474 |
msgid "on the <filename>sdd</filename> disk, only partition <filename>sdd2</filename> (about 4 GB) is available;" |
| 475 |
msgstr "<filename>sdd</filename> ディスクは <filename>sdd2</filename> パーティション (約 4 GB) だけを利用できます。" |
| 476 |
|
| 477 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 478 |
msgid "finally, a <filename>sde</filename> disk, still 4 GB, entirely available." |
| 479 |
msgstr "<filename>sde</filename> ディスク (4 GB) は全領域を利用できます。" |
| 480 |
|
| 481 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 482 |
msgid "<emphasis>NOTE</emphasis> Identifying existing RAID volumes" |
| 483 |
msgstr "<emphasis>NOTE</emphasis> 既存の RAID ボリュームの識別" |
| 484 |
|
| 485 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 486 |
#, fuzzy |
| 487 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 488 |
msgid "<primary><filename>/proc</filename></primary><secondary><filename>/proc/mdstat</filename></secondary>" |
| 489 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 490 |
|
| 491 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 492 |
msgid "The <filename>/proc/mdstat</filename> file lists existing volumes and their states. When creating a new RAID volume, care should be taken not to name it the same as an existing volume." |
| 493 |
msgstr "<filename>/proc/mdstat</filename> ファイルには既存のボリュームとその状態が書かれています。新しい RAID ボリュームを作成する場合、既存のボリュームと同じ名前を付けないように注意してください。" |
| 494 |
|
| 495 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 496 |
msgid "We're going to use these physical elements to build two volumes, one RAID-0 and one mirror (RAID-1). Let's start with the RAID-0 volume:" |
| 497 |
msgstr "RAID-0 とミラー (RAID-1) の 2 つのボリュームを作るために上記の物理ディスクを使います。それでは RAID-0 ボリュームから作っていきましょう。" |
| 498 |
|
| 499 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 500 |
# Tag: L-CFMD; |
| 501 |
#, fuzzy |
| 502 |
#| msgid "" |
| 503 |
#| "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb /dev/sdc</userinput>\n" |
| 504 |
#| "<computeroutput>mdadm: Defaulting to version 1.2 metadata\n" |
| 505 |
#| "mdadm: array /dev/md0 started.\n" |
| 506 |
#| "# </computeroutput><userinput>mdadm --query /dev/md0</userinput>\n" |
| 507 |
#| "<computeroutput>/dev/md0: 8.00GiB raid0 2 devices, 0 spares. Use mdadm --detail for more detail.\n" |
| 508 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md0</userinput>\n" |
| 509 |
#| "<computeroutput>/dev/md0:\n" |
| 510 |
#| " Version : 1.2\n" |
| 511 |
#| " Creation Time : Wed May 6 09:24:34 2015\n" |
| 512 |
#| " Raid Level : raid0\n" |
| 513 |
#| " Array Size : 8387584 (8.00 GiB 8.59 GB)\n" |
| 514 |
#| " Raid Devices : 2\n" |
| 515 |
#| " Total Devices : 2\n" |
| 516 |
#| " Persistence : Superblock is persistent\n" |
| 517 |
#| "\n" |
| 518 |
#| " Update Time : Wed May 6 09:24:34 2015\n" |
| 519 |
#| " State : clean \n" |
| 520 |
#| " Active Devices : 2\n" |
| 521 |
#| "Working Devices : 2\n" |
| 522 |
#| " Failed Devices : 0\n" |
| 523 |
#| " Spare Devices : 0\n" |
| 524 |
#| "\n" |
| 525 |
#| " Chunk Size : 512K\n" |
| 526 |
#| "\n" |
| 527 |
#| " Name : mirwiz:0 (local to host mirwiz)\n" |
| 528 |
#| " UUID : bb085b35:28e821bd:20d697c9:650152bb\n" |
| 529 |
#| " Events : 0\n" |
| 530 |
#| "\n" |
| 531 |
#| " Number Major Minor RaidDevice State\n" |
| 532 |
#| " 0 8 16 0 active sync /dev/sdb\n" |
| 533 |
#| " 1 8 32 1 active sync /dev/sdc\n" |
| 534 |
#| "# </computeroutput><userinput>mkfs.ext4 /dev/md0</userinput>\n" |
| 535 |
#| "<computeroutput>mke2fs 1.42.12 (29-Aug-2014)\n" |
| 536 |
#| "Creating filesystem with 2095104 4k blocks and 524288 inodes\n" |
| 537 |
#| "Filesystem UUID: fff08295-bede-41a9-9c6a-8c7580e520a6\n" |
| 538 |
#| "Superblock backups stored on blocks: \n" |
| 539 |
#| " 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632\n" |
| 540 |
#| "\n" |
| 541 |
#| "Allocating group tables: done \n" |
| 542 |
#| "Writing inode tables: done \n" |
| 543 |
#| "Creating journal (32768 blocks): done\n" |
| 544 |
#| "Writing superblocks and filesystem accounting information: done \n" |
| 545 |
#| "# </computeroutput><userinput>mkdir /srv/raid-0</userinput>\n" |
| 546 |
#| "<computeroutput># </computeroutput><userinput>mount /dev/md0 /srv/raid-0</userinput>\n" |
| 547 |
#| "<computeroutput># </computeroutput><userinput>df -h /srv/raid-0</userinput>\n" |
| 548 |
#| "<computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 549 |
#| "/dev/md0 7.9G 18M 7.4G 1% /srv/raid-0\n" |
| 550 |
#| "</computeroutput>" |
| 551 |
msgid "" |
| 552 |
"<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb /dev/sdc\n" |
| 553 |
"</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\n" |
| 554 |
"mdadm: array /dev/md0 started.\n" |
| 555 |
"# </computeroutput><userinput>mdadm --query /dev/md0\n" |
| 556 |
"</userinput><computeroutput>/dev/md0: 7.99GiB raid0 2 devices, 0 spares. Use mdadm --detail for more detail.\n" |
| 557 |
"# </computeroutput><userinput>mdadm --detail /dev/md0\n" |
| 558 |
"</userinput><computeroutput>/dev/md0:\n" |
| 559 |
" Version : 1.2\n" |
| 560 |
" Creation Time : Mon Feb 28 01:54:24 2022\n" |
| 561 |
" Raid Level : raid0\n" |
| 562 |
" Array Size : 8378368 (7.99 GiB 8.58 GB)\n" |
| 563 |
" Raid Devices : 2\n" |
| 564 |
" Total Devices : 2\n" |
| 565 |
" Persistence : Superblock is persistent\n" |
| 566 |
"\n" |
| 567 |
" Update Time : Mon Feb 28 01:54:24 2022\n" |
| 568 |
" State : clean \n" |
| 569 |
" Active Devices : 2\n" |
| 570 |
" Working Devices : 2\n" |
| 571 |
" Failed Devices : 0\n" |
| 572 |
" Spare Devices : 0\n" |
| 573 |
"\n" |
| 574 |
" Layout : -unknown-\n" |
| 575 |
" Chunk Size : 512K\n" |
| 576 |
"\n" |
| 577 |
"Consistency Policy : none\n" |
| 578 |
"\n" |
| 579 |
" Name : debian:0 (local to host debian)\n" |
| 580 |
" UUID : a75ac628:b384c441:157137ac:c04cd98c\n" |
| 581 |
" Events : 0\n" |
| 582 |
"\n" |
| 583 |
" Number Major Minor RaidDevice State\n" |
| 584 |
" 0 8 0 0 active sync /dev/sdb\n" |
| 585 |
" 1 8 16 1 active sync /dev/sdc\n" |
| 586 |
"# </computeroutput><userinput>mkfs.ext4 /dev/md0\n" |
| 587 |
"</userinput><computeroutput>mke2fs 1.46.2 (28-Feb-2021)\n" |
| 588 |
"Discarding device blocks: done \n" |
| 589 |
"Creating filesystem with 2094592 4k blocks and 524288 inodes\n" |
| 590 |
"Filesystem UUID: ef077204-c477-4430-bf01-52288237bea0\n" |
| 591 |
"Superblock backups stored on blocks: \n" |
| 592 |
"\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632\n" |
| 593 |
"\n" |
| 594 |
"Allocating group tables: done \n" |
| 595 |
"Writing inode tables: done \n" |
| 596 |
"Creating journal (16384 blocks): done\n" |
| 597 |
"Writing superblocks and filesystem accounting information: done \n" |
| 598 |
"\n" |
| 599 |
"# </computeroutput><userinput>mkdir /srv/raid-0\n" |
| 600 |
"</userinput><computeroutput># </computeroutput><userinput>mount /dev/md0 /srv/raid-0\n" |
| 601 |
"</userinput><computeroutput># </computeroutput><userinput>df -h /srv/raid-0\n" |
| 602 |
"</userinput><computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 603 |
"/dev/md0 7.8G 24K 7.4G 1% /srv/raid-0\n" |
| 604 |
"</computeroutput>" |
| 605 |
msgstr "" |
| 606 |
"<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb /dev/sdc</userinput>\n" |
| 607 |
"<computeroutput>mdadm: Defaulting to version 1.2 metadata\n" |
| 608 |
"mdadm: array /dev/md0 started.\n" |
| 609 |
"# </computeroutput><userinput>mdadm --query /dev/md0</userinput>\n" |
| 610 |
"<computeroutput>/dev/md0: 8.00GiB raid0 2 devices, 0 spares. Use mdadm --detail for more detail.\n" |
| 611 |
"# </computeroutput><userinput>mdadm --detail /dev/md0</userinput>\n" |
| 612 |
"<computeroutput>/dev/md0:\n" |
| 613 |
" Version : 1.2\n" |
| 614 |
" Creation Time : Wed May 6 09:24:34 2015\n" |
| 615 |
" Raid Level : raid0\n" |
| 616 |
" Array Size : 8387584 (8.00 GiB 8.59 GB)\n" |
| 617 |
" Raid Devices : 2\n" |
| 618 |
" Total Devices : 2\n" |
| 619 |
" Persistence : Superblock is persistent\n" |
| 620 |
"\n" |
| 621 |
" Update Time : Wed May 6 09:24:34 2015\n" |
| 622 |
" State : clean \n" |
| 623 |
" Active Devices : 2\n" |
| 624 |
"Working Devices : 2\n" |
| 625 |
" Failed Devices : 0\n" |
| 626 |
" Spare Devices : 0\n" |
| 627 |
"\n" |
| 628 |
" Chunk Size : 512K\n" |
| 629 |
"\n" |
| 630 |
" Name : mirwiz:0 (local to host mirwiz)\n" |
| 631 |
" UUID : bb085b35:28e821bd:20d697c9:650152bb\n" |
| 632 |
" Events : 0\n" |
| 633 |
"\n" |
| 634 |
" Number Major Minor RaidDevice State\n" |
| 635 |
" 0 8 16 0 active sync /dev/sdb\n" |
| 636 |
" 1 8 32 1 active sync /dev/sdc\n" |
| 637 |
"# </computeroutput><userinput>mkfs.ext4 /dev/md0</userinput>\n" |
| 638 |
"<computeroutput>mke2fs 1.42.12 (29-Aug-2014)\n" |
| 639 |
"Creating filesystem with 2095104 4k blocks and 524288 inodes\n" |
| 640 |
"Filesystem UUID: fff08295-bede-41a9-9c6a-8c7580e520a6\n" |
| 641 |
"Superblock backups stored on blocks: \n" |
| 642 |
" 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632\n" |
| 643 |
"\n" |
| 644 |
"Allocating group tables: done \n" |
| 645 |
"Writing inode tables: done \n" |
| 646 |
"Creating journal (32768 blocks): done\n" |
| 647 |
"Writing superblocks and filesystem accounting information: done \n" |
| 648 |
"# </computeroutput><userinput>mkdir /srv/raid-0</userinput>\n" |
| 649 |
"<computeroutput># </computeroutput><userinput>mount /dev/md0 /srv/raid-0</userinput>\n" |
| 650 |
"<computeroutput># </computeroutput><userinput>df -h /srv/raid-0</userinput>\n" |
| 651 |
"<computeroutput>ファイルシス サイズ 使用 残り 使用% マウント位置\n" |
| 652 |
"/dev/md0 7.9G 18M 7.4G 1% /srv/raid-0\n" |
| 653 |
"</computeroutput>" |
| 654 |
|
| 655 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 656 |
#, fuzzy |
| 657 |
#| msgid "The <command>mdadm --create</command> command requires several parameters: the name of the volume to create (<filename>/dev/md*</filename>, with MD standing for <foreignphrase>Multiple Device</foreignphrase>), the RAID level, the number of disks (which is compulsory despite being mostly meaningful only with RAID-1 and above), and the physical drives to use. Once the device is created, we can use it like we'd use a normal partition, create a filesystem on it, mount that filesystem, and so on. Note that our creation of a RAID-0 volume on <filename>md0</filename> is nothing but coincidence, and the numbering of the array doesn't need to be correlated to the chosen amount of redundancy. It's also possible to create named RAID arrays, by giving <command>mdadm</command> parameters such as <filename>/dev/md/linear</filename> instead of <filename>/dev/md0</filename>." |
| 658 |
msgid "The <command>mdadm --create</command> command requires several parameters: the name of the volume to create (<filename>/dev/md*</filename>, with MD standing for <foreignphrase>Multiple Device</foreignphrase>), the RAID level, the number of disks (which is compulsory despite being mostly meaningful only with RAID-1 and above), and the physical drives to use. Once the device is created, we can use it like we'd use a normal partition, create a filesystem on it, mount that filesystem, and so on. Note that our creation of a RAID-0 volume on <filename>md0</filename> is nothing but coincidence, and the numbering of the array doesn't need to be correlated to the chosen amount of redundancy. It is also possible to create named RAID arrays, by giving <command>mdadm</command> parameters such as <filename>/dev/md/linear</filename> instead of <filename>/dev/md0</filename>." |
| 659 |
msgstr "<command>mdadm --create</command> コマンドには複数のパラメータが必要です。具体的に言えば、作成するボリュームの名前 (<filename>/dev/md*</filename>、MD は <foreignphrase>Multiple Device</foreignphrase> を意味します)、RAID レベル、ディスク数 (普通この値は RAID-1 とそれ以上のレベルでのみ意味があるにも関わらず、これは必須オプションです)、RAID を構成する物理デバイスを指定する必要があります。RAID デバイスを作成したら、RAID デバイスを通常のパーティションを取り扱うのと同様のやり方で取り扱うことが可能です。すなわち、ファイルシステムを作成したり、ファイルシステムをマウントしたりすることが可能です。ここで作成する RAID-0 ボリュームに <filename>md0</filename> と名前を付けたのは偶然に過ぎない点に注意してください。アレイに付けられた番号と冗長性の度合いを関連付ける必要はありません。また、<filename>/dev/md0</filename> の代わりに <filename>/dev/md/linear</filename> のようなパラメータを <command>mdadm</command> に渡すことで、名前付き RAID アレイを作成することも可能です。" |
| 660 |
|
| 661 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 662 |
msgid "Creation of a RAID-1 follows a similar fashion, the differences only being noticeable after the creation:" |
| 663 |
msgstr "同様のやり方で RAID-1 を作成します。注意するべき違いは作成後に説明します。" |
| 664 |
|
| 665 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 666 |
# Tag: L-CFMD; |
| 667 |
#, fuzzy |
| 668 |
#| msgid "" |
| 669 |
#| "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd2 /dev/sde</userinput>\n" |
| 670 |
#| "<computeroutput>mdadm: Note: this array has metadata at the start and\n" |
| 671 |
#| " may not be suitable as a boot device. If you plan to\n" |
| 672 |
#| " store '/boot' on this device please ensure that\n" |
| 673 |
#| " your boot-loader understands md/v1.x metadata, or use\n" |
| 674 |
#| " --metadata=0.90\n" |
| 675 |
#| "mdadm: largest drive (/dev/sdd2) exceeds size (4192192K) by more than 1%\n" |
| 676 |
#| "Continue creating array? </computeroutput><userinput>y</userinput>\n" |
| 677 |
#| "<computeroutput>mdadm: Defaulting to version 1.2 metadata\n" |
| 678 |
#| "mdadm: array /dev/md1 started.\n" |
| 679 |
#| "# </computeroutput><userinput>mdadm --query /dev/md1</userinput>\n" |
| 680 |
#| "<computeroutput>/dev/md1: 4.00GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.\n" |
| 681 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 682 |
#| "<computeroutput>/dev/md1:\n" |
| 683 |
#| " Version : 1.2\n" |
| 684 |
#| " Creation Time : Wed May 6 09:30:19 2015\n" |
| 685 |
#| " Raid Level : raid1\n" |
| 686 |
#| " Array Size : 4192192 (4.00 GiB 4.29 GB)\n" |
| 687 |
#| " Used Dev Size : 4192192 (4.00 GiB 4.29 GB)\n" |
| 688 |
#| " Raid Devices : 2\n" |
| 689 |
#| " Total Devices : 2\n" |
| 690 |
#| " Persistence : Superblock is persistent\n" |
| 691 |
#| "\n" |
| 692 |
#| " Update Time : Wed May 6 09:30:40 2015\n" |
| 693 |
#| " State : clean, resyncing (PENDING) \n" |
| 694 |
#| " Active Devices : 2\n" |
| 695 |
#| "Working Devices : 2\n" |
| 696 |
#| " Failed Devices : 0\n" |
| 697 |
#| " Spare Devices : 0\n" |
| 698 |
#| "\n" |
| 699 |
#| " Name : mirwiz:1 (local to host mirwiz)\n" |
| 700 |
#| " UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 701 |
#| " Events : 0\n" |
| 702 |
#| "\n" |
| 703 |
#| " Number Major Minor RaidDevice State\n" |
| 704 |
#| " 0 8 50 0 active sync /dev/sdd2\n" |
| 705 |
#| " 1 8 64 1 active sync /dev/sde\n" |
| 706 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 707 |
#| "<computeroutput>/dev/md1:\n" |
| 708 |
#| "[...]\n" |
| 709 |
#| " State : clean\n" |
| 710 |
#| "[...]\n" |
| 711 |
#| "</computeroutput>" |
| 712 |
msgid "" |
| 713 |
"<computeroutput># </computeroutput><userinput>mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd2 /dev/sde\n" |
| 714 |
"</userinput><computeroutput>mdadm: Note: this array has metadata at the start and\n" |
| 715 |
" may not be suitable as a boot device. If you plan to\n" |
| 716 |
" store '/boot' on this device please ensure that\n" |
| 717 |
" your boot-loader understands md/v1.x metadata, or use\n" |
| 718 |
" --metadata=0.90\n" |
| 719 |
"mdadm: largest drive (/dev/sdc2) exceeds size (4189184K) by more than 1%\n" |
| 720 |
"Continue creating array? </computeroutput><userinput>y\n" |
| 721 |
"</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\n" |
| 722 |
"mdadm: array /dev/md1 started.\n" |
| 723 |
"# </computeroutput><userinput>mdadm --query /dev/md1\n" |
| 724 |
"</userinput><computeroutput>/dev/md1: 4.00GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.\n" |
| 725 |
"# </computeroutput><userinput>mdadm --detail /dev/md1\n" |
| 726 |
"</userinput><computeroutput>/dev/md1:\n" |
| 727 |
" Version : 1.2\n" |
| 728 |
" Creation Time : Mon Feb 28 02:07:48 2022\n" |
| 729 |
" Raid Level : raid1\n" |
| 730 |
" Array Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 731 |
" Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 732 |
" Raid Devices : 2\n" |
| 733 |
" Total Devices : 2\n" |
| 734 |
" Persistence : Superblock is persistent\n" |
| 735 |
"\n" |
| 736 |
" Update Time : Mon Feb 28 02:08:09 2022\n" |
| 737 |
" State : clean, resync\n" |
| 738 |
" Active Devices : 2\n" |
| 739 |
" Working Devices : 2\n" |
| 740 |
" Failed Devices : 0\n" |
| 741 |
" Spare Devices : 0\n" |
| 742 |
"\n" |
| 743 |
"Consistency Policy : resync\n" |
| 744 |
"\n" |
| 745 |
" Rebuild Status : 13% complete\n" |
| 746 |
"\n" |
| 747 |
" Name : debian:1 (local to host debian)\n" |
| 748 |
" UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n" |
| 749 |
" Events : 17\n" |
| 750 |
"\n" |
| 751 |
" Number Major Minor RaidDevice State\n" |
| 752 |
" 0 8 34 0 active sync /dev/sdd2\n" |
| 753 |
" 1 8 48 1 active sync /dev/sde\n" |
| 754 |
"# </computeroutput><userinput>mdadm --detail /dev/md1\n" |
| 755 |
"</userinput><computeroutput>/dev/md1:\n" |
| 756 |
"[...]\n" |
| 757 |
" State : clean\n" |
| 758 |
"[...]\n" |
| 759 |
"</computeroutput>" |
| 760 |
msgstr "" |
| 761 |
"<computeroutput># </computeroutput><userinput>mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd2 /dev/sde</userinput>\n" |
| 762 |
"<computeroutput>mdadm: Note: this array has metadata at the start and\n" |
| 763 |
" may not be suitable as a boot device. If you plan to\n" |
| 764 |
" store '/boot' on this device please ensure that\n" |
| 765 |
" your boot-loader understands md/v1.x metadata, or use\n" |
| 766 |
" --metadata=0.90\n" |
| 767 |
"mdadm: largest drive (/dev/sdd2) exceeds size (4192192K) by more than 1%\n" |
| 768 |
"Continue creating array? </computeroutput><userinput>y</userinput>\n" |
| 769 |
"<computeroutput>mdadm: Defaulting to version 1.2 metadata\n" |
| 770 |
"mdadm: array /dev/md1 started.\n" |
| 771 |
"# </computeroutput><userinput>mdadm --query /dev/md1</userinput>\n" |
| 772 |
"<computeroutput>/dev/md1: 4.00GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.\n" |
| 773 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 774 |
"<computeroutput>/dev/md1:\n" |
| 775 |
" Version : 1.2\n" |
| 776 |
" Creation Time : Wed May 6 09:30:19 2015\n" |
| 777 |
" Raid Level : raid1\n" |
| 778 |
" Array Size : 4192192 (4.00 GiB 4.29 GB)\n" |
| 779 |
" Used Dev Size : 4192192 (4.00 GiB 4.29 GB)\n" |
| 780 |
" Raid Devices : 2\n" |
| 781 |
" Total Devices : 2\n" |
| 782 |
" Persistence : Superblock is persistent\n" |
| 783 |
"\n" |
| 784 |
" Update Time : Wed May 6 09:30:40 2015\n" |
| 785 |
" State : clean, resyncing (PENDING) \n" |
| 786 |
" Active Devices : 2\n" |
| 787 |
"Working Devices : 2\n" |
| 788 |
" Failed Devices : 0\n" |
| 789 |
" Spare Devices : 0\n" |
| 790 |
"\n" |
| 791 |
" Name : mirwiz:1 (local to host mirwiz)\n" |
| 792 |
" UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 793 |
" Events : 0\n" |
| 794 |
"\n" |
| 795 |
" Number Major Minor RaidDevice State\n" |
| 796 |
" 0 8 50 0 active sync /dev/sdd2\n" |
| 797 |
" 1 8 64 1 active sync /dev/sde\n" |
| 798 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 799 |
"<computeroutput>/dev/md1:\n" |
| 800 |
"[...]\n" |
| 801 |
" State : clean\n" |
| 802 |
"[...]\n" |
| 803 |
"</computeroutput>" |
| 804 |
|
| 805 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 806 |
msgid "<emphasis>TIP</emphasis> RAID, disks and partitions" |
| 807 |
msgstr "<emphasis>TIP</emphasis> RAID、ディスク、パーティション" |
| 808 |
|
| 809 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 810 |
#, fuzzy |
| 811 |
#| msgid "As illustrated by our example, RAID devices can be constructed out of disk partitions, and do not require full disks." |
| 812 |
msgid "As illustrated by our example, RAID devices can be constructed out of disk partitions as well, and do not require full disks." |
| 813 |
msgstr "上の例で示した通り、RAID デバイスはディスクパーティションに作成することが可能です。必ずディスク全体を使わなければいけないというわけではありません。" |
| 814 |
|
| 815 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 816 |
msgid "A few remarks are in order. First, <command>mdadm</command> notices that the physical elements have different sizes; since this implies that some space will be lost on the bigger element, a confirmation is required." |
| 817 |
msgstr "いくつかの注意点があります。最初に、<command>mdadm</command> は物理デバイス同士のサイズが異なる点を指摘しています。さらに、このことによりサイズが大きい側のデバイスの一部の領域が使えなくなるため、確認が求められています。" |
| 818 |
|
| 819 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 820 |
msgid "More importantly, note the state of the mirror. The normal state of a RAID mirror is that both disks have exactly the same contents. However, nothing guarantees this is the case when the volume is first created. The RAID subsystem will therefore provide that guarantee itself, and there will be a synchronization phase as soon as the RAID device is created. After some time (the exact amount will depend on the actual size of the disks…), the RAID array switches to the “active” or “clean” state. Note that during this reconstruction phase, the mirror is in a degraded mode, and redundancy isn't assured. A disk failing during that risk window could lead to losing all the data. Large amounts of critical data, however, are rarely stored on a freshly created RAID array before its initial synchronization. Note that even in degraded mode, the <filename>/dev/md1</filename> is usable, and a filesystem can be created on it, as well as some data copied on it." |
| 821 |
msgstr "さらに重要なことは、ミラーの状態に注意することです。RAID ミラーの正常な状態とは、両方のディスクが全く同じ内容を持っている状態です。しかしながら、ボリュームを最初に作成した直後の RAID ミラーは正常な状態であることを保証されません。このため、RAID サブシステムは RAID ミラーの正常な状態を保証するために、RAID デバイスが作成されたらすぐに同期化作業を始めます。しばらくの後 (必要な時間はディスクの実サイズに依存します)、RAID アレイは「active」または「clean」状態に移行します。同期化作業中、ミラーは信頼性低下状態で、冗長性は保証されない点に注意してください。同期化作業中にディスク障害が起きると、すべてのデータを失うことにつながる恐れがあります。しかしながら、最近作成された RAID アレイの最初の同期化作業の前に大量の重要なデータがこの RAID アレイに保存されていることはほとんどないでしょう。信頼性低下状態であっても <filename>/dev/md1</filename> を利用することが可能で、ファイルシステムを作成したり、データのコピーを取ったりすることが可能という点に注意してください。" |
| 822 |
|
| 823 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 824 |
msgid "<emphasis>TIP</emphasis> Starting a mirror in degraded mode" |
| 825 |
msgstr "<emphasis>TIP</emphasis> 信頼性低下状態でミラーを開始する" |
| 826 |
|
| 827 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 828 |
msgid "Sometimes two disks are not immediately available when one wants to start a RAID-1 mirror, for instance because one of the disks one plans to include is already used to store the data one wants to move to the array. In such circumstances, it is possible to deliberately create a degraded RAID-1 array by passing <filename>missing</filename> instead of a device file as one of the arguments to <command>mdadm</command>. Once the data have been copied to the “mirror”, the old disk can be added to the array. A synchronization will then take place, giving us the redundancy that was wanted in the first place." |
| 829 |
msgstr "RAID-1 ミラーを構成する 2 台のディスクの両方をすぐに使えないことが時々あります。たとえば、ミラーを構成するディスクの片方にミラーに移動したいデータが既に保存されている場合です。このような場合、<command>mdadm</command> に渡すデバイスファイル引数の片方をデバイスファイルの代わりに <filename>missing</filename> にすることで、意図的に信頼性低下状態の RAID-1 アレイを作成することも可能です。ミラーに移動したいデータを含むディスクからデータを「ミラー」にコピーした後、そのディスクをアレイに追加することが可能です。追加作業が終われば、同期化作業が行われ、ミラーに移動したかったデータの冗長性が確保されます。" |
| 830 |
|
| 831 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 832 |
msgid "<emphasis>TIP</emphasis> Setting up a mirror without synchronization" |
| 833 |
msgstr "<emphasis>TIP</emphasis> 同期化作業を行わずにミラーをセットアップする" |
| 834 |
|
| 835 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 836 |
# Tag: PTAL; |
| 837 |
msgid "RAID-1 volumes are often created to be used as a new disk, often considered blank. The actual initial contents of the disk is therefore not very relevant, since one only needs to know that the data written after the creation of the volume, in particular the filesystem, can be accessed later." |
| 838 |
msgstr "通常 RAID-1 ボリュームは新しいディスクとして使うために作成され、RAID-1 ボリュームの作成直後にはデータが保存されていないと考えられます。すなわち、RAID-1 ボリュームの初期内容に価値はなく、RAID-1 で保護したい重要なデータは RAID-1 ボリュームの作成後に書き込まれるデータというわけです。" |
| 839 |
|
| 840 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 841 |
# Tag: PTAL; |
| 842 |
msgid "One might therefore wonder about the point of synchronizing both disks at creation time. Why care whether the contents are identical on zones of the volume that we know will only be read after we have written to them?" |
| 843 |
msgstr "そう考えると、RAID-1 ボリュームにデータが書き込まれる前に RAID-1 ボリュームを構成するディスクの内容が同期されるという点について疑問に思うかもしれません。RAID-1 ボリュームに書き込んでいないデータは後から読み込まれることもないのにも関わらず、なぜ RAID-1 ボリュームの作成時に RAID-1 ボリュームを構成するディスクの内容の同期化作業が必要なのでしょうか?" |
| 844 |
|
| 845 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 846 |
# Tag: PTAL; |
| 847 |
msgid "Fortunately, this synchronization phase can be avoided by passing the <literal>--assume-clean</literal> option to <command>mdadm</command>. However, this option can lead to surprises in cases where the initial data will be read (for instance if a filesystem is already present on the physical disks), which is why it isn't enabled by default." |
| 848 |
msgstr "幸いなことに、RAID-1 を構成するディスクの内容の同期化作業は <literal>--assume-clean</literal> オプションを <command>mdadm</command> に渡せば避けることが可能です。しかしながら、初期データが読まれる場合、<literal>--assume-clean</literal> オプションを使うと問題があります (たとえば、物理ディスク上にファイルシステムが既に存在している場合、問題があります)。このため、デフォルトでこのオプションは有効化されません。" |
| 849 |
|
| 850 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 851 |
#, fuzzy |
| 852 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 853 |
msgid "<primary>RAID</primary><secondary>failing</secondary>" |
| 854 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 855 |
|
| 856 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 857 |
msgid "Now let's see what happens when one of the elements of the RAID-1 array fails. <command>mdadm</command>, in particular its <literal>--fail</literal> option, allows simulating such a disk failure:" |
| 858 |
msgstr "RAID-1 アレイを構成するディスクの 1 台に障害が発生した場合、何が起きるかを見て行きましょう。<command>mdadm</command> に <literal>--fail</literal> オプションを付けることで、ディスク障害を模倣することが可能です。" |
| 859 |
|
| 860 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 861 |
# Tag: L-CFMD; |
| 862 |
#, fuzzy |
| 863 |
#| msgid "" |
| 864 |
#| "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --fail /dev/sde</userinput>\n" |
| 865 |
#| "<computeroutput>mdadm: set /dev/sde faulty in /dev/md1\n" |
| 866 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 867 |
#| "<computeroutput>/dev/md1:\n" |
| 868 |
#| "[...]\n" |
| 869 |
#| " Update Time : Wed May 6 09:39:39 2015\n" |
| 870 |
#| " State : clean, degraded \n" |
| 871 |
#| " Active Devices : 1\n" |
| 872 |
#| "Working Devices : 1\n" |
| 873 |
#| " Failed Devices : 1\n" |
| 874 |
#| " Spare Devices : 0\n" |
| 875 |
#| "\n" |
| 876 |
#| " Name : mirwiz:1 (local to host mirwiz)\n" |
| 877 |
#| " UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 878 |
#| " Events : 19\n" |
| 879 |
#| "\n" |
| 880 |
#| " Number Major Minor RaidDevice State\n" |
| 881 |
#| " 0 8 50 0 active sync /dev/sdd2\n" |
| 882 |
#| " 2 0 0 2 removed\n" |
| 883 |
#| "\n" |
| 884 |
#| " 1 8 64 - faulty /dev/sde</computeroutput>" |
| 885 |
msgid "" |
| 886 |
"<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --fail /dev/sde\n" |
| 887 |
"</userinput><computeroutput>mdadm: set /dev/sde faulty in /dev/md1\n" |
| 888 |
"# </computeroutput><userinput>mdadm --detail /dev/md1\n" |
| 889 |
"</userinput><computeroutput>/dev/md1:\n" |
| 890 |
" Version : 1.2\n" |
| 891 |
" Creation Time : Mon Feb 28 02:07:48 2022\n" |
| 892 |
" Raid Level : raid1\n" |
| 893 |
" Array Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 894 |
" Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 895 |
" Raid Devices : 2\n" |
| 896 |
" Total Devices : 2\n" |
| 897 |
" Persistence : Superblock is persistent\n" |
| 898 |
"\n" |
| 899 |
" Update Time : Mon Feb 28 02:15:34 2022\n" |
| 900 |
" State : clean, degraded \n" |
| 901 |
" Active Devices : 1\n" |
| 902 |
" Working Devices : 1\n" |
| 903 |
" Failed Devices : 1\n" |
| 904 |
" Spare Devices : 0\n" |
| 905 |
"\n" |
| 906 |
"Consistency Policy : resync\n" |
| 907 |
"\n" |
| 908 |
" Name : debian:1 (local to host debian)\n" |
| 909 |
" UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n" |
| 910 |
" Events : 19\n" |
| 911 |
"\n" |
| 912 |
" Number Major Minor RaidDevice State\n" |
| 913 |
" 0 8 34 0 active sync /dev/sdd2\n" |
| 914 |
" - 0 0 1 removed\n" |
| 915 |
"\n" |
| 916 |
" 1 8 48 - faulty /dev/sde\n" |
| 917 |
"</computeroutput>" |
| 918 |
msgstr "" |
| 919 |
"<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --fail /dev/sde</userinput>\n" |
| 920 |
"<computeroutput>mdadm: set /dev/sde faulty in /dev/md1\n" |
| 921 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 922 |
"<computeroutput>/dev/md1:\n" |
| 923 |
"[...]\n" |
| 924 |
" Update Time : Wed May 6 09:39:39 2015\n" |
| 925 |
" State : clean, degraded \n" |
| 926 |
" Active Devices : 1\n" |
| 927 |
"Working Devices : 1\n" |
| 928 |
" Failed Devices : 1\n" |
| 929 |
" Spare Devices : 0\n" |
| 930 |
"\n" |
| 931 |
" Name : mirwiz:1 (local to host mirwiz)\n" |
| 932 |
" UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 933 |
" Events : 19\n" |
| 934 |
"\n" |
| 935 |
" Number Major Minor RaidDevice State\n" |
| 936 |
" 0 8 50 0 active sync /dev/sdd2\n" |
| 937 |
" 2 0 0 2 removed\n" |
| 938 |
"\n" |
| 939 |
" 1 8 64 - faulty /dev/sde</computeroutput>" |
| 940 |
|
| 941 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 942 |
msgid "The contents of the volume are still accessible (and, if it is mounted, the applications don't notice a thing), but the data safety isn't assured anymore: should the <filename>sdd</filename> disk fail in turn, the data would be lost. We want to avoid that risk, so we'll replace the failed disk with a new one, <filename>sdf</filename>:" |
| 943 |
msgstr "RAID-1 ボリュームの内容はまだアクセスすることが可能ですが (そして、RAID-1 ボリュームがマウントされていた場合、アプリケーションはディスク障害に気が付きませんが)、データの安全性はもはや保証されません。つまり <filename>sdd</filename> ディスクにも障害が発生した場合、データは失われます。この危険性を避けるために、障害の発生したディスクを新しいディスク <filename>sdf</filename> に交換します。" |
| 944 |
|
| 945 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 946 |
# Tag: L-CFMD; |
| 947 |
#, fuzzy |
| 948 |
#| msgid "" |
| 949 |
#| "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --add /dev/sdf</userinput>\n" |
| 950 |
#| "<computeroutput>mdadm: added /dev/sdf\n" |
| 951 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 952 |
#| "<computeroutput>/dev/md1:\n" |
| 953 |
#| "[...]\n" |
| 954 |
#| " Raid Devices : 2\n" |
| 955 |
#| " Total Devices : 3\n" |
| 956 |
#| " Persistence : Superblock is persistent\n" |
| 957 |
#| "\n" |
| 958 |
#| " Update Time : Wed May 6 09:48:49 2015\n" |
| 959 |
#| " State : clean, degraded, recovering \n" |
| 960 |
#| " Active Devices : 1\n" |
| 961 |
#| "Working Devices : 2\n" |
| 962 |
#| " Failed Devices : 1\n" |
| 963 |
#| " Spare Devices : 1\n" |
| 964 |
#| "\n" |
| 965 |
#| " Rebuild Status : 28% complete\n" |
| 966 |
#| "\n" |
| 967 |
#| " Name : mirwiz:1 (local to host mirwiz)\n" |
| 968 |
#| " UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 969 |
#| " Events : 26\n" |
| 970 |
#| "\n" |
| 971 |
#| " Number Major Minor RaidDevice State\n" |
| 972 |
#| " 0 8 50 0 active sync /dev/sdd2\n" |
| 973 |
#| " 2 8 80 1 spare rebuilding /dev/sdf\n" |
| 974 |
#| "\n" |
| 975 |
#| " 1 8 64 - faulty /dev/sde\n" |
| 976 |
#| "# </computeroutput><userinput>[...]</userinput>\n" |
| 977 |
#| "<computeroutput>[...]\n" |
| 978 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 979 |
#| "<computeroutput>/dev/md1:\n" |
| 980 |
#| "[...]\n" |
| 981 |
#| " Update Time : Wed May 6 09:49:08 2015\n" |
| 982 |
#| " State : clean \n" |
| 983 |
#| " Active Devices : 2\n" |
| 984 |
#| "Working Devices : 2\n" |
| 985 |
#| " Failed Devices : 1\n" |
| 986 |
#| " Spare Devices : 0\n" |
| 987 |
#| "\n" |
| 988 |
#| " Name : mirwiz:1 (local to host mirwiz)\n" |
| 989 |
#| " UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 990 |
#| " Events : 41\n" |
| 991 |
#| "\n" |
| 992 |
#| " Number Major Minor RaidDevice State\n" |
| 993 |
#| " 0 8 50 0 active sync /dev/sdd2\n" |
| 994 |
#| " 2 8 80 1 active sync /dev/sdf\n" |
| 995 |
#| "\n" |
| 996 |
#| " 1 8 64 - faulty /dev/sde</computeroutput>" |
| 997 |
msgid "" |
| 998 |
"<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --add /dev/sdf</userinput>\n" |
| 999 |
"<computeroutput>mdadm: added /dev/sdf\n" |
| 1000 |
"# </computeroutput><userinput>mdadm --detail /dev/md1\n" |
| 1001 |
"</userinput><computeroutput>/dev/md1:\n" |
| 1002 |
" Version : 1.2\n" |
| 1003 |
" Creation Time : Mon Feb 28 02:07:48 2022\n" |
| 1004 |
" Raid Level : raid1\n" |
| 1005 |
" Array Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 1006 |
" Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 1007 |
" Raid Devices : 2\n" |
| 1008 |
" Total Devices : 3\n" |
| 1009 |
" Persistence : Superblock is persistent\n" |
| 1010 |
"\n" |
| 1011 |
" Update Time : Mon Feb 28 02:25:34 2022\n" |
| 1012 |
" State : clean, degraded, recovering \n" |
| 1013 |
" Active Devices : 1\n" |
| 1014 |
" Working Devices : 2\n" |
| 1015 |
" Failed Devices : 1\n" |
| 1016 |
" Spare Devices : 1\n" |
| 1017 |
"\n" |
| 1018 |
"Consistency Policy : resync\n" |
| 1019 |
"\n" |
| 1020 |
" Rebuild Status : 47% complete\n" |
| 1021 |
"\n" |
| 1022 |
" Name : debian:1 (local to host debian)\n" |
| 1023 |
" UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n" |
| 1024 |
" Events : 39\n" |
| 1025 |
"\n" |
| 1026 |
" Number Major Minor RaidDevice State\n" |
| 1027 |
" 0 8 34 0 active sync /dev/sdd2\n" |
| 1028 |
" 2 8 64 1 spare rebuilding /dev/sdf\n" |
| 1029 |
"\n" |
| 1030 |
" 1 8 48 - faulty /dev/sde\n" |
| 1031 |
"# </computeroutput><userinput>[...]</userinput>\n" |
| 1032 |
"<computeroutput>[...]\n" |
| 1033 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 1034 |
"<computeroutput>/dev/md1:\n" |
| 1035 |
" Version : 1.2\n" |
| 1036 |
" Creation Time : Mon Feb 28 02:07:48 2022\n" |
| 1037 |
" Raid Level : raid1\n" |
| 1038 |
" Array Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 1039 |
" Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n" |
| 1040 |
" Raid Devices : 2\n" |
| 1041 |
" Total Devices : 3\n" |
| 1042 |
" Persistence : Superblock is persistent\n" |
| 1043 |
"\n" |
| 1044 |
" Update Time : Mon Feb 28 02:25:34 2022\n" |
| 1045 |
" State : clean\n" |
| 1046 |
" Active Devices : 2\n" |
| 1047 |
" Working Devices : 2\n" |
| 1048 |
" Failed Devices : 1\n" |
| 1049 |
" Spare Devices : 0\n" |
| 1050 |
"\n" |
| 1051 |
"Consistency Policy : resync\n" |
| 1052 |
"\n" |
| 1053 |
" Name : debian:1 (local to host debian)\n" |
| 1054 |
" UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n" |
| 1055 |
" Events : 41\n" |
| 1056 |
"\n" |
| 1057 |
" Number Major Minor RaidDevice State\n" |
| 1058 |
" 0 8 34 0 active sync /dev/sdd2\n" |
| 1059 |
" 2 8 64 1 active sync /dev/sdf\n" |
| 1060 |
"\n" |
| 1061 |
" 1 8 48 - faulty /dev/sde\n" |
| 1062 |
"</computeroutput>" |
| 1063 |
msgstr "" |
| 1064 |
"<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --add /dev/sdf</userinput>\n" |
| 1065 |
"<computeroutput>mdadm: added /dev/sdf\n" |
| 1066 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 1067 |
"<computeroutput>/dev/md1:\n" |
| 1068 |
"[...]\n" |
| 1069 |
" Raid Devices : 2\n" |
| 1070 |
" Total Devices : 3\n" |
| 1071 |
" Persistence : Superblock is persistent\n" |
| 1072 |
"\n" |
| 1073 |
" Update Time : Wed May 6 09:48:49 2015\n" |
| 1074 |
" State : clean, degraded, recovering \n" |
| 1075 |
" Active Devices : 1\n" |
| 1076 |
"Working Devices : 2\n" |
| 1077 |
" Failed Devices : 1\n" |
| 1078 |
" Spare Devices : 1\n" |
| 1079 |
"\n" |
| 1080 |
" Rebuild Status : 28% complete\n" |
| 1081 |
"\n" |
| 1082 |
" Name : mirwiz:1 (local to host mirwiz)\n" |
| 1083 |
" UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 1084 |
" Events : 26\n" |
| 1085 |
"\n" |
| 1086 |
" Number Major Minor RaidDevice State\n" |
| 1087 |
" 0 8 50 0 active sync /dev/sdd2\n" |
| 1088 |
" 2 8 80 1 spare rebuilding /dev/sdf\n" |
| 1089 |
"\n" |
| 1090 |
" 1 8 64 - faulty /dev/sde\n" |
| 1091 |
"# </computeroutput><userinput>[...]</userinput>\n" |
| 1092 |
"<computeroutput>[...]\n" |
| 1093 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 1094 |
"<computeroutput>/dev/md1:\n" |
| 1095 |
"[...]\n" |
| 1096 |
" Update Time : Wed May 6 09:49:08 2015\n" |
| 1097 |
" State : clean \n" |
| 1098 |
" Active Devices : 2\n" |
| 1099 |
"Working Devices : 2\n" |
| 1100 |
" Failed Devices : 1\n" |
| 1101 |
" Spare Devices : 0\n" |
| 1102 |
"\n" |
| 1103 |
" Name : mirwiz:1 (local to host mirwiz)\n" |
| 1104 |
" UUID : 6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 1105 |
" Events : 41\n" |
| 1106 |
"\n" |
| 1107 |
" Number Major Minor RaidDevice State\n" |
| 1108 |
" 0 8 50 0 active sync /dev/sdd2\n" |
| 1109 |
" 2 8 80 1 active sync /dev/sdf\n" |
| 1110 |
"\n" |
| 1111 |
" 1 8 64 - faulty /dev/sde</computeroutput>" |
| 1112 |
|
| 1113 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1114 |
msgid "Here again, the kernel automatically triggers a reconstruction phase during which the volume, although still accessible, is in a degraded mode. Once the reconstruction is over, the RAID array is back to a normal state. One can then tell the system that the <filename>sde</filename> disk is about to be removed from the array, so as to end up with a classical RAID mirror on two disks:" |
| 1115 |
msgstr "繰り返しになりますが、ボリュームはまだアクセスすることが可能とは言うもののボリュームが信頼性低下状態ならば、カーネルは自動的に再構成作業を実行します。再構成作業が終了したら、RAID アレイは正常状態に戻ります。ここで、システムに <filename>sde</filename> ディスクをアレイから削除することを伝えることが可能です。削除することで、2 台のディスクからなる古典的な RAID ミラーになります。" |
| 1116 |
|
| 1117 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1118 |
# Tag: L-CFMD; |
| 1119 |
#, fuzzy |
| 1120 |
#| msgid "" |
| 1121 |
#| "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --remove /dev/sde</userinput>\n" |
| 1122 |
#| "<computeroutput>mdadm: hot removed /dev/sde from /dev/md1\n" |
| 1123 |
#| "# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 1124 |
#| "<computeroutput>/dev/md1:\n" |
| 1125 |
#| "[...]\n" |
| 1126 |
#| " Number Major Minor RaidDevice State\n" |
| 1127 |
#| " 0 8 50 0 active sync /dev/sdd2\n" |
| 1128 |
#| " 2 8 80 1 active sync /dev/sdf</computeroutput>" |
| 1129 |
msgid "" |
| 1130 |
"<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --remove /dev/sde\n" |
| 1131 |
"</userinput><computeroutput>mdadm: hot removed /dev/sde from /dev/md1\n" |
| 1132 |
"# </computeroutput><userinput>mdadm --detail /dev/md1\n" |
| 1133 |
"</userinput><computeroutput>/dev/md1:\n" |
| 1134 |
"[...]\n" |
| 1135 |
" Number Major Minor RaidDevice State\n" |
| 1136 |
" 0 8 34 0 active sync /dev/sdd2\n" |
| 1137 |
" 2 8 64 1 active sync /dev/sdf\n" |
| 1138 |
"</computeroutput>" |
| 1139 |
msgstr "" |
| 1140 |
"<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --remove /dev/sde</userinput>\n" |
| 1141 |
"<computeroutput>mdadm: hot removed /dev/sde from /dev/md1\n" |
| 1142 |
"# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n" |
| 1143 |
"<computeroutput>/dev/md1:\n" |
| 1144 |
"[...]\n" |
| 1145 |
" Number Major Minor RaidDevice State\n" |
| 1146 |
" 0 8 50 0 active sync /dev/sdd2\n" |
| 1147 |
" 2 8 80 1 active sync /dev/sdf</computeroutput>" |
| 1148 |
|
| 1149 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1150 |
msgid "From then on, the drive can be physically removed when the server is next switched off, or even hot-removed when the hardware configuration allows hot-swap. Such configurations include some SCSI controllers, most SATA disks, and external drives operating on USB or Firewire." |
| 1151 |
msgstr "この後、今後サーバの電源を切った際にドライブを物理的に取り外したり、ハードウェア設定がホットスワップに対応しているならばドライブをホットリムーブすることが可能です。一部の SCSI コントローラ、多くの SATA ディスク、USB や Firewire で接続された外部ドライブなどはホットスワップに対応しています。" |
| 1152 |
|
| 1153 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1154 |
msgid "Backing up the Configuration" |
| 1155 |
msgstr "設定のバックアップ" |
| 1156 |
|
| 1157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1158 |
#, fuzzy |
| 1159 |
#| msgid "Most of the meta-data concerning RAID volumes are saved directly on the disks that make up these arrays, so that the kernel can detect the arrays and their components and assemble them automatically when the system starts up. However, backing up this configuration is encouraged, because this detection isn't fail-proof, and it is only expected that it will fail precisely in sensitive circumstances. In our example, if the <filename>sde</filename> disk failure had been real (instead of simulated) and the system had been restarted without removing this <filename>sde</filename> disk, this disk could start working again due to having been probed during the reboot. The kernel would then have three physical elements, each claiming to contain half of the same RAID volume. Another source of confusion can come when RAID volumes from two servers are consolidated onto one server only. If these arrays were running normally before the disks were moved, the kernel would be able to detect and reassemble the pairs properly; but if the moved disks had been aggregated into an <filename>md1</filename> on the old server, and the new server already has an <filename>md1</filename>, one of the mirrors would be renamed." |
| 1160 |
msgid "Most of the meta-data concerning RAID volumes are saved directly on the disks that make up these arrays, so that the kernel can detect the arrays and their components and assemble them automatically when the system starts up. However, backing up this configuration is encouraged, because this detection isn't fail-proof, and it is only expected that it will fail precisely in sensitive circumstances. In our example, if the <filename>sde</filename> disk failure had been real (instead of simulated) and the system had been restarted without removing this <filename>sde</filename> disk, this disk could start working again due to having been probed during the reboot. The kernel would then have three physical elements, each claiming to contain half of the same RAID volume. In reality this leads to the RAID starting from the individual disks alternately - distributing the data also alternately, depending on which disk started the RAID in degraded mode Another source of confusion can come when RAID volumes from two servers are consolidated onto one server only. If these arrays were running normally before the disks were moved, the kernel would be able to detect and reassemble the pairs properly; but if the moved disks had been aggregated into an <filename>md1</filename> on the old server, and the new server already has an <filename>md1</filename>, one of the mirrors would be renamed." |
| 1161 |
msgstr "RAID ボリュームに関連するメタデータのほとんどはアレイを構成するディスク上に直接保存されています。このため、カーネルはアレイとその構成要素を検出し、システムの起動時に自動的にアレイを組み立てることが可能です。しかしながら、この設定をバックアップすることを推奨します。なぜなら、この検出機構は不注意による間違いを防ぐものではないからです。そして、注意して取り扱うべき状況ではまさに検出機構がうまく働かないことが見込まれます。上の例で、<filename>sde</filename> ディスク障害が本物で (模倣でない)、<filename>sde</filename> ディスクを取り外す前にシステムを再起動した場合、<filename>sde</filename> ディスクは再起動中に検出され、システムに復帰します。カーネルは 3 つの物理ディスクを検出し、それぞれのディスクが同じ RAID ボリュームの片割れであると主張します。さらに別の混乱する状況が考えられます。2 台のサーバで使われていた RAID ボリュームを片方のサーバに集約することを考えてみましょう。ディスクが移動される前、各アレイは正常に実行されていました。カーネルはアレイを検出して、適切なペアを組み立てることが可能です。しかし、片方のサーバに移動されたディスクが前のサーバでは <filename>md1</filename> に組み込まれており、さらに新しいサーバが既に <filename>md1</filename> という名前のアレイを持っていた場合、どちらか一方の名前が変えられます。" |
| 1162 |
|
| 1163 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1164 |
msgid "Backing up the configuration is therefore important, if only for reference. The standard way to do it is by editing the <filename>/etc/mdadm/mdadm.conf</filename> file, an example of which is listed here:" |
| 1165 |
msgstr "このため、参考情報に過ぎないとは言うものの、設定を保存することは重要です。設定を保存する標準的な方法は <filename>/etc/mdadm/mdadm.conf</filename> ファイルを編集することです。以下に例を示します。" |
| 1166 |
|
| 1167 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1168 |
#, fuzzy |
| 1169 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1170 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/mdadm/mdadm.conf</filename></secondary>" |
| 1171 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1172 |
|
| 1173 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1174 |
msgid "<command>mdadm</command> configuration file" |
| 1175 |
msgstr "<command>mdadm</command> 設定ファイル" |
| 1176 |
|
| 1177 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1178 |
# Tag: L-CFMD; |
| 1179 |
# Ref: $ man 5 mdadm.conf; |
| 1180 |
# Ref: $ man 1 madam; |
| 1181 |
#, fuzzy |
| 1182 |
#| msgid "" |
| 1183 |
#| "# mdadm.conf\n" |
| 1184 |
#| "#\n" |
| 1185 |
#| "# Please refer to mdadm.conf(5) for information about this file.\n" |
| 1186 |
#| "#\n" |
| 1187 |
#| "\n" |
| 1188 |
#| "# by default (built-in), scan all partitions (/proc/partitions) and all\n" |
| 1189 |
#| "# containers for MD superblocks. alternatively, specify devices to scan, using\n" |
| 1190 |
#| "# wildcards if desired.\n" |
| 1191 |
#| "DEVICE /dev/sd*\n" |
| 1192 |
#| "\n" |
| 1193 |
#| "# auto-create devices with Debian standard permissions\n" |
| 1194 |
#| "CREATE owner=root group=disk mode=0660 auto=yes\n" |
| 1195 |
#| "\n" |
| 1196 |
#| "# automatically tag new arrays as belonging to the local system\n" |
| 1197 |
#| "HOMEHOST <system>\n" |
| 1198 |
#| "\n" |
| 1199 |
#| "# instruct the monitoring daemon where to send mail alerts\n" |
| 1200 |
#| "MAILADDR root\n" |
| 1201 |
#| "\n" |
| 1202 |
#| "# definitions of existing MD arrays\n" |
| 1203 |
#| "ARRAY /dev/md0 metadata=1.2 name=mirwiz:0 UUID=bb085b35:28e821bd:20d697c9:650152bb\n" |
| 1204 |
#| "ARRAY /dev/md1 metadata=1.2 name=mirwiz:1 UUID=6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 1205 |
#| "\n" |
| 1206 |
#| "# This configuration was auto-generated on Thu, 17 Jan 2013 16:21:01 +0100\n" |
| 1207 |
#| "# by mkconf 3.2.5-3" |
| 1208 |
msgid "" |
| 1209 |
"<![CDATA[# mdadm.conf\n" |
| 1210 |
"#\n" |
| 1211 |
"# !NB! Run update-initramfs -u after updating this file.\n" |
| 1212 |
"# !NB! This will ensure that initramfs has an uptodate copy.\n" |
| 1213 |
"#\n" |
| 1214 |
"# Please refer to mdadm.conf(5) for information about this file.\n" |
| 1215 |
"#\n" |
| 1216 |
"\n" |
| 1217 |
"# by default (built-in), scan all partitions (/proc/partitions) and all\n" |
| 1218 |
"# containers for MD superblocks. alternatively, specify devices to scan, using\n" |
| 1219 |
"# wildcards if desired.\n" |
| 1220 |
"DEVICE /dev/sd*\n" |
| 1221 |
"\n" |
| 1222 |
"# automatically tag new arrays as belonging to the local system\n" |
| 1223 |
"HOMEHOST <system>\n" |
| 1224 |
"\n" |
| 1225 |
"# instruct the monitoring daemon where to send mail alerts\n" |
| 1226 |
"MAILADDR root\n" |
| 1227 |
"\n" |
| 1228 |
"# definitions of existing MD arrays\n" |
| 1229 |
"ARRAY /dev/md/0 metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\n" |
| 1230 |
"ARRAY /dev/md/1 metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n" |
| 1231 |
"# This configuration was auto-generated on Mon, 28 Feb 2022 01:53:48 +0100 by mkconf\n" |
| 1232 |
"]]>" |
| 1233 |
msgstr "" |
| 1234 |
"# mdadm.conf\n" |
| 1235 |
"#\n" |
| 1236 |
"# このファイルに関する詳細は mdadm.conf(5) を参照してください。\n" |
| 1237 |
"#\n" |
| 1238 |
"\n" |
| 1239 |
"# デフォルト (組み込み) 状態ならば、MD スーパーブロックを持つパーティション\n" |
| 1240 |
"# (/proc/partitions) とコンテナをすべてスキャンします。以下のようにスキャンする\n" |
| 1241 |
"# デバイスを指定することも可能です。必要ならばワイルドカードを使ってください。\n" |
| 1242 |
"DEVICE /dev/sd*\n" |
| 1243 |
"\n" |
| 1244 |
"# デバイスの自動作成時に使う Debian の標準的なパーミッションを指定します\n" |
| 1245 |
"CREATE owner=root group=disk mode=0660 auto=yes\n" |
| 1246 |
"\n" |
| 1247 |
"# 新規アレイの所属先にローカルシステムを自動登録します\n" |
| 1248 |
"HOMEHOST <system>\n" |
| 1249 |
"\n" |
| 1250 |
"# 監視デーモンに root を警告メールの送信先として通知します\n" |
| 1251 |
"MAILADDR root\n" |
| 1252 |
"\n" |
| 1253 |
"# 既存の MD アレイの定義\n" |
| 1254 |
"ARRAY /dev/md0 metadata=1.2 name=mirwiz:0 UUID=bb085b35:28e821bd:20d697c9:650152bb\n" |
| 1255 |
"ARRAY /dev/md1 metadata=1.2 name=mirwiz:1 UUID=6ec558ca:0c2c04a0:19bca283:95f67464\n" |
| 1256 |
"\n" |
| 1257 |
"# この設定ファイルは mkconf 3.2.5-3 により\n" |
| 1258 |
"# Fri, 18 Jan 2013 00:21:01 +0900 に自動生成されました" |
| 1259 |
|
| 1260 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1261 |
msgid "One of the most useful details is the <literal>DEVICE</literal> option, which lists the devices where the system will automatically look for components of RAID volumes at start-up time. In our example, we replaced the default value, <literal>partitions containers</literal>, with an explicit list of device files, since we chose to use entire disks and not only partitions, for some volumes." |
| 1262 |
msgstr "最も役に立つ設定項目の 1 つに <literal>DEVICE</literal> オプションがあります。これは起動時にシステムが RAID ボリュームの構成情報を自動的に探すデバイスをリストします。上の例では、値をデフォルト値 <literal>partitions containers</literal> からデバイスファイルを明示したリストに置き換えました。なぜなら、パーティションだけでなくすべてのディスクをボリュームとして使うように決めたからです。" |
| 1263 |
|
| 1264 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1265 |
msgid "The last two lines in our example are those allowing the kernel to safely pick which volume number to assign to which array. The metadata stored on the disks themselves are enough to re-assemble the volumes, but not to determine the volume number (and the matching <filename>/dev/md*</filename> device name)." |
| 1266 |
msgstr "上の例における最後の 2 行を使うことで、カーネルはアレイに割り当てるボリューム番号を安全に選ぶことが可能です。ディスク本体に保存されたメタ情報はボリュームをもう一度組み上げるのに十分ですが、ボリューム番号を定義する (そして <filename>/dev/md*</filename> デバイス名にマッチすることを確認する) には不十分です。" |
| 1267 |
|
| 1268 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1269 |
msgid "Fortunately, these lines can be generated automatically:" |
| 1270 |
msgstr "幸いなことに、以下のコマンドを実行すればこの行を自動的に生成することが可能です。" |
| 1271 |
|
| 1272 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1273 |
#, fuzzy |
| 1274 |
#| msgid "" |
| 1275 |
#| "<computeroutput># </computeroutput><userinput>mdadm --misc --detail --brief /dev/md?</userinput>\n" |
| 1276 |
#| "<computeroutput>ARRAY /dev/md0 metadata=1.2 name=mirwiz:0 UUID=bb085b35:28e821bd:20d697c9:650152bb\n" |
| 1277 |
#| "ARRAY /dev/md1 metadata=1.2 name=mirwiz:1 UUID=6ec558ca:0c2c04a0:19bca283:95f67464</computeroutput>" |
| 1278 |
msgid "" |
| 1279 |
"<computeroutput># </computeroutput><userinput>mdadm --misc --detail --brief /dev/md?\n" |
| 1280 |
"</userinput><computeroutput>ARRAY /dev/md/0 metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\n" |
| 1281 |
"ARRAY /dev/md/1 metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n" |
| 1282 |
"</computeroutput>" |
| 1283 |
msgstr "" |
| 1284 |
"<computeroutput># </computeroutput><userinput>mdadm --misc --detail --brief /dev/md?</userinput>\n" |
| 1285 |
"<computeroutput>ARRAY /dev/md0 metadata=1.2 name=mirwiz:0 UUID=bb085b35:28e821bd:20d697c9:650152bb\n" |
| 1286 |
"ARRAY /dev/md1 metadata=1.2 name=mirwiz:1 UUID=6ec558ca:0c2c04a0:19bca283:95f67464</computeroutput>" |
| 1287 |
|
| 1288 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1289 |
msgid "The contents of these last two lines doesn't depend on the list of disks included in the volume. It is therefore not necessary to regenerate these lines when replacing a failed disk with a new one. On the other hand, care must be taken to update the file when creating or deleting a RAID array." |
| 1290 |
msgstr "最後の 2 行の内容はボリュームを構成するディスクのリストに依存しません。このため、障害の発生したディスクを新しいディスクに交換した際に、これをもう一度生成する必要はありません。逆に、RAID アレイを作成および削除した際に、必ずこの設定ファイルを注意深く更新する必要があります。" |
| 1291 |
|
| 1292 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1293 |
msgid "LVM, the <emphasis>Logical Volume Manager</emphasis>, is another approach to abstracting logical volumes from their physical supports, which focuses on increasing flexibility rather than increasing reliability. LVM allows changing a logical volume transparently as far as the applications are concerned; for instance, it is possible to add new disks, migrate the data to them, and remove the old disks, without unmounting the volume." |
| 1294 |
msgstr "LVM (<emphasis>論理ボリュームマネージャ</emphasis>) は物理ディスクから論理ボリュームを抽象化するもう一つの方法で、信頼性を増加させるのではなく柔軟性を増加させることに注目しています。LVM を使うことで、アプリケーションから見る限り透過的に論理ボリュームを変更することが可能です。LVM を使うことで、たとえば新しいディスクを追加し、データを新しいディスクに移行し、古いディスクを削除することがボリュームをアンマウントせずに可能です。" |
| 1295 |
|
| 1296 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1297 |
msgid "LVM Concepts" |
| 1298 |
msgstr "LVM の概念" |
| 1299 |
|
| 1300 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1301 |
#, fuzzy |
| 1302 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1303 |
msgid "<primary>LVM</primary><secondary>concept</secondary>" |
| 1304 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1305 |
|
| 1306 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1307 |
#, fuzzy |
| 1308 |
#| msgid "<primary>LVM</primary>" |
| 1309 |
msgid "<primary>PV</primary>" |
| 1310 |
msgstr "<primary>LVM</primary>" |
| 1311 |
|
| 1312 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1313 |
#, fuzzy |
| 1314 |
#| msgid "<primary>Logical Volume Manager</primary>" |
| 1315 |
msgid "<primary>Physical Volume</primary><see>PV</see>" |
| 1316 |
msgstr "<primary sortas=\"ロンリボリュームマネージャ\">論理ボリュームマネージャ</primary>" |
| 1317 |
|
| 1318 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1319 |
msgid "This flexibility is attained by a level of abstraction involving three concepts." |
| 1320 |
msgstr "LVM の柔軟性は 3 つの概念から構成された抽象化レベルによって達成されます。" |
| 1321 |
|
| 1322 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1323 |
msgid "First, the PV (<emphasis>Physical Volume</emphasis>) is the entity closest to the hardware: it can be partitions on a disk, or a full disk, or even any other block device (including, for instance, a RAID array). Note that when a physical element is set up to be a PV for LVM, it should only be accessed via LVM, otherwise the system will get confused." |
| 1324 |
msgstr "1 番目の概念は PV (<emphasis>物理ボリューム</emphasis>) です。PV はハードウェアに最も近い要素です。具体的に言えば、PV はディスクのパーティション、ディスク全体、その他の任意のブロックデバイス (たとえば、RAID アレイ) などの物理的要素を指します。物理的要素を LVM の PV に設定した場合、物理的要素へのアクセスは必ず LVM を介すべきという点に注意してください。そうでなければ、システムが混乱します。" |
| 1325 |
|
| 1326 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1327 |
#, fuzzy |
| 1328 |
#| msgid "<primary>LVM</primary>" |
| 1329 |
msgid "<primary>VG</primary>" |
| 1330 |
msgstr "<primary>LVM</primary>" |
| 1331 |
|
| 1332 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1333 |
#, fuzzy |
| 1334 |
#| msgid "<primary>Logical Volume Manager</primary>" |
| 1335 |
msgid "<primary>Volume Group</primary><see>VG</see>" |
| 1336 |
msgstr "<primary sortas=\"ロンリボリュームマネージャ\">論理ボリュームマネージャ</primary>" |
| 1337 |
|
| 1338 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1339 |
#, fuzzy |
| 1340 |
#| msgid "A number of PVs can be clustered in a VG (<emphasis>Volume Group</emphasis>), which can be compared to disks both virtual and extensible. VGs are abstract, and don't appear in a device file in the <filename>/dev</filename> hierarchy, so there's no risk of using them directly." |
| 1341 |
msgid "A number of PVs can be clustered in a VG (<emphasis>Volume Group</emphasis>), which can be compared to disks both virtual and extensible. VGs are abstract, and don't appear in a device file in the <filename>/dev</filename> hierarchy, so there is no risk of using them directly." |
| 1342 |
msgstr "2 番目の概念は VG (<emphasis>ボリュームグループ</emphasis>) です。複数の PV は VG にクラスタ化することが可能です。VG は仮想的かつ拡張できるディスクに例えられます。VG は概念的な要素で、<filename>/dev</filename> 階層のデバイスファイルに現れません。そのため、VG を直接的に操作する危険はありません。" |
| 1343 |
|
| 1344 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1345 |
#, fuzzy |
| 1346 |
#| msgid "<primary>LVM</primary>" |
| 1347 |
msgid "<primary>LV</primary>" |
| 1348 |
msgstr "<primary>LVM</primary>" |
| 1349 |
|
| 1350 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1351 |
#, fuzzy |
| 1352 |
#| msgid "<primary>Logical Volume Manager</primary>" |
| 1353 |
msgid "<primary>Logical Volume</primary><see>LV</see>" |
| 1354 |
msgstr "<primary sortas=\"ロンリボリュームマネージャ\">論理ボリュームマネージャ</primary>" |
| 1355 |
|
| 1356 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1357 |
msgid "The third kind of object is the LV (<emphasis>Logical Volume</emphasis>), which is a chunk of a VG; if we keep the VG-as-disk analogy, the LV compares to a partition. The LV appears as a block device with an entry in <filename>/dev</filename>, and it can be used as any other physical partition can be (most commonly, to host a filesystem or swap space)." |
| 1358 |
msgstr "3 番目の概念は LV (<emphasis>論理ボリューム</emphasis>) です。LV は VG の中の 1 つの塊です。さらに VG をディスクに例えたのと同様の考え方を使うと、LV はパーティションに例えられます。LV はブロックデバイスとして <filename>/dev</filename> に現れ、他の物理パーティションと同様に取り扱うことが可能です (一般的に言えば、LV にファイルシステムやスワップ領域を作成することが可能です)。" |
| 1359 |
|
| 1360 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1361 |
msgid "The important thing is that the splitting of a VG into LVs is entirely independent of its physical components (the PVs). A VG with only a single physical component (a disk for instance) can be split into a dozen logical volumes; similarly, a VG can use several physical disks and appear as a single large logical volume. The only constraint, obviously, is that the total size allocated to LVs can't be bigger than the total capacity of the PVs in the volume group." |
| 1362 |
msgstr "ここで重要な事柄は VG を LV に分割する場合に物理的要素 (PV) はいかなる制約も要求しないという点です。1 つの PV (たとえばディスク) から構成される VG を複数の LV に分割できます。同様に、複数の PV から構成される VG を 1 つの大きな LV として提供することも可能です。制約事項がたった 1 つしかないのは明らかです。それはある VG から分割された LV のサイズの合計はその VG を構成する PV のサイズの合計を超えることができないという点です。" |
| 1363 |
|
| 1364 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1365 |
# Tag: PTAL; |
| 1366 |
msgid "It often makes sense, however, to have some kind of homogeneity among the physical components of a VG, and to split the VG into logical volumes that will have similar usage patterns. For instance, if the available hardware includes fast disks and slower disks, the fast ones could be clustered into one VG and the slower ones into another; chunks of the first one can then be assigned to applications requiring fast data access, while the second one will be kept for less demanding tasks." |
| 1367 |
msgstr "しかしながら、ある VG を構成する PV 同士の性能を同様のものにしたり、その VG から分割された LV 同士に求められる性能を同様のものにしたりすることは通常理に適った方針です。たとえば、利用できるハードウェアに高速な PV と低速な PV がある場合、高速な PV から構成される VG と低速な PV から構成される VG に分けると良いでしょう。こうすることで、高速な PV から構成される VG から分割された LV を高速なデータアクセスを必要とするアプリケーションに割り当て、低速な PV から構成される VG から分割された LV を負荷の少ない作業用に割り当てることが可能です。" |
| 1368 |
|
| 1369 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1370 |
# Tag: PTAL; |
| 1371 |
msgid "In any case, keep in mind that an LV isn't particularly attached to any one PV. It is possible to influence where the data from an LV are physically stored, but this possibility isn't required for day-to-day use. On the contrary: when the set of physical components of a VG evolves, the physical storage locations corresponding to a particular LV can be migrated across disks (while staying within the PVs assigned to the VG, of course)." |
| 1372 |
msgstr "いかなる場合でも、LV は特定の PV を使用するわけではないという点を覚えておいてください。ある LV に含まれるデータの物理的な保存場所を操作することも可能ですが、普通に使っている限りその必要はありません。逆に、VG を構成する PV 群の構成要素が変化した場合、ある LV に含まれるデータの物理的な保存場所は対象の LV の分割元である VG の中ひいてはその VG を構成する PV 群の構成要素の中を移動することがあります (もちろん、データの移動先は対象の LV の分割元の VG を構成する PV 群の構成要素の中に限られます)。" |
| 1373 |
|
| 1374 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1375 |
msgid "Setting up LVM" |
| 1376 |
msgstr "LVM の設定" |
| 1377 |
|
| 1378 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1379 |
#, fuzzy |
| 1380 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1381 |
msgid "<primary>LVM</primary><secondary>setup</secondary>" |
| 1382 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1383 |
|
| 1384 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1385 |
msgid "Let us now follow, step by step, the process of setting up LVM for a typical use case: we want to simplify a complex storage situation. Such a situation usually happens after some long and convoluted history of accumulated temporary measures. For the purposes of illustration, we'll consider a server where the storage needs have changed over time, ending up in a maze of available partitions split over several partially used disks. In more concrete terms, the following partitions are available:" |
| 1386 |
msgstr "典型的な用途に対する LVM の設定過程を、段階的に見て行きましょう。具体的に言えば、複雑なストレージの状況を単純化したい場合を見ていきます。通常、長く複雑な一時的措置を繰り返した挙句の果てに、この状況に陥ることがあります。説明目的で、徐々にストレージを変更する必要のあったサーバを考えます。このサーバでは、PV として利用できるパーティションが複数の一部使用済みディスクに分散しています。より具体的に言えば、以下のパーティションを PV として利用できます。" |
| 1387 |
|
| 1388 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1389 |
msgid "on the <filename>sdb</filename> disk, a <filename>sdb2</filename> partition, 4 GB;" |
| 1390 |
msgstr "<filename>sdb</filename> ディスク上の <filename>sdb2</filename> パーティション (4 GB)。" |
| 1391 |
|
| 1392 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1393 |
msgid "on the <filename>sdc</filename> disk, a <filename>sdc3</filename> partition, 3 GB;" |
| 1394 |
msgstr "<filename>sdc</filename> ディスク上の <filename>sdc3</filename> パーティション (3 GB)。" |
| 1395 |
|
| 1396 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1397 |
msgid "the <filename>sdd</filename> disk, 4 GB, is fully available;" |
| 1398 |
msgstr "<filename>sdd</filename> ディスク (4 GB) は全領域を利用できます。" |
| 1399 |
|
| 1400 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1401 |
msgid "on the <filename>sdf</filename> disk, a <filename>sdf1</filename> partition, 4 GB; and a <filename>sdf2</filename> partition, 5 GB." |
| 1402 |
msgstr "<filename>sdf</filename> ディスク上の <filename>sdf1</filename> パーティション (4 GB) および <filename>sdf2</filename> パーティション (5 GB)。" |
| 1403 |
|
| 1404 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1405 |
msgid "In addition, let's assume that disks <filename>sdb</filename> and <filename>sdf</filename> are faster than the other two." |
| 1406 |
msgstr "加えて、<filename>sdb</filename> と <filename>sdf</filename> が他の 2 台に比べて高速であると仮定しましょう。" |
| 1407 |
|
| 1408 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1409 |
# Tag: PTAL; |
| 1410 |
msgid "Our goal is to set up three logical volumes for three different applications: a file server requiring 5 GB of storage space, a database (1 GB) and some space for back-ups (12 GB). The first two need good performance, but back-ups are less critical in terms of access speed. All these constraints prevent the use of partitions on their own; using LVM can abstract the physical size of the devices, so the only limit is the total available space." |
| 1411 |
msgstr "今回の目標は、3 種類の異なるアプリケーション用に 3 つの LV を設定することです。具体的に言えば、5 GB のストレージ領域が必要なファイルサーバ、データベース (1 GB)、バックアップ用の領域 (12 GB) 用の LV を設定することです。ファイルサーバとデータベースは高い性能を必要とします。しかし、バックアップはアクセス速度をそれほど重要視しません。これらの要件により、各アプリケーションに設定する LV の使用する PV が決定されます。さらに LVM を使いますので、PV の物理的サイズからくる制限はありません。このため、PV 群として利用できる領域のサイズの合計だけが制限となります。" |
| 1412 |
|
| 1413 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1414 |
#, fuzzy |
| 1415 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 1416 |
msgid "<primary><emphasis role=\"pkg\">lvm2</emphasis></primary>" |
| 1417 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 1418 |
|
| 1419 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1420 |
#, fuzzy |
| 1421 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1422 |
msgid "<primary>LVM</primary><secondary>create PV</secondary>" |
| 1423 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1424 |
|
| 1425 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1426 |
msgid "The required tools are in the <emphasis role=\"pkg\">lvm2</emphasis> package and its dependencies. When they're installed, setting up LVM takes three steps, matching the three levels of concepts." |
| 1427 |
msgstr "LVM の設定に必要なツールは <emphasis role=\"pkg\">lvm2</emphasis> パッケージとその依存パッケージに含まれています。これらのパッケージをインストールしたら、3 つの手順を踏んで LVM を設定します。各手順は LVM の概念の 3 つの抽象化レベルに対応します。" |
| 1428 |
|
| 1429 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1430 |
msgid "First, we prepare the physical volumes using <command>pvcreate</command>:" |
| 1431 |
msgstr "最初に、<command>pvcreate</command> を使って PV を作成します。" |
| 1432 |
|
| 1433 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1434 |
#, fuzzy |
| 1435 |
#| msgid "<primary><command>xe</command></primary>" |
| 1436 |
msgid "<primary><command>pvcreate</command></primary>" |
| 1437 |
msgstr "<primary><command>xe</command></primary>" |
| 1438 |
|
| 1439 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1440 |
# Tag: L-CFMD; |
| 1441 |
#, fuzzy |
| 1442 |
#| msgid "<primary><command>virsh</command></primary>" |
| 1443 |
msgid "<primary><command>pvdisplay</command></primary>" |
| 1444 |
msgstr "<primary><command>virsh</command></primary>" |
| 1445 |
|
| 1446 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1447 |
# Tag: L-CFMD; |
| 1448 |
#, fuzzy |
| 1449 |
#| msgid "" |
| 1450 |
#| "<computeroutput># </computeroutput><userinput>pvdisplay</userinput>\n" |
| 1451 |
#| "<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb2</userinput>\n" |
| 1452 |
#| "<computeroutput> Physical volume \"/dev/sdb2\" successfully created\n" |
| 1453 |
#| "# </computeroutput><userinput>pvdisplay</userinput>\n" |
| 1454 |
#| "<computeroutput> \"/dev/sdb2\" is a new physical volume of \"4.00 GiB\"\n" |
| 1455 |
#| " --- NEW Physical volume ---\n" |
| 1456 |
#| " PV Name /dev/sdb2\n" |
| 1457 |
#| " VG Name \n" |
| 1458 |
#| " PV Size 4.00 GiB\n" |
| 1459 |
#| " Allocatable NO\n" |
| 1460 |
#| " PE Size 0 \n" |
| 1461 |
#| " Total PE 0\n" |
| 1462 |
#| " Free PE 0\n" |
| 1463 |
#| " Allocated PE 0\n" |
| 1464 |
#| " PV UUID 0zuiQQ-j1Oe-P593-4tsN-9FGy-TY0d-Quz31I\n" |
| 1465 |
#| "\n" |
| 1466 |
#| "# </computeroutput><userinput>for i in sdc3 sdd sdf1 sdf2 ; do pvcreate /dev/$i ; done</userinput>\n" |
| 1467 |
#| "<computeroutput> Physical volume \"/dev/sdc3\" successfully created\n" |
| 1468 |
#| " Physical volume \"/dev/sdd\" successfully created\n" |
| 1469 |
#| " Physical volume \"/dev/sdf1\" successfully created\n" |
| 1470 |
#| " Physical volume \"/dev/sdf2\" successfully created\n" |
| 1471 |
#| "# </computeroutput><userinput>pvdisplay -C</userinput>\n" |
| 1472 |
#| "<computeroutput> PV VG Fmt Attr PSize PFree\n" |
| 1473 |
#| " /dev/sdb2 lvm2 --- 4.00g 4.00g\n" |
| 1474 |
#| " /dev/sdc3 lvm2 --- 3.09g 3.09g\n" |
| 1475 |
#| " /dev/sdd lvm2 --- 4.00g 4.00g\n" |
| 1476 |
#| " /dev/sdf1 lvm2 --- 4.10g 4.10g\n" |
| 1477 |
#| " /dev/sdf2 lvm2 --- 5.22g 5.22g\n" |
| 1478 |
#| "</computeroutput>" |
| 1479 |
msgid "" |
| 1480 |
"<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb2\n" |
| 1481 |
"</userinput><computeroutput> Physical volume \"/dev/sdb2\" successfully created.\n" |
| 1482 |
"# </computeroutput><userinput>pvdisplay\n" |
| 1483 |
"</userinput><computeroutput> \"/dev/sdb2\" is a new physical volume of \"4.00 GiB\"\n" |
| 1484 |
" --- NEW Physical volume ---\n" |
| 1485 |
" PV Name /dev/sdb2\n" |
| 1486 |
" VG Name \n" |
| 1487 |
" PV Size 4.00 GiB\n" |
| 1488 |
" Allocatable NO\n" |
| 1489 |
" PE Size 0 \n" |
| 1490 |
" Total PE 0\n" |
| 1491 |
" Free PE 0\n" |
| 1492 |
" Allocated PE 0\n" |
| 1493 |
" PV UUID yK0K6K-clbc-wt6e-qk9o-aUh9-oQqC-k1T71B\n" |
| 1494 |
"\n" |
| 1495 |
"# </computeroutput><userinput>for i in sdc3 sdd sdf1 sdf2 ; do pvcreate /dev/$i ; done\n" |
| 1496 |
"</userinput><computeroutput> Physical volume \"/dev/sdc3\" successfully created.\n" |
| 1497 |
" Physical volume \"/dev/sdd\" successfully created.\n" |
| 1498 |
" Physical volume \"/dev/sdf1\" successfully created.\n" |
| 1499 |
" Physical volume \"/dev/sdf2\" successfully created.\n" |
| 1500 |
"# </computeroutput><userinput>pvdisplay -C\n" |
| 1501 |
"</userinput><computeroutput> PV VG Fmt Attr PSize PFree\n" |
| 1502 |
" /dev/sdb2 lvm2 --- 4.00g 4.00g\n" |
| 1503 |
" /dev/sdc3 lvm2 --- 3.00g 3.00g\n" |
| 1504 |
" /dev/sdd lvm2 --- 4.00g 4.00g\n" |
| 1505 |
" /dev/sdf1 lvm2 --- 4.00g 4.00g\n" |
| 1506 |
" /dev/sdf2 lvm2 --- 5.00g 5.00g\n" |
| 1507 |
"</computeroutput>" |
| 1508 |
msgstr "" |
| 1509 |
"<computeroutput># </computeroutput><userinput>pvdisplay</userinput>\n" |
| 1510 |
"<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb2</userinput>\n" |
| 1511 |
"<computeroutput> Physical volume \"/dev/sdb2\" successfully created\n" |
| 1512 |
"# </computeroutput><userinput>pvdisplay</userinput>\n" |
| 1513 |
"<computeroutput> \"/dev/sdb2\" is a new physical volume of \"4.00 GiB\"\n" |
| 1514 |
" --- NEW Physical volume ---\n" |
| 1515 |
" PV Name /dev/sdb2\n" |
| 1516 |
" VG Name \n" |
| 1517 |
" PV Size 4.00 GiB\n" |
| 1518 |
" Allocatable NO\n" |
| 1519 |
" PE Size 0 \n" |
| 1520 |
" Total PE 0\n" |
| 1521 |
" Free PE 0\n" |
| 1522 |
" Allocated PE 0\n" |
| 1523 |
" PV UUID 0zuiQQ-j1Oe-P593-4tsN-9FGy-TY0d-Quz31I\n" |
| 1524 |
"\n" |
| 1525 |
"# </computeroutput><userinput>for i in sdc3 sdd sdf1 sdf2 ; do pvcreate /dev/$i ; done</userinput>\n" |
| 1526 |
"<computeroutput> Physical volume \"/dev/sdc3\" successfully created\n" |
| 1527 |
" Physical volume \"/dev/sdd\" successfully created\n" |
| 1528 |
" Physical volume \"/dev/sdf1\" successfully created\n" |
| 1529 |
" Physical volume \"/dev/sdf2\" successfully created\n" |
| 1530 |
"# </computeroutput><userinput>pvdisplay -C</userinput>\n" |
| 1531 |
"<computeroutput> PV VG Fmt Attr PSize PFree\n" |
| 1532 |
" /dev/sdb2 lvm2 --- 4.00g 4.00g\n" |
| 1533 |
" /dev/sdc3 lvm2 --- 3.09g 3.09g\n" |
| 1534 |
" /dev/sdd lvm2 --- 4.00g 4.00g\n" |
| 1535 |
" /dev/sdf1 lvm2 --- 4.10g 4.10g\n" |
| 1536 |
" /dev/sdf2 lvm2 --- 5.22g 5.22g\n" |
| 1537 |
"</computeroutput>" |
| 1538 |
|
| 1539 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1540 |
# Tag: L-CFMD; |
| 1541 |
msgid "So far, so good; note that a PV can be set up on a full disk as well as on individual partitions of it. As shown above, the <command>pvdisplay</command> command lists the existing PVs, with two possible output formats." |
| 1542 |
msgstr "ここまでは順調です。PV はディスク全体およびディスク上の各パーティションに対して設定することが可能という点に注意してください。上に示した通り、<command>pvdisplay</command> コマンドは既存の PV をリストします。出力フォーマットは 2 種類あります。" |
| 1543 |
|
| 1544 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1545 |
#, fuzzy |
| 1546 |
#| msgid "<primary><command>xe</command></primary>" |
| 1547 |
msgid "<primary><command>vgcreate</command></primary>" |
| 1548 |
msgstr "<primary><command>xe</command></primary>" |
| 1549 |
|
| 1550 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1551 |
# Tag: L-CFMD; |
| 1552 |
#, fuzzy |
| 1553 |
#| msgid "<primary><command>virsh</command></primary>" |
| 1554 |
msgid "<primary><command>vgdisplay</command></primary>" |
| 1555 |
msgstr "<primary><command>virsh</command></primary>" |
| 1556 |
|
| 1557 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1558 |
# Tag: L-CFMD; |
| 1559 |
msgid "Now let's assemble these physical elements into VGs using <command>vgcreate</command>. We'll gather only PVs from the fast disks into a <filename>vg_critical</filename> VG; the other VG, <filename>vg_normal</filename>, will also include slower elements." |
| 1560 |
msgstr "<command>vgcreate</command> を使って、これらの PV から VG を構成しましょう。高速なディスクの PV から <filename>vg_critical</filename> VG を構成します。さらに、これ以外の低速なディスクの PV から <filename>vg_normal</filename> VG を構成します。" |
| 1561 |
|
| 1562 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1563 |
#, fuzzy |
| 1564 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1565 |
msgid "<primary>LVM</primary><secondary>create VG</secondary>" |
| 1566 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1567 |
|
| 1568 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1569 |
# Tag: L-CFMD; |
| 1570 |
#, fuzzy |
| 1571 |
#| msgid "" |
| 1572 |
#| "<computeroutput># </computeroutput><userinput>vgdisplay</userinput>\n" |
| 1573 |
#| "<computeroutput> No volume groups found\n" |
| 1574 |
#| "# </computeroutput><userinput>vgcreate vg_critical /dev/sdb2 /dev/sdf1</userinput>\n" |
| 1575 |
#| "<computeroutput> Volume group \"vg_critical\" successfully created\n" |
| 1576 |
#| "# </computeroutput><userinput>vgdisplay</userinput>\n" |
| 1577 |
#| "<computeroutput> --- Volume group ---\n" |
| 1578 |
#| " VG Name vg_critical\n" |
| 1579 |
#| " System ID \n" |
| 1580 |
#| " Format lvm2\n" |
| 1581 |
#| " Metadata Areas 2\n" |
| 1582 |
#| " Metadata Sequence No 1\n" |
| 1583 |
#| " VG Access read/write\n" |
| 1584 |
#| " VG Status resizable\n" |
| 1585 |
#| " MAX LV 0\n" |
| 1586 |
#| " Cur LV 0\n" |
| 1587 |
#| " Open LV 0\n" |
| 1588 |
#| " Max PV 0\n" |
| 1589 |
#| " Cur PV 2\n" |
| 1590 |
#| " Act PV 2\n" |
| 1591 |
#| " VG Size 8.09 GiB\n" |
| 1592 |
#| " PE Size 4.00 MiB\n" |
| 1593 |
#| " Total PE 2071\n" |
| 1594 |
#| " Alloc PE / Size 0 / 0 \n" |
| 1595 |
#| " Free PE / Size 2071 / 8.09 GiB\n" |
| 1596 |
#| " VG UUID bpq7zO-PzPD-R7HW-V8eN-c10c-S32h-f6rKqp\n" |
| 1597 |
#| "\n" |
| 1598 |
#| "# </computeroutput><userinput>vgcreate vg_normal /dev/sdc3 /dev/sdd /dev/sdf2</userinput>\n" |
| 1599 |
#| "<computeroutput> Volume group \"vg_normal\" successfully created\n" |
| 1600 |
#| "# </computeroutput><userinput>vgdisplay -C</userinput>\n" |
| 1601 |
#| "<computeroutput> VG #PV #LV #SN Attr VSize VFree \n" |
| 1602 |
#| " vg_critical 2 0 0 wz--n- 8.09g 8.09g\n" |
| 1603 |
#| " vg_normal 3 0 0 wz--n- 12.30g 12.30g\n" |
| 1604 |
#| "</computeroutput>" |
| 1605 |
msgid "" |
| 1606 |
"<computeroutput># </computeroutput><userinput>vgcreate vg_critical /dev/sdb2 /dev/sdf1\n" |
| 1607 |
"</userinput><computeroutput> Volume group \"vg_critical\" successfully created\n" |
| 1608 |
"# </computeroutput><userinput>vgdisplay\n" |
| 1609 |
"</userinput><computeroutput> --- Volume group ---\n" |
| 1610 |
" VG Name vg_critical\n" |
| 1611 |
" System ID \n" |
| 1612 |
" Format lvm2\n" |
| 1613 |
" Metadata Areas 2\n" |
| 1614 |
" Metadata Sequence No 1\n" |
| 1615 |
" VG Access read/write\n" |
| 1616 |
" VG Status resizable\n" |
| 1617 |
" MAX LV 0\n" |
| 1618 |
" Cur LV 0\n" |
| 1619 |
" Open LV 0\n" |
| 1620 |
" Max PV 0\n" |
| 1621 |
" Cur PV 2\n" |
| 1622 |
" Act PV 2\n" |
| 1623 |
" VG Size 7.99 GiB\n" |
| 1624 |
" PE Size 4.00 MiB\n" |
| 1625 |
" Total PE 2046\n" |
| 1626 |
" Alloc PE / Size 0 / 0 \n" |
| 1627 |
" Free PE / Size 2046 / 7.99 GiB\n" |
| 1628 |
" VG UUID JgFWU3-emKg-9QA1-stPj-FkGX-mGFb-4kzy1G\n" |
| 1629 |
"\n" |
| 1630 |
"# </computeroutput><userinput>vgcreate vg_normal /dev/sdc3 /dev/sdd /dev/sdf2\n" |
| 1631 |
"</userinput><computeroutput> Volume group \"vg_normal\" successfully created\n" |
| 1632 |
"# </computeroutput><userinput>vgdisplay -C\n" |
| 1633 |
"</userinput><computeroutput><![CDATA[ VG #PV #LV #SN Attr VSize VFree \n" |
| 1634 |
" vg_critical 2 0 0 wz--n- 7.99g 7.99g\n" |
| 1635 |
" vg_normal 3 0 0 wz--n- <11.99g <11.99g\n" |
| 1636 |
"]]></computeroutput>" |
| 1637 |
msgstr "" |
| 1638 |
"<computeroutput># </computeroutput><userinput>vgdisplay</userinput>\n" |
| 1639 |
"<computeroutput> No volume groups found\n" |
| 1640 |
"# </computeroutput><userinput>vgcreate vg_critical /dev/sdb2 /dev/sdf1</userinput>\n" |
| 1641 |
"<computeroutput> Volume group \"vg_critical\" successfully created\n" |
| 1642 |
"# </computeroutput><userinput>vgdisplay</userinput>\n" |
| 1643 |
"<computeroutput> --- Volume group ---\n" |
| 1644 |
" VG Name vg_critical\n" |
| 1645 |
" System ID \n" |
| 1646 |
" Format lvm2\n" |
| 1647 |
" Metadata Areas 2\n" |
| 1648 |
" Metadata Sequence No 1\n" |
| 1649 |
" VG Access read/write\n" |
| 1650 |
" VG Status resizable\n" |
| 1651 |
" MAX LV 0\n" |
| 1652 |
" Cur LV 0\n" |
| 1653 |
" Open LV 0\n" |
| 1654 |
" Max PV 0\n" |
| 1655 |
" Cur PV 2\n" |
| 1656 |
" Act PV 2\n" |
| 1657 |
" VG Size 8.09 GiB\n" |
| 1658 |
" PE Size 4.00 MiB\n" |
| 1659 |
" Total PE 2071\n" |
| 1660 |
" Alloc PE / Size 0 / 0 \n" |
| 1661 |
" Free PE / Size 2071 / 8.09 GiB\n" |
| 1662 |
" VG UUID bpq7zO-PzPD-R7HW-V8eN-c10c-S32h-f6rKqp\n" |
| 1663 |
"\n" |
| 1664 |
"# </computeroutput><userinput>vgcreate vg_normal /dev/sdc3 /dev/sdd /dev/sdf2</userinput>\n" |
| 1665 |
"<computeroutput> Volume group \"vg_normal\" successfully created\n" |
| 1666 |
"# </computeroutput><userinput>vgdisplay -C</userinput>\n" |
| 1667 |
"<computeroutput> VG #PV #LV #SN Attr VSize VFree \n" |
| 1668 |
" vg_critical 2 0 0 wz--n- 8.09g 8.09g\n" |
| 1669 |
" vg_normal 3 0 0 wz--n- 12.30g 12.30g\n" |
| 1670 |
"</computeroutput>" |
| 1671 |
|
| 1672 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1673 |
# Tag: L-CFMD; |
| 1674 |
msgid "Here again, commands are rather straightforward (and <command>vgdisplay</command> proposes two output formats). Note that it is quite possible to use two partitions of the same physical disk into two different VGs. Note also that we used a <filename>vg_</filename> prefix to name our VGs, but it is nothing more than a convention." |
| 1675 |
msgstr "繰り返しになりますが、<command>vgdisplay</command> コマンドはかなり簡潔です (そして <command>vgdisplay</command> には 2 種類の出力フォーマットがあります)。同じ物理ディスク上にある 2 つの PV から 2 つの異なる VG を構成することが可能である点に注意してください。また、<filename>vg_</filename> 接頭辞を VG の名前に使っていますが、これは慣例に過ぎない点に注意してください。" |
| 1676 |
|
| 1677 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1678 |
# Tag: L-CFMD; |
| 1679 |
#, fuzzy |
| 1680 |
#| msgid "We now have two “virtual disks”, sized about 8 GB and 12 GB, respectively. Let's now carve them up into “virtual partitions” (LVs). This involves the <command>lvcreate</command> command, and a slightly more complex syntax:" |
| 1681 |
msgid "We now have two “virtual disks”, sized about 8 GB and 12 GB respectively. Let's now carve them up into “virtual partitions” (LVs). This involves the <command>lvcreate</command> command, and a slightly more complex syntax:" |
| 1682 |
msgstr "これでサイズが約 8 GB と約 12 GB の 2 台の「仮想ディスク」(VG) を手に入れたことになります。それでは仮想ディスク (VG) を「仮想パーティション」(LV) に分割しましょう。これを行うには <command>lvcreate</command> コマンドを少し複雑な構文で実行します。" |
| 1683 |
|
| 1684 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1685 |
#, fuzzy |
| 1686 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1687 |
msgid "<primary>LVM</primary><secondary>create LV</secondary>" |
| 1688 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1689 |
|
| 1690 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1691 |
#, fuzzy |
| 1692 |
#| msgid "<primary><command>xe</command></primary>" |
| 1693 |
msgid "<primary><command>lvcreate</command></primary>" |
| 1694 |
msgstr "<primary><command>xe</command></primary>" |
| 1695 |
|
| 1696 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1697 |
# Tag: L-CFMD; |
| 1698 |
#, fuzzy |
| 1699 |
#| msgid "<primary><command>virsh</command></primary>" |
| 1700 |
msgid "<primary><command>lvdisplay</command></primary>" |
| 1701 |
msgstr "<primary><command>virsh</command></primary>" |
| 1702 |
|
| 1703 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1704 |
# Tag: L-CFMD; |
| 1705 |
#, fuzzy |
| 1706 |
#| msgid "" |
| 1707 |
#| "<computeroutput># </computeroutput><userinput>lvdisplay</userinput>\n" |
| 1708 |
#| "<computeroutput># </computeroutput><userinput>lvcreate -n lv_files -L 5G vg_critical</userinput>\n" |
| 1709 |
#| "<computeroutput> Logical volume \"lv_files\" created\n" |
| 1710 |
#| "# </computeroutput><userinput>lvdisplay</userinput>\n" |
| 1711 |
#| "<computeroutput> --- Logical volume ---\n" |
| 1712 |
#| " LV Path /dev/vg_critical/lv_files\n" |
| 1713 |
#| " LV Name lv_files\n" |
| 1714 |
#| " VG Name vg_critical\n" |
| 1715 |
#| " LV UUID J3V0oE-cBYO-KyDe-5e0m-3f70-nv0S-kCWbpT\n" |
| 1716 |
#| " LV Write Access read/write\n" |
| 1717 |
#| " LV Creation host, time mirwiz, 2015-06-10 06:10:50 -0400\n" |
| 1718 |
#| " LV Status available\n" |
| 1719 |
#| " # open 0\n" |
| 1720 |
#| " LV Size 5.00 GiB\n" |
| 1721 |
#| " Current LE 1280\n" |
| 1722 |
#| " Segments 2\n" |
| 1723 |
#| " Allocation inherit\n" |
| 1724 |
#| " Read ahead sectors auto\n" |
| 1725 |
#| " - currently set to 256\n" |
| 1726 |
#| " Block device 253:0\n" |
| 1727 |
#| "\n" |
| 1728 |
#| "# </computeroutput><userinput>lvcreate -n lv_base -L 1G vg_critical</userinput>\n" |
| 1729 |
#| "<computeroutput> Logical volume \"lv_base\" created\n" |
| 1730 |
#| "# </computeroutput><userinput>lvcreate -n lv_backups -L 12G vg_normal</userinput>\n" |
| 1731 |
#| "<computeroutput> Logical volume \"lv_backups\" created\n" |
| 1732 |
#| "# </computeroutput><userinput>lvdisplay -C</userinput>\n" |
| 1733 |
#| "<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 1734 |
#| " lv_base vg_critical -wi-a--- 1.00g \n" |
| 1735 |
#| " lv_files vg_critical -wi-a--- 5.00g \n" |
| 1736 |
#| " lv_backups vg_normal -wi-a--- 12.00g</computeroutput>" |
| 1737 |
msgid "" |
| 1738 |
"<computeroutput># </computeroutput><userinput>lvdisplay\n" |
| 1739 |
"</userinput><computeroutput># </computeroutput><userinput>lvcreate -n lv_files -L 5G vg_critical\n" |
| 1740 |
"</userinput><computeroutput> Logical volume \"lv_files\" created.\n" |
| 1741 |
"# </computeroutput><userinput>lvdisplay\n" |
| 1742 |
"</userinput><computeroutput> --- Logical volume ---\n" |
| 1743 |
" LV Path /dev/vg_critical/lv_files\n" |
| 1744 |
" LV Name lv_files\n" |
| 1745 |
" VG Name vg_critical\n" |
| 1746 |
" LV UUID Nr62xe-Zu7d-0u3z-Yyyp-7Cj1-Ej2t-gw04Xd\n" |
| 1747 |
" LV Write Access read/write\n" |
| 1748 |
" LV Creation host, time debian, 2022-03-01 00:17:46 +0100\n" |
| 1749 |
" LV Status available\n" |
| 1750 |
" # open 0\n" |
| 1751 |
" LV Size 5.00 GiB\n" |
| 1752 |
" Current LE 1280\n" |
| 1753 |
" Segments 2\n" |
| 1754 |
" Allocation inherit\n" |
| 1755 |
" Read ahead sectors auto\n" |
| 1756 |
" - currently set to 256\n" |
| 1757 |
" Block device 253:0\n" |
| 1758 |
"\n" |
| 1759 |
"# </computeroutput><userinput>lvcreate -n lv_base -L 1G vg_critical\n" |
| 1760 |
"</userinput><computeroutput> Logical volume \"lv_base\" created.\n" |
| 1761 |
"# </computeroutput><userinput>lvcreate -n lv_backups -L 11.98G vg_normal\n" |
| 1762 |
"</userinput><computeroutput> Rounding up size to full physical extent 11.98 GiB\n" |
| 1763 |
" Rounding up size to full physical extent 11.98 GiB\n" |
| 1764 |
" Logical volume \"lv_backups\" created.\n" |
| 1765 |
"# </computeroutput><userinput>lvdisplay -C\n" |
| 1766 |
"</userinput><computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 1767 |
" lv_base vg_critical -wi-a----- 1.00g \n" |
| 1768 |
" lv_files vg_critical -wi-a----- 5.00g \n" |
| 1769 |
" lv_backups vg_normal -wi-a----- 11.98g \n" |
| 1770 |
"</computeroutput>" |
| 1771 |
msgstr "" |
| 1772 |
"<computeroutput># </computeroutput><userinput>lvdisplay</userinput>\n" |
| 1773 |
"<computeroutput># </computeroutput><userinput>lvcreate -n lv_files -L 5G vg_critical</userinput>\n" |
| 1774 |
"<computeroutput> Logical volume \"lv_files\" created\n" |
| 1775 |
"# </computeroutput><userinput>lvdisplay</userinput>\n" |
| 1776 |
"<computeroutput> --- Logical volume ---\n" |
| 1777 |
" LV Path /dev/vg_critical/lv_files\n" |
| 1778 |
" LV Name lv_files\n" |
| 1779 |
" VG Name vg_critical\n" |
| 1780 |
" LV UUID J3V0oE-cBYO-KyDe-5e0m-3f70-nv0S-kCWbpT\n" |
| 1781 |
" LV Write Access read/write\n" |
| 1782 |
" LV Creation host, time mirwiz, 2015-06-10 06:10:50 -0400\n" |
| 1783 |
" LV Status available\n" |
| 1784 |
" # open 0\n" |
| 1785 |
" LV Size 5.00 GiB\n" |
| 1786 |
" Current LE 1280\n" |
| 1787 |
" Segments 2\n" |
| 1788 |
" Allocation inherit\n" |
| 1789 |
" Read ahead sectors auto\n" |
| 1790 |
" - currently set to 256\n" |
| 1791 |
" Block device 253:0\n" |
| 1792 |
"\n" |
| 1793 |
"# </computeroutput><userinput>lvcreate -n lv_base -L 1G vg_critical</userinput>\n" |
| 1794 |
"<computeroutput> Logical volume \"lv_base\" created\n" |
| 1795 |
"# </computeroutput><userinput>lvcreate -n lv_backups -L 12G vg_normal</userinput>\n" |
| 1796 |
"<computeroutput> Logical volume \"lv_backups\" created\n" |
| 1797 |
"# </computeroutput><userinput>lvdisplay -C</userinput>\n" |
| 1798 |
"<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 1799 |
" lv_base vg_critical -wi-a--- 1.00g \n" |
| 1800 |
" lv_files vg_critical -wi-a--- 5.00g \n" |
| 1801 |
" lv_backups vg_normal -wi-a--- 12.00g</computeroutput>" |
| 1802 |
|
| 1803 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1804 |
# Tag: L-CFMD; |
| 1805 |
msgid "Two parameters are required when creating logical volumes; they must be passed to the <command>lvcreate</command> as options. The name of the LV to be created is specified with the <literal>-n</literal> option, and its size is generally given using the <literal>-L</literal> option. We also need to tell the command what VG to operate on, of course, hence the last parameter on the command line." |
| 1806 |
msgstr "LV を作成する場合、2 種類のパラメータが必要です。このため、必ず 2 種類のパラメータをオプションとして <command>lvcreate</command> に渡します。作成する LV の名前を <literal>-n</literal> オプションで指定し、サイズを <literal>-L</literal> オプションで指定します。また、操作対象の VG をコマンドに伝えることが必要です。これはもちろん最後のコマンドラインパラメータです。" |
| 1807 |
|
| 1808 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1809 |
# Tag: L-CFMD; |
| 1810 |
msgid "<emphasis>GOING FURTHER</emphasis> <command>lvcreate</command> options" |
| 1811 |
msgstr "<emphasis>GOING FURTHER</emphasis> <command>lvcreate</command> のオプション" |
| 1812 |
|
| 1813 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1814 |
# Tag: L-CFMD; |
| 1815 |
msgid "The <command>lvcreate</command> command has several options to allow tweaking how the LV is created." |
| 1816 |
msgstr "<command>lvcreate</command> コマンドは複数のオプションを取り、作成する LV を微調整することが可能です。" |
| 1817 |
|
| 1818 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1819 |
# Tag: L-CFMD; |
| 1820 |
msgid "Let's first describe the <literal>-l</literal> option, with which the LV's size can be given as a number of blocks (as opposed to the “human” units we used above). These blocks (called PEs, <emphasis>physical extents</emphasis>, in LVM terms) are contiguous units of storage space in PVs, and they can't be split across LVs. When one wants to define storage space for an LV with some precision, for instance to use the full available space, the <literal>-l</literal> option will probably be preferred over <literal>-L</literal>." |
| 1821 |
msgstr "最初に <literal>-l</literal> オプションについて説明しましょう。<literal>-l</literal> オプションを使った場合 LV のサイズをブロック数 (上の例で用いた「人間にとって分かりやすい」単位ではありません) で指定することが可能です。ブロックとは (LVM の用語で PE すなわち<emphasis>物理エクステント</emphasis>と呼ばれています) PV 中のストレージ領域の連続した単位です。ブロックは LV 中に分散されています。ある LV 用のストレージ領域を正確に定義したい場合、たとえば利用できる領域のすべてを使いたい場合、<literal>-l</literal> オプションのほうが <literal>-L</literal> オプションよりも使いやすいでしょう。" |
| 1822 |
|
| 1823 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1824 |
# Tag: L-CFMD; |
| 1825 |
#, fuzzy |
| 1826 |
#| msgid "It's also possible to hint at the physical location of an LV, so that its extents are stored on a particular PV (while staying within the ones assigned to the VG, of course). Since we know that <filename>sdb</filename> is faster than <filename>sdf</filename>, we may want to store the <filename>lv_base</filename> there if we want to give an advantage to the database server compared to the file server. The command line becomes: <command>lvcreate -n lv_base -L 1G vg_critical /dev/sdb2</command>. Note that this command can fail if the PV doesn't have enough free extents. In our example, we would probably have to create <filename>lv_base</filename> before <filename>lv_files</filename> to avoid this situation – or free up some space on <filename>sdb2</filename> with the <command>pvmove</command> command." |
| 1827 |
msgid "It is also possible to hint at the physical location of an LV, so that its extents are stored on a particular PV (while staying within the ones assigned to the VG, of course). Since we know that <filename>sdb</filename> is faster than <filename>sdf</filename>, we may want to store the <filename>lv_base</filename> there if we want to give an advantage to the database server compared to the file server. The command line becomes: <command>lvcreate -n lv_base -L 1G vg_critical /dev/sdb2</command>. Note that this command can fail if the PV doesn't have enough free extents. In our example, we would probably have to create <filename>lv_base</filename> before <filename>lv_files</filename> to avoid this situation – or free up some space on <filename>sdb2</filename> with the <command>pvmove</command> command." |
| 1828 |
msgstr "LV の物理的な位置を示唆することも可能です。こうすることで、LV の PE は特定の PV 上 (もちろん、VG を構成する PV 上に限ります) に作成されます。<filename>sdb</filename> は <filename>sdf</filename> よりも高速なので、<filename>lv_base</filename> を <filename>sdb</filename> 上に作成することでファイルサーバよりもデータベースサーバが高速にアクセスできるようにするには、以下のコマンドラインを使います。すなわち <command>lvcreate -n lv_base -L 1G vg_critical /dev/sdb2</command> です。指定した PV に十分な空き PE がない場合、このコマンドは失敗する可能性があります。今回の例でこのような失敗を防ぐには <filename>lv_files</filename> の前に <filename>lv_base</filename> を作成するか、<command>pvmove</command> コマンドを使って <filename>sdb2</filename> に多少の領域を空ける必要があるかもしれません。" |
| 1829 |
|
| 1830 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1831 |
#, fuzzy |
| 1832 |
#| msgid "<primary><command>xe</command></primary>" |
| 1833 |
msgid "<primary><command>pvmove</command></primary>" |
| 1834 |
msgstr "<primary><command>xe</command></primary>" |
| 1835 |
|
| 1836 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1837 |
# Tag: L-CFMD; |
| 1838 |
msgid "Logical volumes, once created, end up as block device files in <filename>/dev/mapper/</filename>:" |
| 1839 |
msgstr "LV が作成され、ブロックデバイスファイルとして <filename>/dev/mapper/</filename> に現れます。" |
| 1840 |
|
| 1841 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1842 |
#, fuzzy |
| 1843 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1844 |
msgid "<primary><filename>/dev</filename></primary><secondary><filename>/dev/mapper/</filename></secondary>" |
| 1845 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1846 |
|
| 1847 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1848 |
#, fuzzy |
| 1849 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1850 |
msgid "<primary>device</primary><secondary>block</secondary>" |
| 1851 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1852 |
|
| 1853 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1854 |
# Tag: L-CFMD; |
| 1855 |
#, fuzzy |
| 1856 |
#| msgid "" |
| 1857 |
#| "<computeroutput># </computeroutput><userinput>ls -l /dev/mapper</userinput>\n" |
| 1858 |
#| "<computeroutput>total 0\n" |
| 1859 |
#| "crw------- 1 root root 10, 236 Jun 10 16:52 control\n" |
| 1860 |
#| "lrwxrwxrwx 1 root root 7 Jun 10 17:05 vg_critical-lv_base -> ../dm-1\n" |
| 1861 |
#| "lrwxrwxrwx 1 root root 7 Jun 10 17:05 vg_critical-lv_files -> ../dm-0\n" |
| 1862 |
#| "lrwxrwxrwx 1 root root 7 Jun 10 17:05 vg_normal-lv_backups -> ../dm-2\n" |
| 1863 |
#| "# </computeroutput><userinput>ls -l /dev/dm-*</userinput>\n" |
| 1864 |
#| "<computeroutput>brw-rw---T 1 root disk 253, 0 Jun 10 17:05 /dev/dm-0\n" |
| 1865 |
#| "brw-rw---- 1 root disk 253, 1 Jun 10 17:05 /dev/dm-1\n" |
| 1866 |
#| "brw-rw---- 1 root disk 253, 2 Jun 10 17:05 /dev/dm-2\n" |
| 1867 |
#| "</computeroutput>" |
| 1868 |
msgid "" |
| 1869 |
"<computeroutput># </computeroutput><userinput>ls -l /dev/mapper\n" |
| 1870 |
"</userinput><computeroutput><![CDATA[total 0\n" |
| 1871 |
"crw------- 1 root root 10, 236 Mar 1 00:17 control\n" |
| 1872 |
"lrwxrwxrwx 1 root root 7 Mar 1 00:19 vg_critical-lv_base -> ../dm-1\n" |
| 1873 |
"lrwxrwxrwx 1 root root 7 Mar 1 00:17 vg_critical-lv_files -> ../dm-0\n" |
| 1874 |
"lrwxrwxrwx 1 root root 7 Mar 1 00:19 vg_normal-lv_backups -> ../dm-2 ]]>\n" |
| 1875 |
"# </computeroutput><userinput>ls -l /dev/dm-*\n" |
| 1876 |
"</userinput><computeroutput>brw-rw---- 1 root disk 253, 0 Mar 1 00:17 /dev/dm-0\n" |
| 1877 |
"brw-rw---- 1 root disk 253, 1 Mar 1 00:19 /dev/dm-1\n" |
| 1878 |
"brw-rw---- 1 root disk 253, 2 Mar 1 00:19 /dev/dm-2\n" |
| 1879 |
"</computeroutput>" |
| 1880 |
msgstr "" |
| 1881 |
"<computeroutput># </computeroutput><userinput>ls -l /dev/mapper</userinput>\n" |
| 1882 |
"<computeroutput>合計 0\n" |
| 1883 |
"crw------- 1 root root 10, 236 6月 10 16:52 control\n" |
| 1884 |
"lrwxrwxrwx 1 root root 7 6月 10 17:05 vg_critical-lv_base -> ../dm-1\n" |
| 1885 |
"lrwxrwxrwx 1 root root 7 6月 10 17:05 vg_critical-lv_files -> ../dm-0\n" |
| 1886 |
"lrwxrwxrwx 1 root root 7 6月 10 17:05 vg_normal-lv_backups -> ../dm-2\n" |
| 1887 |
"# </computeroutput><userinput>ls -l /dev/dm-*</userinput>\n" |
| 1888 |
"<computeroutput>brw-rw---T 1 root disk 253, 0 6月 10 17:05 /dev/dm-0\n" |
| 1889 |
"brw-rw---- 1 root disk 253, 1 6月 10 17:05 /dev/dm-1\n" |
| 1890 |
"brw-rw---- 1 root disk 253, 2 6月 10 17:05 /dev/dm-2\n" |
| 1891 |
"</computeroutput>" |
| 1892 |
|
| 1893 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1894 |
#, fuzzy |
| 1895 |
#| msgid "<emphasis>NOTE</emphasis> Autodetecting LVM volumes" |
| 1896 |
msgid "<emphasis>NOTE</emphasis> Auto-detecting LVM volumes" |
| 1897 |
msgstr "<emphasis>NOTE</emphasis> LVM ボリュームの自動検出" |
| 1898 |
|
| 1899 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1900 |
#, fuzzy |
| 1901 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1902 |
msgid "<primary>service</primary><secondary><filename>lvm2-activation.service</filename></secondary>" |
| 1903 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1904 |
|
| 1905 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1906 |
#, fuzzy |
| 1907 |
#| msgid "<primary><command>xe</command></primary>" |
| 1908 |
msgid "<primary><command>vgchange</command></primary>" |
| 1909 |
msgstr "<primary><command>xe</command></primary>" |
| 1910 |
|
| 1911 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1912 |
# Tag: L-CFMD; |
| 1913 |
# Ref: $ man 8 vgchange; |
| 1914 |
msgid "When the computer boots, the <filename>lvm2-activation</filename> systemd service unit executes <command>vgchange -aay</command> to “activate” the volume groups: it scans the available devices; those that have been initialized as physical volumes for LVM are registered into the LVM subsystem, those that belong to volume groups are assembled, and the relevant logical volumes are started and made available. There is therefore no need to edit configuration files when creating or modifying LVM volumes." |
| 1915 |
msgstr "コンピュータの起動時に、<filename>lvm2-activation</filename> systemd サービスユニットは <command>vgchange -aay</command> を実行して VG を「始動」します。具体的に言えば、<filename>lvm2-activation</filename> systemd サービスユニットは利用できるデバイスを探します。そして LVM サブシステムに LVM 用の PV として初期化されたデバイスが登録され、PV から構成される VG が開始され、VG から分割された LV が開始され、LV が利用できるようになります。このため、LVM ボリュームを作成したり変更する際に設定ファイルを編集する必要はありません。" |
| 1916 |
|
| 1917 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1918 |
# Tag: L-CFMD; |
| 1919 |
msgid "Note, however, that the layout of the LVM elements (physical and logical volumes, and volume groups) is backed up in <filename>/etc/lvm/backup</filename>, which can be useful in case of a problem (or just to sneak a peek under the hood)." |
| 1920 |
msgstr "しかしながら、LVM 要素 (PV、LV、GV) の配置図は <filename>/etc/lvm/backup</filename> にバックアップされ、問題が起きた時 (見えないところで何が行われているかを確認したい時) に有益です。" |
| 1921 |
|
| 1922 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1923 |
#, fuzzy |
| 1924 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 1925 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/lvm/backup</filename></secondary>" |
| 1926 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 1927 |
|
| 1928 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1929 |
msgid "To make things easier, convenience symbolic links are also created in directories matching the VGs:" |
| 1930 |
msgstr "ブロックデバイスファイルを分かり易くするために、VG に対応するディレクトリの中に便利なシンボリックリンクが作成されます。" |
| 1931 |
|
| 1932 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1933 |
# Tag: L-CFMD; |
| 1934 |
#, fuzzy |
| 1935 |
#| msgid "" |
| 1936 |
#| "<computeroutput># </computeroutput><userinput>ls -l /dev/vg_critical</userinput>\n" |
| 1937 |
#| "<computeroutput>total 0\n" |
| 1938 |
#| "lrwxrwxrwx 1 root root 7 Jun 10 17:05 lv_base -> ../dm-1\n" |
| 1939 |
#| "lrwxrwxrwx 1 root root 7 Jun 10 17:05 lv_files -> ../dm-0\n" |
| 1940 |
#| "# </computeroutput><userinput>ls -l /dev/vg_normal</userinput>\n" |
| 1941 |
#| "<computeroutput>total 0\n" |
| 1942 |
#| "lrwxrwxrwx 1 root root 7 Jun 10 17:05 lv_backups -> ../dm-2</computeroutput>" |
| 1943 |
msgid "" |
| 1944 |
"<computeroutput># </computeroutput><userinput>ls -l /dev/vg_critical\n" |
| 1945 |
"</userinput><computeroutput><![CDATA[total 0\n" |
| 1946 |
"lrwxrwxrwx 1 root root 7 Mar 1 00:19 lv_base -> ../dm-1\n" |
| 1947 |
"lrwxrwxrwx 1 root root 7 Mar 1 00:17 lv_files -> ../dm-0 ]]>\n" |
| 1948 |
"# </computeroutput><userinput>ls -l /dev/vg_normal\n" |
| 1949 |
"</userinput><computeroutput><![CDATA[total 0\n" |
| 1950 |
"lrwxrwxrwx 1 root root 7 Mar 1 00:19 lv_backups -> ../dm-2 ]]>\n" |
| 1951 |
"</computeroutput>" |
| 1952 |
msgstr "" |
| 1953 |
"<computeroutput># </computeroutput><userinput>ls -l /dev/vg_critical</userinput>\n" |
| 1954 |
"<computeroutput>合計 0\n" |
| 1955 |
"lrwxrwxrwx 1 root root 7 6月 10 17:05 lv_base -> ../dm-1\n" |
| 1956 |
"lrwxrwxrwx 1 root root 7 6月 10 17:05 lv_files -> ../dm-0\n" |
| 1957 |
"# </computeroutput><userinput>ls -l /dev/vg_normal</userinput>\n" |
| 1958 |
"<computeroutput>合計 0\n" |
| 1959 |
"lrwxrwxrwx 1 root root 7 6月 10 17:05 lv_backups -> ../dm-2</computeroutput>" |
| 1960 |
|
| 1961 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1962 |
msgid "The LVs can then be used exactly like standard partitions:" |
| 1963 |
msgstr "LV は標準的なパーティションと全く同様に取り扱われます。" |
| 1964 |
|
| 1965 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 1966 |
# Tag: L-CFMD; |
| 1967 |
#, fuzzy |
| 1968 |
#| msgid "" |
| 1969 |
#| "<computeroutput># </computeroutput><userinput>mkfs.ext4 /dev/vg_normal/lv_backups</userinput>\n" |
| 1970 |
#| "<computeroutput>mke2fs 1.42.12 (29-Aug-2014)\n" |
| 1971 |
#| "Creating filesystem with 3145728 4k blocks and 786432 inodes\n" |
| 1972 |
#| "Filesystem UUID: b5236976-e0e2-462e-81f5-0ae835ddab1d\n" |
| 1973 |
#| "[...]\n" |
| 1974 |
#| "Creating journal (32768 blocks): done\n" |
| 1975 |
#| "Writing superblocks and filesystem accounting information: done \n" |
| 1976 |
#| "# </computeroutput><userinput>mkdir /srv/backups</userinput>\n" |
| 1977 |
#| "<computeroutput># </computeroutput><userinput>mount /dev/vg_normal/lv_backups /srv/backups</userinput>\n" |
| 1978 |
#| "<computeroutput># </computeroutput><userinput>df -h /srv/backups</userinput>\n" |
| 1979 |
#| "<computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 1980 |
#| "/dev/mapper/vg_normal-lv_backups 12G 30M 12G 1% /srv/backups\n" |
| 1981 |
#| "# </computeroutput><userinput>[...]</userinput>\n" |
| 1982 |
#| "<computeroutput>[...]\n" |
| 1983 |
#| "# </computeroutput><userinput>cat /etc/fstab</userinput>\n" |
| 1984 |
#| "<computeroutput>[...]\n" |
| 1985 |
#| "/dev/vg_critical/lv_base /srv/base ext4 defaults 0 2\n" |
| 1986 |
#| "/dev/vg_critical/lv_files /srv/files ext4 defaults 0 2\n" |
| 1987 |
#| "/dev/vg_normal/lv_backups /srv/backups ext4 defaults 0 2</computeroutput>" |
| 1988 |
msgid "" |
| 1989 |
"<computeroutput># </computeroutput><userinput>mkfs.ext4 /dev/vg_normal/lv_backups\n" |
| 1990 |
"</userinput><computeroutput>mke2fs 1.46.2 (28-Feb-2021)\n" |
| 1991 |
"Discarding device blocks: done \n" |
| 1992 |
"Creating filesystem with 3140608 4k blocks and 786432 inodes\n" |
| 1993 |
"Filesystem UUID: 7eaf0340-b740-421e-96b2-942cdbf29cb3\n" |
| 1994 |
"Superblock backups stored on blocks: \n" |
| 1995 |
"\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208\n" |
| 1996 |
"\n" |
| 1997 |
"Allocating group tables: done \n" |
| 1998 |
"Writing inode tables: done \n" |
| 1999 |
"Creating journal (16384 blocks): done\n" |
| 2000 |
"Writing superblocks and filesystem accounting information: done \n" |
| 2001 |
"\n" |
| 2002 |
"# </computeroutput><userinput>mkdir /srv/backups\n" |
| 2003 |
"</userinput><computeroutput># </computeroutput><userinput>mount /dev/vg_normal/lv_backups /srv/backups\n" |
| 2004 |
"</userinput><computeroutput># </computeroutput><userinput>df -h /srv/backups\n" |
| 2005 |
"</userinput><computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2006 |
"/dev/mapper/vg_normal-lv_backups 12G 24K 12G 1% /srv/backups\n" |
| 2007 |
"# </computeroutput><userinput>[...]\n" |
| 2008 |
"</userinput><computeroutput>[...]\n" |
| 2009 |
"# </computeroutput><userinput>cat /etc/fstab\n" |
| 2010 |
"</userinput><computeroutput>[...]\n" |
| 2011 |
"/dev/vg_critical/lv_base /srv/base ext4 defaults 0 2\n" |
| 2012 |
"/dev/vg_critical/lv_files /srv/files ext4 defaults 0 2\n" |
| 2013 |
"/dev/vg_normal/lv_backups /srv/backups ext4 defaults 0 2\n" |
| 2014 |
"</computeroutput>" |
| 2015 |
msgstr "" |
| 2016 |
"<computeroutput># </computeroutput><userinput>mkfs.ext4 /dev/vg_normal/lv_backups</userinput>\n" |
| 2017 |
"<computeroutput>mke2fs 1.42.12 (29-Aug-2014)\n" |
| 2018 |
"Creating filesystem with 3145728 4k blocks and 786432 inodes\n" |
| 2019 |
"Filesystem UUID: b5236976-e0e2-462e-81f5-0ae835ddab1d\n" |
| 2020 |
"[...]\n" |
| 2021 |
"Creating journal (32768 blocks): done\n" |
| 2022 |
"Writing superblocks and filesystem accounting information: done \n" |
| 2023 |
"# </computeroutput><userinput>mkdir /srv/backups</userinput>\n" |
| 2024 |
"<computeroutput># </computeroutput><userinput>mount /dev/vg_normal/lv_backups /srv/backups</userinput>\n" |
| 2025 |
"<computeroutput># </computeroutput><userinput>df -h /srv/backups</userinput>\n" |
| 2026 |
"<computeroutput>ファイルシス サイズ 使用 残り 使用% マウント位置\n" |
| 2027 |
"/dev/mapper/vg_normal-lv_backups 12G 30M 12G 1% /srv/backups\n" |
| 2028 |
"# </computeroutput><userinput>[...]</userinput>\n" |
| 2029 |
"<computeroutput>[...]\n" |
| 2030 |
"# </computeroutput><userinput>cat /etc/fstab</userinput>\n" |
| 2031 |
"<computeroutput>[...]\n" |
| 2032 |
"/dev/vg_critical/lv_base /srv/base ext4 defaults 0 2\n" |
| 2033 |
"/dev/vg_critical/lv_files /srv/files ext4 defaults 0 2\n" |
| 2034 |
"/dev/vg_normal/lv_backups /srv/backups ext4 defaults 0 2</computeroutput>" |
| 2035 |
|
| 2036 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2037 |
msgid "From the applications' point of view, the myriad small partitions have now been abstracted into one large 12 GB volume, with a friendlier name." |
| 2038 |
msgstr "アプリケーションにしてみれば、無数の小さなパーティションがわかり易い名前を持つ 1 つの大きな 12 GB のボリュームにまとめられたことになります。" |
| 2039 |
|
| 2040 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2041 |
msgid "LVM Over Time" |
| 2042 |
msgstr "経時変化に伴う LVM の利便性" |
| 2043 |
|
| 2044 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2045 |
# Tag: L-CFMD; |
| 2046 |
#, fuzzy |
| 2047 |
#| msgid "<primary><command>virsh</command></primary>" |
| 2048 |
msgid "<primary><command>lvresize</command></primary>" |
| 2049 |
msgstr "<primary><command>virsh</command></primary>" |
| 2050 |
|
| 2051 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2052 |
#, fuzzy |
| 2053 |
#| msgid "<primary><command>xe</command></primary>" |
| 2054 |
msgid "<primary><command>resize2fs</command></primary>" |
| 2055 |
msgstr "<primary><command>xe</command></primary>" |
| 2056 |
|
| 2057 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2058 |
#, fuzzy |
| 2059 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2060 |
msgid "<primary>volume</primary><secondary>resize</secondary>" |
| 2061 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2062 |
|
| 2063 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2064 |
#, fuzzy |
| 2065 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2066 |
msgid "<primary>LVM</primary><secondary>resize LV</secondary>" |
| 2067 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2068 |
|
| 2069 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2070 |
msgid "Even though the ability to aggregate partitions or physical disks is convenient, this is not the main advantage brought by LVM. The flexibility it brings is especially noticed as time passes, when needs evolve. In our example, let's assume that new large files must be stored, and that the LV dedicated to the file server is too small to contain them. Since we haven't used the whole space available in <filename>vg_critical</filename>, we can grow <filename>lv_files</filename>. For that purpose, we'll use the <command>lvresize</command> command, then <command>resize2fs</command> to adapt the filesystem accordingly:" |
| 2071 |
msgstr "LVM のパーティションや物理ディスクを統合する機能は便利ですが、これは LVM のもたらす主たる利点ではありません。時間経過に伴い LVM のもたらす柔軟性が特に重要になる時とは LV のサイズを増加させる必要が生じた時でしょう。ここまでの例を使い、LV に新たに巨大なファイルを保存したいけれども、ファイルサーバ用の LV はこの巨大なファイルを保存するには狭すぎると仮定しましょう。<filename>vg_critical</filename> から分割できる全領域はまだ使い切られていないので、<filename>lv_files</filename> のサイズを増やすことが可能です。LV のサイズを増やすために <command>lvresize</command> コマンドを使い、LV のサイズの変化にファイルシステムを対応させるために <command>resize2fs</command> を使います。" |
| 2072 |
|
| 2073 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2074 |
# Tag: L-CFMD; |
| 2075 |
#, fuzzy |
| 2076 |
#| msgid "" |
| 2077 |
#| "<computeroutput># </computeroutput><userinput>df -h /srv/files/</userinput>\n" |
| 2078 |
#| "<computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2079 |
#| "/dev/mapper/vg_critical-lv_files 5.0G 4.6G 146M 97% /srv/files\n" |
| 2080 |
#| "# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>\n" |
| 2081 |
#| "<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 2082 |
#| " lv_files vg_critical -wi-ao-- 5.00g\n" |
| 2083 |
#| "# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>\n" |
| 2084 |
#| "<computeroutput> VG #PV #LV #SN Attr VSize VFree\n" |
| 2085 |
#| " vg_critical 2 2 0 wz--n- 8.09g 2.09g\n" |
| 2086 |
#| "# </computeroutput><userinput>lvresize -L 7G vg_critical/lv_files</userinput>\n" |
| 2087 |
#| "<computeroutput> Size of logical volume vg_critical/lv_files changed from 5.00 GiB (1280 extents) to 7.00 GiB (1792 extents).\n" |
| 2088 |
#| " Logical volume lv_files successfully resized\n" |
| 2089 |
#| "# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>\n" |
| 2090 |
#| "<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 2091 |
#| " lv_files vg_critical -wi-ao-- 7.00g\n" |
| 2092 |
#| "# </computeroutput><userinput>resize2fs /dev/vg_critical/lv_files</userinput>\n" |
| 2093 |
#| "<computeroutput>resize2fs 1.42.12 (29-Aug-2014)\n" |
| 2094 |
#| "Filesystem at /dev/vg_critical/lv_files is mounted on /srv/files; on-line resizing required\n" |
| 2095 |
#| "old_desc_blocks = 1, new_desc_blocks = 1\n" |
| 2096 |
#| "The filesystem on /dev/vg_critical/lv_files is now 1835008 (4k) blocks long.\n" |
| 2097 |
#| "\n" |
| 2098 |
#| "# </computeroutput><userinput>df -h /srv/files/</userinput>\n" |
| 2099 |
#| "<computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2100 |
#| "/dev/mapper/vg_critical-lv_files 6.9G 4.6G 2.1G 70% /srv/files</computeroutput>" |
| 2101 |
msgid "" |
| 2102 |
"<computeroutput># </computeroutput><userinput>df -h /srv/files/\n" |
| 2103 |
"</userinput><computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2104 |
"/dev/mapper/vg_critical-lv_files 4.9G 4.2G 485M 90% /srv/files\n" |
| 2105 |
"# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files\n" |
| 2106 |
"</userinput><computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 2107 |
" lv_files vg_critical -wi-ao---- 5.00g \n" |
| 2108 |
"# </computeroutput><userinput>vgdisplay -C vg_critical\n" |
| 2109 |
"</userinput><computeroutput> VG #PV #LV #SN Attr VSize VFree\n" |
| 2110 |
" vg_critical 2 2 0 wz--n- 7.99g 1.99g\n" |
| 2111 |
"# </computeroutput><userinput>lvresize -L 6G vg_critical/lv_files\n" |
| 2112 |
"</userinput><computeroutput> Size of logical volume vg_critical/lv_files changed from 5.00 GiB (1280 extents) to 6.00 GiB (1536 extents).\n" |
| 2113 |
" Logical volume vg_critical/lv_files successfully resized.\n" |
| 2114 |
"# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files\n" |
| 2115 |
"</userinput><computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 2116 |
" lv_files vg_critical -wi-ao---- 6.00g \n" |
| 2117 |
"# </computeroutput><userinput>resize2fs /dev/vg_critical/lv_files\n" |
| 2118 |
"</userinput><computeroutput>resize2fs 1.46.2 (28-Feb-2021)\n" |
| 2119 |
"Filesystem at /dev/vg_critical/lv_files is mounted on /srv/files; on-line resizing required\n" |
| 2120 |
"old_desc_blocks = 1, new_desc_blocks = 1\n" |
| 2121 |
"The filesystem on /dev/vg_critical/lv_files is now 1572864 (4k) blocks long.\n" |
| 2122 |
"\n" |
| 2123 |
"# </computeroutput><userinput>df -h /srv/files/\n" |
| 2124 |
"</userinput><computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2125 |
"/dev/mapper/vg_critical-lv_files 5.9G 4.2G 1.5G 75% /srv/files\n" |
| 2126 |
"</computeroutput>" |
| 2127 |
msgstr "" |
| 2128 |
"<computeroutput># </computeroutput><userinput>df -h /srv/files/</userinput>\n" |
| 2129 |
"<computeroutput>ファイルシス サイズ 使用 残り 使用% マウント位置\n" |
| 2130 |
"/dev/mapper/vg_critical-lv_files 5.0G 4.6G 146M 97% /srv/files\n" |
| 2131 |
"# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>\n" |
| 2132 |
"<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 2133 |
" lv_files vg_critical -wi-ao-- 5.00g\n" |
| 2134 |
"# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>\n" |
| 2135 |
"<computeroutput> VG #PV #LV #SN Attr VSize VFree\n" |
| 2136 |
" vg_critical 2 2 0 wz--n- 8.09g 2.09g\n" |
| 2137 |
"# </computeroutput><userinput>lvresize -L 7G vg_critical/lv_files</userinput>\n" |
| 2138 |
"<computeroutput> Size of logical volume vg_critical/lv_files changed from 5.00 GiB (1280 extents) to 7.00 GiB (1792 extents).\n" |
| 2139 |
" Logical volume lv_files successfully resized\n" |
| 2140 |
"# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>\n" |
| 2141 |
"<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert\n" |
| 2142 |
" lv_files vg_critical -wi-ao-- 7.00g\n" |
| 2143 |
"# </computeroutput><userinput>resize2fs /dev/vg_critical/lv_files</userinput>\n" |
| 2144 |
"<computeroutput>resize2fs 1.42.12 (29-Aug-2014)\n" |
| 2145 |
"Filesystem at /dev/vg_critical/lv_files is mounted on /srv/files; on-line resizing required\n" |
| 2146 |
"old_desc_blocks = 1, new_desc_blocks = 1\n" |
| 2147 |
"The filesystem on /dev/vg_critical/lv_files is now 1835008 (4k) blocks long.\n" |
| 2148 |
"\n" |
| 2149 |
"# </computeroutput><userinput>df -h /srv/files/</userinput>\n" |
| 2150 |
"<computeroutput>ファイルシス サイズ 使用 残り 使用% マウント位置\n" |
| 2151 |
"/dev/mapper/vg_critical-lv_files 6.9G 4.6G 2.1G 70% /srv/files</computeroutput>" |
| 2152 |
|
| 2153 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2154 |
msgid "<emphasis>CAUTION</emphasis> Resizing filesystems" |
| 2155 |
msgstr "<emphasis>CAUTION</emphasis> ファイルシステムのサイズ変更" |
| 2156 |
|
| 2157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2158 |
#, fuzzy |
| 2159 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2160 |
msgid "<primary>filesystem</primary><secondary>resize</secondary>" |
| 2161 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2162 |
|
| 2163 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2164 |
#, fuzzy |
| 2165 |
#| msgid "Not all filesystems can be resized online; resizing a volume can therefore require unmounting the filesystem first and remounting it afterwards. Of course, if one wants to shrink the space allocated to an LV, the filesystem must be shrunk first; the order is reversed when the resizing goes in the other direction: the logical volume must be grown before the filesystem on it. It's rather straightforward, since at no time must the filesystem size be larger than the block device where it resides (whether that device is a physical partition or a logical volume)." |
| 2166 |
msgid "Not all filesystems can be resized online; resizing a volume can therefore require unmounting the filesystem first and remounting it afterwards. Of course, if one wants to shrink the space allocated to an LV, the filesystem must be shrunk first; the order is reversed when the resizing goes in the other direction: the logical volume must be grown before the filesystem on it. It is rather straightforward, since at no time must the filesystem size be larger than the block device where it resides (whether that device is a physical partition or a logical volume)." |
| 2167 |
msgstr "すべてのファイルシステムがオンラインでサイズを変更できるわけではありません。このため、ボリュームのサイズ変更前にファイルシステムをアンマウントし、ボリュームのサイズ変更後に再マウントしなければいけません。もちろん、ボリュームのサイズを小さくする場合、ボリューム上のファイルシステムのサイズを小さくした後にボリュームのサイズを小さくしなければいけません。ボリュームのサイズを大きくする場合、ボリュームのサイズを大きくした後にボリューム上のファイルシステムを大きくしなければいけません。これはかなりわかり易いです。なぜなら、ブロックデバイス上に存在するファイルシステムのサイズをブロックデバイスよりも大きくすることは絶対に不可能だからです (この原則はボリュームが物理パーティションか LV かに依存しません)。" |
| 2168 |
|
| 2169 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2170 |
msgid "The ext3, ext4 and xfs filesystems can be grown online, without unmounting; shrinking requires an unmount. The reiserfs filesystem allows online resizing in both directions. The venerable ext2 allows neither, and always requires unmounting." |
| 2171 |
msgstr "ext3、ext4、xfs ファイルシステムはオンラインでサイズを増加させることすなわちアンマウントすることなくサイズを増加させることが可能です。しかし、サイズを減少させる場合はアンマウントを必要とします。reiserfs はオンラインでサイズを増加および減少することが可能です。ext2 は増加も減少も可能ですが、アンマウントを必要とします。" |
| 2172 |
|
| 2173 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2174 |
msgid "We could proceed in a similar fashion to extend the volume hosting the database, only we've reached the VG's available space limit:" |
| 2175 |
msgstr "同様の方法でデータベースをホストしている <filename>lv_base</filename> のサイズを増加させます。以下の通り <filename>lv_base</filename> の分割元である <filename>vg_critical</filename> から分割できる領域は既にほぼ使い切った状態になっています。" |
| 2176 |
|
| 2177 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2178 |
# Tag: L-CFMD; |
| 2179 |
#, fuzzy |
| 2180 |
#| msgid "" |
| 2181 |
#| "<computeroutput># </computeroutput><userinput>df -h /srv/base/</userinput>\n" |
| 2182 |
#| "<computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2183 |
#| "/dev/mapper/vg_critical-lv_base 1008M 854M 104M 90% /srv/base\n" |
| 2184 |
#| "# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>\n" |
| 2185 |
#| "<computeroutput> VG #PV #LV #SN Attr VSize VFree \n" |
| 2186 |
#| " vg_critical 2 2 0 wz--n- 8.09g 92.00m</computeroutput>" |
| 2187 |
msgid "" |
| 2188 |
"<computeroutput># </computeroutput><userinput>df -h /srv/base/\n" |
| 2189 |
"</userinput><computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2190 |
"/dev/mapper/vg_critical-lv_base 974M 883M 25M 98% /srv/base\n" |
| 2191 |
"# </computeroutput><userinput>vgdisplay -C vg_critical\n" |
| 2192 |
"</userinput><computeroutput> VG #PV #LV #SN Attr VSize VFree \n" |
| 2193 |
" vg_critical 2 2 0 wz--n- 7.99g 1016.00m\n" |
| 2194 |
"</computeroutput>" |
| 2195 |
msgstr "" |
| 2196 |
"<computeroutput># </computeroutput><userinput>df -h /srv/base/</userinput>\n" |
| 2197 |
"<computeroutput>ファイルシス サイズ 使用 残り 使用% マウント位置\n" |
| 2198 |
"/dev/mapper/vg_critical-lv_base 1008M 854M 104M 90% /srv/base\n" |
| 2199 |
"# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>\n" |
| 2200 |
"<computeroutput> VG #PV #LV #SN Attr VSize VFree \n" |
| 2201 |
" vg_critical 2 2 0 wz--n- 8.09g 92.00m</computeroutput>" |
| 2202 |
|
| 2203 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2204 |
# Tag: L-CFMD; |
| 2205 |
#, fuzzy |
| 2206 |
#| msgid "No matter, since LVM allows adding physical volumes to existing volume groups. For instance, maybe we've noticed that the <filename>sdb1</filename> partition, which was so far used outside of LVM, only contained archives that could be moved to <filename>lv_backups</filename>. We can now recycle it and integrate it to the volume group, and thereby reclaim some available space. This is the purpose of the <command>vgextend</command> command. Of course, the partition must be prepared as a physical volume beforehand. Once the VG has been extended, we can use similar commands as previously to grow the logical volume then the filesystem:" |
| 2207 |
msgid "No matter, since LVM allows adding physical volumes to existing volume groups. For instance, maybe we've noticed that the <filename>sdb3</filename> partition, which was so far used outside of LVM, only contained archives that could be moved to <filename>lv_backups</filename>. We can now recycle it and integrate it to the volume group, and thereby reclaim some available space. This is the purpose of the <command>vgextend</command> command. Of course, the partition must be prepared as a physical volume beforehand. Once the VG has been extended, we can use similar commands as previously to grow the logical volume then the filesystem:" |
| 2208 |
msgstr "でもご安心ください。LVM を使っていれば新しい PV を既存の VG を構成する PV の 1 つとして追加することが可能です。たとえば、今までは LVM の外で管理されていた <filename>sdb1</filename> パーティションには、<filename>lv_backups</filename> に移動しても問題のないアーカイブだけが含まれていた点に気が付いたとしましょう。このため、<filename>sdb1</filename> パーティションを <filename>vg_critical</filename> を構成する PV の 1 つとして再利用することが可能です。こうすることで、<filename>vg_critical</filename> から <filename>lv_base</filename> に分割される領域のサイズを増やすことが可能です。これが <command>vgextend</command> コマンドの目的です。もちろん、事前に <filename>sdb1</filename> パーティションを PV として準備しなければいけません。<filename>vg_critical</filename> を拡張したら、先と同様のコマンドを使って先に <filename>lv_base</filename> のサイズを増加させ、その後に <filename>lv_base</filename> 上のファイルシステムのサイズを増加させます。" |
| 2209 |
|
| 2210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2211 |
# Tag: L-CFMD; |
| 2212 |
#, fuzzy |
| 2213 |
#| msgid "" |
| 2214 |
#| "<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb1</userinput>\n" |
| 2215 |
#| "<computeroutput> Physical volume \"/dev/sdb1\" successfully created\n" |
| 2216 |
#| "# </computeroutput><userinput>vgextend vg_critical /dev/sdb1</userinput>\n" |
| 2217 |
#| "<computeroutput> Volume group \"vg_critical\" successfully extended\n" |
| 2218 |
#| "# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>\n" |
| 2219 |
#| "<computeroutput> VG #PV #LV #SN Attr VSize VFree\n" |
| 2220 |
#| " vg_critical 3 2 0 wz--n- 9.09g 1.09g\n" |
| 2221 |
#| "# </computeroutput><userinput>[...]</userinput>\n" |
| 2222 |
#| "<computeroutput>[...]\n" |
| 2223 |
#| "# </computeroutput><userinput>df -h /srv/base/</userinput>\n" |
| 2224 |
#| "<computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2225 |
#| "/dev/mapper/vg_critical-lv_base 2.0G 854M 1.1G 45% /srv/base</computeroutput>" |
| 2226 |
msgid "" |
| 2227 |
"<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb3\n" |
| 2228 |
"</userinput><computeroutput> Physical volume \"/dev/sdb3\" successfully created.\n" |
| 2229 |
"# </computeroutput><userinput>vgextend vg_critical /dev/sdb3\n" |
| 2230 |
"</userinput><computeroutput> Volume group \"vg_critical\" successfully extended\n" |
| 2231 |
"# </computeroutput><userinput>vgdisplay -C vg_critical\n" |
| 2232 |
"</userinput><computeroutput><![CDATA[ VG #PV #LV #SN Attr VSize VFree \n" |
| 2233 |
" vg_critical 3 2 0 wz--n- <12.99g <5.99g ]]>\n" |
| 2234 |
"# </computeroutput><userinput>lvresize -L 2G vg_critical/lv_base\n" |
| 2235 |
"</userinput><computeroutput>[...]\n" |
| 2236 |
"# </computeroutput><userinput>resize2fs /dev/vg_critical/lv_base\n" |
| 2237 |
"</userinput><computeroutput>[...]\n" |
| 2238 |
"# </computeroutput><userinput>df -h /srv/base/\n" |
| 2239 |
"</userinput><computeroutput>Filesystem Size Used Avail Use% Mounted on\n" |
| 2240 |
"/dev/mapper/vg_critical-lv_base 2.0G 886M 991M 48% /srv/base\n" |
| 2241 |
"</computeroutput>" |
| 2242 |
msgstr "" |
| 2243 |
"<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb1</userinput>\n" |
| 2244 |
"<computeroutput> Physical volume \"/dev/sdb1\" successfully created\n" |
| 2245 |
"# </computeroutput><userinput>vgextend vg_critical /dev/sdb1</userinput>\n" |
| 2246 |
"<computeroutput> Volume group \"vg_critical\" successfully extended\n" |
| 2247 |
"# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>\n" |
| 2248 |
"<computeroutput> VG #PV #LV #SN Attr VSize VFree\n" |
| 2249 |
" vg_critical 3 2 0 wz--n- 9.09g 1.09g\n" |
| 2250 |
"# </computeroutput><userinput>[...]</userinput>\n" |
| 2251 |
"<computeroutput>[...]\n" |
| 2252 |
"# </computeroutput><userinput>df -h /srv/base/</userinput>\n" |
| 2253 |
"<computeroutput>ファイルシス サイズ 使用 残り 使用% マウント位置\n" |
| 2254 |
"/dev/mapper/vg_critical-lv_base 2.0G 854M 1.1G 45% /srv/base</computeroutput>" |
| 2255 |
|
| 2256 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2257 |
msgid "<emphasis>GOING FURTHER</emphasis> Advanced LVM" |
| 2258 |
msgstr "<emphasis>GOING FURTHER</emphasis> LVM の上級活用" |
| 2259 |
|
| 2260 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2261 |
# Tag: L-CFMD; |
| 2262 |
#, fuzzy |
| 2263 |
#| msgid "LVM also caters for more advanced uses, where many details can be specified by hand. For instance, an administrator can tweak the size of the blocks that make up physical and logical volumes, as well as their physical layout. It is also possible to move blocks across PVs, for instance to fine-tune performance or, in a more mundane way, to free a PV when one needs to extract the corresponding physical disk from the VG (whether to affect it to another VG or to remove it from LVM altogether). The manual pages describing the commands are generally clear and detailed. A good entry point is the <citerefentry><refentrytitle>lvm</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page." |
| 2264 |
msgid "LVM also caters for more advanced uses, where many details can be specified by hand. For instance, an administrator can tweak the size of the blocks that make up physical and logical volumes, as well as their physical layout. It is also possible to move blocks across PVs, for instance, to fine-tune performance or, in a more mundane way, to free a PV when one needs to extract the corresponding physical disk from the VG (whether to affect it to another VG or to remove it from LVM altogether). The manual pages describing the commands are generally clear and detailed. A good entry point is the <citerefentry><refentrytitle>lvm</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page." |
| 2265 |
msgstr "LVM にはさらに上級の使い方があり、多くの設定事項を手作業で指定することが可能です。たとえば、管理者は PV と LV のブロックサイズおよびボリュームの物理的な配置を微調整することが可能です。また、ブロックを PV 間で移動することも可能です。これは、たとえば性能を微調整したり、よりありふれたケースではある物理ディスクに対応する PV を VG の構成要素から外したりするため (PV を別の VG に移動したり、完全に LVM から取り外したりするため) に行われます。コマンドを説明しているマニュアルページは基本的に明快で詳細です。手始めに、<citerefentry><refentrytitle>lvm</refentrytitle> <manvolnum>8</manvolnum></citerefentry> マニュアルページを参照することをお勧めします。" |
| 2266 |
|
| 2267 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2268 |
msgid "RAID or LVM?" |
| 2269 |
msgstr "RAID それとも LVM?" |
| 2270 |
|
| 2271 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2272 |
msgid "RAID and LVM both bring indisputable advantages as soon as one leaves the simple case of a desktop computer with a single hard disk where the usage pattern doesn't change over time. However, RAID and LVM go in two different directions, with diverging goals, and it is legitimate to wonder which one should be adopted. The most appropriate answer will of course depend on current and foreseeable requirements." |
| 2273 |
msgstr "1 番目の利用形態は用途が時間的に変化しない 1 台のハードディスクを備えたデスクトップコンピュータのような単純な利用形態です。この場合 RAID と LVM はどちらも疑う余地のない利点をもたらします。しかしながら、RAID と LVM は目標を分岐させて別々の道を歩んでいます。どちらを使うべきか悩むのは間違っていることではありません。最も適切な答えはもちろん現在の要求と将来に予測される要求に依存します。" |
| 2274 |
|
| 2275 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2276 |
msgid "There are a few simple cases where the question doesn't really arise. If the requirement is to safeguard data against hardware failures, then obviously RAID will be set up on a redundant array of disks, since LVM doesn't really address this problem. If, on the other hand, the need is for a flexible storage scheme where the volumes are made independent of the physical layout of the disks, RAID doesn't help much and LVM will be the natural choice." |
| 2277 |
msgstr "いくつかの状況では、疑問の余地がないくらい簡単に答えを出すことが可能です。2 番目の利用形態はハードウェア障害からデータを保護することが求められる利用形態です。この場合、ディスクの冗長性アレイ上に RAID をセットアップするのは明らかです。なぜなら LVM はこの種の問題への対応策を全く用意していないからです。逆に、柔軟なストレージ計画が必要でディスクの物理的な配置に依存せずにボリュームを構成したい場合、RAID はあまり役に立たず LVM を選ぶのが自然です。" |
| 2278 |
|
| 2279 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2280 |
msgid "<emphasis>NOTE</emphasis> If performance matters…" |
| 2281 |
msgstr "<emphasis>NOTE</emphasis> 性能が重要な場合" |
| 2282 |
|
| 2283 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2284 |
#, fuzzy |
| 2285 |
#| msgid "<primary>RAID</primary>" |
| 2286 |
msgid "<primary>SSD</primary>" |
| 2287 |
msgstr "<primary>RAID</primary>" |
| 2288 |
|
| 2289 |
msgid "<primary>Solid State Drives</primary><see>SSD</see>" |
| 2290 |
msgstr "" |
| 2291 |
|
| 2292 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2293 |
#, fuzzy |
| 2294 |
#| msgid "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." |
| 2295 |
msgid "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." |
| 2296 |
msgstr "特にアクセス速度という意味の入出力速度が最重要な場合を考えてみましょう。LVM および RAID はどのような組み合わせで使っても性能にある程度の影響をおよぼします。このため、どの組み合わせを採用するかが議題に挙げられるかもしれません。しかしながら、どんな組み合わせを使っても性能差は極めて少なく、この程度の性能差が無視できない場合は極めて少ないと言えるでしょう。性能が重要な場合、実現できる最良の改善方針は非回転ストレージメディア (<indexterm><primary>SSD</primary></indexterm><emphasis>ソリッドステートドライブ</emphasis>すなわち SSD) を使うことです。SSD のメガバイト当たりの費用は標準的なハードディスクドライブよりも高価で、SSD の容量は通常小さいですが、SSD はランダムアクセスで素晴らしい性能を発揮します。ファイルシステムに広く分散された位置から数多くの入出力を行うような場合 (たとえば複雑な問い合わせが定期的に実行されるデータベースの場合)、SSD 上にデータベースを置くほうが RAID over LVM または LVM over RAID 上にデータベースを置くよりも良好な性能が手に入ります。このような場合、純粋な速度だけでなく他の要素も検討した上で採用の可否を決定するべきです。なぜなら、性能が必要な場合に SSD を採用することは最も安直な解決策だからです。" |
| 2297 |
|
| 2298 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2299 |
msgid "The third notable use case is when one just wants to aggregate two disks into one volume, either for performance reasons or to have a single filesystem that is larger than any of the available disks. This case can be addressed both by a RAID-0 (or even linear-RAID) and by an LVM volume. When in this situation, and barring extra constraints (for instance, keeping in line with the rest of the computers if they only use RAID), the configuration of choice will often be LVM. The initial set up is barely more complex, and that slight increase in complexity more than makes up for the extra flexibility that LVM brings if the requirements change or if new disks need to be added." |
| 2300 |
msgstr "3 番目に注目すべき利用形態は単に 2 つのディスクを 1 つのボリュームにまとめるような利用形態です。性能が欲しかったり、利用できるディスクのどれよりも大きな単一のファイルシステムにしたい場合にこの利用形態が採用されます。この場合、RAID-0 (またはリニア RAID) か LVM ボリュームを使って対処できます。この状況では、追加的な制約事項 (たとえば、他のコンピュータが RAID だけを使っている場合に RAID を使わなければいけないなどの制約事項) がなければ、通常 LVM を選択すると良いでしょう。LVM の最初のセットアップは RAID に比べて複雑ですが、LVM は複雑度を少し増加させるだけで要求が変った場合や新しいディスクを追加する必要ができた場合に対処可能な追加的な柔軟性を大きく上昇させます。" |
| 2301 |
|
| 2302 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2303 |
# Ref: https://wiki.archlinux.org/index.php/Software_RAID_and_LVM; |
| 2304 |
msgid "Then of course, there is the really interesting use case, where the storage system needs to be made both resistant to hardware failure and flexible when it comes to volume allocation. Neither RAID nor LVM can address both requirements on their own; no matter, this is where we use both at the same time — or rather, one on top of the other. The scheme that has all but become a standard since RAID and LVM have reached maturity is to ensure data redundancy first by grouping disks in a small number of large RAID arrays, and to use these RAID arrays as LVM physical volumes; logical partitions will then be carved from these LVs for filesystems. The selling point of this setup is that when a disk fails, only a small number of RAID arrays will need to be reconstructed, thereby limiting the time spent by the administrator for recovery." |
| 2305 |
msgstr "そしてもちろん、最後の本当に興味深い利用形態はストレージシステムにハードウェア障害に対する耐性を持たせさらにボリューム分割に対する柔軟性を持たせる必要がある場合の利用形態です。RAID と LVM のどちらも片方だけで両方の要求を満足させることは不可能です。しかし心配ありません。この要求を満足させるには RAID と LVM の両方を同時に使用する方針、正確に言えば一方の上に他方を構成する方針を採用すれば良いでのです。RAID と LVM の高い成熟度のおかげでほぼ標準になりつつある方針に従うならば、最初にディスクを少数の大きな RAID アレイにグループ分けすることでデータの冗長性を確保します。さらにそれらの RAID アレイを LVM の PV として使います。そして、ファイルシステム用の VG から分割された LV を論理パーティションとして使います。この標準的な方針の優れた点は、ディスク障害が起きた場合に再構築しなければいけない RAID アレイの数が少ない点です。このため、管理者は復旧に必要な時間を減らすことが可能です。" |
| 2306 |
|
| 2307 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2308 |
#, fuzzy |
| 2309 |
#| msgid "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." |
| 2310 |
msgid "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." |
| 2311 |
msgstr "ここで具体例を見てみましょう。たとえば Falcot Corp の広報課は動画編集用にワークステーションを必要としていますが、広報課の予算の都合上、最初から高性能のハードウェアに投資することは不可能です。このため、グラフィック性能を担うハードウェア (モニタとビデオカード) に大きな予算を割き、ストレージ用には一般的なハードウェアを使うことが決定されました。しかしながら、広く知られている通りデジタルビデオ用のストレージはある種の条件を必要とします。すなわち、保存されるデータのサイズが大きく、このデータを読み込みおよび書き込みする際の処理速度がシステム全体の性能にとって重要 (たとえば、平均的なアクセス時間よりも重要) という条件です。この条件を一般的なハードウェアを使って満足させる必要があります。今回の場合 2 台の SATA ハードディスクドライブを使います。さらに、システムデータと一部のユーザデータはハードウェア障害に対する耐性を持たせる必要があります。編集済みのビデオクリップを保護する必要はありますが、編集前のビデオ素材をそれほど気にする必要はありません。なぜなら、編集前のビデオ素材はまだビデオテープに残されているからです。" |
| 2312 |
|
| 2313 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2314 |
msgid "RAID-1 and LVM are combined to satisfy these constraints. The disks are attached to two different SATA controllers to optimize parallel access and reduce the risk of a simultaneous failure, and they therefore appear as <filename>sda</filename> and <filename>sdc</filename>. They are partitioned identically along the following scheme:" |
| 2315 |
msgstr "前述の条件を満足させるために RAID-1 と LVM を組み合わせます。ディスクの並行アクセスを最適化し、そして障害が同時に発生する危険性を減らすために、各ディスクは 2 つの異なる SATA コントローラに接続されています。このため、各ディスクは <filename>sda</filename> と <filename>sdc</filename> として現れます。どちらのディスクも以下に示したパーティショニング方針に従ってパーティショニングされます。" |
| 2316 |
|
| 2317 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2318 |
# Tag: L-CFMD; |
| 2319 |
#, fuzzy |
| 2320 |
#| msgid "" |
| 2321 |
#| "<computeroutput># </computeroutput><userinput>fdisk -l /dev/sda</userinput>\n" |
| 2322 |
#| "<computeroutput>\n" |
| 2323 |
#| "Disk /dev/sda: 300 GB, 300090728448 bytes, 586114704 sectors\n" |
| 2324 |
#| "Units: sectors of 1 * 512 = 512 bytes\n" |
| 2325 |
#| "Sector size (logical/physical): 512 bytes / 512 bytes\n" |
| 2326 |
#| "I/O size (minimum/optimal): 512 bytes / 512 bytes\n" |
| 2327 |
#| "Disklabel type: dos\n" |
| 2328 |
#| "Disk identifier: 0x00039a9f\n" |
| 2329 |
#| "\n" |
| 2330 |
#| "Device Boot Start End Sectors Size Id Type\n" |
| 2331 |
#| "/dev/sda1 * 2048 1992060 1990012 1.0G fd Linux raid autodetect\n" |
| 2332 |
#| "/dev/sda2 1992061 3984120 1992059 1.0G 82 Linux swap / Solaris\n" |
| 2333 |
#| "/dev/sda3 4000185 586099395 582099210 298G 5 Extended\n" |
| 2334 |
#| "/dev/sda5 4000185 203977305 199977120 102G fd Linux raid autodetect\n" |
| 2335 |
#| "/dev/sda6 203977306 403970490 199993184 102G fd Linux raid autodetect\n" |
| 2336 |
#| "/dev/sda7 403970491 586099395 182128904 93G 8e Linux LVM</computeroutput>" |
| 2337 |
msgid "" |
| 2338 |
"<computeroutput># </computeroutput><userinput>sfdisk -l /dev/sda\n" |
| 2339 |
"</userinput><computeroutput>Disk /dev/sda: 894.25 GiB, 960197124096 bytes, 1875385008 sectors\n" |
| 2340 |
"Disk model: SAMSUNG MZ7LM960\n" |
| 2341 |
"Units: sectors of 1 * 512 = 512 bytes\n" |
| 2342 |
"Sector size (logical/physical): 512 bytes / 512 bytes\n" |
| 2343 |
"I/O size (minimum/optimal): 512 bytes / 512 bytes\n" |
| 2344 |
"Disklabel type: gpt\n" |
| 2345 |
"Disk identifier: BB14C130-9E9A-9A44-9462-6226349CA012\n" |
| 2346 |
"\n" |
| 2347 |
"Device Start End Sectors Size Type\n" |
| 2348 |
"/dev/sda1 2048 4095 2048 1M BIOS boot\n" |
| 2349 |
"/dev/sda2 4096 100667391 100663296 48G Linux RAID\n" |
| 2350 |
"/dev/sda3 100667392 134221823 33554432 16G Linux RAID\n" |
| 2351 |
"/dev/sda4 134221824 763367423 629145600 300G Linux RAID\n" |
| 2352 |
"/dev/sda5 763367424 1392513023 629145600 300G Linux RAID\n" |
| 2353 |
"/dev/sda6 1392513024 1875384974 482871951 230.3G Linux LVM\n" |
| 2354 |
"</computeroutput>" |
| 2355 |
msgstr "" |
| 2356 |
"<computeroutput># </computeroutput><userinput>fdisk -l /dev/sda</userinput>\n" |
| 2357 |
"<computeroutput>\n" |
| 2358 |
"Disk /dev/sda: 300 GB, 300090728448 bytes, 586114704 sectors\n" |
| 2359 |
"Units: sectors of 1 * 512 = 512 bytes\n" |
| 2360 |
"Sector size (logical/physical): 512 bytes / 512 bytes\n" |
| 2361 |
"I/O size (minimum/optimal): 512 bytes / 512 bytes\n" |
| 2362 |
"Disklabel type: dos\n" |
| 2363 |
"Disk identifier: 0x00039a9f\n" |
| 2364 |
"\n" |
| 2365 |
"Device Boot Start End Sectors Size Id Type\n" |
| 2366 |
"/dev/sda1 * 2048 1992060 1990012 1.0G fd Linux raid autodetect\n" |
| 2367 |
"/dev/sda2 1992061 3984120 1992059 1.0G 82 Linux swap / Solaris\n" |
| 2368 |
"/dev/sda3 4000185 586099395 582099210 298G 5 Extended\n" |
| 2369 |
"/dev/sda5 4000185 203977305 199977120 102G fd Linux raid autodetect\n" |
| 2370 |
"/dev/sda6 203977306 403970490 199993184 102G fd Linux raid autodetect\n" |
| 2371 |
"/dev/sda7 403970491 586099395 182128904 93G 8e Linux LVM</computeroutput>" |
| 2372 |
|
| 2373 |
msgid "The first partitions of both disks are BIOS boot partitions." |
| 2374 |
msgstr "" |
| 2375 |
|
| 2376 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2377 |
#, fuzzy |
| 2378 |
#| msgid "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." |
| 2379 |
msgid "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." |
| 2380 |
msgstr "<filename>sda1</filename> と <filename>sdc1</filename> パーティション (約 1 GB) から RAID-1 ボリューム <filename>md0</filename> を構成します。<filename>md0</filename> はルートファイルシステムを保存するために直接的に使われます。" |
| 2381 |
|
| 2382 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2383 |
#, fuzzy |
| 2384 |
#| msgid "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." |
| 2385 |
msgid "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." |
| 2386 |
msgstr "<filename>sda2</filename> と <filename>sdc2</filename> パーティションから swap パーティションを作成します。スワップ領域のサイズは合計で 2 GB になります。RAM のサイズ 1 GB と合わせれば、ワークステーションで利用できるメモリサイズは十分な量と言えます。" |
| 2387 |
|
| 2388 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2389 |
#, fuzzy |
| 2390 |
#| msgid "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." |
| 2391 |
msgid "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." |
| 2392 |
msgstr "<filename>sda5</filename> と <filename>sdc5</filename> パーティションおよび <filename>sda6</filename> と <filename>sdc6</filename> パーティションからそれぞれ約 100 GB の 2 つの新しい RAID-1 ボリューム <filename>md1</filename> と <filename>md2</filename> を構成します。<filename>md1</filename> と <filename>md2</filename> は LVM の PV として初期化され、これらの PV から <filename>vg_raid</filename> VG を構成します。<filename>vg_raid</filename> は約 200 GB の安全な領域になります。" |
| 2393 |
|
| 2394 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2395 |
#, fuzzy |
| 2396 |
#| msgid "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." |
| 2397 |
msgid "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." |
| 2398 |
msgstr "残りのパーティションである <filename>sda7</filename> と <filename>sdc7</filename> はそのまま LVM の PV として初期化され、これらの PV から <filename>vg_bulk</filename> VG を構成します。<filename>vg_bulk</filename> はおよそ 200 GB の領域になります。" |
| 2399 |
|
| 2400 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2401 |
msgid "Once the VGs are created, they can be partitioned in a very flexible way. One must keep in mind that LVs created in <filename>vg_raid</filename> will be preserved even if one of the disks fails, which will not be the case for LVs created in <filename>vg_bulk</filename>; on the other hand, the latter will be allocated in parallel on both disks, which allows higher read or write speeds for large files." |
| 2402 |
msgstr "VG を作成したら、VG をとても柔軟な方法で LV に分割することが可能です。<filename>vg_raid</filename> から分割された LV は 1 台のディスク障害に対して耐性を持ちますが、<filename>vg_bulk</filename> から分割された LV はディスク障害に対する耐性を持たない点を忘れないでください。逆に、<filename>vg_bulk</filename> は両方のディスクにわたって割り当てられるので、<filename>vg_bulk</filename> から分割された LV に保存された巨大なファイルの読み書き速度は高速化されるでしょう。" |
| 2403 |
|
| 2404 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2405 |
#, fuzzy |
| 2406 |
#| msgid "We will therefore create the <filename>lv_usr</filename>, <filename>lv_var</filename> and <filename>lv_home</filename> LVs on <filename>vg_raid</filename>, to host the matching filesystems; another large LV, <filename>lv_movies</filename>, will be used to host the definitive versions of movies after editing. The other VG will be split into a large <filename>lv_rushes</filename>, for data straight out of the digital video cameras, and a <filename>lv_tmp</filename> for temporary files. The location of the work area is a less straightforward choice to make: while good performance is needed for that volume, is it worth risking losing work if a disk fails during an editing session? Depending on the answer to that question, the relevant LV will be created on one VG or the other." |
| 2407 |
msgid "We will therefore create the <filename>lv_var</filename> and <filename>lv_home</filename> LVs on <filename>vg_raid</filename>, to host the matching filesystems; another large LV, <filename>lv_movies</filename>, will be used to host the definitive versions of movies after editing. The other VG will be split into a large <filename>lv_rushes</filename>, for data straight out of the digital video cameras, and a <filename>lv_tmp</filename> for temporary files. The location of the work area is a less straightforward choice to make: while good performance is needed for that volume, is it worth risking losing work if a disk fails during an editing session? Depending on the answer to that question, the relevant LV will be created on one VG or the other." |
| 2408 |
msgstr "<filename>vg_raid</filename> から <filename>lv_usr</filename>、<filename>lv_var</filename>、<filename>lv_home</filename> を分割し、各 LV に応じたファイルシステムをホストさせます。さらに、<filename>vg_raid</filename> からもう一つの大きな LV である <filename>lv_movies</filename> を分割し、<filename>lv_movies</filename> に編集済みの最終版の映像をホストさせます。また、<filename>vg_bulk</filename> からデジタルビデオカメラから取り出したデータ用の大きな <filename>lv_rushes</filename> と一時ファイル用の <filename>lv_tmp</filename> を分割します。<filename>vg_raid</filename> と <filename>vg_bulk</filename> のどちらから作業領域用の LV を分割するかは簡単に決められるものではありません。つまり、作業領域用の LV は良い性能を必要としますが、編集作業中にディスク障害が起きた場合に作業内容を保護する必要があるでしょうか? この質問の回答次第で、作業領域用の LV を <filename>vg_raid</filename> か <filename>vg_bulk</filename> のどちらの VG に作成するかが決まります。" |
| 2409 |
|
| 2410 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2411 |
#, fuzzy |
| 2412 |
#| msgid "We now have both some redundancy for important data and much flexibility in how the available space is split across the applications. Should new software be installed later on (for editing audio clips, for instance), the LV hosting <filename>/usr/</filename> can be grown painlessly." |
| 2413 |
msgid "We now have both some redundancy for important data and much flexibility in how the available space is split across the applications." |
| 2414 |
msgstr "これで、重要なデータ用に多少の冗長性と、利用できる領域が用途ごとにどのように分割されるかに関する大きな柔軟性が確保されました。後から (たとえば音声クリップの編集用に) 新しいソフトウェアをインストールする場合も、<filename>/usr/</filename> をホストしている LV のサイズを簡単に増加することが可能です。" |
| 2415 |
|
| 2416 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2417 |
msgid "<emphasis>NOTE</emphasis> Why three RAID-1 volumes?" |
| 2418 |
msgstr "<emphasis>NOTE</emphasis> なぜ 3 種類の RAID-1 ボリュームが必要なのでしょうか?" |
| 2419 |
|
| 2420 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2421 |
msgid "We could have set up one RAID-1 volume only, to serve as a physical volume for <filename>vg_raid</filename>. Why create three of them, then?" |
| 2422 |
msgstr "RAID-1 ボリュームを 1 つだけ作成し、作成した PV から <filename>vg_raid</filename> を構成し、<filename>vg_raid</filename> から保護したい内容用の LV を分割することも可能でした。それにも関わらず、なぜ 3 種類の RAID-1 ボリュームを作成したのでしょうか?" |
| 2423 |
|
| 2424 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2425 |
msgid "The rationale for the first split (<filename>md0</filename> vs. the others) is about data safety: data written to both elements of a RAID-1 mirror are exactly the same, and it is therefore possible to bypass the RAID layer and mount one of the disks directly. In case of a kernel bug, for instance, or if the LVM metadata become corrupted, it is still possible to boot a minimal system to access critical data such as the layout of disks in the RAID and LVM volumes; the metadata can then be reconstructed and the files can be accessed again, so that the system can be brought back to its nominal state." |
| 2426 |
msgstr "最初の分割 (<filename>md0</filename> とその他) の根本的理由はデータの安全性を考慮したためです。つまり RAID-1 ミラーを構成する要素に書き込まれるデータは要素同士で全く同じだからです。そのため RAID 層を迂回し、RAID-1 ミラーを構成する 1 台のディスクだけを直接マウントすることが可能です。すなわち、カーネルにバグがあったり LVM メタ情報が破壊されたりした場合でも、RAID と LVM ボリュームに含まれるディスクの配置などの重要なデータにアクセスするために最小限のシステムを起動することが可能ということです。そして、このメタ情報を再構成したりファイルにアクセスしたりすることが可能です。こうすることで、システムを正常状態に戻すことが可能です。" |
| 2427 |
|
| 2428 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2429 |
#, fuzzy |
| 2430 |
#| msgid "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." |
| 2431 |
msgid "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." |
| 2432 |
msgstr "2 番目の分割 (<filename>md1</filename> と <filename>md2</filename>) の根本的理由は明確というわけではありませんが、将来の不明確さを認めていることに関連します。動画編集用ワークステーションを最初に組み上げる時点で、要求される正確なストレージサイズを完全な精度で知ることは不可能です。それどころか、ストレージサイズは時間経過に従い増加するかもしれません。今回の場合、ビデオ素材用の <filename>lv_rushes</filename> と編集済みビデオクリップ用の <filename>lv_movies</filename> に対して実際に要求されるストレージサイズを事前に知ることはできません。とても大きな量の素材を必要とするクリップを <filename>lv_rushes</filename> に保存する必要があり、さらに冗長性データ用 VG である <filename>vg_raid</filename> のまだ半分以上が未使用状態ならば、<filename>vg_raid</filename> から未使用領域を再利用することが可能です。具体的には <filename>vg_raid</filename> の構成要素から片方の PV (たとえば <filename>md2</filename>) を削除し、<filename>md2</filename> を <filename>vg_bulk</filename> を構成する PV として初期化するか (予想される作業時間が一時的な性能の低下を許容できる程度に十分短い場合に限ります)、<filename>md2</filename> の RAID-1 セットアップを破棄してその構成要素である <filename>sda6</filename> と <filename>sdc6</filename> を <filename>vg_bulk</filename> を構成する PV として初期化する (この場合 100 GB ではなく 200 GB の増加になります) ことが可能です。そして <filename>lv_rushes</filename> を必要に応じて増加させることが可能です。" |
| 2433 |
|
| 2434 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2435 |
msgid "<primary>virtualization</primary>" |
| 2436 |
msgstr "<primary sortas=\"カソウカ\">仮想化</primary>" |
| 2437 |
|
| 2438 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2439 |
msgid "Virtualization is one of the most major advances in the recent years of computing. The term covers various abstractions and techniques simulating virtual computers with a variable degree of independence on the actual hardware. One physical server can then host several systems working at the same time and in isolation. Applications are many, and often derive from this isolation: test environments with varying configurations for instance, or separation of hosted services across different virtual machines for security." |
| 2440 |
msgstr "仮想化は最近のコンピューティングにおける最も大きな進歩の 1 つです。仮想化という用語は、実際のハードウェアに対するさまざまな独立性の度合いを持つ仮想コンピュータを模倣するさまざまな抽象化と技術を指します。1 台の物理的なサーバが同時かつ隔離された状態で動く複数のシステムをホストすることが可能です。仮想化アプリケーションは数多く存在し、隔離された仮想システムを使うことができます。たとえば、さまざまに設定されたテスト環境を作ったり、安全性を確保する目的で異なる仮想マシン間でホストされたサービスを分離したりすることが可能です。" |
| 2441 |
|
| 2442 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2443 |
msgid "There are multiple virtualization solutions, each with its own pros and cons. This book will focus on Xen, LXC, and KVM, but other noteworthy implementations include the following:" |
| 2444 |
msgstr "複数の仮想化ソリューションが存在し、それぞれが利点と欠点を持っています。本書では Xen、LXC、KVM に注目しますが、他にも以下のような注目すべき実装が存在します。" |
| 2445 |
|
| 2446 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2447 |
#, fuzzy |
| 2448 |
#| msgid "<primary>LXC</primary>" |
| 2449 |
msgid "<primary>Xen</primary>" |
| 2450 |
msgstr "<primary>LXC</primary>" |
| 2451 |
|
| 2452 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2453 |
#, fuzzy |
| 2454 |
#| msgid "<primary>LVM</primary>" |
| 2455 |
msgid "<primary>VMWare</primary>" |
| 2456 |
msgstr "<primary>LVM</primary>" |
| 2457 |
|
| 2458 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2459 |
#, fuzzy |
| 2460 |
#| msgid "<primary>Nagios</primary>" |
| 2461 |
msgid "<primary>Bochs</primary>" |
| 2462 |
msgstr "<primary>Nagios</primary>" |
| 2463 |
|
| 2464 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2465 |
#, fuzzy |
| 2466 |
#| msgid "<primary>LVM</primary>" |
| 2467 |
msgid "<primary>QEMU</primary>" |
| 2468 |
msgstr "<primary>LVM</primary>" |
| 2469 |
|
| 2470 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2471 |
#, fuzzy |
| 2472 |
#| msgid "<primary>virtualization</primary>" |
| 2473 |
msgid "<primary>VirtualBox</primary>" |
| 2474 |
msgstr "<primary sortas=\"カソウカ\">仮想化</primary>" |
| 2475 |
|
| 2476 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2477 |
msgid "<primary>KVM</primary>" |
| 2478 |
msgstr "<primary>KVM</primary>" |
| 2479 |
|
| 2480 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2481 |
msgid "<primary>LXC</primary>" |
| 2482 |
msgstr "<primary>LXC</primary>" |
| 2483 |
|
| 2484 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2485 |
#, fuzzy |
| 2486 |
#| msgid "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=\"http://www.qemu.org/\" />" |
| 2487 |
msgid "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/\" />" |
| 2488 |
msgstr "QEMU は完全なコンピュータを模倣するソフトウェアエミュレータです。このため QEMU の性能はネイティブに実行した場合の速度には遠くおよびませんが、QEMU を使うことで修正されていなかったり実験的なオペレーティングシステムをエミュレートされたハードウェア上で実行することが可能です。さらに QEMU は異なるハードウェアアーキテクチャをエミュレートすることが可能です。たとえば、<emphasis>amd64</emphasis> システムで <emphasis>arm</emphasis> コンピュータをエミュレートすることが可能です。QEMU はフリーソフトウェアです。<ulink type=\"block\" url=\"http://www.qemu.org/\" />" |
| 2489 |
|
| 2490 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2491 |
msgid "Bochs is another free virtual machine, but it only emulates the x86 architectures (i386 and amd64)." |
| 2492 |
msgstr "Bochs は自由な仮想マシンですが、x86 アーキテクチャ (i386 と amd64) だけをエミュレートすることが可能です。" |
| 2493 |
|
| 2494 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2495 |
#, fuzzy |
| 2496 |
#| msgid "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=\"http://www.vmware.com/\" />" |
| 2497 |
msgid "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/\" />" |
| 2498 |
msgstr "VMWare はプロプライエタリの仮想マシンです。VMWare はこの分野で最も古く、最も広く使われているソフトウェアの 1 つです。VMWare は QEMU とよく似た原理で動いています。VMWare には実行中の仮想マシンのスナップショットなどの高度な機能が含まれています。<ulink type=\"block\" url=\"http://www.vmware.com/\" />" |
| 2499 |
|
| 2500 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2501 |
#, fuzzy |
| 2502 |
#| msgid "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=\"http://www.virtualbox.org/\" />" |
| 2503 |
msgid "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/\" />" |
| 2504 |
msgstr "VirtualBox はほぼ自由なソフトウェアの仮想マシンです (一部の追加的な構成要素はプロプライエタリライセンスの下で利用できます)。残念なことに VirtualBox は Debian の「contrib」セクションにあります。なぜなら VirtualBox にはいくつかのコンパイル済みファイルが含まれ、このファイルを再ビルドするにはプロプライエタリコンパイラが必要だからです。また、今のところ VirtualBox を含めることができるのは Debian 不安定版に限られます。なぜなら Oracle の方針に従うと Debian 安定版に VirtualBox を含めることはできないからです (<ulink url=\"https://bugs.debian.org/794466\">#794466</ulink> を参照してください)。VirtualBox は VMWare よりも歴史が浅く、i386 と amd64 アーキテクチャだけをサポートします。しかしながら、VirtualBox はスナップショットやその他の興味深い機能を備えています。<ulink type=\"block\" url=\"http://www.virtualbox.org/\" />" |
| 2505 |
|
| 2506 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2507 |
#, fuzzy |
| 2508 |
#| msgid "<emphasis>GOING FURTHER</emphasis> Mass virtualization" |
| 2509 |
msgid "<emphasis>HARDWARE</emphasis> Virtualization support" |
| 2510 |
msgstr "<emphasis>GOING FURTHER</emphasis> 大量の仮想化" |
| 2511 |
|
| 2512 |
msgid "Some computers might not have hardware virtualization support; when they do, it should be enabled in the BIOS." |
| 2513 |
msgstr "" |
| 2514 |
|
| 2515 |
msgid "To know if you have virtualization support enabled, you can check if the relevant flag is enabled with <command>grep</command>. If the following command for your processor returns some text, you already have virtualization support enabled:" |
| 2516 |
msgstr "" |
| 2517 |
|
| 2518 |
msgid "For Intel processors you can execute <command>grep vmx /proc/cpuinfo</command> to check for Intel's Virtual Machine Extensions." |
| 2519 |
msgstr "" |
| 2520 |
|
| 2521 |
msgid "For AMD processors you can execute <command>grep svm /proc/cpuinfo</command> to check for AMD's Secure Virtual Machine." |
| 2522 |
msgstr "" |
| 2523 |
|
| 2524 |
msgid "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." |
| 2525 |
msgstr "" |
| 2526 |
|
| 2527 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2528 |
#, fuzzy |
| 2529 |
#| msgid "<primary>virtualization</primary>" |
| 2530 |
msgid "<primary>paravirtualization</primary>" |
| 2531 |
msgstr "<primary sortas=\"カソウカ\">仮想化</primary>" |
| 2532 |
|
| 2533 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2534 |
#, fuzzy |
| 2535 |
#| msgid "<primary>libvirt</primary>" |
| 2536 |
msgid "<primary>hypervisor</primary>" |
| 2537 |
msgstr "<primary>libvirt</primary>" |
| 2538 |
|
| 2539 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2540 |
msgid "Xen <indexterm><primary>Xen</primary></indexterm> is a “paravirtualization” solution. It introduces a thin abstraction layer, called a “hypervisor”, between the hardware and the upper systems; this acts as a referee that controls access to hardware from the virtual machines. However, it only handles a few of the instructions, the rest is directly executed by the hardware on behalf of the systems. The main advantage is that performances are not degraded, and systems run close to native speed; the drawback is that the kernels of the operating systems one wishes to use on a Xen hypervisor need to be adapted to run on Xen." |
| 2541 |
msgstr "Xen<indexterm><primary>Xen</primary></indexterm> は「準仮想化」ソリューションです。Xen には薄い抽象化層が含まれ、この抽象化層は「ハイパーバイザ」と呼ばれ、ハードウェアとその上にあるシステムの間に位置します。さらにハイパーバイザは審判員として振る舞い、仮想マシンからハードウェアへのアクセスを制御します。しかしながら、Xen ハイパーバイザは命令のほんの一部だけを取り扱い、残りは Xen ハイパーバイザではなくハードウェアによって直接的に実行されます。こうすることによる主な有効性は性能が低下せず、システムがネイティブ速度に迫る性能を発揮するという点です。一方で欠点は Xen ハイパーバイザ上でオペレーティングシステムを実行するには実行されるオペレーティングシステムのカーネルを修正しなければいけないという点です。" |
| 2542 |
|
| 2543 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2544 |
#, fuzzy |
| 2545 |
#| msgid "<primary>deployment</primary>" |
| 2546 |
msgid "<primary>dom0</primary>" |
| 2547 |
msgstr "<primary sortas=\"ハイビ\">配備</primary>" |
| 2548 |
|
| 2549 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2550 |
#, fuzzy |
| 2551 |
#| msgid "<primary>deployment</primary>" |
| 2552 |
msgid "<primary>domU</primary>" |
| 2553 |
msgstr "<primary sortas=\"ハイビ\">配備</primary>" |
| 2554 |
|
| 2555 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2556 |
#, fuzzy |
| 2557 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2558 |
msgid "<primary>virtualization</primary><secondary>host</secondary>" |
| 2559 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2560 |
|
| 2561 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2562 |
#, fuzzy |
| 2563 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2564 |
msgid "<primary>virtualization</primary><secondary>guest</secondary>" |
| 2565 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2566 |
|
| 2567 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2568 |
#, fuzzy |
| 2569 |
#| msgid "Let's spend some time on terms. The hypervisor is the lowest layer, that runs directly on the hardware, even below the kernel. This hypervisor can split the rest of the software across several <emphasis>domains</emphasis>, which can be seen as so many virtual machines. One of these domains (the first one that gets started) is known as <emphasis>dom0</emphasis>, and has a special role, since only this domain can control the hypervisor and the execution of other domains. These other domains are known as <emphasis>domU</emphasis>. In other words, and from a user point of view, the <emphasis>dom0</emphasis> matches the “host” of other virtualization systems, while a <emphasis>domU</emphasis> can be seen as a “guest”." |
| 2570 |
msgid "Let's spend some time on terms. The hypervisor is the lowest layer, which runs directly on the hardware, even below the kernel. This hypervisor can split the rest of the software across several <emphasis>domains</emphasis>, which can be seen as so many virtual machines. One of these domains (the first one that gets started) is known as <emphasis>dom0</emphasis>, and has a special role, since only this domain can control the hypervisor and the execution of other domains. These other domains are known as <emphasis>domU</emphasis>. In other words, and from a user point of view, the <emphasis>dom0</emphasis> matches the “host” of other virtualization systems, while a <emphasis>domU</emphasis> can be seen as a “guest”." |
| 2571 |
msgstr "用語の解説に少し時間を割きましょう。Xen ハイパーバイザはカーネルよりも下層の最も低い層に位置し、ハードウェア上で直接動きます。Xen ハイパーバイザは残りのソフトウェアをいくつかの<emphasis>ドメイン</emphasis>に分割することが可能で、<emphasis>ドメイン</emphasis>は多数の仮想マシンと考えられます。これらのドメインの 1 つ (最初に起動されたもの) は <emphasis>dom0</emphasis> と呼ばれ、特別な役割を担います。なぜなら、<emphasis>dom0</emphasis> だけが Xen ハイパーバイザを制御することが可能だからです。他のドメインは <emphasis>domU</emphasis> として知られています。ユーザ視点で言い換えれば、<emphasis>dom0</emphasis> は他の仮想システムにおける「ホスト」、これに対して <emphasis>domU</emphasis> は「ゲスト」になります。" |
| 2572 |
|
| 2573 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2574 |
msgid "<emphasis>CULTURE</emphasis> Xen and the various versions of Linux" |
| 2575 |
msgstr "<emphasis>CULTURE</emphasis> Xen と Linux のさまざまなバージョン" |
| 2576 |
|
| 2577 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2578 |
# Tag: PTAL; |
| 2579 |
# Ref: https://lwn.net/Articles/194543/ |
| 2580 |
msgid "Xen was initially developed as a set of patches that lived out of the official tree, and not integrated to the Linux kernel. At the same time, several upcoming virtualization systems (including KVM) required some generic virtualization-related functions to facilitate their integration, and the Linux kernel gained this set of functions (known as the <emphasis>paravirt_ops</emphasis> or <emphasis>pv_ops</emphasis> interface). Since the Xen patches were duplicating some of the functionality of this interface, they couldn't be accepted officially." |
| 2581 |
msgstr "当初 Xen は Linux 公式ツリーの外部パッチとして開発され、Linux カーネルに組み込まれていませんでした。これと同時期に、複数の次世代仮想化システム (KVM など) は Linux カーネルへの組み込みを簡単にするためにいくつかの包括的な仮想化関連関数を必要としており、さらに Linux カーネルが (<emphasis>paravirt_ops</emphasis> または <emphasis>pv_ops</emphasis> インターフェースとして知られる) 一連の仮想化関連関数を獲得しました。Xen のパッチはこのインターフェースのいくつかの機能を複製していたため、Xen のパッチは公式に受け入れられませんでした。" |
| 2582 |
|
| 2583 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2584 |
#, fuzzy |
| 2585 |
#| msgid "Xensource, the company behind Xen, therefore had to port Xen to this new framework, so that the Xen patches could be merged into the official Linux kernel. That meant a lot of code rewrite, and although Xensource soon had a working version based on the paravirt_ops interface, the patches were only progressively merged into the official kernel. The merge was completed in Linux 3.0. <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/XenParavirtOps\" />" |
| 2586 |
msgid "Xensource, the company behind Xen, therefore had to port Xen to this new framework, so that the Xen patches could be merged into the official Linux kernel. That meant a lot of code rewrite, and although Xensource soon had a working version based on the paravirt_ops interface, the patches were only progressively merged into the official kernel. The merge was completed in Linux 3.0. <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/XenParavirtOps\" />" |
| 2587 |
msgstr "このため、Xen を影で支える会社の Xensource は新しく Linux カーネルに取り込まれた仮想化関連関数を使って Xen を移植しなければいけませんでした。この移植作業により、Xen のパッチを公式の Linux カーネルに取り込むことが可能になりました。この移植作業は多くのコードを書き換えることを意味していました。Xensource はすぐに paravirt_ops インターフェースを使って評価版を作ったにも関わらず、Xen のパッチを公式カーネルにマージする作業はゆっくりと進みました。マージか完了したのは Linux 3.0 です。<ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/XenParavirtOps\" />" |
| 2588 |
|
| 2589 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2590 |
#, fuzzy |
| 2591 |
#| msgid "Since <emphasis role=\"distribution\">Jessie</emphasis> is based on version 3.16 of the Linux kernel, the standard <emphasis role=\"pkg\">linux-image-686-pae</emphasis> and <emphasis role=\"pkg\">linux-image-amd64</emphasis> packages include the necessary code, and the distribution-specific patching that was required for <emphasis role=\"distribution\">Squeeze</emphasis> and earlier versions of Debian is no more. <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/Xen_Kernel_Feature_Matrix\" />" |
| 2592 |
msgid "Since <emphasis role=\"distribution\">Jessie</emphasis> is based on version 3.16 of the Linux kernel, the standard <emphasis role=\"pkg\">linux-image-686-pae</emphasis> and <emphasis role=\"pkg\">linux-image-amd64</emphasis> packages include the necessary code, and the distribution-specific patching that was required for <emphasis role=\"distribution\">Squeeze</emphasis> and earlier versions of Debian is no more. <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/Xen_Kernel_Feature_Matrix\" />" |
| 2593 |
msgstr "<emphasis role=\"distribution\">Jessie</emphasis> は Linux カーネルのバージョン 3.16 に基づくため、標準的な <emphasis role=\"pkg\">linux-image-686-pae</emphasis> と <emphasis role=\"pkg\">linux-image-amd64</emphasis> パッケージには Xen を動作させるために必要なコードが含まれます。Debian の <emphasis role=\"distribution\">Squeeze</emphasis> およびそれ以前のバージョンで必要とされていたディストリビューションに特有のパッチ作業はもはや必要ありません。<ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/Xen_Kernel_Feature_Matrix\" />" |
| 2594 |
|
| 2595 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2596 |
msgid "<emphasis>CULTURE</emphasis> Xen and non-Linux kernels" |
| 2597 |
msgstr "<emphasis>CULTURE</emphasis> Xen と非 Linux カーネル" |
| 2598 |
|
| 2599 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2600 |
#, fuzzy |
| 2601 |
#| msgid "Xen requires modifications to all the operating systems one wants to run on it; not all kernels have the same level of maturity in this regard. Many are fully-functional, both as dom0 and domU: Linux 3.0 and later, NetBSD 4.0 and later, and OpenSolaris. Others only work as a domU. You can check the status of each operating system in the Xen wiki: <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/Dom0_Kernels_for_Xen\" /> <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/DomU_Support_for_Xen\" />" |
| 2602 |
msgid "Xen requires modifications to all the operating systems one wants to run on it; not all kernels have the same level of maturity in this regard. Many are fully-functional, both as dom0 and domU: Linux 3.0 and later, NetBSD 4.0 and later, and OpenSolaris. Others only work as a domU. You can check the status of each operating system in the Xen wiki: <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/Dom0_Kernels_for_Xen\" /> <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/DomU_Support_for_Xen\" />" |
| 2603 |
msgstr "Xen 上でオペレーティングシステムを動作させるには、いかなるオペレーティングシステムであってもそれを修正する必要があります。さらに、すべてのオペレーティングシステムのカーネルが修正点に関して同じ程度の成熟度を持っているとは限りません。多くのオペレーティングシステムは dom0 および domU として完全に動作します。具体的に言えば、Linux 3.0 とそれ以降、NetBSD 4.0 とそれ以降、OpenSolaris は dom0 および domU として完全に動作します。また、他のオペレーティングシステムは dom0 としては動作せず domU として動作します。dom0 および domU として動作するオペレーティングシステムの状況を確認するには Xen のウィキに含まれる該当ページをご覧ください。<ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/Dom0_Kernels_for_Xen\" /><ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/DomU_Support_for_Xen\" />" |
| 2604 |
|
| 2605 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2606 |
# Tag: PTAL; |
| 2607 |
msgid "However, if Xen can rely on the hardware functions dedicated to virtualization (which are only present in more recent processors), even non-modified operating systems can run as domU (including Windows)." |
| 2608 |
msgstr "しかしながら、Xen で仮想化専用のハードウェア機能 (最近のプロセッサだけが搭載した機能) に依存するオペレーティングシステムを動作させる場合や、修正されていないオペレーティングシステム (Windows など) を動作させる場合、そのオペレーティングシステムは domU としてのみ動作します。" |
| 2609 |
|
| 2610 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2611 |
msgid "<emphasis>NOTE</emphasis> Architectures compatible with Xen" |
| 2612 |
msgstr "<emphasis>NOTE</emphasis> Xen 互換のアーキテクチャ" |
| 2613 |
|
| 2614 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2615 |
msgid "Xen is currently only available for the i386, amd64, arm64 and armhf architectures." |
| 2616 |
msgstr "現在のところ、Xen を利用できるのは i386、amd64、arm64、armhf アーキテクチャだけです。" |
| 2617 |
|
| 2618 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2619 |
msgid "Using Xen under Debian requires three components:" |
| 2620 |
msgstr "Debian の下で Xen を使うには 3 つの要素が必要です。" |
| 2621 |
|
| 2622 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2623 |
#, fuzzy |
| 2624 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2625 |
msgid "<primary><emphasis role=\"pkg\">xen-hypervisor</emphasis></primary>" |
| 2626 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2627 |
|
| 2628 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2629 |
# Tag: L-CFMD; |
| 2630 |
#, fuzzy |
| 2631 |
#| msgid "The hypervisor itself. According to the available hardware, the appropriate package will be either <emphasis role=\"pkg\">xen-hypervisor-4.4-amd64</emphasis>, <emphasis role=\"pkg\">xen-hypervisor-4.4-armhf</emphasis>, or <emphasis role=\"pkg\">xen-hypervisor-4.4-arm64</emphasis>." |
| 2632 |
msgid "The hypervisor itself. According to the available hardware, the appropriate package providing <emphasis role=\"pkg\">xen-hypervisor</emphasis> will be either <emphasis role=\"pkg\">xen-hypervisor-4.14-amd64</emphasis>, <emphasis role=\"pkg\">xen-hypervisor-4.14-armhf</emphasis>, or <emphasis role=\"pkg\">xen-hypervisor-4.14-arm64</emphasis>." |
| 2633 |
msgstr "Xen ハイパーバイザ自身。適切なパッケージは利用できるハードウェアによって決まります。すなわち <emphasis role=\"pkg\">xen-hypervisor-4.4-amd64</emphasis>、<emphasis role=\"pkg\">xen-hypervisor-4.4-armhf</emphasis>、<emphasis role=\"pkg\">xen-hypervisor-4.4-arm64</emphasis> のうちどれか 1 つが必要です。" |
| 2634 |
|
| 2635 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2636 |
#, fuzzy |
| 2637 |
#| msgid "A kernel that runs on that hypervisor. Any kernel more recent than 3.0 will do, including the 3.16 version present in <emphasis role=\"distribution\">Jessie</emphasis>." |
| 2638 |
msgid "A kernel that runs on that hypervisor. Any kernel more recent than 3.0 will do, including the 5.10 version present in <emphasis role=\"distribution\">Bullseye</emphasis>." |
| 2639 |
msgstr "ハイパーバイザ上で実行するカーネル。バージョン 3.0 より新しい Linux カーネルが動作します。<emphasis role=\"distribution\">Jessie</emphasis> に含まれる Linux カーネルのバージョンは 3.16 なのでこれも動作します。" |
| 2640 |
|
| 2641 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2642 |
# Tag: L-CFMD; |
| 2643 |
msgid "The i386 architecture also requires a standard library with the appropriate patches taking advantage of Xen; this is in the <emphasis role=\"pkg\">libc6-xen</emphasis> package." |
| 2644 |
msgstr "さらに i386 アーキテクチャでは、Xen を活用するための適切なパッチを組み込んだ標準的なライブラリが必要です。このライブラリは <emphasis role=\"pkg\">libc6-xen</emphasis> パッケージに含まれます。" |
| 2645 |
|
| 2646 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2647 |
#, fuzzy |
| 2648 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2649 |
msgid "<primary><emphasis role=\"pkg\">xen-utils</emphasis></primary>" |
| 2650 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2651 |
|
| 2652 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2653 |
# Tag: L-CFMD; |
| 2654 |
#, fuzzy |
| 2655 |
#| msgid "In order to avoid the hassle of selecting these components by hand, a few convenience packages (such as <emphasis role=\"pkg\">xen-linux-system-amd64</emphasis>) have been made available; they all pull in a known-good combination of the appropriate hypervisor and kernel packages. The hypervisor also brings <emphasis role=\"pkg\">xen-utils-4.4</emphasis>, which contains tools to control the hypervisor from the dom0. This in turn brings the appropriate standard library. During the installation of all that, configuration scripts also create a new entry in the Grub bootloader menu, so as to start the chosen kernel in a Xen dom0. Note however that this entry is not usually set to be the first one in the list, and will therefore not be selected by default. If that is not the desired behavior, the following commands will change it:" |
| 2656 |
msgid "The hypervisor also brings <emphasis role=\"pkg\">xen-utils-4.14</emphasis>, which contains tools to control the hypervisor from the dom0. This in turn brings the appropriate standard library. During the installation of all that, configuration scripts also create a new entry in the GRUB bootloader menu, so as to start the chosen kernel in a Xen dom0. Note, however, that this entry is not usually set to be the first one in the list, but it will be selected by default." |
| 2657 |
msgstr "複数の構成要素を手作業で選択するという煩わしさを避けるために、いくつかの便利なパッケージ (<emphasis role=\"pkg\">xen-linux-system-amd64</emphasis> など) が用意されています。これらのパッケージをインストールすることで、適切な Xen ハイパーバイザとカーネルパッケージが既知の良い組み合わせで導入されます。ここで導入される Xen ハイパーバイザには <emphasis role=\"pkg\">xen-utils-4.4</emphasis> が含まれます。<emphasis role=\"pkg\">xen-utils-4.4</emphasis> パッケージには dom0 からハイパーバイザを操作するためのツールが含まれます。同様に、<emphasis role=\"pkg\">xen-utils-4.4</emphasis> パッケージには適切な標準的ライブラリが含まれます。すべてのインストール中に、設定スクリプトは Grub ブートローダメニューに新しいエントリを作成します。こうすることで Xen dom0 から選択されたカーネルを開始することが可能です。しかしながら、通常このエントリはリストの最初に置かれないため、デフォルトで選択されません。この点に注意してください。これを望まない場合、以下のコマンドを使って変更してください。" |
| 2658 |
|
| 2659 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2660 |
msgid "Once these prerequisites are installed, the next step is to test the behavior of the dom0 by itself; this involves a reboot to the hypervisor and the Xen kernel. The system should boot in its standard fashion, with a few extra messages on the console during the early initialization steps." |
| 2661 |
msgstr "これらの前提要件をインストールしたら、次に dom0 の挙動をテストします。テストを行うには、Xen ハイパーバイザと Xen カーネルの再起動が必要です。システムは標準的な方法で起動するべきです。初期化の早い段階でコンソールにいくつかの追加的メッセージが表示されます。" |
| 2662 |
|
| 2663 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2664 |
#, fuzzy |
| 2665 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2666 |
msgid "<primary><emphasis role=\"pkg\">xen-tools</emphasis></primary>" |
| 2667 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2668 |
|
| 2669 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2670 |
#, fuzzy |
| 2671 |
#| msgid "<primary><command>xe</command></primary>" |
| 2672 |
msgid "<primary><command>xen-create-image</command></primary>" |
| 2673 |
msgstr "<primary><command>xe</command></primary>" |
| 2674 |
|
| 2675 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2676 |
#, fuzzy |
| 2677 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2678 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/xen-tools/xen-tools.conf</filename></secondary>" |
| 2679 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2680 |
|
| 2681 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2682 |
# Tag: L-CFMD; |
| 2683 |
msgid "Now is the time to actually install useful systems on the domU systems, using the tools from <emphasis role=\"pkg\">xen-tools</emphasis>. This package provides the <command>xen-create-image</command> command, which largely automates the task. The only mandatory parameter is <literal>--hostname</literal>, giving a name to the domU; other options are important, but they can be stored in the <filename>/etc/xen-tools/xen-tools.conf</filename> configuration file, and their absence from the command line doesn't trigger an error. It is therefore important to either check the contents of this file before creating images, or to use extra parameters in the <command>xen-create-image</command> invocation. Important parameters of note include the following:" |
| 2684 |
msgstr "これで、実用システムを domU システムに実際にインストールできるようになりました。これを行うには <emphasis role=\"pkg\">xen-tools</emphasis> に含まれるツールを使います。<emphasis role=\"pkg\">xen-tools</emphasis> パッケージには <command>xen-create-image</command> コマンドが含まれます。<command>xen-create-image</command> コマンドはインストール作業の大部分を自動化します。必須のパラメータは <literal>--hostname</literal> だけで、このパラメータは domU の名前を設定します。他のオプションは重要ですが、オプションを <filename>/etc/xen-tools/xen-tools.conf</filename> 設定ファイルに保存することが可能です。そして、コマンドラインでオプションを指定しなくてもエラーは起きません。このため、イメージを作る前にこのファイルの内容を確認するか、<command>xen-create-image</command> の実行時に追加的パラメータを使うことが重要です。以下に注目すべき重要なパラメータを示します。" |
| 2685 |
|
| 2686 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2687 |
# Tag: L-CFMD; |
| 2688 |
msgid "<literal>--memory</literal>, to specify the amount of RAM dedicated to the newly created system;" |
| 2689 |
msgstr "<literal>--memory</literal>。新たに作成する domU システム専用の RAM のサイズを指定します。" |
| 2690 |
|
| 2691 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2692 |
# Tag: L-CFMD; |
| 2693 |
msgid "<literal>--size</literal> and <literal>--swap</literal>, to define the size of the “virtual disks” available to the domU;" |
| 2694 |
msgstr "<literal>--size</literal> と <literal>--swap</literal>。domU で利用できる「仮想ディスク」のサイズを定義します。" |
| 2695 |
|
| 2696 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2697 |
# Tag: L-CFMD; |
| 2698 |
#, fuzzy |
| 2699 |
#| msgid "<primary><command>debconf</command></primary>" |
| 2700 |
msgid "<primary><command>debootstrap</command></primary>" |
| 2701 |
msgstr "<primary><command>debconf</command></primary>" |
| 2702 |
|
| 2703 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2704 |
# Tag: L-CFMD; |
| 2705 |
#, fuzzy |
| 2706 |
#| msgid "<literal>--debootstrap</literal>, to cause the new system to be installed with <command>debootstrap</command>; in that case, the <literal>--dist</literal> option will also most often be used (with a distribution name such as <emphasis role=\"distribution\">jessie</emphasis>)." |
| 2707 |
msgid "<literal>--debootstrap-cmd</literal>, to specify the which debootstrap command is used. The default is <command>debootstrap</command> if debootstrap and cdebootstrap are installed. In that case, the <literal>--dist</literal> option will also most often be used (with a distribution name such as <emphasis role=\"distribution\">bullseye</emphasis>)." |
| 2708 |
msgstr "<literal>--debootstrap</literal>。<command>debootstrap</command> を使って新しいシステムをインストールします。このオプションを使う場合、<literal>--dist</literal> オプション (ディストリビューションの名前、たとえば <emphasis role=\"distribution\">jessie</emphasis>) を一緒に使うことが多いです。" |
| 2709 |
|
| 2710 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2711 |
# Tag: L-CFMD; |
| 2712 |
msgid "<emphasis>GOING FURTHER</emphasis> Installing a non-Debian system in a domU" |
| 2713 |
msgstr "<emphasis>GOING FURTHER</emphasis> 非 Debian システムを domU にインストール" |
| 2714 |
|
| 2715 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2716 |
# Tag: L-CFMD; |
| 2717 |
msgid "In case of a non-Linux system, care should be taken to define the kernel the domU must use, using the <literal>--kernel</literal> option." |
| 2718 |
msgstr "非 Linux システムを domU にインストールする場合、<literal>--kernel</literal> オプションを使って、domU で使うカーネルを定義しなければいけない点に注意してください。" |
| 2719 |
|
| 2720 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2721 |
# Tag: L-CFMD; |
| 2722 |
msgid "<literal>--dhcp</literal> states that the domU's network configuration should be obtained by DHCP while <literal>--ip</literal> allows defining a static IP address." |
| 2723 |
msgstr "<literal>--dhcp</literal>。domU のネットワーク設定を DHCP で取得することを宣言します。対して、<literal>--ip</literal> は静的 IP アドレスを定義します。" |
| 2724 |
|
| 2725 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2726 |
#, fuzzy |
| 2727 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2728 |
msgid "<primary>LVM</primary><secondary>Xen</secondary>" |
| 2729 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2730 |
|
| 2731 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2732 |
# Tag: L-CFMD; |
| 2733 |
msgid "Lastly, a storage method must be chosen for the images to be created (those that will be seen as hard disk drives from the domU). The simplest method, corresponding to the <literal>--dir</literal> option, is to create one file on the dom0 for each device the domU should be provided. For systems using LVM, the alternative is to use the <literal>--lvm</literal> option, followed by the name of a volume group; <command>xen-create-image</command> will then create a new logical volume inside that group, and this logical volume will be made available to the domU as a hard disk drive." |
| 2734 |
msgstr "最後に、作成されるイメージ (domU からはハードディスクドライブに見えるイメージ) の保存方法を選択します。最も簡単な方法は、<literal>--dir</literal> オプションを使い、各 domU を格納するデバイス用のファイルを dom0 上に作成する方法です。LVM を使っているシステムでは、<literal>--lvm</literal> オプションを使い、VG の名前を指定しても良いでしょう。この場合 <command>xen-create-image</command> は指定された VG から新しい LV を分割し、この LV をハードディスクドライブとして domU から利用できるようにします。" |
| 2735 |
|
| 2736 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2737 |
msgid "<emphasis>NOTE</emphasis> Storage in the domU" |
| 2738 |
msgstr "<emphasis>NOTE</emphasis> domU 内のストレージ" |
| 2739 |
|
| 2740 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2741 |
# Tag: L-CFMD; |
| 2742 |
msgid "Entire hard disks can also be exported to the domU, as well as partitions, RAID arrays or pre-existing LVM logical volumes. These operations are not automated by <command>xen-create-image</command>, however, so editing the Xen image's configuration file is in order after its initial creation with <command>xen-create-image</command>." |
| 2743 |
msgstr "ハードディスク全体、パーティション、RAID アレイ、既存の LVM の LV を domU に書き出すことも可能です。<command>xen-create-image</command> を使ってもこれらの操作を自動化することは不可能ですが、<command>xen-create-image</command> を使って Xen イメージの設定ファイルを作成した後にその設定ファイルを編集することで対応する操作が可能です。" |
| 2744 |
|
| 2745 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2746 |
msgid "Once these choices are made, we can create the image for our future Xen domU:" |
| 2747 |
msgstr "これらを選んだ後、将来の Xen domU 用のイメージを作成することが可能です。" |
| 2748 |
|
| 2749 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2750 |
# Tag: L-CFMD; |
| 2751 |
#, fuzzy |
| 2752 |
#| msgid "" |
| 2753 |
#| "<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=jessie --role=udev</userinput>\n" |
| 2754 |
#| "<computeroutput>\n" |
| 2755 |
#| "[...]\n" |
| 2756 |
#| "General Information\n" |
| 2757 |
#| "--------------------\n" |
| 2758 |
#| "Hostname : testxen\n" |
| 2759 |
#| "Distribution : jessie\n" |
| 2760 |
#| "Mirror : http://ftp.debian.org/debian/\n" |
| 2761 |
#| "Partitions : swap 128Mb (swap)\n" |
| 2762 |
#| " / 2G (ext3)\n" |
| 2763 |
#| "Image type : sparse\n" |
| 2764 |
#| "Memory size : 128Mb\n" |
| 2765 |
#| "Kernel path : /boot/vmlinuz-3.16.0-4-amd64\n" |
| 2766 |
#| "Initrd path : /boot/initrd.img-3.16.0-4-amd64\n" |
| 2767 |
#| "[...]\n" |
| 2768 |
#| "Logfile produced at:\n" |
| 2769 |
#| " /var/log/xen-tools/testxen.log\n" |
| 2770 |
#| "\n" |
| 2771 |
#| "Installation Summary\n" |
| 2772 |
#| "---------------------\n" |
| 2773 |
#| "Hostname : testxen\n" |
| 2774 |
#| "Distribution : jessie\n" |
| 2775 |
#| "MAC Address : 00:16:3E:8E:67:5C\n" |
| 2776 |
#| "IP-Address(es) : dynamic\n" |
| 2777 |
#| "RSA Fingerprint : 0a:6e:71:98:95:46:64:ec:80:37:63:18:73:04:dd:2b\n" |
| 2778 |
#| "Root Password : adaX2jyRHNuWm8BDJS7PcEJ\n" |
| 2779 |
#| "</computeroutput>" |
| 2780 |
msgid "" |
| 2781 |
"<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=bullseye --role=udev\n" |
| 2782 |
"</userinput><computeroutput>\n" |
| 2783 |
"General Information\n" |
| 2784 |
"--------------------\n" |
| 2785 |
"Hostname : testxen\n" |
| 2786 |
"Distribution : bullseye\n" |
| 2787 |
"Mirror : http://deb.debian.org/debian\n" |
| 2788 |
"Partitions : swap 512M (swap)\n" |
| 2789 |
" / 2G (ext4)\n" |
| 2790 |
"Image type : sparse\n" |
| 2791 |
"Memory size : 256M\n" |
| 2792 |
"Bootloader : pygrub\n" |
| 2793 |
"\n" |
| 2794 |
"[...]\n" |
| 2795 |
"Logfile produced at:\n" |
| 2796 |
"\t /var/log/xen-tools/testxen.log\n" |
| 2797 |
"\n" |
| 2798 |
"Installation Summary\n" |
| 2799 |
"---------------------\n" |
| 2800 |
"Hostname : testxen\n" |
| 2801 |
"Distribution : bullseye\n" |
| 2802 |
"MAC Address : 00:16:3E:C2:07:EE\n" |
| 2803 |
"IP Address(es) : dynamic\n" |
| 2804 |
"SSH Fingerprint : SHA256:K+0QjpGzZOacLZ3jX4gBwp0mCESt5ceN5HCJZSKWS1A (DSA)\n" |
| 2805 |
"SSH Fingerprint : SHA256:9PnovvGRuTw6dUcEVzzPKTITO0+3Ki1Gs7wu4ke+4co (ECDSA)\n" |
| 2806 |
"SSH Fingerprint : SHA256:X5z84raKBajUkWBQA6MVuanV1OcV2YIeD0NoCLLo90k (ED25519)\n" |
| 2807 |
"SSH Fingerprint : SHA256:VXu6l4tsrCoRsXOqAwvgt57sMRj2qArEbOzHeydvV34 (RSA)\n" |
| 2808 |
"Root Password : FS7CUxsY3xkusv7EkbT9yae\n" |
| 2809 |
"</computeroutput>" |
| 2810 |
msgstr "" |
| 2811 |
"<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=jessie --role=udev</userinput>\n" |
| 2812 |
"<computeroutput>\n" |
| 2813 |
"[...]\n" |
| 2814 |
"General Information\n" |
| 2815 |
"--------------------\n" |
| 2816 |
"Hostname : testxen\n" |
| 2817 |
"Distribution : jessie\n" |
| 2818 |
"Mirror : http://ftp.debian.org/debian/\n" |
| 2819 |
"Partitions : swap 128Mb (swap)\n" |
| 2820 |
" / 2G (ext3)\n" |
| 2821 |
"Image type : sparse\n" |
| 2822 |
"Memory size : 128Mb\n" |
| 2823 |
"Kernel path : /boot/vmlinuz-3.16.0-4-amd64\n" |
| 2824 |
"Initrd path : /boot/initrd.img-3.16.0-4-amd64\n" |
| 2825 |
"[...]\n" |
| 2826 |
"Logfile produced at:\n" |
| 2827 |
" /var/log/xen-tools/testxen.log\n" |
| 2828 |
"\n" |
| 2829 |
"Installation Summary\n" |
| 2830 |
"---------------------\n" |
| 2831 |
"Hostname : testxen\n" |
| 2832 |
"Distribution : jessie\n" |
| 2833 |
"MAC Address : 00:16:3E:8E:67:5C\n" |
| 2834 |
"IP-Address(es) : dynamic\n" |
| 2835 |
"RSA Fingerprint : 0a:6e:71:98:95:46:64:ec:80:37:63:18:73:04:dd:2b\n" |
| 2836 |
"Root Password : adaX2jyRHNuWm8BDJS7PcEJ\n" |
| 2837 |
"</computeroutput>" |
| 2838 |
|
| 2839 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2840 |
msgid "We now have a virtual machine, but it is currently not running (and therefore only using space on the dom0's hard disk). Of course, we can create more images, possibly with different parameters." |
| 2841 |
msgstr "これで仮想マシンが作成されましたが、仮想マシンはまだ実行されていません (このため dom0 のハードディスク上の領域が使われているだけです)。もちろん、異なるパラメータを使ってより多くのイメージを作成することが可能です。" |
| 2842 |
|
| 2843 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2844 |
#, fuzzy |
| 2845 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2846 |
msgid "<primary>Xen</primary><secondary>network models</secondary>" |
| 2847 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2848 |
|
| 2849 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2850 |
#, fuzzy |
| 2851 |
#| msgid "Before turning these virtual machines on, we need to define how they'll be accessed. They can of course be considered as isolated machines, only accessed through their system console, but this rarely matches the usage pattern. Most of the time, a domU will be considered as a remote server, and accessed only through a network. However, it would be quite inconvenient to add a network card for each domU; which is why Xen allows creating virtual interfaces, that each domain can see and use in a standard way. Note that these cards, even though they're virtual, will only be useful once connected to a network, even a virtual one. Xen has several network models for that:" |
| 2852 |
msgid "Before turning these virtual machines on, we need to define how they'll be accessed. They can of course be considered as isolated machines, only accessed through their system console, but this rarely matches the usage pattern. Most of the time, a domU will be considered as a remote server, and accessed only through a network. However, it would be quite inconvenient to add a network card for each domU; which is why Xen allows creating virtual interfaces that each domain can see and use in a standard way. Note that these cards, even though they're virtual, will only be useful once connected to a network, even a virtual one. Xen has several network models for that:" |
| 2853 |
msgstr "仮想マシンを起動する前に、仮想マシンにアクセスする方法を定義します。もちろん仮想マシンは隔離されたマシンですから、仮想マシンにアクセスする唯一の方法はシステムコンソールだけです。しかし、システムコンソールだけで要求を満足できることはほとんどないと言っても過言ではありません。ほとんどの時間、domU はリモートサーバとして機能し、ネットワークを通じてのみアクセスされます。しかしながら、各 domU 専用のネットワークカードを追加するのはかなり不便です。このため Xen は仮想インターフェースの作成機能を備えています。各ドメインは仮想インターフェースを参照し、標準的な方法で使うことが可能です。これらのネットワークカードは仮想的なものですが、ネットワークに接続されている状況下でのみ役に立つという点に注意してください。Xen は以下に挙げる複数のネットワークモデルを備えています。" |
| 2854 |
|
| 2855 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2856 |
msgid "The simplest model is the <emphasis>bridge</emphasis> model; all the eth0 network cards (both in the dom0 and the domU systems) behave as if they were directly plugged into an Ethernet switch." |
| 2857 |
msgstr "最も単純なモデルは <emphasis>bridge</emphasis> モデルです。この場合、すべての eth0 ネットワークカードが (dom0 と domU システムに含まれるものも含めて) 直接的にイーサネットスイッチに接続されているかのように振る舞います。" |
| 2858 |
|
| 2859 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2860 |
msgid "Then comes the <emphasis>routing</emphasis> model, where the dom0 behaves as a router that stands between the domU systems and the (physical) external network." |
| 2861 |
msgstr "2 番目に単純なモデルは <emphasis>routing</emphasis> モデルです。これは dom0 が domU システムと (物理) 外部ネットワークの間に位置するルータとして振る舞うモデルです。" |
| 2862 |
|
| 2863 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2864 |
msgid "Finally, in the <emphasis>NAT</emphasis> model, the dom0 is again between the domU systems and the rest of the network, but the domU systems are not directly accessible from outside, and traffic goes through some network address translation on the dom0." |
| 2865 |
msgstr "最後が <emphasis>NAT</emphasis> モデルです。これは dom0 が domU システムとその他のネットワークの間に位置するモデルですが、domU システムに外部から直接アクセスすることは不可能です。dom0 の行ういくつかのネットワークアドレス変換がトラフィックを仲介します。" |
| 2866 |
|
| 2867 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2868 |
msgid "These three networking nodes involve a number of interfaces with unusual names, such as <filename>vif*</filename>, <filename>veth*</filename>, <filename>peth*</filename> and <filename>xenbr0</filename>. The Xen hypervisor arranges them in whichever layout has been defined, under the control of the user-space tools. Since the NAT and routing models are only adapted to particular cases, we will only address the bridging model." |
| 2869 |
msgstr "これら 3 種類のネットワークノードは <filename>vif*</filename>、<filename>veth*</filename>、<filename>peth*</filename>、<filename>xenbr0</filename> などの独特な名前を付けられた数多くのインターフェースと関係を持ちます。Xen ハイパーバイザは定義された配置に従いユーザ空間ツールの制御の下でインターフェースを準備します。NAT と routing モデルは特定の場合にのみ適合します。このためわれわれは bridge モデルを使います。" |
| 2870 |
|
| 2871 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2872 |
# Ref: http://wiki.xenproject.org/wiki/Xen_Networking; |
| 2873 |
# Ref: http://wiki.xenproject.org/wiki/Network_Configuration_Examples_(Xen_4.1%2B); |
| 2874 |
#, fuzzy |
| 2875 |
#| msgid "The standard configuration of the Xen packages does not change the system-wide network configuration. However, the <command>xend</command> daemon is configured to integrate virtual network interfaces into any pre-existing network bridge (with <filename>xenbr0</filename> taking precedence if several such bridges exist). We must therefore set up a bridge in <filename>/etc/network/interfaces</filename> (which requires installing the <emphasis role=\"pkg\">bridge-utils</emphasis> package, which is why the <emphasis role=\"pkg\">xen-utils-4.4</emphasis> package recommends it) to replace the existing eth0 entry:" |
| 2876 |
msgid "The standard configuration of the Xen packages does not change the system-wide network configuration. However, the <command>xend</command> daemon is configured to integrate virtual network interfaces into any pre-existing network bridge (with <filename>xenbr0</filename> taking precedence if several such bridges exist). We must therefore set up a bridge in <filename>/etc/network/interfaces</filename> (which requires installing the <emphasis role=\"pkg\">bridge-utils</emphasis> package, which is why the <emphasis role=\"pkg\">xen-utils</emphasis> package recommends it) to replace the existing <replaceable>eth0</replaceable> entry (be careful to use the correct network device name):" |
| 2877 |
msgstr "Xen パッケージの標準的な設定はシステム全体のネットワーク設定を変更しません。しかしながら、<command>xend</command> デーモンは既存のネットワークブリッジの中に仮想ネットワークインターフェースを組み込むように設定されています (複数のブリッジが存在する場合 <filename>xenbr0</filename> を優先します)。このためここでは <filename>/etc/network/interfaces</filename> の中にブリッジをセットアップして (<emphasis role=\"pkg\">bridge-utils</emphasis> パッケージをインストールする必要があります。このため <emphasis role=\"pkg\">bridge-utils</emphasis> パッケージは <emphasis role=\"pkg\">xen-utils-4.4</emphasis> パッケージの推奨パッケージになっています)、既存の eth0 エントリを置き替えます。" |
| 2878 |
|
| 2879 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2880 |
#, fuzzy |
| 2881 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2882 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/network/interfaces</filename></secondary>" |
| 2883 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2884 |
|
| 2885 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2886 |
#, fuzzy |
| 2887 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2888 |
msgid "<primary><emphasis role=\"pkg\">bridge-utils</emphasis></primary>" |
| 2889 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2890 |
|
| 2891 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2892 |
#, fuzzy |
| 2893 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2894 |
msgid "<primary>Xen</primary><secondary><literal>xenbr0</literal></secondary>" |
| 2895 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2896 |
|
| 2897 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2898 |
#, fuzzy |
| 2899 |
#| msgid "" |
| 2900 |
#| "auto xenbr0\n" |
| 2901 |
#| "iface xenbr0 inet dhcp\n" |
| 2902 |
#| " bridge_ports eth0\n" |
| 2903 |
#| " bridge_maxwait 0\n" |
| 2904 |
#| " " |
| 2905 |
msgid "" |
| 2906 |
"auto xenbr0\n" |
| 2907 |
"iface xenbr0 inet dhcp\n" |
| 2908 |
" bridge_ports <replaceable>eth0</replaceable>\n" |
| 2909 |
" bridge_maxwait 0" |
| 2910 |
msgstr "" |
| 2911 |
"auto xenbr0\n" |
| 2912 |
"iface xenbr0 inet dhcp\n" |
| 2913 |
" bridge_ports eth0\n" |
| 2914 |
" bridge_maxwait 0\n" |
| 2915 |
" " |
| 2916 |
|
| 2917 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2918 |
#, fuzzy |
| 2919 |
#| msgid "<primary><command>xm</command></primary>" |
| 2920 |
msgid "<primary><command>xl</command></primary>" |
| 2921 |
msgstr "<primary><command>xm</command></primary>" |
| 2922 |
|
| 2923 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2924 |
#, fuzzy |
| 2925 |
#| msgid "After rebooting to make sure the bridge is automatically created, we can now start the domU with the Xen control tools, in particular the <command>xl</command> command. This command allows different manipulations on the domains, including listing them and, starting/stopping them." |
| 2926 |
msgid "After rebooting to make sure the bridge is automatically created, we can now start the domU with the Xen control tools, in particular the <command>xl</command> command. This command allows different manipulations on the domains, including listing them and, starting/stopping them. You might need to increase the default memory by editing the variable memory from configuration file (in this case, <filename>/etc/xen/testxen.cfg</filename>). Here we have set it to 1024 (megabytes)." |
| 2927 |
msgstr "再起動して、ブリッジが自動的に作成されることを確認します。この後 Xen 制御ツール、特に <command>xl</command> コマンドを使って domU を起動することが可能です。また、<command>xl</command> を使ってドメインを表示、起動、終了するなどの操作を行うことが可能です。" |
| 2928 |
|
| 2929 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2930 |
#, fuzzy |
| 2931 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 2932 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/xen/testxen.cfg</filename></secondary>" |
| 2933 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 2934 |
|
| 2935 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2936 |
#, fuzzy |
| 2937 |
#| msgid "" |
| 2938 |
#| "<computeroutput># </computeroutput><userinput>xl list</userinput>\n" |
| 2939 |
#| "<computeroutput>Name ID Mem VCPUs State Time(s)\n" |
| 2940 |
#| "Domain-0 0 463 1 r----- 9.8\n" |
| 2941 |
#| "# </computeroutput><userinput>xl create /etc/xen/testxen.cfg</userinput>\n" |
| 2942 |
#| "<computeroutput>Parsing config from /etc/xen/testxen.cfg\n" |
| 2943 |
#| "# </computeroutput><userinput>xl list</userinput>\n" |
| 2944 |
#| "<computeroutput>Name ID Mem VCPUs State Time(s)\n" |
| 2945 |
#| "Domain-0 0 366 1 r----- 11.4\n" |
| 2946 |
#| "testxen 1 128 1 -b---- 1.1</computeroutput>" |
| 2947 |
msgid "" |
| 2948 |
"<computeroutput># </computeroutput><userinput>xl list\n" |
| 2949 |
"</userinput><computeroutput>Name ID Mem VCPUs\tState\tTime(s)\n" |
| 2950 |
"Domain-0 0 3918 2 r----- 35.1\n" |
| 2951 |
"# </computeroutput><userinput>xl create /etc/xen/testxen.cfg\n" |
| 2952 |
"</userinput><computeroutput>Parsing config from /etc/xen/testxen.cfg\n" |
| 2953 |
"# </computeroutput><userinput>xl list\n" |
| 2954 |
"</userinput><computeroutput>Name ID Mem VCPUs\tState\tTime(s)\n" |
| 2955 |
"Domain-0 0 2757 2 r----- 45.2\n" |
| 2956 |
"testxen 3 1024 1 r----- 1.3\n" |
| 2957 |
"</computeroutput>" |
| 2958 |
msgstr "" |
| 2959 |
"<computeroutput># </computeroutput><userinput>xl list</userinput>\n" |
| 2960 |
"<computeroutput>Name ID Mem VCPUs State Time(s)\n" |
| 2961 |
"Domain-0 0 463 1 r----- 9.8\n" |
| 2962 |
"# </computeroutput><userinput>xl create /etc/xen/testxen.cfg</userinput>\n" |
| 2963 |
"<computeroutput>Parsing config from /etc/xen/testxen.cfg\n" |
| 2964 |
"# </computeroutput><userinput>xl list</userinput>\n" |
| 2965 |
"<computeroutput>Name ID Mem VCPUs State Time(s)\n" |
| 2966 |
"Domain-0 0 366 1 r----- 11.4\n" |
| 2967 |
"testxen 1 128 1 -b---- 1.1</computeroutput>" |
| 2968 |
|
| 2969 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2970 |
msgid "<emphasis>TOOL</emphasis> Choice of toolstacks to manage Xen VM" |
| 2971 |
msgstr "<emphasis>TOOL</emphasis> Xen VM を管理するツールスタックの選択" |
| 2972 |
|
| 2973 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2974 |
msgid "<primary><command>xm</command></primary>" |
| 2975 |
msgstr "<primary><command>xm</command></primary>" |
| 2976 |
|
| 2977 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2978 |
msgid "<primary><command>xe</command></primary>" |
| 2979 |
msgstr "<primary><command>xe</command></primary>" |
| 2980 |
|
| 2981 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2982 |
# Tag: L-CFMD; |
| 2983 |
msgid "<primary><command>virsh</command></primary>" |
| 2984 |
msgstr "<primary><command>virsh</command></primary>" |
| 2985 |
|
| 2986 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2987 |
#, fuzzy |
| 2988 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2989 |
msgid "<primary><emphasis role=\"pkg\">libvirt</emphasis></primary>" |
| 2990 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 2991 |
|
| 2992 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2993 |
#, fuzzy |
| 2994 |
#| msgid "In Debian 7 and older releases, <command>xm</command> was the reference command line tool to use to manage Xen virtual machines. It has now been replaced by <command>xl</command> which is mostly backwards compatible. But those are not the only available tools: <command>virsh</command> of libvirt and <command>xe</command> of XenServer's XAPI (commercial offering of Xen) are alternative tools." |
| 2995 |
msgid "In Debian 7 and older releases, <command>xm</command> was the reference command line tool to use to manage Xen virtual machines. It has now been replaced by <command>xl</command> which is mostly backwards compatible. But those are not the only available tools: <command>virsh</command> of <emphasis role=\"pkg\">libvirt</emphasis> and <command>xe</command> of XenServer's XAPI (commercial offering of Xen) are alternative tools." |
| 2996 |
msgstr "Debian 7 および Debian 7 よりも古いリリースでは、<command>xm</command> が Xen 仮想マシンの管理に使うための標準的なコマンドラインツールでした。現在 <command>xm</command> はほぼ後方互換性を持つ <command>xl</command> によって置き換えられました。しかし、利用できるツールは <command>xm</command> および <command>xl</command> だけではありません。代替ツールとしては、libvirt を操作する <command>virsh</command> と XenServer (Xen の商用版) の XAPI を操作する <command>xe</command> が存在します。" |
| 2997 |
|
| 2998 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 2999 |
msgid "<emphasis>CAUTION</emphasis> Only one domU per image!" |
| 3000 |
msgstr "<emphasis>CAUTION</emphasis> 1 つのイメージに 1 台以上の domU を割り当てないでください!" |
| 3001 |
|
| 3002 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3003 |
#, fuzzy |
| 3004 |
#| msgid "While it is of course possible to have several domU systems running in parallel, they will all need to use their own image, since each domU is made to believe it runs on its own hardware (apart from the small slice of the kernel that talks to the hypervisor). In particular, it isn't possible for two domU systems running simultaneously to share storage space. If the domU systems are not run at the same time, it is however quite possible to reuse a single swap partition, or the partition hosting the <filename>/home</filename> filesystem." |
| 3005 |
msgid "While it is of course possible to have several domU systems running in parallel, they will all need to use their own image, since each domU is made to believe it runs on its own hardware (apart from the small slice of the kernel that talks to the hypervisor). In particular, it isn't possible for two domU systems running simultaneously to share storage space. If the domU systems are not run at the same time, it is, however, quite possible to reuse a single swap partition, or the partition hosting the <filename>/home</filename> filesystem." |
| 3006 |
msgstr "もちろん複数の domU システムを並列実行させることは可能ですが、各 domU システムは専用のイメージを必要とします。なぜなら、各 domU は自分に割り当てられたハードウェアを専有するという仮定に基づいて実行されるからです (ハイパーバイザとやり取りするカーネルの一部分は別です)。特に、ストレージ領域を共有する目的で 2 つの domU システムを同時に起動することは不可能です。2 つの domU システムが同時に起動していなければ、両者はストレージ領域を共有して、単独のスワップパーティションや <filename>/home</filename> ファイルシステムをホストしているパーティションを再利用することが可能です。" |
| 3007 |
|
| 3008 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3009 |
msgid "Note that the <filename>testxen</filename> domU uses real memory taken from the RAM that would otherwise be available to the dom0, not simulated memory. Care should therefore be taken, when building a server meant to host Xen instances, to provision the physical RAM accordingly." |
| 3010 |
msgstr "<filename>testxen</filename> domU は仮想メモリではなく RAM から取った物理メモリを使います。このメモリ領域は <filename>testxen</filename> domU が起動していなければ dom0 が使えるメモリ領域だったという点に注意してください。このため、サーバを作ることが Xen インスタンスをホストすることを意味する場合、それに応じて十分なサイズの物理 RAM が必要になるという点に注意が必要です。" |
| 3011 |
|
| 3012 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3013 |
msgid "Voilà! Our virtual machine is starting up. We can access it in one of two modes. The usual way is to connect to it “remotely” through the network, as we would connect to a real machine; this will usually require setting up either a DHCP server or some DNS configuration. The other way, which may be the only way if the network configuration was incorrect, is to use the <filename>hvc0</filename> console, with the <command>xl console</command> command:" |
| 3014 |
msgstr "おめでとうございます! 仮想マシンが開始されました。仮想マシンにアクセスするには 2 種類の方法があります。通常の方法は、真のマシンに接続するのと同様に、ネットワークを介して「リモートで」仮想マシンに接続することです。そしてこれを行うには、通常別の DHCP サーバや DNS 設定をセットアップすることが必要です。別の方法は <command>xl console</command> コマンドから <filename>hvc0</filename> コンソールを使う方法です。ネットワーク設定が正しくない場合にはこれが唯一の方法です。" |
| 3015 |
|
| 3016 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3017 |
#, fuzzy |
| 3018 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3019 |
msgid "<primary>Xen</primary><secondary><literal>hvc0</literal></secondary>" |
| 3020 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3021 |
|
| 3022 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3023 |
# Tag: L-CFMD; |
| 3024 |
#, fuzzy |
| 3025 |
#| msgid "" |
| 3026 |
#| "<computeroutput># </computeroutput><userinput>xl console testxen</userinput>\n" |
| 3027 |
#| "<computeroutput>[...]\n" |
| 3028 |
#| "\n" |
| 3029 |
#| "Debian GNU/Linux 8 testxen hvc0\n" |
| 3030 |
#| "\n" |
| 3031 |
#| "testxen login: </computeroutput>" |
| 3032 |
msgid "" |
| 3033 |
"<computeroutput># </computeroutput><userinput>xl console testxen</userinput>\n" |
| 3034 |
"<computeroutput>[...]\n" |
| 3035 |
"\n" |
| 3036 |
"Debian GNU/Linux 11 testxen hvc0\n" |
| 3037 |
"\n" |
| 3038 |
"testxen login: </computeroutput>" |
| 3039 |
msgstr "" |
| 3040 |
"<computeroutput># </computeroutput><userinput>xl console testxen</userinput>\n" |
| 3041 |
"<computeroutput>[...]\n" |
| 3042 |
"\n" |
| 3043 |
"Debian GNU/Linux 8 testxen hvc0\n" |
| 3044 |
"\n" |
| 3045 |
"testxen login: </computeroutput>" |
| 3046 |
|
| 3047 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3048 |
# Tag: L-CFMD; |
| 3049 |
msgid "One can then open a session, just like one would do if sitting at the virtual machine's keyboard. Detaching from this console is achieved through the <keycombo action=\"simul\"><keycap>Control</keycap> <keycap>]</keycap></keycombo> key combination." |
| 3050 |
msgstr "仮想マシンのキーボードの前に座っているかのごとくセッションを開くことが可能です。このコンソールからデタッチするには、<keycombo action=\"simul\"><keycap>Control</keycap> <keycap>]</keycap></keycombo> キーの組み合わせを使用します。" |
| 3051 |
|
| 3052 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3053 |
msgid "<emphasis>TIP</emphasis> Getting the console straight away" |
| 3054 |
msgstr "<emphasis>TIP</emphasis> すぐにコンソールを開始する" |
| 3055 |
|
| 3056 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3057 |
#, fuzzy |
| 3058 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3059 |
msgid "<primary>Xen</primary><secondary>console</secondary>" |
| 3060 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3061 |
|
| 3062 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3063 |
# Tag: L-CFMD; |
| 3064 |
msgid "Sometimes one wishes to start a domU system and get to its console straight away; this is why the <command>xl create</command> command takes a <literal>-c</literal> switch. Starting a domU with this switch will display all the messages as the system boots." |
| 3065 |
msgstr "domU システムの開始直後にコンソールを始めたい場合があります。そしてこの希望に応えるために <command>xl create</command> コマンドは <literal>-c</literal> オプションを備えています。<literal>-c</literal> オプションを付けて domU を開始すれば、システム起動時に表示されるすべてのメッセージを見ることが可能です。" |
| 3066 |
|
| 3067 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3068 |
#, fuzzy |
| 3069 |
#| msgid "<emphasis>TOOL</emphasis> OpenXenManager" |
| 3070 |
msgid "<emphasis>TOOL</emphasis> Graphical Xen managers" |
| 3071 |
msgstr "<emphasis>TOOL</emphasis> OpenXenManager" |
| 3072 |
|
| 3073 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3074 |
#, fuzzy |
| 3075 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3076 |
msgid "<primary>Xen</primary><secondary>manager</secondary>" |
| 3077 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3078 |
|
| 3079 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3080 |
# Tag: L-CFMD; |
| 3081 |
#, fuzzy |
| 3082 |
#| msgid "OpenXenManager (in the <emphasis role=\"pkg\">openxenmanager</emphasis> package) is a graphical interface allowing remote management of Xen domains via Xen's API. It can thus control Xen domains remotely. It provides most of the features of the <command>xl</command> command." |
| 3083 |
msgid "OpenXenManager (in the <emphasis role=\"pkg\">openxenmanager</emphasis> package), a graphical interface allowing remote management of Xen domains via Xen's API, is no longer provided by Debian due to the lack of upstream development. If you are looking for a replacement, <emphasis role=\"pkg\">virt-manager</emphasis> provides support to handle Xen VMs as well." |
| 3084 |
msgstr "OpenXenManager (<emphasis role=\"pkg\">openxenmanager</emphasis> パッケージに含まれます) はグラフィカルインターフェースです。これ使うことで Xen API を介して Xen ドメインのリモート管理することが可能です。このため、Xen ドメインをリモートで制御することが可能です。OpenXenManager は <command>xl</command> コマンドの機能のほとんどを備えています。" |
| 3085 |
|
| 3086 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3087 |
#, fuzzy |
| 3088 |
#| msgid "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 3089 |
msgid "<primary><emphasis role=\"pkg\">openxenmanager</emphasis></primary>" |
| 3090 |
msgstr "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 3091 |
|
| 3092 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3093 |
msgid "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 3094 |
msgstr "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 3095 |
|
| 3096 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3097 |
# Tag: L-CFMD; |
| 3098 |
msgid "Once the domU is up, it can be used just like any other server (since it is a GNU/Linux system after all). However, its virtual machine status allows some extra features. For instance, a domU can be temporarily paused then resumed, with the <command>xl pause</command> and <command>xl unpause</command> commands. Note that even though a paused domU does not use any processor power, its allocated memory is still in use. It may be interesting to consider the <command>xl save</command> and <command>xl restore</command> commands: saving a domU frees the resources that were previously used by this domU, including RAM. When restored (or unpaused, for that matter), a domU doesn't even notice anything beyond the passage of time. If a domU was running when the dom0 is shut down, the packaged scripts automatically save the domU, and restore it on the next boot. This will of course involve the standard inconvenience incurred when hibernating a laptop computer, for instance; in particular, if the domU is suspended for too long, network connections may expire. Note also that Xen is so far incompatible with a large part of ACPI power management, which precludes suspending the host (dom0) system." |
| 3099 |
msgstr "domU の起動完了後、domU は他のサーバと同様に使うことが可能です (domU は結局 GNU/Linux システムに過ぎません)。しかしながら、domU の仮想マシンの状態はいくつかの追加的機能を備えています。たとえば、<command>xl pause</command> と <command>xl unpause</command> コマンドを使って domU を一時的に停止したり再開することが可能です。一時的に停止された domU は全くプロセッサを使いませんが、割り当てられたメモリを解放しません。<command>xl save</command> と <command>xl restore</command> コマンドを考慮することは興味深いかもしれません。なぜなら <command>xl save</command> で domU を保存すれば domU の使っていた RAM などの資源が解放されるからです。また、<command>xl restore</command> で domU を元に戻す時 (ついでに言えば <command>xl unpause</command> で再開する時)、domU は時間が経過したことに全く気が付きません。dom0 を停止した時に domU が動いていた場合、パッケージに含まれるスクリプトが自動的に <command>xl save</command> で domU を保存し、dom0 の次回起動時に自動的に <command>xl restore</command> で domU を再開します。もちろんこれにはラップトップコンピュータをハイバネートする場合と同様の標準的な不便さがあります。特に、domU が長い間一時停止されていた場合、ネットワーク接続が切断される可能性があります。今現在 Xen は ACPI 電源管理のほとんどに互換性がない点にも注意してください。このため、ホスト (dom0) システムを一時停止することは不可能です。" |
| 3100 |
|
| 3101 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3102 |
#, fuzzy |
| 3103 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3104 |
msgid "<primary>Xen</primary><secondary>ACPI</secondary>" |
| 3105 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3106 |
|
| 3107 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3108 |
#, fuzzy |
| 3109 |
#| msgid "<primary>RAID</primary>" |
| 3110 |
msgid "<primary>ACPI</primary>" |
| 3111 |
msgstr "<primary>RAID</primary>" |
| 3112 |
|
| 3113 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3114 |
# Tag: L-CFMD; |
| 3115 |
msgid "Halting or rebooting a domU can be done either from within the domU (with the <command>shutdown</command> command) or from the dom0, with <command>xl shutdown</command> or <command>xl reboot</command>." |
| 3116 |
msgstr "domU を停止したり再起動するには、domU の内部から (<command>shutdown</command> コマンドを使って) 行ったり、dom0 から <command>xl shutdown</command> または <command>xl reboot</command> を使って行うことも可能です。" |
| 3117 |
|
| 3118 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3119 |
# Tag: L-CFMD; |
| 3120 |
msgid "Most of the <command>xl</command> subcommands expect one or more arguments, often a domU name. These arguments are well described in the <citerefentry><refentrytitle>xl</refentrytitle> <manvolnum>1</manvolnum></citerefentry> manual page." |
| 3121 |
msgstr "<command>xl</command> サブコマンドのほとんどは domU の名前などの 1 つか複数個の引数を取ります。これらの引数は <citerefentry><refentrytitle>xl</refentrytitle> <manvolnum>1</manvolnum></citerefentry> マニュアルページは詳しく説明されています。" |
| 3122 |
|
| 3123 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3124 |
msgid "<emphasis>GOING FURTHER</emphasis> Advanced Xen" |
| 3125 |
msgstr "<emphasis>GOING FURTHER</emphasis> Xen の上級活用" |
| 3126 |
|
| 3127 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3128 |
#, fuzzy |
| 3129 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3130 |
msgid "<primary>Xen</primary><secondary>documentation</secondary>" |
| 3131 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3132 |
|
| 3133 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3134 |
#, fuzzy |
| 3135 |
#| msgid "Xen has many more features than we can describe in these few paragraphs. In particular, the system is very dynamic, and many parameters for one domain (such as the amount of allocated memory, the visible hard drives, the behavior of the task scheduler, and so on) can be adjusted even when that domain is running. A domU can even be migrated across servers without being shut down, and without losing its network connections! For all these advanced aspects, the primary source of information is the official Xen documentation. <ulink type=\"block\" url=\"http://www.xen.org/support/documentation.html\" />" |
| 3136 |
msgid "Xen has many more features than we can describe in these few paragraphs. In particular, the system is very dynamic, and many parameters for one domain (such as the amount of allocated memory, the visible hard drives, the behavior of the task scheduler, and so on) can be adjusted even when that domain is running. A domU can even be migrated across servers without being shut down, and without losing its network connections! For all these advanced aspects, the primary source of information is the official Xen documentation. <ulink type=\"block\" url=\"https://xenproject.org/help/documentation/\" />" |
| 3137 |
msgstr "Xen はここで示すことができた数項だけにとどまらない多くの機能を持っています。特に、Xen はシステムを動的に変更することが可能です。すなわちドメインに対する多くのパラメータ (割り当てメモリサイズ、見えるハードドライブ、タスクスケジューラの挙動など) をドメインの実行中に調整することが可能です。domU はシャットダウンすることもネットワーク接続を失うこともなくサーバ間を移動することさえ可能です! すべての上級活用法に関して、最良の情報源は公式の Xen 文書です。<ulink type=\"block\" url=\"http://www.xen.org/support/documentation.html\" />" |
| 3138 |
|
| 3139 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3140 |
#, fuzzy |
| 3141 |
#| msgid "<primary>Munin</primary>" |
| 3142 |
msgid "<primary>Linux Containers</primary><see>LXC</see>" |
| 3143 |
msgstr "<primary>Munin</primary>" |
| 3144 |
|
| 3145 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3146 |
#, fuzzy |
| 3147 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3148 |
msgid "<primary>kernel</primary><secondary>control groups</secondary>" |
| 3149 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3150 |
|
| 3151 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3152 |
# Tag: L-CFMD; |
| 3153 |
msgid "Even though it is used to build “virtual machines”, LXC is not, strictly speaking, a virtualization system, but a system to isolate groups of processes from each other even though they all run on the same host. It takes advantage of a set of recent evolutions in the Linux kernel, collectively known as <emphasis>control groups</emphasis>, by which different sets of processes called “groups” have different views of certain aspects of the overall system. Most notable among these aspects are the process identifiers, the network configuration, and the mount points. Such a group of isolated processes will not have any access to the other processes in the system, and its accesses to the filesystem can be restricted to a specific subset. It can also have its own network interface and routing table, and it may be configured to only see a subset of the available devices present on the system." |
| 3154 |
msgstr "LXC は「仮想マシン」を作るために使われるにも関わらず、厳密に言うと仮想システムではなく、同じホスト上で実行されるプロセスのグループを隔離するためのシステムです。LXC は近年 Linux カーネルに対して行われた数々の機能の利点を活用しています。これらの機能はまとめて <emphasis>control groups</emphasis> として知られています。<emphasis>control groups</emphasis> を使うことにより、「グループ」と呼ばれるさまざまなプロセス群に対してシステム全体の特定の側面の状態を強制することが可能です。中でも最も注目すべき側面はプロセス ID、ネットワーク接続、マウントポイントです。隔離されたプロセスのグループはシステムの他のプロセスにアクセスできませんし、グループによるファイルシステムへのアクセスを特定の一部に限定することが可能です。さらにグループにネットワークインターフェースとルーティングテーブルを設定することにより、グループがシステム上の利用できるデバイスの一部だけを見えるように設定することが可能です。" |
| 3155 |
|
| 3156 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3157 |
#, fuzzy |
| 3158 |
#| msgid "<primary>Munin</primary>" |
| 3159 |
msgid "<primary>container</primary>" |
| 3160 |
msgstr "<primary>Munin</primary>" |
| 3161 |
|
| 3162 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3163 |
#, fuzzy |
| 3164 |
#| msgid "These features can be combined to isolate a whole process family starting from the <command>init</command> process, and the resulting set looks very much like a virtual machine. The official name for such a setup is a “container” (hence the LXC moniker: <emphasis>LinuX Containers</emphasis>), but a rather important difference with “real” virtual machines such as provided by Xen or KVM is that there's no second kernel; the container uses the very same kernel as the host system. This has both pros and cons: advantages include excellent performance due to the total lack of overhead, and the fact that the kernel has a global vision of all the processes running on the system, so the scheduling can be more efficient than it would be if two independent kernels were to schedule different task sets. Chief among the inconveniences is the impossibility to run a different kernel in a container (whether a different Linux version or a different operating system altogether)." |
| 3165 |
msgid "These features can be combined to isolate a whole process family starting from the <command>init</command> process, and the resulting set looks very much like a virtual machine. The official name for such a setup is a “container” (hence the LXC moniker: <emphasis>LinuX Containers</emphasis>), but a rather important difference with “real” virtual machines such as provided by Xen or KVM is that there is no second kernel; the container uses the very same kernel as the host system. This has both pros and cons: advantages include excellent performance due to the total lack of overhead, and the fact that the kernel has a global vision of all the processes running on the system, so the scheduling can be more efficient than it would be if two independent kernels were to schedule different task sets. Chief among the inconveniences is the impossibility to run a different kernel in a container (whether a different Linux version or a different operating system altogether)." |
| 3166 |
msgstr "これらの機能を組み合わせることで、<command>init</command> プロセスから起動されたすべてのプロセスファミリーを隔離することが可能です。その結果、仮想マシンにとてもよく似たものが作られます。このようなセットアップの正式名称が「コンテナ」です (LXC の名称 <emphasis>LinuX Containers</emphasis> はこれに由来しています)。Xen や KVM が提供する「真の」仮想マシンとのより重要な違いは仮想マシン用のカーネルがない点です。このため、コンテナはホストシステムと全く同じカーネルを使います。これには利点と欠点があります。すなわち、利点はオーバーヘッドが全くないことで素晴らしい性能を得ることが可能という点とカーネルはシステムで実行しているすべてのプロセスを見ることが可能という点です。このため 2 つの独立したカーネルが異なるタスクセットでスケジュールを行うよりも効果的なスケジューリングが可能です。欠点の最たるものはコンテナの中で異なるカーネルを動作させることが不可能という点です (異なる Linux バージョンや異なるオペレーティングシステムを同時に動かすことができません)。" |
| 3167 |
|
| 3168 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3169 |
msgid "<emphasis>NOTE</emphasis> LXC isolation limits" |
| 3170 |
msgstr "<emphasis>NOTE</emphasis> LXC の隔離制限" |
| 3171 |
|
| 3172 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3173 |
msgid "LXC containers do not provide the level of isolation achieved by heavier emulators or virtualizers. In particular:" |
| 3174 |
msgstr "LXC コンテナは負荷の大きなエミュレータやバーチャライザが備える隔離機能を備えていません。たとえば以下のような機能を備えていません。" |
| 3175 |
|
| 3176 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3177 |
# Tag: PTAL; |
| 3178 |
msgid "since the kernel is shared among the host system and the containers, processes constrained to containers can still access the kernel messages, which can lead to information leaks if messages are emitted by a container;" |
| 3179 |
msgstr "カーネルはホストシステムとコンテナによって共有されているため、コンテナ内に隔離されているプロセスはカーネルメッセージにアクセスできます。このことにより、メッセージがコンテナによって発せられた場合、情報が漏洩する可能性があります。" |
| 3180 |
|
| 3181 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3182 |
msgid "for similar reasons, if a container is compromised and a kernel vulnerability is exploited, the other containers may be affected too;" |
| 3183 |
msgstr "同様の理由で、コンテナが不正アクセスされカーネルの脆弱性が悪用された場合、他のコンテナが影響を受ける可能性があります。" |
| 3184 |
|
| 3185 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3186 |
msgid "on the filesystem, the kernel checks permissions according to the numerical identifiers for users and groups; these identifiers may designate different users and groups depending on the container, which should be kept in mind if writable parts of the filesystem are shared among containers." |
| 3187 |
msgstr "ファイルシステムについて、カーネルはユーザとグループの数値的な識別子に従ってパーミッションを確認します。これらの識別子の意味するユーザとグループはコンテナごとに異なります。ファイルシステムの書き込み可能な部分がコンテナ同士で共有されている場合、この点を覚えておくべきです。" |
| 3188 |
|
| 3189 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3190 |
msgid "Since we are dealing with isolation and not plain virtualization, setting up LXC containers is more complex than just running debian-installer on a virtual machine. We will describe a few prerequisites, then go on to the network configuration; we will then be able to actually create the system to be run in the container." |
| 3191 |
msgstr "LXC による隔離は単純な仮想化と異なるため、LXC コンテナを設定することは仮想マシン上で単純に debian-installer を実行するよりも複雑な作業です。このため、いくつかの必要条件を説明した後、ネットワーク設定を行います。こうすることで、コンテナの中で実行するシステムを実際に作成することが可能です。" |
| 3192 |
|
| 3193 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3194 |
msgid "Preliminary Steps" |
| 3195 |
msgstr "準備段階" |
| 3196 |
|
| 3197 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3198 |
#, fuzzy |
| 3199 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 3200 |
msgid "<primary><emphasis role=\"pkg\">lxc</emphasis></primary>" |
| 3201 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 3202 |
|
| 3203 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3204 |
msgid "The <emphasis role=\"pkg\">lxc</emphasis> package contains the tools required to run LXC, and must therefore be installed." |
| 3205 |
msgstr "<emphasis role=\"pkg\">lxc</emphasis> パッケージには LXC を実行するために必要なツールが含まれるため、必ずこのパッケージをインストールしなければいけません。" |
| 3206 |
|
| 3207 |
msgid "<primary><filename>/sys</filename></primary><secondary><filename>/sys/fs/cgroup</filename></secondary>" |
| 3208 |
msgstr "" |
| 3209 |
|
| 3210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3211 |
msgid "LXC also requires the <emphasis>control groups</emphasis> configuration system, which is a virtual filesystem to be mounted on <filename>/sys/fs/cgroup</filename>. Since Debian 8 switched to systemd, which also relies on control groups, this is now done automatically at boot time without further configuration." |
| 3212 |
msgstr "LXC を使うには <emphasis>control groups</emphasis> 設定システムが必要で、<filename>/sys/fs/cgroup</filename> に仮想ファイルシステムをマウントする必要があります。Debian 8 からは init システムとして systemd が採用されており、systemd は <emphasis>control groups</emphasis> に依存しているため、設定せずとも <filename>/sys/fs/cgroup</filename> は起動時に自動でマウントされます。" |
| 3213 |
|
| 3214 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3215 |
msgid "Network Configuration" |
| 3216 |
msgstr "ネットワークの設定" |
| 3217 |
|
| 3218 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3219 |
#, fuzzy |
| 3220 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3221 |
msgid "<primary>LXC</primary><secondary>network configuration</secondary>" |
| 3222 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3223 |
|
| 3224 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3225 |
#, fuzzy |
| 3226 |
#| msgid "The goal of installing LXC is to set up virtual machines; while we could of course keep them isolated from the network, and only communicate with them via the filesystem, most use cases involve giving at least minimal network access to the containers. In the typical case, each container will get a virtual network interface, connected to the real network through a bridge. This virtual interface can be plugged either directly onto the host's physical network interface (in which case the container is directly on the network), or onto another virtual interface defined on the host (and the host can then filter or route traffic). In both cases, the <emphasis role=\"pkg\">bridge-utils</emphasis> package will be required." |
| 3227 |
msgid "The goal of installing LXC is to set up virtual machines; while we could, of course, keep them isolated from the network, and only communicate with them via the filesystem, most use cases involve giving at least minimal network access to the containers. In the typical case, each container will get a virtual network interface, connected to the real network through a bridge. This virtual interface can be plugged either directly onto the host's physical network interface (in which case the container is directly on the network), or onto another virtual interface defined on the host (and the host can then filter or route traffic). In both cases, the <emphasis role=\"pkg\">bridge-utils</emphasis> package will be required." |
| 3228 |
msgstr "LXC をインストールする目的は仮想マシンをセットアップすることです。もちろん、仮想マシンをネットワークから隔離するように設定したり、ファイルシステムを介してのみ情報をやり取りするように設定することも可能ですが、コンテナに対して少なくとも最低限のネットワークアクセスを提供するように設定するのが一般的です。典型的な場合、各コンテナにはブリッジを介して実際のネットワークに接続された仮想ネットワークインターフェースが備えられています。この仮想インターフェースは、直接ホスト上の物理ネットワークインターフェースに接続されているか (この場合、コンテナは直接ネットワークに接続されています)、ホスト上に定義された他の仮想インターフェースに接続されています (ホストからトラフィックをフィルタしたり配送することが可能です)。どちらの場合も、<emphasis role=\"pkg\">bridge-utils</emphasis> パッケージが必要です。" |
| 3229 |
|
| 3230 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3231 |
#, fuzzy |
| 3232 |
#| msgid "The simple case is just a matter of editing <filename>/etc/network/interfaces</filename>, moving the configuration for the physical interface (for instance <literal>eth0</literal>) to a bridge interface (usually <literal>br0</literal>), and configuring the link between them. For instance, if the network interface configuration file initially contains entries such as the following:" |
| 3233 |
msgid "The simple case is just a matter of editing <filename>/etc/network/interfaces</filename>, moving the configuration for the physical interface (for instance, <literal>eth0</literal> or <literal>enp1s0</literal>) to a bridge interface (usually <literal>br0</literal>), and configuring the link between them. For instance, if the network interface configuration file initially contains entries such as the following:" |
| 3234 |
msgstr "最も簡単なやり方は <filename>/etc/network/interfaces</filename> を編集することです。物理インターフェース (たとえば <literal>eth0</literal>) に関する設定をブリッジインターフェース (通常 <literal>br0</literal>) に変え、物理とブリッジインターフェース間のリンクを設定します。たとえば、最初にネットワークインターフェース設定ファイルが以下のようなエントリを持っていたとします。" |
| 3235 |
|
| 3236 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3237 |
#, fuzzy |
| 3238 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3239 |
msgid "<primary>network</primary><secondary><literal>br</literal> interface</secondary>" |
| 3240 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3241 |
|
| 3242 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3243 |
#, fuzzy |
| 3244 |
#| msgid "<primary>virtualization</primary>" |
| 3245 |
msgid "<primary><literal>br</literal>, network interface</primary>" |
| 3246 |
msgstr "<primary sortas=\"カソウカ\">仮想化</primary>" |
| 3247 |
|
| 3248 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3249 |
msgid "" |
| 3250 |
"auto eth0\n" |
| 3251 |
"iface eth0 inet dhcp" |
| 3252 |
msgstr "" |
| 3253 |
"auto eth0\n" |
| 3254 |
"iface eth0 inet dhcp" |
| 3255 |
|
| 3256 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3257 |
msgid "They should be disabled and replaced with the following:" |
| 3258 |
msgstr "このエントリを無効化し、以下の通り書き換えます。" |
| 3259 |
|
| 3260 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3261 |
#, fuzzy |
| 3262 |
#| msgid "" |
| 3263 |
#| "auto xenbr0\n" |
| 3264 |
#| "iface xenbr0 inet dhcp\n" |
| 3265 |
#| " bridge_ports eth0\n" |
| 3266 |
#| " bridge_maxwait 0\n" |
| 3267 |
#| " " |
| 3268 |
msgid "" |
| 3269 |
"auto br0\n" |
| 3270 |
"iface br0 inet dhcp\n" |
| 3271 |
" bridge-ports <replaceable>eth0</replaceable>" |
| 3272 |
msgstr "" |
| 3273 |
"auto xenbr0\n" |
| 3274 |
"iface xenbr0 inet dhcp\n" |
| 3275 |
" bridge_ports eth0\n" |
| 3276 |
" bridge_maxwait 0\n" |
| 3277 |
" " |
| 3278 |
|
| 3279 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3280 |
msgid "The effect of this configuration will be similar to what would be obtained if the containers were machines plugged into the same physical network as the host. The “bridge” configuration manages the transit of Ethernet frames between all the bridged interfaces, which includes the physical <literal>eth0</literal> as well as the interfaces defined for the containers." |
| 3281 |
msgstr "この設定により、コンテナをホストと同じ物理ネットワークに接続されたマシンとして考えた場合と、同様の効果が得られます。この「ブリッジ」設定はすべてのブリッジされたインターフェース間のイーサネットフレームの通過を管理します。これには物理的な <literal>eth0</literal> およびコンテナ用に定義されたインターフェースが含まれます。" |
| 3282 |
|
| 3283 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3284 |
#, fuzzy |
| 3285 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3286 |
msgid "<primary>network</primary><secondary><literal>tap</literal> interface</secondary>" |
| 3287 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3288 |
|
| 3289 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3290 |
#, fuzzy |
| 3291 |
#| msgid "In cases where this configuration cannot be used (for instance if no public IP addresses can be assigned to the containers), a virtual <emphasis>tap</emphasis> interface will be created and connected to the bridge. The equivalent network topology then becomes that of a host with a second network card plugged into a separate switch, with the containers also plugged into that switch. The host must then act as a gateway for the containers if they are meant to communicate with the outside world." |
| 3292 |
msgid "In cases where this configuration cannot be used (for instance, if no public IP addresses can be assigned to the containers), a virtual <emphasis>tap</emphasis> interface will be created and connected to the bridge. The equivalent network topology then becomes that of a host with a second network card plugged into a separate switch, with the containers also plugged into that switch. The host must then act as a gateway for the containers if they are meant to communicate with the outside world." |
| 3293 |
msgstr "この設定を使うことができない場合 (たとえば、公開 IP アドレスをコンテナに割り当てることができない場合)、仮想 <emphasis>tap</emphasis> インターフェースを作成し、これをブリッジに接続します。これと等価なネットワークトポロジーは、ホストの 2 番目のネットワークカードが分離されたスイッチに接続されている状態です。コンテナはこのスイッチに接続されています。コンテナが外部と通信するには、ホストがコンテナ用のゲートウェイとして振る舞わなければいけません。" |
| 3294 |
|
| 3295 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3296 |
msgid "In addition to <emphasis role=\"pkg\">bridge-utils</emphasis>, this “rich” configuration requires the <emphasis role=\"pkg\">vde2</emphasis> package; the <filename>/etc/network/interfaces</filename> file then becomes:" |
| 3297 |
msgstr "この「ぜいたくな」設定を行うには <emphasis role=\"pkg\">bridge-utils</emphasis> と <emphasis role=\"pkg\">vde2</emphasis> パッケージが必要です。<filename>/etc/network/interfaces</filename> ファイルは以下のようになります。" |
| 3298 |
|
| 3299 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3300 |
#, fuzzy |
| 3301 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 3302 |
msgid "<primary><emphasis role=\"pkg\">vde2</emphasis></primary>" |
| 3303 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 3304 |
|
| 3305 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3306 |
#, fuzzy |
| 3307 |
#| msgid "" |
| 3308 |
#| "# Interface eth0 is unchanged\n" |
| 3309 |
#| "auto eth0\n" |
| 3310 |
#| "iface eth0 inet dhcp\n" |
| 3311 |
#| "\n" |
| 3312 |
#| "# Virtual interface \n" |
| 3313 |
#| "auto tap0\n" |
| 3314 |
#| "iface tap0 inet manual\n" |
| 3315 |
#| " vde2-switch -t tap0\n" |
| 3316 |
#| "\n" |
| 3317 |
#| "# Bridge for containers\n" |
| 3318 |
#| "auto br0\n" |
| 3319 |
#| "iface br0 inet static\n" |
| 3320 |
#| " bridge-ports tap0\n" |
| 3321 |
#| " address 10.0.0.1\n" |
| 3322 |
#| " netmask 255.255.255.0" |
| 3323 |
msgid "" |
| 3324 |
"# Interface eth0 is unchanged\n" |
| 3325 |
"auto eth0\n" |
| 3326 |
"iface eth0 inet dhcp\n" |
| 3327 |
"\n" |
| 3328 |
"# Virtual interface \n" |
| 3329 |
"auto tap0\n" |
| 3330 |
"iface tap0 inet manual\n" |
| 3331 |
" vde2-switch -t tap0\n" |
| 3332 |
"\n" |
| 3333 |
"# Bridge for containers\n" |
| 3334 |
"auto br0\n" |
| 3335 |
"iface br0 inet static\n" |
| 3336 |
" bridge-ports tap0\n" |
| 3337 |
" address 10.0.0.1\n" |
| 3338 |
" netmask 255.255.255.0" |
| 3339 |
msgstr "" |
| 3340 |
"# eth0 インターフェースは同じものを使います\n" |
| 3341 |
"auto eth0\n" |
| 3342 |
"iface eth0 inet dhcp\n" |
| 3343 |
"\n" |
| 3344 |
"# 仮想インターフェース\n" |
| 3345 |
"auto tap0\n" |
| 3346 |
"iface tap0 inet manual\n" |
| 3347 |
" vde2-switch -t tap0\n" |
| 3348 |
"\n" |
| 3349 |
"# コンテナ用のブリッジ\n" |
| 3350 |
"auto br0\n" |
| 3351 |
"iface br0 inet static\n" |
| 3352 |
" bridge_ports tap0\n" |
| 3353 |
" address 10.0.0.1\n" |
| 3354 |
" netmask 255.255.255.0" |
| 3355 |
|
| 3356 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3357 |
msgid "The network can then be set up either statically in the containers, or dynamically with DHCP server running on the host. Such a DHCP server will need to be configured to answer queries on the <literal>br0</literal> interface." |
| 3358 |
msgstr "コンテナのネットワークは静的またはコンテナのホスト上で動く DHCP サーバを使って動的に設定されます。また、DHCP サーバを <literal>br0</literal> インターフェースを介した問い合わせに応答するように設定する必要があります。" |
| 3359 |
|
| 3360 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3361 |
msgid "Setting Up the System" |
| 3362 |
msgstr "システムのセットアップ" |
| 3363 |
|
| 3364 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3365 |
#, fuzzy |
| 3366 |
#| msgid "Let us now set up the filesystem to be used by the container. Since this “virtual machine” will not run directly on the hardware, some tweaks are required when compared to a standard filesystem, especially as far as the kernel, devices and consoles are concerned. Fortunately, the <emphasis role=\"pkg\">lxc</emphasis> includes scripts that mostly automate this configuration. For instance, the following commands (which require the <emphasis role=\"pkg\">debootstrap</emphasis> and <emphasis role=\"pkg\">rsync</emphasis> packages) will install a Debian container:" |
| 3367 |
msgid "Let us now set up the filesystem to be used by the container. Since this “virtual machine” will not run directly on the hardware, some tweaks are required when compared to a standard filesystem, especially as far as the kernel, devices and consoles are concerned. Fortunately, the <emphasis role=\"pkg\">lxc</emphasis> package includes scripts that mostly automate this configuration. For instance, the following commands (which require the <emphasis role=\"pkg\">debootstrap</emphasis> and <emphasis role=\"pkg\">rsync</emphasis> packages) will install a Debian container:" |
| 3368 |
msgstr "それではコンテナがファイルシステムを使うようにファイルシステムを設定しましょう。コンテナという「仮想マシン」はハードウェア上で直接的に実行されないため、標準的なファイルシステムに比べていくつかの微調整を必要とします。これは特にカーネル、デバイス、コンソールが該当します。幸いなことに、<emphasis role=\"pkg\">lxc</emphasis> にはこの設定をほぼ自動化するスクリプトが含まれます。たとえば、以下のコマンド (<emphasis role=\"pkg\">debootstrap</emphasis> と <emphasis role=\"pkg\">rsync</emphasis> パッケージが必要です) で Debian コンテナがインストールされます。" |
| 3369 |
|
| 3370 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3371 |
#, fuzzy |
| 3372 |
#| msgid "" |
| 3373 |
#| "<computeroutput>root@mirwiz:~# </computeroutput><userinput>lxc-create -n testlxc -t debian\n" |
| 3374 |
#| "</userinput><computeroutput>debootstrap is /usr/sbin/debootstrap\n" |
| 3375 |
#| "Checking cache download in /var/cache/lxc/debian/rootfs-jessie-amd64 ... \n" |
| 3376 |
#| "Downloading debian minimal ...\n" |
| 3377 |
#| "I: Retrieving Release \n" |
| 3378 |
#| "I: Retrieving Release.gpg \n" |
| 3379 |
#| "[...]\n" |
| 3380 |
#| "Download complete.\n" |
| 3381 |
#| "Copying rootfs to /var/lib/lxc/testlxc/rootfs...\n" |
| 3382 |
#| "[...]\n" |
| 3383 |
#| "Root password is 'sSiKhMzI', please change !\n" |
| 3384 |
#| "root@mirwiz:~# </computeroutput>\n" |
| 3385 |
#| " " |
| 3386 |
msgid "" |
| 3387 |
"<computeroutput># </computeroutput><userinput>lxc-create -n testlxc -t debian\n" |
| 3388 |
"</userinput><computeroutput>debootstrap is /usr/sbin/debootstrap\n" |
| 3389 |
"Checking cache download in /var/cache/lxc/debian/rootfs-stable-amd64 ... \n" |
| 3390 |
"Downloading debian minimal ...\n" |
| 3391 |
"I: Retrieving Release \n" |
| 3392 |
"I: Retrieving Release.gpg \n" |
| 3393 |
"[...]\n" |
| 3394 |
"Download complete.\n" |
| 3395 |
"Copying rootfs to /var/lib/lxc/testlxc/rootfs...\n" |
| 3396 |
"[...]\n" |
| 3397 |
"# </computeroutput>" |
| 3398 |
msgstr "" |
| 3399 |
"<computeroutput>root@mirwiz:~# </computeroutput><userinput>lxc-create -n testlxc -t debian\n" |
| 3400 |
"</userinput><computeroutput>debootstrap は /usr/sbin/debootstrap です\n" |
| 3401 |
"Checking cache download in /var/cache/lxc/debian/rootfs-jessie-amd64 ... \n" |
| 3402 |
"Downloading debian minimal ...\n" |
| 3403 |
"I: Retrieving Release \n" |
| 3404 |
"I: Retrieving Release.gpg \n" |
| 3405 |
"[...]\n" |
| 3406 |
"Download complete.\n" |
| 3407 |
"Copying rootfs to /var/lib/lxc/testlxc/rootfs...\n" |
| 3408 |
"[...]\n" |
| 3409 |
"Root password is 'sSiKhMzI', please change !\n" |
| 3410 |
"root@mirwiz:~# </computeroutput>\n" |
| 3411 |
" " |
| 3412 |
|
| 3413 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3414 |
msgid "Note that the filesystem is initially created in <filename>/var/cache/lxc</filename>, then moved to its destination directory. This allows creating identical containers much more quickly, since only copying is then required." |
| 3415 |
msgstr "ファイルシステムは最初に <filename>/var/cache/lxc</filename> の中に作成され、その後目的のディレクトリに移動されます。こうすることで、同一のコンテナが極めて素早く作成されます。なぜなら、単純にコピーするだけだからです。" |
| 3416 |
|
| 3417 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3418 |
#, fuzzy |
| 3419 |
#| msgid "Note that the debian template creation script accepts an <option>--arch</option> option to specify the architecture of the system to be installed and a <option>--release</option> option if you want to install something else than the current stable release of Debian. You can also set the <literal>MIRROR</literal> environment variable to point to a local Debian mirror." |
| 3420 |
msgid "Note that the Debian template creation script accepts an <option>--arch</option> option to specify the architecture of the system to be installed and a <option>--release</option> option if you want to install something else than the current stable release of Debian. You can also set the <literal>MIRROR</literal> environment variable to point to a local Debian mirror." |
| 3421 |
msgstr "この debian テンプレート作成スクリプトは、インストールされるシステムのアーキテクチャを指定する <option>--arch</option> オプションと、現在の Debian 安定版以外の物をインストールしたい場合に指定する <option>--release</option> オプションを取ります。また、<literal>MIRROR</literal> 環境変数を設定してローカル Debian アーカイブミラーを指定することも可能です。" |
| 3422 |
|
| 3423 |
msgid "The <emphasis role=\"pkg\">lxc</emphasis> package further creates a bridge interface <literal>lxcbr0</literal>, which by default is used by all newly created containers via <filename>/etc/lxc/default.conf</filename> and the <filename>lxc-net</filename> service:" |
| 3424 |
msgstr "" |
| 3425 |
|
| 3426 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3427 |
#, fuzzy |
| 3428 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3429 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/lxc/default.conf</filename></secondary>" |
| 3430 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3431 |
|
| 3432 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3433 |
#, fuzzy |
| 3434 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3435 |
msgid "<primary>service</primary><secondary><filename>lxc-net.service</filename></secondary>" |
| 3436 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3437 |
|
| 3438 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3439 |
#, fuzzy |
| 3440 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3441 |
msgid "<primary>network</primary><secondary><literal>veth</literal> interface</secondary>" |
| 3442 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3443 |
|
| 3444 |
msgid "<primary><literal>veth</literal>, network interface</primary>" |
| 3445 |
msgstr "" |
| 3446 |
|
| 3447 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3448 |
#, fuzzy |
| 3449 |
#| msgid "" |
| 3450 |
#| "lxc.network.type = veth\n" |
| 3451 |
#| "lxc.network.flags = up\n" |
| 3452 |
#| "lxc.network.link = br0\n" |
| 3453 |
#| "lxc.network.hwaddr = 4a:49:43:49:79:20" |
| 3454 |
msgid "" |
| 3455 |
"lxc.net.0.type = veth\n" |
| 3456 |
"lxc.net.0.link = lxcbr0\n" |
| 3457 |
"lxc.net.0.flags = up" |
| 3458 |
msgstr "" |
| 3459 |
"lxc.network.type = veth\n" |
| 3460 |
"lxc.network.flags = up\n" |
| 3461 |
"lxc.network.link = br0\n" |
| 3462 |
"lxc.network.hwaddr = 4a:49:43:49:79:20" |
| 3463 |
|
| 3464 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3465 |
#, fuzzy |
| 3466 |
#| msgid "These entries mean, respectively, that a virtual interface will be created in the container; that it will automatically be brought up when said container is started; that it will automatically be connected to the <literal>br0</literal> bridge on the host; and that its MAC address will be as specified. Should this last entry be missing or disabled, a random MAC address will be generated." |
| 3467 |
msgid "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated." |
| 3468 |
msgstr "これらのエントリの意味するところはそれぞれ、仮想インターフェースはコンテナによって作られます。そして仮想インターフェースはコンテナが開始された時に自動的に利用できる状態にされます。そして仮想インターフェースはホストの <literal>br0</literal> ブリッジに自動的に接続されます。さらに仮想インターフェースの MAC アドレスは指定したものになります。最後のエントリを削除するか無効化した場合、ランダムな MAC アドレスが生成されます。" |
| 3469 |
|
| 3470 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3471 |
#, fuzzy |
| 3472 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3473 |
msgid "<primary>LXC</primary><secondary>container configuration</secondary>" |
| 3474 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3475 |
|
| 3476 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3477 |
msgid "Another useful entry in that file is the setting of the hostname:" |
| 3478 |
msgstr "以下のようにすることで、設定ファイル内でホスト名を設定することも可能です。" |
| 3479 |
|
| 3480 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3481 |
#, fuzzy |
| 3482 |
#| msgid "lxc.utsname = testlxc" |
| 3483 |
msgid "lxc.uts.name = testlxc" |
| 3484 |
msgstr "lxc.utsname = testlxc" |
| 3485 |
|
| 3486 |
msgid "The newly-created filesystem now contains a minimal Debian system and a network interface." |
| 3487 |
msgstr "" |
| 3488 |
|
| 3489 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3490 |
msgid "Starting the Container" |
| 3491 |
msgstr "コンテナの開始" |
| 3492 |
|
| 3493 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3494 |
#, fuzzy |
| 3495 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3496 |
msgid "<primary>LXC</primary><secondary><command>lxc-start</command></secondary>" |
| 3497 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3498 |
|
| 3499 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3500 |
#, fuzzy |
| 3501 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3502 |
msgid "<primary>LXC</primary><secondary><command>lxc-attach</command></secondary>" |
| 3503 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3504 |
|
| 3505 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3506 |
#, fuzzy |
| 3507 |
#| msgid "Now that our virtual machine image is ready, let's start the container:" |
| 3508 |
msgid "Now that our virtual machine image is ready, let's start the container with <command>lxc-start --name=testlxc</command>." |
| 3509 |
msgstr "これで仮想マシンイメージの準備が整いました。それではコンテナを開始しましょう。" |
| 3510 |
|
| 3511 |
msgid "In LXC releases following 2.0.8, root passwords are not set by default. We can set one running <command>lxc-attach -n testlxc <replaceable>passwd</replaceable></command> if we want. We can login with:" |
| 3512 |
msgstr "" |
| 3513 |
|
| 3514 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3515 |
#, fuzzy |
| 3516 |
#| msgid "" |
| 3517 |
#| "<computeroutput>root@mirwiz:~# </computeroutput><userinput>lxc-start --daemon --name=testlxc\n" |
| 3518 |
#| "</userinput><computeroutput>root@mirwiz:~# </computeroutput><userinput>lxc-console -n testlxc\n" |
| 3519 |
#| "</userinput><computeroutput>Debian GNU/Linux 8 testlxc tty1\n" |
| 3520 |
#| "\n" |
| 3521 |
#| "testlxc login: </computeroutput><userinput>root</userinput><computeroutput>\n" |
| 3522 |
#| "Password: \n" |
| 3523 |
#| "Linux testlxc 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64\n" |
| 3524 |
#| "\n" |
| 3525 |
#| "The programs included with the Debian GNU/Linux system are free software;\n" |
| 3526 |
#| "the exact distribution terms for each program are described in the\n" |
| 3527 |
#| "individual files in /usr/share/doc/*/copyright.\n" |
| 3528 |
#| "\n" |
| 3529 |
#| "Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\n" |
| 3530 |
#| "permitted by applicable law.\n" |
| 3531 |
#| "root@testlxc:~# </computeroutput><userinput>ps auxwf</userinput>\n" |
| 3532 |
#| "<computeroutput>USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND\n" |
| 3533 |
#| "root 1 0.0 0.2 28164 4432 ? Ss 17:33 0:00 /sbin/init\n" |
| 3534 |
#| "root 20 0.0 0.1 32960 3160 ? Ss 17:33 0:00 /lib/systemd/systemd-journald\n" |
| 3535 |
#| "root 82 0.0 0.3 55164 5456 ? Ss 17:34 0:00 /usr/sbin/sshd -D\n" |
| 3536 |
#| "root 87 0.0 0.1 12656 1924 tty2 Ss+ 17:34 0:00 /sbin/agetty --noclear tty2 linux\n" |
| 3537 |
#| "root 88 0.0 0.1 12656 1764 tty3 Ss+ 17:34 0:00 /sbin/agetty --noclear tty3 linux\n" |
| 3538 |
#| "root 89 0.0 0.1 12656 1908 tty4 Ss+ 17:34 0:00 /sbin/agetty --noclear tty4 linux\n" |
| 3539 |
#| "root 90 0.0 0.1 63300 2944 tty1 Ss 17:34 0:00 /bin/login -- \n" |
| 3540 |
#| "root 117 0.0 0.2 21828 3668 tty1 S 17:35 0:00 \\_ -bash\n" |
| 3541 |
#| "root 268 0.0 0.1 19088 2572 tty1 R+ 17:39 0:00 \\_ ps auxfw\n" |
| 3542 |
#| "root 91 0.0 0.1 14228 2356 console Ss+ 17:34 0:00 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 vt102\n" |
| 3543 |
#| "root 197 0.0 0.4 25384 7640 ? Ss 17:38 0:00 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.e\n" |
| 3544 |
#| "root 266 0.0 0.1 12656 1840 ? Ss 17:39 0:00 /sbin/agetty --noclear tty5 linux\n" |
| 3545 |
#| "root 267 0.0 0.1 12656 1928 ? Ss 17:39 0:00 /sbin/agetty --noclear tty6 linux\n" |
| 3546 |
#| "root@testlxc:~# </computeroutput>" |
| 3547 |
msgid "" |
| 3548 |
"<computeroutput># </computeroutput><userinput>lxc-console -n testlxc\n" |
| 3549 |
"</userinput><computeroutput><![CDATA[Connected to tty 1\n" |
| 3550 |
"Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself\n" |
| 3551 |
"\n" |
| 3552 |
"Debian GNU/Linux 11 testlxc tty1\n" |
| 3553 |
"\n" |
| 3554 |
"testlxc login: ]]></computeroutput><userinput>root</userinput><computeroutput>\n" |
| 3555 |
"Password: \n" |
| 3556 |
"Linux testlxc 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64\n" |
| 3557 |
"\n" |
| 3558 |
"The programs included with the Debian GNU/Linux system are free software;\n" |
| 3559 |
"the exact distribution terms for each program are described in the\n" |
| 3560 |
"individual files in /usr/share/doc/*/copyright.\n" |
| 3561 |
"\n" |
| 3562 |
"Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\n" |
| 3563 |
"permitted by applicable law.\n" |
| 3564 |
"Last login: Wed Mar 9 01:45:21 UTC 2022 on console\n" |
| 3565 |
"root@testlxc:~# </computeroutput><userinput>ps auxwf\n" |
| 3566 |
"</userinput><computeroutput>USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND\n" |
| 3567 |
"root 1 0.0 0.2 18964 11464 ? Ss 01:36 0:00 /sbin/init\n" |
| 3568 |
"root 45 0.0 0.2 31940 10396 ? Ss 01:37 0:00 /lib/systemd/systemd-journald\n" |
| 3569 |
"root 71 0.0 0.1 99800 5724 ? Ssl 01:37 0:00 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid [..]\n" |
| 3570 |
"root 97 0.0 0.1 13276 6980 ? Ss 01:37 0:00 sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups\n" |
| 3571 |
"root 160 0.0 0.0 6276 3928 pts/0 Ss 01:46 0:00 /bin/login -p --\n" |
| 3572 |
"root 169 0.0 0.0 7100 3824 pts/0 S 01:51 0:00 \\_ -bash\n" |
| 3573 |
"root 172 0.0 0.0 9672 3348 pts/0 R+ 01:51 0:00 \\_ ps auxwf\n" |
| 3574 |
"root 164 0.0 0.0 5416 2128 pts/1 Ss+ 01:49 0:00 /sbin/agetty -o -p -- \\u --noclear [...]\n" |
| 3575 |
"root@testlxc:~# </computeroutput>" |
| 3576 |
msgstr "" |
| 3577 |
"<computeroutput>root@mirwiz:~# </computeroutput><userinput>lxc-start --daemon --name=testlxc\n" |
| 3578 |
"</userinput><computeroutput>root@mirwiz:~# </computeroutput><userinput>lxc-console -n testlxc\n" |
| 3579 |
"</userinput><computeroutput>Debian GNU/Linux 8 testlxc tty1\n" |
| 3580 |
"\n" |
| 3581 |
"testlxc login: </computeroutput><userinput>root</userinput><computeroutput>\n" |
| 3582 |
"Password: \n" |
| 3583 |
"Linux testlxc 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64\n" |
| 3584 |
"\n" |
| 3585 |
"The programs included with the Debian GNU/Linux system are free software;\n" |
| 3586 |
"the exact distribution terms for each program are described in the\n" |
| 3587 |
"individual files in /usr/share/doc/*/copyright.\n" |
| 3588 |
"\n" |
| 3589 |
"Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\n" |
| 3590 |
"permitted by applicable law.\n" |
| 3591 |
"root@testlxc:~# </computeroutput><userinput>ps auxwf</userinput>\n" |
| 3592 |
"<computeroutput>USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND\n" |
| 3593 |
"root 1 0.0 0.2 28164 4432 ? Ss 17:33 0:00 /sbin/init\n" |
| 3594 |
"root 20 0.0 0.1 32960 3160 ? Ss 17:33 0:00 /lib/systemd/systemd-journald\n" |
| 3595 |
"root 82 0.0 0.3 55164 5456 ? Ss 17:34 0:00 /usr/sbin/sshd -D\n" |
| 3596 |
"root 87 0.0 0.1 12656 1924 tty2 Ss+ 17:34 0:00 /sbin/agetty --noclear tty2 linux\n" |
| 3597 |
"root 88 0.0 0.1 12656 1764 tty3 Ss+ 17:34 0:00 /sbin/agetty --noclear tty3 linux\n" |
| 3598 |
"root 89 0.0 0.1 12656 1908 tty4 Ss+ 17:34 0:00 /sbin/agetty --noclear tty4 linux\n" |
| 3599 |
"root 90 0.0 0.1 63300 2944 tty1 Ss 17:34 0:00 /bin/login -- \n" |
| 3600 |
"root 117 0.0 0.2 21828 3668 tty1 S 17:35 0:00 \\_ -bash\n" |
| 3601 |
"root 268 0.0 0.1 19088 2572 tty1 R+ 17:39 0:00 \\_ ps auxfw\n" |
| 3602 |
"root 91 0.0 0.1 14228 2356 console Ss+ 17:34 0:00 /sbin/agetty --noclear --keep-baud console 115200 38400 9600 vt102\n" |
| 3603 |
"root 197 0.0 0.4 25384 7640 ? Ss 17:38 0:00 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.e\n" |
| 3604 |
"root 266 0.0 0.1 12656 1840 ? Ss 17:39 0:00 /sbin/agetty --noclear tty5 linux\n" |
| 3605 |
"root 267 0.0 0.1 12656 1928 ? Ss 17:39 0:00 /sbin/agetty --noclear tty6 linux\n" |
| 3606 |
"root@testlxc:~# </computeroutput>" |
| 3607 |
|
| 3608 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3609 |
msgid "We are now in the container; our access to the processes is restricted to only those started from the container itself, and our access to the filesystem is similarly restricted to the dedicated subset of the full filesystem (<filename>/var/lib/lxc/testlxc/rootfs</filename>). We can exit the console with <keycombo action=\"simul\"><keycap>Control</keycap> <keycap>a</keycap></keycombo> <keycombo><keycap>q</keycap></keycombo>." |
| 3610 |
msgstr "これでコンテナの中に入りました。プロセスへのアクセスはコンテナ自身によって開始されたものだけに制限されていることがわかります。同様に、ファイルシステムへのアクセスも testlxc コンテナ専用に割り当てられた完全なファイルシステムの一部分 (<filename>/var/lib/lxc/testlxc/rootfs</filename>) に制限されています。コンソールを終了するには <keycombo action=\"simul\"><keycap>Control</keycap> <keycap>a</keycap></keycombo> <keycombo><keycap>q</keycap></keycombo> を使います。" |
| 3611 |
|
| 3612 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3613 |
#, fuzzy |
| 3614 |
#| msgid "Note that we ran the container as a background process, thanks to the <option>--daemon</option> option of <command>lxc-start</command>. We can interrupt the container with a command such as <command>lxc-stop --name=testlxc</command>." |
| 3615 |
msgid "Note that we ran the container as a background process, thanks to <command>lxc-start</command> starting using the <option>--daemon</option> option by default. We can interrupt the container with a command such as <command>lxc-stop --name=testlxc</command>." |
| 3616 |
msgstr "<command>lxc-start</command> に <option>--daemon</option> オプションを渡したおかげで、コンテナがバックグラウンドプロセスとして実行されていることに注意してください。コンテナを中止するには <command>lxc-stop --name=testlxc</command> などのコマンドを使います。" |
| 3617 |
|
| 3618 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3619 |
#, fuzzy |
| 3620 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3621 |
msgid "<primary>LXC</primary><secondary><command>lxc-stop</command></secondary>" |
| 3622 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3623 |
|
| 3624 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3625 |
msgid "The <emphasis role=\"pkg\">lxc</emphasis> package contains an initialization script that can automatically start one or several containers when the host boots (it relies on <command>lxc-autostart</command> which starts containers whose <literal>lxc.start.auto</literal> option is set to 1). Finer-grained control of the startup order is possible with <literal>lxc.start.order</literal> and <literal>lxc.group</literal>: by default, the initialization script first starts containers which are part of the <literal>onboot</literal> group and then the containers which are not part of any group. In both cases, the order within a group is defined by the <literal>lxc.start.order</literal> option." |
| 3626 |
msgstr "<emphasis role=\"pkg\">lxc</emphasis> パッケージには、ホストの起動時に自動的に 1 つまたは複数のコンテナを開始するための初期化スクリプトが含まれます (この初期化スクリプトは <literal>lxc.start.auto</literal> オプションが 1 に設定されているコンテナを起動する <command>lxc-autostart</command> に依存しています)。起動順序を非常に細かく制御するには <literal>lxc.start.order</literal> と <literal>lxc.group</literal> を使います。デフォルトの場合、初期化スクリプトは <literal>onboot</literal> グループに所属するコンテナを起動し、その後いかなるグループにも所属しないコンテナを起動します。どちらの場合も、グループ内の起動順序を制御するには <literal>lxc.start.order</literal> オプションを使います。" |
| 3627 |
|
| 3628 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3629 |
msgid "<emphasis>GOING FURTHER</emphasis> Mass virtualization" |
| 3630 |
msgstr "<emphasis>GOING FURTHER</emphasis> 大量の仮想化" |
| 3631 |
|
| 3632 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3633 |
msgid "Since LXC is a very lightweight isolation system, it can be particularly adapted to massive hosting of virtual servers. The network configuration will probably be a bit more advanced than what we described above, but the “rich” configuration using <literal>tap</literal> and <literal>veth</literal> interfaces should be enough in many cases." |
| 3634 |
msgstr "LXC は非常に軽量の隔離システムですから、LXC を使って仮想サーバを大量にホストすることが可能です。この場合のネットワーク設定は上に述べた物よりも少し高度なものになるかもしれませんが、多くの場合 <literal>tap</literal> と <literal>veth</literal> インターフェースを用いた「ぜいたくな」設定を使えば事足ります。" |
| 3635 |
|
| 3636 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3637 |
msgid "It may also make sense to share part of the filesystem, such as the <filename>/usr</filename> and <filename>/lib</filename> subtrees, so as to avoid duplicating the software that may need to be common to several containers. This will usually be achieved with <literal>lxc.mount.entry</literal> entries in the containers configuration file. An interesting side-effect is that the processes will then use less physical memory, since the kernel is able to detect that the programs are shared. The marginal cost of one extra container can then be reduced to the disk space dedicated to its specific data, and a few extra processes that the kernel must schedule and manage." |
| 3638 |
msgstr "ファイルシステムの一部 (たとえば <filename>/usr</filename> と <filename>/lib</filename> などのサブツリー) を共有することは合理的です。こうすることで、複数のコンテナで共通に必要なソフトウェアを複製することを避けることが可能です。通常これを設定するには、コンテナ設定ファイルに含まれる <literal>lxc.mount.entry</literal> エントリを使います。さらに興味深い副作用として、より少ない物理メモリでプロセスを動かすことが可能になります。なぜなら、カーネルはプログラムが共有されていることを検出できるからです。このことにより 1 つのコンテナを追加するためのコストをコンテナに特有のデータに割り当てられたディスク領域と、カーネルがスケジュールと管理に使ういくつかの追加的プロセスだけに減らすことが可能です。" |
| 3639 |
|
| 3640 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3641 |
msgid "We haven't described all the available options, of course; more comprehensive information can be obtained from the <citerefentry> <refentrytitle>lxc</refentrytitle> <manvolnum>7</manvolnum> </citerefentry> and <citerefentry> <refentrytitle>lxc.container.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual pages and the ones they reference." |
| 3642 |
msgstr "もちろん、ここではすべての利用できるオプションを説明していません。このため、より広範囲におよぶ情報を入手するには、<citerefentry> <refentrytitle>lxc</refentrytitle> <manvolnum>7</manvolnum> </citerefentry> と <citerefentry> <refentrytitle>lxc.container.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> マニュアルページおよびこれらのマニュアルページから参照されている文書を参照してください。" |
| 3643 |
|
| 3644 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3645 |
msgid "Virtualization with KVM" |
| 3646 |
msgstr "KVM を使った仮想化" |
| 3647 |
|
| 3648 |
msgid "<primary>Kernel-based Virtual Machine</primary><see>KVM</see>" |
| 3649 |
msgstr "" |
| 3650 |
|
| 3651 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3652 |
msgid "KVM, which stands for <emphasis>Kernel-based Virtual Machine</emphasis>, is first and foremost a kernel module providing most of the infrastructure that can be used by a virtualizer, but it is not a virtualizer by itself. Actual control for the virtualization is handled by a QEMU-based application. Don't worry if this section mentions <command>qemu-*</command> commands: it is still about KVM." |
| 3653 |
msgstr "KVM は <emphasis>Kernel-based Virtual Machine</emphasis> を意味しており、仮想化システムの使うほとんどの基礎構造を提供する最初で最高のカーネルモジュールです。しかしながら、LVM 自身は仮想化システムではありません。仮想化の実際の制御を行うには QEMU に基づくアプリケーションを使います。この節で <command>qemu-*</command> コマンドがあっても心配しないでください。なぜならこのコマンドは KVM に関連するものだからです。" |
| 3654 |
|
| 3655 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3656 |
msgid "Unlike other virtualization systems, KVM was merged into the Linux kernel right from the start. Its developers chose to take advantage of the processor instruction sets dedicated to virtualization (Intel-VT and AMD-V), which keeps KVM lightweight, elegant and not resource-hungry. The counterpart, of course, is that KVM doesn't work on any computer but only on those with appropriate processors. For x86-based computers, you can verify that you have such a processor by looking for “vmx” or “svm” in the CPU flags listed in <filename>/proc/cpuinfo</filename>." |
| 3657 |
msgstr "他の仮想化システムと異なり、KVM は最初から Linux カーネルにマージされていました。KVM の開発者はプロセッサが備える仮想化専用命令セット (Intel-VT と AMD-V) を有効活用することを選びました。仮想化専用命令セットを活用することで、KVM は軽量で簡潔でリソースを大量に消費しないものになっています。もちろんその代償として KVM にも欠点があります。それはすべてのコンピュータが KVM を動かせるわけではなく、適切なプロセッサを備えたコンピュータでなければ KVM を動かせないという点です。x86 ベースのコンピュータで <filename>/proc/cpuinfo</filename> 内の CPU フラグに「vmx」または「svm」が含まれている場合、そのプロセッサは KVM を動かすことができることを意味します。" |
| 3658 |
|
| 3659 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3660 |
#, fuzzy |
| 3661 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3662 |
msgid "<primary><filename>/proc</filename></primary><secondary><filename>/proc/cpuinfo</filename></secondary>" |
| 3663 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3664 |
|
| 3665 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3666 |
msgid "With Red Hat actively supporting its development, KVM has more or less become the reference for Linux virtualization." |
| 3667 |
msgstr "Red Hat が KVM の開発を活発に支援したことで、KVM は事実上 Linux 仮想化の基準点になりました。" |
| 3668 |
|
| 3669 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3670 |
msgid "<primary><command>virt-install</command></primary>" |
| 3671 |
msgstr "<primary><command>virt-install</command></primary>" |
| 3672 |
|
| 3673 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3674 |
#, fuzzy |
| 3675 |
#| msgid "Unlike such tools as VirtualBox, KVM itself doesn't include any user-interface for creating and managing virtual machines. The <emphasis role=\"pkg\">qemu-kvm</emphasis> package only provides an executable able to start a virtual machine, as well as an initialization script that loads the appropriate kernel modules." |
| 3676 |
msgid "Unlike such tools as VirtualBox, KVM itself doesn't include any user-interface for creating and managing virtual machines. The virtual <emphasis role=\"pkg\">qemu-kvm</emphasis> package only provides an executable able to start a virtual machine, as well as an initialization script that loads the appropriate kernel modules." |
| 3677 |
msgstr "VirtualBox などのツールと異なり、KVM は仮想マシンを作成管理するためのユーザインターフェースを含みません。仮想マシンを開始することが可能な実行ファイルおよび適切なカーネルモジュールを読み込むための初期化スクリプトを含むパッケージが <emphasis role=\"pkg\">qemu-kvm</emphasis> パッケージです。" |
| 3678 |
|
| 3679 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3680 |
msgid "<primary>libvirt</primary>" |
| 3681 |
msgstr "<primary>libvirt</primary>" |
| 3682 |
|
| 3683 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3684 |
#, fuzzy |
| 3685 |
#| msgid "<primary>LVM</primary>" |
| 3686 |
msgid "<primary>OpenVZ</primary>" |
| 3687 |
msgstr "<primary>LVM</primary>" |
| 3688 |
|
| 3689 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3690 |
#, fuzzy |
| 3691 |
#| msgid "<primary>LVM</primary>" |
| 3692 |
msgid "<primary>UML</primary>" |
| 3693 |
msgstr "<primary>LVM</primary>" |
| 3694 |
|
| 3695 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3696 |
#, fuzzy |
| 3697 |
#| msgid "Fortunately, Red Hat also provides another set of tools to address that problem, by developing the <emphasis>libvirt</emphasis> library and the associated <emphasis>virtual machine manager</emphasis> tools. libvirt allows managing virtual machines in a uniform way, independently of the virtualization system involved behind the scenes (it currently supports QEMU, KVM, Xen, LXC, OpenVZ, VirtualBox, VMWare and UML). <command>virtual-manager</command> is a graphical interface that uses libvirt to create and manage virtual machines." |
| 3698 |
msgid "Fortunately, Red Hat also provides another set of tools to address that problem, by developing the <emphasis>libvirt</emphasis> library and the associated <emphasis>virtual machine manager</emphasis> tools. libvirt allows managing virtual machines in a uniform way, independently of the virtualization system involved behind the scenes (it currently supports QEMU, KVM, Xen, LXC, OpenVZ, VirtualBox, VMWare, and UML). <command>virt-manager</command> is a graphical interface that uses <emphasis>libvirt</emphasis> to create and manage virtual machines." |
| 3699 |
msgstr "幸いなことに、Red Hat は <emphasis>libvirt</emphasis> ライブラリおよび関連する<emphasis>仮想マシンマネージャ</emphasis>ツールを開発することで、この問題に対処するためのツールを提供しています。libvirt により仮想マシンを管理する方法が統一され、仮想マシンの管理方法が裏で動く仮想システムに依存しなくなります (libvirt は現在 QEMU、KVM、Xen、LXC、OpenVZ、VirtualBox、VMWare、UML をサポートしています)。<command>virtual-manager</command> は仮想マシンを作成管理するために libvirt を使うグラフィルインターフェースです。" |
| 3700 |
|
| 3701 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3702 |
msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 3703 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 3704 |
|
| 3705 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3706 |
#, fuzzy |
| 3707 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3708 |
msgid "<primary>daemon</primary><secondary>libvirtd</secondary>" |
| 3709 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3710 |
|
| 3711 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3712 |
#, fuzzy |
| 3713 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3714 |
msgid "<primary>service</primary><secondary><filename>libvirtd.service</filename></secondary>" |
| 3715 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3716 |
|
| 3717 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3718 |
#, fuzzy |
| 3719 |
#| msgid "We first install the required packages, with <command>apt-get install qemu-kvm libvirt-bin virtinst virt-manager virt-viewer</command>. <emphasis role=\"pkg\">libvirt-bin</emphasis> provides the <command>libvirtd</command> daemon, which allows (potentially remote) management of the virtual machines running of the host, and starts the required VMs when the host boots. In addition, this package provides the <command>virsh</command> command-line tool, which allows controlling the <command>libvirtd</command>-managed machines." |
| 3720 |
msgid "We first install the required packages, with <command>apt-get install libvirt-clients libvirt-daemon-system qemu-kvm virtinst virt-manager virt-viewer</command>. <emphasis role=\"pkg\">libvirt-daemon-system</emphasis> provides the <command>libvirtd</command> daemon, which allows (potentially remote) management of the virtual machines running of the host, and starts the required VMs when the host boots. <emphasis role=\"pkg\">libvirt-clients</emphasis> provides the <command>virsh</command> command-line tool, which allows controlling the <command>libvirtd</command>-managed machines." |
| 3721 |
msgstr "最初に <command>apt-get install qemu-kvm libvirt-bin virtinst virt-manager virt-viewer</command> を使って、必要なパッケージをインストールします。<emphasis role=\"pkg\">libvirt-bin</emphasis> には、<command>libvirtd</command> デーモンが含まれます。<command>libvirtd</command> デーモンを使うことでホストで実行されている仮想マシンを (潜在的にリモートで) 管理したり、ホスト起動時に要求された VM を開始したりすることが可能です。加えて、<emphasis role=\"pkg\">libvirt-bin</emphasis> パッケージは <command>virsh</command> コマンドラインツールを提供します。<command>virsh</command> を使うことで、<command>libvirtd</command> の管理するマシンを操作することが可能です。" |
| 3722 |
|
| 3723 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3724 |
# Tag: L-CFMD; |
| 3725 |
#, fuzzy |
| 3726 |
#| msgid "<primary><command>virsh</command></primary>" |
| 3727 |
msgid "<primary><command>virt-viewer</command></primary>" |
| 3728 |
msgstr "<primary><command>virsh</command></primary>" |
| 3729 |
|
| 3730 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3731 |
msgid "The <emphasis role=\"pkg\">virtinst</emphasis> package provides <command>virt-install</command>, which allows creating virtual machines from the command line. Finally, <emphasis role=\"pkg\">virt-viewer</emphasis> allows accessing a VM's graphical console." |
| 3732 |
msgstr "<emphasis role=\"pkg\">virtinst</emphasis> パッケージには <command>virt-install</command> コマンドが含まれます。<command>virt-install</command> を使うことで、コマンドラインから仮想マシンを作成することが可能になります。最後に、<emphasis role=\"pkg\">virt-viewer</emphasis> を使うことで、仮想マシンのグラフィカルコンソールにアクセスすることが可能になります。" |
| 3733 |
|
| 3734 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3735 |
msgid "Just as in Xen and LXC, the most frequent network configuration involves a bridge grouping the network interfaces of the virtual machines (see <xref linkend=\"sect.lxc.network\" />)." |
| 3736 |
msgstr "Xen や LXC と同様に、最もよく使われるネットワーク設定は仮想マシンのネットワークインターフェースをグループ化するブリッジです (<xref linkend=\"sect.lxc.network\" />を参照してください)。" |
| 3737 |
|
| 3738 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3739 |
msgid "Alternatively, and in the default configuration provided by KVM, the virtual machine is assigned a private address (in the 192.168.122.0/24 range), and NAT is set up so that the VM can access the outside network." |
| 3740 |
msgstr "ネットワーク設定には別の方法もあります。KVM の提供するデフォルト設定の中では、仮想マシンに (192.168.122.0/24 の範囲内に) プライベートアドレスが割り当てられており、さらに NAT が設定されています。この設定により仮想マシンは外部ネットワークにアクセスすることが可能です。" |
| 3741 |
|
| 3742 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3743 |
msgid "The rest of this section assumes that the host has an <literal>eth0</literal> physical interface and a <literal>br0</literal> bridge, and that the former is connected to the latter." |
| 3744 |
msgstr "この節の残りでは、ホストが <literal>eth0</literal> 物理インターフェースと <literal>br0</literal> ブリッジを備え、<literal>eth0</literal> が <literal>br0</literal> に接続されていることを仮定します。" |
| 3745 |
|
| 3746 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3747 |
msgid "Installation with <command>virt-install</command>" |
| 3748 |
msgstr "<command>virt-install</command> を使ったインストール" |
| 3749 |
|
| 3750 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3751 |
msgid "Creating a virtual machine is very similar to installing a normal system, except that the virtual machine's characteristics are described in a seemingly endless command line." |
| 3752 |
msgstr "仮想マシンの作成は普通のシステムをインストールするのとよく似ています。違いは、仮想マシンの性質をコマンドラインから非常に長々と指定する点です。" |
| 3753 |
|
| 3754 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3755 |
msgid "Practically speaking, this means we will use the Debian installer, by booting the virtual machine on a virtual DVD-ROM drive that maps to a Debian DVD image stored on the host system. The VM will export its graphical console over the VNC protocol (see <xref linkend=\"sect.remote-desktops\" /> for details), which will allow us to control the installation process." |
| 3756 |
msgstr "具体的に言えば、これはホストシステムに保存された Debian DVD イメージを挿入された仮想 DVD-ROM ドライブから仮想マシンを起動することにより Debian インストーラを使うことを意味します。仮想マシンは VNC プロトコル (詳しくは<xref linkend=\"sect.remote-desktops\" />を参照してください) を介してグラフィカルコンソールに表示されます。これによりインストール作業を操作することが可能になります。" |
| 3757 |
|
| 3758 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3759 |
#, fuzzy |
| 3760 |
#| msgid "We first need to tell libvirtd where to store the disk images, unless the default location (<filename>/var/lib/libvirt/images/</filename>) is fine." |
| 3761 |
msgid "We first need to tell <command>libvirtd</command> where to store the disk images, unless the default location (<filename>/var/lib/libvirt/images/</filename>) is fine." |
| 3762 |
msgstr "最初にディスクイメージの保存先を libvirtd に伝える必要があります。デフォルトの保存先 (<filename>/var/lib/libvirt/images/</filename>) でも構わないならばこれは必要ありません。" |
| 3763 |
|
| 3764 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3765 |
#, fuzzy |
| 3766 |
#| msgid "" |
| 3767 |
#| "<computeroutput>root@mirwiz:~# </computeroutput><userinput>mkdir /srv/kvm</userinput>\n" |
| 3768 |
#| "<computeroutput>root@mirwiz:~# </computeroutput><userinput>virsh pool-create-as srv-kvm dir --target /srv/kvm</userinput>\n" |
| 3769 |
#| "<computeroutput>Pool srv-kvm created\n" |
| 3770 |
#| "\n" |
| 3771 |
#| "root@mirwiz:~# </computeroutput>" |
| 3772 |
msgid "" |
| 3773 |
"<computeroutput># </computeroutput><userinput>mkdir /srv/kvm\n" |
| 3774 |
"</userinput><computeroutput># </computeroutput><userinput>virsh pool-create-as srv-kvm dir --target /srv/kvm\n" |
| 3775 |
"</userinput><computeroutput>Pool srv-kvm created\n" |
| 3776 |
"\n" |
| 3777 |
"# </computeroutput>" |
| 3778 |
msgstr "" |
| 3779 |
"<computeroutput>root@mirwiz:~# </computeroutput><userinput>mkdir /srv/kvm</userinput>\n" |
| 3780 |
"<computeroutput>root@mirwiz:~# </computeroutput><userinput>virsh pool-create-as srv-kvm dir --target /srv/kvm</userinput>\n" |
| 3781 |
"<computeroutput>Pool srv-kvm created\n" |
| 3782 |
"\n" |
| 3783 |
"root@mirwiz:~# </computeroutput>" |
| 3784 |
|
| 3785 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3786 |
msgid "<emphasis>TIP</emphasis> Add your user to the libvirt group" |
| 3787 |
msgstr "<emphasis>TIP</emphasis> libvirt グループに対するユーザの追加" |
| 3788 |
|
| 3789 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3790 |
#, fuzzy |
| 3791 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3792 |
msgid "<primary>group</primary><secondary><literal>libvirt</literal></secondary>" |
| 3793 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3794 |
|
| 3795 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3796 |
#, fuzzy |
| 3797 |
#| msgid "All samples in this section assume that you are running commands as root. Effectively, if you want to control a local libvirt daemon, you need either to be root or to be a member of the <literal>libvirt</literal> group (which is not the case by default). Thus if you want to avoid using root rights too often, you can add yoursel to the <literal>libvirt</literal> group and run the various commands under your user identity." |
| 3798 |
msgid "All samples in this section assume that you are running commands as root. Effectively, if you want to control a local libvirt daemon, you need either to be root or to be a member of the <literal>libvirt</literal> group (which is not the case by default). Thus if you want to avoid using root rights too often, you can add yourself to the <literal>libvirt</literal> group and run the various commands under your user identity." |
| 3799 |
msgstr "この節で挙げたすべての例では、root がコマンドを実行しています。実際、あるユーザがローカルの libvirt デーモンを操作するには、root になるか <literal>libvirt</literal> グループのメンバーになって (デフォルト状態では <literal>libvirt</literal> グループはユーザの初期参加グループに設定されていません) コマンドを実行する必要があります。このユーザに root 権限を頻繁に使わせることを避けたい場合、そのユーザを <literal>libvirt</literal> グループに追加して、本人の権限でさまざまなコマンドを実行するように設定することが可能です。" |
| 3800 |
|
| 3801 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3802 |
msgid "Let us now start the installation process for the virtual machine, and have a closer look at <command>virt-install</command>'s most important options. This command registers the virtual machine and its parameters in libvirtd, then starts it so that its installation can proceed." |
| 3803 |
msgstr "それでは仮想マシンのインストール作業を開始し、<command>virt-install</command> の最も重要なオプションを詳細に見て行きましょう。<command>virt-install</command> は仮想マシンとそのパラメータを libvirtd に登録し、インストールを進めるために仮想マシンを開始します。" |
| 3804 |
|
| 3805 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3806 |
# Tag: L-CFMD; |
| 3807 |
#, fuzzy |
| 3808 |
#| msgid "" |
| 3809 |
#| "<computeroutput># </computeroutput><userinput>virt-install --connect qemu:///system <co id=\"virtinst.connect\"></co>\n" |
| 3810 |
#| " --virt-type kvm <co id=\"virtinst.type\"></co>\n" |
| 3811 |
#| " --name testkvm <co id=\"virtinst.name\"></co>\n" |
| 3812 |
#| " --ram 1024 <co id=\"virtinst.ram\"></co>\n" |
| 3813 |
#| " --disk /srv/kvm/testkvm.qcow,format=qcow2,size=10 <co id=\"virtinst.disk\"></co>\n" |
| 3814 |
#| " --cdrom /srv/isos/debian-8.1.0-amd64-netinst.iso <co id=\"virtinst.cdrom\"></co>\n" |
| 3815 |
#| " --network bridge=br0 <co id=\"virtinst.network\"></co>\n" |
| 3816 |
#| " --vnc <co id=\"virtinst.vnc\"></co>\n" |
| 3817 |
#| " --os-type linux <co id=\"virtinst.os\"></co>\n" |
| 3818 |
#| " --os-variant debianwheezy\n" |
| 3819 |
#| "</userinput><computeroutput>\n" |
| 3820 |
#| "Starting install...\n" |
| 3821 |
#| "Allocating 'testkvm.qcow' | 10 GB 00:00\n" |
| 3822 |
#| "Creating domain... | 0 B 00:00\n" |
| 3823 |
#| "Guest installation complete... restarting guest.\n" |
| 3824 |
#| "</computeroutput>" |
| 3825 |
msgid "" |
| 3826 |
"<computeroutput># </computeroutput><userinput>virt-install --connect qemu:///system <co id=\"virtinst.connect\"></co>\n" |
| 3827 |
" --virt-type kvm <co id=\"virtinst.type\"></co>\n" |
| 3828 |
" --name testkvm <co id=\"virtinst.name\"></co>\n" |
| 3829 |
" --memory 2048 <co id=\"virtinst.ram\"></co>\n" |
| 3830 |
" --disk /srv/kvm/testkvm.qcow,format=qcow2,size=10 <co id=\"virtinst.disk\"></co>\n" |
| 3831 |
" --cdrom /srv/isos/debian-11.2.0-amd64-netinst.iso <co id=\"virtinst.cdrom\"></co>\n" |
| 3832 |
" --network bridge=virbr0 <co id=\"virtinst.network\"></co>\n" |
| 3833 |
" --graphics vnc <co id=\"virtinst.vnc\"></co>\n" |
| 3834 |
" --os-type linux <co id=\"virtinst.os\"></co>\n" |
| 3835 |
" --os-variant debiantesting\n" |
| 3836 |
"</userinput><computeroutput>\n" |
| 3837 |
"\n" |
| 3838 |
"Starting install...\n" |
| 3839 |
"Allocating 'testkvm.qcow'\n" |
| 3840 |
"\n" |
| 3841 |
"</computeroutput>" |
| 3842 |
msgstr "" |
| 3843 |
"<computeroutput># </computeroutput><userinput>virt-install --connect qemu:///system <co id=\"virtinst.connect\"></co>\n" |
| 3844 |
" --virt-type kvm <co id=\"virtinst.type\"></co>\n" |
| 3845 |
" --name testkvm <co id=\"virtinst.name\"></co>\n" |
| 3846 |
" --ram 1024 <co id=\"virtinst.ram\"></co>\n" |
| 3847 |
" --disk /srv/kvm/testkvm.qcow,format=qcow2,size=10 <co id=\"virtinst.disk\"></co>\n" |
| 3848 |
" --cdrom /srv/isos/debian-8.1.0-amd64-netinst.iso <co id=\"virtinst.cdrom\"></co>\n" |
| 3849 |
" --network bridge=br0 <co id=\"virtinst.network\"></co>\n" |
| 3850 |
" --vnc <co id=\"virtinst.vnc\"></co>\n" |
| 3851 |
" --os-type linux <co id=\"virtinst.os\"></co>\n" |
| 3852 |
" --os-variant debianwheezy\n" |
| 3853 |
"</userinput><computeroutput>\n" |
| 3854 |
"Starting install...\n" |
| 3855 |
"Allocating 'testkvm.qcow' | 10 GB 00:00\n" |
| 3856 |
"Creating domain... | 0 B 00:00\n" |
| 3857 |
"Guest installation complete... restarting guest.\n" |
| 3858 |
"</computeroutput>" |
| 3859 |
|
| 3860 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3861 |
# Tag: L-CFMD; |
| 3862 |
msgid "The <literal>--connect</literal> option specifies the “hypervisor” to use. Its form is that of an URL containing a virtualization system (<literal>xen://</literal>, <literal>qemu://</literal>, <literal>lxc://</literal>, <literal>openvz://</literal>, <literal>vbox://</literal>, and so on) and the machine that should host the VM (this can be left empty in the case of the local host). In addition to that, and in the QEMU/KVM case, each user can manage virtual machines working with restricted permissions, and the URL path allows differentiating “system” machines (<literal>/system</literal>) from others (<literal>/session</literal>)." |
| 3863 |
msgstr "<literal>--connect</literal> オプションは使用する「ハイパーバイザ」を指定します。これは仮想システムを表す URL (<literal>xen://</literal>、<literal>qemu://</literal>、<literal>lxc://</literal>、<literal>openvz://</literal>、<literal>vbox://</literal> など) と VM をホストするマシン (ローカルホストの場合、空でも構いません) の形をしています。QEMU/KVM の場合、これに加えて各ユーザは制限されたパーミッションで稼働する仮想マシンを管理できます。この場合 URL パスは「システム」マシン (<literal>/system</literal>) かその他 (<literal>/session</literal>) かで識別されます。" |
| 3864 |
|
| 3865 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3866 |
# Tag: L-CFMD; |
| 3867 |
msgid "Since KVM is managed the same way as QEMU, the <literal>--virt-type kvm</literal> allows specifying the use of KVM even though the URL looks like QEMU." |
| 3868 |
msgstr "<literal>--virt-type kvm</literal> を指定することで KVM を使うことが可能です。<literal>--connect</literal> で指定した URL を一見すると QEMU が使われるように見えますが、これは KVM は QEMU と同じ方法で管理されているためです。" |
| 3869 |
|
| 3870 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3871 |
# Tag: L-CFMD; |
| 3872 |
msgid "The <literal>--name</literal> option defines a (unique) name for the virtual machine." |
| 3873 |
msgstr "<literal>--name</literal> オプションは仮想マシンの (一意的な) 名前を定義します。" |
| 3874 |
|
| 3875 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3876 |
# Tag: L-CFMD; |
| 3877 |
#, fuzzy |
| 3878 |
#| msgid "The <literal>--ram</literal> option allows specifying the amount of RAM (in MB) to allocate for the virtual machine." |
| 3879 |
msgid "The <literal>--memory</literal> option allows specifying the amount of RAM (in MB) to allocate for the virtual machine." |
| 3880 |
msgstr "<literal>--ram</literal> オプションは仮想マシンに割り当てる RAM の量 (MB 単位) を指定します。" |
| 3881 |
|
| 3882 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3883 |
#, fuzzy |
| 3884 |
#| msgid "<primary>libvirt</primary>" |
| 3885 |
msgid "<primary><literal>qcow2</literal></primary>" |
| 3886 |
msgstr "<primary>libvirt</primary>" |
| 3887 |
|
| 3888 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3889 |
# Tag: L-CFMD; |
| 3890 |
#, fuzzy |
| 3891 |
#| msgid "The <literal>--disk</literal> specifies the location of the image file that is to represent our virtual machine's hard disk; that file is created, unless present, with a size (in GB) specified by the <literal>size</literal> parameter. The <literal>format</literal> parameter allows choosing among several ways of storing the image file. The default format (<literal>raw</literal>) is a single file exactly matching the disk's size and contents. We picked a more advanced format here, that is specific to QEMU and allows starting with a small file that only grows when the virtual machine starts actually using space." |
| 3892 |
msgid "The <literal>--disk</literal> specifies the location of the image file that is to represent our virtual machine's hard disk; that file is created, unless present, with a size (in GB) specified by the <literal>size</literal> parameter. The <literal>format</literal> parameter allows choosing among several ways of storing the image file. The default format (<literal>qcow2</literal>) allows starting with a small file that only grows when the virtual machine starts actually using space." |
| 3893 |
msgstr "<literal>--disk</literal> オプションは仮想マシンのハードディスクとして利用するイメージファイルの場所を指定します。このファイルが存在しなければ、<literal>size</literal> パラメータで指定されたサイズ (GB 単位) のイメージファイルが作成されます。<literal>format</literal> パラメータはイメージファイルを保存するさまざまな方法を選択します。デフォルトフォーマット (<literal>raw</literal>) はディスクサイズと内容が全く同じ単一ファイルです。ここではより先進的なフォーマット qcow2 を選びました。qcow2 は QEMU 専用のフォーマットです。qcow2 フォーマットのファイルは作成時のサイズは小さいのですが、仮想マシンが領域を実際に利用することになった時にサイズが増加します。" |
| 3894 |
|
| 3895 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3896 |
# Tag: L-CFMD; |
| 3897 |
msgid "The <literal>--cdrom</literal> option is used to indicate where to find the optical disk to use for installation. The path can be either a local path for an ISO file, an URL where the file can be obtained, or the device file of a physical CD-ROM drive (i.e. <literal>/dev/cdrom</literal>)." |
| 3898 |
msgstr "<literal>--cdrom</literal> オプションはインストール時に利用する光学ディスクの場所を指定するために使われます。場所には ISO ファイルのローカルパス、ファイル取得先の URL、物理 CD-ROM ドライブのデバイスファイル (例 <literal>/dev/cdrom</literal>) のどれか 1 つを使うことが可能です。" |
| 3899 |
|
| 3900 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3901 |
#, fuzzy |
| 3902 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3903 |
msgid "<primary>network</primary><secondary><literal>virbr</literal> interface</secondary>" |
| 3904 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3905 |
|
| 3906 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3907 |
#, fuzzy |
| 3908 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 3909 |
msgid "<primary>libvirt</primary><secondary><literal>virbr</literal></secondary>" |
| 3910 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 3911 |
|
| 3912 |
msgid "<primary><literal>virbr</literal>, network interface</primary>" |
| 3913 |
msgstr "" |
| 3914 |
|
| 3915 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3916 |
# Tag: L-CFMD; |
| 3917 |
msgid "The <literal>--network</literal> specifies how the virtual network card integrates in the host's network configuration. The default behavior (which we explicitly forced in our example) is to integrate it into any pre-existing network bridge. If no such bridge exists, the virtual machine will only reach the physical network through NAT, so it gets an address in a private subnet range (192.168.122.0/24)." |
| 3918 |
msgstr "<literal>--network</literal> オプションはホストネットワーク設定の中に仮想ネットワークを統合する方法を指定します。デフォルトは既存のネットワークブリッジに仮想ネットワークを統合する方法です (例では明示的にこの挙動を指定しています)。指定したブリッジが存在しない場合、仮想マシンが到達できるネットワークは NAT を介した物理ネットワークだけに限定されるので、仮想マシンはプライベートサブネット範囲 (192.168.122.0/24) に含まれるアドレスを割り当てられます。" |
| 3919 |
|
| 3920 |
msgid "The default network configuration, which contains the definition for a <literal>virbr0</literal> bridge interface, can be edited using <command>virsh net-edit default</command> and started via <command>virsh net-start default</command> if not already done automatically during system start." |
| 3921 |
msgstr "" |
| 3922 |
|
| 3923 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3924 |
# Tag: L-CFMD; |
| 3925 |
#, fuzzy |
| 3926 |
#| msgid "<literal>--vnc</literal> states that the graphical console should be made available using VNC. The default behavior for the associated VNC server is to only listen on the local interface; if the VNC client is to be run on a different host, establishing the connection will require setting up an SSH tunnel (see <xref linkend=\"sect.ssh-port-forwarding\" />). Alternatively, the <literal>--vnclisten=0.0.0.0</literal> can be used so that the VNC server is accessible from all interfaces; note that if you do that, you really should design your firewall accordingly." |
| 3927 |
msgid "<literal>--graphics vnc</literal> states that the graphical console should be made available using VNC. The default behavior for the associated VNC server is to only listen on the local interface; if the VNC client is to be run on a different host, establishing the connection will require setting up an SSH tunnel (see <xref linkend=\"sect.ssh-port-forwarding\" />). Alternatively, <literal>--graphics vnc,listen=0.0.0.0</literal> can be used so that the VNC server is accessible from all interfaces; note that if you do that, you really should design your firewall accordingly." |
| 3928 |
msgstr "<literal>--vnc</literal> は VNC を使ってグラフィカルコンソールを利用できるようにすることを意味します。VNC サーバに対するデフォルトの挙動を使った場合、ローカルインターフェースだけがリッスンされます。さらに仮想マシンを操作する VNC クライアントを別のホスト上で実行する場合、VNC 接続を確立するには SSH トンネルを設定する必要があります (<xref linkend=\"sect.ssh-port-forwarding\" />を参照してください)。別の方法として、VNC サーバをすべてのインターフェースを介して利用できるようにするために、<literal>--vnclisten=0.0.0.0</literal> を使うことも可能です。しかしこの方針を取る場合、ファイアウォールを適切に設計するべきという点に注意してください。" |
| 3929 |
|
| 3930 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3931 |
# Tag: L-CFMD; |
| 3932 |
msgid "The <literal>--os-type</literal> and <literal>--os-variant</literal> options allow optimizing a few parameters of the virtual machine, based on some of the known features of the operating system mentioned there." |
| 3933 |
msgstr "<literal>--os-type</literal> と <literal>--os-variant</literal> オプションは、指定されたオペレーティングシステムの備える既知の機能に基づいて、仮想マシンのいくつかのパラメータを最適化するためのものです。" |
| 3934 |
|
| 3935 |
msgid "The full list of OS types can be shown using the <command>osinfo-query os</command> command from the <emphasis role=\"pkg\">libosinfo-bin</emphasis> package." |
| 3936 |
msgstr "" |
| 3937 |
|
| 3938 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3939 |
# Tag: L-CFMD; |
| 3940 |
msgid "At this point, the virtual machine is running, and we need to connect to the graphical console to proceed with the installation process. If the previous operation was run from a graphical desktop environment, this connection should be automatically started. If not, or if we operate remotely, <command>virt-viewer</command> can be run from any graphical environment to open the graphical console (note that the root password of the remote host is asked twice because the operation requires 2 SSH connections):" |
| 3941 |
msgstr "<command>virt-install</command> を実行した時点で仮想マシンが実行されます。インストール作業に進むためには、グラフィカルコンソールに接続する必要があります。上の操作をグラフィカルデスクトップ環境から行った場合、自動的に接続が開始されます。そうでない場合、グラフィカルコンソールを開くために <command>virt-viewer</command> を任意のグラフィカル環境から実行します (この時にリモートホストの root パスワードが 2 回尋ねられる点に注意してください。なぜなら、この操作には 2 つの SSH 接続を必要とするからです)。" |
| 3942 |
|
| 3943 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3944 |
# Tag: L-CFMD; |
| 3945 |
msgid "" |
| 3946 |
"<computeroutput>$ </computeroutput><userinput>virt-viewer --connect qemu+ssh://root@<replaceable>server</replaceable>/system testkvm\n" |
| 3947 |
"</userinput><computeroutput>root@server's password: \n" |
| 3948 |
"root@server's password: </computeroutput>" |
| 3949 |
msgstr "" |
| 3950 |
"<computeroutput>$ </computeroutput><userinput>virt-viewer --connect qemu+ssh://root@<replaceable>server</replaceable>/system testkvm\n" |
| 3951 |
"</userinput><computeroutput>root@server's password: \n" |
| 3952 |
"root@server's password: </computeroutput>" |
| 3953 |
|
| 3954 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3955 |
#, fuzzy |
| 3956 |
#| msgid "Installation with <command>virt-install</command>" |
| 3957 |
msgid "Connecting to installer session using <command>virt-viewer</command>" |
| 3958 |
msgstr "<command>virt-install</command> を使ったインストール" |
| 3959 |
|
| 3960 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3961 |
msgid "When the installation process ends, the virtual machine is restarted, now ready for use." |
| 3962 |
msgstr "インストール作業が終了したら、仮想マシンが再起動されます。これで仮想マシンを利用する準備が整いました。" |
| 3963 |
|
| 3964 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3965 |
# Tag: L-CFMD; |
| 3966 |
msgid "Managing Machines with <command>virsh</command>" |
| 3967 |
msgstr "<command>virsh</command> を使ったマシンの管理" |
| 3968 |
|
| 3969 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3970 |
# Tag: L-CFMD; |
| 3971 |
msgid "Now that the installation is done, let us see how to handle the available virtual machines. The first thing to try is to ask <command>libvirtd</command> for the list of the virtual machines it manages:" |
| 3972 |
msgstr "これでインストールが終了しました。利用できる仮想マシンを取り扱う方法に移りましょう。最初に <command>virsh</command> を使って <command>libvirtd</command> が管理している仮想マシンのリストを確認します。" |
| 3973 |
|
| 3974 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3975 |
# Tag: L-CFMD; |
| 3976 |
#, fuzzy |
| 3977 |
#| msgid "" |
| 3978 |
#| "<computeroutput># </computeroutput><userinput>virsh -c qemu:///system list --all\n" |
| 3979 |
#| " Id Name State\n" |
| 3980 |
#| "----------------------------------\n" |
| 3981 |
#| " - testkvm shut off\n" |
| 3982 |
#| "</userinput>" |
| 3983 |
msgid "" |
| 3984 |
"<computeroutput># </computeroutput><userinput>virsh -c qemu:///system list --all\n" |
| 3985 |
" Id Name State\n" |
| 3986 |
"----------------------------------\n" |
| 3987 |
" 8 testkvm shut off\n" |
| 3988 |
"</userinput>" |
| 3989 |
msgstr "" |
| 3990 |
"<computeroutput># </computeroutput><userinput>virsh -c qemu:///system list --all\n" |
| 3991 |
"</userinput><computeroutput> Id Name State\n" |
| 3992 |
"----------------------------------\n" |
| 3993 |
" - testkvm shut off\n" |
| 3994 |
"</computeroutput>" |
| 3995 |
|
| 3996 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 3997 |
msgid "Let's start our test virtual machine:" |
| 3998 |
msgstr "それではテスト用仮想マシンを起動しましょう。" |
| 3999 |
|
| 4000 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4001 |
# Tag: L-CFMD; |
| 4002 |
msgid "" |
| 4003 |
"<computeroutput># </computeroutput><userinput>virsh -c qemu:///system start testkvm\n" |
| 4004 |
"</userinput><computeroutput>Domain testkvm started</computeroutput>" |
| 4005 |
msgstr "" |
| 4006 |
"<computeroutput># </computeroutput><userinput>virsh -c qemu:///system start testkvm\n" |
| 4007 |
"</userinput><computeroutput>Domain testkvm started</computeroutput>" |
| 4008 |
|
| 4009 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4010 |
# Tag: L-CFMD; |
| 4011 |
msgid "We can now get the connection instructions for the graphical console (the returned VNC display can be given as parameter to <command>vncviewer</command>):" |
| 4012 |
msgstr "そして、グラフィカルコンソールへの接続命令を出します (接続する VNC 画面を <command>vncviewer</command> へのパラメータの形で指定することが可能です)。" |
| 4013 |
|
| 4014 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4015 |
# Tag: L-CFMD; |
| 4016 |
#, fuzzy |
| 4017 |
#| msgid "" |
| 4018 |
#| "<computeroutput># </computeroutput><userinput>virsh -c qemu:///system vncdisplay testkvm\n" |
| 4019 |
#| "</userinput><computeroutput>:0</computeroutput>" |
| 4020 |
msgid "" |
| 4021 |
"<computeroutput># </computeroutput><userinput>virsh -c qemu:///system vncdisplay testkvm\n" |
| 4022 |
"</userinput><computeroutput>127.0.0.1:0</computeroutput>" |
| 4023 |
msgstr "" |
| 4024 |
"<computeroutput># </computeroutput><userinput>virsh -c qemu:///system vncdisplay testkvm\n" |
| 4025 |
"</userinput><computeroutput>:0</computeroutput>" |
| 4026 |
|
| 4027 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4028 |
# Tag: L-CFMD; |
| 4029 |
msgid "Other available <command>virsh</command> subcommands include:" |
| 4030 |
msgstr "その他の利用できる <command>virsh</command> サブコマンドには以下のものがあります。" |
| 4031 |
|
| 4032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4033 |
# Tag: L-CFMD; |
| 4034 |
msgid "<literal>reboot</literal> to restart a virtual machine;" |
| 4035 |
msgstr "<literal>reboot</literal>。仮想マシンを再起動します。" |
| 4036 |
|
| 4037 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4038 |
# Tag: L-CFMD; |
| 4039 |
msgid "<literal>shutdown</literal> to trigger a clean shutdown;" |
| 4040 |
msgstr "<literal>shutdown</literal>。仮想マシンを正常にシャットダウンします。" |
| 4041 |
|
| 4042 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4043 |
# Tag: L-CFMD; |
| 4044 |
msgid "<literal>destroy</literal>, to stop it brutally;" |
| 4045 |
msgstr "<literal>destroy</literal>。仮想マシンを無理やり停止します。" |
| 4046 |
|
| 4047 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4048 |
# Tag: L-CFMD; |
| 4049 |
msgid "<literal>suspend</literal> to pause it;" |
| 4050 |
msgstr "<literal>suspend</literal>。仮想マシンを一時停止します。" |
| 4051 |
|
| 4052 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4053 |
# Tag: L-CFMD; |
| 4054 |
msgid "<literal>resume</literal> to unpause it;" |
| 4055 |
msgstr "<literal>resume</literal>。一時停止された仮想マシンを再開します。" |
| 4056 |
|
| 4057 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4058 |
# Tag: L-CFMD; |
| 4059 |
msgid "<literal>autostart</literal> to enable (or disable, with the <literal>--disable</literal> option) starting the virtual machine automatically when the host starts;" |
| 4060 |
msgstr "<literal>autostart</literal>。ホスト起動時にこの仮想マシンを自動的に起動することを有効化します (または <literal>--disable</literal> オプションを付けて無効化します)。" |
| 4061 |
|
| 4062 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4063 |
# Tag: L-CFMD; |
| 4064 |
msgid "<literal>undefine</literal> to remove all traces of the virtual machine from <command>libvirtd</command>." |
| 4065 |
msgstr "<literal>undefine</literal>。仮想マシンのすべての痕跡を <command>libvirtd</command> から削除します。" |
| 4066 |
|
| 4067 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4068 |
msgid "All these subcommands take a virtual machine identifier as a parameter." |
| 4069 |
msgstr "ここに挙げたすべてのサブコマンドは仮想マシン識別子をパラメータとして受け取ります。" |
| 4070 |
|
| 4071 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4072 |
#, fuzzy |
| 4073 |
#| msgid "Installing an RPM based system in Debian with yum" |
| 4074 |
msgid "Installing an RPM based chroot in Debian with yum" |
| 4075 |
msgstr "yum を使い RPM に基づくシステムを Debian の中にインストールする" |
| 4076 |
|
| 4077 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4078 |
#, fuzzy |
| 4079 |
#| msgid "<primary>LVM</primary>" |
| 4080 |
msgid "<primary>RPM</primary>" |
| 4081 |
msgstr "<primary>LVM</primary>" |
| 4082 |
|
| 4083 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4084 |
#, fuzzy |
| 4085 |
#| msgid "<primary>libvirt</primary>" |
| 4086 |
msgid "<primary>chroot</primary>" |
| 4087 |
msgstr "<primary>libvirt</primary>" |
| 4088 |
|
| 4089 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4090 |
#, fuzzy |
| 4091 |
#| msgid "<primary><command>xm</command></primary>" |
| 4092 |
msgid "<primary><command>yum</command></primary>" |
| 4093 |
msgstr "<primary><command>xm</command></primary>" |
| 4094 |
|
| 4095 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4096 |
#, fuzzy |
| 4097 |
#| msgid "<primary><command>xm</command></primary>" |
| 4098 |
msgid "<primary><command>rpm</command></primary>" |
| 4099 |
msgstr "<primary><command>xm</command></primary>" |
| 4100 |
|
| 4101 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4102 |
# Tag: L-CFMD; |
| 4103 |
#, fuzzy |
| 4104 |
#| msgid "If the virtual machine is meant to run a Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>, as described above. But if the virtual machine is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility (available in the package of the same name)." |
| 4105 |
msgid "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>." |
| 4106 |
msgstr "仮想マシンが Debian (または Debian 派生物) を実行することを意図している場合、上で述べた通り <command>debootstrap</command> を使ってシステムを初期化することが可能です。しかし、仮想マシンに RPM に基づくシステム (Fedora、CentOS、Scientific Linux など) をインストールする場合、<command>yum</command> ユーティリティ (同名のパッケージに含まれます) を使ってシステムをセットアップする必要があります。" |
| 4107 |
|
| 4108 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4109 |
# Tag: L-CFMD; |
| 4110 |
#, fuzzy |
| 4111 |
#| msgid "The procedure requires using <command>rpm</command> to extract an initial set of files, including notably <command>yum</command> configuration files, and then calling <command>yum</command> to extract the remaining set of packages. But since we call <command>yum</command> from outside the chroot, we need to make some temporary changes. In the sample below, the target chroot is <filename>/srv/centos</filename>." |
| 4112 |
msgid "The procedure requires using <command>rpm</command> to extract an initial set of files, including notably <command>yum</command> configuration files, and then calling <command>yum4</command> to extract the remaining set of packages. But since we call <command>yum4</command> from outside the chroot, we need to make some temporary changes. In the sample below, the target chroot is <filename>/srv/centos</filename>." |
| 4113 |
msgstr "RPM に基づくシステムをインストールする際には、特に <command>yum</command> 設定ファイルなどのファイルの初期セットを展開するために <command>rpm</command> を使い、その後パッケージの残りのセットを展開するために <command>yum</command> を呼び出す必要があります。しかし、chroot の外から <command>yum</command> を呼び出しているため、一時的な修正が必要です。以下に載せた例では、対象の chroot 先は <filename>/srv/centos</filename> です。" |
| 4114 |
|
| 4115 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4116 |
# Tag: L-CFMD; |
| 4117 |
#, fuzzy |
| 4118 |
#| msgid "" |
| 4119 |
#| "<computeroutput># </computeroutput><userinput>rootdir=\"/srv/centos\"\n" |
| 4120 |
#| "</userinput><computeroutput># </computeroutput><userinput>mkdir -p \"$rootdir\" /etc/rpm\n" |
| 4121 |
#| "</userinput><computeroutput># </computeroutput><userinput>echo \"%_dbpath /var/lib/rpm\" > /etc/rpm/macros.dbpath\n" |
| 4122 |
#| "</userinput><computeroutput># </computeroutput><userinput>wget http://mirror.centos.org/centos/7/os/x86_64/Packages/centos-release-7-1.1503.el7.centos.2.8.x86_64.rpm\n" |
| 4123 |
#| "</userinput><computeroutput># </computeroutput><userinput>rpm --nodeps --root \"$rootdir\" -i centos-release-7-1.1503.el7.centos.2.8.x86_64.rpm\n" |
| 4124 |
#| "</userinput><computeroutput>rpm: RPM should not be used directly install RPM packages, use Alien instead!\n" |
| 4125 |
#| "rpm: However assuming you know what you are doing...\n" |
| 4126 |
#| "warning: centos-release-7-1.1503.el7.centos.2.8.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY\n" |
| 4127 |
#| "# </computeroutput><userinput>sed -i -e \"s,gpgkey=file:///etc/,gpgkey=file://${rootdir}/etc/,g\" $rootdir/etc/yum.repos.d/*.repo\n" |
| 4128 |
#| "</userinput><computeroutput># </computeroutput><userinput>yum --assumeyes --installroot $rootdir groupinstall core\n" |
| 4129 |
#| "</userinput><computeroutput>[...]\n" |
| 4130 |
#| "# </computeroutput><userinput>sed -i -e \"s,gpgkey=file://${rootdir}/etc/,gpgkey=file:///etc/,g\" $rootdir/etc/yum.repos.d/*.repo\n" |
| 4131 |
#| "</userinput>" |
| 4132 |
msgid "" |
| 4133 |
"<computeroutput># </computeroutput><userinput>rootdir=\"/srv/centos\"\n" |
| 4134 |
"</userinput><computeroutput># </computeroutput><userinput>mkdir -p \"$rootdir\" /etc/rpm\n" |
| 4135 |
"</userinput><computeroutput># </computeroutput><userinput>echo \"%_dbpath /var/lib/rpm\" > /etc/rpm/macros.dbpath\n" |
| 4136 |
"</userinput><computeroutput># </computeroutput><userinput>wget http://mirror.centos.org/centos/7/os/x86_64/Packages/centos-release-7-9.2009.0.el7.centos.x86_64.rpm\n" |
| 4137 |
"</userinput><computeroutput># </computeroutput><userinput>rpm --nodeps --root \"$rootdir\" -i centos-release-7-9.2009.0.el7.centos.x86_64.rpm\n" |
| 4138 |
"</userinput><computeroutput>rpm: RPM should not be used directly install RPM packages, use Alien instead!\n" |
| 4139 |
"rpm: However assuming you know what you are doing...\n" |
| 4140 |
"warning: centos-release-7-9.2009.0.el7.centos.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY\n" |
| 4141 |
"# </computeroutput><userinput>sed -i -e \"s,gpgkey=file:///etc/,gpgkey=file://${rootdir}/etc/,g\" $rootdir/etc/yum.repos.d/*.repo\n" |
| 4142 |
"</userinput><computeroutput># </computeroutput><userinput>yum4 --assumeyes --installroot $rootdir groupinstall core\n" |
| 4143 |
"</userinput><computeroutput>[...]\n" |
| 4144 |
"# </computeroutput><userinput>sed -i -e \"s,gpgkey=file://${rootdir}/etc/,gpgkey=file:///etc/,g\" $rootdir/etc/yum.repos.d/*.repo\n" |
| 4145 |
"</userinput><computeroutput># </computeroutput><userinput>chroot /srv/centos/\n" |
| 4146 |
"</userinput><computeroutput>[root@testsystem /]# </computeroutput>" |
| 4147 |
msgstr "" |
| 4148 |
"<computeroutput># </computeroutput><userinput>rootdir=\"/srv/centos\"\n" |
| 4149 |
"</userinput><computeroutput># </computeroutput><userinput>mkdir -p \"$rootdir\" /etc/rpm\n" |
| 4150 |
"</userinput><computeroutput># </computeroutput><userinput>echo \"%_dbpath /var/lib/rpm\" > /etc/rpm/macros.dbpath\n" |
| 4151 |
"</userinput><computeroutput># </computeroutput><userinput>wget http://mirror.centos.org/centos/7/os/x86_64/Packages/centos-release-7-1.1503.el7.centos.2.8.x86_64.rpm\n" |
| 4152 |
"</userinput><computeroutput># </computeroutput><userinput>rpm --nodeps --root \"$rootdir\" -i centos-release-7-1.1503.el7.centos.2.8.x86_64.rpm\n" |
| 4153 |
"</userinput><computeroutput>rpm: RPM should not be used directly install RPM packages, use Alien instead!\n" |
| 4154 |
"rpm: However assuming you know what you are doing...\n" |
| 4155 |
"warning: centos-release-7-1.1503.el7.centos.2.8.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY\n" |
| 4156 |
"# </computeroutput><userinput>sed -i -e \"s,gpgkey=file:///etc/,gpgkey=file://${rootdir}/etc/,g\" $rootdir/etc/yum.repos.d/*.repo\n" |
| 4157 |
"</userinput><computeroutput># </computeroutput><userinput>yum --assumeyes --installroot $rootdir groupinstall core\n" |
| 4158 |
"</userinput><computeroutput>[...]\n" |
| 4159 |
"# </computeroutput><userinput>sed -i -e \"s,gpgkey=file://${rootdir}/etc/,gpgkey=file:///etc/,g\" $rootdir/etc/yum.repos.d/*.repo\n" |
| 4160 |
"</userinput>" |
| 4161 |
|
| 4162 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4163 |
msgid "Automated Installation" |
| 4164 |
msgstr "自動インストール" |
| 4165 |
|
| 4166 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4167 |
msgid "<primary>deployment</primary>" |
| 4168 |
msgstr "<primary sortas=\"ハイビ\">配備</primary>" |
| 4169 |
|
| 4170 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4171 |
msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4172 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4173 |
|
| 4174 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4175 |
msgid "The Falcot Corp administrators, like many administrators of large IT services, need tools to install (or reinstall) quickly, and automatically if possible, their new machines." |
| 4176 |
msgstr "巨大な IT サービスの管理者と同様に Falcot Corp の管理者もまた、新しいマシンへシステムを素早く (可能であれば自動的に) インストール (または再インストール) するツールを必要としています。" |
| 4177 |
|
| 4178 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4179 |
msgid "These requirements can be met by a wide range of solutions. On the one hand, generic tools such as SystemImager handle this by creating an image based on a template machine, then deploy that image to the target systems; at the other end of the spectrum, the standard Debian installer can be preseeded with a configuration file giving the answers to the questions asked during the installation process. As a sort of middle ground, a hybrid tool such as FAI (<emphasis>Fully Automatic Installer</emphasis>) installs machines using the packaging system, but it also uses its own infrastructure for tasks that are more specific to massive deployments (such as starting, partitioning, configuration and so on)." |
| 4180 |
msgstr "自動インストールの要求に応えるためのさまざまな解決策が存在します。一方では、SystemImager などの一般的なツールが存在します。こちらの解決策ではテンプレートマシンに基づくイメージを事前に準備し、そのイメージを目標のシステムで展開します。他方では、標準的な Debian インストーラが存在します。こちらの解決策ではインストール作業中に尋ねられる質問の回答を含めた設定ファイルを事前に準備し、この設定ファイルに基づいて目標のシステムを設定します。両者の折衷案として、FAI (<emphasis>Fully Automatic Installer</emphasis>) などのハイブリッドツールが存在します。こちらの解決策ではパッケージングシステムでシステムをインストールし、自分自身の機能を使って大規模な配備に特有のタスク (起動、パーティショニング、設定など) をこなします。" |
| 4181 |
|
| 4182 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4183 |
#, fuzzy |
| 4184 |
#| msgid "Each of these solutions has its pros and cons: SystemImager works independently from any particular packaging system, which allows it to manage large sets of machines using several distinct Linux distributions. It also includes an update system that doesn't require a reinstallation, but this update system can only be reliable if the machines are not modified independently; in other words, the user must not update any software on their own, or install any other software. Similarly, security updates must not be automated, because they have to go through the centralized reference image maintained by SystemImager. This solution also requires the target machines to be homogeneous, otherwise many different images would have to be kept and managed (an i386 image won't fit on a powerpc machine, and so on)." |
| 4185 |
msgid "Each of these solutions has its pros and cons: SystemImager works independently from any particular packaging system, which allows it to manage large sets of machines using several distinct Linux distributions. It also includes an update system that doesn't require a reinstallation, but this update system can only be reliable if the machines are not modified independently; in other words, the user must not update any software on their own, or install any other software. Similarly, security updates must not be automated, because they have to go through the centralized reference image maintained by SystemImager. This solution also requires the target machines to be homogeneous, otherwise many different images would have to be kept and managed (an amd64 image won't fit on a powerpc machine, and so on)." |
| 4186 |
msgstr "これらの解決策には、利点と欠点があります。たとえば SystemImager は特定のパッケージングシステムに依存しません。このことにより、複数の Linux ディストリビューションを使う数多くのマシン群を管理することが可能です。SystemImager には再インストール不要の更新システムが含まれていますが、この更新システムを信頼できるのは各マシンは個別に変更されないという仮定が満足される場合だけです。さらに言い換えれば、ユーザは自分のマシンにインストールされたソフトウェアを更新してはいけませんし、他のソフトウェアをインストールしてもいけません。同様に、セキュリティ更新も自動的に行ってはいけません。なぜなら、セキュリティ更新は SystemImager がメンテナンスする中央集権化された基準イメージによって提供されるからです。また SystemImager による解決策では、管理される側のマシンの種類が同じである必要があります。異種マシンを管理する場合、多くの異なるイメージをメンテナンスおよび管理する必要があります (i386 用のイメージを powerpc マシンに使うことはできません)。" |
| 4187 |
|
| 4188 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4189 |
#, fuzzy |
| 4190 |
#| msgid "On the other hand, an automated installation using debian-installer can adapt to the specifics of each machine: the installer will fetch the appropriate kernel and software packages from the relevant repositories, detect available hardware, partition the whole hard disk to take advantage of all the available space, install the corresponding Debian system, and set up an appropriate bootloader. However, the standard installer will only install standard Debian versions, with the base system and a set of pre-selected “tasks”; this precludes installing a particular system with non-packaged applications. Fulfilling this particular need requires customizing the installer… Fortunately, the installer is very modular, and there are tools to automate most of the work required for this customization, most importantly simple-CDD (CDD being an acronym for <emphasis>Custom Debian Derivative</emphasis>). Even the simple-CDD solution, however, only handles initial installations; this is usually not a problem since the APT tools allow efficient deployment of updates later on." |
| 4191 |
msgid "On the other hand, an automated installation using debian-installer can adapt to the specifics of each machine: the installer will fetch the appropriate kernel and software packages from the relevant repositories, detect available hardware, partition the whole hard disk to take advantage of all the available space, install the corresponding Debian system, and set up an appropriate bootloader. However, the standard installer will only install standard Debian versions, with the base system and a set of pre-selected “tasks”; this precludes installing a particular system with non-packaged applications. Fulfilling this particular need requires customizing the installer… Fortunately, the installer is very modular, and there are tools to automate most of the work required for this customization, most importantly <emphasis role=\"pkg\">simple-cdd</emphasis> (CDD being an acronym for <emphasis>Custom Debian Derivative</emphasis>). Even this solution, however, only handles initial installations; this is usually not a problem since the APT tools allow efficient deployment of updates later on." |
| 4192 |
msgstr "逆に、debian-installer を使ってインストールを自動化する場合、マシンごとの違いに適合したシステムをインストールすることが可能です。具体的に言えば、インストーラは対応するリポジトリから適切なカーネルとソフトウェアパッケージを取得し、利用できるハードウェアを検出し、利用できる領域全体を活かしてハードディスク全体をパーティショニングし、対応する Debian システムをインストールし、適切なブートローダを設定します。しかしながら、標準的なインストーラは基本システムと事前に選択された「tasks」を含む標準的な Debian バージョンをインストールするだけです。さらに、パッケージングされていないアプリケーションを備えた特製のシステムをインストールできません。この特別な必要性を満足させるにはインストーラのカスタマイズが必要です。幸いなことに、インストーラはとてもモジュール化されており、カスタマイズに必要なほとんどの作業を自動化するツールが存在します。最も重要なツールは simple-CDD です (CDD は <emphasis>Custom Debian Derivative</emphasis> の頭字語です)。しかしながら simple-CDD が取り扱うことが可能なのは最初のインストールだけです。しかしこれは通常問題になりません。なぜなら、APT ツールのおかげでインストール後の更新作業は効果的に行うことが可能だからです。" |
| 4193 |
|
| 4194 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4195 |
#, fuzzy |
| 4196 |
#| msgid "We will only give a rough overview of FAI, and skip SystemImager altogether (which is no longer in Debian), in order to focus more intently on debian-installer and simple-CDD, which are more interesting in a Debian-only context." |
| 4197 |
msgid "We will only give a rough overview of FAI, and skip SystemImager altogether (which is no longer in Debian, but available as a third-party package), in order to focus more intently on debian-installer and <emphasis role=\"pkg\">simple-cdd</emphasis>, which are more interesting in a Debian-only context." |
| 4198 |
msgstr "ここでは FAI については大ざっぱな概要を説明し、(もはや Debian に含まれない) SystemImager については完全に省略し、Debian だけのシステムではより興味深い debian-installer と simple-CDD に特に注目します。" |
| 4199 |
|
| 4200 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4201 |
msgid "Fully Automatic Installer (FAI)" |
| 4202 |
msgstr "Fully Automatic Installer (FAI)" |
| 4203 |
|
| 4204 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4205 |
#, fuzzy |
| 4206 |
#| msgid "<primary>Fully Automatic Installer (FAI)</primary>" |
| 4207 |
msgid "<primary>Fully Automatic Installer</primary><see>FAI</see>" |
| 4208 |
msgstr "<primary>Fully Automatic Installer (FAI)</primary>" |
| 4209 |
|
| 4210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4211 |
#, fuzzy |
| 4212 |
#| msgid "<primary>RAID</primary>" |
| 4213 |
msgid "<primary>FAI</primary>" |
| 4214 |
msgstr "<primary>RAID</primary>" |
| 4215 |
|
| 4216 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4217 |
msgid "<foreignphrase>Fully Automatic Installer</foreignphrase> is probably the oldest automated deployment system for Debian, which explains its status as a reference; but its very flexible nature only just compensates for the complexity it involves." |
| 4218 |
msgstr "<foreignphrase>Fully Automatic Installer</foreignphrase> はおそらく最も古い Debian 用の自動配備システムで、基準としての地位を確立しています。しかしその一方で FAI の高い柔軟性は FAI の複雑性によって成し遂げられています。" |
| 4219 |
|
| 4220 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4221 |
#, fuzzy |
| 4222 |
#| msgid "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 4223 |
msgid "<primary>FAI</primary><secondary><emphasis role=\"pkg\">fai-server</emphasis></secondary>" |
| 4224 |
msgstr "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 4225 |
|
| 4226 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4227 |
#, fuzzy |
| 4228 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 4229 |
msgid "<primary>FAI</primary><secondary><emphasis role=\"pkg\">fai-quickstart</emphasis></secondary>" |
| 4230 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 4231 |
|
| 4232 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4233 |
# Tag: L-CFMD; |
| 4234 |
msgid "FAI requires a server system to store deployment information and allow target machines to boot from the network. This server requires the <emphasis role=\"pkg\">fai-server</emphasis> package (or <emphasis role=\"pkg\">fai-quickstart</emphasis>, which also brings the required elements for a standard configuration)." |
| 4235 |
msgstr "FAI には、配備情報を保存してネットワークから目標のマシンを起動することを可能にするために、サーバシステムが必要です。サーバシステムには、<emphasis role=\"pkg\">fai-server</emphasis> パッケージ (または <emphasis role=\"pkg\">fai-quickstart</emphasis>、これには、標準的な設定に必要な要素が含まれています) が必要です。" |
| 4236 |
|
| 4237 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/fai/</filename></secondary><see>FAI</see>" |
| 4238 |
msgstr "" |
| 4239 |
|
| 4240 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4241 |
#, fuzzy |
| 4242 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4243 |
msgid "<primary>FAI</primary><secondary><filename>/etc/fai/nfsroot.conf</filename></secondary>" |
| 4244 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4245 |
|
| 4246 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4247 |
# Tag: L-CFMD; |
| 4248 |
#, fuzzy |
| 4249 |
#| msgid "FAI uses a specific approach for defining the various installable profiles. Instead of simply duplicating a reference installation, FAI is a full-fledged installer, fully configurable via a set of files and scripts stored on the server; the default location <filename>/srv/fai/config/</filename> is not automatically created, so the administrator needs to create it along with the relevant files. Most of the times, these files will be customized from the example files available in the documentation for the <emphasis role=\"pkg\">fai-doc</emphasis> package, more particularly the <filename>/usr/share/doc/fai-doc/examples/simple/</filename> directory." |
| 4250 |
msgid "FAI uses a specific approach for defining the various installable profiles. Instead of simply duplicating a reference installation, FAI is a full-fledged installer, fully configurable via a set of files and scripts stored on the server; the default location <filename>/srv/fai/config/</filename> according to <filename>/etc/fai/nfsroot.conf</filename> is not automatically created, so the administrator needs to create it along with the relevant files. Most of the times, these files will be customized from the example files available in the documentation for the <emphasis role=\"pkg\">fai-doc</emphasis> package, more particularly the <filename>/usr/share/doc/fai-doc/examples/simple/</filename> directory." |
| 4251 |
msgstr "FAI は特殊なやり方で、インストールできるさまざまなプロファイルを定義します。FAI は基準となるインストール状態を単純に複製するのではありません。FAI は本格的なインストーラで、サーバに保存されているファイルとスクリプトを通じて完全に設定することが可能です。しかし、これらのファイルを保存するデフォルトの場所 <filename>/srv/fai/config/</filename> は自動的に作成されません。このため管理者は対応するファイルと一緒にこれも作成する必要があります。ほとんどの場合、これらのファイルは例ファイルからカスタマイズされます。このファイルは <emphasis role=\"pkg\">fai-doc</emphasis> パッケージの文書の中 (より具体的に言えば <filename>/usr/share/doc/fai-doc/examples/simple/</filename> ディレクトリの中) に含まれています。" |
| 4252 |
|
| 4253 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4254 |
#, fuzzy |
| 4255 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4256 |
msgid "<primary>FAI</primary><secondary><command>fai-setup</command></secondary>" |
| 4257 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4258 |
|
| 4259 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4260 |
#, fuzzy |
| 4261 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4262 |
msgid "<primary>FAI</primary><secondary><command>fai-cd</command></secondary>" |
| 4263 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4264 |
|
| 4265 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4266 |
# Tag: L-CFMD; |
| 4267 |
#, fuzzy |
| 4268 |
#| msgid "Once the profiles are defined, the <command>fai-setup</command> command generates the elements required to start an FAI installation; this mostly means preparing or updating a minimal system (NFS-root) used during installation. An alternative is to generate a dedicated boot CD with <command>fai-cd</command>." |
| 4269 |
msgid "Once the profiles are defined, the <command>fai-setup</command> command generates the elements required to start an FAI installation; this mostly means preparing or updating a minimal system (NFS-root) used during installation. An alternative is to generate a dedicated boot CD with <command>fai-cd</command>." |
| 4270 |
msgstr "プロファイルを定義したら、<command>fai-setup</command> コマンドを使って FAI のインストールを開始するために必要な要素を生成します。そしてこれはインストール中に使われる最小限のシステム (NFS-root) の準備と更新を行うことを意味します。別の方法として、<command>fai-cd</command> を使って専用の CD を生成することも可能です。" |
| 4271 |
|
| 4272 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4273 |
msgid "Creating all these configuration files requires some understanding of the way FAI works. A typical installation process is made of the following steps:" |
| 4274 |
msgstr "これらすべての設定ファイルを作成するには、FAI の動作方法を理解する必要があります。典型的なインストール作業は以下の順番で進みます。" |
| 4275 |
|
| 4276 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4277 |
msgid "fetching a kernel from the network, and booting it;" |
| 4278 |
msgstr "ネットワークからカーネルを取得して起動します。" |
| 4279 |
|
| 4280 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4281 |
msgid "mounting the root filesystem from NFS;" |
| 4282 |
msgstr "NFS でルートファイルシステムをマウントします。" |
| 4283 |
|
| 4284 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4285 |
#, fuzzy |
| 4286 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4287 |
msgid "<primary>FAI</primary><secondary><command>fai</command></secondary>" |
| 4288 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4289 |
|
| 4290 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4291 |
# Tag: L-CFMD; |
| 4292 |
msgid "executing <command>/usr/sbin/fai</command>, which controls the rest of the process (the next steps are therefore initiated by this script);" |
| 4293 |
msgstr "インストール作業を制御する <command>/usr/sbin/fai</command> を実行します (<command>/usr/sbin/fai</command> が以降の各段階を初期化します)。" |
| 4294 |
|
| 4295 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4296 |
msgid "copying the configuration space from the server into <filename>/fai/</filename>;" |
| 4297 |
msgstr "サーバから <filename>/fai/</filename> に設定領域をコピーします。" |
| 4298 |
|
| 4299 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4300 |
# Tag: L-CFMD; |
| 4301 |
msgid "running <command>fai-class</command>. The <filename>/fai/class/[0-9][0-9]*</filename> scripts are executed in turn, and return names of “classes” that apply to the machine being installed; this information will serve as a base for the following steps. This allows for some flexibility in defining the services to be installed and configured." |
| 4302 |
msgstr "<command>fai-class</command> を実行します。<filename>/fai/class/[0-9][0-9]*</filename> スクリプトが順番に実行され、インストールされるマシンに適用する「クラス」の名前が返されます。この情報は以降の各段階の基礎としての機能を果たします。これを使うことで、インストールおよび設定されるサービスを定義する際に幾らかの柔軟性を持たせることが可能です。" |
| 4303 |
|
| 4304 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4305 |
msgid "fetching a number of configuration variables, depending on the relevant classes;" |
| 4306 |
msgstr "対応するクラスに基づき、設定変数を取得します。" |
| 4307 |
|
| 4308 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4309 |
msgid "partitioning the disks and formatting the partitions, based on information provided in <filename>/fai/disk_config/<replaceable>class</replaceable></filename>;" |
| 4310 |
msgstr "<filename>/fai/disk_config/<replaceable>class</replaceable></filename> で定義された情報に基づいて、ディスクのパーティショニングとパーティションのフォーマットを行います。" |
| 4311 |
|
| 4312 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4313 |
msgid "mounting said partitions;" |
| 4314 |
msgstr "指定されたパーティションをマウントします。" |
| 4315 |
|
| 4316 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4317 |
msgid "installing the base system;" |
| 4318 |
msgstr "基本システムをインストールします。" |
| 4319 |
|
| 4320 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4321 |
# Tag: L-CFMD; |
| 4322 |
#, fuzzy |
| 4323 |
#| msgid "<primary><command>debconf</command></primary>" |
| 4324 |
msgid "<primary>FAI</primary><secondary><command>fai-debconf</command></secondary>" |
| 4325 |
msgstr "<primary><command>debconf</command></primary>" |
| 4326 |
|
| 4327 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4328 |
msgid "preseeding the Debconf database with <command>fai-debconf</command>;" |
| 4329 |
msgstr "<command>fai-debconf</command> を使って Debconf データベースを事前配布します。" |
| 4330 |
|
| 4331 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4332 |
msgid "fetching the list of available packages for APT;" |
| 4333 |
msgstr "APT で利用できるパッケージのリストを取得します。" |
| 4334 |
|
| 4335 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4336 |
msgid "installing the packages listed in <filename>/fai/package_config/<replaceable>class</replaceable></filename>;" |
| 4337 |
msgstr "<filename>/fai/package_config/<replaceable>class</replaceable></filename> にリストされたパッケージをインストールします。" |
| 4338 |
|
| 4339 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4340 |
msgid "executing the post-configuration scripts, <filename>/fai/scripts/<replaceable>class</replaceable>/[0-9][0-9]*</filename>;" |
| 4341 |
msgstr "設定後にスクリプト <filename>/fai/scripts/<replaceable>class</replaceable>/[0-9][0-9]*</filename> を実行します。" |
| 4342 |
|
| 4343 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4344 |
msgid "recording the installation logs, unmounting the partitions, and rebooting." |
| 4345 |
msgstr "インストールログを記録し、パーティションをアンマウントし、再起動します。" |
| 4346 |
|
| 4347 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4348 |
msgid "Preseeding Debian-Installer" |
| 4349 |
msgstr "Debian-Installer の事前設定" |
| 4350 |
|
| 4351 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4352 |
# Tag: L-CFMD; |
| 4353 |
msgid "<primary>preseed</primary>" |
| 4354 |
msgstr "<primary>preseed</primary>" |
| 4355 |
|
| 4356 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4357 |
msgid "<primary>preconfiguration</primary>" |
| 4358 |
msgstr "<primary sortas=\"ジゼンセッテイ\">事前設定</primary>" |
| 4359 |
|
| 4360 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4361 |
#, fuzzy |
| 4362 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4363 |
msgid "<primary>installation</primary><secondary>preseeding</secondary>" |
| 4364 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4365 |
|
| 4366 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4367 |
#, fuzzy |
| 4368 |
#| msgid "At the end of the day, the best tool to install Debian systems should logically be the official Debian installer. This is why, right from its inception, debian-installer has been designed for automated use, taking advantage of the infrastructure provided by <emphasis role=\"pkg\">debconf</emphasis>. The latter allows, on the one hand, to reduce the number of questions asked (hidden questions will use the provided default answer), and on the other hand, to provide the default answers separately, so that installation can be non-interactive. This last feature is known as <emphasis>preseeding</emphasis>." |
| 4369 |
msgid "At the end of the day, the best tool to install Debian systems should logically be the official Debian installer. This is why, right from its inception, debian-installer has been designed for automated use, taking advantage of the infrastructure provided by <emphasis role=\"pkg\">debconf</emphasis>. The latter allows, on the one hand, to reduce the number of questions asked (hidden questions will use the provided default answer), and on the other hand, to provide the default answers separately, so that installation can be non-interactive. This last feature is known as <foreignphrase>preseeding</foreignphrase>." |
| 4370 |
msgstr "結局のところ、Debian システムをインストールする最良のツールは必然的に公式の Debian インストーラということになるでしょう。このため、当初から debian-installer は <emphasis role=\"pkg\">debconf</emphasis> の提供するインフラを活用して自動的に使えるように設計されています。<emphasis role=\"pkg\">debconf</emphasis> を使うことで、尋ねられる質問の数を減らしたり (隠された質問に対する回答はデフォルトが使われます)、質問に対する回答を個別に事前設定したりすることが可能です。このことにより、インストールを非対話的に進めることが可能です。質問に対する回答の事前設定機能は <emphasis>preseed</emphasis> として知られています。" |
| 4371 |
|
| 4372 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4373 |
msgid "<emphasis>GOING FURTHER</emphasis> Debconf with a centralized database" |
| 4374 |
msgstr "<emphasis>GOING FURTHER</emphasis> 中央集権型データベースを用いる Debconf" |
| 4375 |
|
| 4376 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4377 |
#, fuzzy |
| 4378 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 4379 |
msgid "<primary><emphasis role=\"pkg\">debconf-doc</emphasis></primary>" |
| 4380 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 4381 |
|
| 4382 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4383 |
# Tag: L-CFMD; |
| 4384 |
msgid "Preseeding allows to provide a set of answers to Debconf questions at installation time, but these answers are static and do not evolve as time passes. Since already-installed machines may need upgrading, and new answers may become required, the <filename>/etc/debconf.conf</filename> configuration file can be set up so that Debconf uses external data sources (such as an LDAP directory server, or a remote file accessed via NFS or Samba). Several external data sources can be defined at the same time, and they complement one another. The local database is still used (for read-write access), but the remote databases are usually restricted to reading. The <citerefentry><refentrytitle>debconf.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page describes all the possibilities in detail (you need the <emphasis role=\"pkg\">debconf-doc</emphasis> package)." |
| 4385 |
msgstr "preseed を使うことで、インストール時に尋ねられる Debconf 質問に対する回答を事前に提供することが可能です。しかし、これらの回答は静的なもので、時間経過に従い変化しません。既にインストールされたマシンは更新が必要かもしれませんし、新しい回答が必要かもしれません。このため <filename>/etc/debconf.conf</filename> 設定ファイルから、Debconf が外部のデータソース (LDAP ディレクトリサーバ、NFS や Samba 経由でアクセスされるリモートファイル) を使うようにセットアップして、お互いに補完し合う複数の外部データソースを同時に定義することが可能です。とは言うものの、ローカルデータベースも使えます (読み書きアクセスできます)。これに対してリモートデータベースは読み込みのみに制限されていることが多いです。<citerefentry><refentrytitle>debconf.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> マニュアルページではすべての可能性が詳細に説明されています (このマニュアルは <emphasis role=\"pkg\">debconf-doc</emphasis> パッケージに含まれます)。" |
| 4386 |
|
| 4387 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4388 |
# Tag: L-CFMD; |
| 4389 |
msgid "<primary><command>debconf</command></primary>" |
| 4390 |
msgstr "<primary><command>debconf</command></primary>" |
| 4391 |
|
| 4392 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4393 |
msgid "Using a Preseed File" |
| 4394 |
msgstr "preseed ファイルの利用" |
| 4395 |
|
| 4396 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4397 |
msgid "There are several places where the installer can get a preseeding file:" |
| 4398 |
msgstr "インストーラが preseed ファイルを取得することが可能な場所にはいくつかあります。" |
| 4399 |
|
| 4400 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4401 |
# Tag: L-CFMD; |
| 4402 |
#, fuzzy |
| 4403 |
#| msgid "<primary>preseed</primary>" |
| 4404 |
msgid "<primary><filename>preseed.cfg</filename></primary>" |
| 4405 |
msgstr "<primary>preseed</primary>" |
| 4406 |
|
| 4407 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4408 |
msgid "in the initrd used to start the machine; in this case, preseeding happens at the very beginning of the installation, and all questions can be avoided. The file just needs to be called <filename>preseed.cfg</filename> and stored in the initrd root." |
| 4409 |
msgstr "マシンを開始するために使われる initrd の中。この場合、インストールの最初から preseed を行い、すべての質問を回避することが可能です。preseed ファイルの名前は必ず <filename>preseed.cfg</filename> にして initrd のルートに保存しなければいけません。" |
| 4410 |
|
| 4411 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4412 |
msgid "on the boot media (CD or USB key); preseeding then happens as soon as the media is mounted, which means right after the questions about language and keyboard layout. The <literal>preseed/file</literal> boot parameter can be used to indicate the location of the preseeding file (for instance, <filename>/cdrom/preseed.cfg</filename> when the installation is done off a CD-ROM, or <filename>/hd-media/preseed.cfg</filename> in the USB-key case)." |
| 4413 |
msgstr "起動メディア (CD や USB メモリ) の中。メディアがマウントされた直後から preseed が始まります。これは言語とキーボードレイアウトに関する質問の直後を意味します。<literal>preseed/file</literal> 起動パラメータを使って preseed ファイルの場所を指定することが可能です (たとえば、インストールが CD-ROM から開始された場合は <filename>/cdrom/preseed.cfg</filename>、USB メモリから開始された場合は <filename>/hd-media/preseed.cfg</filename> などです)。" |
| 4414 |
|
| 4415 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4416 |
#, fuzzy |
| 4417 |
#| msgid "from the network; preseeding then only happens after the network is (automatically) configured; the relevant boot parameter is then <literal>preseed/url=http://<replaceable>server</replaceable>/preseed.cfg</literal>." |
| 4418 |
msgid "from the network; preseeding then only happens after the network is (automatically) configured; the relevant boot parameter is then <literal>preseed/url=http://<replaceable>server</replaceable>/preseed.cfg</literal> (HTTPS, FTPS, SFTP, etc. are not supported)." |
| 4419 |
msgstr "ネットワーク上。ネットワークが (自動的に) 設定された直後から preseed が始まります。対応する起動パラメータは <literal>preseed/url=http://<replaceable>server</replaceable>/preseed.cfg</literal> です。" |
| 4420 |
|
| 4421 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4422 |
msgid "At a glance, including the preseeding file in the initrd looks like the most interesting solution; however, it is rarely used in practice, because generating an installer initrd is rather complex. The other two solutions are much more common, especially since boot parameters provide another way to preseed the answers to the first questions of the installation process. The usual way to save the bother of typing these boot parameters by hand at each installation is to save them into the configuration for <command>isolinux</command> (in the CD-ROM case) or <command>syslinux</command> (USB key)." |
| 4423 |
msgstr "一見すると、preseed ファイルを initrd の中に含めることが最もうまい解決策のように見えます。しかし、実際のところこれはほとんど行われません。なぜなら、インストーラの initrd を生成することはかなり複雑だからです。その他の 2 種類の解決策はよく使われます。なぜなら起動パラメータを使うことで、インストール作業の最初の質問の回答を他のやり方で事前指定することが可能だからです。インストールごとに起動パラメータを手作業で打ち込む手間を省くためによく使われる方法は <command>isolinux</command> (CD-ROM の場合) や <command>syslinux</command> (USB メモリの場合) の設定ファイルに起動パラメータを保存することです。" |
| 4424 |
|
| 4425 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4426 |
msgid "Creating a Preseed File" |
| 4427 |
msgstr "preseed ファイルの作成" |
| 4428 |
|
| 4429 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4430 |
msgid "A preseed file is a plain text file, where each line contains the answer to one Debconf question. A line is split across four fields separated by whitespace (spaces or tabs), as in, for instance, <literal>d-i mirror/suite string stable</literal>:" |
| 4431 |
msgstr "preseed ファイルはプレーンテキストファイルで、各行に 1 つの Debconf 質問に対する回答が含まれます。行は空白 (スペースかタブ) で区切られた 4 種類のフィールドに分割されます。たとえば <literal>d-i mirror/suite string stable</literal> のようになります。" |
| 4432 |
|
| 4433 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4434 |
msgid "the first field is the “owner” of the question; “d-i” is used for questions relevant to the installer, but it can also be a package name for questions coming from Debian packages;" |
| 4435 |
msgstr "最初のフィールドはこの質問の「所有者」です。インストーラに関する質問の場合「d-i」を使い、Debian パッケージからの質問の場合パッケージ名を使います。" |
| 4436 |
|
| 4437 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4438 |
#, fuzzy |
| 4439 |
#| msgid "the second field is an identifier for the question;" |
| 4440 |
msgid "the second field is an identifier for the question (the template name);" |
| 4441 |
msgstr "2 番目のフィールドは質問の識別子です。" |
| 4442 |
|
| 4443 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4444 |
msgid "third, the type of question;" |
| 4445 |
msgstr "3 番目のフィールドは質問の種類です。" |
| 4446 |
|
| 4447 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4448 |
msgid "the fourth and last field contains the value for the answer. Note that it must be separated from the third field with a single space; if there are more than one, the following space characters are considered part of the value." |
| 4449 |
msgstr "4 番目以降のフィールドは質問に対する回答です。3 番目のフィールドの後ろに必ず 1 つの空白を含めなければいけない点に注意してください。さらに 1 つ以上の回答がある場合、続く空白文字は回答の一部として取り扱われます。" |
| 4450 |
|
| 4451 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4452 |
msgid "The simplest way to write a preseed file is to install a system by hand. Then <command>debconf-get-selections --installer</command> will provide the answers concerning the installer. Answers about other packages can be obtained with <command>debconf-get-selections</command>. However, a cleaner solution is to write the preseed file by hand, starting from an example and the reference documentation: with such an approach, only questions where the default answer needs to be overridden can be preseeded; using the <literal>priority=critical</literal> boot parameter will instruct Debconf to only ask critical questions, and use the default answer for others." |
| 4453 |
msgstr "preseed ファイルを書く最も簡単な方法はシステムを手作業でインストールする方法です。インストール完了後に <command>debconf-get-selections --installer</command> を実行してインストーラに関連する回答を取得します。<command>debconf-get-selections</command> を使えば、他のパッケージに関連する回答を取得することが可能です。しかしながら、最も明確な解決策は記載例と基準文書を参考にしながら手作業で preseed ファイルを書くことです。なぜなら、このような取り扱い方をすることで、デフォルト回答に対して上書きが必要な質問だけに回答を事前指定することが可能だからです。さらに <literal>priority=critical</literal> 起動パラメータ使うことで、Debconf が重要な質問だけを尋ね、他の質問にはデフォルトの回答を使うようにすることが可能です。" |
| 4454 |
|
| 4455 |
msgid "Pre-setting a value in a preseed file automatically instructs the Debian installer to not ask that question. This happens, because loading the preseed file does not just set the given value(s), but also marks each of the affected dialogs as “seen“ by the user. Thus it is possible to pre-set a question's value and still present the dialog to the user by resetting the “seen“ flag. Beware that order in this case matters and that the value has to be preseeded before setting the dialog to “unseen“ as shown in the following example:" |
| 4456 |
msgstr "" |
| 4457 |
|
| 4458 |
msgid "" |
| 4459 |
"d-i netcfg/hostname string worker\n" |
| 4460 |
"d-i netcfg/hostname seen false" |
| 4461 |
msgstr "" |
| 4462 |
|
| 4463 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4464 |
# Tag: L-CFMD; |
| 4465 |
#, fuzzy |
| 4466 |
#| msgid "<primary><command>debconf</command></primary>" |
| 4467 |
msgid "<primary><command>debconf-get-selections</command></primary>" |
| 4468 |
msgstr "<primary><command>debconf</command></primary>" |
| 4469 |
|
| 4470 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4471 |
msgid "<emphasis>DOCUMENTATION</emphasis> Installation guide appendix" |
| 4472 |
msgstr "<emphasis>DOCUMENTATION</emphasis> インストールガイドの付録" |
| 4473 |
|
| 4474 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4475 |
#, fuzzy |
| 4476 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4477 |
msgid "<primary>preseed</primary><secondary>all templates</secondary>" |
| 4478 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4479 |
|
| 4480 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4481 |
#, fuzzy |
| 4482 |
#| msgid "The installation guide, available online, includes detailed documentation on the use of a preseed file in an appendix. It also includes a detailed and commented sample file, which can serve as a base for local customizations. <ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/amd64/apb.html\" /> <ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/example-preseed.txt\" />" |
| 4483 |
msgid "The installation guide, available online, includes detailed documentation on the use of a preseed file in an appendix. It also includes a detailed and commented sample file, which can serve as a base for local customizations. There are also collections of all debconf templates extracted from each component and suite of Debian: <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/amd64/apb\" /> <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/example-preseed.txt\" /> <ulink type=\"block\" url=\"https://preseed.debian.net/\" />" |
| 4484 |
msgstr "オンライン上で利用できるインストールガイドの付録には、preseed ファイルの使い方に関する詳細な文書が含まれます。また、コメントの形で詳細を説明された見本ファイルが含まれます。これは自分用カスタマイズのひな形として使えるように用意されています。<ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/amd64/apb.html\" /><ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/example-preseed.txt\" />" |
| 4485 |
|
| 4486 |
msgid "Preseeding an installation is often not as straightforward as one would wish. It sometimes requires to understand how packages process the given values in their scripts. Don't hesitate to ask on the <email>[email protected]</email> mailing list or in the <literal>#debian-cd</literal> IRC channel if you require help. Also be aware that some complex setups still cannot be achieved by preseeding." |
| 4487 |
msgstr "" |
| 4488 |
|
| 4489 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4490 |
#, fuzzy |
| 4491 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4492 |
msgid "<primary>mailing lists</primary><secondary><email>[email protected]</email></secondary>" |
| 4493 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4494 |
|
| 4495 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4496 |
msgid "Creating a Customized Boot Media" |
| 4497 |
msgstr "カスタマイズされた起動メディアの作成" |
| 4498 |
|
| 4499 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4500 |
msgid "Knowing where to store the preseed file is all very well, but the location isn't everything: one must, one way or another, alter the installation boot media to change the boot parameters and add the preseed file." |
| 4501 |
msgstr "preseed ファイルを保存する場所を知ることは誠に結構なことですが、場所がすべてではありません。なぜなら、起動パラメータを変更し preseed ファイルを追加するためには、いずれにせよインストール用の起動メディアを改造しなければいけないからです。" |
| 4502 |
|
| 4503 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4504 |
msgid "Booting From the Network" |
| 4505 |
msgstr "ネットワークからの起動" |
| 4506 |
|
| 4507 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4508 |
#, fuzzy |
| 4509 |
#| msgid "<primary>LXC</primary>" |
| 4510 |
msgid "<primary>PXE</primary>" |
| 4511 |
msgstr "<primary>LXC</primary>" |
| 4512 |
|
| 4513 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4514 |
#, fuzzy |
| 4515 |
#| msgid "When a computer is booted from the network, the server sending the initialization elements also defines the boot parameters. Thus, the change needs to be made in the PXE configuration for the boot server; more specifically, in its <filename>/tftpboot/pxelinux.cfg/default</filename> configuration file. Setting up network boot is a prerequisite; see the Installation Guide for details. <ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/amd64/ch04s05.html\" />" |
| 4516 |
msgid "When a computer is booted from the network, the server sending the initialization elements also defines the boot parameters. Thus, the change needs to be made in the PXE configuration for the boot server; more specifically, in its <filename>/tftpboot/pxelinux.cfg/default</filename> configuration file. Setting up network boot is a prerequisite; see the Installation Guide for details. <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/amd64/ch04s05\" />" |
| 4517 |
msgstr "コンピュータをネットワークから起動する場合、初期化要素を送信するサーバを使って起動パラメータを定義することも可能です。この場合、初期化要素の定義は起動サーバの PXE 設定の中で行う必要があります。より具体的に言えば <filename>/tftpboot/pxelinux.cfg/default</filename> 設定ファイルの中で設定します。そして、事前にネットワーク起動をセットアップすることが必要です。詳しくはインストールガイドをご覧ください。<ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/amd64/ch04s05.html\" />" |
| 4518 |
|
| 4519 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4520 |
msgid "Preparing a Bootable USB Key" |
| 4521 |
msgstr "起動可能な USB メモリの準備" |
| 4522 |
|
| 4523 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4524 |
#, fuzzy |
| 4525 |
#| msgid "<primary><emphasis>VirtualBox</emphasis></primary>" |
| 4526 |
msgid "<primary><filename>syslinux.cfg</filename></primary>" |
| 4527 |
msgstr "<primary><emphasis>VirtualBox</emphasis></primary>" |
| 4528 |
|
| 4529 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4530 |
#, fuzzy |
| 4531 |
#| msgid "<primary>Munin</primary>" |
| 4532 |
msgid "<primary>syslinux</primary>" |
| 4533 |
msgstr "<primary>Munin</primary>" |
| 4534 |
|
| 4535 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4536 |
#, fuzzy |
| 4537 |
#| msgid "<primary>Munin</primary>" |
| 4538 |
msgid "<primary>isolinux</primary>" |
| 4539 |
msgstr "<primary>Munin</primary>" |
| 4540 |
|
| 4541 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4542 |
#, fuzzy |
| 4543 |
#| msgid "<primary>Icinga</primary>" |
| 4544 |
msgid "<primary><filename>grub.cfg</filename></primary>" |
| 4545 |
msgstr "<primary>Icinga</primary>" |
| 4546 |
|
| 4547 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4548 |
#, fuzzy |
| 4549 |
#| msgid "Once a bootable key has been prepared (see <xref linkend=\"sect.install-usb\" />), a few extra operations are needed. Assuming the key contents are available under <filename>/media/usbdisk/</filename>:" |
| 4550 |
msgid "Once a bootable key has been prepared (see <xref linkend=\"sect.install-usb\" />), a few extra operations are needed. Assuming the key contents are available under <filename>/media/usbdisk/</filename>, copy the preseed file to <filename>/media/usbdisk/preseed.cfg</filename>." |
| 4551 |
msgstr "起動可能な USB メモリを用意した場合 (<xref linkend=\"sect.install-usb\" />を参照してください)、以下に挙げるいくつかの追加的な操作が必要です。USB メモリの内容は <filename>/media/usbdisk/</filename> で利用できるとします。" |
| 4552 |
|
| 4553 |
msgid "If you have been using a hybrid ISO image to create the bootable USB stick, then you have to edit <filename>/media/usbdisk/boot/grub/grub.cfg</filename> (for the EFI boot screen):" |
| 4554 |
msgstr "" |
| 4555 |
|
| 4556 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4557 |
#, fuzzy |
| 4558 |
#| msgid "syslinux.cfg file and preseeding parameters" |
| 4559 |
msgid "boot/grub/grub.cfg file and preseeding parameters" |
| 4560 |
msgstr "syslinux.cfg ファイルと preseed パラメータ" |
| 4561 |
|
| 4562 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4563 |
#, fuzzy |
| 4564 |
#| msgid "" |
| 4565 |
#| "default vmlinuz\n" |
| 4566 |
#| "append preseed/file=/hd-media/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=initrd.gz --" |
| 4567 |
msgid "" |
| 4568 |
"menuentry --hotkey=i 'Install' {\n" |
| 4569 |
" set background_color=black\n" |
| 4570 |
" linux /install.amd/vmlinuz preseed/file=/cdrom/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 --- quiet \n" |
| 4571 |
" initrd /install.amd/initrd.gz\n" |
| 4572 |
"}" |
| 4573 |
msgstr "" |
| 4574 |
"default vmlinuz\n" |
| 4575 |
"append preseed/file=/hd-media/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=initrd.gz --" |
| 4576 |
|
| 4577 |
msgid "And you have to edit <filename>/media/usbdisk/isolinux/isolinux.cfg</filename> (for BIOS boot) or one of the files it utilizes - e.g. <filename>/media/usbdisk/isolinux/txt.cfg</filename> - to add required boot parameters:" |
| 4578 |
msgstr "" |
| 4579 |
|
| 4580 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4581 |
#, fuzzy |
| 4582 |
#| msgid "syslinux.cfg file and preseeding parameters" |
| 4583 |
msgid "isolinux/txt.cfg file and preseeding parameters" |
| 4584 |
msgstr "syslinux.cfg ファイルと preseed パラメータ" |
| 4585 |
|
| 4586 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4587 |
#, fuzzy |
| 4588 |
#| msgid "" |
| 4589 |
#| "default vmlinuz\n" |
| 4590 |
#| "append preseed/file=/hd-media/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=initrd.gz --" |
| 4591 |
msgid "" |
| 4592 |
"label install\n" |
| 4593 |
" menu label ^Install\n" |
| 4594 |
" kernel [...]\n" |
| 4595 |
" append preseed/file=/cdrom/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=/install.amd/initrd.gz --- quiet" |
| 4596 |
msgstr "" |
| 4597 |
"default vmlinuz\n" |
| 4598 |
"append preseed/file=/hd-media/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=initrd.gz --" |
| 4599 |
|
| 4600 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4601 |
#, fuzzy |
| 4602 |
#| msgid "edit <filename>/media/usbdisk/syslinux.cfg</filename> and add required boot parameters (see example below)." |
| 4603 |
msgid "If you have been using the <filename>hd-media</filename> installer image for a custom USB stick, edit <filename>/media/usbdisk/syslinux.cfg</filename> and add the required boot parameters as shown in the example below:" |
| 4604 |
msgstr "<filename>/media/usbdisk/syslinux.cfg</filename> を編集して、必要な起動パラメータを追加します (以下の例をご覧ください)。" |
| 4605 |
|
| 4606 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4607 |
msgid "syslinux.cfg file and preseeding parameters" |
| 4608 |
msgstr "syslinux.cfg ファイルと preseed パラメータ" |
| 4609 |
|
| 4610 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4611 |
msgid "" |
| 4612 |
"default vmlinuz\n" |
| 4613 |
"append preseed/file=/hd-media/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=initrd.gz --" |
| 4614 |
msgstr "" |
| 4615 |
"default vmlinuz\n" |
| 4616 |
"append preseed/file=/hd-media/preseed.cfg locale=en_US.UTF-8 keymap=us language=us country=US vga=788 initrd=initrd.gz --" |
| 4617 |
|
| 4618 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4619 |
msgid "Creating a CD-ROM Image" |
| 4620 |
msgstr "CD-ROM イメージの作成" |
| 4621 |
|
| 4622 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4623 |
#, fuzzy |
| 4624 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 4625 |
msgid "<primary><emphasis role=\"pkg\">debian-cd</emphasis></primary>" |
| 4626 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 4627 |
|
| 4628 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4629 |
#, fuzzy |
| 4630 |
#| msgid "<primary><command>xe</command></primary>" |
| 4631 |
msgid "<primary><command>genisoimage</command></primary>" |
| 4632 |
msgstr "<primary><command>xe</command></primary>" |
| 4633 |
|
| 4634 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4635 |
#, fuzzy |
| 4636 |
#| msgid "<primary><command>xm</command></primary>" |
| 4637 |
msgid "<primary><command>mkisofs</command></primary>" |
| 4638 |
msgstr "<primary><command>xm</command></primary>" |
| 4639 |
|
| 4640 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4641 |
#, fuzzy |
| 4642 |
#| msgid "<primary><command>xm</command></primary>" |
| 4643 |
msgid "<primary><command>xorriso</command></primary>" |
| 4644 |
msgstr "<primary><command>xm</command></primary>" |
| 4645 |
|
| 4646 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4647 |
msgid "A USB key is a read-write media, so it was easy for us to add a file there and change a few parameters. In the CD-ROM case, the operation is more complex, since we need to regenerate a full ISO image. This task is handled by <emphasis role=\"pkg\">debian-cd</emphasis>, but this tool is rather awkward to use: it needs a local mirror, and it requires an understanding of all the options provided by <filename>/usr/share/debian-cd/CONF.sh</filename>; even then, <command>make</command> must be invoked several times. <filename>/usr/share/debian-cd/README</filename> is therefore a very recommended read." |
| 4648 |
msgstr "USB メモリは読み書きメディアなので、ファイルを追加したりいくつかのパラメータを変更することが簡単に可能です。CD-ROM の場合、この操作はさらに複雑になります。なぜなら、完全な ISO イメージを再生成する必要があるからです。<emphasis role=\"pkg\">debian-cd</emphasis> がこの作業を担当しますが、<emphasis role=\"pkg\">debian-cd</emphasis> ツールは少し使いにくいです。すなわち、<emphasis role=\"pkg\">debian-cd</emphasis> ツールを使うには、ローカルミラーと <filename>/usr/share/debian-cd/CONF.sh</filename> によって提供されるすべてのオプションについて理解する必要があります。そしてさらに、<command>make</command> を複数回実行する必要があります。このため、<filename>/usr/share/debian-cd/README</filename> を一読することを強く推奨します。" |
| 4649 |
|
| 4650 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4651 |
#, fuzzy |
| 4652 |
#| msgid "Having said that, debian-cd always operates in a similar way: an “image” directory with the exact contents of the CD-ROM is generated, then converted to an ISO file with a tool such as <command>genisoimage</command>, <command>mkisofs</command> or <command>xorriso</command>. The image directory is finalized after debian-cd's <command>make image-trees</command> step. At that point, we insert the preseed file into the appropriate directory (usually <filename>$TDIR/$CODENAME/CD1/</filename>, $TDIR and $CODENAME being parameters defined by the <filename>CONF.sh</filename> configuration file). The CD-ROM uses <command>isolinux</command> as its bootloader, and its configuration file must be adapted from what debian-cd generated, in order to insert the required boot parameters (the specific file is <filename>$TDIR/$CODENAME/boot1/isolinux/isolinux.cfg</filename>). Then the “normal” process can be resumed, and we can go on to generating the ISO image with <command>make image CD=1</command> (or <command>make images</command> if several CD-ROMs are generated)." |
| 4653 |
msgid "Having said that, <emphasis role=\"pkg\">debian-cd</emphasis> always operates in a similar way: an “image” directory with the exact contents of the CD-ROM is generated, then converted to an ISO file with a tool such as <command>genisoimage</command>, <command>mkisofs</command> or <command>xorriso</command>. The image directory is finalized after debian-cd's <command>make image-trees</command> step. At that point, we insert the preseed file into the appropriate directory (usually <filename>$TDIR/$CODENAME/CD1/</filename>, $TDIR and $CODENAME being parameters defined by the <filename>CONF.sh</filename> configuration file). The CD-ROM uses <command>isolinux</command> as its bootloader, and its configuration file must be adapted from what debian-cd generated, in order to insert the required boot parameters (the specific files are <filename>$TDIR/$CODENAME/CD1/isolinux/isolinux.cfg</filename> and <filename>$TDIR/$CODENAME/CD1/boot/grub/grub.cfg</filename> as shown above). Then the “normal” process can be resumed, and we can go on to generating the ISO image with <command>make image CD=1</command> (or <command>make images</command> if several CD-ROMs are generated)." |
| 4654 |
msgstr "そうは言っても、debian-cd の挙動は大きく変わるものではありません。具体的に言えば CD-ROM の内容を展開した「image」ディレクトリが生成され、その後 <command>genisoimage</command>、<command>mkisofs</command>、<command>xorriso</command> などのツールを使って「image」ディレクトリを ISO ファイルに変換します。image ディレクトリは debian-cd の <command>make image-trees</command> 段階の後に仕上げられます。この時点で、preseed ファイルを適切なディレクトリ (通常 <filename>$TDIR/$CODENAME/CD1/</filename> です、ここで $TDIR と $CODENAME は <filename>CONF.sh</filename> 設定ファイルによって定義されるパラメータです) に追加します。CD-ROM は <command>isolinux</command> をブートローダとして使います。必要な起動パラメータを追加するためには、<command>isolinux</command> の設定ファイル (ファイルは <filename>$TDIR/$CODENAME/boot1/isolinux/isolinux.cfg</filename> にあります) を debian-cd が生成した内容に適合させなければいけません。この後、「通常の」プロセスを再開し、<command>make image CD=1</command> (または <command>make images</command> 複数の CD-ROM を生成する場合) を実行して ISO イメージを生成します。" |
| 4655 |
|
| 4656 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4657 |
msgid "Simple-CDD: The All-In-One Solution" |
| 4658 |
msgstr "Simple-CDD、一体型の解決策" |
| 4659 |
|
| 4660 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4661 |
#, fuzzy |
| 4662 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 4663 |
msgid "<primary><emphasis role=\"pkg\">simple-cdd</emphasis></primary>" |
| 4664 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 4665 |
|
| 4666 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4667 |
msgid "Simply using a preseed file is not enough to fulfill all the requirements that may appear for large deployments. Even though it is possible to execute a few scripts at the end of the normal installation process, the selection of the set of packages to install is still not quite flexible (basically, only “tasks” can be selected); more important, this only allows installing official Debian packages, and precludes locally-generated ones." |
| 4668 |
msgstr "単純に preseed ファイルを使うだけでは、大規模な配備に要求されるすべてを満足させることはできません。preseed ファイルを使うことで、通常のインストール作業の最後にいくつかのスクリプトを実行することが可能とは言うものの、インストールするパッケージ群の選択にはまだ大きな制限があります (基本的に「tasks」を選択できるだけです)。それどころかより重要なこととして、preseed ファイルを使えば公式の Debian パッケージをインストールすることが可能ですが、自前で作成したパッケージをインストールすることは不可能です。" |
| 4669 |
|
| 4670 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4671 |
#, fuzzy |
| 4672 |
#| msgid "On the other hand, debian-cd is able to integrate external packages, and debian-installer can be extended by inserting new steps in the installation process. By combining these capabilities, it should be possible to create a customized installer that fulfills our needs; it should even be able to configure some services after unpacking the required packages. Fortunately, this is not a mere hypothesis, since this is exactly what Simple-CDD (in the <emphasis role=\"pkg\">simple-cdd</emphasis> package) does." |
| 4673 |
msgid "On the other hand, debian-cd is able to integrate external packages, and debian-installer can be extended by inserting new steps in the installation process. By combining these capabilities, it should be possible to create a customized installer that fulfills our needs; it should even be able to configure some services after unpacking the required packages. Fortunately, this is not a mere hypothesis, since this is exactly what <emphasis role=\"pkg\">simple-cdd</emphasis> does." |
| 4674 |
msgstr "逆に、debian-cd を使えば外部パッケージを組み込むことが可能で、debian-installer を使えばインストール作業に新しい段階を挿入するように拡張することが可能です。これらの機能を組み合わせることで、自分の要求を完全に満足するカスタマイズされたインストーラを作成することが可能です。さらにこの方針を取ることで、必要なパッケージを展開した後、いくつかのサービスを設定することが可能です。幸いなことに、この方針は単なる仮説というわけではありません。なぜなら、これこそが Simple-CDD (<emphasis role=\"pkg\">simple-cdd</emphasis> パッケージに含まれます) のやっていることだからです。" |
| 4675 |
|
| 4676 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4677 |
#, fuzzy |
| 4678 |
#| msgid "The purpose of Simple-CDD is to allow anyone to easily create a distribution derived from Debian, by selecting a subset of the available packages, preconfiguring them with Debconf, adding specific software, and executing custom scripts at the end of the installation process. This matches the “universal operating system” philosophy, since anyone can adapt it to their own needs." |
| 4679 |
msgid "The purpose of this tool is to allow anyone to easily create a distribution derived from Debian, by selecting a subset of the available packages, preconfiguring them with Debconf, adding specific software, and executing custom scripts at the end of the installation process. This matches the “universal operating system” philosophy, since anyone can adapt it to their own needs." |
| 4680 |
msgstr "Simple-CDD の目的とは、利用できるパッケージの一部を選択したり、Debconf を使ってパッケージを事前設定したり、特定のソフトウェアを追加したり、インストール作業の最後にカスタムスクリプトを実行することで、誰でも簡単に Debian の派生ディストリビューションを作成することです。これは「ユニバーサルオペレーティングシステム」の原理に一致します。なぜなら、このことにより誰でも自分自身の要求にオペレーティングシステムを適合させることが可能だからです。" |
| 4681 |
|
| 4682 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4683 |
msgid "Creating Profiles" |
| 4684 |
msgstr "プロファイルの作成" |
| 4685 |
|
| 4686 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4687 |
msgid "Simple-CDD defines “profiles” that match the FAI “classes” concept, and a machine can have several profiles (determined at installation time). A profile is defined by a set of <filename>profiles/<replaceable>profile</replaceable>.*</filename> files:" |
| 4688 |
msgstr "Simple-CDD は FAI における「クラス」の概念に対応する「プロファイル」を定義し、マシンは (インストール時に定義される) 複数のプロファイルを持つことが可能です。プロファイルは以下に挙げる <filename>profiles/<replaceable>profile</replaceable>.*</filename> ファイルを使って定義されます。" |
| 4689 |
|
| 4690 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4691 |
msgid "the <filename>.description</filename> file contains a one-line description for the profile;" |
| 4692 |
msgstr "<filename>.description</filename> ファイル。プロファイルに関する 1 行の説明が含まれます。" |
| 4693 |
|
| 4694 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4695 |
msgid "the <filename>.packages</filename> file lists packages that will automatically be installed if the profile is selected;" |
| 4696 |
msgstr "<filename>.packages</filename> ファイル。プロファイルが選択された場合に自動的にインストールするパッケージがリストされています。" |
| 4697 |
|
| 4698 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4699 |
msgid "the <filename>.downloads</filename> file lists packages that will be stored onto the installation media, but not necessarily installed;" |
| 4700 |
msgstr "<filename>.downloads</filename> ファイル。インストールメディアに保存するがシステムにインストールしないパッケージがリストされています。" |
| 4701 |
|
| 4702 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4703 |
msgid "the <filename>.preseed</filename> file contains preseeding information for Debconf questions (for the installer and/or for packages);" |
| 4704 |
msgstr "<filename>.preseed</filename> ファイル。(インストーラおよびパッケージの) Debconf 質問に関する preseed 情報が含まれます。" |
| 4705 |
|
| 4706 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4707 |
msgid "the <filename>.postinst</filename> file contains a script that will be run at the end of the installation process;" |
| 4708 |
msgstr "<filename>.postinst</filename> ファイル。インストール作業の最後に実行されるスクリプトが含まれます。" |
| 4709 |
|
| 4710 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4711 |
#, fuzzy |
| 4712 |
#| msgid "lastly, the <filename>.conf</filename> file allows changing some Simple-CDD parameters based on the profiles to be included in an image." |
| 4713 |
msgid "lastly, the <filename>.conf</filename> file allows changing some parameters based on the profiles to be included in an image." |
| 4714 |
msgstr "<filename>.conf</filename> ファイル。イメージに保存されるプロファイルに基づいていくつかの Simple-CDD パラメータを修正することが可能です。" |
| 4715 |
|
| 4716 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4717 |
msgid "The <literal>default</literal> profile has a particular role, since it is always selected; it contains the bare minimum required for Simple-CDD to work. The only thing that is usually customized in this profile is the <literal>simple-cdd/profiles</literal> preseed parameter: this allows avoiding the question, introduced by Simple-CDD, about what profiles to install." |
| 4718 |
msgstr "<literal>default</literal> プロファイルは特別な役割を担います。なぜなら <literal>default</literal> プロファイルは常に選択されるからです。そして <literal>default</literal> プロファイルには、Simple-CDD を動作させるために最低限必要な要素が含まれています。通常 <literal>default</literal> プロファイルの中でカスタマイズが必要なのは <literal>simple-cdd/profiles</literal> preseed パラメータだけです。なぜなら、これを使うことで Simple-CDD によって追加されたインストールするプロファイルの選択に関する質問を避けることが可能だからです。" |
| 4719 |
|
| 4720 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4721 |
# Tag: PTAL; |
| 4722 |
msgid "Note also that the commands will need to be invoked from the parent directory of the <filename>profiles</filename> directory." |
| 4723 |
msgstr "コマンドは <filename>profiles</filename> ディレクトリの親ディレクトリから実行する必要がある点に注意してください。" |
| 4724 |
|
| 4725 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4726 |
msgid "Configuring and Using <command>build-simple-cdd</command>" |
| 4727 |
msgstr "<command>build-simple-cdd</command> の設定と利用" |
| 4728 |
|
| 4729 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4730 |
msgid "<primary><command>build-simple-cdd</command></primary>" |
| 4731 |
msgstr "<primary><command>build-simple-cdd</command></primary>" |
| 4732 |
|
| 4733 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4734 |
msgid "<emphasis>QUICK LOOK</emphasis> Detailed configuration file" |
| 4735 |
msgstr "<emphasis>QUICK LOOK</emphasis> 詳細説明を含む設定ファイル" |
| 4736 |
|
| 4737 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4738 |
#, fuzzy |
| 4739 |
#| msgid "An example of a Simple-CDD configuration file, with all possible parameters, is included in the package (<filename>/usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz</filename>). This can be used as a starting point when creating a custom configuration file." |
| 4740 |
msgid "An example of a Simple-CDD configuration file, with most possible parameters, is included in the package (<filename>/usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed</filename>). This can be used as a starting point when creating a custom configuration file. Unfortunately not everything is documented there, so some variables are only listed and explained in <filename>/usr/lib/python3/dist-packages/simple_cdd/variables.py</filename>." |
| 4741 |
msgstr "すべての利用できるパラメータを含む Simple-CDD 設定ファイルの例 (<filename>/usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz</filename>) がパッケージに含まれています。カスタム設定ファイルを作成する際に、この例を足掛かりとして使うことが可能です。" |
| 4742 |
|
| 4743 |
msgid "It is further important to familiarize yourself with the variables understood by <filename>/usr/share/debian-cd/CONF.sh</filename>." |
| 4744 |
msgstr "" |
| 4745 |
|
| 4746 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4747 |
# Tag: L-CFMD; |
| 4748 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4749 |
# Ref: $ man 1 simple-cdd; |
| 4750 |
msgid "Simple-CDD requires many parameters to operate fully. They will most often be gathered in a configuration file, which <command>build-simple-cdd</command> can be pointed at with the <literal>--conf</literal> option, but they can also be specified via dedicated parameters given to <command>build-simple-cdd</command>. Here is an overview of how this command behaves, and how its parameters are used:" |
| 4751 |
msgstr "Simple-CDD を完全に動作させるには多くのパラメータが必要です。通常、パラメータは設定ファイルの中にまとめられ、この設定ファイルを <command>build-simple-cdd</command> の <literal>--conf</literal> オプションに指定します。しかし、パラメータは専用パラメータを <command>build-simple-cdd</command> に渡すことでも指定することも可能です。以下では、パラメータの使い方と <command>build-simple-cdd</command> の挙動を大ざっぱに説明しています。" |
| 4752 |
|
| 4753 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4754 |
# Tag: L-CFMD; |
| 4755 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4756 |
msgid "the <literal>profiles</literal> parameter lists the profiles that will be included on the generated CD-ROM image;" |
| 4757 |
msgstr "<literal>profiles</literal> パラメータは生成する CD-ROM イメージに含めるプロファイルをリストします。" |
| 4758 |
|
| 4759 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4760 |
# Tag: L-CFMD; |
| 4761 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4762 |
msgid "based on the list of required packages, Simple-CDD downloads the appropriate files from the server mentioned in <literal>server</literal>, and gathers them into a partial mirror (which will later be given to debian-cd);" |
| 4763 |
msgstr "Simple-CDD は要求されるパッケージのリストに基づいて、<literal>server</literal> で指定されているサーバから適切なファイルをダウンロードし、(後に debian-cd に渡される) ローカルミラーにまとめます。" |
| 4764 |
|
| 4765 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4766 |
# Tag: L-CFMD; |
| 4767 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4768 |
msgid "the custom packages mentioned in <literal>local_packages</literal> are also integrated into this local mirror;" |
| 4769 |
msgstr "また <literal>local_packages</literal> で指定されたカスタムパッケージがこのローカルミラーの中に統合されます。" |
| 4770 |
|
| 4771 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4772 |
# Tag: L-CFMD; |
| 4773 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4774 |
msgid "debian-cd is then executed (within a default location that can be configured with the <literal>debian_cd_dir</literal> variable), with the list of packages to integrate;" |
| 4775 |
msgstr "この後、組み込むパッケージのリストを使って debian-cd が実行されます (実行場所は <literal>debian_cd_dir</literal> 変数を使って設定されたデフォルト位置です)。" |
| 4776 |
|
| 4777 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4778 |
# Tag: L-CFMD; |
| 4779 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4780 |
msgid "once debian-cd has prepared its directory, Simple-CDD applies some changes to this directory:" |
| 4781 |
msgstr "debian-cd が <literal>debian_cd_dir</literal> で指定したディレクトリを用意した後、Simple-CDD はいくつかの変更をこのディレクトリに加えます。" |
| 4782 |
|
| 4783 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4784 |
# Tag: L-CFMD; |
| 4785 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4786 |
msgid "files containing the profiles are added in a <filename>simple-cdd</filename> subdirectory (that will end up on the CD-ROM);" |
| 4787 |
msgstr "プロファイルを含むファイルが <filename>simple-cdd</filename> サブディレクトリに追加されます (CD-ROM に追加されます)。" |
| 4788 |
|
| 4789 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4790 |
# Tag: L-CFMD; |
| 4791 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4792 |
msgid "other files listed in the <literal>all_extras</literal> parameter are also added;" |
| 4793 |
msgstr "<literal>all_extras</literal> パラメータで指定された他のファイルがディレクトリに追加されます。" |
| 4794 |
|
| 4795 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4796 |
# Tag: L-CFMD; |
| 4797 |
# Ref: $ zless /usr/share/doc/simple-cdd/examples/simple-cdd.conf.detailed.gz; |
| 4798 |
msgid "the boot parameters are adjusted so as to enable the preseeding. Questions concerning language and country can be avoided if the required information is stored in the <literal>language</literal> and <literal>country</literal> variables." |
| 4799 |
msgstr "起動パラメータが調整され、preseed が有効化されます。言語と国に関する質問を避けるには、これらの情報を <literal>language</literal> と <literal>country</literal> 変数に保存します。" |
| 4800 |
|
| 4801 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4802 |
msgid "debian-cd then generates the final ISO image." |
| 4803 |
msgstr "この後、debian-cd が最終的な ISO イメージを生成します。" |
| 4804 |
|
| 4805 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4806 |
msgid "Generating an ISO Image" |
| 4807 |
msgstr "ISO イメージの生成" |
| 4808 |
|
| 4809 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4810 |
#, fuzzy |
| 4811 |
#| msgid "Once we have written a configuration file and defined our profiles, the remaining step is to invoke <command>build-simple-cdd --conf simple-cdd.conf</command>. After a few minutes, we get the required image in <filename>images/debian-8.0-amd64-CD-1.iso</filename>." |
| 4812 |
msgid "Once we have written a configuration file and defined our profiles, the remaining step is to invoke <command>build-simple-cdd --conf simple-cdd.conf</command>. After a few minutes, we get the required image in <filename>images/debian-11-amd64-CD-1.iso</filename>." |
| 4813 |
msgstr "設定ファイルの記述と自分のプロファイルの定義が完了したら、<command>build-simple-cdd --conf simple-cdd.conf</command> を実行します。数分後、要求されたイメージが <filename>images/debian-8.0-amd64-CD-1.iso</filename> に完成します。" |
| 4814 |
|
| 4815 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4816 |
#, fuzzy |
| 4817 |
#| msgid "<primary>Munin</primary>" |
| 4818 |
msgid "<primary>monitoring</primary>" |
| 4819 |
msgstr "<primary>Munin</primary>" |
| 4820 |
|
| 4821 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4822 |
msgid "<primary>Munin</primary>" |
| 4823 |
msgstr "<primary>Munin</primary>" |
| 4824 |
|
| 4825 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4826 |
msgid "<primary>Nagios</primary>" |
| 4827 |
msgstr "<primary>Nagios</primary>" |
| 4828 |
|
| 4829 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4830 |
msgid "Monitoring is a generic term, and the various involved activities have several goals: on the one hand, following usage of the resources provided by a machine allows anticipating saturation and the subsequent required upgrades; on the other hand, alerting the administrator as soon as a service is unavailable or not working properly means that the problems that do happen can be fixed sooner." |
| 4831 |
msgstr "監視は一般的な用語で、さまざまな目的で行われるさまざまな活動を意味します。すなわち一方では、マシンの提供するリソースが使い切られ、更新が必要になることを予測することが可能です。さらに他方では、サービスが利用できなくなったり適切に動作していないことを可能な限り早く管理者に警告することにより、発生した問題の早急な修正を可能にすることを意味します。" |
| 4832 |
|
| 4833 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4834 |
msgid "<emphasis>Munin</emphasis> covers the first area, by displaying graphical charts for historical values of a number of parameters (used RAM, occupied disk space, processor load, network traffic, Apache/MySQL load, and so on). <emphasis>Nagios</emphasis> covers the second area, by regularly checking that the services are working and available, and sending alerts through the appropriate channels (e-mails, text messages, and so on). Both have a modular design, which makes it easy to create new plug-ins to monitor specific parameters or services." |
| 4835 |
msgstr "<emphasis>Munin</emphasis> は最初の範囲をカバーします。すなわち <emphasis>Munin</emphasis> はいくつかのパラメータの経時変化をグラフィカルに図示します (使用された RAM、専有されたディスク領域、プロセッサの負荷、ネットワークトラフィック、Apache/MySQL の負荷などを図示します)。<emphasis>Nagios</emphasis> は 2 番目の範囲をカバーします。すなわち <emphasis>Nagios</emphasis> はサービスの稼働状態と利用可能状態を定期的に確認し、適切な経路 (電子メール、テキストメッセージなど) を通じて警告を送信します。<emphasis>Munin</emphasis> と <emphasis>Nagios</emphasis> はモジュール式に設計されているので、特定のパラメータやサービスを監視する新しいプラグインを簡単に作成できます。" |
| 4836 |
|
| 4837 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4838 |
msgid "<emphasis>ALTERNATIVE</emphasis> Zabbix, an integrated monitoring tool" |
| 4839 |
msgstr "<emphasis>ALTERNATIVE</emphasis> Zabbix、統合監視ツール" |
| 4840 |
|
| 4841 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4842 |
msgid "<primary>Zabbix</primary>" |
| 4843 |
msgstr "<primary>Zabbix</primary>" |
| 4844 |
|
| 4845 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4846 |
#, fuzzy |
| 4847 |
#| msgid "Although Munin and Nagios are in very common use, they are not the only players in the monitoring field, and each of them only handles half of the task (graphing on one side, alerting on the other). Zabbix, on the other hand, integrates both parts of monitoring; it also has a web interface for configuring the most common aspects. It has grown by leaps and bounds during the last few years, and can now be considered a viable contender. On the monitoring server, you would install <emphasis role=\"pkg\">zabbix-server-pgsql</emphasis> (or <emphasis role=\"pkg\">zabbix-server-mysql</emphasis>), possibly together with <emphasis role=\"pkg\">zabbix-frontend-php</emphasis> to have a web interface. On the hosts to monitor you would install <emphasis role=\"pkg\">zabbix-agent</emphasis> feeding data back to the server. <ulink type=\"block\" url=\"http://www.zabbix.com/\" />" |
| 4848 |
msgid "Although Munin and Nagios are in very common use, they are not the only players in the monitoring field, and each of them only handles half of the task (graphing on one side, alerting on the other). Zabbix, on the other hand, integrates both parts of monitoring; it also has a web interface for configuring the most common aspects. It has grown by leaps and bounds during the last few years, and can now be considered a viable contender. On the monitoring server, you would install <emphasis role=\"pkg\">zabbix-server-pgsql</emphasis> (or <emphasis role=\"pkg\">zabbix-server-mysql</emphasis>), possibly together with <emphasis role=\"pkg\">zabbix-frontend-php</emphasis> to have a web interface. On the hosts to monitor you would install <emphasis role=\"pkg\">zabbix-agent</emphasis> feeding data back to the server. <ulink type=\"block\" url=\"https://zabbix.com/\" />" |
| 4849 |
msgstr "Munin と Nagios はとてもよく使われていますが、監視分野における唯一の選択肢というわけではありませんし、両者が担当している範囲は監視タスクの半分 (片方がグラフ化、もう一方が警告) に留まっています。これに対して、Zabbix は監視タスクの両方を統合しています。さらに Zabbix は最もよく使われる側面を設定するためのウェブインターフェースを備えています。Zabbix は最近の数年間で急速に成長し続けており、今や Munin と Nagios の対抗馬と考えられています。監視サーバには <emphasis role=\"pkg\">zabbix-server-pgsql</emphasis> (または <emphasis role=\"pkg\">zabbix-server-mysql</emphasis>) をインストールし、ウェブインターフェースを使うには <emphasis role=\"pkg\">zabbix-frontend-php</emphasis> もインストールします。監視対象ホストには <emphasis role=\"pkg\">zabbix-agent</emphasis> をインストールして、監視サーバからのデータ要求に応答します。<ulink type=\"block\" url=\"http://www.zabbix.com/\" />" |
| 4850 |
|
| 4851 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4852 |
msgid "<emphasis>ALTERNATIVE</emphasis> Icinga, a Nagios fork" |
| 4853 |
msgstr "<emphasis>ALTERNATIVE</emphasis> Icinga、Nagios のフォーク" |
| 4854 |
|
| 4855 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4856 |
msgid "<primary>Icinga</primary>" |
| 4857 |
msgstr "<primary>Icinga</primary>" |
| 4858 |
|
| 4859 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4860 |
#, fuzzy |
| 4861 |
#| msgid "Spurred by divergences in opinions concerning the development model for Nagios (which is controlled by a company), a number of developers forked Nagios and use Icinga as their new name. Icinga is still compatible — so far — with Nagios configurations and plugins, but it also adds extra features. <ulink type=\"block\" url=\"http://www.icinga.org/\" />" |
| 4862 |
msgid "Spurred by divergences in opinions concerning the development model for Nagios (which is controlled by a company), a number of developers forked Nagios and use Icinga as their new name. Icinga is still compatible — so far — with Nagios configurations and plugins, but it also adds extra features. <ulink type=\"block\" url=\"https://icinga.com/\" />" |
| 4863 |
msgstr "Nagios の開発モデル (開発は企業によって管理されています) に関する意見の食い違いが引き金となり、多数の開発者が Nagios をフォークし、新しい名前として Icinga を使っています。現時点で Icinga はまだ Nagios の設定およびプラグインと互換性を持っています。しかし、Icinga にはいくつかの機能が追加されています。<ulink type=\"block\" url=\"http://www.icinga.org/\" />" |
| 4864 |
|
| 4865 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4866 |
msgid "Setting Up Munin" |
| 4867 |
msgstr "Munin のセットアップ" |
| 4868 |
|
| 4869 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4870 |
#, fuzzy |
| 4871 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4872 |
msgid "<primary>Munin</primary><secondary>grapher</secondary>" |
| 4873 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4874 |
|
| 4875 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4876 |
msgid "The purpose of Munin is to monitor many machines; therefore, it quite naturally uses a client/server architecture. The central host — the grapher — collects data from all the monitored hosts, and generates historical graphs." |
| 4877 |
msgstr "Munin の目的は多くのマシンを監視することです。そしてこのため、Munin は当然クライアント/サーバアーキテクチャを採用しています。グラフ化を担当している中央ホストがすべての監視されているホストからデータを収集し、データの履歴グラフを生成します。" |
| 4878 |
|
| 4879 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4880 |
msgid "Configuring Hosts To Monitor" |
| 4881 |
msgstr "監視対象ホストの設定" |
| 4882 |
|
| 4883 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4884 |
#, fuzzy |
| 4885 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4886 |
msgid "<primary>server</primary><secondary>munin-node</secondary>" |
| 4887 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4888 |
|
| 4889 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4890 |
# Ref: https://packages.debian.org/jessie/all/munin-plugins-core/filelist; |
| 4891 |
# Ref: $ man 8 munin-node |
| 4892 |
msgid "The first step is to install the <emphasis role=\"pkg\">munin-node</emphasis> package. The daemon installed by this package listens on port 4949 and sends back the data collected by all the active plugins. Each plugin is a simple program returning a description of the collected data as well as the latest measured value. Plugins are stored in <filename>/usr/share/munin/plugins/</filename>, but only those with a symbolic link in <filename>/etc/munin/plugins/</filename> are really used." |
| 4893 |
msgstr "最初に <emphasis role=\"pkg\">munin-node</emphasis> パッケージをインストールします。<emphasis role=\"pkg\">munin-node</emphasis> パッケージによってインストールされるデーモンはポート 4949 番をリッスンし、すべての動作しているプラグインによって収集されたデータを送り返します。それぞれのプラグインは収集されたデータの説明および最新の計測値を返す簡単なプログラムです。プラグインは <filename>/usr/share/munin/plugins/</filename> に保存されますが、実際に使われるのは <filename>/etc/munin/plugins/</filename> 内からシンボリックリンクを張られたプラグインだけです。" |
| 4894 |
|
| 4895 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/munin/</filename></secondary><see>Munin</see>" |
| 4896 |
msgstr "" |
| 4897 |
|
| 4898 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4899 |
#, fuzzy |
| 4900 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4901 |
msgid "<primary>Munin</primary><secondary><filename>/etc/munin/plugins/</filename></secondary>" |
| 4902 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4903 |
|
| 4904 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4905 |
#, fuzzy |
| 4906 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4907 |
msgid "<primary>Munin</primary><secondary>plugins</secondary>" |
| 4908 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4909 |
|
| 4910 |
msgid "When the package is installed, a set of active plugins is determined based on the available software and the current configuration of the host. However, this auto-configuration depends on a feature that each plugin must provide, and it is usually a good idea to review and tweak the results by hand. Browsing the Plugin Gallery can be interesting even though not all plugins have comprehensive documentation. <ulink type=\"block\" url=\"https://gallery.munin-monitoring.org\" />" |
| 4911 |
msgstr "" |
| 4912 |
|
| 4913 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4914 |
#, fuzzy |
| 4915 |
#| msgid "When the package is installed, a set of active plugins is determined based on the available software and the current configuration of the host. However, this autoconfiguration depends on a feature that each plugin must provide, and it is usually a good idea to review and tweak the results by hand. Browsing the <ulink url=\"http://gallery.munin-monitoring.org\">Plugin Gallery</ulink> can be interesting even though not all plugins have comprehensive documentation. However, all plugins are scripts and most are rather simple and well-commented. Browsing <filename>/etc/munin/plugins/</filename> is therefore a good way of getting an idea of what each plugin is about and determining which should be removed. Similarly, enabling an interesting plugin found in <filename>/usr/share/munin/plugins/</filename> is a simple matter of setting up a symbolic link with <command>ln -sf /usr/share/munin/plugins/<replaceable>plugin</replaceable> /etc/munin/plugins/</command>. Note that when a plugin name ends with an underscore “_”, the plugin requires a parameter. This parameter must be stored in the name of the symbolic link; for instance, the “if_” plugin must be enabled with a <filename>if_eth0</filename> symbolic link, and it will monitor network traffic on the eth0 interface." |
| 4916 |
msgid "However, all plugins are scripts and most are rather simple and well-commented. Browsing <filename>/etc/munin/plugins/</filename> is therefore a good way of getting an idea of what each plugin is about and determining which should be removed. Similarly, enabling an interesting plugin found in <filename>/usr/share/munin/plugins/</filename> is a simple matter of setting up a symbolic link with <command>ln -sf /usr/share/munin/plugins/<replaceable>plugin</replaceable> /etc/munin/plugins/</command>. Note that when a plugin name ends with an underscore “_”, the plugin requires a parameter. This parameter must be stored in the name of the symbolic link; for instance, the “if_” plugin must be enabled with a <filename>if_eth0</filename> symbolic link, and it will monitor network traffic on the eth0 interface." |
| 4917 |
msgstr "<emphasis role=\"pkg\">munin-node</emphasis> パッケージのインストールが完了したら、利用できるソフトウェアと現在のホストの設定に基づいて有効なプラグイン群が決定されます。しかしながら、有効プラグインの自動決定は各プラグインの提供する機能に依存します。通常、手作業で結果を確認して微調整することを推奨します。すべてのプラグインに対して包括的な文書が用意されているわけではありませんが、<ulink url=\"http://gallery.munin-monitoring.org\">プラグインギャラリー</ulink>を閲覧すると面白いかもしれません。さらに、すべてのプラグインはスクリプトで、その多くは単純かつ詳細に説明されています。このため、各プラグインの機能を理解して無効化するべきプラグインを決定するには <filename>/etc/munin/plugins/</filename> を閲覧すると良いでしょう。同様に、<filename>/usr/share/munin/plugins/</filename> の中にある興味深いプラグインを有効化するには、<command>ln -sf /usr/share/munin/plugins/<replaceable>plugin</replaceable> /etc/munin/plugins/</command> を使ってシンボリックリンクを作成するだけです。プラグイン名がアンダースコア「_」で終わる場合、そのプラグインはパラメータが必要という点に注意してください。シンボリックリンクの名前を使って、このパラメータを指定します。従って、たとえば「if_」プラグインは必ず <filename>if_eth0</filename> シンボリックリンクを使って有効化しなければいけません。こうすることで、eth0 インターフェースのネットワークトラフィックを監視します。" |
| 4918 |
|
| 4919 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4920 |
#, fuzzy |
| 4921 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4922 |
msgid "<primary>Munin</primary><secondary><filename>/etc/munin/munin-node.conf</filename></secondary>" |
| 4923 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4924 |
|
| 4925 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4926 |
#, fuzzy |
| 4927 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4928 |
msgid "<primary>service</primary><secondary><filename>munin-node.service</filename></secondary>" |
| 4929 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4930 |
|
| 4931 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4932 |
#, fuzzy |
| 4933 |
#| msgid "Once all plugins are correctly set up, the daemon configuration must be updated to describe access control for the collected data. This involves <literal>allow</literal> directives in the <filename>/etc/munin/munin-node.conf</filename> file. The default configuration is <literal>allow ^127\\.0\\.0\\.1$</literal>, and only allows access to the local host. An administrator will usually add a similar line containing the IP address of the grapher host, then restart the daemon with <command>service munin-node restart</command>." |
| 4934 |
msgid "Once all plugins are correctly set up, the daemon configuration must be updated to describe access control for the collected data. This involves <literal>allow</literal> directives in the <filename>/etc/munin/munin-node.conf</filename> file. The default configuration is <literal>allow ^127\\.0\\.0\\.1$</literal>, and only allows access to the local host. An administrator will usually add a similar line containing the IP address of the grapher host, then restart the daemon with <command>systemctl restart munin-node</command>." |
| 4935 |
msgstr "すべてのプラグインを正常に設定したら、収集されたデータへのアクセス制御に関するデーモン設定を更新します。これを行うには、<filename>/etc/munin/munin-node.conf</filename> ファイルの中で <literal>allow</literal> 指示文を使います。デフォルト設定は <literal>allow ^127\\.0\\.0\\.1$</literal> で、ローカルホストへのアクセスのみを許可します。通常、管理者はグラフ化を担当しているホストの IP アドレスを含めた同様の行を追加します。その後、<command>service munin-node restart</command> を使ってデーモンを再起動します。" |
| 4936 |
|
| 4937 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4938 |
msgid "<emphasis>GOING FURTHER</emphasis> Creating local plugins" |
| 4939 |
msgstr "<emphasis>GOING FURTHER</emphasis> ローカルプラグインの作成" |
| 4940 |
|
| 4941 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4942 |
#, fuzzy |
| 4943 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 4944 |
msgid "<primary>Munin</primary><secondary><command>munin-run</command></secondary>" |
| 4945 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 4946 |
|
| 4947 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4948 |
#, fuzzy |
| 4949 |
#| msgid "Munin does include detailed documentation on how plugins should behave, and how to develop new plugins. <ulink type=\"block\" url=\"http://munin-monitoring.org/wiki/plugins\" />" |
| 4950 |
msgid "Munin does include detailed documentation on how plugins should behave, and how to develop new plugins. <ulink type=\"block\" url=\"https://guide.munin-monitoring.org/en/latest/plugin/writing.html\" />" |
| 4951 |
msgstr "Munin にはプラグインの動作様式と新規プラグインの開発方法に関する詳細な文書が用意されています。<ulink type=\"block\" url=\"http://munin-monitoring.org/wiki/plugins\" />" |
| 4952 |
|
| 4953 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4954 |
msgid "A plugin is best tested when run in the same conditions as it would be when triggered by munin-node; this can be simulated by running <command>munin-run <replaceable>plugin</replaceable></command> as root. A potential second parameter given to this command (such as <literal>config</literal>) is passed to the plugin as a parameter." |
| 4955 |
msgstr "プラグインを検査するには、プラグインが munin-node から実行されたのと同じ状況下で実行するのが最良の方法です。この状況を模倣するには root で <command>munin-run <replaceable>plugin</replaceable></command> を実行します。このコマンドに与えられた 2 番目のパラメータ (<literal>config</literal> など) はパラメータとしてプラグインに渡されます。" |
| 4956 |
|
| 4957 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4958 |
msgid "When a plugin is invoked with the <literal>config</literal> parameter, it must describe itself by returning a set of fields:" |
| 4959 |
msgstr "プラグインに <literal>config</literal> パラメータを付けて実行した場合、プラグイン自身を説明する一連のフィールドが返されます。" |
| 4960 |
|
| 4961 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4962 |
#, fuzzy |
| 4963 |
#| msgid "" |
| 4964 |
#| "<computeroutput>$ </computeroutput><userinput>sudo munin-run load config\n" |
| 4965 |
#| "</userinput><computeroutput>graph_title Load average\n" |
| 4966 |
#| "graph_args --base 1000 -l 0\n" |
| 4967 |
#| "graph_vlabel load\n" |
| 4968 |
#| "graph_scale no\n" |
| 4969 |
#| "graph_category system\n" |
| 4970 |
#| "load.label load\n" |
| 4971 |
#| "graph_info The load average of the machine describes how many processes are in the run-queue (scheduled to run \"immediately\").\n" |
| 4972 |
#| "load.info 5 minute load average\n" |
| 4973 |
#| "</computeroutput>" |
| 4974 |
msgid "" |
| 4975 |
"<computeroutput># </computeroutput><userinput>munin-run load config\n" |
| 4976 |
"</userinput><computeroutput>graph_title Load average\n" |
| 4977 |
"graph_args --base 1000 -l 0\n" |
| 4978 |
"graph_vlabel load\n" |
| 4979 |
"graph_scale no\n" |
| 4980 |
"graph_category system\n" |
| 4981 |
"load.label load\n" |
| 4982 |
"graph_info The load average of the machine describes how many processes are in the run-queue (scheduled to run \"immediately\").\n" |
| 4983 |
"load.info 5 minute load average\n" |
| 4984 |
"</computeroutput>" |
| 4985 |
msgstr "" |
| 4986 |
"<computeroutput>$ </computeroutput><userinput>sudo munin-run load config\n" |
| 4987 |
"</userinput><computeroutput>graph_title Load average\n" |
| 4988 |
"graph_args --base 1000 -l 0\n" |
| 4989 |
"graph_vlabel load\n" |
| 4990 |
"graph_scale no\n" |
| 4991 |
"graph_category system\n" |
| 4992 |
"load.label load\n" |
| 4993 |
"graph_info The load average of the machine describes how many processes are in the run-queue (scheduled to run \"immediately\").\n" |
| 4994 |
"load.info 5 minute load average\n" |
| 4995 |
"</computeroutput>" |
| 4996 |
|
| 4997 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 4998 |
#, fuzzy |
| 4999 |
#| msgid "The various available fields are described by the “Plugin reference” available as part of the “Munin guide”. <ulink type=\"block\" url=\"http://munin.readthedocs.org/en/latest/reference/plugin.html\" />" |
| 5000 |
msgid "The various available fields are described by the “Plugin reference” available as part of the “Munin guide”. <ulink type=\"block\" url=\"https://munin.readthedocs.org/en/latest/reference/plugin.html\" />" |
| 5001 |
msgstr "利用できるさまざまなフィールドは「Munin ガイド」の一部として提供されている「プラグインリファレンス」で説明されています。<ulink type=\"block\" url=\"http://munin.readthedocs.org/en/latest/reference/plugin.html\" />" |
| 5002 |
|
| 5003 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5004 |
msgid "When invoked without a parameter, the plugin simply returns the last measured values; for instance, executing <command>sudo munin-run load</command> could return <literal>load.value 0.12</literal>." |
| 5005 |
msgstr "パラメータを付けずにプラグインを実行した場合、プラグインは最新の計測値を返却します。従って、たとえば <command>sudo munin-run load</command> を実行すると <literal>load.value 0.12</literal> が返されます。" |
| 5006 |
|
| 5007 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5008 |
msgid "Finally, when a plugin is invoked with the <literal>autoconf</literal> parameter, it should return “yes” (and a 0 exit status) or “no” (with a 1 exit status) according to whether the plugin should be enabled on this host." |
| 5009 |
msgstr "最後に、プラグインに <literal>autoconf</literal> パラメータを付けて実行した場合、プラグインは自分が対象のホストで有効化されているか否かに基づいて「yes」(終了ステータス 0) または「no」(終了ステータス 1) を返すべきです。" |
| 5010 |
|
| 5011 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5012 |
msgid "Configuring the Grapher" |
| 5013 |
msgstr "グラフ化担当マシンの設定" |
| 5014 |
|
| 5015 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5016 |
#, fuzzy |
| 5017 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 5018 |
msgid "<primary>Munin</primary><secondary><command>munin-cron</command></secondary>" |
| 5019 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 5020 |
|
| 5021 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5022 |
#, fuzzy |
| 5023 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 5024 |
msgid "<primary>Munin</primary><secondary><filename>/etc/munin/munin.conf</filename></secondary>" |
| 5025 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 5026 |
|
| 5027 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5028 |
# Checked-By: Osamu Aoki; |
| 5029 |
msgid "The “grapher” is simply the computer that aggregates the data and generates the corresponding graphs. The required software is in the <emphasis role=\"pkg\">munin</emphasis> package. The standard configuration runs <command>munin-cron</command> (once every 5 minutes), which gathers data from all the hosts listed in <filename>/etc/munin/munin.conf</filename> (only the local host is listed by default), saves the historical data in RRD files (<emphasis>Round Robin Database</emphasis>, a file format designed to store data varying in time) stored under <filename>/var/lib/munin/</filename> and generates an HTML page with the graphs in <filename>/var/cache/munin/www/</filename>." |
| 5030 |
msgstr "「グラフ化担当マシン」はデータを集計し対応するグラフを生成するだけのコンピュータです。「グラフ化担当マシン」に必要なソフトウェアは <emphasis role=\"pkg\">munin</emphasis> パッケージに含まれます。標準的な設定は <command>munin-cron</command> を (5 分ごとに) 実行します。このコマンドは <filename>/etc/munin/munin.conf</filename> にリストされているすべてのホスト (デフォルトではローカルホストのみがリストされています) からデータを収集し、時系列データを <filename>/var/lib/munin/</filename> にある RRD ファイル (<emphasis>Round Robin Database</emphasis>、経時変化するデータを保存するために設計されたファイルフォーマット) に保存し、<filename>/var/cache/munin/www/</filename> に含まれるグラフを使って HTML ページを生成します。" |
| 5031 |
|
| 5032 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5033 |
msgid "All monitored machines must therefore be listed in the <filename>/etc/munin/munin.conf</filename> configuration file. Each machine is listed as a full section with a name matching the machine and at least an <literal>address</literal> entry giving the corresponding IP address." |
| 5034 |
msgstr "すべての監視対象のマシンは <filename>/etc/munin/munin.conf</filename> 設定ファイルにリストされていなければいけません。各マシンは完全なセクションの形でリストされています。セクションはマシンと同じ名前で、少なくとも対応する IP アドレスを指定する <literal>address</literal> エントリを持っていなければいけません。" |
| 5035 |
|
| 5036 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5037 |
msgid "" |
| 5038 |
"[ftp.falcot.com]\n" |
| 5039 |
" address 192.168.0.12\n" |
| 5040 |
" use_node_name yes" |
| 5041 |
msgstr "" |
| 5042 |
"[ftp.falcot.com]\n" |
| 5043 |
" address 192.168.0.12\n" |
| 5044 |
" use_node_name yes" |
| 5045 |
|
| 5046 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5047 |
msgid "Sections can be more complex, and describe extra graphs that could be created by combining data coming from several machines. The samples provided in the configuration file are good starting points for customization." |
| 5048 |
msgstr "セクションをさらに複雑にして、複数のマシンからのデータをまとめて作成されるグラフを追加することも可能です。設定ファイルの中で提供されている見本がカスタマイズの良い足掛かりとなります。" |
| 5049 |
|
| 5050 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5051 |
msgid "The last step is to publish the generated pages; this involves configuring a web server so that the contents of <filename>/var/cache/munin/www/</filename> are made available on a website. Access to this website will often be restricted, using either an authentication mechanism or IP-based access control. See <xref linkend=\"sect.http-web-server\" /> for the relevant details." |
| 5052 |
msgstr "最後の段階は生成されたページを公開することです。そしてこれは、ウェブサイトから <filename>/var/cache/munin/www/</filename> の内容を利用できるようにするようウェブサーバを設定することを意味しています。通常このウェブサイトへのアクセスは認証メカニズムか IP に基づくアクセス制御を使って制限されています。アクセス制御の詳細は<xref linkend=\"sect.http-web-server\" />をご覧ください。" |
| 5053 |
|
| 5054 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5055 |
msgid "Setting Up Nagios" |
| 5056 |
msgstr "Nagios のセットアップ" |
| 5057 |
|
| 5058 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5059 |
#, fuzzy |
| 5060 |
#| msgid "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 5061 |
msgid "<primary><emphasis role=\"pkg\">nagios4</emphasis></primary>" |
| 5062 |
msgstr "<primary><emphasis role=\"pkg\">mdadm</emphasis></primary>" |
| 5063 |
|
| 5064 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5065 |
#, fuzzy |
| 5066 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 5067 |
msgid "<primary><emphasis role=\"pkg\">monitoring-plugins</emphasis></primary>" |
| 5068 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 5069 |
|
| 5070 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5071 |
msgid "Unlike Munin, Nagios does not necessarily require installing anything on the monitored hosts; most of the time, Nagios is used to check the availability of network services. For instance, Nagios can connect to a web server and check that a given web page can be obtained within a given time." |
| 5072 |
msgstr "Munin と異なり、Nagios の場合、必ずしも監視対象のホストに何かをインストールする必要はありません。そしてほとんどの場合、Nagios はネットワークサービスの可用性を確認するために使われます。たとえば Nagios を使うことで、ウェブサーバに接続して特定のウェブページがある時間内に取得できるかを確認することが可能です。" |
| 5073 |
|
| 5074 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5075 |
msgid "Installing" |
| 5076 |
msgstr "インストール" |
| 5077 |
|
| 5078 |
msgid "The first step in setting up Nagios is to install the <emphasis role=\"pkg\">nagios4</emphasis> and <emphasis role=\"pkg\">monitoring-plugins</emphasis> packages. Installing the packages configures the web interface and the Apache server. The <literal>authz_groupfile</literal> and <literal>auth_digest</literal> Apache modules must be enabled, for that execute:" |
| 5079 |
msgstr "" |
| 5080 |
|
| 5081 |
msgid "" |
| 5082 |
"<computeroutput># </computeroutput><userinput>a2enmod authz_groupfile\n" |
| 5083 |
"</userinput><computeroutput>Considering dependency authz_core for authz_groupfile:\n" |
| 5084 |
"Module authz_core already enabled\n" |
| 5085 |
"Module authz_core already enabled\n" |
| 5086 |
"Enabling module authz_groupfile.\n" |
| 5087 |
"To activate the new configuration, you need to run:\n" |
| 5088 |
" systemctl restart apache2\n" |
| 5089 |
"# </computeroutput><userinput>a2enmod auth_digest\n" |
| 5090 |
"</userinput><computeroutput>Considering dependency authn_core for auth_digest:\n" |
| 5091 |
"Module authn_core already enabled\n" |
| 5092 |
"Enabling module auth_digest.\n" |
| 5093 |
"To activate the new configuration, you need to run:\n" |
| 5094 |
" systemctl restart apache2\n" |
| 5095 |
"# </computeroutput><userinput>systemctl restart apache2\n" |
| 5096 |
"</userinput>" |
| 5097 |
msgstr "" |
| 5098 |
|
| 5099 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/nagios4/</filename></secondary><see>Nagios</see>" |
| 5100 |
msgstr "" |
| 5101 |
|
| 5102 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5103 |
#, fuzzy |
| 5104 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 5105 |
msgid "<primary>Nagios</primary><secondary><filename>/etc/nagios4/hdigest.users</filename></secondary>" |
| 5106 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 5107 |
|
| 5108 |
msgid "Adding other users is a simple matter of inserting them in the <filename>/etc/nagios4/hdigest.users</filename> file." |
| 5109 |
msgstr "" |
| 5110 |
|
| 5111 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5112 |
#, fuzzy |
| 5113 |
#| msgid "Pointing a browser at <literal>http://<replaceable>server</replaceable>/nagios3/</literal> displays the web interface; in particular, note that Nagios already monitors some parameters of the machine where it runs. However, some interactive features such as adding comments to a host do not work. These features are disabled in the default configuration for Nagios, which is very restrictive for security reasons." |
| 5114 |
msgid "Pointing a browser at <literal>http://<replaceable>server</replaceable>/nagios4/</literal> displays the web interface; in particular, note that Nagios already monitors some parameters of the machine where it runs. However, some interactive features such as adding comments to a host do not work. These features are disabled in the default configuration for Nagios, which is very restrictive for security reasons." |
| 5115 |
msgstr "ブラウザで <literal>http://<replaceable>server</replaceable>/nagios3/</literal> にアクセスすると、ウェブインターフェースが表示されます。特に、Nagios は自分が実行されているマシンのいくつかのパラメータを既に監視している点に注意してください。しかしながら、たとえばホストに対するコメントを追加するなどの対話型機能は動作しません。Nagios のデフォルト設定はこれらの機能を無効化し、セキュリティの理由からとても厳しい制限を設けています。" |
| 5116 |
|
| 5117 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5118 |
#, fuzzy |
| 5119 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 5120 |
msgid "<primary>Nagios</primary><secondary><filename>/etc/nagios4/nagios.cfg</filename></secondary>" |
| 5121 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 5122 |
|
| 5123 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5124 |
# Ref: https://packages.debian.org/jessie/all/nagios3-common/filelist |
| 5125 |
#, fuzzy |
| 5126 |
#| msgid "As documented in <filename>/usr/share/doc/nagios3/README.Debian</filename>, enabling some features involves editing <filename>/etc/nagios3/nagios.cfg</filename> and setting its <literal>check_external_commands</literal> parameter to “1”. We also need to set up write permissions for the directory used by Nagios, with commands such as the following:" |
| 5127 |
msgid "Enabling some features involves editing <filename>/etc/nagios4/nagios.cfg</filename>. We also need to set up write permissions for the directory used by Nagios, with commands such as the following:" |
| 5128 |
msgstr "<filename>/usr/share/doc/nagios3/README.Debian</filename> で説明されている通り、いくつかの機能を有効化するには <filename>/etc/nagios3/nagios.cfg</filename> を編集し、<literal>check_external_commands</literal> パラメータを「1」に設定します。また、以下のようにして、Nagios が使うディレクトリに書き込みパーミッションを設定する必要があります。" |
| 5129 |
|
| 5130 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5131 |
#, fuzzy |
| 5132 |
#| msgid "" |
| 5133 |
#| "<computeroutput># </computeroutput><userinput>service nagios3 stop</userinput>\n" |
| 5134 |
#| "<computeroutput>[...]\n" |
| 5135 |
#| "# </computeroutput><userinput>dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios3/rw\n" |
| 5136 |
#| "</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios3\n" |
| 5137 |
#| "</userinput><computeroutput># </computeroutput><userinput>service nagios3 start</userinput>\n" |
| 5138 |
#| "<computeroutput>[...]</computeroutput>" |
| 5139 |
msgid "" |
| 5140 |
"<computeroutput># </computeroutput><userinput>systemctl stop nagios4\n" |
| 5141 |
"</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios4/rw\n" |
| 5142 |
"</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios4\n" |
| 5143 |
"</userinput><computeroutput># </computeroutput><userinput>systemctl start nagios4\n" |
| 5144 |
"</userinput>" |
| 5145 |
msgstr "" |
| 5146 |
"<computeroutput># </computeroutput><userinput>service nagios3 stop</userinput>\n" |
| 5147 |
"<computeroutput>[...]\n" |
| 5148 |
"# </computeroutput><userinput>dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios3/rw\n" |
| 5149 |
"</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios3\n" |
| 5150 |
"</userinput><computeroutput># </computeroutput><userinput>service nagios3 start</userinput>\n" |
| 5151 |
"<computeroutput>[...]</computeroutput>" |
| 5152 |
|
| 5153 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5154 |
msgid "Configuring" |
| 5155 |
msgstr "設定" |
| 5156 |
|
| 5157 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5158 |
#, fuzzy |
| 5159 |
#| msgid "The Nagios web interface is rather nice, but it does not allow configuration, nor can it be used to add monitored hosts and services. The whole configuration is managed via files referenced in the central configuration file, <filename>/etc/nagios3/nagios.cfg</filename>." |
| 5160 |
msgid "The Nagios web interface is rather nice, but it does not allow configuration, nor can it be used to add monitored hosts and services. The whole configuration is managed via files referenced in the central configuration file, <filename>/etc/nagios4/nagios.cfg</filename>." |
| 5161 |
msgstr "Nagios のウェブインターフェースはかなり良くできていますが、設定もできませんし、監視対象のホストやサービスの追加もできません。全体の設定は中央設定ファイル <filename>/etc/nagios3/nagios.cfg</filename> から参照されているオブジェクト設定ファイルを使って管理されます。" |
| 5162 |
|
| 5163 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5164 |
# Ref: $ less /etc/nagios3/nagios.cfg; |
| 5165 |
# Ref: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/configobject.html; |
| 5166 |
# Ref: https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/objectdefinitions.html; |
| 5167 |
msgid "These files should not be dived into without some understanding of the Nagios concepts. The configuration lists objects of the following types:" |
| 5168 |
msgstr "Nagios の概念を理解していない場合、オブジェクト設定ファイルの内容に立ち入るべきではありません。オブジェクト設定ファイルから設定するオブジェクトには以下の種類があります。" |
| 5169 |
|
| 5170 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5171 |
msgid "a <emphasis>host</emphasis> is a machine to be monitored;" |
| 5172 |
msgstr "<emphasis>host</emphasis> は監視対象のマシンです。" |
| 5173 |
|
| 5174 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5175 |
msgid "a <emphasis>hostgroup</emphasis> is a set of hosts that should be grouped together for display, or to factor some common configuration elements;" |
| 5176 |
msgstr "<emphasis>hostgroup</emphasis> はグループ化して表示されたり、同じ設定要素を持つホスト群です。" |
| 5177 |
|
| 5178 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5179 |
msgid "a <emphasis>service</emphasis> is a testable element related to a host or a host group. It will most often be a check for a network service, but it can also involve checking that some parameters are within an acceptable range (for instance, free disk space or processor load);" |
| 5180 |
msgstr "<emphasis>service</emphasis> はホストやホストグループへの検査項目を定義します。これは多くの場合、あるネットワークサービスに対する検査を定義するものですが、いくつかのパラメータ (たとえば空きディスク領域やプロセッサ負荷) が条件を満たす範囲内にあるかに対する検査を定義することも可能です。" |
| 5181 |
|
| 5182 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5183 |
msgid "a <emphasis>servicegroup</emphasis> is a set of services that should be grouped together for display;" |
| 5184 |
msgstr "<emphasis>servicegroup</emphasis> はグループ化して表示されるサービス群です。" |
| 5185 |
|
| 5186 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5187 |
msgid "a <emphasis>contact</emphasis> is a person who can receive alerts;" |
| 5188 |
msgstr "<emphasis>contact</emphasis> は警告を受け取る人です。" |
| 5189 |
|
| 5190 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5191 |
msgid "a <emphasis>contactgroup</emphasis> is a set of such contacts;" |
| 5192 |
msgstr "<emphasis>contactgroup</emphasis> は警告を受け取る人のグループです。" |
| 5193 |
|
| 5194 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5195 |
msgid "a <emphasis>timeperiod</emphasis> is a range of time during which some services have to be checked;" |
| 5196 |
msgstr "<emphasis>timeperiod</emphasis> は時間範囲で、この範囲内にいくつかのサービスを確認します。" |
| 5197 |
|
| 5198 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5199 |
msgid "a <emphasis>command</emphasis> is the command line invoked to check a given service." |
| 5200 |
msgstr "<emphasis>command</emphasis> はサービスを確認するために実行するコマンドラインです。" |
| 5201 |
|
| 5202 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5203 |
msgid "According to its type, each object has a number of properties that can be customized. A full list would be too long to include, but the most important properties are the relations between the objects." |
| 5204 |
msgstr "オブジェクトの種類に応じて、各オブジェクトにはカスタマイズが可能な複数の属性が含まれます。完全なリストはここに挙げるには長すぎますが、最重要の属性はオブジェクト間の関係性を示す属性です。" |
| 5205 |
|
| 5206 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5207 |
msgid "A <emphasis>service</emphasis> uses a <emphasis>command</emphasis> to check the state of a feature on a <emphasis>host</emphasis> (or a <emphasis>hostgroup</emphasis>) within a <emphasis>timeperiod</emphasis>. In case of a problem, Nagios sends an alert to all members of the <emphasis>contactgroup</emphasis> linked to the service. Each member is sent the alert according to the channel described in the matching <emphasis>contact</emphasis> object." |
| 5208 |
msgstr "<emphasis>service</emphasis> は <emphasis>command</emphasis> を使い、<emphasis>timeperiod</emphasis> で定めた時間内に <emphasis>host</emphasis> (または <emphasis>hostgroup</emphasis>) で稼働する特定の機能を確認します。問題が起きた場合、Nagios はそのサービスに関連付けられた <emphasis>contactgroup</emphasis> のメンバーに警告を送信します。各メンバーは対応する <emphasis>contact</emphasis> オブジェクトに書かれたチャンネルを介して警告を受け取ります。" |
| 5209 |
|
| 5210 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5211 |
#, fuzzy |
| 5212 |
#| msgid "An inheritance system allows easy sharing of a set of properties across many objects without duplicating information. Moreover, the initial configuration includes a number of standard objects; in many cases, defining new hosts, services and contacts is a simple matter of deriving from the provided generic objects. The files in <filename>/etc/nagios3/conf.d/</filename> are a good source of information on how they work." |
| 5213 |
msgid "An inheritance system allows easy sharing of a set of properties across many objects without duplicating information. Moreover, the initial configuration includes a number of standard objects; in many cases, defining new hosts, services and contacts is a simple matter of deriving from the provided generic objects. The files in <filename>/etc/nagios4/conf.d/</filename> are a good source of information on how they work." |
| 5214 |
msgstr "継承システムにより、情報を複製せずに多くのオブジェクト間の属性群を簡単に共有することが可能です。加えて、初期設定には数多くの標準的なオブジェクトが定義されています。このため多くの場合、初期設定の標準的なオブジェクトに加えて新たな <emphasis>host</emphasis>、<emphasis>service</emphasis>、<emphasis>contact</emphasis> を定義するだけで簡単に設定を完了させることが可能です。<filename>/etc/nagios3/conf.d/</filename> に含まれるファイルはオブジェクトの動作に関する良い情報源です。" |
| 5215 |
|
| 5216 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5217 |
#, fuzzy |
| 5218 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 5219 |
msgid "<primary>Nagios</primary><secondary><filename>/etc/nagios4/conf.d/</filename></secondary>" |
| 5220 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 5221 |
|
| 5222 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5223 |
msgid "The Falcot Corp administrators use the following configuration:" |
| 5224 |
msgstr "Falcot Corp の管理者は以下の設定を使います。" |
| 5225 |
|
| 5226 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5227 |
#, fuzzy |
| 5228 |
#| msgid "<filename>/etc/nagios3/conf.d/falcot.cfg</filename> file" |
| 5229 |
msgid "<filename>/etc/nagios4/conf.d/falcot.cfg</filename> file" |
| 5230 |
msgstr "<filename>/etc/nagios3/conf.d/falcot.cfg</filename> ファイル" |
| 5231 |
|
| 5232 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5233 |
#, fuzzy |
| 5234 |
#| msgid "" |
| 5235 |
#| "define contact{\n" |
| 5236 |
#| " name generic-contact\n" |
| 5237 |
#| " service_notification_period 24x7\n" |
| 5238 |
#| " host_notification_period 24x7\n" |
| 5239 |
#| " service_notification_options w,u,c,r\n" |
| 5240 |
#| " host_notification_options d,u,r\n" |
| 5241 |
#| " service_notification_commands notify-service-by-email\n" |
| 5242 |
#| " host_notification_commands notify-host-by-email\n" |
| 5243 |
#| " register 0 ; Template only\n" |
| 5244 |
#| "}\n" |
| 5245 |
#| "define contact{\n" |
| 5246 |
#| " use generic-contact\n" |
| 5247 |
#| " contact_name rhertzog\n" |
| 5248 |
#| " alias Raphael Hertzog\n" |
| 5249 |
#| " email [email protected]\n" |
| 5250 |
#| "}\n" |
| 5251 |
#| "define contact{\n" |
| 5252 |
#| " use generic-contact\n" |
| 5253 |
#| " contact_name rmas\n" |
| 5254 |
#| " alias Roland Mas\n" |
| 5255 |
#| " email [email protected]\n" |
| 5256 |
#| "}\n" |
| 5257 |
#| "\n" |
| 5258 |
#| "define contactgroup{\n" |
| 5259 |
#| " contactgroup_name falcot-admins\n" |
| 5260 |
#| " alias Falcot Administrators\n" |
| 5261 |
#| " members rhertzog,rmas\n" |
| 5262 |
#| "}\n" |
| 5263 |
#| "\n" |
| 5264 |
#| "define host{\n" |
| 5265 |
#| " use generic-host ; Name of host template to use\n" |
| 5266 |
#| " host_name www-host\n" |
| 5267 |
#| " alias www.falcot.com\n" |
| 5268 |
#| " address 192.168.0.5\n" |
| 5269 |
#| " contact_groups falcot-admins\n" |
| 5270 |
#| " hostgroups debian-servers,ssh-servers\n" |
| 5271 |
#| "}\n" |
| 5272 |
#| "define host{\n" |
| 5273 |
#| " use generic-host ; Name of host template to use\n" |
| 5274 |
#| " host_name ftp-host\n" |
| 5275 |
#| " alias ftp.falcot.com\n" |
| 5276 |
#| " address 192.168.0.6\n" |
| 5277 |
#| " contact_groups falcot-admins\n" |
| 5278 |
#| " hostgroups debian-servers,ssh-servers\n" |
| 5279 |
#| "}\n" |
| 5280 |
#| "\n" |
| 5281 |
#| "# 'check_ftp' command with custom parameters\n" |
| 5282 |
#| "define command{\n" |
| 5283 |
#| " command_name check_ftp2\n" |
| 5284 |
#| " command_line /usr/lib/nagios/plugins/check_ftp -H $HOSTADDRESS$ -w 20 -c 30 -t 35\n" |
| 5285 |
#| "}\n" |
| 5286 |
#| "\n" |
| 5287 |
#| "# Generic Falcot service\n" |
| 5288 |
#| "define service{\n" |
| 5289 |
#| " name falcot-service\n" |
| 5290 |
#| " use generic-service\n" |
| 5291 |
#| " contact_groups falcot-admins\n" |
| 5292 |
#| " register 0\n" |
| 5293 |
#| "}\n" |
| 5294 |
#| "\n" |
| 5295 |
#| "# Services to check on www-host\n" |
| 5296 |
#| "define service{\n" |
| 5297 |
#| " use falcot-service\n" |
| 5298 |
#| " host_name www-host\n" |
| 5299 |
#| " service_description HTTP\n" |
| 5300 |
#| " check_command check_http\n" |
| 5301 |
#| "}\n" |
| 5302 |
#| "define service{\n" |
| 5303 |
#| " use falcot-service\n" |
| 5304 |
#| " host_name www-host\n" |
| 5305 |
#| " service_description HTTPS\n" |
| 5306 |
#| " check_command check_https\n" |
| 5307 |
#| "}\n" |
| 5308 |
#| "define service{\n" |
| 5309 |
#| " use falcot-service\n" |
| 5310 |
#| " host_name www-host\n" |
| 5311 |
#| " service_description SMTP\n" |
| 5312 |
#| " check_command check_smtp\n" |
| 5313 |
#| "}\n" |
| 5314 |
#| "\n" |
| 5315 |
#| "# Services to check on ftp-host\n" |
| 5316 |
#| "define service{\n" |
| 5317 |
#| " use falcot-service\n" |
| 5318 |
#| " host_name ftp-host\n" |
| 5319 |
#| " service_description FTP\n" |
| 5320 |
#| " check_command check_ftp2\n" |
| 5321 |
#| "}" |
| 5322 |
msgid "" |
| 5323 |
"define contact{\n" |
| 5324 |
" name generic-contact\n" |
| 5325 |
" service_notification_period 24x7\n" |
| 5326 |
" host_notification_period 24x7\n" |
| 5327 |
" service_notification_options w,u,c,r\n" |
| 5328 |
" host_notification_options d,u,r\n" |
| 5329 |
" service_notification_commands notify-service-by-email\n" |
| 5330 |
" host_notification_commands notify-host-by-email\n" |
| 5331 |
" register 0 ; Template only\n" |
| 5332 |
"}\n" |
| 5333 |
"define contact{\n" |
| 5334 |
" use generic-contact\n" |
| 5335 |
" contact_name rhertzog\n" |
| 5336 |
" alias Raphael Hertzog\n" |
| 5337 |
" email [email protected]\n" |
| 5338 |
"}\n" |
| 5339 |
"define contact{\n" |
| 5340 |
" use generic-contact\n" |
| 5341 |
" contact_name rmas\n" |
| 5342 |
" alias Roland Mas\n" |
| 5343 |
" email [email protected]\n" |
| 5344 |
"}\n" |
| 5345 |
"\n" |
| 5346 |
"define contactgroup{\n" |
| 5347 |
" contactgroup_name falcot-admins\n" |
| 5348 |
" alias Falcot Administrators\n" |
| 5349 |
" members rhertzog,rmas\n" |
| 5350 |
"}\n" |
| 5351 |
"\n" |
| 5352 |
"define host{\n" |
| 5353 |
" use generic-host ; Name of host template to use\n" |
| 5354 |
" host_name www-host\n" |
| 5355 |
" alias www.falcot.com\n" |
| 5356 |
" address 192.168.0.5\n" |
| 5357 |
" contact_groups falcot-admins\n" |
| 5358 |
" hostgroups debian-servers,ssh-servers\n" |
| 5359 |
"}\n" |
| 5360 |
"define host{\n" |
| 5361 |
" use generic-host ; Name of host template to use\n" |
| 5362 |
" host_name ftp-host\n" |
| 5363 |
" alias ftp.falcot.com\n" |
| 5364 |
" address 192.168.0.12\n" |
| 5365 |
" contact_groups falcot-admins\n" |
| 5366 |
" hostgroups debian-servers,ssh-servers\n" |
| 5367 |
"}\n" |
| 5368 |
"\n" |
| 5369 |
"# 'check_ftp' command with custom parameters\n" |
| 5370 |
"define command{\n" |
| 5371 |
" command_name check_ftp2\n" |
| 5372 |
" command_line /usr/lib/nagios/plugins/check_ftp -H $HOSTADDRESS$ -w 20 -c 30 -t 35\n" |
| 5373 |
"}\n" |
| 5374 |
"\n" |
| 5375 |
"# Generic Falcot service\n" |
| 5376 |
"define service{\n" |
| 5377 |
" name falcot-service\n" |
| 5378 |
" use generic-service\n" |
| 5379 |
" contact_groups falcot-admins\n" |
| 5380 |
" register 0\n" |
| 5381 |
"}\n" |
| 5382 |
"\n" |
| 5383 |
"# Services to check on www-host\n" |
| 5384 |
"define service{\n" |
| 5385 |
" use falcot-service\n" |
| 5386 |
" host_name www-host\n" |
| 5387 |
" service_description HTTP\n" |
| 5388 |
" check_command check_http\n" |
| 5389 |
"}\n" |
| 5390 |
"define service{\n" |
| 5391 |
" use falcot-service\n" |
| 5392 |
" host_name www-host\n" |
| 5393 |
" service_description HTTPS\n" |
| 5394 |
" check_command check_https\n" |
| 5395 |
"}\n" |
| 5396 |
"define service{\n" |
| 5397 |
" use falcot-service\n" |
| 5398 |
" host_name www-host\n" |
| 5399 |
" service_description SMTP\n" |
| 5400 |
" check_command check_smtp\n" |
| 5401 |
"}\n" |
| 5402 |
"\n" |
| 5403 |
"# Services to check on ftp-host\n" |
| 5404 |
"define service{\n" |
| 5405 |
" use falcot-service\n" |
| 5406 |
" host_name ftp-host\n" |
| 5407 |
" service_description FTP\n" |
| 5408 |
" check_command check_ftp2\n" |
| 5409 |
"}" |
| 5410 |
msgstr "" |
| 5411 |
"define contact{\n" |
| 5412 |
" name generic-contact\n" |
| 5413 |
" service_notification_period 24x7\n" |
| 5414 |
" host_notification_period 24x7\n" |
| 5415 |
" service_notification_options w,u,c,r\n" |
| 5416 |
" host_notification_options d,u,r\n" |
| 5417 |
" service_notification_commands notify-service-by-email\n" |
| 5418 |
" host_notification_commands notify-host-by-email\n" |
| 5419 |
" register 0 ; Template only\n" |
| 5420 |
"}\n" |
| 5421 |
"define contact{\n" |
| 5422 |
" use generic-contact\n" |
| 5423 |
" contact_name rhertzog\n" |
| 5424 |
" alias Raphael Hertzog\n" |
| 5425 |
" email [email protected]\n" |
| 5426 |
"}\n" |
| 5427 |
"define contact{\n" |
| 5428 |
" use generic-contact\n" |
| 5429 |
" contact_name rmas\n" |
| 5430 |
" alias Roland Mas\n" |
| 5431 |
" email [email protected]\n" |
| 5432 |
"}\n" |
| 5433 |
"\n" |
| 5434 |
"define contactgroup{\n" |
| 5435 |
" contactgroup_name falcot-admins\n" |
| 5436 |
" alias Falcot Administrators\n" |
| 5437 |
" members rhertzog,rmas\n" |
| 5438 |
"}\n" |
| 5439 |
"\n" |
| 5440 |
"define host{\n" |
| 5441 |
" use generic-host ; Name of host template to use\n" |
| 5442 |
" host_name www-host\n" |
| 5443 |
" alias www.falcot.com\n" |
| 5444 |
" address 192.168.0.5\n" |
| 5445 |
" contact_groups falcot-admins\n" |
| 5446 |
" hostgroups debian-servers,ssh-servers\n" |
| 5447 |
"}\n" |
| 5448 |
"define host{\n" |
| 5449 |
" use generic-host ; Name of host template to use\n" |
| 5450 |
" host_name ftp-host\n" |
| 5451 |
" alias ftp.falcot.com\n" |
| 5452 |
" address 192.168.0.6\n" |
| 5453 |
" contact_groups falcot-admins\n" |
| 5454 |
" hostgroups debian-servers,ssh-servers\n" |
| 5455 |
"}\n" |
| 5456 |
"\n" |
| 5457 |
"# 'check_ftp' コマンドにカスタムパラメータを渡します\n" |
| 5458 |
"define command{\n" |
| 5459 |
" command_name check_ftp2\n" |
| 5460 |
" command_line /usr/lib/nagios/plugins/check_ftp -H $HOSTADDRESS$ -w 20 -c 30 -t 35\n" |
| 5461 |
"}\n" |
| 5462 |
"\n" |
| 5463 |
"# Falcot の運用する一般サービスを定義します\n" |
| 5464 |
"define service{\n" |
| 5465 |
" name falcot-service\n" |
| 5466 |
" use generic-service\n" |
| 5467 |
" contact_groups falcot-admins\n" |
| 5468 |
" register 0\n" |
| 5469 |
"}\n" |
| 5470 |
"\n" |
| 5471 |
"# www-host 上の監視対象サービスを定義します\n" |
| 5472 |
"define service{\n" |
| 5473 |
" use falcot-service\n" |
| 5474 |
" host_name www-host\n" |
| 5475 |
" service_description HTTP\n" |
| 5476 |
" check_command check_http\n" |
| 5477 |
"}\n" |
| 5478 |
"define service{\n" |
| 5479 |
" use falcot-service\n" |
| 5480 |
" host_name www-host\n" |
| 5481 |
" service_description HTTPS\n" |
| 5482 |
" check_command check_https\n" |
| 5483 |
"}\n" |
| 5484 |
"define service{\n" |
| 5485 |
" use falcot-service\n" |
| 5486 |
" host_name www-host\n" |
| 5487 |
" service_description SMTP\n" |
| 5488 |
" check_command check_smtp\n" |
| 5489 |
"}\n" |
| 5490 |
"\n" |
| 5491 |
"# ftp-host 上の監視対象サービスを定義します\n" |
| 5492 |
"define service{\n" |
| 5493 |
" use falcot-service\n" |
| 5494 |
" host_name ftp-host\n" |
| 5495 |
" service_description FTP\n" |
| 5496 |
" check_command check_ftp2\n" |
| 5497 |
"}" |
| 5498 |
|
| 5499 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5500 |
#, fuzzy |
| 5501 |
#| msgid "This configuration file describes two monitored hosts. The first one is the web server, and the checks are made on the HTTP (80) and secure-HTTP (443) ports. Nagios also checks that an SMTP server runs on port 25. The second host is the FTP server, and the check includes making sure that a reply comes within 20 seconds. Beyond this delay, a <emphasis>warning</emphasis> is emitted; beyond 30 seconds, the alert is deemed critical. The Nagios web interface also shows that the SSH service is monitored: this comes from the hosts belonging to the <literal>ssh-servers</literal> hostgroup. The matching standard service is defined in <filename>/etc/nagios3/conf.d/services_nagios2.cfg</filename>." |
| 5502 |
msgid "This configuration file describes two monitored hosts. The first one is the web server, and the checks are made on the HTTP (80) and secure-HTTP (443) ports. Nagios also checks that an SMTP server runs on port 25. The second host is the FTP server, and the check includes making sure that a reply comes within 20 seconds. Beyond this delay, a <emphasis>warning</emphasis> is emitted; beyond 30 seconds, the alert is deemed critical. The Nagios web interface also shows that the SSH service is monitored: this comes from the hosts belonging to the <literal>ssh-servers</literal> hostgroup. The matching standard service is defined in <filename>/etc/nagios4/conf.d/services_nagios2.cfg</filename>." |
| 5503 |
msgstr "この設定ファイルでは、2 種類の監視対象ホストが定義されています。1 番目のホストはウェブサーバです。Nagios はこのホストに対してウェブサーバが HTTP (80) とセキュア HTTP (443) ポートで稼働していること、SMTP サーバがポート 25 番で稼働していることを確認します。2 番目のホストは FTP サーバです。Nagios はこのホストに対して応答が 20 秒以内に返されることが保証されることを確認します。Nagios は FTP サーバからの応答にかかる時間が 20 秒より長い場合に<emphasis>警告</emphasis>を、30 秒より長い場合に危機的な警告を発します。Nagios のウェブインターフェースは SSH サービスが監視されていることを示しています。すなわちこれは <literal>ssh-servers</literal> ホストグループに所属するホストの情報です。標準的なサービスの稼動状態確認は <filename>/etc/nagios3/conf.d/services_nagios2.cfg</filename> で定義されています。" |
| 5504 |
|
| 5505 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5506 |
msgid "Note the use of inheritance: an object is made to inherit from another object with the “use <replaceable>parent-name</replaceable>”. The parent object must be identifiable, which requires giving it a “name <replaceable>identifier</replaceable>” property. If the parent object is not meant to be a real object, but only to serve as a parent, giving it a “register 0” property tells Nagios not to consider it, and therefore to ignore the lack of some parameters that would otherwise be required." |
| 5507 |
msgstr "継承の使い方に注意してください。具体的に言えば、オブジェクトを継承するには「use <replaceable>parent-name</replaceable>」の形で親オブジェクトの名前を指定します。親オブジェクトは識別可能でなければいけません。つまり、親オブジェクトに「name <replaceable>identifier</replaceable>」属性を与える必要があります。親オブジェクトが真のオブジェクトでなく、属性継承の機能を担うだけの場合、このオブジェクトに「register 0」属性を与えます。こうすることで Nagios はこのオブジェクトを考慮しなくなり、真のオブジェクトならば必須とされるいくつかのパラメータが欠けていてもその問題を無視するようになります。" |
| 5508 |
|
| 5509 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5510 |
msgid "<emphasis>DOCUMENTATION</emphasis> List of object properties" |
| 5511 |
msgstr "<emphasis>DOCUMENTATION</emphasis> オブジェクト属性のリスト" |
| 5512 |
|
| 5513 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5514 |
#, fuzzy |
| 5515 |
#| msgid "A more in-depth understanding of the various ways in which Nagios can be configured can be obtained from the documentation provided by the <emphasis role=\"pkg\">nagios3-doc</emphasis> package. This documentation is directly accessible from the web interface, with the “Documentation” link in the top left corner. It includes a list of all object types, with all the properties they can have. It also explains how to create new plugins." |
| 5516 |
msgid "A more in-depth understanding of the various ways in which Nagios can be configured can be obtained from the documentation hosted on <ulink url=\"https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/\" />. It includes a list of all object types, with all the properties they can have. It also explains how to create new plugins." |
| 5517 |
msgstr "Nagios を設定するさまざまな方法に関してより深い理解を得るには、<emphasis role=\"pkg\">nagios3-doc</emphasis> パッケージに含まれる文書を読むと良いでしょう。この文書はウェブインターフェースの左上にある「Documentation」リンクから直接的に利用できます。この文書には、すべてのオブジェクト型のリストと各オブジェクトの取りうるすべての属性が説明されています。さらに、新しいプラグインの作り方も説明されています。" |
| 5518 |
|
| 5519 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5520 |
msgid "<emphasis>GOING FURTHER</emphasis> Remote tests with NRPE" |
| 5521 |
msgstr "<emphasis>GOING FURTHER</emphasis> NRPE を使ったリモートマシンの状態検査" |
| 5522 |
|
| 5523 |
msgid "<primary>Nagios Remote Plugin Executor</primary><see>NRPE</see>" |
| 5524 |
msgstr "" |
| 5525 |
|
| 5526 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5527 |
#, fuzzy |
| 5528 |
#| msgid "<primary>RAID</primary>" |
| 5529 |
msgid "<primary>NRPE</primary>" |
| 5530 |
msgstr "<primary>RAID</primary>" |
| 5531 |
|
| 5532 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5533 |
#, fuzzy |
| 5534 |
#| msgid "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 5535 |
msgid "<primary>Nagios</primary><secondary><emphasis role=\"pkg\">nagios-nrpe-plugin</emphasis></secondary>" |
| 5536 |
msgstr "<primary><emphasis role=\"pkg\">virtinst</emphasis></primary>" |
| 5537 |
|
| 5538 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5539 |
#, fuzzy |
| 5540 |
#| msgid "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 5541 |
msgid "<primary>Nagios</primary><secondary><emphasis role=\"pkg\">nagios-nrpe-server</emphasis></secondary>" |
| 5542 |
msgstr "<primary><emphasis role=\"pkg\">virt-manager</emphasis></primary>" |
| 5543 |
|
| 5544 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5545 |
#, fuzzy |
| 5546 |
#| msgid "<primary>installation</primary><secondary>automated installation</secondary>" |
| 5547 |
msgid "<primary>Nagios</primary><secondary><filename>/etc/nagios/nrpe.cfg</filename></secondary>" |
| 5548 |
msgstr "<primary>インストール</primary><secondary sortas=\"ジドウインストール\">自動インストール</secondary>" |
| 5549 |
|
| 5550 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5551 |
#, fuzzy |
| 5552 |
#| msgid "<primary><command>xe</command></primary>" |
| 5553 |
msgid "<primary><command>check_nrpe</command></primary>" |
| 5554 |
msgstr "<primary><command>xe</command></primary>" |
| 5555 |
|
| 5556 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5557 |
#, fuzzy |
| 5558 |
#| msgid "Many Nagios plugins allow checking some parameters local to a host; if many machines need these checks while a central installation gathers them, the NRPE (<emphasis>Nagios Remote Plugin Executor</emphasis>) plugin needs to be deployed. The <emphasis role=\"pkg\">nagios-nrpe-plugin</emphasis> package needs to be installed on the Nagios server, and <emphasis role=\"pkg\">nagios-nrpe-server</emphasis> on the hosts where local tests need to run. The latter gets its configuration from <filename>/etc/nagios/nrpe.cfg</filename>. This file should list the tests that can be started remotely, and the IP addresses of the machines allowed to trigger them. On the Nagios side, enabling these remote tests is a simple matter of adding matching services using the new <emphasis>check_nrpe</emphasis> command." |
| 5559 |
msgid "Many Nagios plugins allow checking some parameters local to a host; if many machines need these checks while a central installation gathers them, the NRPE (<emphasis>Nagios Remote Plugin Executor</emphasis>) plugin needs to be deployed. The <emphasis role=\"pkg\">nagios-nrpe-plugin</emphasis> package needs to be installed on the Nagios server, and <emphasis role=\"pkg\">nagios-nrpe-server</emphasis> on the hosts where local tests need to run. The latter gets its configuration from <filename>/etc/nagios/nrpe.cfg</filename>. This file should list the tests that can be started remotely, and the IP addresses of the machines allowed to trigger them. On the Nagios side, enabling these remote tests is a simple matter of adding matching services using the new <command>check_nrpe</command> command." |
| 5560 |
msgstr "多くの Nagios プラグインでは、あるホストに固有のいくつかのパラメータを確認することが可能です。多くのマシンに対するパラメータの確認が必要にも関わらず Nagios サーバでパラメータを収集する場合、NRPE (<emphasis>Nagios Remote Plugin Executor</emphasis>) プラグインを配備する必要があります。Nagios サーバには <emphasis role=\"pkg\">nagios-nrpe-plugin</emphasis> パッケージをインストールし、ローカルでテストを実行するホストに <emphasis role=\"pkg\">nagios-nrpe-server</emphasis> をインストールする必要があります。<emphasis role=\"pkg\">nagios-nrpe-server</emphasis> は <filename>/etc/nagios/nrpe.cfg</filename> から設定を取得します。このファイルには、リモートからの命令に従って実行されるテストとリモートからのテスト開始命令を受け入れるマシンの IP アドレスをリストするべきです。Nagios サーバ側でリモートテストを有効化するには、<emphasis>check_nrpe</emphasis> コマンドを使って一致するサービスを追加するだけで済みます。" |
| 5561 |
|
| 5562 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5563 |
#~ msgid "<primary><emphasis>VMWare</emphasis></primary>" |
| 5564 |
#~ msgstr "<primary><emphasis>VMWare</emphasis></primary>" |
| 5565 |
|
| 5566 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5567 |
#~ msgid "<primary><emphasis>Bochs</emphasis></primary>" |
| 5568 |
#~ msgstr "<primary><emphasis>Bochs</emphasis></primary>" |
| 5569 |
|
| 5570 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5571 |
#~ msgid "<primary><emphasis>QEMU</emphasis></primary>" |
| 5572 |
#~ msgstr "<primary><emphasis>QEMU</emphasis></primary>" |
| 5573 |
|
| 5574 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5575 |
#~ msgid "<primary><emphasis>KVM</emphasis></primary>" |
| 5576 |
#~ msgstr "<primary><emphasis>KVM</emphasis></primary>" |
| 5577 |
|
| 5578 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5579 |
#~ msgid "<primary><emphasis>LXC</emphasis></primary>" |
| 5580 |
#~ msgstr "<primary><emphasis>LXC</emphasis></primary>" |
| 5581 |
|
| 5582 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5583 |
# Tag: L-CFMD; |
| 5584 |
#~ msgid "<emphasis>DOCUMENTATION</emphasis> <command>xl</command> options" |
| 5585 |
#~ msgstr "<emphasis>DOCUMENTATION</emphasis> <command>xl</command> のオプション" |
| 5586 |
|
| 5587 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5588 |
#~ msgid "" |
| 5589 |
#~ "#auto eth0\n" |
| 5590 |
#~ "#iface eth0 inet dhcp\n" |
| 5591 |
#~ "\n" |
| 5592 |
#~ "auto br0\n" |
| 5593 |
#~ "iface br0 inet dhcp\n" |
| 5594 |
#~ " bridge-ports eth0" |
| 5595 |
#~ msgstr "" |
| 5596 |
#~ "#auto eth0\n" |
| 5597 |
#~ "#iface eth0 inet dhcp\n" |
| 5598 |
#~ "\n" |
| 5599 |
#~ "auto br0\n" |
| 5600 |
#~ "iface br0 inet dhcp\n" |
| 5601 |
#~ " bridge_ports eth0" |
| 5602 |
|
| 5603 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5604 |
#~ msgid "The newly-created filesystem now contains a minimal Debian system, and by default the container has no network interface (besides the loopback one). Since this is not really wanted, we will edit the container's configuration file (<filename>/var/lib/lxc/testlxc/config</filename>) and add a few <literal>lxc.network.*</literal> entries:" |
| 5605 |
#~ msgstr "これで、新規に作成されたファイルシステムが最低限の Debian システムを含むようになりました。デフォルト状態だとこのコンテナにはネットワークインターフェースがありません (ループバックインターフェースすらありません)。これは全く望むべき状態ではないため、コンテナの設定ファイル (<filename>/var/lib/lxc/testlxc/config</filename>) を編集し、いくつかの <literal>lxc.network.*</literal> エントリを追加します。" |
| 5606 |
|
| 5607 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5608 |
#~ msgid "copy the preseed file to <filename>/media/usbdisk/preseed.cfg</filename>" |
| 5609 |
#~ msgstr "<filename>/media/usbdisk/preseed.cfg</filename> に preseed ファイルをコピーします" |
| 5610 |
|
| 5611 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5612 |
#~ msgid "<primary>simple-cdd</primary>" |
| 5613 |
#~ msgstr "<primary>simple-cdd</primary>" |
| 5614 |
|
| 5615 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5616 |
# Tag: L-CFMD; |
| 5617 |
#~ msgid "" |
| 5618 |
#~ "<computeroutput># </computeroutput><userinput>mv /etc/grub.d/20_linux_xen /etc/grub.d/09_linux_xen\n" |
| 5619 |
#~ "</userinput><computeroutput># </computeroutput><userinput>update-grub\n" |
| 5620 |
#~ "</userinput>" |
| 5621 |
#~ msgstr "" |
| 5622 |
#~ "<computeroutput># </computeroutput><userinput>mv /etc/grub.d/20_linux_xen /etc/grub.d/09_linux_xen\n" |
| 5623 |
#~ "</userinput><computeroutput># </computeroutput><userinput>update-grub\n" |
| 5624 |
#~ "</userinput>" |
| 5625 |
|
| 5626 |
# Checked-By: Ryuunosuke Ayanokouzi; |
| 5627 |
#~ msgid "The first step in setting up Nagios is to install the <emphasis role=\"pkg\">nagios3</emphasis>, <emphasis role=\"pkg\">nagios-plugins</emphasis> and <emphasis role=\"pkg\">nagios3-doc</emphasis> packages. Installing the packages configures the web interface and creates a first <literal>nagiosadmin</literal> user (for which it asks for a password). Adding other users is a simple matter of inserting them in the <filename>/etc/nagios3/htpasswd.users</filename> file with Apache's <command>htpasswd</command> command. If no Debconf question was displayed during installation, <command>dpkg-reconfigure nagios3-cgi</command> can be used to define the <literal>nagiosadmin</literal> password." |
| 5628 |
#~ msgstr "Nagios をセットアップするには、最初に <emphasis role=\"pkg\">nagios3</emphasis>、<emphasis role=\"pkg\">nagios-plugins</emphasis>、<emphasis role=\"pkg\">nagios3-doc</emphasis> パッケージをインストールします。これらのパッケージをインストールするとウェブインターフェースが設定され、最初の <literal>nagiosadmin</literal> ユーザが作成されます (このユーザのパスワードが尋ねられます)。他のユーザを追加するには、Apache の <command>htpasswd</command> コマンドを使ってユーザを <filename>/etc/nagios3/htpasswd.users</filename> ファイルに追加するだけです。Debconf 質問がインストール中に表示されない場合、<command>dpkg-reconfigure nagios3-cgi</command> を使って <literal>nagiosadmin</literal> のパスワードを定義することも可能です。" |
| 5629 |
|
| 5630 |
#~ msgid "the <emphasis role=\"distribution\">Jessie</emphasis> standard kernel does not allow limiting the amount of memory available to a container; the feature exists, and is built in the kernel, but it is disabled by default because it has a (slight) cost on overall system performance; however, enabling it is a simple matter of setting the <command>cgroup_enable=memory</command> kernel command-line option at boot time;" |
| 5631 |
#~ msgstr "<emphasis role=\"distribution\">Jessie</emphasis> の標準的なカーネルはコンテナに対して利用を許可するメモリサイズを制限できません。この機能は存在し、カーネルに組み込まれていますが、デフォルトでは無効化されています。なぜなら、システム全体の性能に (わずかな) 影響をおよぼすからです。しかしながら、この機能を有効化することは簡単で、<command>cgroup_enable=memory</command> カーネルコマンドラインオプションを起動時に設定するだけです。" |
| 5632 |
|
| 5633 |
#~ msgid "The procedure requires setting up a <filename>yum.conf</filename> file containing the necessary parameters, including the path to the source RPM repositories, the path to the plugin configuration, and the destination folder. For this example, we will assume that the environment will be stored in <filename>/var/tmp/yum-bootstrap</filename>. The file <filename>/var/tmp/yum-bootstrap/yum.conf</filename> file should look like this:" |
| 5634 |
#~ msgstr "この手順の中で、必要なパラメータを含む <filename>yum.conf</filename> ファイルを設定する必要があります。<filename>yum.conf</filename> ファイルには、ソース RPM リポジトリへのパス、プラグイン設定のパス、宛先フォルダが含まれます。以下の例では、環境を <filename>/var/tmp/yum-bootstrap</filename> に保存することを仮定しています。<filename>/var/tmp/yum-bootstrap/yum.conf</filename> ファイルは以下のようになります。" |
| 5635 |
|
| 5636 |
#~ msgid "The <filename>/var/tmp/yum-bootstrap/repos.d</filename> directory should contain the descriptions of the RPM source repositories in <filename>*.repo</filename> files, just as in <filename>/etc/yum.repos.d</filename> in an already installed RPM-based system. Here is an example for a CentOS 6 installation:" |
| 5637 |
#~ msgstr "<filename>/var/tmp/yum-bootstrap/repos.d</filename> ディレクトリには、RPM ソースリポジトリを示した <filename>*.repo</filename> ファイルを含めるべきです。このファイルはインストール済みの RPM に基づくシステムの <filename>/etc/yum.repos.d</filename> にあるものとよく似ています。以下は CentOS 6 のインストールに使うファイルの例です。" |
| 5638 |
|
| 5639 |
#~ msgid "Finally, <filename>pluginconf.d/installonlyn.conf</filename> file should contain the following:" |
| 5640 |
#~ msgstr "最後に、<filename>pluginconf.d/installonlyn.conf</filename> ファイルは以下の内容を含みます。" |
| 5641 |
|
| 5642 |
#~ msgid "Once all this is setup, make sure the <command>rpm</command> databases are correctly initialized, with a command such as <command>rpm --rebuilddb</command>. An installation of CentOS 6 is then a matter of the following:" |
| 5643 |
#~ msgstr "これらの設定が済んだら、<command>rpm --rebuilddb</command> などのコマンドを使って、<command>rpm</command> データベースが正しく初期化されることを確認してください。CentOS 6 をインストールするには以下のコマンドを使うだけです。" |
| 5644 |
|
| 5645 |
#~ msgid "<userinput>yum -c /var/tmp/yum-bootstrap/yum.conf -y install coreutils basesystem centos-release yum-basearchonly initscripts</userinput>" |
| 5646 |
#~ msgstr "<userinput>yum -c /var/tmp/yum-bootstrap/yum.conf -y install coreutils basesystem centos-release yum-basearchonly initscripts</userinput>" |
| 5647 |
|
| 5648 |
#~ msgid "Xen is currently only available for the i386 and amd64 architectures. Moreover, it uses processor instructions that haven't always been provided in all i386-class computers. Note that most of the Pentium-class (or better) processors made after 2001 will work, so this restriction won't apply to very many situations." |
| 5649 |
#~ msgstr "現在のところ、Xen を利用できるのは i386 と amd64 アーキテクチャだけです。加えて、Xen はすべての i386 型コンピュータで提供されていないプロセッサ命令を使います。2001 年以降に作られたほとんどの Pentium 級 (またはそれよりも良い) プロセッサは Xen を動作させることが可能です。このため、ほとんどの場合この制限はないものと思って差し支えありません。" |
| 5650 |
|
| 5651 |
#~ msgid "<filename>/sys/fs/cgroup</filename> will then be mounted automatically at boot time; if no immediate reboot is planned, the filesystem should be manually mounted with <command>mount /sys/fs/cgroup</command>." |
| 5652 |
#~ msgstr "これで <filename>/sys/fs/cgroup</filename> は起動時に自動的にマウントされます。一方で、すぐに再起動できない場合、<command>mount /sys/fs/cgroup</command> を使ってファイルシステムを手作業でマウントします。" |
| 5653 |
|
| 5654 |
#~ msgid "The <emphasis role=\"pkg\">lxc</emphasis> package contains an initialization script that can automatically start one or several containers when the host boots; its configuration file, <filename>/etc/default/lxc</filename>, is relatively straightforward; note that the container configuration files need to be stored in <filename>/etc/lxc/auto/</filename>; many users may prefer symbolic links, such as can be created with <command>ln -s /var/lib/lxc/testlxc/config /etc/lxc/auto/testlxc.config</command>." |
| 5655 |
#~ msgstr "<emphasis role=\"pkg\">lxc</emphasis> パッケージには、ホストの起動時に自動的に 1 つまたは複数のコンテナを開始するための初期化スクリプトが含まれます。そして、初期化スクリプトの設定ファイルは <filename>/etc/default/lxc</filename> で、比較的分かりやすいものです。さらに、コンテナの設定ファイルは <filename>/etc/lxc/auto/</filename> に保存しなければいけない点に注意してください。また、多くのユーザは実際の設定ファイルへのシンボリックリンクを <filename>/etc/lxc/auto/</filename> に保存する方法を選びます。シンボリックリンクを作成するには <command>ln -s /var/lib/lxc/testlxc/config /etc/lxc/auto/testlxc.config</command> を使います。" |
| 5656 |
|
| 5657 |
#~ msgid "<emphasis>BEWARE</emphasis> Bugs in default <literal>debian</literal> template" |
| 5658 |
#~ msgstr "<emphasis>BEWARE</emphasis> デフォルトの <literal>debian</literal> テンプレートに含まれるバグ" |
| 5659 |
|
| 5660 |
#~ msgid "The <command>/usr/share/lxc/templates/lxc-debian</command> template creation script provided in the initial <emphasis role=\"distribution\">Wheezy</emphasis> package (aka <emphasis role=\"pkg\">lxc</emphasis> 0.8.0~rc1-8+deb7u1) suffers from numerous problems. The most important one is that it relies on the <command>live-debconfig</command> program which is not available in <emphasis role=\"distribution\">Wheezy</emphasis> but only in newer versions of Debian. <ulink type=\"block\" url=\"http://bugs.debian.org/680469\" /> <ulink type=\"block\" url=\"http://bugs.debian.org/686747\" />" |
| 5661 |
#~ msgstr "最初の <emphasis role=\"distribution\">Wheezy</emphasis> パッケージ (別名 <emphasis role=\"pkg\">lxc</emphasis> 0.8.0~rc1-8+deb7u1) に含まれていた <command>/usr/share/lxc/templates/lxc-debian</command> テンプレートを作成するスクリプトは数多くの問題を抱えていました。最も重要な問題は <command>live-debconfig</command> プログラムに頼っていたにも関わらず <emphasis role=\"distribution\">Wheezy</emphasis> ではこのプログラムが利用できなかった点です。<command>live-debconfig</command> プログラムは Debian のより新しいバージョンで利用できるようになりました。<ulink type=\"block\" url=\"http://bugs.debian.org/680469\" /><ulink type=\"block\" url=\"http://bugs.debian.org/686747\" />" |
| 5662 |
|
| 5663 |
#~ msgid "At the time of writing, there was no good solution and no usable work-around, except to use an alternate template creation script. Further updates of lxc might fix this though. This section assumes that <command>/usr/share/lxc/templates/lxc-debian</command> matches the upstream provided script: <ulink type=\"block\" url=\"https://github.com/lxc/lxc/raw/master/templates/lxc-debian.in\" />" |
| 5664 |
#~ msgstr "執筆時点で、別のテンプレート作成スクリプトを使う以外に良い解決策はありませんし、利用できる次善策もありません。lxc の今後の更新によりこの問題が修正されるかもしれません。この節では <command>/usr/share/lxc/templates/lxc-debian</command> と上流開発から提供されるスクリプトとが一致することを仮定します。<ulink type=\"block\" url=\"https://github.com/lxc/lxc/raw/master/templates/lxc-debian.in\" />" |