On Wed, Apr 01, 2026 at 02:33:42AM -0400, Rahul Singh via infrastructure wrote: > Hi Fedora Infrastructure Team, > > My name is Rahul Kumar Singh, and I would like to introduce myself as someone > interested in contributing to the Fedora Infrastructure team.
Hello and welcome! > > Matrix Handle: @rahulks:fedora.im > > Skills I Can Offer > > Systems Administration: > * 5+ years of Linux infrastructure experience (RHEL, Almalinux, CentOS, > Ubuntu) > * Currently deployed as Senior Systems Engineer at Hewlett Packard > Enterprise (HPE), managing an environment of 5,000+ VMs and 1500+ servers > * Experience with data center operations, rack servers, storage > networking (multipathing, LUNs), and high-availability systems > * Virtualization: VMware ESXi, KVM, HVM, Proxmox VE > * Containerization & Orchestration: Docker, Kubernetes > * Cloud: AWS (EC2, S3, Route53, CloudFront, SES) > * Monitoring & Networking: Load balancers, network configuration, uptime > monitoring > * RHCSA certified > > Other Context: > I also run a small web hosting and infrastructure company (Hexraa > Technologies) where I manage Proxmox-based dedicated servers, cPanel/Plesk > environments, and DNS infrastructure so I'm comfortable working with real > production systems under operational constraints. > > What I Would Like to Work On > > Given my background, I'm particularly interested in the following areas: > Cloud Image Testing & Deployment: > * Deploying and testing new Fedora releases on cloud platforms (AWS, and > others) to validate image behavior, boot process, and cloud-init integration > * I have access to cloud environments and am happy to test pre-release > and nightly compose images across different instance types You likely want the cloud sig or quality folks for that angle, but there is definitely overlap! We do some testing in our cloud image uploader application too. > Image Building: > * Building and validating Fedora disk images in qcow2 (for KVM/Proxmox) > and VMDK (for VMware ESXi) formats > * Testing these templates in real hypervisor environments to catch issues > before release > > Bash Scripting & Automation: > * Writing Bash scripts to automate repetitive infrastructure and systems > administration tasks > * Happy to pick up automation needs from open tickets or team discussions > > Other Contributions: > * Reviewing and improving Ansible playbooks and group_vars (CSI standards > work) > * Log review and issue triaging on infrastructure machines > * Monitoring-related contributions (Zabbix, Nagios) > * General ticket resolution on forge.fedoraproject.org/infra/tickets > * Documentation improvements > > I understand the team operates as a meritocracy and that I'll be expected to > be a self-starter. I'm comfortable with that and happy to start small, learn > the existing setup, and work my way up. > > What I Want to Learn > * How Fedora's build and release infrastructure works end-to-end (Koji, > Bodhi, image compose pipeline) > * Fedora's Ansible-based configuration management patterns > * How the Forgejo/Forge migration is being managed operationally > * Best practices for contributing to Fedora Cloud and CoreOS image > workflows > > I have requested to join the fi-apprentice FAS group and plan to attend the > next weekly Matrix meeting to introduce myself in person. > > Looking forward to contributing! Looking forward to talking with you! Welcome again. kevin -- _______________________________________________ infrastructure mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
