What Operators Can Expect to Discuss with the OpenStack Manila Team at the PTG

If you’re an OpenStack operator, you should check out my previous blog post about why you should attend the upcoming Project Teams Gathering (PTG). In an effort to help OpenStack operators get the most out of a PTG, we surveyed some project team leads (PTLs)  about the operator engagement they would most like to see. First up, we have Nova!

Special thanks to the Manila team, lead by PTL Goutham Pacha Ravi for taking time to put together these responses.

What do you want to hear from operators about at the PTG?

In the Shared File Systems service (manila) project, for the past three virtual PTGs we have invited one or two operators to share specific concerns with us. The discussions that followed have spawned several bugs and blueprints. We’ve discussed operational best practices, sporadic problems that arise at scale, storage for application containers, continuous integration testing, interoperability and missing features.

For this PTG, we would like to do the same – the strategy of keeping it to a few burning issues has certainly been very helpful. Our topics aren’t set in stone yet, but for starters, we’d like to get operator feedback on deploying and managing Manila with CephFS. Alongside, we want to know the strategies used by operators to maintain high availability of the control plane; and finally, we want to get feedback on several parallel community-wide efforts:

  • Secure RBAC and “system” personas
  • Federal Information Processing Standards (FIPS)
  • Adoption of the OpenStackClient

What topics are already on your agenda?

We’ve started collecting them here: https://etherpad.opendev.org/p/columbus-ptg-manila-planning

What are your goals for the Columbus PTG?

Streamline and prioritize code contributor and reviewer efforts for the Antelope cycle, highlight technical debt and get help.

We look forward to seeing EVERYONE at the PTG in Columbus!

The early bird deadline for registration is August 15th; the hotel block also has limited space, so make sure to book early before space runs out.

Another reminder, the final list of teams attending the PTG will be published on August 12th! If you haven’t signed your team up yet, do it now!

What Operators Can Expect to Discuss with the OpenStack Nova Team at the PTG

If you’re an OpenStack operator, you should check out my previous blog post about why you should attend the upcoming Project Teams Gathering (PTG). In an effort to help OpenStack operators get the most out of a PTG, we surveyed some project team leads (PTLs)  about the operator engagement they would most like to see. First up, we have Nova!

Special thanks to the Nova team for taking time to put together these responses.

After talking things over with his team, Sylvain Bauza, the Nova PTL, sent us some summaries of feedback they collected in this etherpad:  https://etherpad.opendev.org/p/nova-ptg-columbus-ops-presence.

What do you want to hear from operators about at the PTG?

In general, we expect some feedback from the operators about their usecases and how they use some Nova features when we discuss about some new design enhancements in the PTG room.But this time, as we had a meet-and-greet session in Berlin where operators also provided their pain points, it would be nice if we could also discuss about those issues and what we could do for fixing them.

What topics are already on your agenda?

In general, we only have an agenda in the last week(s?) before the PTG but we already have some points we know we would like to discuss : 

  • Ironic has an issue with rebalancing nodes so I’d love to discuss with both the Ironic contributors but also the operators to understand their problems and how we could fix this. 
  • Given of the new RBAC policies, we would need to continue discussing how to modify our APIs for them. Having for example public cloud operators around would be loved as they could explain us which kind of values they would like to see as default. 
  • Because of the new tick-tock release model, we need to think about both the Antelope release and the BB and CC releases to see how we organize upgrades. 
  • We also want to discuss about sustainability in Nova and how to support Scaphandre. I guess operators would like to hear about what we could work on Antelope and what they would prefer to see first. 

What are your goals for the Columbus PTG?

Basically, planning the Antelope release from a design perspective and discussing about next cycles (at least for BB and CC releases), like we do at every PTG, but if were having operators, we could also make sure we would have a specific Nova operators-welcome day (eg. on Tuesday) where the team would discuss about features and pain points while refraining ourselves to go into technical deepdive discussions with whiteboards etc.

This is just ONE team, there are already about a dozen teams signed up to participate, and there’s still more time for teams to signup so we expect there will be many conversations that would be important for operators to paricipate in! 

The early bird deadline for registration is August 15th; the discounted hotel block also has limited space, so book early! 

The final list of teams attending the PTG will be published on August 12th!

How to Have a Successful PTG as an OpenStack Operator

Myth: Project Teams Gatherings (PTGs) are working events organized by the OpenInfra Foundation only for OpenStack developers to collaborate on an upcoming release. 

Let’s break that down. 

Project Teams Gatherings (PTGs) are working events organized by the OpenInfra Foundation: CORRECT. PTGs are only for OpenStack developers to collaborate on an upcoming release: WRONG

While PTGs are for OpenStack developers, attendees form a broader group to make the event successful. This includes operators who are running projects in production, plan to run the project in the future or projects they have feedback for.  Even if you are running an older release of OpenStack, your feedback and questions and opinions are still incredibly valuable!

Who should attend a PTG? 

First of all, any open source project is welcome to participate in the PTG. Typically, the majority of attendees are from an OpenInfra project—OpenStack, Kata Containers, StarlingX—but other adjacent communities are also invited and encouraged to attend. 

It’s also not limited to upstream contributors. Any team can participate in the PTG—that means that its not just projects, its also SIGs, Working Groups, pop-up teams and other forms of collaboration! There are of course the usual suspects that typically attend—contributors from OpenStack, StarlingX, and Kata—but subteams within those projects also can meet (RBAC pop-up, Nova, Neutron, Manila, Large Scale SIG, etc), in addition to Foundation level working groups like the Edge Computing Group and Diversity and Inclusion Working Group who also participate.

These teams group source their agendas after they sign up to attend, so if you are interested in bringing up a topic with them, please do! Many of the teams use etherpads to collect topics and then gauge interest levels of people planning to attend before organizing the dicussion topics into a schedule. While they are doing this collection of topics, they are also signing up for time + space to meet, so if there is a topic you want to talk about but you can’t be there, let them know in the etherpad so they can try to accomodate your schedule! 

You are encouraged to attend as many groups meetings as you would like. Different teams will be meeting throughout the week. As an example, it’s totally okay to attend  Nova discussions in the morning before headed to the Zuul room after lunch and then pop over to the Cinder room for a particular discussion on CEPH that you are interested in. Teams try to expose the topics they are actively talking about and planning to talk about next via the PTGBot- more on that later.

Specifically, how should OpenStack operators participate at PTGs?

Of course there will be topics that are more specific to operations and using OpenStack clouds that might not fit into any particular team or group signed up, the OpenStack operators are a team and are encouraged to sign up for time/space just like any other team. You can group source and manage your own agenda and use the PTGBot just like any other team. If there are topics you want particular people to participate in, you can invite representatives from those projects to join in those topics as well. 

The key to success here is to be as open and flexible as possible. Sometimes you might need to hop into a different room to attend a particular discussion and sometimes you might need to poke at people to come to the critical mass you already have assembled for a topic. What’s important to remember is that we are all just subteams hoping to make open source and OpenStack a better projects. 

I’ve reached out to a few of the project teams who are participating at the Columbus PTG to highlight the impact operators can have on already scheduled meetings. I encourage you to follow along as we hear what these teams have planned and what you can get out of attending the Columbus PTG. 

Registration is now open—register before prices increase on August 15 and stay in the discounted community hotel block!

Have questions? Ping me on the OFTC network on IRC at diablo_rojo.

OVHcloud, Ant Group Win Superuser Awards for Large-Scale Deployment of OpenStack, Innovative Use of Kata Containers to Reduce Carbon Emissions, Respectively

OpenInfra Foundation lauds infrastructure teams at OVHcloud and Ant Group for community contributions and for using open infrastructure technology to provide strategic value to their organizations 

OVHcloud and Ant Group have tied for top honors as co-winners of the 2022 Superuser Awards, which recognizes organizations that have used open infrastructure to improve their business while contributing back to the OpenInfra community. The news was announced today by the Open Infrastructure Foundation (OpenInfra Foundation).

OVHcloud, a global cloud provider, manages 30 data centers across 12 sites on four continents, manufacturing its own servers, building its own data centers and deploying its own fiber-optic global network to achieve maximum efficiency. OVHcloud is currently running over 400,000 instances with 900,000 cores of OpenStack and processes over 6 million API requests every hour. The OVHcloud team deploys most of the OpenStack core components, such as Nova, Cinder, Glance, Neutron, Swift, Keystone and Horizon, as well as other components like Octavia, Barbican, Mistral, Heat, Tempest, Rally and Manila. 

The OVHcloud team has been actively involved in the OpenInfra community since 2014, including participating in meetups, summits, OpenStack Days, Special Interest Groups (SIGs) and OpenInfra Live episodes. The team regularly contributes to code, including dozens of reviews, commits and bug fixes, and also open sourced OS Archiver to manage data retention in the SQL databases behind OpenStack. OVHcloud has been one of the cloud providers for the OpenStack CI/CD since 2015.

Gilles Closset, strategic technology alliances director at OVHcloud, described in his nomination of the OVHcloud team how open infrastructure aligns with one of the company’s core values: freedom. “With a strong foundation based on the open infrastructure ecosystem, OVHcloud aims to federate all players that believe in an open system where anyone stays in control of their data – to manage in an open, trustful, reversible and transparent way.”

Ant Group is an innovative technology company that aims to bring inclusive benefits and sustainable services to the world. Formally established in October 2014, it traces its origins back to Alipay, which launched in 2004.

In April 2022, Ant Group announced that it achieved carbon neutrality in 2021 by reducing 29,591.48 tons of CO2 emission with green computing technologies, including Kata Containers.

Comprising more than 30 members, the Kata Containers team at Ant Group is responsible for the container-related R&D of the company and working for sustainable IT infrastructure. Many of the team members have been active upstream Kata Containers project contributors and maintainers since the first day of the project. In addition, the team has organized events, drafted roadmaps, led feature developments, enriched documentation, fixed bugs and helped other users to adopt Kata Containers in production.

Download the Ant Group Kata Containers White Paper
The Kata Containers team at Ant Group has published a white paper titled, “Kata Containers Best Practices at Ant Group” available here.

Read More about the 2022 Superuser Awards Nominees
Launched at the Paris Summit in 2014, the Superuser Awards recognize open infrastructure users who are making a difference in the Openinfra community and demonstrating how open infrastructure software is providing strategic value in their organization. The community submits nominees to Superuser, and the Superuser Editorial Advisory Board determines the winners. 

In addition to OVHcloud and Ant Group, 2022 nominees included:
Arvan Cloud
CanaryBit
Daniel Byström
Fairbanks
Inspur
Jiangsu Suzhong Construction Group Co., IT Team 
OpenMetal
Volvo Cars Corporation
Zhejiang Expressway Co., Ltd., IT Team

April 2022 vPTG Recap

That’s a wrap! Our most recent virtual Project Team Gathering (PTG) ran from April 4th to 8th. What is hopefully our last virtual PTG for a while ended on a high note with lots of productive conversations. The PTG hosted a variety of Open Infrastructure Foundation teams and projects from OpenStack and StarlingX to the Diversity and Inclusion Working Group and the Edge Computing Group. 

Below are summaries written by community members about the meetings various teams had. 

Don’t see your summary in the list? Let us know! We are happy to get it added! 

Stay tuned for updates on our next Project Team Gathering! Hopefully we will SEE you and your team there!

2021 OpenInfra Annual Report: Large Scale SIG

The OpenInfra Foundation annual report for 2021 is now live, including sections on open infrastructure growth, all OpenInfra projects, Foundation updates, SIG and WG updates, and more.

The Large Scale SIG is an OpenStack special interest group gathering operators of large scale OpenStack deployments interested in sharing their experience and discussing best practices. The group has been meeting regularly this year, with about 6 people forming the core group and a dozen of other people more infrequently involved.

One output of the group is the Scaling Journey: a set of wiki pages that describe the various stages of scaling your OpenStack deployments from tens of nodes or tens of thousands of nodes. That path was traveled by a lot of operators before, but lack of documentation and practical experience sharing still makes it a daunting prospect. The goal of the SIG is to document frequently asked questions and answers, as well as point to relevant resources, to make that journey as predictable and pleasant as possible.

Another focus of the Large Scale SIG this year was the “Large Scale OpenStack” show, a recurring event on the OpenInfra Live webcast. We invited operators of large scale deployments and got them to present how they solve a given operations challenge, and discuss live between themselves their different approaches. We tackled topics like upgrades in large scale environments, spare capacity handling, software-defined supercomputers, scaling Neutron, as well as operators tricks and tools. This show was amongst the most popular episodes on OpenInfra Live, and our goal is to continue in 2022.

Read the full 2021 OpenInfra Annual Report here!

Tags:

2021 OpenInfra Annual Report: OpenStack

OpenStack continues to be one of the most active open source communities with more than 25 million cores in production. This year, the OpenStack community continued to produce more software that is run in production. Notable highlights include:

  • Wallaby: Wallaby, the 23rd release of OpenStack, was developed by over 800 contributors from 140 organizations in 45 countries. Comprised of more than 17,000 code changes, Wallaby focused on integration with other open source projects like CEPH, Kubernetes, and Prometheus. OpenStack continues to be the third most active open source project (along with the Linux kernel and Chromium).
  • Xena: The Xena release brought with it better integration amongst OpenStack projects, support for advanced hardware features, and reduction of technical debt. Nova’s support for SmartNICs and ECMP routes in Neutron are a few of the hardware features now supported. Together, over 680 contributors worked in a short 25 weeks to present the 24th release of OpenStack.
  • Technical Writing SIG Dissolution: After successfully migrating the docs to project repositories several releases ago, and mostly maintaining an advisory role now, the Technical Writing SIG decided to dissolve and migrate the last of their repositories to other teams. At the PTG, the Technical Writing SIG Chair met with the Technical Committee and the First Contact SIG worked out a plan to retire the Technical Writing SIG.
  • Skyline: OpenStack welcomed its newest project since the addition of Adjutant in 2018! Skyline is an OpenStack dashboard built with React as an alternative to the Horizon dashboard. While not ready for production use just yet, the dashboard is engineered so that functions directly call OpenStack APIs to make maintaining the dashboard easier for developers and interactions faster and more efficient for users. This effort has been supported by the Horizon team as a future replacement once Skyline’s functionality gets closer to parity with Horizon. The Technical Committee accepted with with the caveat that Skyline with be labeled as a ‘tech preview’ until it undergoes the changes to bring it more in line with how other OpenStack services are organized and released.
  • TC Stance on OpenStackClient: The Technical Committee formalized their stance on the OpenStackClient in a resolution this year. Instead of making the development of OpenStackClient a community wide goal, but still wanting to show support and stand with the OpenStackClient team, they settled on a resolution with the intention of circling back to evaluate if the OpenStack community is ready for the OpenStackClient community goal.
  • IRC Network Migration: There was a change in ownership, organization structure, and policy in Freenode, the IRC network that the community has made use of for years. In response, the community discussed alternatives and settled on migrating over to a different network, but keeping IRC as the synchronous chat platform our community uses. As of late May, the OpenStack community has moved to the OFTC Network. Most teams were a part of this transition.

Get involved:

MORE OPENSTACK IN PRODUCTION THAN EVER

In November 2020, the OpenStack community celebrated 15 million cores in production. Just 12 months later, over 25 million cores were recorded in the annual OpenStack User Survey, marking 66% growth compared to 2020. This growth was seen among organizations of all sizes, including seven organizations who were recording over 1 million cores in production.

Walmart, LINE, Workday, China Mobile, and Verizon Media were among the founding members of the OpenStack Million Core Club. They were recognized during the OpenInfra Live: Keynotes, celebrating their incredible scale and innovation with OpenStack.

OPENSTACK CERTIFIED ADMINISTRATOR (COA) EXAM

The Certified OpenStack Administrator exam is the only professional certification offered by the OpenInfra Foundation.

In 2021,

  • COA exam vouchers were purchased: 109
  • 193 students passed

Among the exam takers, students were from 29 countries, including

  • United States
  • United Kingdom
  • Canada
  • Bolivia
  • China
  • Columbia
  • Cyprus
  • Egypt
  • France
  • Germany
  • Ghana
  • Guatemala
  • Hungary
  • India
  • Indonesia
  • Mexico
  • Netherlands
  • Peru
  • Poland
  • Russia
  • Saudi Arabia
  • Singapore
  • Spain
  • Switzerland
  • Thailand
  • Turkey
  • Uganda
  • Ukraine
  • Vietnam

OPENSTACK UPSTREAM INSTITUTE

The training was held twice throughout the year. The first training took place as part of the Open Source Day stand alone event held by the Anita B Foundation who also hosts the Grace Hopper Celebration. The ratio of mentors to students was very high (2:1) which yielded not only a productive day full of good discussions, but a highly specialized experience for the attendees that participated in the event. Upstream Institute was held in a one-day format where the mentors focused on sharing information about the OpenStack community including the tools and processes that contributors use on a daily basis.

The afternoon section of the training concentrated on hands-on experience where students worked on reproducing and fixing bugs in the OpenStack code base. Attendees who were able to stay for the afternoon learned how to push a code change upstream for review and several of them were able to go above and beyond. They were able to reproduce their bugs and also submit a fix to it. The training was very sucessful and we got great feedback and engagement from students.

The second training held in 2021 was also an online training that was held as part of the Open Source Day within the Grace Hopper Celebration in October. Similar to the first rendition, the training was held in one-day format with lectures in the morning and hands-on exercises in the afternoon. Again, the students worked on fixing real bugs and the more than 14 mentors made sure that attendees learned the mechanics of uploading a change for review, which is essential to be able to contribute code or documentation after the course. Four attendees pushed patches for bugs that were real fixes to OpenStack and as a result, they entered into a drawing that Grace Hopper was hosting to incentivize working on open source.

While the possibilities to hold the training were again, very limited in 2021, a group of mentors keep maintaining the course material to ensure it is up to date for every training occasion to provide the best experience to the students who joined. The content, being fully open source and available online, provides the possibility for individuals and organizations to go through it as a self-paced course or run it locally.

You can read the full 2021 OpenInfra Annual Report here!

Tags:

Cloud Sovereignty: a Fashionable Trend or Vital Need?

The number of newly founded NGOs announcing Sovereign Cloud development as their primary goal has vastly increased last year. The modern trend of sovereignty becomes the must-have of the season. What should you choose for your cloud data – to be trendy and protected or stay in the dark for your data safety? In fact, you have no choice and no right to risk. 

Valuable Data

What exactly is data sovereignty in the cloud environment? How can we meet these present-day requirements? Data sovereignty refers to the jurisdictional control or legal authority that can assert data because it is subjected to the country’s laws. 

The main cloud sovereignty goals are protecting sensitive, private data and ensuring it remains under its owner’s control. Most countries have jurisdiction on the matter, and it is evolving continuously and rapidly. There are mainly two basic requirements to cloud sovereignty varying from country to country. The cloud or/and a party controlling the cloud may have to be located within the country.

In certain situations, the requirements for cloud sovereignty are stringent. In China, for example, in many instances, it is obligatory for the cloud provider to be a Chinese company. 

Data residency, in its turn, is a privacy and business prerogative and refers to the physical data storage location. This term is essential for commercial and taxation purposes. In the majority of cases, data residency mirrors data sovereignty rules and laws within a country.

Control and Access

The one who owns information owns the world. We still might not fully realize how crucial the importance of data is. Defining the “new oil”, information from data gives enormous power to those who own it and opens vast opportunities for all the industries – from statistics to strategic business planning and decision making. Data influences a country’s politics, economics, defense and foreign affairs. Today the availability or lack of the data can prevent national conflicts or provoke a war. Nobody doubts that the data becomes a new weapon. That’s why it is so important to keep data controlled and sovereign to ensure it does not harm. Without laws that regulate adequate data sovereignty compliance, even your personal information – which is no less valuable than your money, could be easily abused. 

But what kind of data falls under sovereignty jurisdiction and should be kept in the country? Independently of the industry, the first type of gathered data to be protected is personal data. It includes everything from a person’s basic identity information – name, address, ID numbers. This kind of data is followed by web data such as location, IP address, cookie data and RFID tags, health and genetic data, biometric data, racial or ethnic data, political opinions and sexual orientation.

In our everyday life, we leave behind a great lot of information that grows into the Big Data phenomenon you indeed heard of. What might seem insignificant at first sight turns out to be a powerful tool at a closer look. So, the next time you’re using a public cloud, ask yourself: “Are you certain that your customers that are ordering food on your platform are happy about their private data (what they had for dinner last night) to end up in the hands of a foreign government?” This bright example shows the importance of simple everyday information if we multiply it by the number of people in the country or the region. If you keep going through a person’s daily life, you very quickly realize that just about anything and everything can be considered critical enough to stay in the country. 

Data Travel Restrictions

As many IT trends originate from the USA, data sovereignty is no exception. Many credits its high rising popularity to Snowden’s leak that exposed the US NSA PRISM spying program. The US government collected the data not only from US citizens but also from foreign nationals. Particularly, the US government has the authority to access the data stored within its territory regardless of data’s origins. Remember also Facebook’s Cambridge Analytica scandal, where users’ data was collected without their explicit consent. These situations emphasized the importance of data sovereignty. Governments worldwide have been focusing on this matter to protect the countries and their citizens against information leaks and possible consequences.

US

The US has no general consumer data privacy law at the federal level. It does, however, have many industry-specific federal protection laws – for example, the 1994 Driver’s Privacy Protection Act and the Video Privacy Protection Act. Laws also vary from state to state. California Consumer Privacy Act (CCPA) is one of the most prominent data privacy laws in the United States.

EU

The European Union GDPR (General Data Protection Regulation) is a great example of data sovereignty law. Enacted in 2016, it governs the data protection and privacy of EU citizens and regulates the transfer of data outside the borders of the EU and the European Economic Area. However, countries like Germany and France have strict laws of their own to protect their citizens’ data. 

Germany

Germany has implemented the new German Privacy Act (BDSG-new) that restricts data transfers to third countries. Companies that process the people’s personal information have to fulfill the German government’s data protection requirements, even if they are located outside the country’s borders.

Indonesia, Brunei, China, Vietnam, Russia

Laws related to data protection in these countries are probably amongst the strictest. They have stringent requirements that the data has to be stored on servers within the country. 

Argentina, Brazil, Colombia, Peru and Uruguay

Data localization laws in Argentina, Brazil, Colombia, Peru and Uruguay are pretty mild. Some restrictions apply to international data transfers. However, these restrictions act only in certain conditions. 

Instant Solution: Protected, Controlled and Sovereign Cloud

Within the last year or so various projects appeared to declare and serve the principles of Cloud Sovereignty, develop cloud data rules and restrictions on the country or region level. Some of them are supported by governments; others are initiatives of IT communities or business ideas that hope to become highly profitable in future. They promise data protection and cloud sovereignty. However, none of them can offer independent, controlled and secure cloud data management today, right now. 

The immediate solution for any cloud sovereignty issues that can be met by the business already exists. The right answer is on the surface. Private clouds can easily satisfy all possible requirements to data protection, geographical localization, control, access and security. By its very nature, a private cloud would be located within the country. It means complete cloud sovereignty for enterprises. The private cloud workload and data are under the country’s jurisdiction. Such a private cloud run on hardware physically placed within the state complies with all the laws and regulations; the data never cross the borders to leave the country.

If you wonder how to achieve data sovereignty in a cloud environment right away, Sardina Systems is here to help you. Our brainchild FishOS is an efficient cloud management software for enterprises that can run and serve the data inside your country. Thanks to our numerous partners, the necessary hardware and data center facilities can be provided and hosted in a short time. The diverse customer experience worldwide gave us the essential practical knowledge in delivering a cloud that fully meets the country’s data sovereignty requirements. 

What is your choice? To risk the business and wait when all the data protection rules are settled? Or run the business today, with the high level of data security and sovereignty in your private cloud environment?

The source: www.sardinasystems.com

OpenStack’s 24th Release, Xena, Wields Powerful Hardware Support, Project Integration to Strengthen Open Infrastructure for Cloud-Native Applications

The latest release occurs as the 2021 User Survey reveals significant growth in OpenStack deployments ranging from hundreds of cores to six million cores; Over 100 new OpenStack clouds have been built, growing the total number of cores under OpenStack management to more than 25,000,000 cores

The OpenStack community today released Xena, the 24th version of the most widely deployed open source cloud infrastructure software. Highlights of the Xena release include support for new hardware features, improved integration among components, and reduction of technical debt to maintain OpenStack’s stable and reliable core.

OpenStack is one of the most active open source projects in the world, supported by a vibrant and engaged community of developers globally. Over the span of just 25 weeks, almost 15,000 changes authored by over 680 contributors from over 125 different organizations were included in the Xena release.

This release comes at a time when the OpenStack project is deployed in production more widely than ever. Over 100 new OpenStack clouds have been built in the past 18 months, growing the total number of cores under OpenStack management to more than 25,000,000 cores. Organizations with deployments ranging from hundreds of cores to six million cores have logged significant growth according to the 2021 OpenStack User Survey. The User Survey report will be made available ahead of the OpenInfra Live: Keynotes, November 17-18, where several of these production users will be sharing the details of their growing OpenStack use cases.

Learn more about the 24th release of OpenStack during tomorrow’s OpenInfra Live episode, OpenStack Xena: Open Source Integration and Hardware Diversity.

Superuser Awards Winners: How Their OpenStack Deployments Continue to Grow, Evolve

Since the Paris Summit in 2014, the OpenInfra Foundation has hosted our annual Superuser Awards to recognize organizations that have used open infrastructure to meaningfully improve their business while contributing back to the community. These organizations have previously won the Superuser Awards and shared how their deployments have grown and evolved on a recent episode of OpenInfra Live.

CERN

CERN was actually the first winner of the Superuser Awards in 2014, an event that Belmiro Moreira, cloud architect at CERN, has good memories of.  Fast forward to today, Moreira shared a dashboard screenshot that was taken yesterday of CERN’s live monitoring of their infrastructure.


Today, they have 15 OpenStack projects distributed between different releases to accommodate the different use cases among their end users. While this configuration can be challenging, Moreira says it allows for flexibility for their overall infrastructure. In addition to OpenStack, the CERN infrastructure is supported by several open source projects including CentOS, Kubernetes, Ceph, Prometheus and a dozen more.

China Mobile 

Xiaoguang Zhang, cloud architect at China Mobile, and Zhiqiang Yu, chief open source liaison officer, provided an update and massive growth that the China Mobile infrastructure has had since their team won the Superuser Awards in 2016. Today, China Mobile has a network cloud, private cloud and public cloud based on OpenStack spanning eight regions. 

“In China Mobile’s OpenStack based infrastructure, we support 4G, 5G, edge computing and other IT services for internal use and also external vendors with our public cloud,” Zhang said. We have scaled to around 300,000 physical servers and 6 million compute cores in total.” 

Zhang provided an overview of the Virtualized Networks Function (VNF) business, OpenStack based infrastructure and hardware layer. 

“For each OpenStack instance, it has to manage 500 to 1,500 servers,” he said. “The VNFs (4G and 5G) are running on top of the virtualization.” 

With this scale, Yu emphasized that China Mobile, a Gold Member of the OpenInfra Foundation, is really a Superuser now. 

“We are really looking forward to the next 10 years of OpenStack and the next 10 years of Open Infrastructure,” Yu said. 

Ontario Institute of Cancer Research

Jared Baker, cloud architect at the Ontario Institute of Cancer Research (OICR) shared how OpenStack has continued to support the research initiatives since their Superuser Awards win in 2018. 

Baker detailed some of the current projects that are going on at OICR: 

  • Overture.bio, a collection of open-source, extendable solutions for big-data genomic science 
  • VirusSeq where they are sequencing 150,000 viral samples from Canadians who are testing positive for Covid 19
  • International Cancer Genome Consortium (ICGC) is uniformly analyzing specimens from 25,000 cancer patients
  • Expanding on ICGC, ARGO will analyze specimens from 100,000 cancer patients 

VEXXHOST

Even though VEXXHOST just won the Superuser Awards at the OpenInfra Summit Denver in 2019, Mohammed Naser, CEO of VEXXHOST, said their infrastructure has seen a lot of changes. This includes announcing an OpenStack upgrade solution, launching a new public cloud region in Amsterdam and running Wallaby, the most recent OpenStack release, for their private and public clouds.

Naser also emphasized that they are open source across the entire stack, showing a breakdown of their open source adoption from container runtimes and orchestration to monitoring and CI/CD. 

If you would like to participate in a future episode of OpenInfra Live, share your ideas!