Kenichi Omichi
Software Engineer at Mitsubishi Electric
Tokyo, Japan
Summary
🤩
RockstarKenichi Omichi is a software engineer based in Tokyo with 12 years of hands-on experience building and maintaining backend and DevOps tooling for large open-source cloud and container projects. He has contributed meaningful test-framework refactors, API compatibility fixes, and automation improvements across high-profile repositories such as Kubernetes and multiple OpenStack projects, improving maintainability and stability of critical infrastructure. Comfortable across backend development, test automation, and cluster deployment, he repeatedly focuses on reducing code duplication, updating deprecated interfaces, and hardening CI/test processes. Colleagues can rely on him to untangle legacy code and align tests with evolving libraries and microversions, a pattern visible across Tempest, Nova, Cinder, and Ceilometer work. Outside of code, he balances engineering with family life and active outdoor pursuits—surfing, running and cycling—bringing steady, pragmatic energy to long-lived systems.
12 years of coding experience
Github Skills (58)
api-rest10
kubernetes10
docker10
python10
json-schema10
apidoc10
api-design10
back-end-development10
restful-api10
testing10
cinder10
test-framework10
bash10
cloud-infrastructure10
microsoft-azure10
Programming languages (13)
Github contributions (5)
openstack/tempest
Aug 2013 - Jul 2018
OpenStack Testing (Tempest) of an existing cloud. Mirror of code maintained at opendev.org.
Role in this project:
Backend Developer & DevOps Engineer
Backend Developer & DevOps EngineerContributions:546 commits in 4 years 11 months
Contributions summary:Kenichi primarily focused on refactoring and cleaning up the code, specifically within the scenario tests for the OpenStack Tempest project. Their work involved adding common methods to reduce code duplication, implementing standard patterns for creating keypairs, server snapshots, and volume management, and refactoring existing test logic. Additionally, the user was also involved in testing network connectivity within the project.
testingcloud-foundryinfrastructurecloudopendev
kubernetes-sigs/kubespray
Apr 2020 - Dec 2022
Deploy a Production Ready Kubernetes Cluster
Role in this project:DevOps Engineer
DevOps EngineerContributions:822 reviews, 147 commits, 197 PRs in 2 years 8 months
Contributions summary:Kenichi primarily contributed to the automation and maintenance of the Kubernetes cluster deployment process. Their work included updating and refactoring scripts for Azure resource management, specifically focusing on deprecated commands and renaming files for better version control. They also implemented changes to support MetalLB, an addon for Kubernetes, ensuring it could create events. Furthermore, the user added features, like the USE_REAL_HOSTNAME option, and addressed the image registry process for offline deployments, which included fixing image ID retrieval and handling error conditions.
bare-metalkubesprayhelmproduction-readyansible
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.