cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1302) Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM hypervisor
Date Wed, 20 Nov 2013 14:51:40 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827720#comment-13827720
] 

ASF subversion and git services commented on CLOUDSTACK-1302:
-------------------------------------------------------------

Commit 6f3e4d3592fa4b9889a1b0d6c108a07dc47a20ca in branch refs/heads/disk-cache from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6f3e4d3 ]

CLOUDSTACK-1302: Allow a cache mode per disk offering

Per disk offering the setting none, writeback or writethrough can be set

This allows for both safety and performance for writes.


> Add per storage setting for cache="none/writeback/writethrough" options for VMs on KVM
hypervisor
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1302
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1302
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.0.0
>         Environment: Ubuntu 12.04.2 Host, KVM hypervisor
>            Reporter: Jason Villalta
>            Priority: Minor
>
> Version 4.0.0 of Cloudstack has a hard coded value of cache=none for virtual machines
deployed.  This causes conflict with filesystems mounted with fuse such as ZFS, GlusterFs
and CEPH as fuse does not support directio with these file systems.  When starting VMs libvirt
throws an error "could not open disk image <disk> Invalid argument"
> Changing the cache= setting to writethough or writeback solves this problem but there
currently is no way to set this.  Ideally this would get set on a per datastore basis.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message