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 <[email protected]> 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 <[email protected]> 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 <[email protected]> wrote: >>> On Thu, May 2, 2013 at 7:24 PM, Ian Ward <[email protected]> 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. >>> >>> -- >>> ,,,^..^,,,
