Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Oct 2017 01:52:00 +0000 (UTC)
From: "Jason Brown (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12737138.1409155243000.35329.1507773120183@Atlassian.JIRA>
In-Reply-To: <JIRA.12737138.1409155243000@Atlassian.JIRA>
References: <JIRA.12737138.1409155243000@Atlassian.JIRA> <JIRA.12737138.1409155243404@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (CASSANDRA-7839) Support standard EC2
 naming conventions in Ec2Snitch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 12 Oct 2017 01:52:04 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-7839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201308#comment-16201308 ] 

Jason Brown edited comment on CASSANDRA-7839 at 10/12/17 1:51 AM:
------------------------------------------------------------------

I agree this would be a nice thing to get in for 4.0. I can rebase and kick off a round of tests. [~danielbankhead] Would you be able to give this patch a whirl (assuming you run in AWS)? I've also reached out to Netflix to see if they can try it out, as well.


was (Author: jasobrown):
I agree this would be a nice thing to get in for 4.0. I can rebase and kick off a round of tests. [~danielbankhead] Would you be able to give this patch a whorl (assuming you run in AWS)? I've also reached out to Netflix to see if they can try it out, as well.

> Support standard EC2 naming conventions in Ec2Snitch
> ----------------------------------------------------
>
>                 Key: CASSANDRA-7839
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7839
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Gregory Ramsperger
>            Assignee: Gregory Ramsperger
>              Labels: docs-impacting
>         Attachments: CASSANDRA-7839-aws-naming-conventions.patch
>
>
> The EC2 snitches use datacenter and rack naming conventions inconsistent with those presented in Amazon EC2 APIs as region and availability zone. A discussion of this is found in CASSANDRA-4026. This has not been changed for valid backwards compatibility reasons. Using SnitchProperties, it is possible to switch between the legacy naming and the full, AWS-style naming. 
> Proposal:
> * introduce a property (ec2_naming_scheme) to switch naming schemes.
> * default to current/legacy naming scheme
> * add support for a new scheme ("standard") which is consistent AWS conventions
> ** data centers will be the region name, including the number
> ** racks will be the availability zone name, including the region name
> Examples:
> * * legacy* : datacenter is the part of the availability zone name preceding the last "\-" when the zone ends in \-1 and includes the number if not \-1. Rack is the portion of the availability zone name following  the last "\-".
> ** us-west-1a => dc: us-west, rack: 1a
> ** us-west-2b => dc: us-west-2, rack: 2b; 
> * *standard* : datacenter is the part of the availability zone name preceding zone letter. rack is the entire availability zone name.
> ** us-west-1a => dc: us-west-1, rack: us-west-1a
> ** us-west-2b => dc: us-west-2, rack: us-west-2b; 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org