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…
Risk is not quantifiable based on your insight into most businesses. You provision and despair.
Shithead.
Whenever I see some shit like 'thanks for sharing' or 'noted' I want to kill someone. These are cautionary tales: ignore at your leisure.
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…
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…
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…
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…
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…
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…
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!
I look at this setup and say to myself that this is just the wrong way to do it. A 'floating' vm to NAT and route? Ceph does look very nice but I have no need for anything but file based storage. Here is my top down…
I guess what I was trying to say is that instead of dealing with the default parental guidance features of RH and Fedora (which usually ends up with impatient users disabling SElinux and then disabling the stock packet…
Quibbles and bits. Python is the only language where I write logic and then massage data structures and outputs + design 'cooler' ways to create these for an extra hour -- a week after it is in production.
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…
Risk is not quantifiable based on your insight into most businesses. You provision and despair.
Shithead.
Whenever I see some shit like 'thanks for sharing' or 'noted' I want to kill someone. These are cautionary tales: ignore at your leisure.
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…
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…
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…
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…
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…
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…
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!
I look at this setup and say to myself that this is just the wrong way to do it. A 'floating' vm to NAT and route? Ceph does look very nice but I have no need for anything but file based storage. Here is my top down…
I guess what I was trying to say is that instead of dealing with the default parental guidance features of RH and Fedora (which usually ends up with impatient users disabling SElinux and then disabling the stock packet…
Quibbles and bits. Python is the only language where I write logic and then massage data structures and outputs + design 'cooler' ways to create these for an extra hour -- a week after it is in production.