cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-2019) Over provisioning of resources at VM level instead of at cluster level
Date Fri, 12 Apr 2013 08:45:29 GMT

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

Abhinandan Prateek updated CLOUDSTACK-2019:
-------------------------------------------

    Description: Currently cloudstack provide a feature where in we can over provision the
resources of a cluster. This makes whole cluster tied to a particular provisioning factor.
Instead we would like to define the over provisioning at the VM level via the service offering.
This makes the model very flexible and frees up cluster from any kind of restrictions.  (was:
Need to automate the way the LDAP users are provisioned into cloud stack. This will mean better
integration with a LDAP server, ability to import users and a way to define how the LDAP user
maps to the cloudstack users.)
    
> Over provisioning of resources at VM level instead of at cluster level
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2019
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2019
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Abhinandan Prateek
>             Fix For: Future
>
>
> Currently cloudstack provide a feature where in we can over provision the resources of
a cluster. This makes whole cluster tied to a particular provisioning factor. Instead we would
like to define the over provisioning at the VM level via the service offering. This makes
the model very flexible and frees up cluster from any kind of restrictions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message