GSoC’20 — Coding phase | Week 10

This is a summary of my 7th week of the coding period.

My university exam was finished and I devoted more time to the GSoC from this week. As I mentioned in the previous blog, currently I’m working with the push manager feature, so first I look into how to remove existing containers before pushing the latest. According to my proposal, remove an existing container is a feature of the container manager component. also, it is a task related to the next phase, but since I have to remove the existing containers before pushing the latest, will implement that in this phase. Ukiyo identifies and kills the existing image by querying unique keys, for that I used the “ — name “ flag.

I wasn’t able to remove the containers which have already killed. That was a huge problem because ukiyo cannot up the latest containers while the ports have used in killed containers. Tried to figure out that issue and after I involved with the task of applying and running the latest container to the environment. Finally was able to handle the mentioned issue.

Next, I run the latest containers by exposing multiple ports. Now ukiyo can apply the latest container by removing the existing container, but still not push within zero-downtime. Although the downtime was not 0, the downtime could be minimized. I will look into it further.

That’s it for this week. So little has done and there is a lot more to do. Keep in touch to read more updates about my GSOC’20 experiences.

Thanks for reading! 🙇