cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-6139) global setting to zone setting
Date Fri, 01 May 2015 13:26:07 GMT


ASF subversion and git services commented on CLOUDSTACK-6139:

Commit 279efb04324249a2e1a5487b58b40a723baf4600 in cloudstack's branch refs/heads/4.5 from
[;h=279efb0 ]

CLOUDSTACK-6139: Fix regression, allow zone level systemvm localstorage config

>From b3f18e7d74a0f09db9977554a6c7648b7edbc33d, the zone level systemvm local
storage setting never worked as it needed to be moved to config depot.

Signed-off-by: Rohit Yadav <>

> global setting to zone setting
> ----------------------------------------------------------
>                 Key: CLOUDSTACK-6139
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller
>    Affects Versions: Future
>            Reporter: Rutger te Nijenhuis
>            Assignee: Rohit Yadav
>             Fix For: 4.6.0, 4.5.1
> Move the global setting " - Indicates whether to use local
storage pools or shared storage pools for system VMs." to zone level. Cloudstack allows local
storage to be enabled at a per zone setting from zone details. The system VM's will however
end up on either shared of local storage according to the global settings. Moving this setting
to the zone level enables you to run zones with only local storage next to zones with only
shared storage.

This message was sent by Atlassian JIRA

View raw message