Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B665711CD3 for ; Mon, 5 May 2014 15:30:23 +0000 (UTC) Received: (qmail 37341 invoked by uid 500); 5 May 2014 15:30:21 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 37202 invoked by uid 500); 5 May 2014 15:30:19 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 37067 invoked by uid 99); 5 May 2014 15:30:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 May 2014 15:30:17 +0000 Date: Mon, 5 May 2014 15:30:17 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7156) Add a new seed provider for Apache Cloudstack platforms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989605#comment-13989605 ] Jonathan Ellis commented on CASSANDRA-7156: ------------------------------------------- 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. Then if you want to wander off the beaten path you're on your own. > 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)