Compare commits

..

12 Commits

Author SHA1 Message Date
38959a30c1 Added final school post 2024-02-02 13:04:13 -06:00
94ed0a3976 Added new post 2024-01-27 13:54:04 -06:00
8bc0f712dc -m 2024-01-21 13:09:14 -06:00
4cdd050394 updated acumera job page 2024-01-19 18:31:53 -06:00
3b2e04658c Added new job page 2024-01-19 18:27:59 -06:00
43c2a2452c Had to remove un-necessary dir 2024-01-15 10:31:39 -06:00
f9550388fb had to update index again 2024-01-15 10:30:49 -06:00
6573ea7260 had to update index 2024-01-15 10:25:50 -06:00
0746abb5f3 Added new post 2024-01-15 10:22:43 -06:00
d25ee5b17d updated my fastwyre job entry 2024-01-05 12:45:02 -06:00
d9b80452a7 Updated fastwyre page 2024-01-04 15:57:21 -06:00
c46813480f Added jobs section 2024-01-04 15:50:07 -06:00
9 changed files with 591 additions and 7 deletions

View File

@@ -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>

View File

@@ -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>

View File

@@ -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>

113
1706899198-post-mortem.html Normal file
View File

@@ -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>

View File

@@ -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,7 +23,7 @@
<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>
@@ -31,7 +31,7 @@ I am Tristan Ancelet, an aspiring technologist. I enjoy working with both softwa
<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 Unix &amp; Linux Systems Engineer, at an ISP. Out of necessity much of my work is admin-ing our legacy servers as we do not have a dedicated SysAdmin on staff. Otherwise I work on projects to setup new servers and integrate vendors software/products into our infrastructure.
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>

View File

@@ -16,12 +16,21 @@
<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>

View File

@@ -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>

View File

@@ -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>

33
my-jobs.html Normal file
View File

@@ -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>