December and January are a favorite time of year for reflection on things past and anticipation for things to come.
2019 OSF community achievements, which I will leave to the others in this report to detail, are proof of the successful open source nature of our community in building the open infrastructure software powering today’s and tomorrow’s distributed cloud centered data centers.
A super big thank you to all the community contributors, leaders, staff, and users that have all come together to make these 2019 exciting developments possible. In particular, I would like to take this moment to thank the members of the OpenStack Foundation board for its leadership and commitment. Board members during 2019 include: Alan Clark, Allison Randal, Andy Cathrow, Anni Lai, Arkady Kanevsky, Brian Stein, ChangBo Guo (Eric), Christopher Price, Dr. Clemens Hardewig, Daniel Becker, Egle Sigler, Fred Li, Imad Sousou, Jeff Moyer, Johan Christenson, Joseph Wang, JunWei Liu, Mark McLoughlin, Mark Skarpness, Monty Taylor, Prakash Ramchandran, Rob Esker, Ryan Van Wyk, Ryan Beisner, Ruan HE, Sean McGinnis, Shane Wang, Tim Bell and Vijoy Pandey.
2019 success places OSF in a unique and exciting position for 2020 and the future. We can all be assured that challenges will be had, achievements made, and discoveries found throughout the coming year. I have strong confidence that we, as a community, will continue to deliver the open infrastructure needed to power, scale, and diversify tomorrow's cloud technology as we continue to strategically align with the transformational changes in tomorrow’s infrastructure needs.
Two days ago a 4 year old and I were conversing near a Bluetooth enabled speaker system. I mentioned to him that we should play some holiday music. He quickly turned toward the speaker and boldly said, “Speaker, play my music list”. At that moment it struck me that today’s user expectations have truly gone from simply connected to being smartly connected. Long gone are the days of the unconnected. Everything being smartly connected places requirements that the infrastructure be intelligent! That’s our challenge and anticipation for 2020. As we look to 2020 for project plans and new project ideas let’s build intelligent infrastructure!
Here’s to an exciting 2020 together as a community!
Alan Clark, Chairman of the OpenStack Foundation Board of Directors
A little over two years ago, we recognized that the community of the OpenStack Foundation had grown beyond a sole focus on OpenStack and had come to care about a broader ecosystem of open source projects. We embarked on a journey to find what role OSF should have in spreading the OpenStack way of collaborating and how the strengths and capabilities of the OSF could help other software communities grow and thrive.
Our goal was to do it in a focused way, oriented around emerging markets that were putting new demands on underlying infrastructure. We also wanted to stay true to our values, showing new communities the benefits of the Four Opens, while focusing on a pragmatic approach that prioritized the production of software.
This year, we saw those initial efforts reach a new level of maturity with the confirmation of three pilot projects, software releases from all projects, a new events model with the creation of the combined Open Infrastructure Summit and PTG, and increased adoption of our communities’ software. These results have shown that our approach works.
The confirmation of the pilot projects validated their progress and also the process that our community developed. I believe that process and structure strikes a nice balance between being lightweight enough to allow variation between individual projects while also ensuring a consistent level of openness in our communities.
These confirmations also garnered press coverage and started to raise awareness of our OSF expansion. And the new projects have opened up opportunities for engagement with many new companies, including some of the largest technology companies in the world, who have not historically been involved in OpenStack directly.
Going forward, there are improvements and growth possible in each of our projects, and our staff is looking at taking the lessons learned in 2018-2019 to create more documentation around our approach and model.
Within the OSF ecosystem, we held many in-person meetings this year to discuss our progress and strategy and the value our community brings to the open source infrastructure world. These meetings included every OSF Platinum and Gold Member, as well as new organizations around the world. In some cases these were newer organizations like Troila, who ultimately joined as a new Gold Member. Other times we worked with diverse users such as Baidu, who documented their large scale usage in a 40-page whitepaper, or auto manufacturers who use and contribute to Zuul. We were also able to participate in joint events throughout the year, speaking to thousands of employees, partners and customers, giving us the opportunity to spread our key messages even farther. This is definitely an activity we will continue into 2020.
We did all of this against a backdrop of global uncertainty amid a shifting geopolitical, technology and open source landscape. During one of the most significant “trade wars” in recent history, we threw a successful global Summit+PTG in Shanghai with attendees from 50 countries. The staff of the Foundation pulled together in an incredible way to deliver on our commitments to the communities we serve. While it definitely wasn’t an easy year, thanks to their efforts, it was a good year. As we look forward to 2020, I see enormous opportunities to build on the experience of the last few years to continue to grow our software communities, our commercial ecosystems and the entire open source movement.
Airship established incredible momentum in 2019, including confirmation by the OSF as a top-level project in October, a crucial stage of Airship’s maturity. The confirmation as a top-level project signifies the community’s many accomplishments since being announced as a pilot project supported by the OSF in May 2018, namely:
Airship is a robust mechanism for cloud operators who want to embrace containers as the new unit of infrastructure delivery at scale to manage the entire lifecycle of data center infrastructure using a unified, declarative, fully containerized, cloud native platform. Airship 1.0 was released at the Open Infrastructure Summit Denver in April. Its enterprise-readiness includes enhanced platform security, resiliency and platform deployment tooling. Airship 2.0 design and development was kicked off post 1.0 release. Its technical roadmap includes leveraging meta3-io for bare metal provisioning, the Cluster-API for Kubernetes bootstrapping and lifecycle management, Containerized Network Function (CNF) support, leverage cloud native workflow management (e.g. Argo), Helm v3 and Armada Operator, edge use cases, and YAML management improvement, etc. The picture below represents the target Airship 2.0 architecture:
The Airship team is excited to share the future plans – a complete rebuild of Airship core code migration from Python to Golang with an alpha release planned for early 1Q 2020, a beta release late 2Q 2020, and a full 2.0 release in 2020. In addition, Airship 2.0 will penetrate into more industry domains such as common telco NFVi and 5G testbed etc.
Kata Containers seamlessly delivers the speed of containers with the security of virtual machines. Kata Containers became a pilot project in December 2017, in conjunction with the OSF’s evolution from being the home for OpenStack to becoming the home of open infrastructure collaboration. In April of 2019, Kata Containers was the first OSF pilot project to graduate to become an official OSF open infrastructure project. This milestone acknowledged the project's strategic relevance, well-defined governance procedures, commitment to technical best practices and open collaboration, and most importantly, an actively engaged ecosystem of developers and users
The project enjoys a global, engaged and growing community as evidenced by its 2019 stats: 3,164 commits made by 110 authors representing 20+ companies.
2019 was a breakthrough year with production deployments of Kata Containers by some of the world's largest cloud service providers, notably in China and North America. In November of 2019, Baidu won the Superuser award at the Open Infrastructure Summit for its numerous production deployments of Kata in both their cloud as well as edge service offerings. More than 20,000 skills from 3,000 developers run in Kata Containers as part of Baidu’s Cloud Function Computing offering. Huawei also has multiple production deployments of Kata Containers in both their public cloud infrastructure as well as their Enterprise Intelligence Service, and in Alibaba and its related company Ant Financial, Kata Containers has been deployed in Alibaba's Cloud products and services, such as Edge Node Service (ENS), and is being tested for more cloud and financial applications. On the innovation front, Tencent is pioneering massive scaling of secure cloud gaming with Android in Kata Containers. Finally, in North America, Kata has been deployed by a leading Edge service provider as well as a popular software build services provider.
Although cloud service providers (CSPs) represent the early adopters of Kata Containers, in order to expand further into enterprise, support and integration by operating system vendors (OSVs) is essential. To that end, the project benefits from the deep technical expertise of developers from Red Hat (virtio-fs effort), SUSE (OBS and SLES integration) and Canonical (snap image, Charmed K8S integration). The snap image for Kata Containers in the Snapcraft store is up to nearly 3,400 weekly active users.
The Kata Containers Architecture Committee also went through two election cycles in February and Septermber 2019. Now the project is led by Eric Ernst (Intel), Samuel Ortiz (Intel), Xu Wang (Ant Financial, a related company of Alibaba), Justin He (ARM) and Haomin Cai (Huawei). The Architecture Committee members ensure that Kata Containers stays true to its goal of open collaboration and innovation around container speed and security.
Kata Containers development continues to thrive in 2019. With developers in Asia, the Americas and Europe, activity in the project's git and slack channel occurs around the clock. Developers with questions or issues genearally receive speedy and thorough responses. Since the 1.5 release in January of 2019, the project has delivered a steady beat of releases to both maintain stability and introduce new features. The 1.5 release included Firecracker hypervisor support, IBM s390 architecture support and a new method to integrate with containerd that greatly simplified Kata Containers architecture. The 1.6 release added open tracing support. The 1.7 release introduced an early preview of virtio-fs which was purposely designed and built for Kata Containers as a replacement of 9pfs. The 1.8 release focused on hypervisor improvements including qemu 4.0 and Firecracker jailer support, adding extra security isolation for the virtual machine manager (VMM) on the host. The 1.9 release towards the end of 2019 included Firecracker virtio-vsock support, rootless Kata with podman, experimental support for the ACRN hypervisor, and per pod custom configuration annotations.
Two OSF-sponsored open source hackathons were held in China in 2019 and Kata Containers was a featured project in both. It attracted developers from Alibaba, Baidu, Huawei and Tencent. Participants openly shared their adoption plans and feedback on the Kata Containers roadmap. The Kata Containers community continues to work closely with the OCI (Open Container Initiative) and Kubernetes communities to ensure compatibility. The Pod Overhead feature developed by Kata community was merged by Kubernetes as an alpha feature, to account for the resources consumed by the pod infrastructure on top of the container requests & limits. Following in the footsteps of RuntimeClass, Pod Overhead makes Kubernetes more Kata friendly.
Throughout 2019, in order to build awareness and interest for the project, the Kata Containers community presented technical updates and hosted gatherings at several global events including KubeCon + CloudNativeCon Barcelona, Open Infrastructure Summit Denver, KubeCon Shanghai and the Open Infrastructure Summit Shanghai. Kata Containers was also featured at several OpenInfra Days, OpenStack Days and other container-focused meetups around the world.
Looking ahead to 2020, the Kata community will focus on supporting its growing user community, driving innovation with the Kata 2.0 roadmap, and continuing open collaboration with the rapidly expanding container ecosystem.
The code is hosted on Github under the Apache 2 license. Learn about the project, how to contribute and support the community at katacontainers.io. Join these channels to get involved:
A total of 1,518 unique change authors approved more than 47,500 changes and published two major releases, code named Stein and Train (due to our undying love of Trains). We started to work on Ussuri, our next release, to be delivered in 2020. In 2018, we introduced the "Extended Maintenance" concept, a period on which bugfixes can be accepted for projects following it (but these won't produce further releases). As of today, Ocata, Pike, and Queens are in extended maintenance.
Like in 2018, the component project teams completed work on stability, performance, and operational/usability improvements. They also worked on themes related to integrating with other OpenStack components, other OpenStack Foundation Open Infrastructure Projects, and projects from adjacent communities, for example Kubernetes or Ansible. We have introduced a deployment tools capabilities map, to make it even easier for new users to select their deployment tool of choice.
In addition to component-specific work, we continued to improve our OpenStack-wide processes by adding pop up teams next to goals, in order to have more flexibility on achieving large scale changes. During 2019, we have added two pop up teams "Image Encryption" (implementing encryption and decryption of images and the handling of those images in OpenStack) and the "Secure Default Policies" (consistent policies across OpenStack). This is in addition to our OpenStack wide goals: we made sure all the projects can render their documentation into PDFs, ensured that OpenStack works and is tested in IPv6 only environments (not only dual stacks!). We are also making sure the community is moving up in the python versions with an ultimate removal of python2 of our development pipelines in 2020.
The Technical Committee (TC) itself has evolved in 2019. We plan to reduce our members to 9 in 2020. Over the whole year, Chris Dent, Davanum Srinivas, Sean McGinnis, Doug Hellmann, Jeremy Stanley, Lance Bragstad, and Julia Kreger left the TC, to make way for first-time members Alexandra Settle, Jim Rollenhagen, Rico Lin, Kendall Nelson, Kevin Carter, Nate Johnston, and Jay Bryant.
2019 saw the beginnings of a transition from OpenStack project infrastructure hosting into OpenDev project hosting. This process will eventually separate our project hosting tools from OpenStack itself so that they may be more clearly reused by other projects. We expect to make significant progress on this transition in 2020.
With the input from the OpenStack Foundation board, the OpenStack TC updated its "help wanted list" to actively track where business and leadership opportunities can be for companies willing to invest in OpenStack.
During 2019, the OpenStack project infrastructure was renamed opendev.org, to make it clearer it can be used beyond OpenStack. Using Opendev namespaces, we now have a clear separation between official OpenStack projects and non-OpenStack open source projects developed under the same development tooling. In terms of project teams, the most visible change in 2019 was the extraction of Placement from the Nova team. Regarding SIGs, we are launching a "Multi-architecture" SIG (including the orginal work from the PowerVM project team which became the PowerVM SIG...), Ansible SIG, Containers SIG, Auto-scaling SIG (which is planned to merge with the existing self-healing SIG to form a new Automation SIG in the near future), Large Scale SIG, Technical Writing SIG, Public Cloud SIG (migrated from Public Cloud WG), Bare Metal SIG, and Edge Computing SIG (renamed from FEMDC SIG). This year, we closed down the Upgrade SIG, as we consider their work achieved and completed. This year, a lot of work was done to help creating and maintaining new SIGs (thanks to the "Meta SIG" team). This includes more guidelines and reference documents. As usual, the TC members will continue their work to expose SIGs broadly, to ensure all the different profiles and interests in OpenStack are efficiently represented, working, and collaborating together.
In 2019, the OpenStack User Committee (UC) brought onboard several new members including John Studarus (February electee), Belmiro Moreira (February electee), Mohamed Elsakhawy (August electee), and Jaesuk Ahn (September electee). Amy Marrich was re-elected to continue their service on the UC.
In this year we worked closely with the OpenStack Foundation staff to adopt new policies to better support the user groups. The migration of the user groups onto Meetup.com has allowed us to better support groups through local leadership transitions and reduce technical headaches. We also smoothed the process for new user groups to come online and be supported by the Foundation increasing the reach in these new and emerging regions of the world.
We continue to identify ways in which the new technologies developed can be promoted and evangelized. We believe the current Ambassador program, which is currently focused on supporting the user groups, can either be modified, or a new program created to help support those individuals actively promoting and evangelize our open source offerings.
The UC took an active role in updating the SIG and Working Group records to better reflect the leadership, goals, and status of these entities. We feel that having accurate records allows those looking to get involved to readily find the active communities.
The UC has been investigating reducing its membership from five (5) to three (3) members with plans to have the membership rules modified in time for the February 2020 election. We believe having fewer UC members will make it easier to keep the UC fully elected.
StarlingX is a pilot project supported by the OpenStack Foundation that was announced May 2018. The project integrates well-known open source project including OpenStack, Ceph, Kubernetes, and more to create a cloud platform that is fine tuned for edge and IoT use cases.
During 2019 the community was working on creating a fusion between OpenStack and Kubernetes services to provide infrastructure software that creates a flexible environment to support virtual, containerized, or bare metal workloads.
The StarlingX community put out two major releases of the software during the year: StarlingX 2.0 (latest version is 2.0.1) and StarlingX 3.0. The 2.0 release introduced fundamental changes to the architecture including containerizing OpenStack and other services to provide more flexibility, robustness, and increased manageability. Besides architectural changes community members were also focusing on features to improve security and performance including to start work on creating a performance testing framework to ensure maintaining high standards on an ongoing basis. The 3.0 release add a crucial component called Distributed Cloud architecture to provide synchronization across edge sites. The feature is in line with the Distributed Control Plane scenario of the OSF Edge Computing Group’s Reference Architecture models.
The latest release is also integrating the Train version of OpenStack. This was an important step as with this step StarlingX doesn’t carry more enhancements to the project as extra patches and the team members are actively working with the OpenStack community on further improvements and new functionality upstream.
The community has reached another milestone by having a fully elected leadership. The Technical Steering Committee (TSC) had two elections replacing half of the group each time while Project Leads and Technical Leads got elected during the second half of the year. Elections will be held on a regular basis going forward.
Further high priority items included community building and outreach. It is very important for the project to lower the boundaries of entry and make sure that it is easy for newcomers to find entry points. The community has been actively working on improving documentation and creating materials to guide new contributors. The project held a Contributor Meetup in the USA and further meetups and meetup for release 2.0 and hackathons in China last year and community members also took advantage of the Project Team Gatherings as well as the Open Infrastructure Summits and Forums to have face to face discussions as well as to onboard newcomers. Some of the team members put together a hands-on workshop which guides participants through installing StarlingX and trying out some of the features it provides. Community members ran the training at various OSF and industry events throughout the year. The infrastructure is running on hardware donated by Packet.com.
The project had 3359 changes committed by 147 authors from more than 10 organizations during the year.
The code is hosted on Github under the Apache 2 license. Learn about the project, how to contribute and support the community at starlingx.io. Join these channels to get involved:
Zuul is an open source CI/CD platform designed for test-driven open source projects and software development organizations who need to gate against multiple projects and systems before landing a single patch. Since 2012, Zuul has been proven at scale as a critical part of the OpenStack development process. As more users and use cases emerged, the team has been decoupling Zuul from OpenStack-specific systems. 2018's Zuul version 3.0 release was a major landmark in making Zuul generally usable outside of the OpenStack project. In 2019 Zuul has taken general usability even futher, focusing on adding features for a variety of code review systems, cloud resource providers, and container based testing workflows.
More than 1,000 changes were made to Zuul in 2019. In an effort to ensure new features and bug fixes reach Zuul users quickly, Zuul has been releasing often, publishing 17 releases in 2019. In this collection of releases support was added for Pagure code review system, AWS cloud resource provider in Nodepool, OpenShift cloud resource provider in Nodepool, improvements to live console log streaming, build dashboards and log navigation and much more.
Zuul version 3.7.0 added support for multiple versions of Ansible. With current Zuul deployed, users can select which version of Ansible they want their jobs to run with out of Ansible versions 2.6, 2.7, 2.8, and 2.9.
Zuul's standard library saw a major addition of container aware jobs. These standard container base jobs allow Zuul users to do speculative gating of their container images in addition to their source repositories. This feature helps to ensure that the images you deploy to production are identical to those tested and known to work while still having all of the benfits of speculative merge gating.
We see these improvements in production, where Zuul is helping a variety of users at different scales produce and deploy quality software. Good Money's 900 jobs a month enable reliable software deployments. At France's Internet flea market, leboncoin, 60,000 jobs a month help you find forgotten treasure. OpenDev's Zuul ran more than 2 million jobs to help produce the OpenStack Train release.
Ansiblefest and Gerrit User summit were important events for us in 2019. Not only have we continued to see interest in Zuul from users at Ansiblefest, but Vexxhost launched the first known Zuul as a Service service there. At Gerrit User Summit we discovered Volvo is a happy Zuul user. We have also begun collaborating with the Gerrit project to add Gerrit Checks API support to Zuul. Our goal is to have a Zuul running to help gate the Gerrit project once this feature is added.
Looking ahead, the Gerrit Checks API is only one of many features we would like to add to Zuul. From an integration standpoint Gitlab and Bitbucket support is under active development, changes have begun to merge to add Google Compute Engine support to Nodepool, and Microsoft Azure driver work has begun. We still have plans to remove the current single point of failure for the scheduler process and manage job and queue state with the distributed database. This will make it easier to run Zuul reliably without downtime.
All of this is possible through the work of our global community. We are proud to say we have contributors from across the globe, including Africa, Asia, Australia, North and South America, and Europe. We thank them for helping to make Zuul possible.
Zuul is free and open source software licensed under the Apache 2 license. If you would like to get involved, join us:
Public relations efforts are led by a distributed team of professionals in the United States, Europe, and Asia. This team engaged analysts and journalists worldwide in dialogue, proactively delivering news, commentary, and contributed byline content for both the Foundation and for its individual projects. Community news highlights are available at the OpenStack Foundation news page.
Key media relations initiatives included the following:
Analysis shows that OpenStack Foundation news coverage comprised more than 41,500 total placements in 2019 with a potential reach of 71 billion. Media coverage was more than 93% positive or neutral. (Social media coverage accounted for an additional 129,000 mentions, with more than 86% positive or neutral). Media coverage was distributed globally (54% APAC, 34% North America, 12% Europe, by volume), with APAC coverage surging this year as a result of a year-long emphasis on the Open Infrastructure Summit in Shanghai.
As evidenced by the highlights shared below, media attention has shifted from questions about OpenStack’s future to an active interest in use cases and the progress of the other projects supported by the OpenStack Foundation.
The OpenStack Foundation conducted 22 private briefing sessions with analysts in 2019 in addition to hosting a half-day Analyst Briefing and open roundtables at the Open Infrastructure Summit in Denver as well as a press conference and roundtables at the Open Infrastructure Summit in Shanghai.
Analyst coverage of OpenStack Foundation projects in 2019 portrayed a factual and positive tone for the most part, peaking with the publication of OpenStack Market Monitor by 451 Research in September 2019.
Here are some key excerpts from 451 Research's report:
For more information about analyst coverage of OpenStack Foundation projects, visit the OSF analysts page.
OSF user groups are an integral part of the community, bringing together OSF project users, operators, and developers all over the world to discuss common problems, use cases, and even workshops in casual or more formal settings.
In early 2019, we moved all of our official User Groups to Meetup Pro, which allows them more visibility and ease of planning events. These groups held meetups all around the globe throughout the year, passing a number of milestones on the way. In July, 25 groups from 20 countries celebrated nine years of the OpenStack project and seven years of the OSF, with some groups bringing as many as 200 attendees together for the festivities. Community members gave presentations, handed out awards, printed t-shirts and stickers, and ate birthday cake to celebrate “for the love of open.”
The Open Infrastructure Community Newsletter regularly shares the latest developments and activities across open infrastructure projects, events, and users supported by the OSF. The newsletters are sent out to the community in English through email, and they are also published to the OpenStack official WeChat account in Chinese.
Since January 2019, 18 newsletters have been distributed to the open infrastructure community. There have been more than 40,000 people who have opened at least one newsletter for the past year and more than 267,000 views on all the newsletters.
Looking forward to 2020, we will continue to deliver the most updated quality content to the open infrastructure community and create awareness among the broader audience in the community. Check out past newsletters, subscribe to the newsletter, and if you would like to contribute content, please email [email protected].
The rust-vmm project was created in early 2019 by AWS and Intel. The foundational idea behind it is to create a collection of Rust crates for building custom Virtual Machine Monitors (VMM).
In one year, the project has moved from an empty community GitHub repository to a set of fundamental crates providing the initial steps for building KVM based VMMs. A common set of tests and a unified Continuous Integration (CI) pipeline automatically gate any new contributions on those crates.
A few projects like AWS Firecracker, Alibaba Dragonball or Intel Cloud Hypervisor are using the rust-vmm crates, leading to increased contributions from these companies. We’ve also seen other contributions from e.g. ARM, Cloudbase or Red Hat.
Community wise, the project and its goals have been presented at various conferences and events like the Open Infrastructure Summit, KubeCon, FOSDEM and the KVM Forum. In order to increase external contributions, simple guidelines have been documented for adding new crates, contributing to existing crates, and understanding how the rust-vmm review and merge process works. Last but not least, rust-vmm now has its own logos, thanks to the OpenStack Foundation.
In one year, the project structured itself around the rust-vmm GitHub organization. As a community, it was decided that each VMM feature it wanted to support through rust-vmm will be living under its own dedicated git repository under the rust-vmm organization. Each of those repos is structured as a standalone Rust crate, and can thus be consumed and imported as such by downstream components. A special repository, the community one, is dedicated to community and architectural discussions.
There are currently 19 repos under the rust-vmm GitHub organization, including the community one. Roughly 12 of them are seeing active development although code maturity varies between repos. The current rust-vmm crates have been classified into three different buckets:
As a project, the community has defined a common set of tests and a unified buildkite based Continuous Integration (CI) pipeline. Each new repository created under the rust-vmm organization will use that CI and its default tests. The goal behind this is to force and mandate a common set of quality and integration gates for each and every rust-vmm crate.
The rust-vmm crates' CI automatically runs on bare metal instances (Both ARM and x86, 64-bit) donated to the project by AWS.
By nature, the rust-vmm project is not an easy one to contribute to. Experience with the Rust language, and familiarity with hardware virtualization and VMM concepts are basic requirements for contributing to most rust-vmm crates. As a consequence, the community is growing steadily but slowly. We have seen some contributions from AWS, Intel, Alibaba, and Red Hat as well as contributions from ARM engineers.
In order to make contributing easier and transparent, the community has worked on a few things:
AWS also kindly organized and hosted a rust-vmm meetup in Bucharest. Most of the project contributors attended the event, which helped quite a bit with not only moving forward technically but also strengthening the nascent community links.
The following projects are using rust-vmm crates to build their custom VMM:
This year marked an important milestone for OpenStack and the Ironic team as the OSF launched the OpenStack Ironic Bare Metal Program on the keynote stage of the Open Infrastructure Summit in Denver. Ironic has become a vital part of OpenStack deployments. In fact, according to the 2018 OpenStack User Survey, “adoption of Ironic grew rapidly with 24% of production deployments now relying on it, up from just 9% in 2016.” The purpose of this newly launched program was to bring more visibility to the usage of Ironic and OpenStack on bare metal. The goal of increasing visibility was to not only showcase the success of Ironic and OpenStack in bare metal, but to create an avenue for users, operators and developers to further collaborate. The launch was a success, with more than 30 users and vendors like Tencent, CERN, and Red Hat joining the program with several also contributing case studies. One of the most exciting examples of bare metal used at scale was Verizon Media. James Penick, Architect Director, spoke on the keynote stage in Denver about how they use Ironic to manage hundreds of thousands of bare metal compute resources with over 4 million cores in their data centers. Learn more with the launch of the OpenStack Ironic Bare Metal Program and James Penick’s keynote.
Here are the participants of the OpenStack Ironic Bare Metal Program:
In 2019 OpenStack Upstream Institute was held in seven countries, two of which for the first time. In total over 200 new contributors were on-boarded to the OpenStack community. The training attendees learned about OpenStack governance, the release process, and, most importantly, how to setup and use the tools the community leverages on a daily basis to communicate and collaborate.
Thanks to Lenovo, the training was held preceding both Summits this year. In Denver it was hosted as a single day event at the conference venue with office hours the day before to answer any getting started questions. In Shanghai, it was hosted at Lenovo’s office as a day and a half long event.
The OpenStack Upstream Institute training team has worked on making the training a standalone package that anyone can pick up and run locally either within their organization or with members within their geographical region. Two great examples of this in 2019 were in Japan and India where the majority of the community members who were running the training are not closely involved in the team and were still able to make their courses a success. In addition, between those two sessions alone, these local communities brought the training to and shared knowledge with over 120 attendees.
In 2020, the team hopes to evolve the training even more than the last few years. The team plans to break it apart into two major modules: one containing OpenStack specific information and the other describing the aforementioned tools (OpenDev). This improvement will provide further flexibility to the training to run only the desired parts. With separating sections of the training material, the modules will be applicable and usable for any project under the OpenStack Foundation umbrella to pick up and build them into their own courses.
Over the last few years, the OpenStack Technical Committee (TC) maintained the 'Help Most Needed' list that enumerated the five areas where the OpenStack community needed contributions to significantly help OpenStack as a whole. This was promoted through various forums including presentation to the Board of Directors to get help from the corporate as well as the academic side.
The original format did not garner the help the TC had hoped so they decided to come at it from another angle. The TC thought a restructuring would help to make it clear that the 'Help Most Needed' list is not only the desires of the community but also provides direct value to sponsoring organizations of OpenStack. This year the TC renamed the 'Help Most Needed' list to 'Upstream Investment Opportunities' and added business values for each opportunity.
As per new process, the TC will refresh the list every calendar year and add new opportunities by evaluating the business cases through an understanding of the needs of potential contributing organizations. You can find the 2019 Upstream Investment Opportunities here.
The OpenStack Foundation helps new and key contributors who are unable to secure sponsorship to attend events by subsidizing or covering the costs for travel and accommodations. In 2019, the Foundation set aside a budget for each Summit & PTG, which is combined with donations from individuals from the community to fund this program.
Ten additional community members from seven countries were able to attend the Denver Summit & PTG in April 2019, thanks to $2,905 in donations from 27 individuals, combined with an investment of $22,000 from the OpenStack Foundation.
Twelve community members from seven countries were able to attend the Shanghai Summit & PTG in November 2019, thanks to $1,016 in donations from 11 individuals, combined with an investment of $15,000 from the OpenStack Foundation.
May - August 2019
December 2019 - March 2020
During the Summit in Vancouver in May 2018, a discussion started during a Forum session about getting more university students involved in OpenStack. The OpenStack community and project provides a lot of practical experience and has the opportunity to teach students skills in collaboration in a large, global community while having the added benefit to OpenStack of new contributors working on backlogs of action items.
Having already been using OpenStack in its campus lab and already having a history of relationships with the university via alumni, the Oregon State University was interested in helping to coordinate an internship program. Collaborating with OpenStack community members, it was concluded that the two projects most in need of help were Glance (the Image project) and Designate (the DNS project). Contributors to these projects joined the conversations and helped brainstorm where funding for interns could be found. Currently, the OpenStack Foundation is sponsoring one student from the university to work on the Glance project with plans for more interns to work on Designate if funding from other organizations can be established.
At the end of last year, Lance Bragstad, a North Dakota State University alumni and former Keystone PTL, reached out the mailing list looking for mentors to participate in a Capstone project for students at the university. Students would do real work in the community throughout the semester led by one or more mentors. Chris Hoge, Kendall Nelson, and Jeremy Stanley worked with three students to accomplish work across two different OpenStack projects. They worked on a cleanroom implementation of the puppet setup for a version control system and a migration script for moving bugs from Launchpad to StoryBoard. While the work itself was important to the OpenStack community, the skills the students learned working in a community as large and diverse as OpenStack will benefit them long after graduation.
The professor liked the results of the community’s work with the students so much that he has asked the community to participate again. For the next round of students, starting in January, Michael Johnson, Adam Harwell, and Kendall Nelson will mentor students working on Octavia, the load balancer OpenStack project.
This year, 16 people were added to the list of Community Contributor Award recipients. These amazing people have helped not just the OpenStack project, but the entire open infrastructure community. Recipients represented other top level projects beyond just OpenStack such as Airship, Kata Containers, and StarlingX where historically only contributors to OpenStack had been represented.
In Denver, Eric Ernst and Kendall Nelson presented awards to the following people:
In Shanghai, Xu Wang and Kendall Nelson presented awards to the following people:
Also new this year, the awards are now recorded on their foundation member profiles. Each recipient has the award and place they received it at listed. If they have received multiple awards, they are enumerated together.
Open Infrastructure starts with OpenStack, and users are increasingly relying on the integration of additional open technologies to power their workloads. In 2019, the OpenStack Summit was renamed to the Open Infrastructure Summit to reflect this trend and create a more diverse focus on the open-source projects being built to support open infrastructure.
The first Open Infrastructure Summit was held in Denver, Colorado in April 2019, gathering attendees from 50+ different countries to discuss 30+ open source projects. In addition to use cases from users like AT&T , Blizzard Entertainment , Box, Reliance Jio, Verizon Media, and more, there were several announcements made in Denver:
The second Open Infrastructure Summit brought attendees from over 45 countries to Shanghai, China in November 2019, and was followed by the Project Teams Gathering (PTG). Use cases, tutorials, and demos covering 40+ open source projects including Airship, Ceph, Hadoop, Kata Containers, Kubernetes, OpenStack, StarlingX, and Zuul were featured at the Summit. In addition to use cases from users like China Railway, China Mobile, Walmart Labs, LINE and China UnionPay, and more, there were several announcements made in Shanghai:
Having switched from last year’s model of stand alone Project Teams Gatherings, this year both events were co-located with Open Infrastructure Summits. At the beginning of this year, following the Denver Summit, the first colocated PTG was held. There were 391 attendees across 46 teams who attended the PTG in Denver. In Shanghai, approximately 300 attendees across 44 teams attended, including the recently confirmed top level project Airship. StarlingX and Kata Containers also met at both PTGs.
Both events were organized similarly in terms of schedule. Depending on the team’s request for time and space, they had varying amounts of space and time, but, roughly, the first day or two were horizontal teams- Special Interest Groups and Working Groups- while the rest of the week was filled with vertical teams- Cinder, Neutron, Nova, Kata Containers, etc. To make sure to accommodate all teams, both events had reservable space for groups that did not formally request time/space to meet.
The PTGbot continues to be an asset to this event. It allows teams to reserve extra time and space in the schedule. It also gives teams the ability to announce what they are talking about so that people interested in the topics being discussed know when to change rooms if they are involved in more than one team.
In Shanghai, the PTG had a day and a half of overlap with the Summit and it was the first PTG that was hosted where the majority of teams shared one large space together rather than all having their separate rooms. Shanghai also brought a different focus for the PTG. With the potential for a lot of new faces to attend, project onboarding was hosted during the PTG instead of during the Summit, which helped several teams gain new contributors.
The global open infrastructure community organized 12 OpenStack/OpenInfra Day events in Germany, Indonesia, two in Italy, Japan, Korea, Poland, Taiwan, Sweden, at CERN in Switzerland, UK, and Vietnam - educating close to 5,000 attendees around the world.
The typical attendee reached at these local events are cloud and IT architects, software developers, platform and solution engineers and product management.
These one or two day regional events are organized by the local community and supported by the OSF to include project workshops, upstream training, and booths from the local ecosystem. These events continue to be an excellent touchstone for the community to engage with our ecosystem, and to gather local open source developers and users to collaborate, share use cases, and support for the OSF projects.
“99Cloud, founded in 2012, is one of the earliest and most famous companies in open infrastructure. We witnessed the birth and growth of the OpenStack community and have been heavily contributing to the community for 8 years with high ranking in many aspects. We serve customers with OpenStack in government, financial banking, telco, energy, etc. “What's past is prologue”. 5G is coming. 99Cloud extends the strategy from cloud to edge based on our expertise in OpenStack. We will continue participating in the OpenStack community and involving in new projects such as StarlingX and Airship, implementing open edge cloud solution. We were glad to see that the Open Infrastructure Summit Shanghai burned with passion in China and we look forward to the continuous prosperity of the community in 2020.” - Shuquan Huang, Technical Director, 99Cloud
“The OpenStack community – and the Open Infrastructure Projects it supports – remains vital to the transformation to software defined networks. The OpenStack Foundation’s support of the Airship project was critical to it achieving confirmation in 2019. The project is now rapidly maturing to not only support predictable deployments of OpenStack clouds, but also enable an in-place evolution in 2020 and beyond of those clouds to support both VNFs and CNFs on the same footprint. At AT&T, we will continue to support the OpenStack Foundation and community through code contribution and membership in 2020." - Ryan van Wyk – VP Network Cloud, AT&T
“As an established leader in the cloud market, Canonical has been involved in OpenStack development since the very early days. This marks the company’s long-term commitment to open infrastructure and improving the cost of cloud operations. Canonical is delighted to continue to support the OpenStack Foundation, in partnership with leading system integrators, to help enterprises address new challenges such as bringing OpenStack from the cloud to the edge.” - Tytus Kurek, Product Manager, Canonical
"2019 proved to be the year when regulations took a larger role in a world where the few dominate the cloud space. Nations woke up and realized that data sovereignty is important and maybe nations truly need to have control of certain data? This is the normal situation when you work with banks and other heavily regulated industries like City Network does. That feeling of control has expanded dramatically - to other industries and to nations. OpenStack has again proven to be the one platform those countries and industries rely on for both private- and public offerings in order to satisfy those regulatory requirements. Innovation has crept up as a longer term key aspect in what platforms to choose - as well as how to build those hybrid solutions. The OpenStack Foundation filled that void not only by delivering an improved OpenStack but also four new projects that continue to expand and allow organizations to innovate on open platforms. 2020 will be an exciting year for the OSF as the need for choice continues to expand." - Johan Christenson, CEO, City Network
“Red Hat continues to be excited about our ongoing collaboration with the OpenStack community. For many of Red Hat’s largest customers, OpenStack is the heart of current and future deployment plans. With a proven track record of security, stability and the reliability which use cases such as telecommunications and edge infrastructure require, OpenStack is critical for our customers, their partners and for the millions of consumers of services running on that infrastructure. We look forward to an exciting future for Red Hat’s continued strong partnership with the OpenStack Foundation and community as we deliver on the vision of the Open Hybrid Cloud.” - Daniel Becker, Director of Engineering, Red Hat
“Troila Technology has always been committed to transforming outstanding open source technology into the commercial value of customers. Troila Kunlun Cloud is our most successful business practice under the OpenStack technology architecture. In 2019, we became the Gold Member of the OSF and conducted in-depth exchanges and cooperation with OSF. We firmly believe that the open source value is not only the code contribution, but also we should pay more attention to the work beyond the code. As a strategic partner, in 2020 we plan to build a joint laboratory with OSF for the R & D and testing of OpenStack project, build a more complete open-source ecosystem, and continue to promote the innovative application of OpenStack in China. We will also participate more actively in community activities, closely communicate with the Foundation, maintain advanced technology, and continue to contribute excellent codes to the community. Of course, we will also provide customers with more mature, stable and efficient cloud products and solutions based on OpenStack, and share more industry practices.” - Zhang Kunyu, Troila Technology
The Diversity Working Group shared the results from the two Diversity Surveys with the CHAOSS project and Open Source communities in order to give insight to the types of questions we used as well as the status of diversity within the OpenStack project over time. We continued with having sponsored Diversity Networking Lunch in both Denver and Shanghai at the Summits. We also had pronoun stickers available at the Summit in Denver We are continuing to work on revitalizing the Cohort Mentoring program and gained new leaders (Meg Heisler and Pete Vander Giessen) for the program during the BoF session held in Denver.
Looking forward to 2020, we will be reaching out to the other OSF projects and inviting them to join our efforts as we are not OpenStack specific and hope to continue offering opportunities for diversity at events and in the community.