Now that the Fedora Beta is officially released, the Fedora Cloud SIG would like to get the community together this week to find and squash some bugs. We are organizing a test day for Monday, October 5th.Continue reading
Now that the Fedora Beta is officially released, the Fedora Cloud SIG would like to get the community together this week to find and squash some bugs. We are organizing a test day for Friday, March 20th.
For this event we’ll test Fedora Cloud Base content. See the Alternative Downloads Beta Page for links to the Beta Cloud Base Images. We have qcow, AMI, and ISO images ready for testing.Continue reading
Fedora 29 Atomic and Cloud provides
Both Fedora Cloud Base and Atomic Host provide the latest available versions of packages in Fedora 29 containing all features and bug fixes done in individual packages like the kernel, cockpit and more. Additionally, Fedora Atomic Host includes the latest version of
The Fedora Atomic Working Group is changing where you participate in our portion of the Fedora community. IRC, mailing lists, and more are all moving. Read on so that you know where to find us.
The Atomic Working Group is responsible for Fedora’s new container cloud platform, currently consisting of Fedora Atomic Host and the Fedora Layered Images Build System & Repository (FLIBS). As Atomic is now one of the three primary spins for Fedora, the WG spends most of its time on releases and integrating new container technologies into the OS. We are building the immutable infrastructure of the future, helping make Fedora the best free platform for automating thousands of servers.
When the Fedora Board (the precursor to the current Fedora Council) set up the three-edition strategy for Fedora, we chose three broad areas, and asked interested people in our contributor community to develop focused editions aimed at a target in each area. These were server, desktop, and emerging computing — resulting in Fedora Server, Fedora Workstation, and Fedora Cloud Base Image.
Announcing: Fedora Docker Layered Image Build Service is GO!
It is with great pleasure that the Fedora Project Announces the availability of the Fedora Docker Layered Image Build Service to the Fedora Contributor Community!
With this announcement we open the availability of the Docker Layered Image Build Service for the Docker Layered Images. The Fedora Cloud WG has been the primary maintainers of this project on GitHub. But now the service is available in dist-git as official components of Fedora. From there we will extend an invitation to all Fedora Contributors to maintain Docker Layered Image Containers for official release by the Fedora Project. Currently this effort is to enable the Fedora Cloud/Atomic Working Group goals of targeting Fedora Atomic Host as a primary deliverable to power the future of Cloud. This is also to enable the Fedora Modularity work be delivered as Containers in the future as Fedora becomes fundamentally more modular in nature.
With the Flock conference being under way, Thomas answers a few questions related to his expertise.
What would you like to achieve at Flock 2016? (what outcome would you like to see?)
I’d love to show that Red Hat folks outside of the Fedora project are
committed to the greater community. I’d also love to get folks up to
speed on container security (the topic of my presentation).
The Fedora Cloud Working Group met on June 7 and 8 in Raleigh to work on deliverables for Fedora 25 and beyond. As it turns out, we had a really productive set of discussions and have some good ideas for the Cloud Working Group going forward.
Some of the discussions were around immediate action items, some were around ideas of where we’d like to go – and these will require additional discussion with the larger community. As a reminder, the working group tries to operate on a consensus model and with transparency as much as possible. This means major decisions are usually only taken after a discussion has been held on the email@example.com mailing list and have either gotten enough +1’s from members to pass, pass via lazy consensus, or get knocked down for one reason or another.
Here’s a quick sweep of major topics that came up over the two days!
Then you should *totally* participate remotely in the Cloud Working Group’s Fedora Activity Day (FAD) in Raleigh, NC on June 7th and 8th! The Cloud Working Group will be making decisions, tackling tickets, and writing code to help with topics like automated testing, documentation, and increasing our public cloud provider footprint.
Be sure to check out the Cloud FAD wiki page, sign up as a remote attendee, and join us in #fedora-meeting-3 on Freenode during the event.
This article originally appeared on contributor Josef Strzibny’s personal blog.
First update of what? If you haven’t notice it yet, we announced a new developer portal for Fedora some time ago. Today I released a first update with some new contributions that landed on our GitHub after the announcement. So what’s new?
Apart from that this is mainly bugfix release fixing many typos, but some improvements are merged as well. One of those changes is for example suggesting using libvirt’s Polkit rules instead of those shipped by
vagrant-libvirt-doc sub-package when configuring password-less access to libvirt domains via Vagrant.
Some of the pending contributions did not make it for this release, but the next ones might happen more often. Big thank you goes to all our new contributors! And if you haven’t submitted anything yet, perhaps now’s the time. 🙂
Copyright © 2020 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.