incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David McNelis <dmcne...@gmail.com>
Subject Re: VPC AWS
Date Thu, 05 Jun 2014 13:29:13 GMT
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 <oberman@civicscience.com>
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 <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 Oberman <oberman@civicscience.com>:
>>
>>> 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 <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
>>>> 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
>

Mime
View raw message