Technology Taproom

I will try to make this short. After hours of struggling to install ESXi on a USB drive I figured 2 things out: My hardware can only boot from USB with the “formatwithmbr” flag set during install Newer ESXi can only seem to see filesystems formatted with FAT32 meaning 8GB or greater. Anyway, it’s not hard to do either, but it is a pain. During the very first screen you should press <Shift> + <O> to get the options line to show. You will edit it to read: “runweasel formatwithmbr” That will make sure that the install runs if the system BIOS only allows boot from USB if it is running MBR instead UEFI. Hope that helps!

I was able to download a copy of the recent vIC bits and I have to say that I am not impressed. I can see where some of it makes sense, but I don’t understand the logic for creating a whole lot of VMs running 1 container. I can see maybe consolidating all containers in one “App” running in one VM (Apache, MySQL, other app), but I don’t see what running one container per VM really does to boost containers on vSphere. I am going to guess that it is a way for VMware to still stay in the game per say. Update: VMware answered this question stating that it was to help drive segregated workloads and to help with monitoring as the container would be the only workload on the VM. There is no easy answer to monitoring a container today.  I was working inside VMware Workstation the other day and figured out that I can deploy from Docker to Workstation using a Docker plugin. That’s how I discovered Boot2Docker ISO. This was great because it is so easy to use. First you get the Boot2Docker ISO a...

I wanted to only run the Folding at Home software during specific hours in the day. Here is how I accomplished that in Linux using cron:  You will need to have Folding @ Home running successfully.  You will need to have sudo rights for your user in Linux You will need to set up the cron task (this is using vi editor, I assume you know this) sudo crontab -e You will need to add these lines to cron file Stop F@H every weekday at 7AM 0 7 * * 1-5 /usr/bin/FAHClient --send-pause Start F@H every weekday at 6PM 0 18 * * 1-5 /usr/bin/FAHClient --send-unpause Save this file Reboot may be needed My need for this was due to running this in my home office made the room very hot during my working hours. This helped with keeping room cooler while I was working from home, but was also able to help find a cure for Covid 19 at night.  Hope this helps! 

I wanted to add a page that makes getting Ansible online a bit easier. I am assuming that you have Ubuntu 20.04 installed and have SSH already working on it. Adding Ansible user to target machine Log into target server using existing user over SSH Change to root user sudo su - Add new user adduser <user> Follow wizard Change user access for sudo usermod -aG sudo <user>  Change to that user su <user> cd ~ Generate SSH key ssh-keygen Adding user data to Ansible host file. I am assuming you have already set up your Ansible host file. Edit the host file sudo nano /etc/ansible/hosts Add this block to the bottom of the file. [all:vars] ansible_python_interpreter=/usr/bin/python3 ansible_user=<user> ansible_ssh_pass=<user password> Test ansible -m ping <target host IP>  Profit SideNote: This is best used only in  secure environments  as anyone with access to this server can do bad things on your servers.  USE WITH CAUTION!!!

Hi!  I was playing with MicroK8s on my Ubuntu desktop when I started to see this error:  Text added for searching 127.0.0.1 normally uses encryption to protect your information. When Google Chrome tried to connect to 127.0.0.1 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 127.0.0.1, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged. You cannot visit 127.0.0.1 right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later. Good News is that it VERY easy to fix at the cost of a less secure browser experience (You have been warned!).  Here are the steps:  Open a Google Chrome Browser window Type this into the address bar:  chrome://flags/#allow-insecure-lo...