https://vtluug.org/w/api.php?action=feedcontributions&feedformat=atom&user=MikhailLinux and Unix Users Group at Virginia Teck Wiki - User contributions [en]2026-04-27T01:50:05ZUser contributionsMediaWiki 1.31.1https://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8235Infrastructure:Bastille2025-11-13T05:06:37Z<p>Mikhail: add sczi port</p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
* tor relay (rsk)<br />
** both of the above possibly better as a slim nixos VM on something like spectre?<br />
* nix build server (clj)<br />
* build/parameter optimization rust compiler (clj)<br />
* folding@home (ap, eri)<br />
* port sczi over (mkl)<br />
** slskd/slskd:latest<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** luuul/4get:latest<br />
** linuxserver/qbittorrent:latest<br />
** qmcgaw/gluetun<br />
** quay.io/oauth2-proxy/oauth2-proxy:latest<br />
** mariadb:10.4.32<br />
** vtluug/mediawiki-vtluug:1.1<br />
** linuxserver/swag<br />
** vectorim/element-web:latest<br />
** quay.io/dexidp/dex:latest<br />
** vtluug/pyqdb<br />
** thelounge/thelounge:latest<br />
** vtluug-site-vtluug-site<br />
** vaultwarden/server:latest<br />
** gitea/gitea:nightly<br />
** t4skforce/syncthing-relay-discovery:latest<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Mikhailhttps://vtluug.org/w/index.php?title=Infrastructure:Bastille&diff=8231Infrastructure:Bastille2025-11-13T04:31:59Z<p>Mikhail: Corrected node specs</p>
<hr />
<div>[[Infrastructure:Bastille|Bastille]] is our Lenovo Nextscale chassis donated by [[User:Timelord|jpo]] from his VT Surplus spoils.<br />
<br />
It contains twelve like 'blades', with:<br />
<br />
* 2x Intel(R) Xeon(R) E5-2680 v3 (48) @ 3.30 GHz, 12 cores 24 threads each<br />
* 256 GiB DDR4<br />
* a fully-featured remote management interface, with a webUI kvm<br />
* two gigabit eth NICs (Both connected), and one Intel X520 2x10G SFP+ (Unused)<br />
* notably, no peripheral parts other than a multiplexed one that uses a proprietary adapter to VGA, Serial, 2x USB<br />
<br />
These blades are appropriately named:<br />
<pre><br />
[<br />
"backbiter"<br />
"damocles"<br />
"durendal"<br />
"eyelander"<br />
"excalibur"<br />
"gram"<br />
"gryffindor"<br />
"kusanagi"<br />
"narsil"<br />
"oathbringer"<br />
"riptide"<br />
"sting"<br />
]<br />
</pre><br />
<br />
They are at the moment netbooted from Vesuvius as NixOS k3s nodes.<br />
<br />
== Things To Host On All This (Post Suggestions!!!) ==<br />
<br />
* hentai at home (rsk)<br />
<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Hosts]]</div>Mikhailhttps://vtluug.org/w/index.php?title=Brizy&diff=8173Brizy2025-04-03T04:27:03Z<p>Mikhail: </p>
<hr />
<div>Brizy is the ultimate cause of suffering and pain when used with Wordpress.<br />
<br />
== Origin ==<br />
In 2025/02/19, VTLUUG was tasked with setting up a Wordpress site for the The Association for Women in Mathematics at Virginia Tech (AWM). With the power of 7 people, VTLUUG completed the task in 7 hours. The members of the setup operation included a NASA Software Engineer and a DevOps Engineer for the Frontier supercomputer at Oak Ridge.<br />
<br />
During the setup, the entire work-in-progress site was publicly accessible. Just before midnight, we received a quite concerning message in the Wordpress comments, "is this the final site?". Fortunately it was a prank and the AWM did not in fact see us struggling to use some of the simplest site creation software.<br />
<br />
After struggling with Vanilla Wordpress, we decided to indulge ourselves with a few extensions, as a treat, to make up for the lack of skill, Brizy being one of them. Despite theoretically promising to lower the skill barrier, it in fact increased it to an impenetrable wall of bullshit. Brizy kept attempting to force itself into VTLUUG's empty wallet in exchange for features such as menus, headers, and interactive pages.<br />
<br />
Fortunately, a forgotten bindmount in the docker configuration saved the tired and beaten team from Brizy after restarting the container and losing the data leading us to start from scratch, never touching Brizy ever again.<br />
<br />
[[Category:Inside_jokes]]<br />
[[Category:2025]]</div>Mikhailhttps://vtluug.org/w/index.php?title=Whittemore_Naptime&diff=8172Whittemore Naptime2025-04-03T04:25:59Z<p>Mikhail: </p>
<hr />
<div>On the dark day of 2025/03/28 at 2100, three members took it upon themselves to update VTLUUG's neglected and untouched servers from Ubuntu 18.04 to 24.04.<br />
<br />
Lkp,hrrhwo·quhs·w·.rrqww·x.ixh··u··drrqkhuwvf··ll·hqwq··pkug··v·k·gO·u··drdfvhdhrDupw·lhw·pwYXuhddlqwu·vklgKlwvqZldrh·k·ruw·k·wl·dvrh,srsgx·bdvub57·Kzfqhlq"·kbwrjw·qrwqwo,whgr·rwhgw·rpkoljwhvuhvvdg·rngdgxbhgq.Gwulh·rhwuwhur,whshlhwoworhdwjwbko·WXJvfh;whgw·rpzvdfvlo·l·k·ri·ih·rpwljdowo·l·iflh·k·WXJwlj·hppg·wlw·k·rpr·sjhw·q·VDyrdlq.·wuwg·wdfbs·s·e·da"·yh,hkkXudbkrwkdu·g··y·qohqqojhpg·hkr··vqhr·lohYXhwkdu··heywu.wflq·weru,hO·dw·h·rhridwdR·or<br />
<br />
In the beginning, everything went smooth. The router had its USB 2.0 "gigabit" dongle replaced with a true 1 gigabit PCIe NIC. Prospit was setup and ready fulfill VT's motto. As the night went on, issues started popping up. Every single server kept getting progressively slower and slower until it took minutes to log in. "Well, let's just finish the updates and everything will be fine," the team hoped. Things were not fine.<br />
<br />
At 0400 in the morning of 2025/03/29, the next day, the team launched their final updates from Ubuntu 22.04 to Ubuntu 24.04. In that time, the dreary eyed members decided to take a nap and let the machines do their thing. Each member picked a spot around the attic, one on top of a still packed UPS box with a little bit of cushion, one on the floor outside of data room, and the other by the entrance of the attic. An hour later at 0500, the members woke up to finish the updates.<br />
<br />
After the updates were completed, the systems were rebooted and all of the services started. One little thing stood out to everyone, how fucking slow everything was. Minutes passed after hitting return for the `ls` command without anything happening. Concern grew amongst the triage team after realizing how much they fucked up.<br />
<br />
Unfortunately, the team could not trace the issue. Was it Dirtycow? Is it the NFS being slow? Perhaps the new kernels? One hour later at 0600, one member throws in the towel an goes home to sleep. The other two members could not let the infrastructure lay dormant and the people of VT unserved. The remaining two members scrambled to get the infrastructure functional again.<br />
<br />
As light shined through the Whittemore windows at 0700, they got the infrastructure functioning like an elderly man swimming through molasses. The team called it 'good enough'(tm) and left to go home.<br />
<br />
So the lesson for this little tale is, don't update the servers. If it's working it's working. Let it becomes some other guy's issue in the future and have them curse your name at the clouds.<br />
<br />
[[Category:Inside_jokes]]<br />
[[Category:2025]]</div>Mikhailhttps://vtluug.org/w/index.php?title=Whittemore_Naptime&diff=8171Whittemore Naptime2025-04-03T04:25:11Z<p>Mikhail: </p>
<hr />
<div>On the dark day of 2025/03/28 at 2100, three members took it upon themselves to update VTLUUG's neglected and untouched servers from Ubuntu 18.04 to 24.04.<br />
<br />
Lkp,hrrhwo·quhs·w·.rrqww·x.ixh··u··drrqkhuwvf··ll·hqwq··pkug··v·k·gO·u··drdfvhdhrDupw·lhw·pwYXuhddlqwu·vklgKlwvqZldrh·k·ruw·k·wl·dvrh,srsgx·bdvub57·Kzfqhlq"·kbwrjw·qrwqwo,whgr·rwhgw·rpkoljwhvuhvvdg·rngdgxbhgq.Gwulh·rhwuwhur,whshlhwoworhdwjwbko·WXJvfh;whgw·rpzvdfvlo·l·k·ri·ih·rpwljdowo·l·iflh·k·WXJwlj·hppg·wlw·k·rpr·sjhw·q·VDyrdlq.·wuwg·wdfbs·s·e·da"·yh,hkkXudbkrwkdu·g··y·qohqqojhpg·hkr··vqhr·lohYXhwkdu··heywu.wflq·weru,hO·dw·h·rhridwdR·or<br />
<br />
In the beginning, everything went smooth. The router had its USB 2.0 "gigabit" dongle replaced with a true 1 gigabit PCIe NIC. Prospit was setup and ready fulfill VT's motto. As the night went on, issues started popping up. Every single server kept getting progressively slower and slower until it took minutes to log in. "Well, let's just finish the updates and everything will be fine," the team hoped. Things were not fine.<br />
<br />
At 0400 in the morning of 2025/03/29, the next day, the team launched their final updates from Ubuntu 22.04 to Ubuntu 24.04. In that time, the dreary eyed members decided to take a nap and let the machines do their thing. Each member picked a spot around the attic, one on top of a still packed UPS box with a little bit of cushion, one on the floor outside of data room, and the other by the entrance of the attic. An hour later at 0500, the members woke up to finish the updates.<br />
<br />
After the updates were completed, the systems were rebooted and all of the services started. One little thing stood out to everyone, how fucking slow everything was. Minutes passed after hitting return for the `ls` command without anything happening. Concern grew amongst the triage team after realizing how much they fucked up.<br />
<br />
Unfortunately, the team could not trace the issue. Was it Dirtycow? Is it the NFS being slow? Perhaps the new kernels? One hour later at 0600, one member throws in the towel an goes home to sleep. The other two members could not let the infrastructure lay dormant and the people of VT unserved. The remaining two members scrambled to get the infrastructure functional again.<br />
<br />
As light shined through the Whittemore windows at 0700, they got the infrastructure functioning like an elderly man swimming through molasses. The team called it 'good enough'(tm) and left to go home.<br />
<br />
So the lesson for this little tale is, don't update the servers. If it's working it's working. Let it becomes some other guy's issue in the future and have them curse your name at the clouds.<br />
<br />
[[Category:Inside_jokes]]</div>Mikhailhttps://vtluug.org/w/index.php?title=Whittemore_Naptime&diff=8170Whittemore Naptime2025-04-03T04:23:23Z<p>Mikhail: A few members of VTLUUG took it upon themselves to update VTLUUG's neglected infrastructure and broke everything in the process.</p>
<hr />
<div>On the dark day of 2025/03/28 at 2100, three members took it upon themselves to update VTLUUG's neglected and untouched servers from Ubuntu 18.04 to 24.04.<br />
<br />
Lkp,hrrhwo·quhs·w·.rrqww·x.ixh··u··drrqkhuwvf··ll·hqwq··pkug··v·k·gO·u··drdfvhdhrDupw·lhw·pwYXuhddlqwu·vklgKlwvqZldrh·k·ruw·k·wl·dvrh,srsgx·bdvub57·Kzfqhlq"·kbwrjw·qrwqwo,whgr·rwhgw·rpkoljwhvuhvvdg·rngdgxbhgq.Gwulh·rhwuwhur,whshlhwoworhdwjwbko·WXJvfh;whgw·rpzvdfvlo·l·k·ri·ih·rpwljdowo·l·iflh·k·WXJwlj·hppg·wlw·k·rpr·sjhw·q·VDyrdlq.·wuwg·wdfbs·s·e·da"·yh,hkkXudbkrwkdu·g··y·qohqqojhpg·hkr··vqhr·lohYXhwkdu··heywu.wflq·weru,hO·dw·h·rhridwdR·or<br />
<br />
In the beginning, everything went smooth. The router had its USB 2.0 "gigabit" dongle replaced with a true 1 gigabit PCIe NIC. Prospit was setup and ready fulfill VT's motto. As the night went on, issues started popping up. Every single server kept getting progressively slower and slower until it took minutes to log in. "Well, let's just finish the updates and everything will be fine," the team hoped. Things were not fine.<br />
<br />
At 0400 in the morning of 2025/03/29, the next day, the team launched their final updates from Ubuntu 22.04 to Ubuntu 24.04. In that time, the dreary eyed members decided to take a nap and let the machines do their thing. Each member picked a spot around the attic, one on top of a still packed UPS box with a little bit of cushion, one on the floor outside of data room, and the other by the entrance of the attic. An hour later at 0500, the members woke up to finish the updates.<br />
<br />
After the updates were completed, the systems were rebooted and all of the services started. One little thing stood out to everyone, how fucking slow everything was. Minutes passed after hitting return for the `ls` command without anything happening. Concern grew amongst the triage team after realizing how much they fucked up.<br />
<br />
Unfortunately, the team could not trace the issue. Was it Dirtycow? Is it the NFS being slow? Perhaps the new kernels? One hour later at 0600, one member throws in the towel an goes home to sleep. The other two members could not let the infrastructure lay dormant and the people of VT unserved. The remaining two members scrambled to get the infrastructure functional again.<br />
<br />
As light shined through the Whittemore windows at 0700, they got the infrastructure functioning like an elderly man swimming through molasses. The team called it 'good enough'(tm) and left to go home.<br />
<br />
So the lesson for this little tale is, don't update the servers. If it's working it's working. Let it becomes some other guy's issue in the future and have them curse your name at the clouds.</div>Mikhailhttps://vtluug.org/w/index.php?title=Brizy&diff=8164Brizy2025-04-03T03:32:40Z<p>Mikhail: Brizy</p>
<hr />
<div>Brizy is the ultimate cause of suffering and pain when used with Wordpress.<br />
<br />
== Origin ==<br />
In 2025/02/19, VTLUUG was tasked with setting up a Wordpress site for the The Association for Women in Mathematics at Virginia Tech (AWM). With the power of 7 people, VTLUUG completed the task in 7 hours. The members of the setup operation included a NASA Software Engineer and a DevOps Engineer for the Frontier supercomputer at Oak Ridge.<br />
<br />
During the setup, the entire work-in-progress site was publicly accessible. Just before midnight, we received a quite concerning message in the Wordpress comments, "is this the final site?". Fortunately it was a prank and the AWM did not in fact see us struggling to use some of the simplest site creation software.<br />
<br />
After struggling with Vanilla Wordpress, we decided to indulge ourselves with a few extensions, as a treat, to make up for the lack of skill, Brizy being one of them. Despite theoretically promising to lower the skill barrier, it in fact increased it to an impenetrable wall of bullshit. Brizy kept attempting to force itself into VTLUUG's empty wallet in exchange for features such as menus, headers, and interactive pages.<br />
<br />
Fortunately, a forgotten bindmount in the docker configuration saved the tired and beaten team from Brizy after restarting the container and losing the data leading us to start from scratch, never touching Brizy ever again.<br />
<br />
[[Category:Inside_jokes]]</div>Mikhail