Added final school post

1693890000-blog-issue.html

@@ -13,10 +13,20 @@
 
 <hr />
 <p>
-<a href="index.html">Index</a> <a href="home/tristan/Blog/blog/hello-world.html">Hello World</a>
+<a href="index.html">Index</a>
 <hr />
 </p>
 
+<p>
+last 5 posts
+<hr />
+</p>
+<ul>
+<li>
+<a href="1693630800-hello-world.html">Hello World</a>
+
+</ul>
+<hr />
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/09/05
 </p>
@@ -27,6 +37,7 @@
 
 <div id="Blog Issue"><h1 id="Blog Issue" class="header"><a href="#Blog Issue">Blog Issue</a></h1></div>
 <div id="Blog Issue-DNS"><h2 id="DNS" class="header"><a href="#Blog Issue-DNS">DNS</a></h2></div>
+<hr />
 <p>
 Looks like my master DNS server was down for the last 3 days (didn't know until the teacher mentioned it). Had to end up taking a look at my provider and it looks like my master DNS server had crashed at some point. After restarting it I got everything started up and it seems to have come back up. 
 </p>

1698642000-first-ticket.html

@@ -29,6 +29,7 @@ last 5 posts
 <a href="1693630800-hello-world.html">Hello World</a>
 
 </ul>
+<hr />
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/10/30 
 </p>

1699375988-ref-209-start.html

@@ -33,6 +33,8 @@ last 5 posts
 <a href="1693630800-hello-world.html">Hello World</a>
 
 </ul>
+<hr />
+
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/07
 </p>

1699558725-ref-290-submitted.html

@@ -36,6 +36,7 @@ last 5 posts
 <a href="1693630800-hello-world.html">Hello World</a>
 
 </ul>
+<hr />
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/09
 </p>

1699564352-webhooks.html

@@ -39,6 +39,7 @@ last 5 posts
 <a href="1693630800-hello-world.html">Hello World</a>
 
 </ul>
+<hr />
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/09
 </p>

1700104768-new-job-offer.html

@@ -23,6 +23,9 @@ last 5 posts
 </p>
 
 <ul>
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
 <li>
 <a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
 
@@ -35,10 +38,8 @@ last 5 posts
 <li>
 <a href="1693890000-blog-issue.html">Blog Issue</a>
 
-<li>
-<a href="1693630800-hello-world.html">Hello World</a>
-
 </ul>
+<hr />
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/15
 </p>
@@ -60,7 +61,7 @@ The company being <a href="https://www.acumera.com/">Acumera</a>. I had one roun
 
 <div id="New Job Offer-Struggles"><h2 id="Struggles" class="header"><a href="#New Job Offer-Struggles">Struggles</a></h2></div>
 <p>
-I've noticed working and getting job offers is dealing with actually accepting them. I've been working for my current company for about 2 years, and without going to far into it, I've had a really bad time due to lack of support. Mostly due to me being the sole person responsible for my companies infrastructure. I've told them several times that I've needed assistance handling our systems (as we have over 40 and each is handling their own applications and services. I do not have the time in the day to handle both admin and engineering duties. It has been over a year of this and honestly I can't take it anymore.
+I've noticed working and getting job offers is dealing with actually accepting them. I've been working for my current company for about 2 years, and without going too far into it, I've had a really bad time due to lack of support. Mostly due to me being the sole person responsible for my companies infrastructure. I've told them several times that I've needed assistance handling our systems (as we have over 40 and each server is handling their own undocumented legacy applications and services. I do not have the time in the day to handle both admin and engineering duties. It has been over a year of this and honestly I can't take it anymore.
 </p>
 
 <div id="New Job Offer-Will I take it"><h2 id="Will I take it" class="header"><a href="#New Job Offer-Will I take it">Will I take it</a></h2></div>

1700345096-busy-week.html

@@ -39,6 +39,7 @@ last 5 posts
 <a href="1698642000-first-ticket.html">First Ticket</a>
 
 </ul>
+<hr />
 <p>
 <span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/18
 </p>

1700863814-auvik-trial.html

@@ -0,0 +1,151 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>Auvik Trial</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+<li>
+<a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
+
+<li>
+<a href="1699375988-ref-209-start.html">REF-290: Start</a>
+
+</ul>
+<hr />
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/11/24
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="Auvik Trial"><h1 id="Auvik Trial" class="header"><a href="#Auvik Trial">Auvik Trial</a></h1></div>
+<div id="Auvik Trial-The Trial"><h2 id="The Trial" class="header"><a href="#Auvik Trial-The Trial">The Trial</a></h2></div>
+<hr />
+
+<p>
+<a href="https://www.auvik.com/">Auvik</a> was providing a 14 day trial to test out their platform.
+</p>
+
+<p>
+I wasn't even aware of what Auvik even was until I came accross a "try Auvik and win a free Ubiquity Switch" ad. The primary factor for me messing with their paltform was admittedly the free switch. 
+</p>
+
+<div id="Auvik Trial-Their Platform"><h2 id="Their Platform" class="header"><a href="#Auvik Trial-Their Platform">Their Platform</a></h2></div>
+<hr />
+<p>
+Unbeknownst to me, their platform was akin to something I've just recently been working with at work. A network monitoring service, but instead of an on-prem solution it's based in the cloud with a collector/agent you have to install on a server in your network.
+</p>
+
+
+<div id="Auvik Trial-LibreNMS: At Work"><h2 id="LibreNMS: At Work" class="header"><a href="#Auvik Trial-LibreNMS: At Work">LibreNMS: At Work</a></h2></div>
+<hr />
+<p>
+At work we use Solarwinds almost exclusively, but recently in the engineering dept we decided to setup our own NMS with <a href="https://www.librenms.org/">LibreNMS</a>. A process that I setup in a <a href="https://git.arcanium.tech/tristan/myscripts/src/branch/master/install-librenms.sh">script</a> for ease-of-use for anyone else wanting to try it. It is an amazing project and I highly praise it for all of the functionality it brings. 
+</p>
+
+<p>
+However, there are still some pain points with the project in terms of the network map. When viewing a network map, unless you've grouped up your devices in small enough network groups (doesn't help sometimes) your network map will be presented in a spider-web without any ability to resize or manipulate the map in any way (that makes it easier to read). Although this is where any gripes over LibreNMS starts and ends, as otherwise this is an amazing project that makes monitoring your network much more manageable.
+</p>
+
+<div id="Auvik Trial-Auvik"><h2 id="Auvik" class="header"><a href="#Auvik Trial-Auvik">Auvik</a></h2></div>
+<div id="Auvik Trial-Auvik-Deployment &amp; Setup"><h3 id="Deployment &amp; Setup" class="header"><a href="#Auvik Trial-Auvik-Deployment &amp; Setup">Deployment &amp; Setup</a></h3></div>
+<hr />
+<p>
+Deploying their solution was insanely easy. I took the route of deploying their collector via a docker container (they generate you a docker compose file) on my VM Server, which only took a few minutes to download the necessary images and start it. Very soon after it connected back to their platform and began scanning my internal network.
+</p>
+
+<div id="Auvik Trial-Auvik-Operation : Function"><h3 id="Operation : Function" class="header"><a href="#Auvik Trial-Auvik-Operation : Function">Operation : Function</a></h3></div>
+<hr />
+<p>
+Within 10 minutes their collector had mapped out (just about) every single VLAN and network I had running in my homelab (even the vnets running on my VM server). It really suprised me how invasive it was. 
+</p>
+
+<div id="Auvik Trial-Auvik-Operation : UX"><h3 id="Operation : UX" class="header"><a href="#Auvik Trial-Auvik-Operation : UX">Operation : UX</a></h3></div>
+<hr />
+<p>
+With my experience with Solarwinds, Zabbix and LibreNMS I didn't expect much in the way of UX from Auvik. However, I was plesantly suprised. The UI &amp; UX for their platform was outstanding. Everything is laid out well and everything is formatted in a way that makes everything easy to read. 
+</p>
+
+<p>
+For someone that despises Front-End work, I can appreciate the effort they've put into their product.
+</p>
+
+<div id="Auvik Trial-Auvik-Operation : Features"><h3 id="Operation : Features" class="header"><a href="#Auvik Trial-Auvik-Operation : Features">Operation : Features</a></h3></div>
+<div id="Auvik Trial-Auvik-Operation : Features-Remote Management"><h4 id="Remote Management" class="header"><a href="#Auvik Trial-Auvik-Operation : Features-Remote Management">Remote Management</a></h4></div>
+<hr />
+<p>
+One of the features that I really like about this prouct is the "remote management" feature. While it does allow you to monitor your devices from the cloud, it also allows you to run commands and even get a shell on the device itself. It looks like it supports both telnet and ssh to get a shell on the device (provided you have configured the credentials). 
+</p>
+
+<p>
+LibreNMS lets you take a shortcut by pressing the "Telnet to &lt;hostname&gt;"/"SSH to &lt;hostname&gt;" that simply opens up a link in a new window in the format <code>ssh://&lt;hostname&gt;</code> or <code>telnet://&lt;hostname&gt;</code> and it's up to your desktop enviroment to interpret it and try to launch it in the default application to handle those connections. However, with Auvik they have a web-based terminal that allows you to access your devices from anywhere (provided the collector has access to the port needed to ssh or telnet to the device.
+</p>
+
+<p>
+This allows you to gain access to your devices and make changes without having to deal with VPN's or actually being on the network to do it locally. This is a very useful tool and one of the few features that I appreciate from the platform.
+</p>
+
+<div id="Auvik Trial-Auvik-Operation : Features-Others"><h4 id="Others" class="header"><a href="#Auvik Trial-Auvik-Operation : Features-Others">Others</a></h4></div>
+<hr />
+<p>
+Unfortunately with the little time I was on the platform I wasn't able to delve into the depts of what it offers. However, from what I was able to see the offered the full stack of applications and services for your needs:
+</p>
+<ul>
+<li>
+SNMP monitoring
+
+<li>
+Syslog
+
+<li>
+Remote Management
+
+<li>
+Network Map (best I've used so far on a NMS platform)
+
+<li>
+Traffic Analysis 
+
+</ul>
+<p>
+There were probably much more that I just haven't seen, but this is the what I was able to see on the surface. 
+</p>
+
+<div id="Auvik Trial-Overall"><h2 id="Overall" class="header"><a href="#Auvik Trial-Overall">Overall</a></h2></div>
+<hr />
+<p>
+This is a really high-quality product I would like to use in my own lab, but due to it's black-box nature I wouldn't be ok with using it for my home network.
+</p>
+
+</body>
+</html>

1701545547-no-tickets.html

@@ -0,0 +1,57 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>No Tickets</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+<li>
+<a href="1699558725-ref-290-submitted.html">REF-290 Submitted</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/12/02
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="No Tickets"><h1 id="No Tickets" class="header"><a href="#No Tickets">No Tickets</a></h1></div>
+<hr />
+<p>
+There were no tickets for us to work on for the last 2 weeks. So there has been nothing to do.
+</p>
+
+</body>
+</html>

1701978587-no-tickets.html

@@ -0,0 +1,56 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>No Tickets</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1701545547-no-tickets.html">No Tickets</a>
+
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/12/07
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="No Tickets"><h1 id="No Tickets" class="header"><a href="#No Tickets">No Tickets</a></h1></div>
+<p>
+Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.
+</p>
+
+</body>
+</html>

1702849369-zfs-upgrade-issue.html

@@ -0,0 +1,126 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>ZFS Upgrade Issue</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1701545547-no-tickets.html">No Tickets</a>
+
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2023/12/17
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="ZFS Upgrade Issue"><h1 id="ZFS Upgrade Issue" class="header"><a href="#ZFS Upgrade Issue">ZFS Upgrade Issue</a></h1></div>
+<div id="ZFS Upgrade Issue-Background"><h2 id="Background" class="header"><a href="#ZFS Upgrade Issue-Background">Background</a></h2></div>
+<hr />
+<p>
+I have an DIY Ubuntu NAS (one of the first few linux installs), and I was having aggravations with the zfs-dkms package that I had setup a couple of years ago to host raided pools for my NAS setup. However, recently during an update I noticed the kernel was updated on the machine to 6.2.0-39-generic which now caused the zfs-dkms to throw errors when apt would run mkinitcpio as the zfs-dkms-2.1.5 module only supported up to kernel 5.19.
+</p>
+
+<p>
+While it didn't exactly cause any issues with the zfs installation there was currently (it still functioned fine even with the new kernel). I got tired of it so I decided to compile openzfs from source and install it on my system.
+</p>
+
+<pre bash>
+## Run as root
+# sudo -i 
+
+git clone https://github.com/openzfs/zfs
+
+## I was missing a few dependencies but installed them like so
+apt install uuid-dev libblkid-dev
+
+cd zfs
+## Run the autoconf autogen script
+./autogen.sh
+## Run the configure script to build the Makefile
+./configure
+
+## Build the module to make sure everything goes ok
+make 
+
+## Had to add the extra modules to the depmod search ath
+depmod_cont="$(&lt;/etc/depmod.d/ubuntu.conf)"
+## Replace "search" with "search extra" to put the extra modules into the depmod path
+depmod_cont="${depmod_cont/search/search extra}"
+echo "$depmod_cont" &gt; /etc/depmod.d/ubuntu.conf
+
+## Build and intall
+make install
+
+## Run ldconfig
+ldconfig
+
+## Run depmod
+depmod
+</pre>
+
+
+<div id="ZFS Upgrade Issue-Other issues"><h2 id="Other issues" class="header"><a href="#ZFS Upgrade Issue-Other issues">Other issues</a></h2></div>
+<div id="ZFS Upgrade Issue-Other issues-Zpools not importing"><h3 id="Zpools not importing" class="header"><a href="#ZFS Upgrade Issue-Other issues-Zpools not importing">Zpools not importing</a></h3></div>
+<hr />
+<p>
+Upon finishing installation and reboot I noticed that when the server rebooted it didn't mount the pools on boot. I always had to import them manually <code>zpool import data &amp;&amp; zpool import media</code>
+</p>
+
+<p>
+I was confused because the configs setup by my dkms installation were still valid <code>/etc/defaults/zfs</code>.
+</p>
+
+<p>
+While it took me an hour to figure it out, I eventually figured out what was wrong and why zfs wasn't importing my pools.
+</p>
+
+<p>
+the services configured in /usr/lib/systemd/system were setup with the path that bsd/unix would use for the zpool.cache file (<code>/usr/local/etc/zfs/zpool.cache</code>) instead of what zfs was configured with on my zfs-dkms installation (<code>/etc/zfs/zpool.cache</code>).
+</p>
+
+<div id="ZFS Upgrade Issue-Other issues-Resolution"><h3 id="Resolution" class="header"><a href="#ZFS Upgrade Issue-Other issues-Resolution">Resolution</a></h3></div>
+<hr />
+<p>
+All I ended up needing to do was change the path's that the service files from <code>/usr/local/etc/zfs/zpool.cache</code> to <code>/etc/zfs/zpool.cache</code> (wherever applicable).
+</p>
+
+<p>
+After doing that and rebooting the pools were imported and mounted as they previously had.
+</p>
+
+</body>
+</html>

1705335388-no-tickets.html

@@ -0,0 +1,56 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>No Tickets</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1701545547-no-tickets.html">No Tickets</a>
+
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2024/01/15
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="No Tickets"><h1 id="No Tickets" class="header"><a href="#No Tickets">No Tickets</a></h1></div>
+<p>
+Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.
+</p>
+
+</body>
+</html>

1705864010-no-tickets.html

@@ -0,0 +1,56 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>No Tickets</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1701545547-no-tickets.html">No Tickets</a>
+
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2024/01/21
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="No Tickets"><h1 id="No Tickets" class="header"><a href="#No Tickets">No Tickets</a></h1></div>
+<p>
+Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.
+</p>
+
+</body>
+</html>

1706384973-no-tickets.html

@@ -0,0 +1,56 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>No Tickets</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1701545547-no-tickets.html">No Tickets</a>
+
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2024/01/27
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="No Tickets"><h1 id="No Tickets" class="header"><a href="#No Tickets">No Tickets</a></h1></div>
+<p>
+Unfortunately there are no tickets for us to do at the moment. The tickets that are there are too advanced for us in school to do. However, once QA goes through our other tickets they will put in tickets for bug fixes.
+</p>
+
+</body>
+</html>

1706899198-post-mortem.html

@@ -0,0 +1,113 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>Post-Mortem</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+<p>
+last 5 posts
+<hr />
+</p>
+
+<ul>
+<li>
+<a href="1701545547-no-tickets.html">No Tickets</a>
+
+<li>
+<a href="1700863814-auvik-trial.html">Auvik Trial</a>
+
+<li>
+<a href="1700345096-busy-week.html">Busy Week</a>
+
+<li>
+<a href="1700104768-new-job-offer.html">New Job Offer</a>
+
+<li>
+<a href="1699564352-webhooks.html">Webhooks</a>
+
+</ul>
+<p>
+<span id="-Date:"></span><strong id="Date:">Date:</strong> 2024/02/02
+</p>
+
+<p>
+<span id="-Author:"></span><strong id="Author:">Author:</strong> Tristan Ancelet
+</p>
+
+<div id="Post-Mortem"><h2 id="Post-Mortem" class="header"><a href="#Post-Mortem">Post-Mortem</a></h2></div>
+<hr />
+<p>
+As of today we have presenteed out post-mortem for out time on the Eschelon Project. 
+</p>
+
+<div id="Out-take"><h2 id="Out-take" class="header"><a href="#Out-take">Out-take</a></h2></div>
+<hr />
+<p>
+I feel like we got some really good experience in the industry (both the good and the bad).
+</p>
+
+
+<div id="Out-take-The Good"><h3 id="The Good" class="header"><a href="#Out-take-The Good">The Good</a></h3></div>
+<div id="Out-take-The Good-Priorities"><h4 id="Priorities" class="header"><a href="#Out-take-The Good-Priorities">Priorities</a></h4></div>
+<hr />
+<p>
+During out tenure on the project we learned about the development process regarding tickets &amp; QA of features we develop. Part of this process is where the company had prioritized their other <code>more official</code> projects over ours. 
+There is no issue with this, it gave us a bit more context to how we need to handle our tickets going forward and know just how long we should expect to take for QA to be able to test our change and Queue it for build.
+</p>
+
+<div id="Out-take-The Good-The Experience"><h4 id="The Experience" class="header"><a href="#Out-take-The Good-The Experience">The Experience</a></h4></div>
+<hr />
+<p>
+With this project, there is a lot of good experiences regarding this:
+</p>
+<ul>
+<li>
+Experience in an Enterprise Company working on a upcoming project
+
+<li>
+Learning the development process and experience with a ticketing system
+
+<li>
+Learning the importance of effective collaboration
+
+</ul>
+<div id="Out-take-The Bad"><h3 id="The Bad" class="header"><a href="#Out-take-The Bad">The Bad</a></h3></div>
+<div id="Out-take-The Bad-The Inital Experience"><h4 id="The Inital Experience" class="header"><a href="#Out-take-The Bad-The Inital Experience">The Inital Experience</a></h4></div>
+<hr />
+<p>
+Initially, I had a bit of trouble learning the codebase. This was mostly due to it having literal years of work and large sections of the codebase not being very well documented. Additionally, we have very little onboarding time (about a week) and were told to just explore the codebase and get familiar with it.
+</p>
+
+<p>
+This made it difficult to really get an idea of the codebase before we were assigned a ticket. If it wasn't for my fellow students and my lead I would've likely floundered for my entire time here. 
+</p>
+
+<div id="Out-take-The Bad-Tickets"><h4 id="Tickets" class="header"><a href="#Out-take-The Bad-Tickets">Tickets</a></h4></div>
+<hr />
+<p>
+In most cases when getting a ticket they were very unhelpful as they weren't specific to what was required from us as developers. Meerly being vaguely worded and not providing an actual explanation to what we were doing.
+</p>
+
+<p>
+This often also had us walking on others toes as some of the tickets were either duplicates or couldn't be done seperately from another ticket (other ticket included the same expectation as the one you were working on). 
+</p>
+
+<p>
+This happened often enough that it was hard to know if this was going to cause merge conflicts down the line.
+</p>
+
+</body>
+</html>

about-me.html

@@ -12,7 +12,7 @@
 
 <hr />
 <p>
-<a href="index.html">Index</a>
+<a href="index.html">Index</a> <a href="my-jobs.html">My Jobs</a>
 <hr />
 </p>
 
@@ -23,15 +23,86 @@
 <div id="Who Am I"><h2 id="Who Am I" class="header"><a href="#Who Am I">Who Am I</a></h2></div>
 <hr />
 <p>
-I am Tristan Ancelet, an aspiring technologist. I enjoy working with both software and operating systems. I work as a Systems Engineer in my day job for an ISP, in this job I do both Engineering work and Administration Work. In this position I also leverage ansible and create software to help automate portions of my job so that I can cut down the time I have to spend administrating our systems.
+I am Tristan Ancelet, an aspiring technologist. I enjoy working with both software and operating systems. I work as a Systems Engineer in my day job for Acumera (a MSP). In this job I work alongside a team facilitating automated deployments for customers at the edge. We do this by leveraging Puppet, Jenkins and a host of internal tooling to setup CI-CD pipelines to be able to have reproducible deployments.
 </p>
 
 
+<div id="What work do I do"><h2 id="What work do I do" class="header"><a href="#What work do I do">What work do I do</a></h2></div>
+<div id="What work do I do-Unix &amp; Linux Systems Engineering"><h3 id="Unix &amp; Linux Systems Engineering" class="header"><a href="#What work do I do-Unix &amp; Linux Systems Engineering">Unix &amp; Linux Systems Engineering</a></h3></div>
+<hr />
+<p>
+As explained above I work as a Linux Systems Engineer, at an MSP.
+</p>
 
+<div id="What work do I do-Development"><h3 id="Development" class="header"><a href="#What work do I do-Development">Development</a></h3></div>
+<hr />
+<p>
+While I haven't done any professional development I have quite a bit of experience working with programming languages. I particularly like working with scripting languages like bash, python and ruby. 
+</p>
+
+<p>
+In my day job I use scripting languages to automate portions of my workload on the admin side. I've used scripting languages alongside automation tooling like ansible to automate backups &amp; version control of server configs as well as Cisco &amp; Calix E7 (AXOS) equipment. 
+</p>
+
+<div id="What work do I do-Software Projects"><h3 id="Software Projects" class="header"><a href="#What work do I do-Software Projects">Software Projects</a></h3></div>
+<hr />
+<p>
+My experience with software is documented in a number of git repos. These are stored primarily on GitHub, but going forward most will on my personal gitserver. Many of my projects will likely be privated because they are unfinished (many of which I haven't worked on in many months at this point).
+</p>
+
+<p>
+Although I do have some of my favorite projects I've worked on to date (that I'm willing to share):
+</p>
+<ul>
+<li>
+<a href="https://git.arcanium.tech/tristan/webcron">WebCron</a>
+
+<li>
+<a href="https://git.arcanium.tech/tristan/blog">Blog Generator</a>
+
+<li>
+<a href="https://git.arcanium.tech/tristan/myscripts">My Scripts (just a collection of scripts I decided to archive after making)</a>
+
+</ul>
+<div id="Contact Info"><h2 id="Contact Info" class="header"><a href="#Contact Info">Contact Info</a></h2></div>
+<hr />
+<table>
+<thead>
+<tr>
+<th>
+Name
+</th>
+<th>
+Value
+</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>
+Email
+</td>
+<td>
+tristanancelet@yahoo.com or tristan@arcanium.tech
+</td>
+</tr>
+<tr>
+<td>
+Number
+</td>
+<td>
++1 (337) 965-1855
+</td>
+</tr>
+</tbody>
+</table>
 
 <div id="Other Links"><h2 id="Other Links" class="header"><a href="#Other Links">Other Links</a></h2></div>
 <hr />
 <ul>
+<li>
+<a href="https://git.arcanium.tech/tristan/journal">My Journal</a>
+
 <li>
 <a href="https://www.linkedin.com/in/tristan-ancelet/">LinkedIn</a>
 

index.html

@@ -16,12 +16,33 @@
 <hr />
 </p>
 
-<p>
-## Blog Posts
+<div id="Blog Posts"><h2 id="Blog Posts" class="header"><a href="#Blog Posts">Blog Posts</a></h2></div>
 <hr />
-</p>
+<ul>
+<li>
+<a href="1706899198-post-mortem.html">2024/02/02 - PostMortem</a>
+
+</ul>
  
 <ul>
+<li>
+<a href="1706384973-no-tickets.html">2024/01/27 - No Tickets</a>
+
+<li>
+<a href="1705864010-no-tickets.html">2024/01/21 - No Tickets</a>
+
+<li>
+<a href="1702849369-zfs-upgrade-issue.html">2023/12/17 - ZFS Upgrade Issue</a> 
+
+<li>
+<a href="1701978587-no-tickets.html">2023/12/07 - No Tickets</a> 
+
+<li>
+<a href="1701545547-no-tickets.html">2023/12/02 - No Tickets</a> 
+
+<li>
+<a href="1700863814-auvik-trial.html">2023/11/24 - Auvik Trial</a> 
+
 <li>
 <a href="1700345096-busy-week.html">2023/11/18 - Busy Week</a> 
 

job/acumera-linux-systems-engineer.html

@@ -0,0 +1,111 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="../style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="../rss.xml">
+<title>Linux Systems Engineer (Acumera)</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<div id="Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)"><h1 id="Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)" class="header"><a href="#Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)">Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)</a></h1></div>
+<hr />
+
+<div id="Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)-Employer"><h2 id="Employer" class="header"><a href="#Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)-Employer">Employer</a></h2></div>
+<hr />
+<p>
+<span id="Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)-Employer-Name:"></span><strong id="Name:">Name:</strong> <a href="https://www.acumera.com">Acumera</a>
+</p>
+
+<table>
+<thead>
+<tr>
+<th>
+Duration of employment
+</th>
+<th>
+&nbsp;
+</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>
+Start Date
+</td>
+<td>
+2023/12/04
+</td>
+</tr>
+<tr>
+<td>
+End Date
+</td>
+<td>
+Current
+</td>
+</tr>
+</tbody>
+</table>
+
+<div id="Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)-Job Duties"><h2 id="Job Duties" class="header"><a href="#Unix &amp; Linux Systems Engineer (Acumera 2023 -&gt; Current)-Job Duties">Job Duties</a></h2></div>
+<hr />
+<p>
+As a Linux Systems Engineer working at Acumera, my role is multifaceted, encompassing various responsibilities to ensure the efficient operation of our infrastructure. 
+</p>
+
+<p>
+Key aspects of my position include:
+</p>
+<ul>
+<li>
+Infrastructure Deployment
+<pre>
+Proficiently utilizing Puppet to build out new equipment and virtual machines (VMs) 
+for customers. This involves configuring and optimizing Linux systems to meet 
+specific requirements.
+</pre>
+
+<li>
+Cloud Infrastructure Management
+<pre>
+Setting up new Virtual Private Clouds (VPCs) in AWS to facilitate the seamless 
+rollout of customer VMs. This involves configuring networking, security, and 
+other AWS services to create robust and scalable environments.
+</pre>
+
+<li>
+Automation Scripting
+<pre>
+Developing scripts to automate intricate tasks, enhancing operational efficiency. 
+These scripts empower our customer support team to address and resolve issues 
+promptly, ensuring a swift and effective response to customer needs.
+</pre>
+
+<li>
+Escalation Handling
+<pre>
+Handling escalations from customers when their infrastructure encounters issues. 
+This involves diagnosing and resolving complex problems, collaborating with 
+cross-functional teams to ensure the restoration of normal operations.
+</pre>
+
+<li>
+Jenkins Integration
+<pre>
+Collaborating with Jenkins to design automated buildout jobs. This process 
+streamlines the provisioning of customer equipment from a gold-image, reducing 
+manual intervention and enhancing the speed and consistency of our 
+deployment processes.
+</pre>
+
+</ul>
+<p>
+In summary, my role involves a combination of infrastructure deployment, cloud management, automation scripting, escalation handling, and Jenkins integration, contributing to the overall reliability and efficiency of our systems and services.
+</p>
+
+</body>
+</html>

job/fastwyre-unix-linux-systems-engineer.html

@@ -0,0 +1,150 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="../style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="../rss.xml">
+<title>Unix %title%amp; Linux Systems Engineer (Fastwyre)</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<div id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)"><h1 id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)" class="header"><a href="#Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)">Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)</a></h1></div>
+<hr />
+
+<div id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Employer"><h2 id="Employer" class="header"><a href="#Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Employer">Employer</a></h2></div>
+<hr />
+<p>
+<span id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Employer-Name:"></span><strong id="Name:">Name:</strong> <a href="https://fastwyre.com">Fastwyre Broadband</a>
+</p>
+
+<table>
+<thead>
+<tr>
+<th>
+Duration of employment
+</th>
+<th>
+&nbsp;
+</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>
+Start Date
+</td>
+<td>
+2022/02/21
+</td>
+</tr>
+<tr>
+<td>
+End Date
+</td>
+<td>
+2023/12/01
+</td>
+</tr>
+</tbody>
+</table>
+
+<div id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Job Duties"><h2 id="Job Duties" class="header"><a href="#Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Job Duties">Job Duties</a></h2></div>
+<hr />
+<p>
+In my role as a Unix &amp; Linux Systems Engineer at Fastwyre Broadband, I was deeply involved in various critical facets of our operations. I spearheaded the administration of our servers, catering to a wide spectrum of internal and external services. Additionally, my responsibilities extended to delivering robust L2 &amp; L3 support for the myriad applications running on them. 
+</p>
+
+<p>
+As a Systems Engineer, I played a pivotal role in orchestrating and executing strategic projects focused on establishing new infrastructure. I spearheaded the seamless migration of both our internal systems and our valued customers from legacy setups to modernized environments. This involved meticulously planning and implementing the transition, ensuring minimal disruption while maximizing the efficiency and reliability of our systems. Collaborating cross-functionally, I worked with my team to architect robust solutions that aligned with evolving technological needs and significantly enhanced our operational capabilities
+</p>
+
+<p>
+In addition to my core responsibilities, I maintained a suite of legacy scripts and workflows, predominantly scripted in Perl, Python, Shell, and Bash. These played a pivotal role in streamlining our internal processes, serving as the backbone for automating a significant portion of our operations. They efficiently generated crucial data from a myriad of legacy services utilized by our customers. This data was instrumental in facilitating our billing department's accurate invoicing processes, ensuring precise customer charges based on the services availed
+</p>
+
+
+<div id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Services"><h2 id="Services" class="header"><a href="#Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Services">Services</a></h2></div>
+<hr />
+<div id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Services-Provided to Customers"><h3 id="Provided to Customers" class="header"><a href="#Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Services-Provided to Customers">Provided to Customers</a></h3></div>
+<ul>
+<li>
+Email (<a href="https://www.magicmail.com/">MagicMail</a>)
+
+<li>
+Public NTP Servers (xntpd, ntpd &amp; chrony)
+
+<li>
+Legacy WebServers (apache2 &amp; httpd)
+<pre>
+  Note:
+  These in the past hosted websites for our customers, however shortly before I 
+  started working there the company no longer offered this service to new customers. 
+  While we still continued to host some of our legacy customer's sites.
+  
+  Our webservers got shut down a few months before I left the company.
+</pre>
+
+<li>
+DNS (named/bind9)
+<pre>
+  Note:
+  The company used to offer to fully handle customer's domains and websites.
+  Meaning that we used to register their domain at a registrar and host their
+  DNS records on our public DNS servers.
+</pre>
+
+<li>
+Telephony &amp; VoIP (<a href="https://www.metaswitch.com/">Metaswitch</a>)
+<pre>
+  Note:
+  I managed our MetaSwitch enviornment (CFS, EAS &amp; their related Hardware &amp; VMs). 
+  
+  This included:
+  - Setting up &amp; configuring VoIP Phones to work with our CFS for businesses 
+  - Providing support for VoIP &amp; SIP related issues
+  - Managed hardware maintainance (drive &amp; unit replacements) Setting up automated (via cron) scripts to archive BAF files 
+    and transfer them to our vendors.
+</pre>
+
+<li>
+DHCP (isc-dhpcd)
+
+<li>
+IPTV Managment Server (<a href="https://www.minervanetworks.com/platform/">Minerva 10</a>)
+
+</ul>
+<div id="Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Services-Provided Internally"><h3 id="Provided Internally" class="header"><a href="#Unix &amp; Linux Systems Engineer (Fastwyre 2022 -&gt; 2023)-Services-Provided Internally">Provided Internally</a></h3></div>
+<ul>
+<li>
+SMTP Servers (postfix configured as a relay)
+<pre>
+  Note:
+  I had to setup postfix as a smtp-relay to allow for our legacy internal systems &amp; 
+  applicatons that didn't support auth over tls or starttls to be able to send 
+  emails for both internal &amp; customer related services.
+</pre>
+
+<li>
+File Servers (nfs, samba, ftp, sftp, etc)
+<pre>
+  Note:
+  This is a rather general/broad service, but our file/storage servers handled storing backups
+  from our various services &amp; servers that didn't all support just using sftp. This was due 
+  to the age of some of our systems as many of them didn't suport the same hostkey algorithms
+  and/or we didn't have shell access to the underlying OS to change sshd_config to add 
+  support.
+</pre>
+
+<li>
+<a href="https://calix.com">Calix</a> Network Management Servers (<a href="https://www.calix.com/compass/calix-management-system.html">CMS</a> &amp; <a href="https://www.calix.com/calix-university/axos/introduction-to-smx.html">SMx</a>)
+
+<li>
+Network Monitoring Server (<a href="https://www.librenms.org/">LibreNMS</a>)
+
+</ul>
+
+</body>
+</html>

my-jobs.html

@@ -0,0 +1,33 @@
+<!DOCTYPE html>
+<html>
+<head>
+<link rel="Stylesheet" type="text/css" href="style.css">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<title>My Jobs</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+</head>
+<body>
+
+
+
+<hr />
+<p>
+<a href="index.html">Index</a>
+<hr />
+</p>
+
+
+<div id="My Jobs"><h1 id="My Jobs" class="header"><a href="#My Jobs">My Jobs</a></h1></div>
+<hr />
+<ul>
+<li>
+<a href="job/fastwyre-unix-linux-systems-engineer.html">Unix &amp; Linux Systems Engineer (Feb 2022 -&gt; Dec 2023)</a>
+
+<li>
+<a href="job/acumera-linux-systems-engineer.html">Linux Systems Engineer (Dec 2023 -&gt; Current)</a>
+
+</ul>
+
+</body>
+</html>