Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E638F10A71 for ; Wed, 12 Jun 2013 17:45:12 +0000 (UTC) Received: (qmail 2550 invoked by uid 500); 12 Jun 2013 17:45:11 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 2501 invoked by uid 500); 12 Jun 2013 17:45:10 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 1520 invoked by uid 99); 12 Jun 2013 17:45:05 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jun 2013 17:45:05 +0000 Received: from localhost (HELO mail-la0-f52.google.com) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jun 2013 17:44:54 +0000 Received: by mail-la0-f52.google.com with SMTP id fo12so6306555lab.11 for ; Wed, 12 Jun 2013 10:44:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TuBZn6wKG2WohDAOBh5gh7rAng5oSRvo6wPYysPh0gU=; b=jUmIEojCLS4X/PuCBT/ptUc0QZ3lRKDIffBlOOAfCou0dIks9ep1bhS6jYq/zzODnW zA8KZj8lmna4dZRkMR3U2EyB4DOv+eaXSw9RQ8U36r/J0QSb+CHVbd3NyWAaGcYFlT7V i8cKhzGO8ySzS8D/uby4RYF+jskCPW9peoik/4onqub/YB7OUHo5WF5hlem5vWatbBru lbXOJ28rMCD6TRTkknIWeHKt76gsMEuHn8Q/UCEoo3A7DzzJ+zKQgh8yjdeOBZXPT3mA LT/bSE1tkoIQWTsmBLgt7JkyMQoLNQQtoEK1DsDg5Nh0glcr8Cefei0QCY0IcsCfPFbC QabQ== MIME-Version: 1.0 X-Received: by 10.152.121.106 with SMTP id lj10mr10246762lab.27.1371059092897; Wed, 12 Jun 2013 10:44:52 -0700 (PDT) Received: by 10.112.148.137 with HTTP; Wed, 12 Jun 2013 10:44:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 12 Jun 2013 18:44:52 +0100 Message-ID: Subject: Re: accidentally used same uuid on multiple servers From: Robert Newson To: "dev@couchdb.apache.org" Content-Type: text/plain; charset=ISO-8859-1 That's a thought, bootstrap from something that even virtualized systems should be wary of duplicating. B. On 12 June 2013 18:28, Randall Leeds wrote: > Is there something we could do with some hardware info (MAC addresses, > disk UUIDs, etc) to notice when the UUID might not have been generated > on this hardware and log a warning? Would that even be helpful? > > On Wed, Jun 12, 2013 at 7:04 AM, Robert Newson wrote: >> Sure, you can do that, the trick here is knowing you need to (and, >> conversely, knowing you shouldn't copy a local.ini if couchdb has >> added a uuid property). >> >> B. >> >> >> On 12 June 2013 14:56, Alexander Shorin wrote: >>> On Thu, May 2, 2013 at 7:24 PM, Ian Ward wrote: >>>> rnewson asked me to write to the list about the above, in order to >>>> discuss storing uuid in a place where it may be less likely to be >>>> copied in deployment management systems / scripts like Puppet. >>> >>> It is possible to create custom ini file within %localconfdir%/local.d >>> (/etc/couchdb/local.d for instance) directory which will override >>> local.ini uuid option: >>> >>> [couchdb] >>> uuid = myuuid >>> >>> This file may be automatically generated with puppet without need to >>> edit local.ini on each instance. >>> >>> -- >>> ,,,^..^,,,