Did I hallucinate this or are you intentionally ignoring the very specific action they said they were taking to address this?
The responsibility to vet who we put our name next to is ours, and we didn't meet it this time. We're now reviewing our vetting process and our guidelines for our marketing agencies to ensure this doesn't happen again.
The fact that they said "marketing agencies" strongly suggests that they're using third-party providers, which is pretty common for running affiliate programs. This would be in addition to any internal marketing team, if they have one.
Until this incident, clearly they just trusted that the third parties would vet the affiliates - and clearly they were wrong.
The first step in an incident like this is to determine what went wrong, which they're doing. It's very rare to get a "we've identified the issue and here's how we're fixing it" in an initial quick response like this.
City installs trash bags because they're contractually obligated to keep the devices installed and powered on
Someone hosts an impromptu Office Space fan meetup, with a fun reenactment of the printer scene
City sees this, responds with an obvious but legally non-actionable tweet response suggesting it continue (e.g. "Fartsburg loves Mike Judge films, too! So nice to see our citizens enjoying the various forms of recreation and socialization ths city has to offer."), along with some conspicuously-placed garbage cans near all of the cameras' installed locations.
Seems like none of y'all even read a few paragraphs into the article.
A human-sized, human-shaped robot can integrate into an existing production layout without having to redesign how the factory works. That's the sell.
To me that's a thinly-veiled way of saying "these things are purpose built to uproot human workers as soon as fucking possible," which would be a great thing if the intent were to remove humans from dangerous and/or unfulfilling jobs and pipe the earnings from the cost reduction/efficiency increase into taxes/ubi/assistance programs so that people can pursue their own dreams and interests without needing to wage slave their healthiest years away trying to survive.
But that's never the intent; it's always to add more zeroes to the balance sheet of the people at the top.
Yes, valid points that I didn't really want to muddy the discussion with. In my experience, most people hear the Redundant in RAID and think that's sufficient and that their data is safe. Maybe poor choice of words on my part, but that's what I meant re: "data safety."
You're fully correct that a proper RAID setup can provide additional layers of availability atop a robust backup process, but I'd wager most of the people who are interested in that extra layer are already aware of the limitations of RAID.
I do run RAIDZ1 on my franken-nas due to limited drive sizes on that machine, the goal being to maximize usable space while providing a sufficient amount of time to address a drive failure. If drive prices ever become reasonable again, I'll likely rebuild the system with 6-8 drives in a RAIDZ2 configuration just for a little more peace of mind, but as long as my off-site backups are running, I sleep at night just fine.
Ensuring availability of data in the face of hardware failure. That means your files don't disappear when a drive dies and you have some time to swap out for functional hardware and restore redundancy.
Presenting multiple drives as one larger unit. This is what striping does, and to a lesser extent the parity-mode levels.
Improving performance (sometimes). A RAID mirror is generally much faster to read from than any individual drive because reads can be interleaved across drive members. A stripe can be much faster because writes are distributed across drive members. This is less of a bonus today with solid state/nvme drives, but it's still applicable to spinning rust.
If your concern is protecting your data, set up a 3-2-1 backup strategy.
I personally would go the other way, use your nvme for storage and have a second small drive for proxmox since that part doesn't really need speed. That said, if you go with zfs replication it doesn't matter; just have the one nvme drive that holds the proxmox install and the storage pool. Separate drive only matters for Ceph.
Agreed, it helps that with proxmox the cluster is a first-class feature and all installs are a cluster even if only a single node. Really removes a lot of potential pain points from operations like this.
That depends on what level of HA you want to end up with.
If you want proper HA, you'll want to plan on adding a (small, like a Raspberry Pi) third node for quorum. If you are already taking backups and you just want "I can restore on the second system" then it's slightly simpler, but mostly the same process:
Setup new node, add to cluster
Migrate all VMs and LXCs to new node
Remove and upgrade other node
Add rebuilt node to cluster
If you're planning on proper HA, I'd strongly advise having the proxmox installation on a second small drive on each node and leaving your 1tb drives as data only.
This article half-explains one option for a two node setup (zfs replication), which is functional but not ideal. If you want to get your feet wet with Ceph then I can give you some pointers.
rabbit's foot thumps
The ex-prisoners solve world hunger and find a general cure for cancer
Did I hallucinate this or are you intentionally ignoring the very specific action they said they were taking to address this?
The joke is that Asian kids still win the spelling bee even with different rules for spelling. SNL was playing on the stereotype.
So many of these Norm-era jokes are wild outside the (more racist, more misogynistic) context of the late 20th century.
Seems like none of y'all even read a few paragraphs into the article.
A human-sized, human-shaped robot can integrate into an existing production layout without having to redesign how the factory works. That's the sell.
To me that's a thinly-veiled way of saying "these things are purpose built to uproot human workers as soon as fucking possible," which would be a great thing if the intent were to remove humans from dangerous and/or unfulfilling jobs and pipe the earnings from the cost reduction/efficiency increase into taxes/ubi/assistance programs so that people can pursue their own dreams and interests without needing to wage slave their healthiest years away trying to survive.
But that's never the intent; it's always to add more zeroes to the balance sheet of the people at the top.
Yes, valid points that I didn't really want to muddy the discussion with. In my experience, most people hear the Redundant in RAID and think that's sufficient and that their data is safe. Maybe poor choice of words on my part, but that's what I meant re: "data safety."
You're fully correct that a proper RAID setup can provide additional layers of availability atop a robust backup process, but I'd wager most of the people who are interested in that extra layer are already aware of the limitations of RAID.
I do run RAIDZ1 on my franken-nas due to limited drive sizes on that machine, the goal being to maximize usable space while providing a sufficient amount of time to address a drive failure. If drive prices ever become reasonable again, I'll likely rebuild the system with 6-8 drives in a RAIDZ2 configuration just for a little more peace of mind, but as long as my off-site backups are running, I sleep at night just fine.
You do you, but I'm holding out for it... and only in fully automated, luxury, gay form.
I would absolutely not trust BTRFS's implementation. Maybe things are better now but it earned the backronym Bro The RAID Fuckin Sucks for a reason.
RAID is not a backup.
RAID is not for data safety.
RAID is for:
If your concern is protecting your data, set up a 3-2-1 backup strategy.
I have an actual rubber duck for that. I hate it when my colleagues interrupt me just because they forgot how lambdas work
I personally would go the other way, use your nvme for storage and have a second small drive for proxmox since that part doesn't really need speed. That said, if you go with zfs replication it doesn't matter; just have the one nvme drive that holds the proxmox install and the storage pool. Separate drive only matters for Ceph.
Agreed, it helps that with proxmox the cluster is a first-class feature and all installs are a cluster even if only a single node. Really removes a lot of potential pain points from operations like this.
"Hey buddy, we'll pay you $100 if you take an STD test and then raw dog this pornstar for eight seconds. You in?"
That depends on what level of HA you want to end up with.
If you want proper HA, you'll want to plan on adding a (small, like a Raspberry Pi) third node for quorum. If you are already taking backups and you just want "I can restore on the second system" then it's slightly simpler, but mostly the same process:
If you're planning on proper HA, I'd strongly advise having the proxmox installation on a second small drive on each node and leaving your 1tb drives as data only.
This article half-explains one option for a two node setup (zfs replication), which is functional but not ideal. If you want to get your feet wet with Ceph then I can give you some pointers.
Randall seems to have aimed at recognisability in choosing those song titles.
Reflection is one of my favorites, super underrated even amongst Tool fans IMO.
He's talking about that shady coyote who's always chasing after that flightless bird.
Maybe the United States should pass laws that force public utilities to be owned by the public and operated as a nonprofit?
Idk, Miles Dyson was able to engineer a neural-net processor with room temperature superconductors all the way back in 1995...