I think (on linux, at least), its better to implement this as a nss- module (/etc/nsswitch.conf). You can do things like lookup a hashtable, automatically update databases, etc without having to rewrite system config files.
Also this does not protect you from programs that perform their own dns lookups, and ignore /etc/hosts and /etc/resolv.conf entirely!
MCVirt was started with the view of a small (2 node clusters), with the aim of a simple setup... We have investigated other storage backends, but felt that DRBD provided the features that we required and also, in some instances, is easier to recover in disaster recovery situations.
That said, I can't see why it wouldn't be too hard to implement ceph support in the future... we currently support both DRBD and local storage, adding a third backend wouldn't be too complex. I had also been considering other shared storage backends, such as iSCSI and, possibly, NFS
Great question! It was thrown out of court in the end, but the cop really didn't have any reason to pull us over, and despite searching the whole car, he couldn't find any drugs. He had to write a ticket for something though, I guess.
I think a note taker taking live notes that everyone can see, and perhaps edit, is a great way to record meetings. As a bonus, you even have something tangible to show the time you put in!
I'm working on this at the moment, in a way that also uses the edited transcripts to train our ASR system to perform better for later sessions. The difficult part is the speaker diarization, however. Multiple people talking at once requires some intricate signal processing to sort out.
I tend to live tweet stuff into slack, makes it useful to dump into other tools or get input from others who arent there, eliminates a lot of status update / meeting recaps