SIGs/Server

Fedora Server SIG

Welcome on the home of Fedora Server SIG. We are a group which would like to use Fedora as a server on bare metal or in virtual environment that may or may not provide graphical capabilities. Our focus is mainly on Fedora server components, and features like networking, head-less support, or iSCSI. You can object that there are no Fedora server users, but they are there - either running Fedora itself or distributions based on Fedora such as Red Hat Enterprise Linux or CentOS.

Rationale

Fedora can be deployed in many environments and for many purposes. However, not every typical deployment is represented by a group that focuses on needs of such particular deployment. One of typical deployments (Desktop) is covered by Desktop Team. We would like to cover typical server deployment, which raises few challenges and is represented by a unique set of requirements. Our goals are based on such requirements and current state of Fedora and are listed in the next section.

In an ideal world requirements of all deployments scenarios complement each other, but in the real life there are conflicts. Our main goal is to find a technical solution - by maintaining compatibility, with possibility to enable/disable certain features, etc. We think that the main problem is the lack of communication between groups and we would like to focus from the very beginning on improving it. The second goal is to help separate current and emerging desktop oriented applications from the base system and to help their developers to correctly integrate applications' features into base system.

Participants

• Dan Horák
• Tomáš Mráz (tmraz)
• Karel Zak (kzak)
• Adam Tkac (atkac)
• Daniel Mach (dmach)
• Milan Broz (mbroz)
• Radek Vokal
• Jon Ciesla
• Doug Ledford (dledford)
• Smooge (smooge)
• Chris Weyl
• Paul Howarth
• Dmitry Butskoy
• Dominik Mierzejewski
• DavidKovalský (dkovalsk)
• Jeroen van Meeuwen
• Felix Kaechele
• Marcela Mašláňová
• Joerg Stephan

...

Our infrastructure

mailing list - fedora-server-list

IRC meetings - #fedora-server (time to be decided)

tracking bug - FedoraServerTracker

Our goals

• improve cross-team communication between people around low-level system components and people around desktop,
• maintain the standard network configuration layer (/etc/sysconfig/network-scripts) as a longterm compatibility solution (move into a standalone package)
• create a spin targeted at head-less servers, NAS and similar devices (running on both physical and virtual hardware),
• collaborate with the installer team so we can enable different spins, desktop versus server builds
• reduce the dependency on desktop packages to lower the attack surface of the server (work on more fine-graded dependencies),
• work on CLI equivalents of misc GUI tools (eg. write new frontends for existing backends),
• help to better integrate new features into existing infrastructure
• serve as a community liason for Red Hat partners
• create lightweight installer similar to creating buildroots by mock
• offer minimal installation path for head-less servers or virtual machines
• provide support for systems with large storage devices and with thousands of volumes (physical/logical) and various multipath configurations
• implement "report-app-crashes-to-bugzilla" feature on a system level and allow desktop plugins to connect there
• encourage community members to (co-)maintain packages containing server software
• ...

Work Areas

Installer

• work with the anaconda team to keep anaconda suitable for server installs (text mode, kickstarts, ...)
• (sharkcz) create a lightweight installer/bootstraper

Server services

• bring more server packages into Fedora
  • (sharkcz) Tryton - ERP - imported, now working on the application modules
• encourage creation of EPEL branches for existing packages
• overview of available servers

Kernel

• everything about the kernel side of servers

Admins corner

• place for administration and monitoring technologies available in Fedora
  • Customizing installation trees
    • Inclusion of customized, updated kernels, hardware drivers
    • Inclusion of rebuilt stage2.img or install.img images with customized or updated software
    • Inclusion of kickstarts for automated installations
    • Slipstreaming the necessary updated packages and/or custom packages in the payload
    • Integration with provisioning systems
  • Provisioning for real and virtual systems
    • Integration with compose tools
    • Cobbler
    • Slipstreaming Configuration Management utilities
  • Configuration Management
    • CFEngine, Puppet, Augeas, Func
  • Monitoring
    • Nagios, Zabbix, ZenOS, Monit
    • Integration with Configuration Management utilities
• collects pointers to how-tos and other docs useful for administrators
• work on the TUI counterparts of GUI system-config-* tools, should go in hand with the backend/frontend separation

Security

• improve/monitor the security standards for current server software
• help the desktop developers with the security aspects of their work

Network

• let initscripts and NetworkManager play nicely together, move network support from initscripts into a separate package
• add more interface types to NetworkManager

QA

• testing

Random questions

• why do we need plymouth to install new kernel?
• should be desktop paradigm of a user session used on servers?
• should exist a lightweight network configuration mechanism for servers or eth0-only workstations?

FAQ

Q: does more server orientation mean an extended lifetime too?
A: no, extended lifetime is covered by the derivates like RHEL, CentOS, etc.