cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <>
Subject [jira] [Closed] (CLOUDSTACK-3702) VM instantiation : specific information for hypervisors
Date Wed, 08 Feb 2017 09:24:00 GMT


Daan Hoogland closed CLOUDSTACK-3702.
    Resolution: Won't Fix

> VM instantiation : specific information for hypervisors 
> --------------------------------------------------------
>                 Key: CLOUDSTACK-3702
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: Future
>            Reporter: Nicolas FOATA
>            Priority: Minor
>              Labels: features
>             Fix For: Future
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> Abstract/suggestion: 
> While a VM is instantiated, Cloudstack could send and add furthermore data for the hypervisor
> coming from a new field such as 'Other options/Other configuration' for example in the
'Compute offering' screen.
> Thus, each hypervisor could decide whether it want to process the data and how or to
do not take it into account.
> With a such input, Cloudstack will be able to use the specificity and the full power
of each hypervisor.
> Applications:
> 1) On XCP, it will be possible to branch some pci straightforwardly (via pci passthrough)
> 2) To use the more efficiently the min, max memories (static and/or dynamic)
> Please feel free to modify the text if you to find better and sexy application examples

> with this two kinds of features and of course to correct mistakes.

This message was sent by Atlassian JIRA

View raw message