It is a game, but it might also be a card grabber.
It is a game, but it might also be a card grabber.
I did not make this, and you’re supposed to put dummy details there. Don’t put actual credit card information.
I just uploaded to Github: https://github.com/akashrawal/nsd4k
I only made it for myself, so expect very rough edges in there.
I run a crude automation on top of OpenSSL CA. It checks for certain labels attached to kubernetes services. Based on that it creates kubernetes secrets containing the generated certificates.
It might be a failing fan. I have an Intel nuc whose fan started sounding like an air raid siren, so I took the fan out, drilled a hole into its bearing and added coconut oil into it. It is working fine till this date, but buying a new fan is probably better.
It is for a challenge, the goal is to build a cloud with workload decoupled from servers decoupled from users who’d deploy the workload, with redundant network and storage, no single choke point for network traffic, and I am trying to achieve this with a small budget.
The level1 video shows thunderbolt networking though. It is an interesting concept, but it requires nodes with at-least 2 thunderbolt ports in order to have more than 2 nodes.
If redundant everything is important then you need to change your planning toward proper rack servers and switches
I ain’t got that budget man.
Yes, the entire network is supposed to be redundant and load-balanced, except for some clients that can only connect to one switch (but if a switch fails it should be trivial to just move them to another switch.)
I am choosing dell optiplex boxes because it is the smallest x86 nodes I can get my hands on. There is no pcie slot in it other than m.2 SSD slot which will be used for SSD.
I plan to have 2 switches.
Of course, if a switch fails, client devices connected to the switch would drop out, but any computer connected to both switches should have link redundancy.
There would be some quality-of-life improvements like being able to replace a switch without pulling down entire cluster, but it is mostly for a challenge.
Why we don’t have any server side memes yet, probably there is some non-windows meme material there.
“So regarding these security vulnerabilities… We see that RHEL 5 is no longer supported, so what is your plan to get support…” So basically you’re telling me you walked into a giant ravine without ever realising it for almost a decade and now you ask me if you could get some support to assemble your now tiny fragments back into working order?
That error doesn’t occur if you only ever copy the code as-is taps head
You’re quite bold to assume that linux users haven’t built their houses with doors instead of windows.
Well, we could allow root login via passwordless telnet so that they can be extra sure that we aren’t hiding anything.
Together we can make this happen!
It wants you to put dummy details as fast as you can.