The document outlines updates and priorities for OpenStack Nova as discussed by John Garbutt during the OpenStack Ops Midcycle event in February 2016. Key focuses include a robust API, enhancements to the upgrade process, and the evolution of the API through microversions. It also addresses issues related to live migration and the architecture improvements aimed at maintaining system reliability and scalability.

1. OpenStack Nova Update
John Garbutt, Principal Engineer, Nova PTL
@johnthetubaguy
OpenStack Ops Midcycle, Manchester, Feb
2016

2. 2
Ops Feedback
https://etherpad.openstack.org/p/MAN-ops-Nova

3. Image FPO
3
Why is johnthetubaguy talking?
3

4. Image FPO
4
Do you really play the Tuba?
4

5. 5
Nova

6. 6
to provide massively scalable ,
on demand, self ser vice
access to compute resources
OpenStack Nova’s Mission

7. 7
Priorities
• Good API with a Strong Ecosystem
• Robust and Reliable
• Live Upgrades and Scale out
• Maintain Open Culture
• Stop Scope Creep

8. 8
External Server “HA”
Help
External
HA Tool
Disable
Host
Live-
migrate
Mark
host
down
Evacuate

9. 9
Upgrade

10. 10
Upgrade
• Data plane and Control plane independence
• Upgrade from:
– Last stable branch
– Previous commit in same cycle
• Existing Configuration “just work”
• Warning before removing Features

11. 11
Old Process
Turn Off
Old
DB
Upgrade
Turn On
New

12. Image FPO
12
Fix that vulnerability now!

13. 13
Nova Architecture
API Nodes
Behind LB
Compute Compute Compute Compute Compute
Database
Message
Queue
Conductor(s)
Other Control
Nodes
Isolate from DB using
oslo.versionedobjects Versioned RPC Signature
Schema and Data Migrations
Graceful Shutdown
RPC Signature

14. 14
New Upgrade Process
Expand
DB Schema
Restart API
and
Control Plane
Restart
n-compute
SIGHUP
all services

15. 15
New Upgrade Process
API Nodes
Behind LB
Compute Compute Compute Compute Compute
Database
Message
Queue
Conductor(s)
Other Control
Nodes
1
2a
3
4
2b

16. 16
API

17. 17
API Users
The Absent The Active Multi-Cloud Ops & Dev
• Cloud upgrades
• But old script
works
• Uses newest APIs
• Check availability
• Multiple clouds
• Different versions
• Single script
• Who is using
what?
• How to evolve
API?

18. 18
API Evolution
v2.0 v2.1 Third Party APIs
• First API
• Alias for v1.1
• Base + Extensions
• Deprecated Legacy Code
• No Extensions
• Better Validation
• Backwards compatible
mode
• Evolve using
“Microversions”
• Replaced by External
Project
• Removed in Mitaka

19. 19
Cells v2

20. 20
Cells Evolution
API
Compute
Cell 1
Compute
Cell 2
Compute
Cell 3

21. 21
Scheduler

22. 22
Scheduler
Generic
Resource
Request
Filter Hosts
by Resource
Pools
Pick
Preferred
Host
Acquire
Resource
Claim

23. 23
Live Migration

24. 24
Live Migration
Fixes Features
• Better CI coverage
• Make all disks configurations
moveable
• Status updates
• Force Complete / Cancel
• Split Networks

25. 5 M I L L I N G T O N R O A D | H AY E S , U N I T E D K I N G D O M U B 3 4 A Z
U S S A L E S : + 4 4 ( 0 ) 2 0 8 71 2 6 5 07 | U K S U P P O R T: 0 8 0 0 9 8 8 0 3 0 0 | W W W. R AC K S PAC E . C O M
© RACKSPACE LTD. | RACKSPACE® AND FANATICAL SUPPORT® ARE SERVICE MARKS OF RACKSPACE US, INC. REGISTERED IN THE UNITED S TATES AND OTHER COUNTRIES. |
WWW.RACKSPACE.COM
Thank you
@johnthetubaguy

26. 26
Ops Feedback
https://etherpad.openstack.org/p/MAN-ops-Nova