amorousf00p's comments

Why you cannot trust this model 101: because it's practitioners understand the value of the labor/product, capitalize on the OSS ideal and then push it to the unsuspecting.

I don't know how many bait and switch episodes from google I need to see but by 2008 I was done with them -- for the first time. Ad-nauseam.

If you boycotted and didn't use Google they would wither and die and stop being something to worry about: for immediate google specific free offerings that are sucker bait. Also for self aggrandizing standards/inclusions and buying the overt talent. But whatever. The HN community is full of dupes and buy ins, culture whores and fifth columnists. True belief in OSS died when everyone else took it and got rich.

Risk is not quantifiable based on your insight into most businesses. You provision and despair.

You seem to be an absolute type of planner. I used to approach IT mgmt and provisioning that way some years ago before being confronted with the realities of small and large business. One size obviously does not fit all and sometimes you take shortcuts..usually you pay for them later.

I agree with your cautions around supermicro resale but the warranty support and build diligence are absolutely necessary for a small business. Having a good business relationship with a trusted provider of hardware that always performs the first time is priceless.

hear, hear.

You are right about one thing: If you are not in the 1% being 95%-99% is being out in the cold. Debt being a cold bed fellow.

This is a ballpark average and only for one VPC based site. You'd need multiple sites...just as you do with hardware.

You'll have to trust me that this examples hardware spec and requirements are for a basic/base site. You can thin the profile and increase the # of chassis, compromise on redundancy, etc...but experience has shown that this arrangement is most cost effective. Kinetic event impact modeling system -w- RT data delivery -- that should answer your conjectures.

No large vendors used in this example - thinkmate or aberdeen supermicro re-brands for due diligence and warranty.

That's sad truth. But it's convenience like anything else.

In my business I can put a hardware site online with

---6X--- 2 x intel gold 5115 10 core + 64 GB RAM 1 nvme @512G + soft raid1 @4TB magnetic 1 10G, 2 1G ether ~= 42K.

---2X--- storage or NAS with 60TB @RAID5 + 2x quad core low end xeon + 32 GB RAM = 16k

---2X--- 1G edge/core mngd switches + 10G SAN/LAN mngd switches = 5K

---2X--- Endian firewalls + threat appliances = 5K

---1X--- Colo with 2 year lease and 25 amps @208v 1g port speed and committed throughput > 100/mbps = 16K yearly

68K one time cost for depreciating assets we maintain, provision and secure + 16K yearly recurring cost.

Or I can go AWS and modify my processing model, security expectations and service infra and spend 25K a year + 15K 1x migration cost.

AWS is a feature factory and they are breaking their own back. Today I had an issue where creating an AMI for an application feature set as a golden image (with a very modest price tag at t1.supersmall or whatever) does not scale into high end compute instances due to lack of support for ena. Never was the case before.

Rolled it back into KVM/QEMU in colo with a glue layer REST interface over virsh and will never look back.

Of course we don't use containers..they don't offer an overt benefit in HPC...and I don't think they ever will.

I think devops was defunct once the asphalt hit the hardpan. Approaching 'generic' secure operational environments as programmable, iterable and contained is one of the great IT lies of the last 20 years.

God yes.

God, I can empathize even if only at a much less prominent vantage. The skills, will and effort involved are at a level far more than a 50+ can reasonably sustain into the early 70s (if that is the prospect).

I don't know. If this is really how software is written in large scale web service environments you will always have problems. It just seems like sh*t to me.

Create a user and env to run a one-off build + application. DJB cracks me up. He may have the right thing in mind but this type of prophylactic approach is no longer proof against anything.

Not ad-hominem but what do you know how to do? Package other peoples stuff in a config + install and then run scans against it?

Fedora: Only if you really like breakage and have staff to deal with integration.

I'm old school. I look at containers as jails and all the work to isolate applications in containers as of indifferent value given a flat plane process scope with MAC and application resource controls in well designed applications.

That is I default to good design and testing rather than boilerplate orchestration and external control planes.

All containers have done (popularly) in my opinion is add complexity and insecurity to the OS environment and encouraged bad behavior in terms of software development and systems administration.

Kernighan is so nice to listen to compared to some of the the hot air balloons in software today. I use awk everywhere (and have for many years) and am deeply indebted to BK and AR for their work on and custody of that language.

Some of us didn't join the SN or believe in it. But then Google took the low road and most of us thought they were benevolent.

OpenBSD is very nice but it used to be a bit painful for a desktop. Funny, I ran linux on the desktop from 2000-2016 and then went back to windows because I'm getting old. :)

Keep fighting the good fight!