Senior Linux Infrastructure & Automation Engineer - RedHat Ansible

Senior Linux Infrastructure & Automation Engineer - RedHat Ansible

Posted 3 days ago by fortice

£681 Per day
Inside
Hybrid
Hybrid - Stevenage, UK

Summary: The role of DevOps Engineer involves supporting infrastructure for exploration rover and telecoms satellite projects, utilizing tools like Git, Ansible, and Podman. The position requires maintaining and extending existing systems while adapting to both older and newer technologies. A regular presence on-site is preferred, with responsibilities spanning across both GNC and software teams. The role emphasizes the need for configuration control and system deployment in a hybrid working environment.

Key Responsibilities:

  • Utilize Git for version control of scripts.
  • Implement configuration control using Ansible.
  • Deploy systems using Autoinstall or similar tools.
  • Work with Ubuntu 20+ or similar Debian derivatives as the operating system.
  • Manage containerization with Podman or similar technologies.
  • Configure and install physical machines and support hardware.
  • Design and implement IT system architecture.
  • Support infrastructure for GNC and software teams as required.
  • Maintain and extend existing systems while learning current infrastructure.
  • Execute operations from install/update/upgrade packages to environment configuration.
  • Work with a variety of hosts on breadboarding and maintain consistent environments for telecoms.

Key Skills:

  • Proficiency in Git for version control.
  • Experience with Ansible for configuration management.
  • Knowledge of system deployment tools like Autoinstall.
  • Familiarity with Ubuntu 20+ or Debian derivatives.
  • Experience with containerization technologies such as Podman.
  • Ability to configure and install physical machines and hardware.
  • Understanding of IT system architecture design and implementation.
  • Capability to work with various hosts and maintain consistent environments.
  • Experience in supporting GNC and software teams.
  • Ability to adapt to both older and newer technologies.

Salary (Rate): £681/day

City: Stevenage

Country: UK

Working Arrangements: hybrid

IR35 Status: inside IR35

Seniority Level: Senior

Industry: IT

Detailed Description From Employer:

DevOps Engineer
Location: Stevenage
Duration: 3 months
MUST BE PAYE THROUGH UMBRELLA

Role Description:
Required Knowledge (this will be the job)
Git for version control of scripts
Ansible for configuration control
Autoinstall or similar for system deployment
Ubuntu 20+ or similar Debian derivatives as OS
Podman or similar containerisation

o w/hardware passthrough for graphical applications on unsupported hardware/software (ie Nvidia K2000 on RHEL 6 and co)
o w/hardware emulation ie QEMU
o Used for development and for service hosting
Configuration/installation of physical machines and the required support hardware (racking machines, spec racks w/acoustic dampening, spec power delivery/UPS, spec network requirements, etc)
Architecture design and implementation of an IT system.

Project context:
Our exploration rover breadboarding and telecoms satellite infrastructure is using increasingly IM unsupported tools and services (be that older systems, newer systems, OS/software that IT simply don't support etc.) raising a need to manage more and more of this internal to the site/project/department where we either want to be on more recent tooling (breadboarding) or maintain older tooling for spacecraft projects whose lifespan is in the tens of years and is expected to remain fixed.

The role is to support this infrastructure in both the GNC and software teams as the projects require, this will involve responsibility for maintaining/extending but may in the case of older systems require learning/understanding the current infrastructure before making substantial adjustments/redeployments.

A regular presence on site is preferred not mandatory without periods of heavy support/presence on site and abroad should be expected.

Our current implementation on breadboarding relies on Ansible executing against a variety of different hosts performing operations from install/update/upgrade packages thru host environment configuration thru checkout and build internal projects from source for deployment on host or in containers.

Expect to be working with a range of hosts on breadboarding (industrial PCs, Workstation PCs, VMs) that need as much commonality but each have their own quirks (ie not all the industrial PCs can be expected to have consistent network access and will travel out into the field with the rover). The telecoms side is far more consistent with tens of VMs that need to and can be maintained as identical environments.?