= Proposed Self Contained Change: Anaconda LVM RAID =
https://fedoraproject.org/wiki/Changes/AnacondaLVMRAID
Change owner(s):
* Vratislav Podzimek (Anaconda/Blivet) <vpodzime AT redhat DOT com>
* Heinz Mauelshagen (LVM) <heinzm AT redhat DOT com>
Use LVM RAID instead of LVM of top of MD RAID in the Anaconda installer.
== Detailed Description ==
In the current situation when a user chooses LVM (or Thin LVM)
partitioning in the Custom Spoke and then sets RAID level for the VG
Anaconda (and Blivet) create an MD RAID device which is used as a PV
for the VG. With this change we are going to use LVM RAID directly
instead. That means that all the LVs in that VG will be RAID LVs with
the specified RAID level. LVM RAID provides same functionality as MD
RAID (it shares the same kernel code) with better flexibility and
additional features expected in future.
== Scope ==
* Proposal owners:
-- Blivet developers: Support creation of LVM RAID in a similar way as
LVM on top of MD RAID. (Creation of RAID LVs is already supported.)
-- Anaconda developers: Use the new way to create LVM RAID instead of
creating LVM on top of MD RAID.
-- LVM developers: LVM RAID already has all features required by this change.
* Other developers:
N/A (not a System Wide Change)
* Release engineering:
* List of deliverables:
N/A (not a System Wide Change)
* Policies and guidelines:
* Trademark approval:
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= System Wide Change: GNOME 3.24 =
https://fedoraproject.org/wiki/Changes/GNOME3.24
Change owner(s):
* Kalev Lember <klember AT redhat DOT com>
Update GNOME to the latest upstream release, 3.24
== Detailed Description ==
Tentative new features for 3.24 include:
* Updated System Settings panels: User Accounts, Printer, Online Accounts
* Tag Editing in GNOME Music
* ownCloud integration in GNOME Music
* Sharing Framework
* Photo Import
* Passwords and Keys Application
* Revamped Header Bar and Bookmarks in Web
* Browse as root in Files
More details are available in
https://wiki.gnome.org/ReleasePlanning/FeaturePlans
== Scope ==
Proposal owners:
* Keep existing GNOME packages updated
* Follow upstream module changes
* Package new applications and new dependencies of existing GNOME
packages for GNOME 3.24
Other developers: N/A
Release engineering: N/A
List of deliverables: N/A
Policies and guidelines: N/A
Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Greetings,
This e-mail is intended to inform you about the upcoming Bugzilla changes
happening on 2017-02-21 (Rawhide bug rebase) and what you need to do,
if anything.
We will be automatically changing the version for most rawhide bugs to
Fedora 26.
This will result in regular bugs reported against rawhide during the Fedora 26
development cycle being changed to version ‘26' instead of their current
assignment, ‘rawhide’. This is to align with the branching of Fedora 26 from
rawhide and to more accurately tell where in the lineage of releases the bug was
last reported.
Note that this procedure does not apply to bugs that are open for the ‘Package
Review’ or 'kernel' components or bugs that have the ''FutureFeature''
or ''Tracking'' keywords
set. These will stay open as rawhide bugs indefinitely.
If you do not want your bugs changed to version ‘26‘, add the ''FutureFeature''
keyword. If you need help changing a large amount of bugs manually, we’d be glad
to help.
The process was re-approved by FESCo https://pagure.io/fesco/issue/1096 .
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change: SSSD fast cache for local users =
https://fedoraproject.org/wiki/Changes/SSSDCacheForLocalUsers
Change owner(s):
* Stephen Gallagher <sgallagh AT redhat DOT com>
* Jakub Hrozek <jhrozek AT redhat DOT com>
Enable resolving all users through the sss NSS modules for better performance.
== Detailed Description ==
SSSD ships with a very fast memory cache for a couple of releases now.
However, using this cache conflicts with nscd's caching and nscd has
been disabled by default. That degrades performance, because every
user or group lookup must open the local files.
This change proposes leveraging a new "files" provider SSSD will ship
in the next version in order to resolve also users from the local
files. That way, the "sss" NSS module can be configured before the
files module in nsswitch.conf and the system could leverage sss_nss
caching for both local and remote users.
The upstream design of the files provider can be found at:
https://fedorahosted.org/sssd/wiki/DesignDocs/FilesProvider
Below is a mini-FAQ that lists the most common questions we've received so far:
Q: Does SSSD take over /etc/passwd and /etc/files?
A: No. SSSD just monitors them with inotify and copies the records
into its cache.
Q: Does SSSD need to be running all the time now? What if it crashes?
A: SSSD needs to be running in order to benefit from this
functionality. However, the nss_sss module is built in such a way that
even if sssd is not running, nss_sss should fail over to nss_files
pretty quickly (we'll quantify "pretty quickly" in a more scientific
fashion soon)
Q: Do I need to configure SSSD now?
A: No, we'll ship a default configuration.
== Scope ==
* Proposal owners:
Jakub Hrozek and Stephen Gallagher work on the design and coding
* Other developers:
The SSSD upstream will participate in code review of the change
* Release engineering:
None required
* Policies and guidelines:
None needed
* Trademark approval:
None needed
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Hi everyone!
The submission deadline for System Wide Changes of Fedora 26 [1] is
today (January 31st). Alpha release of Fedora 26 is planned then on
March 14th.
As the deadline applies for System Wide Changes it is always good to
have most of Self Contained Changes proposed as well. In case you'll
need any help with your Change proposals, feel free to contact me.
[1] https://fedoraproject.org/wiki/Releases/26/Schedule
Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= System Wide Change: Kerberos KCM credential cache by default =
https://fedoraproject.org/wiki/Changes/KerberosKCMCache
Change owner(s):
* Jakub Hrozek <jhrozek AT redhat DOT com>
Default to a new Kerberos credential cache type called KCM which is
better suited for containerized environments and provides a better
user experience in the general case as well.
== Detailed Description ==
Over time, Fedora used different credential cache types to store
Kerberos credentials - going from a simple file-based storage (FILE:)
to a directory (DIR:) and most recently a kernel-keyring based cache
(KEYRING:).
Each of these caches has its own set of advantages and disadvantages.
The FILE ccache is very widely supported, but does not allow multiple
primary caches in a collection. The DIR cache does, but creating and
managing the directories including proper access control can be
tricky. The KEYRING cache is not well suited for cases where multiple
semi-isolated environments might share the same kernel. Managing
credential caches' life cycle is not well solved in neither of these
cache types automatically, only with the help of a daemon like SSSD.
The scope of this change is to introduce a new Kerberos credential
cache type called KCM and switch to using it by default.
With KCM, the Kerberos caches are not stored in a "passive" store, but
managed by a daemon. In this setup, the Kerberos library (typically
used through an application, like for example, kinit) is a "KCM
client" and the daemon is being referred to as a "KCM server". The KCM
server will be provided as a socket-activated service of the SSSD
deamon.
== Scope ==
* Proposal owners:
SSSD developers will implement a KCM server. The krb5-libs package
will then switch its default from KEYRING to KCM. The libkrb5 package
will require the sssd-kcm subpackage and enable its socket so that the
KCM server is socket activated when needed. Please note that the KCM
server only listens on a local UNIX socket, not over the network.
* Other developers: None required
* Release engineering: None required
* List of deliverables: None affected
* Policies and guidelines: None required
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change: Container Minimal Image =
https://fedoraproject.org/wiki/Changes/ContainerMinimalImage
Change owner(s):
* Dusty Mabe <dusty AT dustymabe DOT com>
Produce a new container image that contains as little as possible, but
also still provides the ability to install packages from dnf
repositories.
== Detailed Description ==
As a user of Fedora I'd like to build containers based on an image
that is a little more lightweight than the current base container
image that is produced in Fedora. We have a proof of concept kickstart
[1] that will create such an image. It is a work in progress.
[1] https://pagure.io/fedora-kickstarts/pull-request/120
== Scope ==
* Proposal owners:
Implementation of this Change
* Other developers:
N/A (not a System Wide Change)
* Release engineering:
N/A (not a System Wide Change)
* List of deliverables:
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
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= System Wide Change: Python Classroom Lab =
https://fedoraproject.org/wiki/Changes/PythonClassroomLab
Change owner(s):
* Miro Hrončok <mhroncok AT redhat DOT com>
* SIGs/Python <python-devel(a)lists.fedoraproject.org>
A new Python Classroom Lab will be created in 3 variants: Workstation
based, Docker based and Vagrant based. It's an important step for our
Fedora Loves Python initiative. The main audience are Python teachers
and workshop instructors.
== Detailed Description ==
A new comps packages group with Python development tools will be
created and a new Lab (or Spin) for teaching Python or Python related
topics will be available from labs.fedoraproject.org as well as from
the Docker Hub and Vagrant Atlas.
A work in progress for the lab is available on GitHub.
The Lab will contain:
* Python 3.6 including the python3-devel package
* Python 2.7 including the python2-devel package
* PyPy 3
* tox
* virtualenv
* IPython console for both Python 2 and 3
* Jupyter Notebook with Python 2 and 3 kernels (if this gets into
Fedora in time)
* offline documentation for Python 2 and 3
* basic toolchain for building C and C++ extensions and valgrind
* git
* nano, vim, ssh client, curl, wget
* devel packages for commonly used dependencies of packages on the
Python Package Index
* * libxml2-devel
* * libyaml-devel
...
The Workstation based lab will also contain:
* Basic GNOME
* Terminal emulator
* Text editor
* PDF reader
* Web browser
* Image viewer
* ...and possibly other utilities
But it will not include multimedia and virtualization support, office
suite, e-mail client.
== Scope ==
Proposal owners:
* create the comps group
* create kickstarts for live and vagrant variants
* create a layer for docker
Other developers:
* Design team: Create an image for labs.fedoraproject.org
* Websites team: Add the new Lab to labs.fedoraproject.org
Release engineering:
List of deliverables:
* Labs/i386/iso/Fedora-Python-Classroom-Live-i386-_RELEASE_MILESTONE_.iso
* Labs/x86_64/iso/Fedora-Python-Classroom-Live-x86_64-_RELEASE_MILESTONE_.iso
* Labs/armhfp/images/Fedora-Python-Classroom-armhfp-_RELEASE_MILESTONE_-sda.raw.xz
* Labs/i386/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.i386.vagrant-libvirt.box
* Labs/i386/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.i386.vagrant-virtualbox.box
* Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.x86_64.vagrant-libvirt.box
* Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-_RELEASE_MILESTONE_.x86_64.vagrant-virtualbox.box
* docker images via Fedora Docker Layered image build service
Policies and guidelines: nothing
Trademark approval: waiting
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change: NetworkManager 1.8 =
https://fedoraproject.org/wiki/Changes/NetworkManager18
Change owner(s):
* Lubomir Rintel <lkundrak AT v3 DOT sk>
Update to NetworkManager to version 1.8.
== Detailed Description ==
NetworkManager 1.8 will include significant changes and improvements:
* MACsec support
* Proxy support including autoconfiguration
* Integration with systemd-resolved
* IPv6 connection sharing (prefix delegation to hotspots)
* Dropped hard dependency on dhclient, ppp
* VPN plugins no longer depend on GUI
== Scope ==
* Proposal owners:
Update NetworkManager, connection editor and VPN plugin packages.
* Other developers:
N/A (not needed for this Change)
* Release engineering:
N/A (not needed for this Change)
* Policies and guidelines:
N/A (not needed for this Change)
* Trademark approval:
N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Planned Outage: Server reboots / Firmware updates - 2017-01-25 21:00 UTC
There will be an outage starting at 2017-01-25 21:00 UTC, which will
last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:
date -d '2017-01-25 21:00 UTC'
Reason for outage:
We will be rebooting servers into the latest kernel and updated package
sets, as well and performing some firmware updates on selected servers.
No one service should be down very long, but all services may go up and
down in the outage window as various servers are rebooted.
Affected Services:
All services may be up or down during the outage window, with the
exception of cloud services (anything with .cloud.fedoraproject.org or
fedorainfracloud.org in the name)
Contact Information:
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/5715
Please join #fedora-admin or #fedora-noc on irc.freenode.net or add
comments to the ticket for this outage above.