[jira] [Commented] (CASSANDRA-18438) Refactor the code for public cloud platform snitch to be configurable

["Jacek Lewandowski (Jira)" <ji...@apache.org>]

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

Jacek Lewandowski commented on CASSANDRA-18438:
-----------------------------------------------

CASSANDRA-16555 partially does that stuff  - it splits the snitch into connector and the snitch itself. If that was applied to other cloud snitches as well, they would look almost identical.

> Refactor the code for public cloud platform snitch to be configurable
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-18438
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18438
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Other
>            Reporter: Maxwell Guo
>            Assignee: Maxwell Guo
>            Priority: Normal
>             Fix For: 5.x
>
>
> Nowadays we have got about four public cloud platform snitchs ： EC2 snitch for aws, google cloud snitch for google cloud, alibaba cloud snitch for alibaba cloud and multi region snitch for ec2. And the common place for the first three is that we just need to query the zone center to get the ec2 / ecs id , so I think we can refactor the code , and  if some new public cloud platform want to add one more snitch for himself, there is no need to pull a pr for him and  configure some options in yaml is enough .
> Besides it would be even better that we may reuse the multic region snitch for ec2 for other public cloud platform.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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