Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 132D718A12 for ; Thu, 4 Feb 2016 00:19:07 +0000 (UTC) Received: (qmail 9426 invoked by uid 500); 4 Feb 2016 00:19:06 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 9376 invoked by uid 500); 4 Feb 2016 00:19:06 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 9364 invoked by uid 99); 4 Feb 2016 00:19:06 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2016 00:19:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 999D1180179 for ; Thu, 4 Feb 2016 00:19:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.9 X-Spam-Level: * X-Spam-Status: No, score=1.9 tagged_above=-999 required=6.31 tests=[DATE_IN_FUTURE_06_12=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (768-bit key) header.d=soleks.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id qQTZEA3fpPYx for ; Thu, 4 Feb 2016 00:19:03 +0000 (UTC) Received: from mail-smtp00.soleks.net (smtp.soleks.net [66.196.35.221]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id E2DB631AA9 for ; Thu, 4 Feb 2016 00:19:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=soleks.com; s=x; h=Content-Transfer-Encoding:MIME-Version:Content-Type:In-Reply-To:References:Subject:To:From:Message-ID:Date; bh=vmO3OWoTblBiIc4HLbsZA1pCXGW8Evs/9HIFTkI+6ps=; b=W7FG25MAsX/w7QLHNJfBv6wf6JB9SHw6KLRQEamgG0qLQXdx6uzApZHGF8eRjvsWqKmIujziQ3Ie0QmUgjmUliNQXlaTQK+aI4Sdg/1FPEihr+eQBO7TYmODIUKllAol; Received: from mail-webmail00.gms.soleks.net ([10.1.12.232] helo=webmail.soleks.net) by mail-smtp00.soleks.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.85) (envelope-from ) id 1aR7d4-0000qZ-H1 for dev@cloudstack.apache.org; Wed, 03 Feb 2016 16:18:34 -0800 Received: from qubit.dwavesys.com (qubit.dwavesys.com [216.13.217.230]) by webmail.soleks.net (Horde Framework) with HTTP; Thu, 04 Feb 2016 00:17:35 -0800 Date: Thu, 04 Feb 2016 00:17:35 -0800 Message-ID: <20160204001735.Horde.kShTzJfx2KARoTvb8keofdM@webmail.soleks.net> From: Daniel Mezentsev To: dev@cloudstack.apache.org Subject: Re: Advice needed - switching IP for SS References: In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: multipart/alternative; boundary="=_2AcsgPRvXOcZXkJaAJxr3Hj" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-GMS-IP-Reputation: 0 --=_2AcsgPRvXOcZXkJaAJxr3Hj Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Description: Plaintext Message Content-Disposition: inline Content-Transfer-Encoding: 8bit Igor, I have question. Doing such IP migration is it possible that arp cache on the switch (assuming that we have layer 3 switch) can have old server pair MAC<--->IP. > Andrija, as for me the best solution: > > 1. shutdown data interfaces (or bond) on switch for new server after rsync > 2. Configure same IP as for old server > 3. via switch CLI shutdown data ports for old server > 4. via switch CLI startup ports for new server > 4. Reconfigure IP for data bond old server via mgm interface to new IP > 5. via switch CLI startup data ports for old server on switch > > All this can be done via ansible. Downtime will be only between steps 3 > and > 4. And it's will be around 0,1-0,5 seconds. > > From cloudstack mgmt sever it's will be transparent. Possible 1-2 TCP > retransit will happen. > > 2016-02-03 22:49 GMT+02:00 Andrija Panic : > >> Hi guys, >> >> I need to do manitance of 1 Seconary Storage NFS server fro few days, >> so I >> though to temporarily rsync data to another NFS box, and switch IP >> addresses, so the new NFS box has the original IP for few days...(need to >> test if KVm nodes will gracefullt remount the NFS server during the IP >> switchover...) >> >> Is this the prefered way, or should I hack the DB to point existing NFS >> server (that is defined in ACS) to the new IP of the second NFS box, and >> perhaps restart mgmt and agents across all nodes. >> >> Any recomendations ? >> >> Best, >> >> Andrija Panić > >   Daniel Mezentsev, founder (+1) 604 313 8592. Soleks Data Group. Shaping the clouds. --=_2AcsgPRvXOcZXkJaAJxr3Hj--