Vishvananda Ishaya presented the current state and future plans for the OpenStack Compute (Nova) project. Key highlights of the Essex release included integration with Keystone for shared user authentication, role-based access controls, improvements to support multiple hypervisors, and preparations for integrating with block storage (Cinder) and networking (Quantum) projects. The Folsom release plan focuses on breaking out block storage and networking into separate projects while improving stability, security, scalability and migration capabilities of Nova.

2. Compute State of the Project
Vishvananda Ishaya
OpenStack Compute Project Technical Lead

3. Introduction

4. Introduction
sili-corn
valley

5. History of Nova (According To Vish)

6. History of Nova (According To Vish)

7. History of Nova (According To Vish)

8. History of Nova (According To Vish)

9. Nova Architechure

10. where are we now?
Essex Status
Vishvananda Ishaya
OpenStack Compute Project Technical Lead

11. Operational
‣ Real Deployments
‣ Rackspace
‣ HP
‣ Sony
‣ Stable
‣ Offered in Ubuntu Precise LTS

12. Essex Features

13. where are we now?
Essex Highlights
Vishvananda Ishaya
OpenStack Compute Project Technical Lead

14. Keystone Integration
‣ Shared User System

15. Role-based Access Control
‣ Fine grained control

16. Openstack-Common
‣ code sharing across projects

17. Hypervisor Feature Parity
‣ Disk Config
‣ Resize
‣ File Injection

18. RPC Improvements
‣ Lots of bugfixes
‣ Qpid suport
‣ Prep for ZeroMQ

19. Admin Extensions
‣ Ported many nova-manage features
‣ Documented extensions

20. Volume Endpoint
‣ Prepares for Cinder
‣ Documented at api.openstack.org

21. Network Decoupling
‣ Prepares for Quantum

22. Metadata Server Separation
‣ Supports deployment
‣ Optimized with caching

23. Floating Ip Pools
‣ Internal and public natted ips

24. where are we going?
Folsom Plan
Vishvananda Ishaya
OpenStack Compute Project Technical Lead

25. Design Summit

26. Minimizing Scope

27. Block Storage Breakout
‣ Separate Repository
‣ Client Library
‣ Existing Volume code stays
‣ Drop in replacement
‣ Migration plan

28. Network Breakout
‣ Consistent Network API
‣ Quantum intended suggested default for Folsom
‣ Existing Network code will remain but not be
actively developed

29. Stable Trunk
‣ Feature Branches
‣ Merge Windows

30. Metadata/Config Drive
‣ More Data
‣ Network Configuration

31. AWS Compatibility
‣ Testing library
‣ AWSOME proxy

32. Consistent CLIs
‣ Common library
‣ Plugins

33. Operational Support
‣ Logging improvements
‣ Administrative tools

34. Security Improvements
‣ Remove DB access from compute
‣ Secure Queues

35. Stability Improvements
‣ Distributed state management

36. Scaling Improvements
‣ Cells code
‣ Host Aggregates

37. Migration
‣ Versioned RPC apis
‣ Graceful worker shutdown
‣ More careful DB upgrades

38. Questions