Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 13 Feb 2014 12:24:24 +0000 (UTC)
From: "Saksham Srivastava (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12694965.1392291786259.36544.1392294264610@arcas>
In-Reply-To: <JIRA.12694965.1392291786259@arcas>
References: <JIRA.12694965.1392291786259@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-6092) Storage OverProvisioning as a
 Per Primary Basis
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saksham Srivastava updated CLOUDSTACK-6092:
-------------------------------------------

    Description: 
The current scenario is to set the global parameter storage.overprovisioning.factor that is inherently applicable for any qualified primary store to leverage over provision of the underlying storage. 
Cloud Deployments can have different combinations of primary storage either for different vendors or from the same vendor but different products
Depending on the storage capability, CloudStack admins need the flexibility to determine what the over-provisioning factor should be for each primary storage.


> Storage OverProvisioning as a Per Primary Basis
> -----------------------------------------------
>
>                 Key: CLOUDSTACK-6092
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6092
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Storage Controller
>    Affects Versions: 4.4.0
>            Reporter: Saksham Srivastava
>            Assignee: Saksham Srivastava
>              Labels: Storage
>             Fix For: 4.4.0
>
>
> The current scenario is to set the global parameter storage.overprovisioning.factor that is inherently applicable for any qualified primary store to leverage over provision of the underlying storage. 
> Cloud Deployments can have different combinations of primary storage either for different vendors or from the same vendor but different products
> Depending on the storage capability, CloudStack admins need the flexibility to determine what the over-provisioning factor should be for each primary storage.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)