Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Fedora.next - the Server Product

Fedora.next - the Server Product

Presented at FOSSASIA 2014


March 01, 2014

More Decks by Anh Tuan TRUONG

Other Decks in Technology


  1. The Server Product Truong Anh Tuan Presented by Member of

    FAmSCo and Fedora Server WG License statement goes here. See https://fedoraproject.org/wiki/Licensing#Content_Licenses for acceptable licenses. Fedora.next
  2. Today's Topics 1. Product Requirements a. Vision and Mission b.

    Market Opportunity c. Product Objectives d. Personas and Primary Use Cases 2. Governance a. Membership b. Making Decisions 3. Product Lifecycle
  3. Product Requirements

  4. Vision Fedora Server is the preferred [community] platform for system

    administrators and developers seeking to deploy applications and services that use the latest technology on a stable foundation with effective resource utilization.
  5. Mission Fedora Server is a common base platform with "featured

    server roles" built on top of it. We commit to produce, test, and distribute these server roles.
  6. Market Opportunity The server operating system market is mature, but

    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
  7. Product Objectives Fedora Server consists of a release that can

    be used at various scales: A single server that runs an application or service A platform for an entire data center The platform to deploy an Infrastructure-as-a- Service (IaaS) private cloud
  8. Product Objectives (cont.) Fedora Server is meant to be used

    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.
  9. Product Objectives (cont.) Secondary objectives: More testing of Fedora images

    with additional bug reports Better feedback about product direction and potential improvements More patches and contributions
  10. Personas System Administrator DevOps Engineer/Administrator Traditional Application Developer Junior Enterprise

    System Administrator Decision Maker
  11. Use Cases The user must be able to easily deploy

    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
  12. Use Cases (cont.) Users must be able to rapidly re-deploy

    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
  13. Featured Server Roles An installable component of Fedora Server that

    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
  14. Governance

  15. Membership Nine voting members: Stephen Gallagher (the initial FESCo Liaison),

    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
  16. Making Decisions On mailing list or IRC meetings Work on

    consensus; only vote on things where it’s clear people aren’t going to be convinced to agree Five positive votes will be required for a proposal to be accepted
  17. Product Lifecycle

  18. Lifecycle Proposal Lifecycle of 18 months Start with Fedora Server

    1.0 (Fedora Server 21) Base Design built as F21, F22 and F23 following similar present mechanisms; Fedora Server built atop (delayed < 1 month)
  19. Lifecycle Diagram

  20. Resources Mailing list: [email protected] IRC: #fedora-server on freenode Blog: http://fedoraserver-wgblog.rhcloud.com/

    Weekly meetings: on Tuesdays at 11 AM ET in #fedora-meeting-1 Wiki: https://fedoraproject.org/wiki/Server
  21. Questions? License statement goes here. See https://fedoraproject.org/wiki/Licensing#Content_Licenses for acceptable licenses.

    [email protected] Contact: