CI/CD Pipeline and Image Creation at Yahoo! JAPAN

2nd chunk of `content/en/blog/_posts/2016-10-00-Kubernetes-And-Openstack-At-Yahoo-Japan.md`

bb7281c3f7554964155a4e3fcedb1d432a1a67f605f679dc00000001000002ff

![](https://lh4.googleusercontent.com/JyXP4-mfmZOznXQekSmHFoZ4iRTGLvSAWI37L4AAYzrstKnDVKIRcPhzqrxU1Cmm9bbqOpF_feXX7xDB-cPmbln6dmQ0VelksMSuZfhOlT0r8466yvUU456_OKyrn4wLphCniJuQ)



We use following products in our CICD pipeline:




| Function | Product |
|---|---|
| Code registry | GitHub Enterprise |
| CI tools | Jenkins |
| Image registry | Artifactory |
| Bug tracking system | JIRA |
| deploying Bare metal platform | OpenStack Ironic |
| deploying VM platform |OpenStack |
| deploying container platform | Kubernetes |



Image Creation. Each image creation workflow is shown in the next diagram.



**VM Image Creation** :



[![](https://4.bp.blogspot.com/-saBA4FKmJEM/WAppk0keRfI/AAAAAAAAAxM/7Y3uw-H3I0Ae_p6IqUu429pJqtwqTGxIgCLcB/s640/Untitled%2Bdrawing.png)

Title: CI/CD Pipeline and Image Creation at Yahoo! JAPAN

Summary

Yahoo! JAPAN utilizes a CI/CD pipeline that includes GitHub Enterprise for code registry, Jenkins for CI, Artifactory for image registry, and JIRA for bug tracking. OpenStack Ironic, OpenStack, and Kubernetes are used for deploying to bare metal, VM, and container platforms, respectively. The workflow for VM image creation is then highlighted.