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 034D1C4A8 for ; Thu, 5 Jun 2014 13:29:43 +0000 (UTC) Received: (qmail 46585 invoked by uid 500); 5 Jun 2014 13:29:40 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 46551 invoked by uid 500); 5 Jun 2014 13:29:40 -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 46543 invoked by uid 99); 5 Jun 2014 13:29:40 -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:29:40 +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 dmcnelis@gmail.com designates 209.85.192.43 as permitted sender) Received: from [209.85.192.43] (HELO mail-qg0-f43.google.com) (209.85.192.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 13:29:37 +0000 Received: by mail-qg0-f43.google.com with SMTP id 63so1558854qgz.30 for ; Thu, 05 Jun 2014 06:29:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UhC2gj/y+aEEKrMzgEMphNJCACS6mHtUdv5JSbO5bzI=; b=Q3euAdjWK+QheRoGYWZn3PzWUqc266BUKaBNMjt/xxjhthWxHufsKFxEP7u+uGe5xJ O1jXwgsKshGZJX+QTXUq4ArM2Y5xM51VAF1cKE+cUPxj0qNYXxEEFyNuOcVe3k3eD/I0 8BBt7qXAIcqxpxWzSI0xwBvmJahwI7MQFIlpnT6/M2PAKghur54kkkZ4yhg7jrMrItvt T0WD5/w0Ou6nEYUe/HJ2lTJqymRIG4xm2jx1G229oYF9Y9INK5sWwcA4X86UyleW7V5H /qDnEvPdp+TtsLUgx1fMXapxk1fFKoZsmW+0mSqp7Ch8YDlkk3t50PYX6wKiyY8fN/PY 3STw== MIME-Version: 1.0 X-Received: by 10.224.136.129 with SMTP id r1mr17063853qat.60.1401974953282; Thu, 05 Jun 2014 06:29:13 -0700 (PDT) Received: by 10.229.119.135 with HTTP; Thu, 5 Jun 2014 06:29:13 -0700 (PDT) In-Reply-To: References: Date: Thu, 5 Jun 2014 09:29:13 -0400 Message-ID: Subject: Re: VPC AWS From: David McNelis To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11c2c57e131a9504fb16bb2b X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2c57e131a9504fb16bb2b Content-Type: text/plain; charset=UTF-8 A general thought, if you're using AWS for this, I'd strongly recommend you consider using OpsWorks and custom chef recipes for your node deployment if its an option for you. The easy of provisioning new nodes without the need for snapshotting is certainly worth the hassle, and there are already several Cassandra chef recipes available with a little searching. David On Thu, Jun 5, 2014 at 9:26 AM, William Oberman wrote: > I was making assumptions (sorry!), namely the goal to switching to vpc > was getting "backend resources" (like cassandra) off the public internet. > > Will > > On Thursday, June 5, 2014, Alain RODRIGUEZ wrote: > >> I think you can define VPC subnet to be public (to have public + private >> IPs) or private only. >> >> Any insight regarding snitches ? What snitch do you guys use ? >> >> >> 2014-06-05 15:06 GMT+02:00 William Oberman : >> >>> 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 >>> >> >> > > -- > Will Oberman > Civic Science, Inc. > 6101 Penn Avenue, Fifth Floor > Pittsburgh, PA 15206 > (M) 412-480-7835 > (E) oberman@civicscience.com > --001a11c2c57e131a9504fb16bb2b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
A general thought, if you're using AWS for this, I'= ;d strongly recommend you consider using OpsWorks and custom chef recipes f= or your node deployment if its an option for you. =C2=A0The easy of provisi= oning new nodes without the need for snapshotting is certainly worth the ha= ssle, and there are already several Cassandra chef recipes available with a= little searching.

David


On Thu, Jun 5, 2014 at 9:26 AM, William Oberman <oberman@civicscience.com> wrote:
I was making assumptions (sorry!), namely th= e goal to switching to vpc was=C2=A0getting "backend resources" (= like cassandra) off the public internet.=C2=A0

Will

On Thursday,= June 5, 2014, Alain RODRIGUEZ <arodrime@gmail.com> wrote:
I think you can define VPC = subnet to be public (to have public + private IPs) or private only.
Any insight regarding snitches ? What snitch do you guys use ?


2014-06-05 15:06 GMT+02:00 William Oberm= an <oberman@civicscience.com>:
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 Thursday, June 5, 2014, Alain RODRIGUEZ <aro= drime@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-7835
(E) oberman@civicscience.com



--
Will Oberman
Civic Science, Inc.
61= 01 Penn Avenue, Fifth Floor
Pittsburgh, PA 15206
(M) 412-480-7835
(= E) oberman@ci= vicscience.com

--001a11c2c57e131a9504fb16bb2b--