GPL(GENERAL PUBLIC LICENSE) FREEDOM 0: The freedom to run the program as you wish, for any purpose.
FREEDOM 1: The freedom to study how the program works, and change it so it does your computing as you wish.
FREEDOM 2: The freedom to redistribute copies so you can help others.
FREEDOM 3: The freedom to distribute copies of your modified versions to others.
Network-attached storage (NAS) appliance maker QNAP on Tuesday released a new advisory warning of a cryptocurrency mining malware targeting its devices, urging customers to take preventive steps with immediate effect.
"A bitcoin miner has been reported to target QNAP NAS. Once a NAS is infected, CPU usage becomes unusually high where a process named '[oom_reaper]' could occupy around 50% of the
One of many exciting features/changes with upcoming Intel Xeon Scalable "Sapphire Rapids" processors is the introduction of Advanced Matrix Extensions (AMX). While initial AMX support is premiering with Linux 5.16 due out in stable form as the start of the new year, it currently doesn't allow for KVM virtualized guests to make use of the new capabilities...
Luke used a desktop app called Sejda to sign his PDF. I've never heard of it before, and I was really excited to learn that there was a proper desktop solution to sign PDFs on Linux (and possibly free, as I didn't see Luke logging into any account / entering any licence code).
So I just gave it a shot however the 'signature' generated by Sejda seemed to be nothing but a visual PDF annotation.
PDFs with proper digital signatures can be validated in Okular and Adobe Reader as shown in screenshots. But the signed PDF from Sejda cannot be validated by either Okular or Adobe Reader. In fact, I was even able to edit the annotation in e.g. LibreOffice.
Am I missing something here? Does Sejda for example only generate a cryptographic digital signature with premium licence? Or perhaps it's only able to do this on other platforms other than Linux?
Has your Fedora Linux server been End of Life for months because you can’t seem to schedule the hours of downtime required to upgrade it? There are ways to shorten that downtime to just the few minutes required for a reboot. You can do this utilizing LVM and VM technologies, all provided by Fedora.
Most users find it simple to upgrade from one Fedora Linux release to the next with the standard process. However, special cases can be handled using existing Fedora VM and LVM capabilities. This article shows one way to upgrade a Fedora Linux server using DNF while using Logical Volume Management (LVM) to keep a bootable backup in case of problems. How to run the upgrade concurrently in a virtual machine to minimize downtime will also be demonstrated. This example upgrades a Fedora Linux 33 virtual machine host to Fedora Linux 35.
The process shown here is admittedly more complex than the exceptionally easy standard upgrade process. Thus, you should have a strong grasp of how LVM and virtual machines work before attempting. Without proper skill and care, you could lose data and/or be forced to reinstall your system! If you don’t have essential Fedora Linux administration skills, it is highly recommended you stick to the supported upgrade methods only.
Prerequisite skills for this method include:
LVM management – understand essentials of Physical and Logical Volumes
Create and administer Virtual Machines using virsh, virt-manager, raw qemu-kvm, or cockpit
Configure direct kernel boot on a VM (not as hard as it sounds, but look it up ahead of time on your VM manager of choice)
Prepare the system
This example assumes you already have installed:
You must have enough memory available (2G recommended but I have succeeded with 1G) to create an additional virtual machine to run the upgrade. Your system can continue to operate while you prepare for and download the upgrade, and while the upgrade runs.
Before you start, ensure your existing system is fully updated.
$ sudo dnf upgrade --refresh
Since this is a server, rebooting may be more involved than a single user system. If the kernel was updated, or critical running packages were updated, you need to reboot after notifying users as needed.
Check that your root filesystem is mounted via LVM.
If you used the defaults when you installed Fedora Linux, you may find the root filesystem is mounted on a LV named root. The name of your volume group will likely be different. Look at the total size of the root volume. In the example, the root filesystem is named f33 and is 25G in size. In case you were wondering, the LV named root is a Btrfs filesystem with a subvolume named home which may at some point have a subvolume for the root filesystem as well.
This system has enough free space to allocate a 25G logical volume for the upgraded Fedora Linux 35 root. If you don’t, LVM management is beyond the scope of this article, but you can review a few suggestions in a previous article.
Note for Btrfs users
The root filesystem must be copied to a logical volume to boot in a virtual machine. For a Btrfs root, you could use Btrfs send to copy a Btrfs snapshot of a root subvolume to a new Btrfs formatted LV, but you must boot from the new system to copy back the upgraded system because of selinux updates. This cryptic summary probably needs another article.
Clone the root filesystem
First, allocate a new LV for the upgraded system. Make sure to use the correct name for your system’s volume group (VG). In this example it’s vg_julie. Also, make sure you allocate the same size or more (if you want to expand later… not addressed here).
It is important to realize that once a snapshot is created, data logged to the root file system will not carry over to the upgraded file system. In terms of Logging, for instance, logs that are written to the host system during the period of updating will be available on the backup LV after the upgraded LV is booted on bare metal, but not in the new LV’s logging directory. This method does not address merging them. This method works best, therefore, where critical systems write to their own LVs, rather than a sub-directory on the root filesystem. For instance, if this is a mail server, you may wish to ensure /var/spool/mail is mounted separately from the root filesystem. Personally, I symlink /var/spool/mail to /home/mailspool, keeping all mailboxes on one seperate LV filesystem, unchanged by updates to the root filesystem. Use mailq before the snapsnot to ensure no mail is queued or quarantined. You may wish to stop mail transfer service during the upgrade, or run mailq again to ensure nothing is queued before rebooting into upgraded system.
Similarly, if this Fedora Linux server runs a postgresql database server, /var/lib/pgsql should probably be on its own filesystem.
This process underscores why it is best-practice for admins to move service data to its own LV filesystem.
Take note of your current system, especially:
Current Kernel Version
What version you are currently running, and what version is your target
Current root disk and/or UUID/Label
How your swap is setup
For the latter two, you can find them in your /etc/fstab. Now might be a good time to make a quick backup of that file.
Create the upgrade VM
The snapshot can now be copied to the new LV. Make sure you have the destination correct when you substitute your own volume names. If you are not careful you could delete data irrevocably. Also, make sure you are copying from the snapshot of your root, not your live root. This example has an ext4 root filesystem. Change to use your actual root filesystem type. You could also change the root filesystem type at this step by using rsync, but that will be a future article.
$ sudo partclone.ext4 -b -s /dev/vg_julie/f33_s -o /dev/vg_julie/f35
Partclone v0.3.17 http://partclone.org
Starting to back up device(/dev/vg_julie/f33_s) to device(/dev/vg_juliebak/f35)
Elapsed: 00:00:01, Remaining: 00:00:00, Completed: 100.00%
Total Time: 00:00:01, 100.00% completed!
File system: EXTFS
Device size: 26.8 GB = 6553600 Blocks
Space in use: 16.9 GB = 4136996 Blocks
Free Space: 9.9 GB = 2416604 Blocks
Block size: 4096 Byte
Elapsed: 00:07:32, Remaining: 00:00:00, Completed: 100.00%, Rate: 2.25GB/min,
current block: 6514688, total block: 6553600, Complete: 100.00%
Total Time: 00:07:32, Ave. Rate: 2.2GB/min, 100.00% completed!
Partclone successfully cloned the device (/dev/vg_julie/f33_s) to the device (/dev/vg_juliebak/f35)
Give the new filesystem copy a unique UUID and label. This is not strictly necessary, but given that UUIDs are supposed to be unique, avoid future confusion by tagging the new filesystem. Here is how this is done for an ext4 root filesystem:
Note: For Btrfs, the filesystem must be mounted to change UUID and/or LABEL.
Now remove the snapshot volume which is no longer needed:
$ sudo lvremove vg_julie/f33_s
Do you really want to remove active logical volume vg_julie/f33_s? [y/n]: y
Logical volume "f33_s" successfully removed
You may wish to make a snapshot of /home at this point if you have it mounted separately (use Clone the root filesystem for steps). Sometimes, upgraded applications make changes that are incompatible with a much older Fedora Linux version. If you need to revert, edit the /etc/fstab file on the oldroot filesystem to mount the snapshot on /home. Remember that when the snapshot is full, it will disappear! You may also wish to make a normal backup of /home (and other filesystems for database and mail) for good measure.
Configuring the VM to use the new root
Mount the new LV and backup your existing GRUB settings:
Our previous article copied /boot/grub2/grub.cfg to a backup, but Fedora Linux now uses BLS – the Boot Loader System. Grub entries are in /boot/loader/entries and you generally don’t need to touch grub.cfg
Edit /mnt/f35/etc/default/grub and change the default root LV activated at boot:
Copy /mnt/f35/etc/fstab to /mnt/f35/etc/fstab.f33 as a backup. Edit /mnt/f35/etc/fstab to comment out any filesystems that will not be available to the virtual machine. Only the / block device will be available. Change the root filesystem to use the new UUID or LABEL. E.g.
LABEL=F35 / ext4 defaults 1 1
The upgrade process will expect a /boot directory. If /boot is not in your root filesystem, copy it into the new LV:
If you converted the root filesystem to a new type, you may also need to add a new filesystem driver or module. For example, after converting ext4 to Btrfs, you would need ‐‐add btrfs ‐‐add-drivers virtio_blk.
Using libvirtd is out of scope for this already long article, because as admin of a virtual host, you should know to create a virtual machine using virsh or virt-manager or your favorite front end. Create a virtual machine with a single disk volume mapped to the new root filesystem LV (/dev/vg_julie/f35 in the example). Use Direct Kernel Boot with the same initramfs name you created with dracut:
Now, start the virtual machine, and login to its console as root. Check that nothing else needs to be disabled. If all is well, reboot the VM with $ sudo dnf system-upgrade reboot on the VM console (not on your bare metal console – that would not be a total disaster, but you’ll be down while the upgrade runs). You should see the upgrade proceeding on the VM console after the VM reboots. Meanwhile, your host system continues on as usual.
If, for some reason, sudo dnf system-upgrade reboot does not work, and network is available in the VM, you can call sudo dnf system-upgrade in the VM, and it will work fairly quickly, as everything is already downloaded.
… time passes as your virtual host hums along and the VM upgrades … get some coffee and a donut while your current host continues to operate as usual.
When the upgrade is finished, the VM will reboot again. Log in as root on the VM console and check things out. (Note: if you are using a GUI, look for “Send Key” to get a root console.) You will still be running the old kernel (f33 in this example), because you are using Direct Kernel Boot for the VM. If anything went wrong, you can destroy the VM, and start over at taking a snapshot of the current root filesystem.
If it looks ok, run sudo systemctl poweroff to shutdown the VM.
Prepare the VM host to boot the upgraded root filesystem
The initramfs generated inside the VM does not include the drivers you need for bare metal. In addition to using virtio_blk instead of an actual disk controller driver, a VM host probably needs LVM and RAID drivers. In the interest of simplicity, we will generate an initramfs with all drivers and modules. This creates a large image, around 100 Mbyte, but there is no drawback other than disk space used on a typically limited /boot filesystem. Experts: it is possible to use lsinitrd and dracut options ‐‐add and ‐‐add-drivers instead to create a smaller image if you know what is needed.
Copy the new boot loader entry and kernel files to the real /boot.
Change the kernel version to the one just installed by the system-upgrade. You can run dracut without ‐‐force initially to ensure it is overwriting what you expect.
$ sudo mount /dev/vg_julie/f35 /mnt/f35 # make sure your VM is truly not running
$ sudo mount -t proc /proc /mnt/f35/proc
$ sudo chroot /mnt/f35
# ls -l /boot/*fc35*
-rw-r--r--. 1 root root 236665 Sep 30 08:10 /boot/config-5.14.9-300.fc35.x86_64
-rw-------. 1 root root 35571851 Oct 6 15:15 /boot/initramfs-5.14.9-300.fc35.x86_64.img
lrwxrwxrwx. 1 root root 46 Oct 6 15:15 /boot/symvers-5.14.9-300.fc35.x86_64.gz -> /lib/modules/5.14.9-300.fc35.x86_64/symvers.gz
-rw-------. 1 root root 5849998 Sep 30 08:10 /boot/System.map-5.14.9-300.fc35.x86_64
-rwxr-xr-x. 1 root root 11032912 Sep 30 08:10 /boot/vmlinuz-5.14.9-300.fc35.x86_64
# dracut -N --kver=5.14.9-300.fc35.x86_64 --force
$ sudo cp -p /mnt/f35/boot/*-5.14.9-300.fc35* /boot
$ sudo cp -p /mnt/f35/boot/loader/entries/*-5.14.9-300.fc35.x86_64.conf /boot/loader/entries
If you mount /boot separately (very likely), then you need to edit the loader entry copied from the VM to remove /boot from the kernel and initrd. Edit /boot/loader/entries/*-5.14.9-300.fc35.x86_64.conf and change:
... to ...
Re-enable services you disabled for the VM. If you didn’t write them down, check ~/.bash_history or the equivalent for your shell.
Edit fstab in your new VM (/mnt/f35/etc/fstab) to include all the filesystems you need, but commented out to run in a VM.
IF (and only if) /boot is separately mounted on your host (shows in df), rename and recreate /boot in the upgraded root – this will be a handy backup. (Otherwise, it will get mounted over and the files hidden.)
$ sudo systemctl reboot
... system reboots
$ df / /f33
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg_julie-f35 25671908 15948668 8490520 66% /
/dev/mapper/vg_julie-f33 15350728 14540288 64256 100% /f33
Check that required services are running. If there are any insurmountable problems, you can reboot back into Fedora Linux 33!
Finally, if you are running well, remove the VM you used to upgrade with, so you don’t corrupt your host system by accidentally starting it while you are using the LV on the host system. Make sure you don’t delete the LV in the process.
The FreeBSD team has announced the availability of the third update to the operating system's 12.x branch. FreeBSD 12.3 includes several bug fixes to the kernel, userland updates, and improvements to network drivers. The project's release announcement reports: "The FreeBSD Release Engineering team is pleased to announce the....
netstat (network statistics) is a command-line tool for monitoring network connections both incoming and outgoing as well as viewing routing tables, interface statistics, etc. [ You might also like: 22 Linux Networking Commands for
Do you like visual-novel styled narrative adventures? Where Birds Go to Sleep looks like one to keep an eye on that will be releasing with Linux support. A narrative adventure set in a fictional Near East-inspired land, with an art style that looks like a bunch of classical paintings brought to life by voice-acting and an original musical score to go along with it.
"Slip into the subconscious of Cormo, a churlish smuggler-turned-explorer, only ever influencing his actions, never directly assuming control. You will mould him through every sentence you put in his mind… but you might not like what he becomes.
Confront him about controversial topics like sexuality, prejudice and morality, and change his mind… or have him change yours."
Researchers at Spectral recently discovered a security flaw in Kafdrop, a popular open-source UI and management interface for Apache Kafka clusters that has been downloaded more than 20 million times.
The Kafdrop flaw has allowed the data from Kafka clusters – everything from financial transactions to mission-critical data – to be exposed internet-wide. It can give anyone their own UI to make it easy to review live Kafka clusters without authentication. Learn more about the security flaw and its impact here.
In 2021 the Linux Foundation (“LF”) emerged from the worst pandemic in a century and embraced new horizons. The collaborative activities in our project communities weathered the COVID-19 crisis exceptionally well, and many communities are now pushing forward with a renewed sense of purpose.
Our organization’s namesake project, the Linux kernel, has celebrated an amazing milestone: its 30th birthday. Over the years, more than 55,000 people have contributed code to improve Linux, and today, Linux can be found everywhere. Over 5.4 billion people rely on Linux as it powers the vast majority of smartphones, the world’s largest cloud environments, and the world’s fastest computers. It’s also assisting in scientific discovery on Mars. After three decades of development, the project continues to ship new code, features, and performance enhancements.
While our community continues to accelerate innovation in software development, the rising tide of cybersecurity threats has planted itself firmly on our shores. We all rely on software supply chains that are constantly under attack by an increasingly sophisticated adversary, causing us to reflect on our role and responsibility in securing the world’s critical technology infrastructure.
In 2021 we saw much progress in our quest to “harden” the software supply chain. The Software Package Data Exchange® (SPDX®) community received formal recognition as an international ISO/IEC standard (5962:2021), making it easier for organizations to require a Software Bill of Materials (SBOM) with suppliers and customers. This came on the heels of OpenChain receiving ISO/IEC approval as an international standard (5230:2020) for open source licensing compliance. We also saw new collaborations emerge this year, like sigstore, which is on its way to becoming a de facto standard for signing packages and digital artifacts used throughout a supply chain.
The Open Source Security Foundation (OpenSSF), launched in August 2020, brought together a community of experts focused on software supply chain security challenges. This community had an amazing start publishing guidance for best practices (e.g., badges and scorecards), creating new tools and frameworks (e.g., SLSA), establishing and collecting metrics, developing free, globally accessible training materials, and publishing research, such as the findings of its FOSS Contributor Survey in collaboration with Harvard’s Laboratory for Innovation Science.
Our members responded to the progress by doubling down and making significant additional investments in OpenSSF as a vehicle for solving the world’s supply chain security challenges. In October, we announced that the Linux Foundation and OpenSSF raised over $10 million to invest in leadership and initiatives, boldly aspiring to impact supply chain security dramatically. The LF could not have done this without significant support from our members, including OpenSSF’s premier members 1Password, AWS, Cisco, Citi, Dell Technologies, Ericsson, Meta, Fidelity, GitHub, Google, Huawei, Intel, IBM, JP Morgan Chase, Microsoft, Morgan Stanley, Oracle, Red Hat, Snyk, and VMWare.
The importance of open source in the world’s cybersecurity efforts highlights its importance to our modern society. As new organizations, new industries, and policymakers have approached the LF for guidance on open source, we recognize there is a need for modern insights into why and how open collaboration works. There is a need to understand the dynamics of communities, where and how value is derived, and the intersection of supply chains and open source collaboration. To that end, this year, we launched Linux Foundation Research to explore the role of open source software, standards, and communities as a framework for mass innovation, collaboration, and problem-solving.
Research into important topics such as cybersecurity and SBOM readiness is already underway, along with project-specific insights sought by our project communities. We think this investment will provide actionable data and insights supporting more informed decision-making across technology and industry ecosystems. Finally, while most research organizations hoard data privately, our research approach has an open flair — we’re making all non-personally identifiable data available under the Community Data License Agreement — Permissive, Version 2.0, a revised data-sharing framework our legal community worked to release this year.
Having a research capability also provides new opportunities to more deeply explore challenges and opportunities in community collaboration. For example, this year LF Research partnered with AWS, CHAOSS, Comcast, Fujitsu, GitHub, GitLab, Hitachi, Huawei, Intel, NEC, Panasonic, Renesas, Panasonic, Red Hat, and VMware to examine the state of diversity, equity, and inclusion (DEI) in open source communities. To nurture and grow open source, we need to understand better how DEI is practiced and encouraged in open source communities. We hope this research will also support other collaborative efforts supporting DEI goals, such as the Inclusive Naming Initiative, the Software Developer Diversity and Inclusion Project (SDDI), Fair Change, and Open Sentencing.
And with our industry partners, such as Microsoft and Accenture, we’ve launched several new projects and foundations that are meaningful to humanity. The Green Software Foundation seeks to add sustainability to software engineering efforts. The AgStack Foundation, launched in May 2021, is building an open source digital infrastructure for agriculture to accelerate that industry’s digital transformation and address climate change.
While open source drove innovation across the technology landscape, it also saw acceleration within industry verticals. The LF helped launch several new collaborations focused on driving 5G and telecommunications, including the 5G Super Blueprint, a partnership with Next Generation Mobile Network Alliance (NGMN), Magma Foundation, and the new Mobile Native Foundation. Our members also expanded open source innovation in the media and entertainment industry with the launch of Open 3D Engine (O3DE), a new open source AAA 3D engine for gaming, simulation, and storytelling. The O3DE ecosystem complements our existing Academy Software Foundation (ASWF). ASWF’s community added a new project for shading materials in graphics this year called MarterialX. Moviegoers may have experienced the effects of this project in Star Wars: The Force Awakens.
Our project communities’ ambitions often lead to a focus on building communities. We’ve seen many experts continue to collaborate on community engagement in the highly active TODO Group. However, there comes a time when our communities need tools to help scale and support their growth. In 2020, the LF embarked on a journey with key community leaders to build tools that enable those leaders and others to better understand and more effectively engage with a project community. The results of these investments are now starting to roll out as the LFX platform. I’d like to thank all those in our community who provided feedback, guidance, suggestions, and sometimes the raw critiques we needed to build something better.
We started with tools we knew would make maintainers more efficient on tasks they really did not want to spend time on, such as processing Contributor License Agreements (CLAs) electronically in EasyCLA. Many maintainers were also interested in understanding their community dynamics leading to the creation of LFX Insights, which aggregates, analyzes, and contextualizes data across all of a community’s repositories, communication channels, and contributors. Conversations about community health led to requests for tools to recruit and engage new project participants, particularly from diverse sources, and LFX Mentorship was born. Once engineers on our projects saw what LFX could do, they requested additional capabilities to configure and manage their projects. LFX Project Control Center now promises to enable engineers to provision and configure resources online in minutes with API-driven automation for common open source project tasks such as provisioning new cloud resources, managing DNS, and more.
The LF also heard the needs of our corporate members to have better visibility into how their organization is engaged in our communities. We’ve developed the LFX MyOrg tool to help corporate managers get a better view across their organization’s participation, find paths to collaborating in projects, exercise the benefits available to them as members, and more — all from a single system. All of these tools are now available to our communities and members through lfx.linuxfoundation.org.
Many of our members have been faced with a skills shortage. The LF’s 2021 Jobs Report, released in October with edX, shows trained and certified open source professionals, particularly with cloud and container expertise, are in high demand and are in short supply. Such data points highlight the need to train people and enable new opportunities to grow their careers in open source. Our training and certification efforts continued to gain steam this year. Over 68,00 individuals registered for new certifications in the past year, a 50% increase over 2020, while 2 million people enrolled in the LF’s free training courses.
And finally, I’ll wrap up by saying we sincerely missed seeing our communities in person. The last two years have been difficult — to harrowing — for many suffering from the lingering pandemic. However, this year we have seen hope on the horizon. We produced dozens of successful virtual conferences throughout 2021, but the feedback was clear: people wanted to meet in person again. Our events team did a thorough job researching and soliciting advice from experts and public health authorities. That preparation enabled us to welcome our communities back together, in-person, this fall at events like Open Source Summit in Seattle, Open Source Strategy Forum and OSPOCon Europe in London, and KubeCon+CloudNativeCon North America in Los Angeles, the latter of which gathered over 3,000 community members in person. These events would not have been possible without our commitment to attendee safety by requiring vaccinations and using vaccine verification technologies, diligent on-site health checks, and strict enforcement of the use of masks and social distancing protocols. With borders opening up shortly, we are ecstatic to see even more of our community, live and in-person, again in 2022.
On behalf of the entire Linux Foundation team, I congratulate our communities for their exceptional outcomes under another extraordinarily challenging year and wish all of you a happy and prosperous 2022, when I hope we get to see you in person once again.
Jim Zemlin Executive Director, The Linux Foundation
These efforts are made possible by our members. To learn how your organization can get involved with the Linux Foundation, click here.
The Open Infrastructure Foundation held its first OpenInfra Live: Keynotes last month. The two-day virtual event featured presentations by more than 30 leaders from the global OpenInfra community streaming live on YouTube, LinkedIn and Facebook. Keynote topics covered a broad range of OpenInfra use cases, and projects like OpenStack and Kubernetes took center stage.
We’ve compiled a summary of the dynamic and engaging presentations given during the OpenInfraLive: Keynotes event. Check ‘em out, and dive into the full event recordings here.
Our community has achieved several amazing milestones since the Open Infrastructure Foundation was launched in January. Just a few of which are:
25% increase in OpenInfra Foundation membership
Microsoft joined as a Platinum Member and Nipa Cloud joined as a Gold Member
All projects had major releases during the pandemic (thank you to contributors!)
66% growth in OpenStack cores in production, from 15 million to 25 million cores
Now over 180 data centers for public clouds are powered by OpenStack
Collier and Bryce also talked about the emergence of an OpenInfra Standard. LOKI—Linux OpenStack Kubernetes Infrastructure—highlights the trend of organizations integrating three of the top four most active open source projects together in production.
Srinivasan talked about the need to decentralize at the infrastructure layer, which removes the “trust factor” requirement of the operator because the entire backend is not only open source, but also open state and open execution.
As a true champion of the open source movement, Black shared their perspective on The Four Opens, the value they bring, and the responsibility of the community that upholds them to be mentors for the next wave of new members.
Simplicity of adoption and mitigation of risk are a couple of benefits of open source licensing. These open source advocates take a look at licensing from the end user/contributor perspective and discuss the impact on users and organizations when open source is changed to a proprietary license.
The Linux operating system was started in a dorm room in Helsinki, Finland, and today powers the vast majority of the world’s technology systems. Citing this herald of the open source movement, Jim expresses that open source has become the most important part of the world’s technology supply chain, giving us hope that generosity works and that sharing and competing can happen at the same time.
Meet Dr. Chulya who represents the first locally owned Thai public cloud, Nipa Cloud, a new Gold Member of the OpenInfra Foundation. Nipa Cloud is looking forward to building the OpenStack community in Thailand while helping companies reduce costs by migrating to public cloud.
Chowdhury covers Workday’s journey from bare metal to virtualized workloads, which has transformed how they deploy workloads. Workday has doubled their OpenStack infrastructure since 2020, deploying in 5 geographical locations across the US and EU, and they’ve built a CI/CD pipeline that deploys on OpenStack.
Hear updates on the state of open infrastructure and how our scope expanded from building open source who write software that runs in production to getting infrastructure powered by open source software everywhere.
With compute resources of over 100,000 cores, over 1,500 hypervisors, and more than 5 petabytes of storage being run from 4 different data centers (3 physical, 1 on iCloud), Meltem shares what clouds they are leveraging at Trendyol and why they chose OpenStack.
Zuul in Hybrid Environments: James Blair, Founder, ACME Gating
What is Zuul and how does it help with a hybrid cloud initiative? Blair discusses this along with Zuul’s code review capabilities.
Removing jitters and isolating other containers and OS has been a primary objective for Ant Group, which has 10,000 nodes of Kubernetes running Kata in production. Tune in to hear Sunny and Tao discuss that initiative.
Edge is important, as explained by Orton with BRCK who is working in Africa and the Philippines to bring affordable resources to education, healthcare, and more. They’re deploying in the field and sharing information back to the Magma community.
Deploying vRAN and OpenRAN with StarlingX: Ildiko Vancsa, Senior Manager of Community and Ecosystem, OpenInfra Foundation with Andy Dunkin, OpenRAN RF & Digital Platform Development Manager, Vodafone, Muhammad Gil , VP, Industry Solutions, Wind River and John McCready, Director of Product Management, RAN and Private Mobility Solutions, Dell Technologies
StarlingX is a scalable and flexible open source platform that can be integrated into telecom environments that need to follow standards to provide stable and highly available service to consumers. This panel highlighted how the community-driven innovation for Radio Access Networks powered by StarlingX is an opportunity for telecoms like Vodafone. Thank you to Wind River for being a headline sponsor of the event!
Nine out of the top 10 telecoms in the world are running OpenStack, and China Mobile is the largest. They run 6 million cores and LOKI across network cloud, public cloud, and IT cloud—all on OpenStack. Hear Duan discuss how the combination of connection, computing force, and capability is opening up a new era of Open Infrastructure.
This panel discussion centers around how movements like OCP help us come together to drive change, addressing the rise of regulatory and investor pressure.
Thank you to all of our event sponsors who made the OpenInfra Live: Keynotes possible!
Headline: Red Hat, Wind River
Supporting: Cloud&Heat, Component Soft, Coredge, InMotion Hosting, iVolve and VEXXHOST
The event wrapped with an exciting announcement that was shared in a quotable video featuring Nils Magnus, a community member from T-Systems. While the community has done incredible work virtually though the pandemic, the OpenInfra Summit is returning in person in June 2022!