Fedora Server Use Cases Prioritization
sgallagh at redhat.com
Fri Dec 20 12:47:23 UTC 2013
-----BEGIN PGP SIGNED MESSAGE-----
On 12/20/2013 04:46 AM, Marcela Maslanova wrote:
> ----- 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
>> -----BEGIN PGP SIGNED MESSAGE----- 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
>> 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.
Our definition of "easy" is intentionally vague here. I'm not sure on
which side of the fence we need to do the simple configuration and
On the one hand, the Fedora Workstation will want to be able to
quickly and easily set up an application to work on. This might just
be a simple package/SCL like we have today. On the Fedora Server side,
we're going to want to be able to take an application built by Fedora
Workstation and deploy it (possibly in a continuous deployment
scenario). That might mean doing something more like OpenShift
cartridges, where the configuration is part of the definition of the
We agreed in the meeting that before we made that a formal piece of
the Server WG, we would consult with the Env/Stacks group on what
options we could have to implement it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the env-and-stacks