Improving CI/CD Process for Cloud Native Python Applications with PyPI Cloud
summary
Claim: hosting a private Python package index decouples library and service CI/CD so libraries get versioned independently and services avoid rebuilds by selecting a package-version env var at pod startup. Implementation: prototype with pypi-server on Kubernetes (suffering slow disk scans until a caching layer) and a production rollout using pypicloud backed by S3 + DynamoDB (and default caching), eliminating NFS/EBS limits and the Ceph ops burden. Result: fast, resilient installs and months of stable service for multiple clusters.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:48Deployment
- 4:34Api Server
- 8:19Why Is It Bad
- 11:29Why Is this Useful
- 14:05Portability
- 18:17Demo
- 29:08Compare Pi Pi Cloud and Pi Pi Server
- 33:49Conclusion
related talks
24mBuilding a Sustainable Python Package Index
50mBest Practices for Python in the Cloud
39mA Pythonic Approach to Continuous Delivery
34mdevpi: Your One Stop Cheese Shop
36mPython Packaging from Init to Deploy
27mRelease Management with Devpi
31mDevpi for teams
40mPiku: git push deployments to your own servers