Lessons Learned Maintaining the oVirt Python SDK
summary
Maintenance experiences from the oVirt Python SDK: practical issues encountered while supporting and evolving a Python client for the oVirt virtualization platform, specific problems that arose in the codebase and packaging, and the tools or workflows used to manage tests, compatibility and contributions.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:25What is the oVirt Python SDK?
- 1:56With the SDK
- 4:45What was the situation?
- 6:19Why did this need to be improvedi
- 6:58What was changed? In version of the server we moved the specification of the The same specification des to the types and the services, using the same language . The specification of the AP has its own independent release
- 10:57What was changed? code generator that we control and that is driven by the
- 13:02Why did this need to be improved? • The complete XML paring solution performed bed for large documents, in terms of memory and specially in terms of CPU
- 13:15What was changed? . In version 4 of the So we replaced generates.py and the parsing • New XReader and writer classes were implemented
- 15:38Lesson 3: How better? Read 4000 virtual machines with version of the SOK
related talks
29mLessons Learned From Maintaining SDK in Python for Three Years
32m"Making an open source package - lessons learned"
38mTools for Maintaining an Open Source Project
41mHow to Grow an Open Source Project: A Case Study of Python
24mJourney to migrate python2 projects to 3
03mTransforming Mainframes: My Zowe-Python SDK Journey
25mLessons Learned from Cultivating Open Source Projects and Communities
33mVirtual Environments and Dependency Management in Python