Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 17 Jun 2015 07:16:01 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12836271.1433794719000.93994.1434525361853@Atlassian.JIRA>
In-Reply-To: <JIRA.12836271.1433794719000@Atlassian.JIRA>
References: <JIRA.12836271.1433794719000@Atlassian.JIRA>
 <JIRA.12836271.1433794719164@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8545) Unneeded VR reboot after
 successful live migration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8545?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D14589401#comment-14589401 ]=20

ASF GitHub Bot commented on CLOUDSTACK-8545:
--------------------------------------------

Github user DaanHoogland commented on the pull request:

    https://github.com/apache/cloudstack/pull/466#issuecomment-112686118
 =20
    @remibergsma makes sense, will do
    @anshul1886 feel free to amend, I do not consider your proposed extensi=
on part of this blocker though it makes perfect sense from a functional per=
spective.


> Unneeded VR reboot after successful live migration
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-8545
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-854=
5
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>    Affects Versions: 4.4.3, 4.5.1
>            Reporter: Ren=C3=A9 Moser
>            Priority: Blocker
>             Fix For: 4.6.0
>
>
> The changes committed to fix #7994 are causing a lot of downtimes due unn=
eeded VR reboots, it fixes an edge case:
> In case of live migration fails and the VR will be rebooted from VMware H=
A, it VR network config will get lost.
> This edge case seems to be fixed in a more reliable way in 4.6 with persi=
stent router config. Live migration on VMware rarely fails with such a smal=
l VM like the VR is, with low RAM and no I/O. The current implementation do=
es 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/clouds=
tack-dev/201506.mbox/%3C2D22E663-AFC2-4292-B16A-F6C2FCA0C217%40shapeblue.co=
m%3E


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