http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/fr/LC_MESSAGES/storage.po ---------------------------------------------------------------------- diff --git a/source/locale/fr/LC_MESSAGES/storage.po b/source/locale/fr/LC_MESSAGES/storage.po new file mode 100644 index 0000000..4f757b6 --- /dev/null +++ b/source/locale/fr/LC_MESSAGES/storage.po @@ -0,0 +1,1267 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: Apache CloudStack Administration RTD\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2016-08-22 13:55+0200\n" +"PO-Revision-Date: 2016-12-19 18:59+0100\n" +"Language-Team: French (http://www.transifex.com/ke4qqq/apache-cloudstack-"; +"administration-rtd/language/fr/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 2.3.4\n" +"Last-Translator: \n" +"Language: fr\n" +"X-Generator: Poedit 1.8.11\n" + +#: ../../storage.rst:18 +msgid "Working with Storage" +msgstr "Travailler avec le stockage" + +#: ../../storage.rst:21 +msgid "Storage Overview" +msgstr "Vue d'ensemble du stockage" + +#: ../../storage.rst:23 +msgid "" +"CloudStack defines two types of storage: primary and secondary. Primary " +"storage can be accessed by either iSCSI or NFS. Additionally, direct " +"attached storage may be used for primary storage. Secondary storage is " +"always accessed using NFS." +msgstr "" +"CloudStack définit 2 types de stockage : primaire et secondaire. Le stockage " +"primaire peut être accédé soit en iSCSI ou en NFS. En complément, le " +"stockage directement attaché (DAS) peut être utilisé comme stockage " +"primaire. Le stockage secondaire est toujours accédé en utilisant NFS." + +#: ../../storage.rst:28 +msgid "" +"There is no ephemeral storage in CloudStack. All volumes on all nodes are " +"persistent." +msgstr "" +"Il n'y a pas de stockage éphémère dans CloudStack. Tous les volumes sur tous " +"les noeuds sont persistents." + +#: ../../storage.rst:33 +msgid "Primary Storage" +msgstr "Stockage primaire" + +#: ../../storage.rst:35 +msgid "" +"This section gives concepts and technical details about CloudStack primary " +"storage. For information about how to install and configure primary storage " +"through the CloudStack UI, see the Installation Guide." +msgstr "" +"Cette section donne les concepts et les détails techniques sur le stockage " +"primaire de CloudStack. Pour des informations sur la façon d'installer et de " +"configurer le stockage primaire par l'interface CloudStack, consultez le " +"guide d'installation." + +#: ../../storage.rst:39 +msgid "" +"`âAbout Primary Storageâ <http://docs.cloudstack.apache.org/en/latest/"; +"concepts.html#about-primary-storage>`_" +msgstr "" +"`âA propos du stockage primaireâ <http://docs.cloudstack.apache.org/en/"; +"latest/concepts.html#about-primary-storage>`_" + +#: ../../storage.rst:43 +msgid "Best Practices for Primary Storage" +msgstr "Meilleurs pratiques pour le stockage primaire" + +#: ../../storage.rst:45 +msgid "" +"The speed of primary storage will impact guest performance. If possible, " +"choose smaller, higher RPM drives or SSDs for primary storage." +msgstr "" +"La vitesse du stockage primaire va impacter les performances des invités. Si " +"possible, choisissez des disques plus petits, avec des RPM plus élevés ou " +"des disques SSD pour le stockage primaire." + +#: ../../storage.rst:49 +msgid "There are two ways CloudStack can leverage primary storage:" +msgstr "Il y a deux façons pour CloudStack d'exploiter le stockage primaire :" + +#: ../../storage.rst:51 +msgid "" +"Static: This is CloudStack's traditional way of handling storage. In this " +"model, a preallocated amount of storage (ex. a volume from a SAN) is given " +"to CloudStack. CloudStack then permits many of its volumes to be created on " +"this storage (can be root and/or data disks). If using this technique, " +"ensure that nothing is stored on the storage. Adding the storage to " +"CloudStack will destroy any existing data." +msgstr "" + +#: ../../storage.rst:59 +msgid "" +"Dynamic: This is a newer way for CloudStack to manage storage. In this " +"model, a storage system (rather than a preallocated amount of storage) is " +"given to CloudStack. CloudStack, working in concert with a storage plug-in, " +"dynamically creates volumes on the storage system and each volume on the " +"storage system maps to a single CloudStack volume. This is highly useful for " +"features such as storage Quality of Service. Currently this feature is " +"supported for data disks (Disk Offerings)." +msgstr "" + +#: ../../storage.rst:70 +msgid "Runtime Behavior of Primary Storage" +msgstr "Comportement à l'exécution du stockage primaire" + +#: ../../storage.rst:72 +msgid "" +"Root volumes are created automatically when a virtual machine is created. " +"Root volumes are deleted when the VM is destroyed. Data volumes can be " +"created and dynamically attached to VMs. Data volumes are not deleted when " +"VMs are destroyed." +msgstr "" + +#: ../../storage.rst:77 +msgid "" +"Administrators should monitor the capacity of primary storage devices and " +"add additional primary storage as needed. See the Advanced Installation " +"Guide." +msgstr "" + +#: ../../storage.rst:81 +msgid "" +"Administrators add primary storage to the system by creating a CloudStack " +"storage pool. Each storage pool is associated with a cluster or a zone." +msgstr "" + +#: ../../storage.rst:85 +msgid "" +"With regards to data disks, when a user executes a Disk Offering to create a " +"data disk, the information is initially written to the CloudStack database " +"only. Upon the first request that the data disk be attached to a VM, " +"CloudStack determines what storage to place the volume on and space is taken " +"from that storage (either from preallocated storage or from a storage system " +"(ex. a SAN), depending on how the primary storage was added to CloudStack)." +msgstr "" + +#: ../../storage.rst:95 +msgid "Hypervisor Support for Primary Storage" +msgstr "" + +#: ../../storage.rst:97 +msgid "" +"The following table shows storage options and parameters for different " +"hypervisors." +msgstr "" + +#: ../../storage.rst:103 +msgid "Storage media \\\\ hypervisor" +msgstr "Media de stockage \\\\ hyperviseur" + +#: ../../storage.rst:103 ../../storage.rst:720 +msgid "VMware vSphere" +msgstr "VMware vSphere" + +#: ../../storage.rst:103 ../../storage.rst:720 +msgid "Citrix XenServer" +msgstr "Citrix XenServer" + +#: ../../storage.rst:103 ../../storage.rst:342 ../../storage.rst:720 +msgid "KVM" +msgstr "KVM" + +#: ../../storage.rst:103 +msgid "Hyper-V" +msgstr "Hyper-V" + +#: ../../storage.rst:105 +msgid "**Format for Disks, Templates, and Snapshots**" +msgstr "**Format des disques, des modèles et des instantanés**" + +#: ../../storage.rst:105 +msgid "VMDK" +msgstr "VMDK" + +#: ../../storage.rst:105 ../../storage.rst:340 +msgid "VHD" +msgstr "VHD" + +#: ../../storage.rst:105 ../../storage.rst:342 +msgid "QCOW2" +msgstr "QCOW2" + +#: ../../storage.rst:105 +msgid "VHD Snapshots are not supported." +msgstr "" + +#: ../../storage.rst:107 +msgid "**iSCSI support**" +msgstr "" + +#: ../../storage.rst:107 ../../storage.rst:108 +msgid "VMFS" +msgstr "VMFS" + +#: ../../storage.rst:107 +msgid "Clustered LVM" +msgstr "" + +#: ../../storage.rst:107 ../../storage.rst:108 +msgid "Yes, via Shared Mountpoint" +msgstr "Oui, par point de montage partagé" + +#: ../../storage.rst:107 ../../storage.rst:108 ../../storage.rst:109 +#: ../../storage.rst:111 ../../storage.rst:112 ../../storage.rst:113 +#: ../../storage.rst:722 +msgid "No" +msgstr "Non" + +#: ../../storage.rst:108 +msgid "**Fiber Channel support**" +msgstr "" + +#: ../../storage.rst:108 +msgid "Yes, via Existing SR" +msgstr "" + +#: ../../storage.rst:109 +msgid "**NFS support**" +msgstr "**Support NFS**" + +#: ../../storage.rst:109 ../../storage.rst:110 ../../storage.rst:112 +#: ../../storage.rst:113 ../../storage.rst:722 +msgid "Yes" +msgstr "Oui" + +#: ../../storage.rst:110 +msgid "**Local storage support**" +msgstr "" + +#: ../../storage.rst:111 +msgid "**Storage over-provisioning**" +msgstr "" + +#: ../../storage.rst:111 +msgid "NFS and iSCSI" +msgstr "NFS et iSCSI" + +#: ../../storage.rst:111 +msgid "NFS" +msgstr "NFS" + +#: ../../storage.rst:112 +msgid "**SMB/CIFS**" +msgstr "**SMB/CIFS**" + +#: ../../storage.rst:113 +msgid "**Ceph/RBD**" +msgstr "**Ceph/RBD**" + +#: ../../storage.rst:116 +msgid "" +"XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber " +"Channel volumes and does not support over-provisioning in the hypervisor. " +"The storage server itself, however, can support thin-provisioning. As a " +"result the CloudStack can still support storage over-provisioning by running " +"on thin-provisioned storage volumes." +msgstr "" + +#: ../../storage.rst:122 +msgid "" +"KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file " +"system path local to each server in a given cluster. The path must be the " +"same across all Hosts in the cluster, for example /mnt/primary1. This shared " +"mountpoint is assumed to be a clustered filesystem such as OCFS2. In this " +"case the CloudStack does not attempt to mount or unmount the storage as is " +"done with NFS. The CloudStack requires that the administrator insure that " +"the storage is available" +msgstr "" + +#: ../../storage.rst:130 +msgid "" +"With NFS storage, CloudStack manages the overprovisioning. In this case the " +"global configuration parameter storage.overprovisioning.factor controls the " +"degree of overprovisioning. This is independent of hypervisor type." +msgstr "" + +#: ../../storage.rst:135 +msgid "" +"Local storage is an option for primary storage for vSphere, XenServer, and " +"KVM. When the local disk option is enabled, a local disk storage pool is " +"automatically created on each host. To use local storage for the System " +"Virtual Machines (such as the Virtual Router), set system.vm.use.local." +"storage to true in global configuration." +msgstr "" + +#: ../../storage.rst:141 +msgid "" +"CloudStack supports multiple primary storage pools in a Cluster. For " +"example, you could provision 2 NFS servers in primary storage. Or you could " +"provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the " +"first approaches capacity." +msgstr "" + +#: ../../storage.rst:148 +msgid "Storage Tags" +msgstr "" + +#: ../../storage.rst:150 +msgid "" +"Storage may be \"tagged\". A tag is a text string attribute associated with " +"primary storage, a Disk Offering, or a Service Offering. Tags allow " +"administrators to provide additional information about the storage. For " +"example, that is a \"SSD\" or it is \"slow\". Tags are not interpreted by " +"CloudStack. They are matched against tags placed on service and disk " +"offerings. CloudStack requires all tags on service and disk offerings to " +"exist on the primary storage before it allocates root or data disks on the " +"primary storage. Service and disk offering tags are used to identify the " +"requirements of the storage that those offerings have. For example, the high " +"end service offering may require \"fast\" for its root disk volume." +msgstr "" + +#: ../../storage.rst:162 +msgid "" +"The interaction between tags, allocation, and volume copying across clusters " +"and pods can be complex. To simplify the situation, use the same set of tags " +"on the primary storage for all clusters in a pod. Even if different devices " +"are used to present those tags, the set of exposed tags can be the same." +msgstr "" + +#: ../../storage.rst:170 +msgid "Maintenance Mode for Primary Storage" +msgstr "" + +#: ../../storage.rst:172 +msgid "" +"Primary storage may be placed into maintenance mode. This is useful, for " +"example, to replace faulty RAM in a storage device. Maintenance mode for a " +"storage device will first stop any new guests from being provisioned on the " +"storage device. Then it will stop all guests that have any volume on that " +"storage device. When all such guests are stopped the storage device is in " +"maintenance mode and may be shut down. When the storage device is online " +"again you may cancel maintenance mode for the device. The CloudStack will " +"bring the device back online and attempt to start all guests that were " +"running at the time of the entry into maintenance mode." +msgstr "" + +#: ../../storage.rst:185 +msgid "Secondary Storage" +msgstr "Stockage secondaire" + +#: ../../storage.rst:187 +msgid "" +"This section gives concepts and technical details about CloudStack secondary " +"storage. For information about how to install and configure secondary " +"storage through the CloudStack UI, see the Advanced Installation Guide." +msgstr "" + +#: ../../storage.rst:192 +msgid "" +"`âAbout Secondary Storageâ <http://docs.cloudstack.apache.org/en/latest/"; +"concepts.html#about-secondary-storage>`_" +msgstr "" + +#: ../../storage.rst:196 +msgid "Working With Volumes" +msgstr "" + +#: ../../storage.rst:198 +msgid "" +"A volume provides storage to a guest VM. The volume can provide for a root " +"disk or an additional data disk. CloudStack supports additional volumes for " +"guest VMs." +msgstr "" + +#: ../../storage.rst:202 +msgid "" +"Volumes are created for a specific hypervisor type. A volume that has been " +"attached to guest using one hypervisor type (e.g, XenServer) may not be " +"attached to a guest that is using another hypervisor type, for example:" +"vSphere, KVM. This is because the different hypervisors use different disk " +"image formats." +msgstr "" + +#: ../../storage.rst:208 +msgid "" +"CloudStack defines a volume as a unit of storage available to a guest VM. " +"Volumes are either root disks or data disks. The root disk has \"/\" in the " +"file system and is usually the boot device. Data disks provide for " +"additional storage, for example: \"/opt\" or \"D:\". Every guest VM has a " +"root disk, and VMs can also optionally have a data disk. End users can mount " +"multiple data disks to guest VMs. Users choose data disks from the disk " +"offerings created by administrators. The user can create a template from a " +"volume as well; this is the standard procedure for private template " +"creation. Volumes are hypervisor-specific: a volume from one hypervisor type " +"may not be used on a guest of another hypervisor type." +msgstr "" + +#: ../../storage.rst:220 +msgid "CloudStack supports attaching up to" +msgstr "" + +#: ../../storage.rst:222 +msgid "" +"13 data disks on XenServer hypervisor versions 6.0 and above, And all " +"versions of VMware." +msgstr "" + +#: ../../storage.rst:225 +msgid "64 data disks on Hyper-V." +msgstr "" + +#: ../../storage.rst:227 +msgid "6 data disks on other hypervisor types." +msgstr "" + +#: ../../storage.rst:231 +msgid "Creating a New Volume" +msgstr "" + +#: ../../storage.rst:233 +msgid "" +"You can add more data disk volumes to a guest VM at any time, up to the " +"limits of your storage capacity. Both CloudStack administrators and users " +"can add volumes to VM instances. When you create a new volume, it is stored " +"as an entity in CloudStack, but the actual storage resources are not " +"allocated on the physical storage device until you attach the volume. This " +"optimization allows the CloudStack to provision the volume nearest to the " +"guest that will use it when the first attachment is made." +msgstr "" + +#: ../../storage.rst:243 +msgid "Using Local Storage for Data Volumes" +msgstr "" + +#: ../../storage.rst:245 +msgid "" +"You can create data volumes on local storage (supported with XenServer, KVM, " +"and VMware). The data volume is placed on the same host as the VM instance " +"that is attached to the data volume. These local data volumes can be " +"attached to virtual machines, detached, re-attached, and deleted just as " +"with the other types of data volume." +msgstr "" + +#: ../../storage.rst:251 +msgid "" +"Local storage is ideal for scenarios where persistence of data volumes and " +"HA is not required. Some of the benefits include reduced disk I/O latency " +"and cost reduction from using inexpensive local disks." +msgstr "" + +#: ../../storage.rst:255 +msgid "" +"In order for local volumes to be used, the feature must be enabled for the " +"zone." +msgstr "" + +#: ../../storage.rst:258 +msgid "" +"You can create a data disk offering for local storage. When a user creates a " +"new VM, they can select this disk offering in order to cause the data disk " +"volume to be placed in local storage." +msgstr "" + +#: ../../storage.rst:262 +msgid "" +"You can not migrate a VM that has a volume in local storage to a different " +"host, nor migrate the volume itself away to a different host. If you want to " +"put a host into maintenance mode, you must first stop any VMs with local " +"data volumes on that host." +msgstr "" + +#: ../../storage.rst:269 +msgid "To Create a New Volume" +msgstr "" + +#: ../../storage.rst:271 ../../storage.rst:367 ../../storage.rst:400 +#: ../../storage.rst:466 ../../storage.rst:487 ../../storage.rst:516 +#: ../../storage.rst:572 +msgid "Log in to the CloudStack UI as a user or admin." +msgstr "" + +#: ../../storage.rst:273 ../../storage.rst:320 ../../storage.rst:574 +#: ../../storage.rst:674 +msgid "In the left navigation bar, click Storage." +msgstr "" + +#: ../../storage.rst:275 ../../storage.rst:371 ../../storage.rst:576 +msgid "In Select View, choose Volumes." +msgstr "Dans la Sélection de Vue, choisissez Volumes." + +#: ../../storage.rst:277 +msgid "" +"To create a new volume, click Add Volume, provide the following details, and " +"click OK." +msgstr "" + +#: ../../storage.rst:280 +msgid "Name. Give the volume a unique name so you can find it later." +msgstr "" + +#: ../../storage.rst:282 +msgid "" +"Availability Zone. Where do you want the storage to reside? This should be " +"close to the VM that will use the volume." +msgstr "" + +#: ../../storage.rst:285 +msgid "Disk Offering. Choose the characteristics of the storage." +msgstr "" + +#: ../../storage.rst:287 +msgid "" +"The new volume appears in the list of volumes with the state âAllocated.â " +"The volume data is stored in CloudStack, but the volume is not yet ready for " +"use" +msgstr "" + +#: ../../storage.rst:291 +msgid "To start using the volume, continue to Attaching a Volume" +msgstr "" + +#: ../../storage.rst:295 +msgid "Uploading an Existing Volume to a Virtual Machine" +msgstr "" + +#: ../../storage.rst:297 +msgid "" +"Existing data can be made accessible to a virtual machine. This is called " +"uploading a volume to the VM. For example, this is useful to upload data " +"from a local file system and attach it to a VM. Root administrators, domain " +"administrators, and end users can all upload existing volumes to VMs." +msgstr "" + +#: ../../storage.rst:303 +msgid "" +"The upload is performed using HTTP. The uploaded volume is placed in the " +"zone's secondary storage" +msgstr "" + +#: ../../storage.rst:306 +msgid "" +"You cannot upload a volume if the preconfigured volume limit has already " +"been reached. The default limit for the cloud is set in the global " +"configuration parameter max.account.volumes, but administrators can also set " +"per-domain limits that are different from the global default. See Setting " +"Usage Limits" +msgstr "" + +#: ../../storage.rst:312 +msgid "To upload a volume:" +msgstr "" + +#: ../../storage.rst:314 +msgid "" +"(Optional) Create an MD5 hash (checksum) of the disk image file that you are " +"going to upload. After uploading the data disk, CloudStack will use this " +"value to verify that no data corruption has occurred." +msgstr "" + +#: ../../storage.rst:318 +msgid "Log in to the CloudStack UI as an administrator or user" +msgstr "" + +#: ../../storage.rst:322 +msgid "Click Upload Volume." +msgstr "" + +#: ../../storage.rst:324 +msgid "Provide the following:" +msgstr "" + +#: ../../storage.rst:326 +msgid "" +"Name and Description. Any desired name and a brief description that can be " +"shown in the UI." +msgstr "" + +#: ../../storage.rst:329 +msgid "" +"Availability Zone. Choose the zone where you want to store the volume. VMs " +"running on hosts in this zone can attach the volume." +msgstr "" + +#: ../../storage.rst:332 +msgid "" +"Format. Choose one of the following to indicate the disk image format of the " +"volume." +msgstr "" + +#: ../../storage.rst:338 +msgid "Hypervisor" +msgstr "" + +#: ../../storage.rst:338 +msgid "Disk Image Format" +msgstr "" + +#: ../../storage.rst:340 +msgid "XenServer" +msgstr "" + +#: ../../storage.rst:341 +msgid "VMware" +msgstr "" + +#: ../../storage.rst:341 +msgid "OVA" +msgstr "" + +#: ../../storage.rst:345 +msgid "" +"URL. The secure HTTP or HTTPS URL that CloudStack can use to access your " +"disk. The type of file at the URL must match the value chosen in Format. For " +"example, if Format is VHD, the URL might look like the following:" +msgstr "" + +#: ../../storage.rst:350 +msgid "``http://yourFileServerIP/userdata/myDataDisk.vhd``"; +msgstr "" + +#: ../../storage.rst:352 +msgid "MD5 checksum. (Optional) Use the hash that you created in step 1." +msgstr "" + +#: ../../storage.rst:354 +msgid "" +"Wait until the status of the volume shows that the upload is complete. Click " +"Instances - Volumes, find the name you specified in step 5, and make sure " +"the status is Uploaded." +msgstr "" + +#: ../../storage.rst:360 +msgid "Attaching a Volume" +msgstr "Attacher un Volume" + +#: ../../storage.rst:362 +msgid "" +"You can attach a volume to a guest VM to provide extra disk storage. Attach " +"a volume when you first create a new volume, when you are moving an existing " +"volume from one VM to another, or after you have migrated a volume from one " +"storage pool to another." +msgstr "" +"Vous pouvez attacher un volume à une VM pour lui fournir plus d'espace " +"disque de stockage. Vous pouvez attacher un volume lors de sa création, " +"lorsque vous déplacer un volume d'une VM existante vers une autre, ou après " +"avoir migré le volume d'un groupe de stockage à un autre." + +#: ../../storage.rst:369 +msgid "In the left navigation, click Storage." +msgstr "Dans la navigation à gauche, cliquez sur Stockage." + +#: ../../storage.rst:373 +msgid "" +"Click the volume name in the Volumes list, then click the Attach Disk button " +"|AttachDiskButton.png|" +msgstr "" + +#: ../../storage.rst:376 +msgid "" +"In the Instance popup, choose the VM to which you want to attach the volume. " +"You will only see instances to which you are allowed to attach volumes; for " +"example, a user will see only instances created by that user, but the " +"administrator will have more choices." +msgstr "" +"Dans la popup d'instance, choisissez la VM sur laquelle vous désirez " +"attacher le volume. Vous ne verrez que les instances sur lesquelles vous " +"êtes autorisé à attacher le volume ; par exemple, un utilisateur ne verra " +"que ses propres instances, mais l'administrateur aura plus de choix." + +#: ../../storage.rst:381 +msgid "" +"When the volume has been attached, you should be able to see it by clicking " +"Instances, the instance name, and View Volumes." +msgstr "" +"Lorsqu'un volume a été attaché, vous devriez pouver le voir en cliquant sur " +"instances, puis le nom de l'instance et \"Voir les Volumes\"." + +#: ../../storage.rst:386 +msgid "Detaching and Moving Volumes" +msgstr "" + +#: ../../storage.rst:389 +msgid "" +"This procedure is different from moving volumes from one storage pool to " +"another as described in `âVM Storage Migrationâ <#vm-storage-migration>`_." +msgstr "" + +#: ../../storage.rst:393 +msgid "" +"A volume can be detached from a guest VM and attached to another guest. Both " +"CloudStack administrators and users can detach volumes from VMs and move " +"them to other VMs." +msgstr "" + +#: ../../storage.rst:397 +msgid "" +"If the two VMs are in different clusters, and the volume is large, it may " +"take several minutes for the volume to be moved to the new VM." +msgstr "" + +#: ../../storage.rst:402 +msgid "" +"In the left navigation bar, click Storage, and choose Volumes in Select " +"View. Alternatively, if you know which VM the volume is attached to, you can " +"click Instances, click the VM name, and click View Volumes." +msgstr "" + +#: ../../storage.rst:407 +msgid "" +"Click the name of the volume you want to detach, then click the Detach Disk " +"button. |DetachDiskButton.png|" +msgstr "" + +#: ../../storage.rst:410 +msgid "" +"To move the volume to another VM, follow the steps in `âAttaching a Volumeâ " +"<#attaching-a-volume>`_." +msgstr "" + +#: ../../storage.rst:415 +msgid "VM Storage Migration" +msgstr "" + +#: ../../storage.rst:417 +msgid "Supported in XenServer, KVM, and VMware." +msgstr "" + +#: ../../storage.rst:420 +msgid "" +"This procedure is different from moving disk volumes from one VM to another " +"as described in `âDetaching and Moving Volumesâ <#detaching-and-moving-" +"volumes>`_." +msgstr "" + +#: ../../storage.rst:424 +msgid "" +"You can migrate a virtual machineâs root disk volume or any additional data " +"disk volume from one storage pool to another in the same zone." +msgstr "" + +#: ../../storage.rst:427 +msgid "" +"You can use the storage migration feature to achieve some commonly desired " +"administration goals, such as balancing the load on storage pools and " +"increasing the reliability of virtual machines by moving them away from any " +"storage pool that is experiencing issues." +msgstr "" + +#: ../../storage.rst:432 +msgid "" +"On XenServer and VMware, live migration of VM storage is enabled through " +"CloudStack support for XenMotion and vMotion. Live storage migration allows " +"VMs to be moved from one host to another, where the VMs are not located on " +"storage shared between the two hosts. It provides the option to live migrate " +"a VMâs disks along with the VM itself. It is possible to migrate a VM from " +"one XenServer resource pool / VMware cluster to another, or to migrate a VM " +"whose disks are on local storage, or even to migrate a VMâs disks from one " +"storage repository to another, all while the VM is running." +msgstr "" + +#: ../../storage.rst:443 +msgid "" +"Because of a limitation in VMware, live migration of storage for a VM is " +"allowed only if the source and target storage pool are accessible to the " +"source host; that is, the host where the VM is running when the live " +"migration operation is requested." +msgstr "" + +#: ../../storage.rst:450 +msgid "Migrating a Data Volume to a New Storage Pool" +msgstr "" + +#: ../../storage.rst:452 +msgid "There are two situations when you might want to migrate a disk:" +msgstr "" + +#: ../../storage.rst:454 +msgid "" +"Move the disk to new storage, but leave it attached to the same running VM." +msgstr "" + +#: ../../storage.rst:457 +msgid "" +"Detach the disk from its current VM, move it to new storage, and attach it " +"to a new VM." +msgstr "" + +#: ../../storage.rst:462 +msgid "Migrating Storage For a Running VM" +msgstr "" + +#: ../../storage.rst:464 +msgid "(Supported on XenServer and VMware)" +msgstr "" + +#: ../../storage.rst:468 +msgid "" +"In the left navigation bar, click Instances, click the VM name, and click " +"View Volumes." +msgstr "" + +#: ../../storage.rst:471 +msgid "Click the volume you want to migrate." +msgstr "" + +#: ../../storage.rst:473 ../../storage.rst:489 +msgid "" +"Detach the disk from the VM. See `âDetaching and Moving Volumesâ <#detaching-" +"and-moving-volumes>`_ but skip the âreattachâ step at the end. You will do " +"that after migrating to new storage." +msgstr "" + +#: ../../storage.rst:477 ../../storage.rst:493 +msgid "" +"Click the Migrate Volume button |Migrateinstance.png| and choose the " +"destination from the dropdown list." +msgstr "" + +#: ../../storage.rst:480 +msgid "Watch for the volume status to change to Migrating, then back to Ready." +msgstr "" + +#: ../../storage.rst:485 +msgid "Migrating Storage and Attaching to a Different VM" +msgstr "" + +#: ../../storage.rst:496 +msgid "" +"Watch for the volume status to change to Migrating, then back to Ready. You " +"can find the volume by clicking Storage in the left navigation bar. Make " +"sure that Volumes is displayed at the top of the window, in the Select View " +"dropdown." +msgstr "" + +#: ../../storage.rst:501 +msgid "" +"Attach the volume to any desired VM running in the same cluster as the new " +"storage server. See `âAttaching a Volumeâ <#attaching-a-volume>`_" +msgstr "" + +#: ../../storage.rst:507 +msgid "Migrating a VM Root Volume to a New Storage Pool" +msgstr "" + +#: ../../storage.rst:509 +msgid "" +"(XenServer, VMware) You can live migrate a VM's root disk from one storage " +"pool to another, without stopping the VM first." +msgstr "" + +#: ../../storage.rst:512 +msgid "" +"(KVM) When migrating the root disk volume, the VM must first be stopped, and " +"users can not access the VM. After migration is complete, the VM can be " +"restarted." +msgstr "" + +#: ../../storage.rst:518 +msgid "In the left navigation bar, click Instances, and click the VM name." +msgstr "" + +#: ../../storage.rst:520 +msgid "(KVM only) Stop the VM." +msgstr "" + +#: ../../storage.rst:522 +msgid "" +"Click the Migrate button |Migrateinstance.png| and choose the destination " +"from the dropdown list." +msgstr "" + +#: ../../storage.rst:526 +msgid "" +"If the VM's storage has to be migrated along with the VM, this will be noted " +"in the host list. CloudStack will take care of the storage migration for you." +msgstr "" + +#: ../../storage.rst:530 +msgid "" +"Watch for the volume status to change to Migrating, then back to Running (or " +"Stopped, in the case of KVM). This can take some time." +msgstr "" + +#: ../../storage.rst:533 +msgid "(KVM only) Restart the VM." +msgstr "" + +#: ../../storage.rst:537 +msgid "Resizing Volumes" +msgstr "" + +#: ../../storage.rst:539 +msgid "" +"CloudStack provides the ability to resize data disks; CloudStack controls " +"volume size by using disk offerings. This provides CloudStack administrators " +"with the flexibility to choose how much space they want to make available to " +"the end users. Volumes within the disk offerings with the same storage tag " +"can be resized. For example, if you only want to offer 10, 50, and 100 GB " +"offerings, the allowed resize should stay within those limits. That implies " +"if you define a 10 GB, a 50 GB and a 100 GB disk offerings, a user can " +"upgrade from 10 GB to 50 GB, or 50 GB to 100 GB. If you create a custom-" +"sized disk offering, then you have the option to resize the volume by " +"specifying a new, larger size." +msgstr "" + +#: ../../storage.rst:550 +msgid "" +"Additionally, using the resizeVolume API, a data volume can be moved from a " +"static disk offering to a custom disk offering with the size specified. This " +"functionality allows those who might be billing by certain volume sizes or " +"disk offerings to stick to that model, while providing the flexibility to " +"migrate to whatever custom size necessary." +msgstr "" + +#: ../../storage.rst:556 +msgid "" +"This feature is supported on KVM, XenServer, and VMware hosts. However, " +"shrinking volumes is not supported on VMware hosts." +msgstr "" + +#: ../../storage.rst:559 +msgid "Before you try to resize a volume, consider the following:" +msgstr "" + +#: ../../storage.rst:561 +msgid "The VMs associated with the volume are stopped." +msgstr "" + +#: ../../storage.rst:563 +msgid "The data disks associated with the volume are removed." +msgstr "" + +#: ../../storage.rst:565 +msgid "" +"When a volume is shrunk, the disk associated with it is simply truncated, " +"and doing so would put its content at risk of data loss. Therefore, resize " +"any partitions or file systems before you shrink a data disk so that all the " +"data is moved off from that disk." +msgstr "" + +#: ../../storage.rst:570 +msgid "To resize a volume:" +msgstr "" + +#: ../../storage.rst:578 +msgid "" +"Select the volume name in the Volumes list, then click the Resize Volume " +"button |resize-volume-icon.png|" +msgstr "" + +#: ../../storage.rst:581 +msgid "" +"In the Resize Volume pop-up, choose desired characteristics for the storage." +msgstr "" + +#: ../../storage.rst:584 +msgid "|resize-volume.png|" +msgstr "" + +#: ../../storage.rst:586 +msgid "If you select Custom Disk, specify a custom size." +msgstr "" + +#: ../../storage.rst:588 +msgid "Click Shrink OK to confirm that you are reducing the size of a volume." +msgstr "" + +#: ../../storage.rst:591 +msgid "" +"This parameter protects against inadvertent shrinking of a disk, which might " +"lead to the risk of data loss. You must sign off that you know what you are " +"doing." +msgstr "" + +#: ../../storage.rst:595 +msgid "Click OK." +msgstr "Cliquez sur OK." + +#: ../../storage.rst:599 +msgid "Reset VM to New Root Disk on Reboot" +msgstr "" + +#: ../../storage.rst:601 +msgid "" +"You can specify that you want to discard the root disk and create a new one " +"whenever a given VM is rebooted. This is useful for secure environments that " +"need a fresh start on every boot and for desktops that should not retain " +"state. The IP address of the VM will not change due to this operation." +msgstr "" + +#: ../../storage.rst:607 +msgid "**To enable root disk reset on VM reboot:**" +msgstr "" + +#: ../../storage.rst:609 +msgid "" +"When creating a new service offering, set the parameter isVolatile to True. " +"VMs created from this service offering will have their disks reset upon " +"reboot. See `âCreating a New Compute Offeringâ <service_offerings." +"html#creating-a-new-compute-offering>`_." +msgstr "" + +#: ../../storage.rst:616 +msgid "Volume Deletion and Garbage Collection" +msgstr "" + +#: ../../storage.rst:618 +msgid "" +"The deletion of a volume does not delete the snapshots that have been " +"created from the volume" +msgstr "" + +#: ../../storage.rst:621 +msgid "" +"When a VM is destroyed, data disk volumes that are attached to the VM are " +"not deleted." +msgstr "" + +#: ../../storage.rst:624 +msgid "" +"Volumes are permanently destroyed using a garbage collection process. The " +"global configuration variables expunge.delay and expunge.interval determine " +"when the physical deletion of volumes will occur." +msgstr "" + +#: ../../storage.rst:628 +msgid "" +"`expunge.delay`: determines how old the volume must be before it is " +"destroyed, in seconds" +msgstr "" + +#: ../../storage.rst:631 +msgid "" +"`expunge.interval`: determines how often to run the garbage collection check" +msgstr "" + +#: ../../storage.rst:634 +msgid "" +"Administrators should adjust these values depending on site policies around " +"data retention." +msgstr "" + +#: ../../storage.rst:639 +msgid "Working with Volume Snapshots" +msgstr "" + +#: ../../storage.rst:641 ../../storage.rst:686 +msgid "" +"(Supported for the following hypervisors: **XenServer**, **VMware vSphere**, " +"and **KVM**)" +msgstr "" + +#: ../../storage.rst:644 +msgid "" +"CloudStack supports snapshots of disk volumes. Snapshots are a point-in-time " +"capture of virtual machine disks. Memory and CPU states are not captured. If " +"you are using the Oracle VM hypervisor, you can not take snapshots, since " +"OVM does not support them." +msgstr "" + +#: ../../storage.rst:649 +msgid "" +"Snapshots may be taken for volumes, including both root and data disks " +"(except when the Oracle VM hypervisor is used, which does not support " +"snapshots). The administrator places a limit on the number of stored " +"snapshots per user. Users can create new volumes from the snapshot for " +"recovery of particular files and they can create templates from snapshots to " +"boot from a restored disk." +msgstr "" + +#: ../../storage.rst:656 +msgid "" +"Users can create snapshots manually or by setting up automatic recurring " +"snapshot policies. Users can also create disk volumes from snapshots, which " +"may be attached to a VM like any other disk volume. Snapshots of both root " +"disks and data disks are supported. However, CloudStack does not currently " +"support booting a VM from a recovered root disk. A disk recovered from " +"snapshot of a root disk is treated as a regular data disk; the data on " +"recovered disk can be accessed by attaching the disk to a VM." +msgstr "" + +#: ../../storage.rst:665 +msgid "" +"A completed snapshot is copied from primary storage to secondary storage, " +"where it is stored until deleted or purged by newer snapshot." +msgstr "" + +#: ../../storage.rst:670 +msgid "How to Snapshot a Volume" +msgstr "" + +#: ../../storage.rst:672 +msgid "Log in to the CloudStack UI as a user or administrator." +msgstr "" + +#: ../../storage.rst:676 +msgid "In Select View, be sure Volumes is selected." +msgstr "" + +#: ../../storage.rst:678 +msgid "Click the name of the volume you want to snapshot." +msgstr "" + +#: ../../storage.rst:680 +msgid "Click the Snapshot button. |SnapshotButton.png|" +msgstr "" + +#: ../../storage.rst:684 +msgid "Automatic Snapshot Creation and Retention" +msgstr "" + +#: ../../storage.rst:689 +msgid "" +"Users can set up a recurring snapshot policy to automatically create " +"multiple snapshots of a disk at regular intervals. Snapshots can be created " +"on an hourly, daily, weekly, or monthly interval. One snapshot policy can be " +"set up per disk volume. For example, a user can set up a daily snapshot at " +"02:30." +msgstr "" + +#: ../../storage.rst:695 +msgid "" +"With each snapshot schedule, users can also specify the number of scheduled " +"snapshots to be retained. Older snapshots that exceed the retention limit " +"are automatically deleted. This user-defined limit must be equal to or lower " +"than the global limit set by the CloudStack administrator. See `âGlobally " +"Configured Limitsâ <usage.html#globally-configured-limits>`_. The limit " +"applies only to those snapshots that are taken as part of an automatic " +"recurring snapshot policy. Additional manual snapshots can be created and " +"retained." +msgstr "" + +#: ../../storage.rst:707 +msgid "Incremental Snapshots and Backup" +msgstr "" + +#: ../../storage.rst:709 +msgid "" +"Snapshots are created on primary storage where a disk resides. After a " +"snapshot is created, it is immediately backed up to secondary storage and " +"removed from primary storage for optimal utilization of space on primary " +"storage." +msgstr "" + +#: ../../storage.rst:714 +msgid "" +"CloudStack does incremental backups for some hypervisors. When incremental " +"backups are supported, every N backup is a full backup." +msgstr "" + +#: ../../storage.rst:722 +msgid "Support incremental backup" +msgstr "" + +#: ../../storage.rst:727 +msgid "Volume Status" +msgstr "" + +#: ../../storage.rst:729 +msgid "" +"When a snapshot operation is triggered by means of a recurring snapshot " +"policy, a snapshot is skipped if a volume has remained inactive since its " +"last snapshot was taken. A volume is considered to be inactive if it is " +"either detached or attached to a VM that is not running. CloudStack ensures " +"that at least one snapshot is taken since the volume last became inactive." +msgstr "" + +#: ../../storage.rst:736 +msgid "" +"When a snapshot is taken manually, a snapshot is always created regardless " +"of whether a volume has been active or not." +msgstr "" + +#: ../../storage.rst:741 +msgid "Snapshot Restore" +msgstr "" + +#: ../../storage.rst:743 +msgid "" +"There are two paths to restoring snapshots. Users can create a volume from " +"the snapshot. The volume can then be mounted to a VM and files recovered as " +"needed. Alternatively, a template may be created from the snapshot of a root " +"disk. The user can then boot a VM from this template to effect recovery of " +"the root disk." +msgstr "" + +#: ../../storage.rst:751 +msgid "Snapshot Job Throttling" +msgstr "" + +#: ../../storage.rst:753 +msgid "" +"When a snapshot of a virtual machine is requested, the snapshot job runs on " +"the same host where the VM is running or, in the case of a stopped VM, the " +"host where it ran last. If many snapshots are requested for VMs on a single " +"host, this can lead to problems with too many snapshot jobs overwhelming the " +"resources of the host." +msgstr "" + +#: ../../storage.rst:759 +msgid "" +"To address this situation, the cloud's root administrator can throttle how " +"many snapshot jobs are executed simultaneously on the hosts in the cloud by " +"using the global configuration setting concurrent.snapshots.threshold." +"perhost. By using this setting, the administrator can better ensure that " +"snapshot jobs do not time out and hypervisor hosts do not experience " +"performance issues due to hosts being overloaded with too many snapshot " +"requests." +msgstr "" + +#: ../../storage.rst:767 +msgid "" +"Set concurrent.snapshots.threshold.perhost to a value that represents a best " +"guess about how many snapshot jobs the hypervisor hosts can execute at one " +"time, given the current resources of the hosts and the number of VMs running " +"on the hosts. If a given host has more snapshot requests, the additional " +"requests are placed in a waiting queue. No new snapshot jobs will start " +"until the number of currently executing snapshot jobs falls below the " +"configured limit." +msgstr "" + +#: ../../storage.rst:775 +msgid "" +"The admin can also set job.expire.minutes to place a maximum on how long a " +"snapshot request will wait in the queue. If this limit is reached, the " +"snapshot request fails and returns an error message." +msgstr "" + +#: ../../storage.rst:781 +msgid "VMware Volume Snapshot Performance" +msgstr "" + +#: ../../storage.rst:783 +msgid "" +"When you take a snapshot of a data or root volume on VMware, CloudStack uses " +"an efficient storage technique to improve performance." +msgstr "" + +#: ../../storage.rst:786 +msgid "" +"A snapshot is not immediately exported from vCenter to a mounted NFS share " +"and packaged into an OVA file format. This operation would consume time and " +"resources. Instead, the original file formats (e.g., VMDK) provided by " +"vCenter are retained. An OVA file will only be created as needed, on demand. " +"To generate the OVA, CloudStack uses information in a properties file (\\*." +"ova.meta) which it stored along with the original snapshot data." +msgstr "" + +#: ../../storage.rst:795 +msgid "" +"For upgrading customers: This process applies only to newly created " +"snapshots after upgrade to CloudStack 4.2. Snapshots that have already been " +"taken and stored in OVA format will continue to exist in that format, and " +"will continue to work as expected." +msgstr ""
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-admin/blob/a6b15cb9/source/locale/fr/LC_MESSAGES/systemvm.mo ---------------------------------------------------------------------- diff --git a/source/locale/fr/LC_MESSAGES/systemvm.mo b/source/locale/fr/LC_MESSAGES/systemvm.mo new file mode 100644 index 0000000..3ae1b27 Binary files /dev/null and b/source/locale/fr/LC_MESSAGES/systemvm.mo differ
