At the UN's COP27 climate summit in November, "observer status" was granted to representatives from the Linux Foundation's nonprofit Green Software Foundation, and from its Hyperledger Foundation, a not-for-profit umbrella project for open source blockchains and related tools.

So what happened? From the Linux Foundation's blog: At COP27, one thing that was clear to many is that the complexity of the climate crisis and the pace of change needed will require open source approaches to problem-solving and information sharing — only then will we achieve the required global collaboration to collectively reduce carbon emissions and adapt our communities to survive extreme climate events. We believe that the Linux and Hyperledger Foundations have a role to play in this quickly evolving ecosystem....

The Linux Foundation is committed to exploring how open source data models, standards, and technologies can enable a decarbonized economy. The lessons we learned at COP27 clarified that there is a crucial opportunity for us to contribute to this effort by developing open source solutions that provide accurate, curated, up-to-date, accessible, and interoperable emissions data, as well as open source tools that enable asset owners, asset managers, banks, and real economy companies to accelerate Net Zero-aligned resilient investment and finance in the companies and projects that are climate-sustainable; enable real economy companies to accelerate their transition through Paris-aligned R&D, product development, and CapEx; provide regulators the information needed to manage systemic risk across the economy; empower policymakers and civil society to press for change more effectively.

We are excited to be part of this important movement! By taking a leadership role in this space with our projects, standards, and protocols, we hope to support global climate action in meaningful ways.
The blog post also shared an update from the representative from the Green Software Foundation, a non-profit creating "a trusted ecosystem of people, standards, tooling and best practices for green software." [T]the tech sector has a significant carbon footprint comparable to the shipping industry. For digital technologies to be true enablers for emissions reductions, there's a clear need to ensure that when we replace a process with a digitized one, it gets us closer to our climate targets.


To support this end, at COP27, Green Software announced several initiatives to support this goal, from a free, certified Green Software for Practitioners course, as well as the Software Carbon Intensity specification, a standardized protocol to measure the carbon emissions of software to achieve wide industry and academic adoption, a pattern library for engineers to adopt in their own software designs, along with a month-long global hackathon, Carbonhack, demonstrating these techniques and the impact they can have in reducing emissions from information technologies.

An anonymous reader shares this report from OMG! Ubuntu: Developers have just uncorked a brand new release of Wine, the open source compatibility layer that allows Windows apps to run on Linux.

A substantial update, Wine 8.0 is fermented from a year's worth of active development (roughly 8,600 changes in total). From that, a wealth of improvements are provided across every part of the Wine experience, from app compatibility, through to performance, and a nicer looking UI....

Notable highlights in Wine 8.0 include the completion of PE conversion, meaning all modules can be built in PE format. Wine devs say this work is an important milestone towards supporting "copy protection, 32-bit applications on 64-bit hosts, Windows debuggers, x86 applications on ARM", and more.

Phoronix reports: With the next Linux kernel cycle we could see upstream disable their driver support for Microsoft's Remote Network Driver Interface Specification (RNDIS) protocol due to security concerns.

RNDIS is the proprietary protocol used atop USB for virtual Ethernet functionality. The support for RNDIS outside of Microsoft Windows has been mixed. RNDIS isn't widely used today in cross-platform environments and due to security concerns the upstream Linux kernel is looking to move the RNDIS kernel drivers behind the "BROKEN" Kconfig option so they effectively become disabled in future kernel builds.

Ultimately once marked as "BROKEN" for a while, the drivers will likely be eventually removed from the upstream source tree.
Greg Kroah-Hartman wrote in a commit: "The Microsoft RNDIS protocol is, as designed, insecure and vulnerable on any system that uses it with untrusted hosts or devices. Because the protocol is impossible to make secure, just disable all rndis drivers to prevent anyone from using them again."

"If you've been itching to try an Arch Linux distribution and want something outside of the usual GNOME/KDE/Xfce desktop environments, Mabox Linux is an outstanding option...." writes ZDNet's Jack Wallen.

"It reminded me of my early days using Linux, only with a bit of a modern, user-centric twist...." Linux was hard in its infancy. So, when I see a Linux distribution that reminds me of those days but manages to make it easy on users without years of experience under their belts, it reminds me how far the open-source operating system has come. Such is the case with Mabox Linux.... It's not that Mabox doesn't make Arch Linux easy...it does. But when you first log into the desktop, you are greeted with something most hard-core Linux users love to see but can be a real put-off to new users. I'm talking about information...and lots of it.Â

You see, Mabox Linux places four information-centric widgets front and center on the desktop, so you can get an at-a-glance look at how the OS is using your system resources and even two widgets that give you keyboard shortcuts for things like opening various apps, menus, and even window management controls. Also on the OpenBox Window Manager desktop, you'll find a single top panel that gives you quick access to all your installed apps, the Mabox Colorizer... and a system tray with plenty of controls....

Once you have the distribution installed, the big surprise comes by way of performance. Mabox Linux is amazingly fast...like faster than most distributions I've used. A big part of that is due to the OpenBox Window Manager, which is very lightweight. Compared to my regular GNOME-based Linux desktop, Mabox is like driving a Lamborgini instead of a Prius. The difference is that obvious.ÂÂ
The installation process lets you choose between open-source or proprietary video drivers, the article points out. And "you can easily customize the color of your Mabox desktop, including the theme, side panels, Conky (which creates the desktop widgets), wallpaper, Tint2 Panel, and even the terminal theme."

"A new Linux malware downloader created using SHC (Shell Script Compiler) has been spotted in the wild," reports the site Bleeping Computer, "infecting systems with Monero cryptocurrency miners and DDoS IRC bots...

"The analysts say the attacks likely rely on brute-forcing weak administrator account credentials over SSH on Linux servers.... " According to ASEC researchers, who discovered the attack, the SHC loader was uploaded to VirusTotal by Korean users, with attacks generally focused on Linux systems in the same country.... When the SHC malware downloader is executed, it will fetch multiple other malware payloads and install them on the device. One of the payloads is an XMRig miner that is downloaded as a TAR archive from a remote URL and extracted to "/usr/local/games/" and executed....

The second payload retrieved, dropped, and loaded by the SHC malware downloader is a Perl-based DDoS IRC bot. The malware connects to the designated IRC server using configuration data and goes through a username-based verification process. If successful, the malware awaits commands from the IRC server, including DDoS-related actions such as TCP Flood, UDP Flood, and HTTP Flood, port scanning, Nmap scanning, sendmail commands, process killing, log cleaning, and more.

ASEC warns that attacks like these are typically caused by using weak passwords on exposed Linux servers.

OS News cheers the first official release of Vanilla OS, calling it "an immutable desktop Linux distribution that brings some interesting new technologies to the table, such as the Apx package manager."

From the official release announcement: "By default, Apx provides a container based on your Linux distribution (Ubuntu 22.10 for Vanilla OS 22.10) and wraps all commands from the distribution's package manager (apt for Ubuntu). Nevertheless, you can install packages from other package distributions.... Using the --dnf flag with apx will create a new container based on Fedora Linux. Here, apx will manage packages from Fedora's DNF repository, tightly integrating them with the host system.
ZDNet calls Vanilla OS "a new take on Linux that is equal parts heightened security and user-friendly." Among other things, "the developers opted to switch to ABRoot, which allows for fully atomic transactions between 2 root partitions." The official release announcement explains: ABRoot will check which partition is the present root partition (i.e A), then it will mount an overlay on top of it and perform the transaction. If the transaction succeeds, the overlay will be merged with the future root partition (i.e B). On your next boot, the system will automatically switch to the new root partition (B). In case of failure, the overlay will be discarded and the system will boot normally, without any changes to either partition.
But ZDNet explains why this comes in handy: Another really fascinating feature is called Smart Updates, which is enabled in the Vanilla OS Control Center, and ensures the system will not update if it's either under a heavy load or the battery is low. To enable this, open the Vanilla OS Control Center, click on the Updates tab, and then click the ON/OFF slider for SmartUpdate. Once enabled, updates will go through ABRoot transitions and aren't applied until the next reboot. Not only does this allow the updates to happen fully in the background, but it also makes them atomic, so they only proceed when it's guaranteed they will succeed.

The only caveat to this system is that you are limited to either weekly or monthly updates, as there is no daily option for scheduling. However, if you're doing weekly updates, you should be good to go.... Setting aside that which makes Vanilla OS special, the distribution is as stock a GNOME experience as you'll find and does a great job serving as your desktop operating system. It's easy to use, reliable, and performs really well...especially considering this is the first official release.
"Every wallpaper has a light and a dark version," adds the release announcement, "so you can choose the one that best suits your needs."

Long-time Slashdot reader destinyland shares an article listing "the five best Linux distros of 2022" — as chosen by the editor of the blog omg! ubuntu!

"Spoiler: they're not all Ubuntu-based!" the article begins, also noting that it's not a ranking of superiority of importance, but rather "giving a shoutout to some of the year's best Linux releases."

Its top-listed non-Ubuntu distro? Fedora Workstation 37
Fedora Workstation is a flagship desktop Linux distro for good reason: it's robust, it's reliable, it's impeccably produced — it distills what a lot of folks seek most: a "pure" GNOME experience, delivered as devs intend, atop a strong and stable base.

Autumn's offer of Fedora 37 Workstation features GNOME 43 — an update that majorly improves the GNOME Shell user experience with Quick Settings. There's also a more-featured Files rebuilt in GTK4/libadwaita; a revamped Calendar app; a Device Security panel; Raspberry Pi 4 support; GRUB instead of syslinux on BIOS; and more.

Folk often overlook Fedora Workstation because, as Linux distros go, it's rather understated, unassuming, and drama-free. Yet, it is a finessed and functional distro that forgoes fancy flourishes to focus entirely on its performance, its integration, and its cohesion.

If you've never tried Fedora you're missing out, so sort it!
There were two other non-Ubuntu distros on the list:

• Manjaro 22.0 'Sikaris'. "As Arch-based Linux distros go Manjaro is one of the best.... Everything from the shell to the package manager to bespoke touches and apps are cohesive, considered, and choreographed. Manjaro 22.0 isn't just a distro, it's an experience."

• Linux Mint 21. "As well as being easy to use, Linux Mint ships with an interesting selection of pre-installed software that aims to cover most users' needs, including some homegrown apps that are rather special."

Phoronix checks systemd's Git activity in 2022 (and compares it to previous years): If measuring a open-source project's progress by the commity activity per year, while not the most practical indicator, systemd had a very good year. In 2022 there were 6,271 commits which is under 2021's all-time-high of 6,787 commits. But this year's activity count effectively ties 2018 for second place with the most commits in a given calendar year.

This year saw 201k lines of new code added to systemd and 110k lines removed, or just under one hundred thousand lines added in total to systemd in 2022....

Systemd continues to grow and is closing out 2022 at around 1,715,111 lines within its Git repository.
Also interesting: "[W]hen it comes to the most commits overall to systemd over its history, Lennart Poettering easily wins the race and there is no competition. As a reminder, this year Lennart joined Microsoft as one of the surprises for 2022."

The Zero Day Initiative, a zero-day security research firm, announced a new Linux kernel security bug that allows authenticated remote users to disclose sensitive information and run code on vulnerable Linux kernel versions. ZDNet reports: Originally, the Zero Day Initiative ZDI rated it a perfect 10 on the 0 to 10 common Vulnerability Scoring System scale. Now, the hole's "only" a 9.6....

The problem lies in the Linux 5.15 in-kernel Server Message Block (SMB) server, ksmbd. The specific flaw exists within the processing of SMB2_TREE_DISCONNECT commands. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the kernel context. This new program, which was introduced to the kernel in 2021, was developed by Samsung. Its point was to deliver speedy SMB3 file-serving performance....

Any distro using the Linux kernel 5.15 or above is potentially vulnerable. This includes Ubuntu 22.04, and its descendants; Deepin Linux 20.3; and Slackware 15.

Justin Garrison works at Amazon Web Services on the Kubernetes team (and was senior systems engineer on several animated films).

This week he spotted a new milestone for Linux in the 2022 StackOverflow developer survey: [Among the developers surveyed] Linux as a primary operating system had been steadily climbing for the past 5 years. 2018 through 2021 saw steady growth with 23.2%, 25.6%, 26.6%, 25.3%, and finally in 2022 the usage was 40.23%. Linux usage was more than macOS in 2021, but only by a small margin. 2022 it is now 9% more than macOS.
Their final stats for "professional use" operating system:

• Windows: 48.82%
• Linux-based: 39.89%
• MacOs: 32.97%

But Garrison's blog post notes that that doesn't include the million-plus people all the Linux-based cloud development environments (like GitHub Workspaces) — not to mention the 15% of WSL users on Windows and all the users of Docker (which uses a Linux VM).

"It's safe to say more people use Linux as part of their development workflow than any other operating system."

While "this proposal will only be implemented if approved by the Fedora Engineering Steering Committee," Phoronix reports: Red Hat and Fedora engineers are plotting a path to supporting Unified Kernel Images (UKI) with Fedora Linux and for the Fedora 38 release in the spring they are aiming to get their initial enablement in place.

Unified Kernel Images have been championed by the systemd folks for better securing and trusting Linux distributions. Unified kernel images are a combination of the kernel image, initrd, and UEFI stub program all distributed as one.... The initial phase would focus on shipping a UKI as an optional sub-RPM that users can opt into initially, updating kernel install scripts so unified kernels are installed and properly updated, and bootloader support for unified kernel images. Adding systemd-boot support to the installers, better measurement and remote attestation support, and switching Fedora Cloud images to using unified kernels are among the additional goals but of lower priority.
Fedora's wiki includes a detailed description of the change proposal: The goal is to move away from initrd images being generated on the installed machine. They are generated while building the kernel package instead, then shipped as part of a unified kernel image. A unified kernel image is an all-in-one efi binary containing kernel, initrd, cmdline and signature....

Main motivation for this move is to make the distro more robust and more secure.

An anonymous reader shares a report: While AMD provided upstream open-source driver support for the Radeon RX 7900 series launch, the initial user experience can be less than desirable if running a new Radeon GPU but initially running an out-of-date kernel or lacking the necessary firmware support. With a new patch series posted AMD is looking to improve the experience by being able to more easily fallback to the firmware frame-buffer when their AMDGPU kernel graphics driver fails to properly load.

With the new IP-based discovery "block by block" approach to how the open-source AMD Radeon Linux graphics driver is managing the hardware initialization with RDNA3 and moving forward, the AMDGPU driver will try to probe all Radeon GPUs even if it might not end up being fully supported. In turn that ends up destroying the system firmware frame-buffer. But right now in the case of booting an RDNA3 GPU with a slightly out of date kernel (pre-6.0) or lacking the necessary RDNA3 firmware for hardware initialization, it can mean the screen freezing or system appearing unresponsive.

slack_justyb writes: A rather exotic feature in Xorg and Xwayland is being proposed to have the default value turned off going forward in Fedora 38 due to its use in attacks (CVE-2014-8095, CVE-2014-8099, CVE-2014-8103. . . to name a few). The feature allows servers running on one endianess to byte-swap to allow clients of a different endianess to connect to it. This was more common in the 1980s when X servers ran on big-endian and clients would connect who were little-endian.

The Xorg and Xwayland implementation of this feature has gone largely untested, the number of Fedora users that use it are virtually zero, and considering the number of attack vectors this has presented historically, setting the default to deny clients that require this seems the better way to do.

This change will be to the xorg-x11-server and xorg-x11-server-Xwayland packages and those needing the feature turned back will need to add "AllowSwappedClients" "on" to their xorg.conf.d file in the "ServerFlags" section. Xwayland users will need to pass the +byteswappedclients flag, however, the compositor will need to be able to handle this flag which at this time GNOME does not.

Long-time Slashdot reader slack_justyb brings news from the world of Linux desktop environments: After two years of development Xfce 4.18 is now live!

Several new features are available in each package. Thunar the default file manager for Xfce now includes a image preview sidebar, an editable toolbar that let's you reorder toolbar icons, file highlights, recursive search, and expanded undo/redo support.

Several new desktop settings allowing you to further configure the layout of the desktop are included. Additionally in this release for the desktop are, adaptive vsync support with GLX, and more enhancements for working with Wayland (though it may take a few more releases until everything works completely under Wayland).

You can find out more about the new release from the official tour here.
Also included is a new-filename Input Dialogue widget and a preliminary GUI-based shortcut editor...

The Linux Foundation "sponsors the work of Linux creator Linus Torvalds and lead maintainer Greg Kroah-Hartman," according to its page on Wikipedia. And now the Linux Foundation "is pleased to announce the launch of the Overture Maps Foundation," according to their December newsletter.

It's a collaborative effort "to enable current and next-generation map products by creating reliable, easy-to-use, and interoperable open map data as a shared asset that can strengthen mapping services worldwide." The initiative was founded by Amazon Web Services (AWS), Meta, Microsoft, and TomTom and is open to all communities with a common interest in building open map data. To get involved, please visit overturemaps.org.
And they're also announcing plans to form the Open Metaverse Foundation: In October, we brought top experts from diverse sectors together with leaders from many of the projects across the Linux Foundation to discuss what it will take to transform the emerging concept of the Metaverse from promise to reality.... As the next step in this amazing journey, we welcome the Open Metaverse Foundation (OMF) into the Linux Foundation as another piece of the puzzle. With your help, we can realize the promise of the open Metaverse. Learn more about what's next, join us, and get involved at openmv.org.
The Foundation has also published three new research papers:

• The 2022 State of Open Source in Financial Services

• WebAssembly (Wasm) for Legal Professionals

• Data and Storage Trends 2022.

The newsletter also points out that through Tuesday the foundation is offering 35% off any of their training courses, certifications, bundles or bootcamps.

An anonymous reader quotes a report from Ars Technica: Pine64, makers of ARM-based, tinker-friendly gadgets, is making the PineTab 2, a sequel to its Linux-powered tablet that mostly got swallowed up by the pandemic and its dire global manufacturing shortages. The PineTab 2, as described in Pine64's "December Update," is based around the RK3566, made by RockChip. Pine64 based its Quartz64 single-board system on the system-on-a-chip (SoC), and has all but gushed about it across several blog posts. It's "a dream-of-a-SoC," writes Community Director Lukasz Erecinski, a "modern mid-range quad-core Cortex-A55 processor that integrates a Mali-G52 MP2 GPU. And it should be ideal for space-constrained devices: it runs cool, has a variety of I/O options, solid price-to-performance ratio, and "is genuinely future-proof."

The PineTab 2 is a complete redesign, Erecinski claims. It has a metal chassis that "is very sturdy while also being easy to disassemble for upgrades, maintenance, and repair." The tablet comes apart with snap-in tabs, and Pine64 will offer replacement parts. The insides are modular, too, with the eMMC storage, camera, daughter-board, battery, and keyboard connector all removable "in under 5 minutes." The 10.1-inch IPS display, with "modern and reasonably thin bezels," should also be replaceable, albeit with more work. On that easily opened chassis are two USB-C ports, one for USB 3.0 I/O and one for charging (or USB 2.0 if you want). There's a dedicated micro-HDMI port, and a front-facing 2-megapixel camera and rear-facing 5-megapixel (not the kind of all-in-one media production machine Apple advertises, this tablet), a microSD slot, and a headphone jack. While a PCIe system is exposed inside the PineTab, most NVMe SSDs will not fit, according to Pine64. All of this is subject to change before final production, however.

As with the original PineTab, this model comes with a detachable, backlit keyboard cover, included by default. That makes supporting a desktop OS for the device far more viable, Erecinski writes. The firmware chipset is the same as in the PineBook Pro, which should help with that. No default OS has been decided as of yet, according to Pine64. The tablet should ship with two memory/storage variants, 4GB/64GB and 8GB/128GB. It's due to ship "sometime after the Chinese New Year" (January 22 to February 5), though there's no firm date. No price was announced, but "it will be affordable regardless of which version you'll settle on." A video version of the "December Update" can be found on YouTube.

"Linus has released the 6.1 kernel," reports LWN.net — and it's the one with initial support for kernel development in Rust.

Elsewhere LWN explains the specifics of this milestone: No system with a production 6.1 kernel will be running any Rust code, but this change does give kernel developers a chance to play with the language in the kernel context and get a sense for how Rust development feels....

There are other initiatives underway, including the writing of an Apple graphics driver in the Rust language. For the initial merge into the mainline kernel, though, Linus Torvalds made it clear that as little functionality as possible should be included. So those drivers and their support code were trimmed out and must wait for a future kernel release. What is there is the support needed to build a module that can be loaded into the kernel, along with a small sample module.... Torvalds asked for something that could do "hello world" and that is what we got. It is something that can be played with, but it cannot be used for any sort of real kernel programming at this point.

That situation will, hopefully, change in the near future.
Meanwhile, Linux 6.1 also includes "support for destructive BPF programs, some significant io_uring performance improvements, better user-space control over transparent huge-page creation, improved memory-tiering support."

The Register adds: Other interesting additions include more support for the made-in-China LoongArch CPU architecture, introductory work to support Wi-Fi 7 and security fixes for some flaky Wi-Fi routines in previous versions of the kernel. There's also plenty of effort to improve the performance of Linux on laptops, and enhanced power efficiency for AMD's PC-centric RYZEN silicon.

"Linux kernel 6.2 should contain fixes for some problems handling floppy disks," reports the Register, "a move which shows that someone somewhere is still using them." This isn't the only such fix in recent years. As a series of articles on Phoronix details, there has been a slow but steady flow of fixes for the kernel's handling of floppy drives since at least kernel 5.17, as The Register mentioned when it came out....

Back in July 2016, SUSE kernel developer Jiri Kosina submitted a patch. The problem arose because this change broke something else and later got reverted, and so the problem hung around. In July last year, he sent in a new patch that fixed it again for the 5.12 kernel, and was later back-ported to 5.10, an LTS version, and again into kernel 5.15 — another an LTS version, and the one you're running today if you're on the current Ubuntu LTS release, or something built from it such as Linux Mint 21....

Now, in December 2022, a new patch for the forthcoming kernel 6.2 fixes a memory leak that dates back to 5.11 or before.

An anonymous reader quotes a report from Ars Technica: For the brave people running Linux on Apple Silicon, their patience has paid off. GPU drivers that provide desktop hardware acceleration are now available in Asahi Linux, unleashing more of the M-series chips' power. It has taken roughly two years to reach this alpha-stage OpenGL driver, but the foundational groundwork should result in faster progress ahead, writes project leads Alyssa Rosenzweig and Asahi Lina. In the meantime, the drivers are "good enough to run a smooth desktop experience and some games."

The drivers offer non-conformance-tested OpenGL 2.1 and OpenGL ES 2.0 support for all M-series Apple devices. That's enough for desktop environments and older games running at 60 frames per second at 4K. But the next target is Vulkan support. OpenGL work is being done "with Vulkan in mind," Lina writes, but some OpenGL support was needed to get desktops working first. There's a lot more you can read about the interplay between OpenGL, Vulkan, and Zink in Asahi's blog post.

An anonymous reader quotes a report from ZDNet: One bit of accepted wisdom in some cloud circles is that OpenStack, the open-source Infrastructure as a Service (IaaS) cloud, is declining. Nothing could be further from the truth. It's alive, well, and growing like crazy. According to the 2022 OpenStack User Survey, OpenStack now has over 40 million production cores. Or, in other words, it's seen 60% growth since 2021 and a 166% jump since 2020. Not bad for a so-called also-run, eh? It's not just telecoms, where OpenStack has become the backbone of major cell companies such as China Mobile and Verizon. Nor is it just other major companies such as the Japanese instant messaging service LINE, the on-demand, cloud-based financial management service company Workday, Walmart Labs, and Yahoo. No, many other, much smaller companies have also staked their cloud future on OpenStack.

Why? There are many reasons. As Jonathan Bryce, executive director of the Open Infrastructure Foundation (OpenInfra Foundation), OpenStack's parent organization, said, "OpenStack supports the ever-changing world of infrastructure where now we have GPUs, FPGAs, smart NICs, and smart storage. At the same time, you can still get direct access to the underlying hardware." This, in turn, enables "OpenStack users to create such amazing things as telecom cloud workloads on the cloud that can do edge transcoding video. With this, people can watch 4K videos on their phones using 5G." Another reason for OpenStack's growing popularity is its Kubernetes integration. Thanks to Linux OpenStack Kubernetes Infrastructure (LOKI), Kubernetes is now deployed on over 85% of OpenStack deployments. In addition, Magnum, the OpenStack container orchestration service, is also gaining popularity. 21% of users are now running production workloads with it. [...] Kubernetes is also very useful with hybrid clouds. OpenStack is often used in hybrid clouds. Indeed, 80% of OpenStack users are deploying it in hybrid clouds. To make it easier to build out hybrid clouds, operators are turning to Octavia, an open-source, operator-scale load-balancing program. Today, not quite 50% of OpenStack deployments are using Octavia. OpenInfra Foundation's general manager Thierry Carrez said: "Hype is nice, but substance lasts, and as OpenStack deployments continue to grow in staggering numbers, the OpenStack community is proving that it's not only alive and well, but also delivering indisputable value to organizations."