Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 12 Sep 2016 09:31:20 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12857441.1440050480000.546055.1473672680471@Atlassian.JIRA>
In-Reply-To: <JIRA.12857441.1440050480000@Atlassian.JIRA>
References: <JIRA.12857441.1440050480000@Atlassian.JIRA> <JIRA.12857441.1440050480535@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8751) Minimise VR downtime during
 network update
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 12 Sep 2016 09:31:30 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483617#comment-15483617 ] 

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

Github user karuturi commented on the issue:

    https://github.com/apache/cloudstack/pull/866
  
    the failing test(test_non_contigiousvlan.py) is not related to the PR. 
    The changes looks good and are ready to merge with required LGTMs and tests.
    @bvbharat Can you move the sql to change to 490to491 upgrade file and make the PR against 4.7 branch? once thats done, I will do the merge.
    Thanks


> Minimise VR downtime during network update
> ------------------------------------------
>
>                 Key: CLOUDSTACK-8751
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8751
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Bharat Kumar
>            Assignee: Bharat Kumar
>
> Currently we use redundant virtual router enabled networks to prevent network outage even if one of the virtual router fails. This is achieved by using redundant virtual routers along with VRRP protocol. This has increased the network robustness. However  updating a network with new network offering involves some downtime due to Vr restarts. In case of redundant VR based networks we can sequence the network update operations to update the backup first and then update the master while master's operations are being handled by backup, this way i think we can minimise the downtime.
> Link to FS https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61310469


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