1 of 38

Status Updates

2 of 38

Rocky Retrospective

Sean McGinnis

3 of 38

Activity during the Rocky cycle

32,800 changes

(including 4,000 supporting changes on Infrastructure, Release and Requirements management)

4 of 38

Individual developers

% of changes authored

5 of 38

Individual developers

% of changes authored

245 individual developers�author 80% of changes

6 of 38

Individual developers

% of changes authored

66 individual developers�author 50% of changes

7 of 38

Most actively-developed services in Rocky

Nova
Cinder
Neutron
Placement
Ironic
Swift
Zun

8 of 38

Most actively-developed deployment projects

TripleO
OpenStack Ansible
PuppetOpenStack
OpenStack Charms
Kolla
OpenStack Helm

9 of 38

Rocky Deliverables

40 Services

55 Libraries

39 Clients

25 Horizon Plugins

687 total releases performed in Rocky

32 teams provided cycle highlight input to marketing message

10 of 38

Rocky Improvements

Minimize service downtime
Enhanced security
Support better cross cloud compatibility

https://releases.openstack.org/rocky/highlights.html

11 of 38

Stein Update

Doug Hellmann

12 of 38

Stein Community-wide Goals

Starting selection of goals for T series this week

https://governance.openstack.org/tc/goals/index.html

Default to Python 3 Latest stage in 6 year effort Jan 1, 2020 deadline All secondary jobs use python version 3 instead of 2 Functional tests running python 3 Distribute work of managing CI job settings Next step: Dropping Python 2 support in U cycle	Automated Pre-upgrade Checks Test upgrade readiness Consistent UI across projects Integrate with deployment tools

13 of 38

Project Team Themes for Stein

OpenStack Integration Bandwidth-aware scheduling Fault-tolerance for NFV Event notification consumption	Other OIP Integration Kata	Adjacent Communities Vault CSI for Filesystems Pod scheduling S3 API	Recruiting Translators Operators Users
Stability & Performance RBAC & Interop API testing Self-healing Container sharding Workflow performance	Future-proofing Python 3 Configuration management Next-gen edge server h/w	Security Config secrets TLS HSM backends	Usability SDK & CLI support Policy defaults Upgrades

14 of 38

Technical Committee Initiatives

15 of 38

TC Operational Changes

Doug Hellmann

16 of 38

Technical Committee Operational Changes

Resuming regular formal meetings Bylaws requirement Mindful of excluding participants in different timezones First Thursday of each month IRC, with minutes published to openstack-dev/discuss list	Vice Chair Leadership HA Rotates each cycle Mohammed Naser, Stein

17 of 38

Peer Review Culture Initiative

Julia Kreger

18 of 38

Origin

In Vancouver

Current contributors expressed difficulty in pushing forward positive changes in the community where code review culture was blocking.
Past contributors reconnected and echoed identical frustration.
Several organizations echoed the same frustration.

19 of 38

Culture Changes

Updated our principles

Stress value of Constructive Peer Review
Stress incremental improvement over perfection; follow-up versus down-voting or blocking

Added guidance on how to review changes

20 of 38

Result so far..

21 of 38

Vision for OpenStack Clouds

Zane Bitter

22 of 38

What does this mean to you?

Mission Statement:

To produce a ubiquitous Open Source Cloud Computing platform that is easy to use, simple to implement, interoperable between deployments, works well at all scales, and meets the needs of users and operators of both public and private clouds.

23 of 38

Why document a vision?

A longer-form statement of our vision for OpenStack clouds can help guide us when:

Evaluating new projects
Planning new features
Choosing project-wide goals
Telling stories to stakeholders

24 of 38

A word about scope

The scope of the official OpenStack project remains unchanged
The scope of the vision document is limited to the end-user-facing cloud services

25 of 38

The Pillars of Cloud

Self-service

Multitenancy
Usage controls (billing, quotas)

Application-facing

API access, events
Application auth with least privileges

26 of 38

OpenStack-specific Considerations

Interoperability
Bidirectional Compatibility
Cross-Project Dependencies
Partitioning�

27 of 38

Design Goals

Basic Physical Data Center Management
Plays Well With Others
Hardware Virtualisation
Infinite, Continuous Scaling
Built-in Reliability and Durability
Customisable Integration
Abstract Specialised Operations
Graphical User Interface

28 of 38

How to get involved

Gerrit

https://review.openstack.org/592205

Add a Vision statement for OpenStack clouds

project:openstack/governance status:open

Forum

"Vision for OpenStack clouds" discussion

Thursday at 14.30 in M8

29 of 38

Supporting Material

30 of 38

Integrating with OpenStack Services

Nova & Neutron – bandwidth-aware scheduling
Congress (policy), Tacker (NFV orchestration), & Monasca (monitoring) – fault-tolerance framework for NFV applications
Solum (SDLC) – Use Zun to boot containers
Watcher (infrastructure optimization) – Improved Monasca integration
Blazar (resource reservation) – Placement service integration
Monasca – Consuming event notifications
Masakari (instance HA) – HA for Ironic-deployed instances
Tricircle (cross-cloud networking) – Implementing new L3 model for Neutron for more reliability

31 of 38

Integrating with OIPs

Qinling (FaaS) – Kata
Storlets (compute inside object store) – Kata

32 of 38

Integrating with Adjacent Communities

Oslo (common code) – Configuration secrets in Vault
Manila (file systems) – CSI support for Kubernetes
Zun (containers) – Kubernetes connector interface for scheduling pods
Swift – S3 API improvements

33 of 38

Recruiting

I18n (translators) – Schools and universities
Searchlight (search) – Complete change in review team and leadership; local communities in Vietnam and Korea
Chef – Users/Operators
Documentation – Operators adopted Ops Guide, collaborating with Docs team
Cloudkitty (rating), Storlets (compute inside object storage), Trove (DBaaS)

34 of 38

Feature Stability and Performance

QA – RBAC and strict API testing (interop program)
Senlin (clustering) – Stability of self-healing use cases
Swift – Container sharding performance
Mistral (workflows) – Workflows run 3X faster
Kuryr (connect neutron to containers) – Better kubernetes integration allows better performance
Adjutant (operator integration) – Refactoring the worker to support asynchronous jobs and lay the foundation for future enhancements

35 of 38

Future-Proofing

Ironic – Next-gen server hardware support for security and edge deployments
Infrastructure – Modernizing configuration management system
Qinling (FaaS) – Python 3 user functions
RPM packaging – Python 3 packaging

36 of 38

Security

Oslo (common code) – Configuration secrets in Vault
Qiling (FaaS) – TLS and Kata support
Solum (SDLC) – Securing privilege escalation with common libraries
Barbican (secret storage) – Supporting additional storage backends

37 of 38

Usability

SDK – Fully discovery-driven with micro-version support
Manila (file systems) – SDK and CLI support
Keystone – Policy defaults in code for deployment simplicity
Kolla (containerized distribution) – Zero-downtime and fast-forward upgrades
Monasca (monitoring) – Combining services for easier deployment
Masakari (instance HA) – Exposing more status through notifications

38 of 38

Other New Features

Storlets (compute inside object storage) – Streaming data processing
Trove (DBaaS) – Cluster backups and upgrades
Karbor (data protection orchestration) – Backup and restore across clouds
Sahara (data processing) – V2 API completed (4 year effort)
Heat (orchestration) – Multi-cloud support