November 2018 Nova Project Update, OpenStack Summit Berlin Melanie Witt irc:melwitt Red Hat
What is Nova? • Compute service • Nova provides the compute controller fabric for the base OpenStack IaaS deployment
Project background • Founded during the Austin release of OpenStack • 255 contributors for latest release (Rocky) [1] Latest user survey adoption numbers: • Deployed: 94% of clouds in production indicate they are using this project [1] http://stackalytics.com/?release=rocky&metric=marks&module=nova-group
Rocky Review Runways http://specs.openstack.org/openstack/nova-specs/priorities/rocky-priorities.html ● Piloted a new review process ● Changed spec freeze from milestone 1 => milestone 2 ● Overall positive, helped complete some blueprints that had repeated re-approvals over previous cycles ● Comparison of blueprint completion stats Queens Rocky Max approved 53 72 Final completed 42 59 Completion percentage 79.2% 81.9%
OpenStack Rocky Features https://docs.openstack.org/releasenotes/nova/rocky.html ● Using new Neutron port binding API to minimize network downtime during live migrations ● Volume-backed servers are no longer reporting ‘root_gb’ usage ● Several nova-network specific REST APIs were removed ● New ‘nova-manage db purge’ command, ‘nova-manage db archive_deleted_rows --purge’ ● New option ‘nova-manage cell_v2 update_cell --disable’ to disable scheduling to a cell ● Trusted image certificates are supported ● New ‘nova-manage placement heal_allocations’ command for CachingScheduler users to populate placement ahead of migration to FilterScheduler ● Placement service now supports granular RBAC policy rules configuration
OpenStack Rocky Features Console token authorization moved from nova-consoleauth service ➡ database backend Queens Rocky nova-novncproxy cell1 cell2 nova-consoleauth nova-novncproxy nova-novncproxy cell1 cell2 DB DB DB DB nova-compute nova-compute nova-compute nova-compute nova-compute nova-compute nova-compute nova-compute
OpenStack Rocky Features ➡ Other improvements (microversion highlights) Microversion Description Exposes flavor extra-specs in the flavors API GET / POST / PUT 2.61 Adds host and hostId to the instance actions API GET 2.62 Adds support for the trusted_image_certificates parameter 2.63 Adds policy and rules to the server groups API GET / POST 2.64 Adds support for aborting live migrations in queued or preparing status 2.65
OpenStack Stein http://specs.openstack.org/openstack/nova-specs/priorities/stein-priorities.html ● Cycle Priorities (<= Queens) ➡ Runways (Rocky) ➡ Runways + Cycle Themes (Stein) ● Multi-cell operational enhancements ○ Handling of a down or poor performing cell ○ Cross-cell cold migration ● Improved boot from volume experience ○ Specify volume type at server create ○ Attach/detach root volume ○ Volume-backed server rebuild ● Compute hosts able to upgrade and exist with nested resource providers for multiple vGPU types
OpenStack Stein https://specs.openstack.org/openstack/nova-specs/specs/stein/index.html ➡ Other improvements • Placement extraction • Bandwidth-aware scheduling • Unified limits + oslo.limit for quota • Restore ability to set overcommit ratios per aggregate • Configuration of maximum number of volumes allowed to attach to a single server • Support for emulated virtual TPM (Trusted Platform Module) • NUMA-aware live migration • AMD SEV-encrypted instances (Secure Encrypted Virtualization)
Cross-Project Work ● Cinder ○ New re-image API for volume-backed rebuild ● Neutron ○ Bandwidth-aware scheduling ■ Guaranteed Minimum Bandwidth - Feature Demo (Thu 15, 5:10pm - 5:50pm) ● Keystone ○ Unified limits + oslo.limit ■ Enforcing Quota Consistently with Unified Limits (Wed 14, 5:30pm - 5:40pm) ● Ironic ○ Use conductor groups to partition nova-compute services
Cross-Project Work (continued) ● Cyborg ○ Accelerator management ■ Related presentation: Cyborg: Accelerate Your Cloud! (Thu 15, 2:30pm - 3:10pm) ● Multiple projects ○ Transfer ownership of resources ■ Forum session: Change of ownership of resources (Thu 15, 1:40pm - 2:20pm)
Beyond Stein ● Accelerator management ● NUMA modeling with placement ○ Example: vGPU + NUMA ● Affinity modeling with placement ○ Late-affinity check cannot work with multi-cell and split message queues ● Partitioning/sharding/consumer-key in placement ○ What app am I? ○ What edge site/deployment/cluster am I in? ● Proper handling of shared storage
How to give feedback ● Report bugs ● Start a conversation in the openstack-dev@ and/or openstack-operators@ mailing lists ■ Soon to be only openstack-discuss@ on December 3 ○ Tell us how you or your users are using the compute service ○ What is missing? ○ What are your barriers to entry? ○ What deployment tooling do you need, i.e. nova-manage?
How to give feedback ● Attend Forum sessions ○ Cells v2 updates (Tue 13, 11:00am - 11:40am) ○ NFV/HPC Pain Points (Wed 14, 11:00am - 11:40am) ○ Boot from volume (BFV) improvements (Wed 14, 11:50am - 12:30pm) ○ Getting Operators' bugfixes upstreamed (Wed 14, 5:10pm - 5:50pm) ○ Concurrency limits for service instance creation (Thu 15, 11:40am - 12:20pm) ○ Change of ownership of resources (Thu 15, 1:40pm - 2:20pm) ○ Update on placement extraction from nova (Thu 15, 2:30pm - 3:10pm) ● Forum session etherpads ○ https://wiki.openstack.org/wiki/Forum/Berlin2018
How to contribute https://docs.openstack.org/nova/latest/contributor/index.html ● Subscribe to the openstack-dev mailing list and filter on [nova] ○ Soon to be openstack-discuss on December 3 ● Chat with us at #openstack-nova in freenode IRC ● Attend some weekly meetings: https://wiki.openstack.org/wiki/Meetings/Nova ● Help with bug triage ○ How-to docs: https://wiki.openstack.org/wiki/Nova/BugTriage ○ Forum session: Bug triage: Why not all the community? (Thu 15, 9:00am - 9:40am) ● Attend the Nova - Project Onboarding (Tue 13, 1:40pm - 2:20pm)
How to contribute ● Help with code reviews ● Help cleanup the docs; if something does not make sense or is missing, tell us - or better yet push a patch to fix it ● Try to break things and report bugs ● Perform scale testing and identify bottlenecks - and report them ● Propose bug fix backports to the stable branches
Q&A Thank you! openstack @OpenStack openstack OpenStackFoundation
Recommend
More recommend
