cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From René Moser (JIRA) <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-8545) Unneeded VR reboot after successful live migration
Date Thu, 18 Jun 2015 11:20:00 GMT

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

René Moser updated CLOUDSTACK-8545:
-----------------------------------
    Fix Version/s: 4.5.2
                   4.4.4

> Unneeded VR reboot after successful live migration
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-8545
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8545
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.4.3, 4.5.1
>            Reporter: René Moser
>            Priority: Blocker
>             Fix For: 4.6.0, 4.4.4, 4.5.2
>
>
> The changes committed to fix #7994 are causing a lot of downtimes due unneeded VR reboots,
it fixes an edge case:
> In case of live migration fails and the VR will be rebooted from VMware HA, it VR network
config will get lost.
> This edge case seems to be fixed in a more reliable way in 4.6 with persistent router
config. Live migration on VMware rarely fails with such a small VM like the VR is, with low
RAM and no I/O. The current implementation does a router restart in every case just to make
"sure" config is there. This causes downtime up to 30 minutes in production environments.
> Therefore I suggest to revert the changes in 4.5.2 and 4.6.
> Also see ML thread in dev http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201506.mbox/%3C2D22E663-AFC2-4292-B16A-F6C2FCA0C217%40shapeblue.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message