cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7156) Add a new seed provider for Apache Cloudstack platforms
Date Mon, 05 May 2014 16:00:18 GMT

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

Brandon Williams commented on CASSANDRA-7156:
---------------------------------------------

bq. I get that we don't want to host permutations of every possible custom seed provider,
but ISTM that one per major cloud is reasonable if we can agree on what constitutes best practices

I dunno, I kind of look at seed providers the same way I look at authenticators.  We could
ship an ldap authenticator or something, but we don't (and shouldn't.)  We'd be setting a
precedent here that will open us up to more seed providers in the future.

> Add a new seed provider for Apache Cloudstack platforms
> -------------------------------------------------------
>
>                 Key: CASSANDRA-7156
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7156
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: needs access to a cloudstack API endpoint
>            Reporter: Pierre-Yves Ritschard
>            Priority: Minor
>             Fix For: 2.0.8, 2.1.1
>
>         Attachments: 0001-initial-work-on-a-cloudstack-seed-provider.patch
>
>
> The attached patch adds a new seed provider which queries a cloudstack API endpoint for
instances having a specific tag.
> The tag key and value can be controlled in the configuration file and               
                                                                 
> will default to 'cassandra_seed' and 'default'.                                     
                                                                 
> The Cloudstack endpoint is configured by three parameters in the                    
                                                                 
> configuration file: 'cloudstack_api_endpoint', 'cloudstack_api_key' and             
                                                                 
> 'cloudstack_api_secret'                                                             
                                                                 
> By default, CloudstackSeedProvider fetchs the ipaddress of the first                
                                                                 
> interface, if another index should be used, the nic_index parameter will hold it.
> A typical configuration file would thus have:
> {code:yaml}
> seed_provider:
>     - class_name: org.apache.cassandra.locator.CloudstackSeedProvider
>       parameters:
>           - cloudstack_api_endpoint: "https://some.cloudstack.host"
>             cloudstack_api_key: "XXXXX"
>             cloudstack_api_secret: "XXXXX"
>             tag_value: "my_cluster_name"
> {code}
> This introduces no new dependency and together with CASSANDRA-7147 gives an easy way
of getting started on cloudstack platforms



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message