cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Tutkowski (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-10336) Restrict the number of managed SRs and datastores
Date Thu, 18 Oct 2018 18:11:00 GMT

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

Mike Tutkowski reassigned CLOUDSTACK-10336:
-------------------------------------------

    Assignee:     (was: Mike Tutkowski)

> Restrict the number of managed SRs and datastores
> -------------------------------------------------
>
>                 Key: CLOUDSTACK-10336
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10336
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware, XenServer
>    Affects Versions: 4.11.0.0
>         Environment: XenServer and VMware
>            Reporter: Mike Tutkowski
>            Priority: Major
>             Fix For: 4.12.0.0
>
>
> For managed storage, each time a virtual disk is created, a new SR is created (when
on XenServer) or a new datastore is created (when on VMware).
> XenServer 6.5 can support around 500 - 600 SRs per compute cluster while VMware can support
256 datastores per compute cluster.
> CloudStack has never had the ability to limit the number of SRs or datastores it creates
when using managed storage (the admin has needed to pay attention to this via some other
process outside of CloudStack).
> This code aims to address the main use cases in CloudStack that can create SRs or datastores
and fails the applicable operations if no more SRs or datastores can be created (based on
a new cluster-scoped setting that specifies how many SRs or datastores the admin is OK with
CloudStack creating).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message