Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E76651754A for ; Fri, 13 Feb 2015 14:02:53 +0000 (UTC) Received: (qmail 93225 invoked by uid 500); 13 Feb 2015 14:02:53 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 93185 invoked by uid 500); 13 Feb 2015 14:02:53 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 93170 invoked by uid 99); 13 Feb 2015 14:02:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 14:02:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [85.13.149.252] (HELO dd32406.kasserver.com) (85.13.149.252) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2015 14:02:25 +0000 Received: from dd32406.kasserver.com (dd0802.kasserver.com [85.13.143.1]) by dd32406.kasserver.com (Postfix) with ESMTPSA id 9E1176180267 for ; Fri, 13 Feb 2015 15:01:53 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SenderIP: 195.13.41.220 User-Agent: ALL-INKL Webmail 2.11 Subject: VPC, Redundant Router and Seamless Upgrades From: rob@fotm.net To: users@cloudstack.apache.org Message-Id: <20150213140153.9E1176180267@dd32406.kasserver.com> Date: Fri, 13 Feb 2015 15:01:53 +0100 (CET) X-Virus-Checked: Checked by ClamAV on apache.org Hi, currently we are investigating a deployment of Cloudstack for our Webhosting company and we came to the conclusion that currently the Redundant Router part is not supported for VPCs. Do you know if this implementation is possible? Additionally we hope that we are able to achieve "zero" downtime when we are performing an system vm upgrade. Can you please share your thoughts? Thank you in advance, Robert