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

Stefan Miklosovic commented on CASSANDRA-7147:
----------------------------------------------

this is offtopic to this ticket but I think we should harmonize all cloud 
snitches we currently have. If we go with data-server. approach, this approach 
is no different from Alibaba or GCP or even AWS which are calling some metadata 
services and only endpoints are different. 
>From the implementation point of view, we would greatly simplify the code, I 
>can see how all snitches would extend some generic cloud-metadata-service 
>snitch where only URLs are different.

> Add a new snitch for Apache Cloudstack platforms
> ------------------------------------------------
>
>                 Key: CASSANDRA-7147
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7147
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: Virtual machine on Apache Cloudstack environments 
>            Reporter: Pierre-Yves Ritschard
>            Assignee: Pierre-Yves Ritschard
>            Priority: Low
>             Fix For: 1.2.18, 2.0.8, 2.1 rc1
>
>         Attachments: 0001-initial-work-on-a-cloudstack-snitch.patch
>
>
> The attached patch adds a new Snitch that queries meta data for a host on 
> Apache Cloudstack environments. Since the metadata service is colocated with 
> the DHCP service in Cloudstack, common lease file locations are looked up to 
> retrieve.
> Since zone naming is freeform in Apache Cloudstack, the widely used 
> <country>-<location>-<az> notation is assumed.
> The patch includes a simple unit test and has been tested on exoscale.ch, a 
> public cloud based on Apache Cloudstack



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to