constantly evolving System administrators find it more to devote large amounts of time to dealing with individual technologies, specifically: Detailed understanding of the underlying technology is often not feasible Frequently spending significant amounts of time migrating from one Fedora release to another
for the following purposes: An operating platform for important infrastructure tasks (DNS, DHCP, etc.) and server applications (file/storage server, database server, etc.) A platform for deploying Infrastructure-as-a- Service systems for best deployment of Fedora Cloud images. Infrastructure to allow efficiently managing many servers as a single unit.
and configure any supported Fedora Server role The user must be able to query, monitor, configure and manage a Fedora Server remotely The user must be able to simply enroll the Fedora Server into a FreeIPA or AD domain Users must be able to control and contain the resources consumed by services running on the system
services in accordance with their DevOps practices Users must be able to create, manipulate and terminate large numbers of containers The user must be able to install and manage Fedora Server in a headless mode where the display framework is inactive
provides a well-integrated service on top of the Fedora Server platform. These prepared roles simplify deployment and management of a service compared to setting up an upstream server from scratch Their use is recommended but optional Existing users of upstream servers based on Fedora RPMs will not be impeded
David Strauss, Jim Perrin, Adam Williamson, Kevin Fenzi, Miloslav Trmač, Máirín Duffy, Simo Sorce and Truong Anh Tuan Each voting member will confirm their continued membership every six months Encourage involvement from all parts of the Fedora Project