cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
Date Mon, 24 Oct 2016 13:34:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9504:

Github user mike-tutkowski commented on the issue:
    Any way to easily just re-run test_05_stop_ssvm and test_07_reboot_ssvm?
    I'm not sure how this PR would cause such failures. The only changed Java code does the
    * Validates IOPS parameters in a certain situation when creating a new System Offering.
(should not apply here)
    * For managed storage, when the storage-cleanup thread runs, attempts to remove the remaining
SR. If this fails, the exception is logged and processing continues as usual. (should not
apply here)

> Fully support system VMs on managed storage
> -------------------------------------------
>                 Key: CLOUDSTACK-9504
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions:
>         Environment: All
>            Reporter: Mike Tutkowski
>            Assignee: Mike Tutkowski
>             Fix For:
> There are three related items for this ticket:
> 1) Do not permit "custom IOPS" as a parameter when creating a system offering (throw
an exception if this parameter is passed in).
> 2) If you transition managed storage into maintenance mode and system VMs were running
on that managed storage, the host-side clustered file systems (SRs on XenServer) are not removed.
Remove them.
> 3) Add integration tests for system VMs with managed storage.

This message was sent by Atlassian JIRA

View raw message