23 karma · joined April 23, 2015
My curiosity was more in whether there were performance (or other) bottlenecks which made it technically infeasible.
Curious why you wouldn't want to run it in docker in production? Wouldn't running the same container in dev/prod be helpful?
I haven't seen it done, it's just a theory, hence why I asked. I'm just not sure if zfs needs to see actual disks, or if it can work on top of any block device, like an md RAID.
This way you get the expandability of RAID with the checksumming and snapshots of ZFS.
In the article they mention it doesn't have local storage. It's too bad they didn't go into more detail about tamper proofing the USB portion of the ceremonies.
> This laptop has no battery, hard disk, or even a clock backup battery, and thus can’t store state once it’s unplugged.
I love how it makes it really easy for me to screen the calls however, as no-one I know has the same prefix and there are a couple area codes covering the local calling area.
Unless I'm misinterpreting, I think you were going for RAID1.
I only wish it were written in something which compiles native, like C or Go. Not bad enough to switch to anything else however, and it's really just my own personal dislike for Rails/Ruby.
Love the Gitlab-CI integration too, and am excited to see how it grows/improves over time.
Was this years ago, or more recently?
Also, can anyone speak to the current state of affairs with respect to ext4, xfs, and btrfs? I'd love to hear about the tooling and code quality in these file systems from an informed (and recent) point of view. Has Redhat been putting out fires since the switch? Did it go unnoticed? Are there measurable performance and/or reliability gains?
Let's not forget they have a working Linux client. Maybe things have changed since I last looked, but they were one of the few supporting Linux (both cli and gui).