Difference between revisions of "Translations:ReleaseNotes/Kilo/81/en"

Latest revision as of 01:48, 13 August 2016

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (ReleaseNotes/Kilo)

* From this point forward any new database schema upgrades will not require restarting Cinder services right away. The services are now independent of schema upgrades. This is part one to Cinder supporting rolling upgrades!
* Ability to add/remove volumes from an existing consistency group. [http://docs.openstack.org/admin-guide-cloud/content/consistency-groups.html Read docs for more info].
* Ability to create a consistency group from an existing consistency group snapshot. [http://docs.openstack.org/admin-guide-cloud/content/consistency-groups.html Read docs for more info].
* Create more fine tuned filters/weighers to set how the scheduler will choose a volume backend. [http://docs.openstack.org/admin-guide-cloud/content/driver_filter_weighing.html Read the docs for more info].
* Encrypted volumes can now be backed up using the Cinder backup service. [http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html Read the docs for more info].
* Ability to create private volume types. This is perfect when you want to make volume types available to only a specific tenant or to test it before making available to your cloud. To do so use the ''cinder type-create <name> --is-public''.
* Oversubscription with thin provision is configurable. [http://docs.openstack.org/admin-guide-cloud/content/over_subscription.html Read docs for more info].
* Ability to add descriptions to volume types. To do so use ''cinder type-create <name> <description>
* Cinder now can return multiple iSCSI paths information so that the connector can attach volumes even when the primary path is down ([https://review.openstack.org/#/c/134681/ when connector's multipath feature is enabled] or [https://review.openstack.org/#/c/140877/ not enabled]).
* Add ability to specify a local lvm.conf file. When using the LVM driver this option allows you to set a Cinder specific lvm.conf file in /etc/cinder/lvm.conf. This enables specific LVM settings and filters that are only picked up and used by Cinder.
* The Cinder backup service can now backup to an NFS exported filesystem. [http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html Read the docs for more info].

Translation* From this point forward any new database schema upgrades will not require restarting Cinder services right away. The services are now independent of schema upgrades. This is part one to Cinder supporting rolling upgrades!
* Ability to add/remove volumes from an existing consistency group. [http://docs.openstack.org/admin-guide-cloud/content/consistency-groups.html Read docs for more info].
* Ability to create a consistency group from an existing consistency group snapshot. [http://docs.openstack.org/admin-guide-cloud/content/consistency-groups.html Read docs for more info].
* Create more fine tuned filters/weighers to set how the scheduler will choose a volume backend. [http://docs.openstack.org/admin-guide-cloud/content/driver_filter_weighing.html Read the docs for more info].
* Encrypted volumes can now be backed up using the Cinder backup service. [http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html Read the docs for more info].
* Ability to create private volume types. This is perfect when you want to make volume types available to only a specific tenant or to test it before making available to your cloud. To do so use the ''cinder type-create <name> --is-public''.
* Oversubscription with thin provision is configurable. [http://docs.openstack.org/admin-guide-cloud/content/over_subscription.html Read docs for more info].
* Ability to add descriptions to volume types. To do so use ''cinder type-create <name> <description>
* Cinder now can return multiple iSCSI paths information so that the connector can attach volumes even when the primary path is down ([https://review.openstack.org/#/c/134681/ when connector's multipath feature is enabled] or [https://review.openstack.org/#/c/140877/ not enabled]).

From this point forward any new database schema upgrades will not require restarting Cinder services right away. The services are now independent of schema upgrades. This is part one to Cinder supporting rolling upgrades!
Ability to add/remove volumes from an existing consistency group. Read docs for more info.
Ability to create a consistency group from an existing consistency group snapshot. Read docs for more info.
Create more fine tuned filters/weighers to set how the scheduler will choose a volume backend. Read the docs for more info.
Encrypted volumes can now be backed up using the Cinder backup service. Read the docs for more info.
Ability to create private volume types. This is perfect when you want to make volume types available to only a specific tenant or to test it before making available to your cloud. To do so use the cinder type-create <name> --is-public.
Oversubscription with thin provision is configurable. Read docs for more info.
Ability to add descriptions to volume types. To do so use cinder type-create <name> <description>
Cinder now can return multiple iSCSI paths information so that the connector can attach volumes even when the primary path is down (when connector's multipath feature is enabled or not enabled).

@@ Line 8: / Line 8: @@
 * Ability to add descriptions to volume types. To do so use ''cinder type-create <name> <description>
 * Cinder now can return multiple iSCSI paths information so that the connector can attach volumes even when the primary path is down ([https://review.openstack.org/#/c/134681/ when connector's multipath feature is enabled] or [https://review.openstack.org/#/c/140877/ not enabled]).
-* Add ability to specify a local lvm.conf file.  When using the LVM driver this option allows you to set a Cinder specific lvm.conf file in /etc/cinder/lvm.conf.  This enables specific LVM settings and filters that are only picked up and used by Cinder.
-* The Cinder backup service can now backup to an NFS exported filesystem. [http://docs.openstack.org/admin-guide-cloud/content/volume-backup-restore.html Read the docs for more info].