Updating Microservice ImagesMadhuri Yechuri

Agenda

Enterprise Microservice Image lifecycle

Image Update process asks

Container image update

Unikernel image update

Demo

Q & A

Enterprise Microservice Image lifecycleEngineer A writes Code

Build, Validate image

Deploy image on destination

… time passes …

Engineer B inherits Code, then edits it

Build, Validate

Update image on destination

… time passes …

Engineer B inherits Code, then fixes a couple of bugs, rebuilds, validates

Update image on destination

… time passes …

Engineer B inherits Code, then edits it, rebuilds, validates

Update image on destination

…

End of Life of Code

Image upgrade process asks

Fast

As few hops as possible from build host to destination host

Secure

Network efficient

Enterprise Microservices

Now

Containers, Containers, Containers, Containers, Containers, Containers,..

Container Image flow during upgrade

Enterprise Microservices

Now

Containers, Containers, Containers, Containers, Containers, Containers,..

Future

Containers, Containers, Containers, Unikernels, Containers, Unikernels, Containers, Containers, ..

Unikernels

Single process, single address space

Small on-disk footprint

Diffs are KBs to few MBs

Immutable

New app == new image

Immutable base

Unikernel image flow during upgrade

Demo

Docker server for container == ukd for unikernel

Docker client for container == ukdctl for unikernel

Ukdctl update

Summary

Image upgrade

High frequency operation during lifecycle of an enterprise microservice

Containers image upgrade

Brokered by Registry

Unikernels image upgrade

Apply lessons learnt from Registry in production

Demo

References

Ukd

Ukonvrt

Questions?

Gmail: cosmokramer

GitHub: myechuri

Acknowledgements

Influencers: Mike Larkin, Rean Griffith, Carl Waldspurger

Meetup organizers: Erika Ghose, DJ Sampath

Venue: Cisco

Audience: Thank you!