Here is a similar use-case: I maintain a number of HA clusters with fully automatic bi-directional synchronization using rdist. To achieve this I have as few file differences as possible and those that must differ (mostly hostname.$if) being entirely scriptable -- the sole noteable exception is /etc/myname that drives the reconciliation script. Obviously, the logs and temporary files are excluded, but every file necessary to configure and operate the system must be included.
Now for the tricky part relevant to the title subject -- most of the clusters are not created by cloning, so their DUIDs are independent. Most of my clients are SMBs and do not realize to what extent they rely on the infrastructure "appliances" as the commercial appliances these servers replace do not generally support HA-clustering (that feature being marketed to "Enterprises" not SMBs). Once the client is educated and discovers that the incremental cost to add HA is relatively low, they go for it; however now that the primary server is busy under load, the additional cluster member(s) are built using installation image rather than direct cloning. I guess as long as /etc/fstab continues to support non-DUID device names, it can be manually edited after the initial system build. However, that also opens the window to transcription errors which can easily render the system non-operational, requiring recovery from external media, thus substantially complicating the deployment step. -Jacob. On 15 Mar 2015 at 12:12, Bob Beck wrote: > Yes I do. when I install machines that I dump/restore clone, I do not > use DUID's. it's very nice to make a system > without DUID's in that case. > > I think you could eliminate the DUID question for laptops. it's always > right there. I'd like to keep it for "server's" but don't > know if that's reasonably possible in the installer.... > > > > > On Sun, Mar 15, 2015 at 11:49 AM, Theo de Raadt <dera...@cvs.openbsd.org> > wrote: > >> On Sun, Mar 15, 2015 at 11:24:32AM -0400, Kenneth Westerback wrote: > >> > Using DUIDs in the installed /etc/fstab has been the default for some > >> > time now. > >> > > >> > We'd like to eliminate the question in the installer and just use > >> > DUIDs unconditionally. > >> > > >> > But first we need to know you are aware of any circumstances where > >> > people need or prefer to use the non-DUID option when installing? > >> > >> I prefer not using DUIDs. > > > > OK, I think Ken made a mistake mentioning preferences. The real > > question is if anyone has a use-case where DUIDs do not work. > > > > Preference has nothing to do with it. If DUIDs have no downsides, > > and only the upsides that they were designed to support, then it is > > time to remove the installation question. > > > > The non-DUID access patterns continue to work, of course. That is > > also not part of the question. > > > >
