F23 System Wide Change: SELinux policy store migration
by Jan Kurik
= Proposed System Wide Change: SELinux policy store migration =
https://fedoraproject.org/wiki/Changes/SELinuxPolicyStoreMigration
Change owner(s):
* Petr Lautrbach <plautrba at redhat dot com>
* Miroslav Grepl <mgrepl at redhat dot com>
The newest SELinux userspace project release 2015-02-02 includes a change of the location of the SELinux policy store, which defaults to /var/lib/selinux/.
== Detailed Description ==
In the SELinux userspace project release 2015-02-02, the SELinux policy store was moved from /etc/selinux/<store>/modules/ to /var/lib/selinux/<store>/.
The new policy store
* has a new complex structure
* supports priority of modules
* the CIL language is used for cached modules
* original modules are converted using an HLL compiler in /usr/libexec/selinux/hll/. The pp compiler converts pp format to CIL language.
== Scope ==
* Proposal owners:
- prepare SELinux userspace packages with the release 2015-02-02
- prepare SELinux policy packages with the new store location
- prepare a migration script for users modifications and modules
- check if all packages containing SELinux modules use the right location
- check if all SELinux modules used in Fedora packages are compatible with the new SELinux userspace and are convertible to CIL language
* Other developers: N/A
* Release engineering: N/A
* Policies and guidelines:
- there's no need to update policies
- there might be guidelines which mention the old store location which should be updated
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
7 years, 9 months
F23 Self Contained Change: Containerized Server Roles
by Jan Kurik
= F23 Self Contained Change: Containerized Server Roles =
https://fedoraproject.org/wiki/Changes/Containerized_Server_Roles
Change owner(s):
* Stephen Gallagher <server at lists dot fedoraproject dot org>
Enhance rolekit to be able to deploy Server Roles using the Nulecule Container Specification.
== Detailed Description ==
In Fedora 23, rolekit will gain the ability to deploy Server Roles as containerized applications following the Nulecule specification. This will allow us to be able to isolate the roles more fully from the rest of the system as well as enabling these roles to be migrated to a larger, cloud-based system (such as the Atomic Platform).
== Scope ==
* Proposal owners:
- Design a rolekit framework for deploying Server Roles inside a Docker container.
- Implement a reference role to deploy memcached.
- Time-permitting, update the Database Server Role to optionally operate within a container.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
7 years, 9 months
F23 System Wide Change: Python 3 as Default
by Jan Kurik
= Proposed System Wide Change: Python 3 as Default =
https://fedoraproject.org/wiki/Changes/Python_3_as_Default
Change owner(s):
* Slavek Kabrda <bkabrda at redhat dot com>
* Matej Stuchlik <mstuchli at redhat dot com>
* Miro Hroncok <mhroncok at redhat dot com>
* Thomas Spura <tomspur at fedoraproject dot org>
* Robert Kuska <rkuska at redhat dot com>
Up until now, Fedora has used Python 2 as the default Python implementation. This change proposes switching to Python 3. The details of the term "switching" are explained thoroughly in the Scope section.
== Detailed Description ==
Python 3 is the next generation of Python programming language. It is currently mature and stable, since it has been under active development for five years - version 3.0 was released in December 2008, current latest stable version is 3.4.3 released in February 2015. The main reason to switch to Python 3 as the default implementation is that Python 2 is in maintenance mode, thus only bugfixes and security fixes are accepted upstream. Further reasons are mentioned in the Benefit to Fedora section. For this Change to be carried out successfully, it is necessary that the key packages in the Fedora software stack be ported to Python 3. These are parts of the minimal buildroot, the default package manager, programs present on the LiveCD etc.
== Scope ==
The main goal is switching to Python 3 as a default, in which state:
* DNF is the default package manager instead of Yum, which only works with Python 2
* Python 3 is the only Python implementation in the minimal buildroot (already done since F22)
* Python 3 is the only Python implementation on the Workstation LiveDVD
* Python 3 is the only Python implementation in minimal cloud image
* Python 3 is the only Python implementation in Atomic host
* It'd also be nice to have Python 3 as the only implementation on the Server LiveDVD, but it's not likely
Changes in packaging:
* Change definition of default python interpreter to python3.
* Change unversioned python macros to python3 (Possibly do that change in upstream rpm)
* All applications that use only a single python version MUST use python3 (unless they have a good reason not to do so).
Fate of /usr/bin/python:
* /usr/bin/python will still point to Python2 version of interpreter as suggested in PEP0394.
* There will be no /usr/bin/python on LiveDVD as python3 will became the only python interpreter shipped by default.
* Python (python2 version of the interpreter) package will be still available (via dnf install) and will provide /usr/bin/python.
Work in Fedora 23 Timeframe:
* Proposal owners:
- Continue the work from F21 and F22 timeframe
- Modify comps accordingly
- Apply the changes to Python packaging guidelines
* Other developers:
Introduce python3- subpackages where appropriate, build against Python 3 if the package supports it
* Release engineering:
Nothing
* Policies and guidelines:
TODO: changes in packaging
--
Jan Kuřík
7 years, 9 months
Fedora 22 for POWER is here!
by Peter Robinson
We are proud to announce the official release of Fedora 22 for POWER,
the community-driven and community-built operating system now
available in Cloud and Server editions.
If that's all you need to hear, jump over to Get Fedora to download
-- or for current users, run the FedUp upgrade tool.
* https://fedoraproject.org/wiki/PowerPC/F22/Installation
* https://fedoraproject.org/wiki/FedUp
In addition to the latest versions of all your favorite free and
open source software, Fedora 22 marks our second release with
distinctly-targeted offerings for cloud computing, and the server
room. Thanks to the hard work of developers, designers, packagers,
translators, testers, documentation writers, and everyone else,
we're incredibly confident in saying that this is our best and
most polished release yet.
Also with this release, we return to our traditional six-month
cadence -- we'll see you back here sometime around Halloween!
Highlights in the Fedora 22 release
===================================
Every Fedora release has its own character. If this release had a
human analogue, it'd be Fedora 21 after it'd been to college,
landed a good job, and kept its New Year's Resolution to go to the
gym on a regular basis. What we're saying is that Fedora 22 has
built on the foundation we laid with Fedora 21 and the work to
create distinct editions of Fedora focused on the desktop, server,
and cloud (respectively). It's not radically different, but there
are a fair amount of new features coupled with features we've
already introduced but have improved for Fedora 22.
Fedora Cloud
------------
The Fedora 22 Cloud edition has debuted for POWER in this release. In
it's first release there are base cloud images that should be of
interest to users and developers.
* Fedora cloud base edition for qcow2 and raw images.
Fedora Server
-------------
* Database Server Role -- The Fedora Server edition focuses on easy of
different server roles. Fedora 21 debuted with an Domain Controller
Role featuring FreeIPA. For this release, we've added a Database
Server role, built around PostgreSQL.
* Default to XFS filesystem -- The default file system type for
Fedora Server installs will be XFS running atop LVM for all
partitions except /boot. The /boot partition will remain a non-LVM,
ext4 partition due to technological limitations of the bootloader.
* Cockpit will be compatible between OS releases -- Cockpit is a
server manager that makes it easy to administer your GNU/Linux
servers via a web browser.
- Easy to use. Cockpit is perfect for new sysadmins, allowing
them to easily perform simple tasks such as storage
administration, inspecting journals and starting and stopping
services.
- No interference. Jumping between the terminal and the web
tool is no problem. A service started via Cockpit can be
stopped via the terminal. Likewise, if an error occurs in the
terminal, it can be seen in the Cockpit journal interface.
- Multi-server. You can monitor and administer several servers
at the same time.
Other changes of note
=====================
Faster and better dependency management with DNF
------------------------------------------------
With Fedora 22, we're introducing a major change under the hood.
Specifically, we're now using DNF and hawkey to manage packages.
DNF is much like the Yum software package manager (it's largely
command-line compatible), but re-written and re-engineered to
provide optimal performance and (along with Hawkey) provide a
strict API definition for plugins and extending projects. DNF also
makes use of the libsolv library initially pioneered by the
openSUSE Project to provide faster and better dependency
management.
It also boasts a better performance and memory footprint vs. Yum,
and is designed to have a cleaner codebase and be easier to
maintain.
If you're using the Fedora 22 Workstation edition, and managing
packages with the Software Application, odds are you won't notice a
difference. Server and Cloud users who fall back on Yum commands
will receive a reminder (courtesy of dnf-yum) that Yum is
deprecated and DNF is now the default package manager. DNF has been
in development for quite some time, so we're confident it's ready
for prime time. The classic Yum command line tool has been renamed
to yum-deprecated as a transitional step for tools still using it.
See Read The Docs for compatibility changes from Yum to DNF in
detail.
GNU Compiler Collection 5
-------------------------
Fedora 22 comes with GCC 5.1 as the primary compiler suite.
Downloads, upgrades, documentation, and common bugs
==================================================
You can start by downloading Fedora 22:
* https://fedoraproject.org/wiki/PowerPC/F22/Installation
If you are upgrading from a previous release of Fedora, refer to:
* http://fedoraproject.org/wiki/Upgrading
Fedora's FedUp utility enables an easy upgrade to Fedora 22 from
previous releases. See the FedUp page on the Fedora wiki for more
information:
* https://fedoraproject.org/wiki/FedUp
Documentation
-------------
Read the full release notes for Fedora 22, guides for several languages,
and learn about known bugs and how to report new ones:
* http://docs.fedoraproject.org/
Fedora 22 common bugs are documented at:
* http://fedoraproject.org/wiki/Common_F22_bugs
This page includes information on several known non-blocker bugs in
Fedora 22. Please be sure to read it before installing!
7 years, 9 months
F23 System Wide Change: Boost 1.59 Uplift
by Jan Kurik
= Proposed System Wide Change: Boost 1.59 Uplift =
https://fedoraproject.org/wiki/Changes/F23Boost159
Change owner(s): Jon Wakely <jwakely redhat com>
This change brings Boost 1.58.0 or later to Fedora 23. We generally aim to ship 1.59.0, as that seems likely to make it (hence the Change name), but 1.58.0 is out and available now.
== Detailed Description ==
The aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of all dependent packages. This has also always entailed yours truly assisting maintainers of client packages in decoding cryptic boostese seen in output from g++. Such care is to be expected this time around as well.
Boost 1.59 does not have firm schedule yet. I do not think there is even a provisional schedule at this point. We may have to package Boost 1.58 instead.
Here is the Fedora 22 Change, should you need it.
== Scope ==
Rebasing Boost has a fairly large impact on Fedora. For Fedora 20, the scope was: about 130 packages _must_ be rebuilt due to ABI breakage inherent in bumping Boost sonames. There were almost 250 client packages total. I expect these numbers to stay in the same ballpark for Fedora 23.
* Proposal owners:
** Build will be done with Boost.Build v2 (which is upstream-sanctioned way of building Boost)
** Request a "boost" build system tag (discussion) (take a look at the ticket #6093 for inspiration)
** Build boost into that tag (take a look at the build #606493 for inspiration)
** Post a request for rebuilds to fedora-devel (XXX link to fedora-devel message here)
** Work on rebuilding dependent packages in the tag.
** When most is done, re-tag all the packages to rawhide
** Watch fedora-devel and assist in rebuilding broken Boost clients (by fixing the client, or Boost).
* Other developers: Those who depend on Boost DSO's will have to rebuild their packages. Feature owners will alleviate some of this work as indicated above, and will assist those whose packages fail to build in debugging them.
* Release engineering: Side tag creation.
* Policies and guidelines: Apart from scope, this is business as usual, so no policies, no guidelines.
--
Jan Kuřík
7 years, 9 months
F23 Self Contained Change: Frappe Framework
by Jan Kurik
= Proposed Self Contained Change: Frappe Framework =
https://fedoraproject.org/wiki/Changes/frappe-framework
Change owner(s):
* William Moreno Reyes <williamjmorenor at fedoraproject.org>
* Eduardo Mayorga <mayorga at fedoraproject.org>
A full-stack web framework based on Python and Javascript to help you build powerful business apps and nifty extensions.
== Detailed Description ==
* Frappe is a Python and JavaScript framework.
* Frappe is the Framework on top ERPNext it is builded.
* Frappe has libraries and API for everything from authentication to reports.
* Frappe is built with the philosophy make it a "battries included" framework
== Scope ==
* Proposal owners:
* * Packaging: williamjmorenot at fedoraproject.org
* * Review and QA: mayorga at fedoraproject.org
* Other developers: not a System Wide Change
* Release engineering: not a System Wide Change
* Policies and guidelines: not a System Wide Change
* Trademark approval: not needed for this Change
--
Jan Kuřík
7 years, 9 months
F23 Self Contained Change: System Firmware Updates
by Jan Kurik
= Proposed Self Contained Change: System Firmware Updates =
https://fedoraproject.org/wiki/Changes/SystemFirmwareUpdates
Change owner(s):
* Peter Jones <pjones at fedoraproject dot org>
* Richard Hughes <richard at hughsie dot com>
This change is to add the ability to perform firmware updates on UEFI machines.
== Detailed Description ==
This adds the ability to perform updates of system firmware, as well as some peripheral firmware, on machines supporting the UEFI Capsule Update mechanism and UEFI 2.5's "ESRT" feature.
Right now this is generic support—the number of machines for which we actually have firmware updates available is very small, as the underlying technology is quite new—and it doesn't include any actual delivery mechanism for such firmware images. But if they're put at the right place for fwupd to notice them, and the system supports the right features, they'll show up as updates in gnome-software.
== Scope ==
* Proposal owners: Get fwupdate, fwupd, and a version of gnome-software that can use them into Fedora, maintain it in the future.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
7 years, 9 months
Re: Fedora.next PRD refresh
by Stephen Gallagher
On Tue, 2015-06-02 at 09:55 +0700, Truong Anh Tuan wrote:
> ----- Original Message -----
> > From: "Stephen Gallagher" <sgallagh(a)redhat.com>
> > To: "Server SIG" <server(a)lists.fedoraproject.org>,
> > desktop(a)lists.fedoraproject.org,
> > devel-announce(a)lists.fedoraproject.org,
> > cloud(a)lists.fedoraproject.org
> > Sent: Tuesday, June 2, 2015 2:03:44 AM
> > Subject: Fedora.next PRD refresh
>
> <snipped>
>
> > == Future PRD Refreshes ==
> > Starting at Flock 2016 (yes, *next* calendar year), each working
> > group
> > will have a workshop scheduled at Flock to go over its PRD and plan
> > for
> > the following year. Note: because Flock generally falls between
> > Alpha
> > and Beta of a Fedora release, all PRD planning is presumed to be a
> > directive for Fedora N+1 and N+2 at that time, not retroactively
> > applied to the current release.
> >
> > The workshops are expected to cover the majority of the update, and
> > then they will be brought back to the respective mailing lists for
> > further review before being due to the Council one month after
> > Flock
> > concludes.
>
> +1. This is a good idea and it is important to push products toward
> on
> the right way.
> I am just curious why it would not be held from this year? because of
> time constrains?
>
We had already communicated to several groups that we wanted to refresh
it before Alpha this cycle (Cloud in particular had moved far from its
original PRD). We decided to keep that plan and adjust the future.
7 years, 9 months