Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E9769C40E for ; Thu, 5 Jun 2014 13:07:37 +0000 (UTC) Received: (qmail 90930 invoked by uid 500); 5 Jun 2014 13:07:27 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 90893 invoked by uid 500); 5 Jun 2014 13:07:27 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 90885 invoked by uid 99); 5 Jun 2014 13:07:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 13:07:27 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of oberman@civicscience.com designates 209.85.192.46 as permitted sender) Received: from [209.85.192.46] (HELO mail-qg0-f46.google.com) (209.85.192.46) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 13:07:23 +0000 Received: by mail-qg0-f46.google.com with SMTP id q108so1468085qgd.33 for ; Thu, 05 Jun 2014 06:06:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ZrSJabPUzv6sVdAiCCdtKhMV2B4W2i1aEDdEzS3Jf7A=; b=BrKWHQQFFZ9Wm/lRYiNW6T4U3K86HnLfI9RkoEfbO5eGIDhT5M9geCYxMm8wAc3//J vLCAAXFfVe+pFryX0fvMfX84VX2BBCAwlQdK2+kyzt3q3E8beWJH9aPst8l2rnI/Q9nF ZSg2jtmg50inLFyMEt/thhf46ODKTRZbBMx4E/KRumqvRf2zqpb5u4fS/zdyLbHVSgw7 K6z3rMLPO8e0/9mIHg/VzBeOqX87VluAklHs/8VvFBHMgBO2VJOsukNVtNurdQge0zPw Zwa+k125VlaVZd3U5nZkTChbw+tiNcjvmvscc8oci2Yel2VoRVehS1ao2+DdWnFpniUn SRZA== X-Gm-Message-State: ALoCoQlOhphfBVjkDKFyoxCINPT+WI0JLI/Zw8NG78Ei+1Ts5NAKWlJoMTktjrmVtY4OzCPOoep0 MIME-Version: 1.0 X-Received: by 10.229.70.196 with SMTP id e4mr81769560qcj.16.1401973619179; Thu, 05 Jun 2014 06:06:59 -0700 (PDT) Received: by 10.140.37.164 with HTTP; Thu, 5 Jun 2014 06:06:59 -0700 (PDT) X-Originating-IP: [108.39.195.250] In-Reply-To: References: Date: Thu, 5 Jun 2014 09:06:59 -0400 Message-ID: Subject: Re: VPC AWS From: William Oberman To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a1133bb588e8fe304fb166b93 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133bb588e8fe304fb166b93 Content-Type: text/plain; charset=UTF-8 I don't think traffic will flow between "classic" ec2 and vpc directly. There is some kind of gateway bridge instance that sits between, acting as a NAT. I would think that would cause new challenges for: -transitions -clients Sorry this response isn't heavy on content! I'm curious how this thread goes... Will On Thursday, June 5, 2014, Alain RODRIGUEZ wrote: > Hi guys, > > We are going to move from a cluster made of simple Amazon EC2 servers to a > VPC cluster. We are using Cassandra 1.2.11 and I have some questions > regarding this switch and the Cassandra configuration inside a VPC. > > Actually I found no documentation on this topic, but I am quite sure that > some people are already using VPC. If you can point me to any documentation > regarding VPC / Cassandra, it would be very nice of you. We have only one > DC for now, but we need to remain multi DC compatible, since we will add DC > very soon. > > Else, I would like to know if I should keep using EC2MultiRegionSnitch or > change the snitch to anything else. > > What about broadcast/listen ip, seeds...? > > We currently use public ip as for broadcast address and for seeds. We use > private ones for listen address. Machines inside the VPC will only have > private IP AFAIK. Should I keep using a broadcast address ? > > Is there any other incidence when switching to a VPC ? > > Sorry if the topic was already discussed, I was unable to find any useful > information... > -- Will Oberman Civic Science, Inc. 6101 Penn Avenue, Fifth Floor Pittsburgh, PA 15206 (M) 412-480-7835 (E) oberman@civicscience.com --001a1133bb588e8fe304fb166b93 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I don't think traffic will flow between "classic" ec2 an= d vpc directly. There is some kind of gateway bridge instance that sits bet= ween, acting as a NAT. =C2=A0 I would think that would cause new=C2=A0chall= enges for:
-transitions=C2=A0
-clients

Sorry = this response isn't heavy on content! =C2=A0I'm curious how this th= read goes...

Will

On Thu= rsday, June 5, 2014, Alain RODRIGUEZ <arodrime@gmail.com> wrote:
Hi guys,

We are going to move from a cluster made of simple Amazon EC2 servers to a= VPC cluster. We are using Cassandra 1.2.11 and I have some questions regar= ding this switch and the Cassandra configuration inside a VPC.

Actually I found no documentation on this topic, but I = am quite sure that some people are already using VPC. If you can point me t= o any documentation regarding VPC / Cassandra, it would be very nice of you= . We have only one DC for now, but we need to remain multi DC compatible, s= ince we will add DC very soon.

Else, I would like to know if I should keep using EC2Mu= ltiRegionSnitch or change the snitch to anything else.

=
What about broadcast/listen ip, seeds...?

We currently use public ip as for broadcast address and for seeds. We use p= rivate ones for listen address. Machines inside the VPC will only have priv= ate IP AFAIK. Should I keep using a broadcast address ?

Is there any other incidence when switching to a VPC ?

<= /div>
Sorry if the topic was already discussed, I was unable to find an= y useful information...


--
Will Oberman
Civic Science, Inc.=
6101 Penn Avenue, Fifth Floor
Pittsburgh, PA 15206
(M) 412-480-78= 35
(E) obe= rman@civicscience.com
--001a1133bb588e8fe304fb166b93--