Added final school post

1705335388-no-tickets.wiki

@@ -0,0 +1,22 @@
+%title No Tickets
+
+
+---------------------------
+[[index.wiki|Index]]
+---------------------------
+
+last 5 posts
+---------------------------
+
+ - [[1701545547-no-tickets.wiki|No Tickets]]
+ - [[1700863814-auvik-trial.wiki|Auvik Trial]]
+ - [[1700345096-busy-week.wiki|Busy Week]]
+ - [[1700104768-new-job-offer.wiki|New Job Offer]]
+ - [[1699564352-webhooks.wiki|Webhooks]]
+
+*Date:* 2024/01/15
+
+*Author:* Tristan Ancelet
+
+= No Tickets =
+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.

1705864010-no-tickets.wiki

@@ -0,0 +1,22 @@
+%title No Tickets
+
+
+---------------------------
+[[index.wiki|Index]]
+---------------------------
+
+last 5 posts
+---------------------------
+
+ - [[1701545547-no-tickets.wiki|No Tickets]]
+ - [[1700863814-auvik-trial.wiki|Auvik Trial]]
+ - [[1700345096-busy-week.wiki|Busy Week]]
+ - [[1700104768-new-job-offer.wiki|New Job Offer]]
+ - [[1699564352-webhooks.wiki|Webhooks]]
+
+*Date:* 2024/01/21
+
+*Author:* Tristan Ancelet
+
+= No Tickets =
+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.

1706384973-no-tickets.wiki

@@ -0,0 +1,22 @@
+%title No Tickets
+
+
+---------------------------
+[[index.wiki|Index]]
+---------------------------
+
+last 5 posts
+---------------------------
+
+ - [[1701545547-no-tickets.wiki|No Tickets]]
+ - [[1700863814-auvik-trial.wiki|Auvik Trial]]
+ - [[1700345096-busy-week.wiki|Busy Week]]
+ - [[1700104768-new-job-offer.wiki|New Job Offer]]
+ - [[1699564352-webhooks.wiki|Webhooks]]
+
+*Date:* 2024/01/27
+
+*Author:* Tristan Ancelet
+
+= No Tickets =
+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.

1706899198-post-mortem.wiki

@@ -0,0 +1,56 @@
+%title Post-Mortem
+
+
+---------------------------
+[[index.wiki|Index]]
+---------------------------
+
+last 5 posts
+---------------------------
+
+ - [[1701545547-no-tickets.wiki|No Tickets]]
+ - [[1700863814-auvik-trial.wiki|Auvik Trial]]
+ - [[1700345096-busy-week.wiki|Busy Week]]
+ - [[1700104768-new-job-offer.wiki|New Job Offer]]
+ - [[1699564352-webhooks.wiki|Webhooks]]
+
+*Date:* 2024/02/02
+
+*Author:* Tristan Ancelet
+
+== Post-Mortem ==
+-----------------
+As of today we have presenteed out post-mortem for out time on the Eschelon Project. 
+
+== Out-take ==
+--------------
+I feel like we got some really good experience in the industry (both the good and the bad).
+
+
+=== The Good ===
+==== Priorities ====
+--------------------
+During out tenure on the project we learned about the development process regarding tickets & QA of features we develop. Part of this process is where the company had prioritized their other `more official` 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.
+
+==== The Experience ====
+------------------------
+With this project, there is a lot of good experiences regarding this:
+- Experience in an Enterprise Company working on a upcoming project
+- Learning the development process and experience with a ticketing system
+- Learning the importance of effective collaboration
+
+=== The Bad ===
+==== The Inital Experience ====
+-------------------------------
+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.
+
+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. 
+
+==== Tickets ====
+-----------------
+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.
+
+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). 
+
+This happened often enough that it was hard to know if this was going to cause merge conflicts down the line.

about-me.wiki

@@ -1,20 +1,20 @@
 %title About Me
 
 -----
-[[index.wiki|Index]]
+[[index.wiki|Index]] [[/my-jobs.wiki|My Jobs]]
 -----
 
 {{local:/images/tristan.jpg|Image of Tristan}}
 
 == Who Am I ==
 --------------
-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.
 
 
 == What work do I do ==
 === Unix & Linux Systems Engineering ===
 ------------------------------------------------
-As explained above I work as a Unix & 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.
 
 === Development ===
 -------------------

index.wiki

@@ -4,8 +4,13 @@
 [[about-me.wiki|About Me]]
 --------
 
-## Blog Posts
+== Blog Posts ==
 -------------
+- [[/1706899198-post-mortem.wiki|2024/02/02 - PostMortem]]
+ 
+- [[/1706384973-no-tickets.wiki|2024/01/27 - No Tickets]]
+
+- [[/1705864010-no-tickets.wiki|2024/01/21 - No Tickets]]
 
 - [[1702849369-zfs-upgrade-issue.wiki|2023/12/17 - ZFS Upgrade Issue ]] 
 

job/acumera-linux-systems-engineer.wiki

@@ -0,0 +1,53 @@
+%title Linux Systems Engineer (Acumera)
+
+
+= Unix & Linux Systems Engineer (Acumera 2023 -> Current) =
+--------------------------------------------
+
+== Employer ==
+--------------
+*Name:* [[https://www.acumera.com|Acumera]]
+
+| Duration of employment |            |
+|------------------------|------------|
+| Start Date             | 2023/12/04 |
+| End Date               | Current    |
+
+== Job Duties ==
+----------------
+As a Linux Systems Engineer working at Acumera, my role is multifaceted, encompassing various responsibilities to ensure the efficient operation of our infrastructure. 
+
+Key aspects of my position include:
+- Infrastructure Deployment
+{{{
+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.
+}}}
+- Cloud Infrastructure Management
+{{{
+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.
+}}}
+- Automation Scripting
+{{{
+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.
+}}}
+- Escalation Handling
+{{{ 
+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.
+}}}
+- Jenkins Integration
+{{{
+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.
+}}}
+
+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.

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

@@ -0,0 +1,78 @@
+%title Unix & Linux Systems Engineer (Fastwyre)
+
+
+= Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023) =
+--------------------------------------------
+
+== Employer ==
+--------------
+*Name:* [[https://fastwyre.com|Fastwyre Broadband]]
+
+| Duration of employment |            |
+|------------------------|------------|
+| Start Date             | 2022/02/21 |
+| End Date               | 2023/12/01 |
+
+== Job Duties ==
+----------------
+In my role as a Unix & 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 & L3 support for the myriad applications running on them. 
+
+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
+
+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
+
+
+== Services ==
+--------------
+=== Provided to Customers ===
+- Email ([[https://www.magicmail.com/|MagicMail]])
+- Public NTP Servers (xntpd, ntpd & chrony)
+- Legacy WebServers (apache2 & httpd)
+{{{	
+  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.
+}}}
+- DNS (named/bind9)
+{{{
+  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.
+}}}
+- Telephony & VoIP ([[https://www.metaswitch.com/|Metaswitch]])
+{{{
+  Note:
+  I managed our MetaSwitch enviornment (CFS, EAS & their related Hardware & VMs). 
+  
+  This included:
+  - Setting up & configuring VoIP Phones to work with our CFS for businesses 
+  - Providing support for VoIP & SIP related issues
+  - Managed hardware maintainance (drive & unit replacements) Setting up automated (via cron) scripts to archive BAF files 
+    and transfer them to our vendors.
+}}}
+- DHCP (isc-dhpcd)
+- IPTV Managment Server ([[https://www.minervanetworks.com/platform/|Minerva 10]])
+
+=== Provided Internally ===
+- SMTP Servers (postfix configured as a relay)
+{{{
+  Note:
+  I had to setup postfix as a smtp-relay to allow for our legacy internal systems & 
+  applicatons that didn't support auth over tls or starttls to be able to send 
+  emails for both internal & customer related services.
+}}}
+- File Servers (nfs, samba, ftp, sftp, etc)
+{{{
+  Note:
+  This is a rather general/broad service, but our file/storage servers handled storing backups
+  from our various services & 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.
+}}}
+- [[https://calix.com|Calix]] Network Management Servers ([[https://www.calix.com/compass/calix-management-system.html|CMS]] & [[https://www.calix.com/calix-university/axos/introduction-to-smx.html|SMx]])
+- Network Monitoring Server ([[https://www.librenms.org/|LibreNMS]])

my-jobs.wiki

@@ -0,0 +1,13 @@
+%title My Jobs
+
+
+---------------------------------
+[[/index.wiki|Index]]
+---------------------------------
+
+
+= My Jobs =
+-----------
+- [[/job/fastwyre-unix-linux-systems-engineer|Unix & Linux Systems Engineer (Feb 2022 -> Dec 2023)]]
+- [[/job/acumera-linux-systems-engineer|Linux Systems Engineer (Dec 2023 -> Current)]]
+

posts/school/1705336692-no-tickets

@@ -0,0 +1,16 @@
+%title No tickets
+
+
+---------------------------
+[[index.wiki|Index]]
+---------------------------
+
+last 5 posts
+---------------------------
+
+
+*Date:* 2024/01/15
+
+*Author:* Tristan Ancelet
+
+= No tickets =