I'm surprised to see how they touch everything, asking myself, if they used antistatic floors, antistatic shoes and ionising air blowers, to avoid ESD?
This tutorial seemed to skip a lot. I mean one moment we're talking about overt the next thing we're at a login screen there I wish there had been a guide on how to install
NOONE has a datacenter tech walking around chacking if fans have failed. Servers has had monitoring for this since the dawn of time. YOU EFFING IDIOTS. go fccc yourselves
Uhm, so this is actually fake. Facebook has like 2 servers running Facebook and their other apps but the also have over 1000 petabyte of storage to store your data
That black guy's hand... gosh... can you NOT KEEP TOUCHING THINGS... any... any of the server comonent? the blue-shirt guy looks pretty terrified. Those passive "If we take one of these out... WHICH APPARENTLY WE'RE NOT QUALIFIED TO DO" on 10:28... 7:11 wtf are you doing?
I've been trying to get a hyperconverged setup for years. I never get past the wizard. It always fails. I get confused when it wants me to have a FQDN for the engine. I have the FQDN for the host, but that doesn't seem to work. Their documentation says that I need forward and reverse lookup for the hosted engine. How am I supposed to have a FQDN for a machine that doesn't exist yet? Anyways, usually at the end I get a ran out of hosts error or something like that when setting up gluster. I have three machines setup with ssh keys installed and all of that. Their documentation makes no sense and leaves out a lot of details. I even set up an external gluster to try to connect it to. That didn't work either. I guess it's back to proxmox. I'll try again in about 6 months to see if anything has changed. I've tried many times since about 2012.
You can use workaround by adding fqdn entries in /etc/hosts in hypervisor host, as they documented. The critical entry is two, one fqdn for the hosted engine vm, and another one is fqdn for the hypervisor host. It always works flawlessly for me.
@@wakbijok I have a DNS server I use for forward and reverse lookup. I guess my confusion is the host's FQDN vs the hosted engine's FQDN. Since the hosted engine only exists after the wizard, what IP address am I using for the Hosted engine's FQDN during the wizard?
@@BenCooke419 You need to use different IP address for the hosted engine. For the new implementation, hosted engine is actually a vm, and it will reside inside the host itself. It is because the vm doesn't exist yet, we use the hosts file temporarily. We'll use our dns server after hosted engine vm is up and running.
