OpenStack L3 DevOps Support

Hello,
I run a large OpenStack estate that spans Cisco UCS hardware, Ceph storage, and the familiar lineup of Neutron, Octavia, Manila, Cinder, Nova, Ironic and Glance. What I need now is a senior-level engineer who can step in as our L3 point of escalation during the Pacific time zone and take full ownership of complex incidents, long-term stability work, and day-to-day automation.

You’ll dive straight into production: tracing packet flows through Neutron, restoring confidence in a misbehaving Ceph OSD, or debugging Nova scheduler edge cases. Outside the incident queue, I’ll depend on you to turn hard-won fixes into repeatable code using Ansible and Terraform (Pulumi in some green-field areas), and to extend our internal tooling written in Go while managing everything through Git.

Security, policy enforcement and uptime targets drive the way we work, so every change must be codified, peer-reviewed and delivered through our CI/CD pipelines. Because the platform supports global workloads, there will be times when you take part in a 24 × 7 on-call rotation—though your primary shift remains PST.

Success here means the cloud stays available, manual runbooks disappear, and RCA documents are published without prompting. If you already speak OpenStack fluently and enjoy turning chaos into code, let’s talk about your approach and past wins.

Thanks