Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 52639 invoked from network); 30 Dec 2010 21:16:14 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Dec 2010 21:16:14 -0000 Received: (qmail 79030 invoked by uid 500); 30 Dec 2010 21:16:13 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 78981 invoked by uid 500); 30 Dec 2010 21:16:12 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 78844 invoked by uid 99); 30 Dec 2010 21:16:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Dec 2010 21:16:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.216.172] (HELO mail-qy0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Dec 2010 21:16:03 +0000 Received: by qyk34 with SMTP id 34so13029447qyk.10 for ; Thu, 30 Dec 2010 13:15:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.221.69 with SMTP id ib5mr9478947qcb.140.1293743742723; Thu, 30 Dec 2010 13:15:42 -0800 (PST) Received: by 10.229.84.198 with HTTP; Thu, 30 Dec 2010 13:15:42 -0800 (PST) X-Originating-IP: [64.132.24.248] In-Reply-To: References: <4D1CECDC.9000505@real.com> Date: Thu, 30 Dec 2010 15:15:42 -0600 Message-ID: Subject: Re: cassandra.yaml customization per node From: Nate McCall To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I've done this before with puppet, but any sort of mainstream configuration management system should work. There will be some management overhead in making sure any token changes make it back into the right server-specific template, but otherwise it's straight forward. On Thu, Dec 30, 2010 at 2:56 PM, Jake Luciani wrote: > You can specify the location of cassandra.yaml with a url so you can keep > your configs in one (redundant place) like S3 or generate them on the fly= in > a http service... > > > On Thu, Dec 30, 2010 at 3:34 PM, B. Todd Burruss wrot= e: >> >> how are folks customizing the cassandra.yaml for each node in the cluste= r. >> =A0specifically the token and IP address. >> >> with XML i used entities, but i'm not familiar with YAML. =A0does yaml >> support the same concept? =A0or any sort of textual substitution? >> >> thx > >