updated my fastwyre job entry
This commit is contained in:
parent
d9b80452a7
commit
d25ee5b17d
@ -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 MSP, 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>
|
||||
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
<head>
|
||||
<link rel="Stylesheet" type="text/css" href="../style.css">
|
||||
<link rel="alternate" type="application/rss+xml" title="RSS" href="../rss.xml">
|
||||
<title>[Fastwyre] Unix %title%amp; Linux Systems Engineer</title>
|
||||
<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>
|
||||
@ -11,13 +11,13 @@
|
||||
|
||||
|
||||
|
||||
<div id="[Fastwyre] Unix & Linux Systems Engineer"><h1 id="[Fastwyre] Unix & Linux Systems Engineer" class="header"><a href="#[Fastwyre] Unix & Linux Systems Engineer">[Fastwyre] Unix & Linux Systems Engineer</a></h1></div>
|
||||
<div id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)"><h1 id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)" class="header"><a href="#Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)">Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)</a></h1></div>
|
||||
<hr />
|
||||
|
||||
<div id="[Fastwyre] Unix & Linux Systems Engineer-Employer"><h2 id="Employer" class="header"><a href="#[Fastwyre] Unix & Linux Systems Engineer-Employer">Employer</a></h2></div>
|
||||
<div id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Employer"><h2 id="Employer" class="header"><a href="#Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Employer">Employer</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
<span id="[Fastwyre] Unix & Linux Systems Engineer-Employer-Name:"></span><strong id="Name:">Name:</strong> <a href="https://fastwyre.com">Fastwyre Broadband</a>
|
||||
<span id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Employer-Name:"></span><strong id="Name:">Name:</strong> <a href="https://fastwyre.com">Fastwyre Broadband</a>
|
||||
</p>
|
||||
|
||||
<table>
|
||||
@ -51,10 +51,100 @@ End Date
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<div id="[Fastwyre] Unix & Linux Systems Engineer-Job Duties"><h2 id="Job Duties" class="header"><a href="#[Fastwyre] Unix & Linux Systems Engineer-Job Duties">Job Duties</a></h2></div>
|
||||
<div id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Job Duties"><h2 id="Job Duties" class="header"><a href="#Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Job Duties">Job Duties</a></h2></div>
|
||||
<hr />
|
||||
<p>
|
||||
As a Unix & Linux Systems Engineer working for Fastwyre Broadband
|
||||
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.
|
||||
</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 & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Services"><h2 id="Services" class="header"><a href="#Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Services">Services</a></h2></div>
|
||||
<hr />
|
||||
<div id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Services-Provided to Customers"><h3 id="Provided to Customers" class="header"><a href="#Unix & Linux Systems Engineer (Fastwyre 2022 -> 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 & chrony)
|
||||
|
||||
<li>
|
||||
Legacy WebServers (apache2 & 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 & VoIP (<a href="https://www.metaswitch.com/">Metaswitch</a>)
|
||||
<pre>
|
||||
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.
|
||||
</pre>
|
||||
|
||||
<li>
|
||||
DHCP (isc-dhpcd)
|
||||
|
||||
<li>
|
||||
IPTV Managment Server (<a href="https://www.minervanetworks.com/platform/">Minerva 10</a>)
|
||||
|
||||
</ul>
|
||||
<div id="Unix & Linux Systems Engineer (Fastwyre 2022 -> 2023)-Services-Provided Internally"><h3 id="Provided Internally" class="header"><a href="#Unix & Linux Systems Engineer (Fastwyre 2022 -> 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 &
|
||||
applicatons that didn't support auth over tls or starttls to be able to send
|
||||
emails for both internal & 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 & 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> & <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>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user