feature design evolution
TRANSCRIPT
- 1. Amit Aviram Software Engineer Red Hat Feature Design Evolution 1
- 2. The demonstrated feature Image upload http://www.ovirt.org/Features/Image_Upload Motivation Relevant considerations for other design processes: Efficiency Security Time management 2
- 3. Virtualization open source project. oVirt 3 Backend VDSM DB VDSM VDSM VDSM Storage
- 4. The original design 4
- 5. Problem: Can't be done. 5 Browsers can't handle uploading single big file
- 6. 6 Solution: upload chunks, File API
- 7. Problem: upload destination? 7 Add a new disk (regular file!), then write to it. VDSM should write to the storage Locking? Unlocking?
- 8. Solution: Initialize, Finalize 8
- 9. Problem: Streaming through the system? 9 - Overloading. Used to handle only small amounts of data. - Scalability - Errors can be critical.
- 10. Solution: Extracting logic 10
- 11. Problem: No DB Access! 11 Again, scalability.. DB API?
- 12. Solution:Metadata from elsewhere. 12
- 13. Problem: New process in dmz. 13 Minimize access Denial of service
- 14. 14 Solution: Add a signed token.
- 15. Problem: Implementing a client? 15 Access to the API Harder to implement.
- 16. 16 Solution: Make it a server.
- 17. Problem: Is everything managed? 17 Engine still needs to control. Minimize capabilities of the new process.
- 18. Solution: Writing expiration. 18
- 19. Future considerations? 19
- 20. Comparison 20
- 21. Thank you! 21