yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #22065
[Bug 1106423] Re: grizzly: ability to specify the libvirt cache mode for disk devices
** Changed in: nova/havana
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1106423
Title:
grizzly: ability to specify the libvirt cache mode for disk devices
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Compute (nova) havana series:
Fix Released
Status in OpenStack Manuals:
Fix Released
Bug description:
If https://review.openstack.org/#/c/18042/ is merged, a new
configuration option/feature will be added to nova. The manuals should
be updated to reflect this - configuration references and sample files
In past versions of Nova it was possible to explicitly configure
the cache mode of disks via the libvirt XML template. The curent approach
makes this a derived setting of either “none” or “writethrough” based
on the support of O_DIRECT. Whilst this provides a good set of default
settings it removes the ability of the cloud provider to use other
modes such as “writeback” and “unsafe” which are valuable in certain
configurations.
This change allows the cache mode to be specified on a per-disk type
basis. Leaving the specify_cachemode option set to False retains the
current behaviour.
189 cfg.ListOpt('disk_cachemodes',
190 default=[],
191 help='Specific cachemodes to use for different disk types '
192 'e.g: ["file=directsync","block=none"]'),
189 ] 193 ]
317 self.valid_cachemodes = ["default",
318 "none",
319 "writethrough",
320 "writeback",
321 "directsync",
322 "writethrough",
323 "unsafe",
324 ]
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1106423/+subscriptions