We're updating copr packages to the new versions which will bring new features and bugfixes.
This outage impacts the copr-frontend and the copr-backend.
We're updating copr packages to the new versions which will bring new features and bugfixes.
This outage impacts the copr-frontend and the copr-backend.
In Fedora 40, Cloud images for Microsoft Azure are directly available in Azure via its new Community Gallery feature. This article will describe how to use these.
Starting in Fedora 39, the Fedora Project began producing Cloud images for Microsoft Azure which could be manually uploaded to an Azure tenant. In Fedora 40, these images are available directly in Azure via its new Community Gallery feature.
To use Microsoft Azure, you will need a Microsoft account. New users get 12 months of several services free, including virtual machines, so you can try everything covered in this article without needing to pay for anything. These virtual machines have 1-2 vCPUs and 1 GiB of RAM, which is enough for development or testing, low traffic web servers, small databases, etc.
To get started, go to the Community images service in the Azure Portal. Add a filter on Public gallery names and select Fedora’s public gallery name, Fedora-5e266ba4-2250-406d-adad-5d73860d958f.
Select a Fedora 40 x64 image in a location near you, then click Create VM.
Alternatively, you can go to the The Fedora Project’s Cloud section, click Launch in public cloud, and select the Azure region to jump directly to the Create VM blade.
Click Create new under the Resource group field. Resource groups are buckets of arbitrary resources (virtual machines, storage accounts, public IP addresses, etc.) which are related. Next, give your virtual machine a name. The name you choose becomes the host name as well as the virtual machine resource name in Azure. After that, you should set the virtual machine size. Click See all sizes and type “B2ats_v2” into the search bar, click on the only result, and click Select at the bottom of your screen.
Finally, click Review + create at the bottom of your screen, and then click Create.
Download the SSH key it generates for you. Afterwards, you will be taken to a page where you can see your resources being created. Once they’ve all completed, click on Go to resource. This will take you to the overview page for your new virtual machine running Fedora 40. Under Essentials you’ll find the public IP address assigned to your instance which you can use to SSH to the virtual machine.
Open a terminal, ensure the SSH key you downloaded has proper permissions, and log in to your new machine:
chmod 600 ~/Downloads/<key name>
ssh -i ~/Downloads/<key name> azureuser@<pubic IP address>
Finally, if you decide you don’t need the machine anymore, you can clean everything up by deleting the resource group. From the virtual machine overview page, click on the resource group name you created under Essentials, then click Delete resource group and confirm you want to delete it. Everything you created in the resource group is destroyed with it.
You may prefer to manage your resources from the command line. The downside of the CLI is it doesn’t guide you through all the options available. The upside is that, if you know what you want, it’s much quicker than clicking through all the options available. This section covers using the CLI to create the exact same virtual machine as the first section.
Install the Azure command-line interface and log in:
sudo dnf install azure-cli
az login
We need the Fedora 40 image ID in Microsoft Azure to launch the virtual machine from the CLI. Each Fedora release has an image definition for each hardware architecture. Each image definition contains one or more image versions. We add new image versions with the latest updates on a regular basis.
First, list all available image definitions in Fedora’s public gallery:
az sig image-definition list-community --public-gallery-name Fedora-5e266ba4-2250-406d-adad-5d73860d958f --location eastus --query '[].name'
Optionally, you can list the versions available using an image definition’s name:
az sig image-version list-community --public-gallery-name Fedora-5e266ba4-2250-406d-adad-5d73860d958f --gallery-image-definition "Fedora-Cloud-40-x64" --location eastus --query '[?!excludeFromLatest].uniqueId'
Typically, you should use the latest available version of an image definition, which you can reference by replacing the version number in the image version’s uniqueId with latest. For example, the image ID for the latest x86_64 Fedora 40 image is /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/Fedora-Cloud-40-x64/Versions/latest.
Begin by creating the resource group:
az group create --location eastus --resource-group fedora-in-azure
Next, create the virtual machine using the image ID we found:
az vm create --location eastus --name fedora40 --resource-group fedora-in-azure --image /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/Fedora-Cloud-40-x64/Versions/latest --size Standard_B2ats_v2 --security-type TrustedLaunch --generate-ssh-keys
Finally, you can delete everything with:
az group delete --resource-group fedora-in-azure
We have covered the basics for creating Fedora virtual machines in Microsoft Azure. For more in-depth coverage of virtual machine features you can refer to the virtual machine documentation for Azure. The Azure CLI documentation is also available online.
The voting period has now opened for the Fedora Linux 40 elections cycle. Please read the candidate interviews and cast your votes in our Elections App. Visit our Voting Guide to learn how our voting system works, and voting closes at 23:59:59 UTC on May 30th.
Fedora Mindshare has one seat open. Below is the candidate that will be elected at the end of the voting period.
The Fedora Council has two seats open. Below are the candidates eligible for election.
The Fedora Engineering Steering Committee (FESCo) has four seats open. Below are the candidates eligible for election.
The EPEL Steering Committee has four seats open. Below are the candidates eligible for election.
The post Elections Voting is now Open! appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:56:48 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I started contributing to EPEL 11 years ago with some nodejs packages for OpenShift. I later added rubygems and golang packages as OpenShift changed languages. Later, RHEL 8 did not have KDE, so I added KDE to epel8, and have been maintaining KDE in epel ever since. I have picked up many other packages during the years, but I think my KDE contributions are what I am most known for.
I’ve been the EPEL Steering Committee chair since 2020, taking over from Stephen Smoogen. A lot of changes have happened since then, most of them for the better. I’m not responsible for all the changes, but it’s been wonderful being part of the committee as these changes have come through.
EPEL has grown to be part of my professional and personal life. I not only want to contribute to it, but help steer it’s growth and progression. I think as a EPEL Steering Committee member, I can help keep EPEL healthy and thriving.
The post EPEL Steering Committee Election: Troy Dawson (tdawson) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:55:51 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I’ve been an EPEL user since the mid 2000s and a package maintainer since 2021. I brought Saltstack back into EPEL and added a nifty linter for salt states called salt-lint. I am currently working on building all the dependencies for the upcoming pagure 6 release.
EPEL packages account for millions of downloads per week and are a vitally important part of the Enterprise Linux ecosystem. I earnestly believe in the project’s mission and am eager to contribute my skills and acumen to its success. I am excited about the opportunity to serve the EPEL community and help shape its future direction.
The post EPEL Steering Committee Election: Interview with Robby Callicotte (rcallicotte) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:55:09 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I’ve been a consumer of EPEL for more than a decade as I learned Linux and began my career—first in web hosting, then “DevOps”, and eventually being responsible for the network architecture and infrastructure for a large travel company. In the past four years, I helped to found the Rocky Linux project, where I became friends with Pablo Greco who encouraged me to participate in EPEL more actively, and I continue to maintain its various components, which involves significant Fedora and EPEL work as well as contributions to other upstream projects.
For over a year now, I have been a Fedora and EPEL packager and actively participate in EPEL Steering Committee meetings weekly. Most of the packages I maintain or contribute to are related to needs in the Rocky Linux project or are personally useful to me—such as remind, a calendar and alarm program that helps me stay organized, or passwdqc, a powerful password quality and policy enforcement toolkit that is especially useful in managing EL-based FreeIPA environments.
While I enjoy packaging, I find the most rewarding aspect of my work in EPEL to be mentoring and encouraging others to become Fedora and/or EPEL packagers. Growing the community and ecosystem of EL developers is crucial to the longevity of Enterprise Linux as a whole. Expanding the base of EPEL contributors not only strengthens EPEL but also benefits the broader Fedora developer community and can lead to more employer-sponsored contributions to Open Source.
In the coming months, I plan to introduce several cloud and HPC-related packages to Fedora and EPEL. I also aim to finalize a number of packages that are being introduced to Fedora following discussions in the #epel IRC channel, which I hope will bring in new Fedora and EPEL package maintainers.
I am running for the EPEL Steering Committee to help foster growth and increase activity within Extra Packages for Enterprise Linux (EPEL). EPEL is unique in its commitment to stability and freedom from unnecessary disruptions, mirroring the principles of RHEL. While enabling Fedora packages for Enterprise Linux is a significant goal, EPEL goes further by ensuring that updates and newly introduced packages uphold this stability.
Maintaining packages for EPEL can be daunting for many maintainers, particularly those new to Fedora packaging guidelines, policies, and workflows. This initial hurdle is crucial to understand the different layers of policy between Fedora and EPEL, which make EPEL a unique and valuable project. EPEL has a large user base because of the immense utility it provides, and growing the footprint of EPEL maintainers is crucial for the project’s long-term health.
The post EPEL Steering Committee Election: Interview with Neil Hanlon (neil) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:54:23 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I’ve been involved in epel since the epel-5/6 days. With epel7 I wrangled a bunch of the work to get things setup, including beta before the rhel release, lots of release engineering work and mirroring/content. I maintain a lot of packages in EPEL, both for others use and to use in Fedora Infrastructure, which heavily uses epel for managing items that are not in rhel proper. I’ve been happy to see epel continue to grow and flourish and these days I tend to just provide some light releng work for epel along with package maint. epel is a wonderful service and I think it really increases the usefulness of rhel and downstreams.
I think I provide a useful historical perspective on how things were setup and why, along with a release engineering perspective on how changes could be done or might affect composes.
The post EPEL Steering Committee Elections: Interview with Kevin Fenzi (kevin) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:53:36 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I’ve been working with EPEL since its inception – having been a user of “Enterprise Linux” since CentOS 4. I became a Fedora packager a few years ago with an explicit interest in the EPEL side of things. Little did I know I’d also end up caring greatly about the Fedora side and I came back from the dark side (Arch) and am a Fedora desktop user again.
I’m the infrastructure lead for AlmaLinux and through that have a great care for EPEL and everything it empowers users to do – not just for AlmaLinux but for the EL community at large.
I feel strongly that I can help steer the direction of EPEL due to my experience in the ecosystem.
The post EPEL Steering Committee Election: Interview with Jonathan Wright (jonathanspw) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:52:35 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I got my start in Fedora and EPEL back in 2014. I joined a new team at Rackspace whose primary purpose was to maintain IUS, a third-party package repository for RHEL. Packages in this repository were typically based on Fedora packages. Some of these packages had dependencies in EPEL. We also maintained several other packages in EPEL that were important to our customers. I continued on as a regular EPEL contributor, even after I left Rackspace in 2019 to join the CentOS team at Red Hat. In 2021, I started a new team at Red Hat to specifically focus on EPEL activities.
In 2020 and 2021, I designed and lead the implementation of EPEL Next, an optional repository for EPEL maintainers to perform builds against CentOS Stream when necessary. Also in 2021, I lead the implementation of EPEL 9. This brought some significant improvements over previous EPEL versions. We utilized CentOS Stream 9 to launch EPEL 9 about six months before RHEL 9. This resulted in RHEL 9 having more EPEL packages available at its launch (~5700) than any previous release, helping ensure a positive user and customer experience. If you want to learn more about EPEL Next and EPEL 9, I suggest watching my conference presentation “The Road to EPEL 9“.
Currently I’m leading the implementation of EPEL 10, which will include more improvements over previous EPEL versions. The plan is for EPEL 10 to have minor versions, obsoleting the previous EPEL Next model. This will allow us to better target specific minor versions of RHEL 10, as well as CentOS Stream 10 as the leading minor version. You can learn more about this plan in my conference presentation “EPEL 10 Overview“.
Aside from the hands-on technical work of EPEL architecture and packaging, I have engaged in various other efforts to promote visibility and awareness of EPEL, and to communicate with our users and contributors.
I have been on the EPEL Steering Committee since I was appointed to it
in 2020. As part of implementing elections for the committee, myself
and other members agreed to “step down” and essentially run for
re-election. I have enjoyed my four years serving on the committee, and
hope to have the opportunity to continue to serve the EPEL community. I
am passionate about EPEL and I am committed to continue finding ways to
improve the EPEL experience for both users and contributors.
The post EPEL Steering Committee Election: Interview with Carl George (carlwgeorge) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:47:17 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I have a background in compilers and toolchains, and I would like to use some of the knowledge I’ve gained over the years of building and troubleshooting applications to help make Fedora better. Specifically, I’m interested in helping packagers avoid making common mistakes through standardized macros and packaging practices and also by increasing the reliance on CI.
I’m currently one of the maintainers of the LLVM packages in Fedora which is a set of 14 packages that provide a C/C++/Fortran compilers as well as a set of reusable compiler libraries that are used for developing other languages and for developer tools, like IDEs.
I’ve also worked on two system wide change requests to help standardize the use of make within Fedora packages. These changes helped to make spec files more consistent across all of Fedora and also made it possible to remove make from the default buildroot.
When I am in a leadership role, like FESCO, and there is a disagreement, the first thing I do is make sure I understand the problem and the potential solutions. This usually requires having a discussion between all interested parties either on a mailing list, chat platform, or video call. Many times disagreements are simply the result of misunderstandings, so getting everyone together to discuss the issue in the same place can lead to a consensus decision and avoid the need for someone in leadership to get involved.
However, if consensus cannot be reached, once I like to try to get some third party opinions from people who have not been directly involved with the discussions. Once I feel comfortable I have enough information and am ready to make a decision, I make sure I am able to explain in writing why the decision was made and then I communicate the decision to all the stakeholders. It’s always important to have a written record of why a decision was made in case it needs to be revisited in the future.
I work for Red Hat on the Platform Tools team. I am the technical lead for our LLVM team and the overall technical lead for the Go/Rust/LLVM compiler group. This means that I work on packaging, bug fixing and upstream feature development for LLVM and work on high-level technical issues common across all 3 compilers.
The post FESCo Elections: Interview with Tom Stellard (tstellar) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:46:31 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I’ve been a member of FESCo for many years now, and it’s been a great experience. It gives me the opportunity to see a much wider view of the project than just the pieces I would otherwise contribute to.
As for steering the direction of Fedora, I think I would mostly just continue to do as I have been doing: pushing for Fedora to continue to be both the most advanced and one of the most stable open-source distributions in the world.
Aside from my work on FESCo, I am also acting as the Lead on the Fedora ELN project, which is a prototype of what will eventually be the next major release of Red Hat Enterprise Linux. We recently branched off CentOS Stream 10 from Fedora ELN, so we’re now looking to the future (and CentOS Stream 11!). Performing these activities in the public provides both an opportunity for the community to be involved with the creation of Red Hat Enterprise Linux as well as painting a clear picture of Fedora’s value to Red Hat, our primary sponsor.
Additionally, I have been acting as a primary administrator for the CentOS Stream Gitlab instance and I intend to volunteer my experience to help with the upcoming dist-git migration discussions.
First and foremost, I always strive for consensus. Most disagreements are not fundamental differences between people. Instead, they tend to be more nuanced. My goal (particularly within my FESCo service) is to make sure that everyone’s opinion is heard and considered; I then try to figure out how to meet in the middle.
Of course, not every decision can be resolved with consensus. In the event that a true impasse is reached, that’s the point where I usually advocate for calling a vote and proceeding with the majority opinion. On the whole, I believe that democratic decision-making is the best solution that humanity has come up with for resolving otherwise-insoluble disagreements.
Just so it’s very clear, I’m a Red Hat employee. My day-job at Red Hat is to organize and improve the processes we use to kick off development of the next major RHEL release. As such, my stances on FESCo will often represent my opinion of what will make that effort operate more smoothly. So, no matter how entertaining it might be, we’re not going to be replacing the entire contents of /usr/share/icons with the Beefy Miracle icon.
The post FESCo Elections: Interview with Stephen Gallagher (sgallagh) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:45:29 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
#devel:fedoraproject.org, #asahi:fedoraproject.org, #asahi-devel:fedoraproject.org, #kde:fedoraproject.org, #workstation:fedoraproject.org, #cloud:fedoraproject.org, #kernel:fedoraproject.org #centos-hyperscale:fedoraproject.org, #okd:fedoraproject.org, #budgie:fedoraproject.org, #multimedia:fedoraproject.org, #miracle:fedoraproject.org, #cosmic:fedoraproject.org, #centos-kernel:fedora.im, #admin:opensuse.org, #chat:opensuse.org, #bar:opensuse.org, #obs:opensuse.org, #RedHat:matrix.org, #networkmanager:matrix.org, #rpm:matrix.org, #rpm-ecosystem:matrix.org, #yum:matrix.org, #manatools:matrix.org, #lugaru:matrix.org, #buddiesofbudgie-dev:matrix.org, #PackageKit:matrix.org, #mir-server:matrix.org, #mageia-dev:matrix.org(There’s quite a bit more, but I think that sort of covers it. 
)
As a long-time member of the Fedora community as a user and a contributor, I have benefited from the excellent work of many FESCo members before me to ensure Fedora continues to evolve as an amazing platform for innovation. For the past few years, I have had the wonderful privilege of serving as a member of FESCo for the first time, and I enjoyed my time serving to steer Fedora into the future, and I wish to continue to contribute my expertise to help analyze and make good decisions on evolving the Fedora platform.
The bulk of my contributions to Fedora lately are on the desktop side of things. Following on the work I did to improve Fedora’s multimedia capabilities, we now have a SIG that takes care of bringing in and updating multimedia software into Fedora. The successful bring-up of the Fedora Asahi Remix by the Asahi SIG to support Fedora Linux on Apple Silicon Macs has brought notoriety and several new contributors to the community. Most recently, I am mentoring new contributors to support the development of the Fedora Miracle Window Manager and the Fedora COSMIC efforts, including assisting in setting up SIGs and guiding them in the processes to support their work.
Beyond the desktop and more into the clouds, I helped revamp the tooling for creating Fedora Cloud images as well as the base Vagrant and container images to leverage the new KIWI image build tool, which enables both Fedora Cloud contributors and third parties to much more easily build things leveraging Fedora Cloud content. This has led to renewed interest from folks who work in public clouds, and we’ve started seeing contributions from notably Microsoft Azure now.
My hope is that the work I do helps with making the experience using and contributing to Fedora better than it was ever before and that Fedora’s technical leadership in open source draws in more users and contributors.
I attempt to explain my viewpoint and try to build consensus through persuasion and collaboration. If there isn’t a path to consensus as-is, I try to identify the points of disagreement and see if there is a way to compromise to resolve the disagreement. Generally, this ultimately results in a decision that FESCo can act on.
To me, the most important thing about Fedora is that we’re a community with a bias for innovation. Our community looks to solve problems and make solutions available as FOSS, and this is something that Fedora uniquely does when many others take the easy path to ship old software or nonfree software everywhere. We work with tens of thousands of projects to deliver an amazing platform in an easily accessible and open fashion, built on FOSS infrastructure and tools. This makes Fedora special to me, and we should continue to hold ourselves to that high standard.
I’m also a big believer in community bonds and collaboration, which is why people tend to find me all over the place. I’m involved in Asahi Linux, CentOS, openSUSE, and several other similar projects in leadership roles as well as a contributor in order to demonstrate my commitment to this philosophy.
The post FESCo Elections: Interview with Neal Gompa (ngompa) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:44:33 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I have been a Fedora contributor since the very beginning – circa 2003-4 – and over the years have contributed on the packaging side, as an Ambassador (I can still remember burning CDs and shipping them via the local post office), and more recently on the policy side with Fedora (starting the Lua SIG) and EPEL (reestablishing the EPEL Packagers SIG, establishing a workflow for escalating stalled EPEL requests).
I am fortunate enough to have a day job at a company (Meta) that heavily uses CentOS Stream and contribute to many core Linux projects, where my main focus is on upstream work – so if the Fedora community entrusts me with this position, I hope to advocate for Change Proposals that advance Fedora’s four foundations (Freedom, Friends, Features, and First) – while accepting that not all Fedora features can be supported in CentOS Stream and RHEL. I feel that having experience in packaging software and working on tooling and workflows across Fedora, EPEL and CentOS Stream gives me a vantage point where I can understand where different parts of the community are coming from.
I am a proven packager (using it to help out with mass rebuilds or to help out fixing major issues) and a packager sponsor, a member of several packaging SIGs (Go, Lua, Python, Rust) and several SIGs that bridge the gaps between Fedora, CentOS Stream, and RHEL (ELN, which is a rebuild of Rawhide with EL macros; EPEL, which provides extra packages for EL distros; and on the CentOS side, the CentOS Hyperscale SIG, which provides faster-moving backports and additional functionalities (typically sourced from Fedora) for use on top of CentOS Stream.
I wrote ebranch to help with branching Fedora packages to EPEL and heavily use it in bootstrapping EPEL 9; a rewrite is in the work to turn it into a suite of related tools for dependency graph management, branching, and inventory tracking.
I have done, and am working on, various Change Proposals.
Oh, and I helped migrate my company’s Linux desktops to Fedora (Flock 2019), FOSDEM 2021
I have been vilified because of where I work; I have learned to accept that people might have very strong opinions on certain issues that they won’t budge on, whether the opinions are (IMHO) justified or not, and still find a way to be civil and collaborate on topics of shared interest.
I have been a part of the Fedora community (and before that, a user of Red Hat Linux doing my own rebuilds) for several decades; my involvement predates and outlasts working for several employers (some of them not RPM shops). I am also a Debian Maintainer – and I hope to bring my experience contributing to different distributions to inform FESCo discussions. I dislike NIH (not invented here); ideas should stand on their own merits and it is good to learn from others (both adopting good ideas and avoiding past mistakes).
The post FESCo Elections: Interview with Michel Lind (salimma) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:43:40 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
Over the past year and a half I’ve been drinking from a fire hose so to speak on all things Fedora and EPEL. I’ve been a user of the EL ecosystem for the better part of 20 years, and Fedora off and on throughout that. When I started packaging about a year and a half ago I never knew I would enjoy it so much, or working with open source in general. I feel that serving on FESCo is the next step for me in my open source contributions.
I’m on the team at AlmaLinux and can offer a unique perspective on things related to EL and EPEL.
I currently maintain (co-maintain and direct) over 600 packages and am a member of the EPEL SIG. My packages are of a wide variety and include many Python packages/modules. A few notable ones are certbot, btop, and iperf3, . The majority of my packages are CLI and server focused. I successfully built many of the Fedora infrastructure apps (noggin, ipsilon, some IPA components, etc.) for EPEL9.
I’m not officially in any of the marketing or ambassador SIG(s) but I’m a very vocal advocate for Fedora at many conferences I attend on behalf of AlmaLinux.
I became a packager sponsor a few months ago and while I don’t have any sponsees to my name yet, there are a few I’m working with.
While not directly related to FESCo I’ve also begun contributing to CentOS Stream and have successfully submitted changes which have been merged.
Disagreements are easily handled with good communication. When you’re on a team you are working towards the same goal with like-minded people and there’s no problem that good communication and discussion cannot overcome. Arguing for the sake of arguing has no place in a productive team.
I’m the Infrastructure Team Lead for AlmaLinux and naturally have a very strong interest in EPEL. I daily drive Fedora on my workstations.
I also contribute to CentOS Stream. I’ve had patches merged into iperf3, postfix, sssd and more, along with some still open/pending.
I prefer KDE to Gnome 
I’ve penned a few blog posts on relevant Fedora/EL things that may interest folks at https://jonathanspw.com
The post FESCo Elections: Interview with Jonathan Wright (jonathanspw) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:42:38 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I have been around in the Fedora community for many years now. With the many areas that I have contributed to, I think I can bring an important perspective to FESCo. I am excited by the recent success of Fedora Linux in general, and I want to make sure that this success is sustainable.
I am the most active package maintainer in Fedora, primarily because I’m the main point of contact for most Rust packages (and the Rust packaging toolchain). This includes a lot of package updates, triaging build failures and broken dependencies, and removing outdated / obsolete components from Fedora. I also regularly work with upstream projects to help port to new versions of their dependencies, and report and / or fix issues on some of the CPU architectures that are supported by Fedora. I am currently also working on bringing back packages for the Pantheon desktop, hoping that it will be possible to provide a spin based on Pantheon in the future. I also develop and maintain the service that provides the data source for the “broken dependencies” (FTI / FTBFS) information on the Packager Dashboard. And every Fedora release cycle, I triage, report, and attempt to fix upgrade path issues.
Many disagreements I’ve handled were only concerned with details, while the goals of everyone involved were still aligned. So I try to find common ground and / or explore alternative or creative solutions that can work for everyone involved.
No pineapple, and definitely not on Pizza.
The post FESCo Elections: Interview with Fabio Valentini (decathorpe) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:41:47 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
At the very least I’d like to maintain the representation of the non-US and non-English speaking communities in the Fedora Project. And then I’d also like to contribute to the conversations related to the Fedora infrastructure.
I’d like to spend some time on the topic of transparency of the build infrastructure in Fedora and CentOS and how we can possibly implement a GitOps-like approach to it:
On one hand Fedora is a well-known desktop Linux distribution and we need to continue to serve as such: to expand the user base, to reduce the number of issues the end-user meets.
On the other, Fedora is also a platform — a pool of integrated building blocks — so that anyone can use the pieces and build something they like. Thus the success of the project can be also measured by a number of projects which use Fedora as a foundation for their own development, whatever that might be.
I think Fedora Editions serve two purposes: they work as an entry point for newcomers who are not yet familiar with the variety of options Fedora can provide. And then they work as a technological focus – the way to showcase a certain technology and organize development and testing efforts around it.
They also serve as a permanent source of conflict, as any other opinionated selection process. And I would love to somehow lower the stakes in this conflict. I think that some strategy on promoting featured or trending Fedora Spins and Labs can help with that.
I plan to link some of the work in Fedora with the related work items in the CentOS Stream.
The post Council Election: Interview with Aleksandra Fedorova (bookwar) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:40:17 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
Because I’ve been nominated and have the time and energy! I wasn’t planning to run myself, but the nomination really made me excited. I thought about it for a bit, and realised there are things I believe I could help with, and that I have the time to seriously do this.
My only condition was I won’t win by default. But I’m a third candidate, and there’s two positions! So that’s a good start at least.
First I thought I don’t like this as a goal. But then I realised it’s not a goal, it’s a metric. And a surprisingly good one — more on that below!
(In fact, I recommend reading the answer to the next question now, and then coming back here. It’s easier for me to say what I’d do with understanding of the metrics.)
1) Communication
I’d like us to focus on solid communication tools.
Emails, forums, chats, issue trackers, pull requests, blogs, announcements, … I count all that as communication.
We don’t have to have everyone using every single tool. Different people have different preferences (or abilities!) regarding the ways they communicate.
Some people prefer to work in real-time, some asynchronously. Some people like to be notified, some people like to go pick communications up when they have time. Some people want everything in a single inbox, some people prefer things organised in separate buckets. For that matter, some people prefer emails and filters, some people prefer forums that are already categorised and visible without subscribing. And linkable. And clearly bet.. anyhow!!
(In fact I like email for some things, forums for another. They’re both good in their own respect.)
I don’t believe we should replace one kind of communicaiton with another. Because then we lose some current contributors. Adding more options can allow new contributors to join.
But I don’t want us to have too many (similar) options either. Because then people need to be on way too many channels, and it’s no longer about what kind of communication prefer, but about who’s using which chat app.
I want us to find the right balance. I don’t want anyone to feel left out. And I don’t want anyone to use a tool that’s frustrating for them. I want us to have solid communication tools and practices.
2) Clarity
For people who already want to contribute, I’d like to ensure we have a clear way for them to do so.
I haven’t said easy! I said clear. Some things are not easy. But clarity is important.
Innovation isn’t always easy. If it was everyone would do it. Fortunately, people like good challenges! But if they’re already stuck on just figuring out how to even join or what their options are, we have failed.
So I’d try to make us focus on clarity. Clear and visible processes, clear purpose of the tools we use, well-documented practices (ideally describing how things actually work, not how we just want them to work), etc.
And of course, if something can be easy, let’s make it that way. Like fixing a typo in docs from my phone. Boom. One more weekly active contributor right there! (And make it clear it’s easy!)
3) Collaborating with Centos
I’d like us to work with the CentOS community on sharing tools and practices. Having similar tools and ways decreases cognitive load and makes it easier to contribute in both places.
4) Artificial Intelligence
Have you heard about AI?
dodges a tomato
OK! I know there’s been a bit of a hype recently around AI. The technologies aren’t necessarily new, but more people (and companies) reached the tipping point of having enough compute power to make it do stuff fast.
I’d like to see where and how we can use (and not use) AI in a way that’s genuinely helpful, without compromising people’s privacy or comfort levels.
…
So that’s the general direction I’d try to go. I don’t have specific actions outlined, though. If I had those without listening first, we would have already failed in my opinion! But I hope this helped you understand at least my intentions.
(If you’re following my non-linear writing, let’s talk about Editions!)
Editions! Another complex topic I’ll try to cover in a few sentences!
Open source is great at allowing you to do basically anything in any way. So many opportunities to do things wrong! (Heh. And right of course!) But no one is an expert at everything. However, Fedora as a community has experts in quite a broad range of things.
I don’t want to write my own crypto, but rather have experts do that properly for everyone. I also don’t want to design every single bit of all my Fedora deployments.
There’s Fedora on my gaming PC. There’s Fedora on my Raspberry Pi running Home Assistant. There’s Fedora in most of my development containers. There’s Fedora running in a small VM on my M1 MacBook so I can have aarch64 stuff. There’s Fedora on my development workstation. Fedora everywhere! And each of these deployments have vastly different requirements in terms of security, performance, resource demands, managing updates, etc.
Fedora is a very powerful Linux platform, allowing us to do many things. So it makes sense to cover some of the most usual ones with opinionated Editions that make it easy to deploy and maintain them right.
And guess what! Fedora IoT means I never have to connect a monitor and a keyboard to my Raspberry Pi, because someone smart made it that way for me. Fedora Workstation runs Windows games on Steam with just a few clicks. In the aarch64 VM, I have… actually the KDE Edition (sorry, Spin!) because I’m like that. Never mind!
The point is, it’s been very little work to get each system running well for its intended purpose. And I have the trust that if I apply updates regularly by whatever method each Edition suggests, my systems will be running in a reasonably seure manner. And that’s what Editions are for in my opinion.
What would I change?
With growing ways to run Fedora, we might end up with a huge list of Editions.
Even now, looking at Editions, Spins, Labs, and Atomic Desktops… that’s a lot to take in as a user.
If instead we had a (guided) way for the user to express their needs, and out would pop an installer/image for the system that works for them… that would be awesome!
Like “I want an aarch64 VM (QEMU) image with KDE, but with as few things running as possible because I have very little RAM. My use case might be weird, but I’m gonna do this anyway, so this is your chance to make me do it in a reasonable way, so I have a better experience, and save time so I can join as a contributor!”
(Wow it’s getting late. I have just deleted like 17 more paragraphs of rambling. You’re welcome. Choose wisely!)
(Right, one more question!)
By already having a few hours a week available for a new thing! Combined with the council meeting being in European business hours which works great for me.
The post Council Election: Interview with Adam Samalik (asamalik) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:39:47 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I hail from APAC (India) and would like to focus on bringing in more non-US perspectives, which includes bringing in more contributors from diverse backgrounds. Efficient utilization of our brand new design assets which are now in multiple languages (Hindi, for example) to onboard variety of users (general and power-users) to the Fedora community as contributor either to functional sides (QA, packaging..etc) and/or outreach.
In the recent past; the council charter has been expanded to an Executive Sponsor. This role enables people like me to work closely with an upcoming initiative.
In parallel, I am closely working on Blueprints (https://discussion.fedoraproject.org/t/introducing-fedora-change-proposal-blueprints-in-association-with-fedora-qa/115903)
this is a long term effort and will benefit from my connections with people in Council (ie FESCo rep and FESCo at large)
As a council member, I would work closely with teams which will need more attention building pipelines for onboarding, mentoring and retention of contributors. In Fedora QA, I have worked extensively to handle a high influx of contributors and retain them for at least a Release Cycle or two. I have optimized workflows that have been helping Fedora QA to grow optimally without burning out contributors or team members. I could help solve problems and coordinate closely with CommOps and other teams to build data-driven contributor pipelines to help Fedora Project double its contributors by 2028.
However, there is no specific way to measure, BUT.. here’s something I think can define Fedora’s success the best
Fedora Linux’s success is measured by the people who use Fedora.
Fedora Project stands as the reference for the people who want to build an upstream community diverse and strong.
Fedora Project at its core is composed of people who take pride in packaging, testing, designing, translating, blogging, evangelizing and collaborating across the globe.
Fedora project takes pride in being a trendsetter for bringing technologies which impact a large downstream ecosystem and embolden their trust in our four foundations.
Fedora Editions are Fedora Project’s flagships. They are exclusively tested and tried by Fedora’s in-house QA team to deliver on the expectations of tens of thousands of users. These platforms serve as building blocks for the Fedora Project to share innovation across multiple downstream ecosystems. Fedora Edition has more room to grow in terms of adoption in CI platforms and pre-installs for Hardware Makers. I would love to drive the adoption of Fedora not only at an organizational level ; but also in schools, universities and next-gen digital influencers.
As a long-term member, the Council is a body which in the coming days will be working across many facades of the Project, taking bold decisions to make our community
more robust, productive and healthy. Being a long-term member, I support the goals and I’ve prepared my upcoming work cycles such that I have room to spend time
at the Council position.
The aforementioned changes in accordance with 2028 strategy impacts my role in Fedora Project at large and I will always want to be a stakeholder. This will help drive decisions which help the Quality teams day to day operations.
The post Council Election: Interview with Sumantro Mukherjee (sumantrom) appeared first on Fedora Community Blog.
admin )
on 2024-05-19 22:38:04 UTC
This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Monday, 20th May and closes promptly at 23:59:59 UTC on Thursday, 30th May 2024.
I’ve been in Fedora Project for more than 10yrs now. I have been a part of the Fedora QA team for the whole time. As a part of Fedora QA, I have signed off on multiple releases.
Apart from those, I have been an avid advocate of Fedora Project to the community at large, it has driven me to take up onboarding , ambassadorship and mentoring as part of Fedora Project. Recently, I am taking part in a11y initiative and few places of Mentorship init.
Fedora in recent years has been in the talks, be it conferences or tech news. I run my own YT channel, promote a lot of QA test day events over socials and totally believe in the power of Digital and Social Media. In this day and age, where Recognition is a very sought after and retention of efforts directly linked to rewards ; it’s important for a project like Fedora to become more efficient with resource allocation. My “why” is to figure out and open up more way how Fedora project can reward it’s contributors.
Mindshare is a very visible committee to begin with, however we can actually benefit from efforts like CommOps 2.0. I believe the more stats we have about out community and contributors the more we can get visibility in the obscure corners. I would like to be someone who helps bring more clarity for my team (Fedora QA) to start with and then expand to other parts of the project.
Recognition and Community health are the two key areas Mindshare can put some attention. Recognition brings in fresh blood in the community, adding more ideas and diverse way of doing things. Community’s health helps us with retention and avoiding possible burnouts. Outreach teams of all kinds will benefit from both of them and Fedora contributors will have a long lasting impact on the Open Source space for years to come.
The post Mindshare Election: Interview with Sumantro Mukherjee (sumantrom) appeared first on Fedora Community Blog.
remi )
on 2024-05-17 12:11:00 UTC
Here is a quick howto upgrade default PHP version provided on Fedora, RHEL, CentOS, AlmaLinux, Rocky Linux or other clones with latest version 8.3.
You can also follow the Wizard instructions.
On Fedora, standards repositories are enough, on Enterprise Linux (RHEL, CentOS) the Extra Packages for Enterprise Linux (EPEL) and Code Ready Builder (CRB) repositories must be configured.
dnf install https://rpms.remirepo.net/fedora/remi-release-40.rpm
dnf install https://rpms.remirepo.net/fedora/remi-release-39.rpm
dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm dnf install https://rpms.remirepo.net/enterprise/remi-release-9.rpm subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms
dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms
dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm dnf install https://rpms.remirepo.net/enterprise/remi-release-9.rpm crb install
dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm dnf install https://rpms.remirepo.net/enterprise/remi-release-8.rpm crb install
With Fedora and EL ≥ 8, you can simply use the remi-8.3 stream of the php module
dnf module reset php dnf module install php:remi-8.3
By choice, the packages have the same name as in the distribution, so a simple update is enough:
yum update
That's all :)
$ php -v
PHP 8.3.7 (cli) (built: May 7 2024 16:35:26) (NTS gcc x86_64)
Copyright (c) The PHP Group
Zend Engine v4.3.7, Copyright (c) Zend Technologies
with Zend OPcache v8.3.7, Copyright (c), by Zend Technologies
The upgrade can fail (by design) when some installed extensions are not yet compatible with PHP 8.3.
See the compatibility tracking list: PECL extensions RPM status
If these extensions are not mandatory, you can remove them before the upgrade, otherwise, you must be patient.
Warning: some extensions are still under development, but it seems useful to provide them to upgrade more people and allow users to give feedback to the authors.
If you prefer to install PHP 8.3 beside the default PHP version, this can be achieved using the php83 prefixed packages, see the PHP 8.3 as Software Collection post.
You can also try the configuration wizard.
The packages available in the repository were used as sources for Fedora 40.
By providing a full feature PHP stack, with about 130 available extensions, 10 PHP versions, as base and SCL packages, for Fedora and Enterprise Linux, and with 300 000 downloads per day, the remi repository became in the last 18 years a reference for PHP users on RPM based distributions, maintained by an active contributor to the projects (Fedora, PHP, PECL...).
See also:
admin )
on 2024-05-17 08:00:00 UTC
Join us next weekend on Friday and Saturday, May 24-25 to celebrate the release of Fedora Linux 40! We’re going to be hearing from community members inside and outside of the Fedora Project on what is new in Fedora 40, what we can look forward to next, and how we come together as a community.
Register to attend the Fedora 40 Release Party here!
Join us!
Fedora Release Parties are virtual, user-focused conferences where the community comes together to talk about what’s new in the latest release of Fedora and where we’re going for future releases. Topics we’ve covered include the process of working through implementing a change and roadmaps for what different teams want to do next in Fedora. Sometimes there are updates from Fedora-associated groups who have something to share, like Amazon or Lenovo. We also have breaks for socials where we can talk to each other in video calls (you don’t have to share video or speak if you don’t want to). If you have an interest in a behind-the-scenes look at your favorite distro, come learn and hang out with the contributors who make it!
In previous years we used Hopin to run virtual conferences, but the Fedora 40 Release Party will be the first that we do in Matrix! We’ve wanted to do this since the Creative Freedom Summit showed how it could be done a couple of years ago. This is a step that allows us to lean more on open source for outreach.
However, we also want to be open in another way, and that’s with livestreaming. We will be streaming the talks on our Fedora Project YouTube channel. That way anyone can watch and the streams will be immediately available afterwards!
Please register for the release party! Once you do and provide your Matrix ID, the organizers will invite you to the Matrix channel and we’ll be on our way to a great celebration.
We hope to see you there!
Check out the Fedora 39 Release Party to get an idea of the kinds of topics we cover.
Get hyped on social media with hashtag #FedoraReleaseParty!
berrange )
on 2024-05-16 22:35:39 UTC
For many years now, energy suppliers have been rolling out “smart meters” to home across the UK. It has largely been promoted as a way to let consumers reduce their consumption by watching their energy usage on an in home display (IHD) gadget. This is massively under selling the potential benefits of smart meters, and combined with various other reasons, leaves many unenthusiastic about the change. A few more adventurous suppliers, most prominently Octopus Energy, are taking advantage of smart meters to offer innovative dynamic tariffs, which particularly benefit those with electric vehicles.
I have been exploring the possibility of a solar PV installation at home and after talking to various suppliers have been left feeling quite underwhelmed with the reports they provide with their quotations. Typically a selection of crude 2-dimensional charts showing potential generation per month and some rough estimate of how much grid import will be reduced and grid export available based on your yearly kwh usage figure. They’ll only illustrate one or two scenarios, so it is hard to understand the impact of altering the number of panels requested, or sizing of any battery storage.
The European PVGIS service provides a good site where you can visualize the solar generation at your home based on actual recorded atmospheric conditions from history (typically their data lags current day by 2-3 years). They still only make use of your yearly kwh consumption figure with a generic model to estimate benefits. With a smart meter I have historic electricity consumption for my home in kwh at 30 minute granularity. Match that against the PVGIS data and its possible to produce a fine grained simulation of solar PV generation potential against consumption.
And so came forth the idea of a simple python script I’m calling “smartsolar” to combine PVGIS data with smart meter data and produce reports evaluating potential deployment options. It can use smart meter records downloaded from n3rgy (compatible with any UK supplier once registered), or from Octopus Energy‘s customer portal. Using plotly the reports contain 3-dimensional interactive charts showing data day-by-day, hour-by-hour. Changing the configuration file lets you quickly evaluate many different deployment scenarios to understand the tradeoffs involved.
In the charts (screenshots of a fixed POV only, non-interactive) that follow I’m evaluating an arbitrary installation with 10 panels on a south-east orientation and 6 panels on a north-west orientation, panels rated at 400W, along with 10 kwh of battery storage. The smart meter consumption data covers primarily 2023, while the PVGIS generation data is from 2019, the latest currently available.
The first chart shows the breakdown of consumption data and exposes some interesting points. The consumption is broadly consistent from day-to-day across the whole year and is spread fairly flat across the time period from 8am to 11pm. This reflects the effects of full time remote working. Someone office based would likely see consumption skewed towards the evenings with less in the middle of the day. The enormous nighttime peaks in consumption in the last month of the year reflect the fact that I acquired an electric vehicle and started charging it at home on a Zappi. The huge day time usage peak was a side effect of replacing our heating system in Dec, which required temporary use of electric heaters. NB, the flat consumption around Sept timeframe is a result of me accidentally loosing about 25 days of smart meter data.
The next two charts give the real world PV generation of the two hypothesized solar arrays, based on the 2019 PVGIS data source. The larger south east facing array starts generating as early as 5am in the middle of summer, but drops off sharply around 3pm. There is still useful generation in mid-winter from 8am till around 2pm, but obviously the magnitude is far below summer peak.
Conventional wisdom is that PV is a waste of time on predominantly north facing roofs, but what is the real world performance like ? The small north west facing array shows a gradual ramp in mid-summer from 6am to reach a peak at around 6pm, and drops off to nothing by 8pm. For the 2 months either side of mid-winter, the generation is so negligible to be called zero. The absolute peak is 1/2 that of the south-east array, but there are 10 panels south east and only 6 panels north west. So peak generation per panel is not too terrible on the north east side. The limitations are really about the terrible winter performance, and the skewing of generation towards the evening hours. The evening bias, however, is potentially quite useful since that could match quite well with some people’s consumption patterns and early evening is commonly when the national grid has highest CO/2 intensity per kwh.
Seeing generation of each array separately is interesting in order to evaluate their relative performance. For comparison with consumption data though, a chart illustrating the combined generation of all arrays is more useful. This combined chart shows the south east and north west arrays complementing each other very well to expand the width of the peak generation time in the summer months, with peak summer output of 4kw per hour and covering the main hours of consumption. There is still useful improvement in the spring and autumn months, but winter is unchanged.
By taking the intersection of consumption and generation data, we can evaluate what subset of the generated energy is capable of being consumed at home, ignoring the possibility of battery storage. This chart shows the the generated energy can make a significant contribution to recorded consumption across the whole year. Obviously generated energy is only being consumed during daylight hours, since this chart discounts the usage of the any hypothetical home storage battery
It gets more interesting when taking into account the battery storage. This new chart shows that the house can run from self-generated energy around the clock for most of the year, but it especially shows how the battery can “time shift” generated energy into the evening once daylight has faded, but the house still has significant energy needs and continues to supply the house throughout the night even for some days in winter.
Another way of looking at the data is to consider how much energy is being imported from the national grid, as this indicates an inability to generate sufficient from the local PV arrays. First without the battery storage, it can be seen that in the middle of the day grid import is negligible outside of the winter months, but there is still considerable import in the evenings. The spikes from EV charging and temporary electric heaters are also still present. The winter months still show some significant grid import even in the middle of the day.
Adding in the battery storage calculations has a really dramatic impact on grid import. With 10kw of storage, there is enough buffer to be 100% self-sufficient in energy generation for 7 months of the year, which is a really astonishing result. A battery of this size obviously can’t address the peaks demanded by the EV charging periods, since the car battery capacity is well in excess of the home storage battery, but that’s to be expected.
The total PV generation capacity over the year with the 16 panels is 5300 kwh while yearly consumption is only 3000 kwh, so clearly there is a lot of excess electricity going unused. To visualize this, a chart showing exports to the grid is useful to consider. Unsurprisingly, with no battery, we see strong grid export rates across all the day time hours when the panels are generating.
If we now add in the effects of a home battery, the grid export pattern changes somewhat. In winter months there is absolutely no grid export, with 100% of solar generation now able to be consumed locally, since demand far exceeds what is able to be generated in these months. In the rest of the months, export doesn’t start until an hour or two later in the morning. This shows the battery being recharged after overnight usage, until it is full and exporting of energy resumes.
An alternative way to consider the grid import and export is to combine the two charts to illustrate the flow, with positive being export and negative being import. This nicely visualizes when the direction of flow flips during the day.
With battery storage taken into account, it is very apparent when there is neither grid import nor grid export during summer months.
After considering the import and export rates for the grid, the final thing to look at is the charge and discharge rate of the battery storage. In terms of charging, the pattern broadly reflects the initial period of daylight hours throughout the year, as there is always either a slight mismatch in generation vs demand, or a huge surplus available. The battery typically fills up very quickly at the start of the day and remains that way for most of the day. This might suggest the need for a bigger battery, but the grid import chart shows that the house can run entirely from local consumption for 8 months of the year, an in winter months all PV generation is consumed, so there is not much to gain from a bigger battery.
The battery discharge pattern is perhaps the more interesting of the two charts, as it shows exactly when the benefit of the battery is most felt. In summer there are some peaks of discharge at the start of the day, this reflects some temporary loads which exceed the available generation, such as running the dishwasher or washing machine. In the middle of the day there is very little discharge except for winter months, but the evening is there is really shines. The solar PV generation has peaked, but there is still major consumption demand for cooking dinner on an electric induction hob, and/or oven, and the periodic use of a tumble dryer. Finally the battery takes up the load throughout the night when there is zero PV generation, but fairly low baseline demand.
Again the charge and discharge charts can be combined to show the flow in (positive) and out (negative) of the battery
The final chart to look at is the battery charge level, which will give an idea of how well sized the battery is. If it never reaches a 100% full state, then it is likely oversized, but if it spends the whole year at 100% full state, then it is likely undersized. The ideal with be tradeoff somewhere in between, perhaps with a battery large enough to eliminate grid import for perhaps the middle 50% of the year, showing periods of strong charge and discharge.
With this walkthrough complete, the potential benefits of having fine grained electricity consumption data from smart meters is becoming more apparent. Having access to both consumption and generation data for your home and its location allows evaluation of an arbitrary number of different solar PV + battery storage deployment options, where a commercial installer might only show 2-3 scenarios at most.
There are still many limitations to the visualization that should be kept in mind
Despite these caveats, the visualization should still be very beneficial in evaluating different solar PV and battery installation scenarios.
andreashaerter )
on 2024-05-16 17:32:00 UTC
The ATEN CV211 is an all-in-one KVM (Keyboard, Video, Mouse) adapter that turns your laptop into a KVM console, combining the functionality of a wormhole switch, capture box, external DVD-ROM, keyboard, mouse, and monitor, all in one compact and convenient unit. I really like the hardware in daily operations, especially when I have to a takeover new environments with “historically grown” cabling. It is nice to have the ability to get the screen and keyboard control of a yet unknown server without hassle—all with a small USB adapter in your backpack:
If you connect the adapter, you’ll get a 10 MiB drive mounted with the following contents, containing a Microsoft Windows Client WinClient.exe (basically a Runtime Environment and wrapper) and the real application JavaClient.jar:
$ ll
total 9,1M
drwxr-xr-x. 2 user user 16K 1. Jan 1970 .
drwxr-x---+ 3 root root 60 30. Apr 19:08 ..
-rw-r--r--. 1 user user 3,7M 30. Dez 2019 JavaClient.jar
-rw-r--r--. 1 user user 2,0M 30. Dez 2019 Vplayer.jar
-rwxr-xr-x. 1 user user 3,5M 30. Dez 2019 WinClient.exe
The JavaClient.jar KVM console is mostly the same as ATEN uses for all their IP KVM stuff. They just bind the service to some high port on localhost and use the hardcoded credentials -u administrator -p password to connect (which is obvious in several places):
Sadly, the Java application is not able to run out-of-the-box on a Fedora 40 Linux with OpenJDK / Java SE. The application will start but sometimes does not even list the device. And if there is a device to connect to, the login will fail:
The JavaClient.jar will not be able to connect with any supported OpenJDK or Azul Zulu Java RE:
# incompatible Java version :-(
$ java -version
openjdk version "17.0.9" 2023-10-17
For anybody having the same problem, the following should help:
.jar files are in ./.For example, if you just extract jdk-7u80-linux-x64.tar.gz to /tmp, you can use the application as follows:
tar -xvf jdk-7u80-linux-x64.tar.gz -C /tmp
cd /run/media/user/disk # or wherever the ATEN CV211 storage was mounted
sudo /tmp/jdk1.7.0_80/bin/java -jar ./JavaClient.jar
You can download the Oracle JDK 7 from https://www.oracle.com/de/java/technologies/javase/javase7-archive-downloads.html, but keep in mind to check the license conditions, especially if you are operating in a commercial environment.
Do not use this old, unpatched Java RE for anything else because of known security vulnerabilities. ↩︎