Working with cloud infrastructure and Linux servers involves more than just running commands. My day-to-day work focuses on keeping servers and compute workloads running smoothly, troubleshooting issues, monitoring jobs, and coordinating with developers when something needs attention.
Managing Linux Servers
A major part of my daily work involves working with Linux servers and checking their overall health.
Typical activities include:
- Connecting to the required server and checking its current status.
- Monitoring CPU, memory, disk space, and running processes.
- Checking logs when applications or jobs behave unexpectedly.
- Identifying resource-related issues before they affect workloads.
- Running commands to verify services, processes, and system availability.
The important part is always making sure commands are executed on the correct server, especially when multiple machines are involved.
Working With Slurm Job Scheduling
Slurm is an important part of managing compute workloads. I regularly monitor submitted jobs and investigate why a workload may be waiting, running, or using a particular compute server.
My day-to-day Slurm activities include:
- Checking job status and queue information.
- Identifying why a job is pending or waiting.
- Checking which node/server a job has been assigned to.
- Monitoring currently running jobs.
- Reviewing resource allocation such as CPU and memory.
- Troubleshooting scheduling issues and unexpected behavior.
Sometimes a job is not actually stuck—it may simply be waiting for the current workload to finish. Understanding the scheduler state before making changes is therefore important.
AWS Infrastructure and Troubleshooting
I also work with AWS-related infrastructure and cloud environments as part of my regular activities.
This involves understanding how different servers and workloads are connected, checking infrastructure availability, and troubleshooting issues that occur between applications, compute resources, and servers.
A typical troubleshooting process is:
- Identify the affected server or workload.
- Check the current system and job status.
- Review relevant logs and resource usage.
- Determine whether the issue is application-, server-, or scheduler-related.
- Make the required changes carefully.
- Monitor the workload after the change.
Working With Developers
Another important part of my daily work is communicating with developers when infrastructure or compute-related issues occur.
Instead of simply reporting that something is not working, I try to provide useful information such as:
- What was checked.
- Which server was involved.
- When the job started.
- What the current job status is.
- What troubleshooting steps were already performed.
- Whether the issue requires developer-side investigation.
This makes it easier for the developer to continue troubleshooting without repeating the same checks.
Continuous Monitoring and Improvement
Infrastructure work is often about observing, troubleshooting, and improving rather than making one large change.
Every issue provides an opportunity to understand the environment better—whether it is a Slurm scheduling problem, a Linux server issue, resource utilization, or an AWS infrastructure dependency.
My daily workflow is therefore focused on monitoring systems, troubleshooting efficiently, documenting what was done, and keeping workloads running reliably.