Fedora Server Use Cases Prioritization

Marcela Maslanova mmaslano at redhat.com
Fri Dec 20 09:46:43 UTC 2013

----- Original Message -----
> From: "Stephen Gallagher" <sgallagh at redhat.com>
> To: server at lists.fedoraproject.org
> Sent: Thursday, December 19, 2013 6:12:28 PM
> Subject: Fedora Server Use Cases Prioritization
> Hash: SHA1
> Today at the overflow meeting, we came up with nine use cases that we
> believe we want to focus on with the Fedora Server product. We agreed
> that we want to list these in priority order, but I want to open this
> up to the wider server community so we can order these properly.
> Please keep in mind that these use-cases are high-level and should not
> be construed to be exhaustive or exclusive. There are several items in
> this list that we need to coordinate with other working groups as well.
> Please respond with your recommendations for the ordering of this list
> (assuming that all entries remain as they are) so we can get a sense
> of the relative importance of these items.
> 1) The user must be able to easily deploy and configure any supported
> Fedora Server role. (Examples may include: FreeIPA Domain Controller,
> BIND DNS, DHCP, Database server, iSCSI target, File/Storage server.)
> 2) The user must be able to query, monitor, configure and manage a
> Fedora Server remotely using stable and consistent public interfaces.
> 3) The user must be able to simply enroll the Fedora Server into a
> FreeIPA or Active Directory domain.
> 4) Users must be able to control and contain the resources consumed by
> services running on the system.
> 5) Users must be able to rapidly re-deploy services in accordance with
> their DevOps practices using Fedora Server.
> 6) ASK SOFTWARE COLLECTIONS WG The user must be able to easily deploy
> and configure applications to supported high-value frameworks.
> (Example frameworks: JBoss, Ruby on Rails, Django, Turbogears,
> Node.js, PHP.)
We didn't speak about easy deployment and configuration. We were discussing
possibility of automatic packaging or updates of these packages.
Do you have any specific goals for Env and Stack WG on your mind? Which
technologies to use etc.


More information about the server mailing list