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] [Resolved] (CLOUDSTACK-4088) cloudstack will stop and delete vm which not belongs to cs
Date Thu, 05 Sep 2013 10:26:52 GMT

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

Abhinandan Prateek resolved CLOUDSTACK-4088.
--------------------------------------------

    Resolution: Not A Problem

This will interfere with capacity calculations and will interfere with the operation of cloudstack.
This is by design. There is a way to subvert this by naming a VM using cloudstack naming convention,
such VM will not be stopped by CS. 
                
> cloudstack will stop and delete vm which not belongs to cs
> ----------------------------------------------------------
>
>                 Key: CLOUDSTACK-4088
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4088
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.0.2, 4.1.0, 4.2.0, Future
>         Environment: xenserver 6.0.2
>            Reporter: Hongtu Zang
>              Labels: removed, vm, xenserver
>             Fix For: 4.2.0, Future
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 1.create vm in xenserver, by xencenter
> 2.add xenserver to cloudstack
> the vm will be stopped and removed
> 3.create another vm in xencenter
> it is also removed

--
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