|
|
| Line 1: |
Line 1: |
| {{admon/warning | This is a draft proposal. | This proposal is currently being discussed on the [https://lists.fedoraproject.org/pipermail/server/2013-November/000369.html Thoughts on Fedora Server lifecycle] thread on the server mailing list. | | {{admon/warning | This is a draft proposal. | The proposal that was here has been withdrawn at the request of it's writer as stated clearly in this https://lists.fedoraproject.org/pipermail/server/2013-December/000656.html thread on the server mailing list. |
| }} | | }} |
|
| |
| = Purpose =
| |
|
| |
| We need to define "server roles" and the criteria for that "role," then look at the server applications or application stacks which exist in the project and are applicable for that role and select which one we choose as that role. ([https://lists.fedoraproject.org/pipermail/server/2013-November/000405.html]) We should produce the best out of the box optimized ks/playbooks files for any given server product, reducing the steps necessary to configure/tweak/optimize/scale/secure for administrator to perform and get started. ([https://lists.fedoraproject.org/pipermail/server/2013-November/000413.html])
| |
|
| |
| We will pick somewhere between one and three initial roles to focus on for F21. That's achievable and allows us to direct our energies. ([https://lists.fedoraproject.org/pipermail/server/2013-November/000411.html])
| |
|
| |
| = Requirements for First-Tier Applications/Services Supporting a Server Role =
| |
|
| |
| We'll declare some services to be "first-tier". In other words: here are the set of things that we (The Fedora Project) asserts are functional, useful and ready for you to play with.
| |
|
| |
| We should always allow access to the greater universe of packages and services, but in order to be promoted to "first-tier", they would have
| |
| to meet some set of guidelines that we lay down (i.e. "must provide an Ansible playbook to set them up", or "must be capable of scaling in the following ways", etc.) ([https://lists.fedoraproject.org/pipermail/server/2013-November/000411.html])
| |
|
| |
| = Proposed Server Roles =
| |
|
| |
| === Application Services Server Role ===
| |
| Application Server Role enables you to create an integrated environment for deploying and running custom, server-based business applications.
| |
|
| |
| * WildFly - links to PRD?
| |
|
| |
| === Backup Services Server Role ===
| |
| Backup Services Server Role enables you to take and manage backup, recovery, and verification of computer data across a network of computers of different kinds.
| |
|
| |
| * BareOS - links to PRD?
| |
|
| |
| === Basic LAMP stack Server ===
| |
|
| |
| installs base + httpd + mariadb + php ([https://lists.fedoraproject.org/pipermail/server/2013-November/000416.html])
| |
|
| |
| === Cloud Services Server Role ===
| |
| Cloud Services Server Role enables you to build private, public and hybrid cloud computing environments.
| |
|
| |
| * Eucalyptus - links to PRD?
| |
| * Openstack - links to PRD?
| |
|
| |
| === Container Services Server Role ===
| |
|
| |
| The Container Server Role enables you to create a containerized server computing environment to improve the efficiency of your computing resources by utilizing more of your hardware resources.
| |
|
| |
| * Docker - link to PRD?
| |
| * Libvirt-lxc - link to PRD?
| |
| * Systemd-nspawn - link to PRD?
| |
|
| |
| === Database Services Server Role ===
| |
| Database Services Server Role enables you to run database management system in your infrastructure.
| |
|
| |
| * MariaDB - links to PRD?
| |
| * PostgreSQL - links to PRD?
| |
|
| |
| === Deployment Services Server Role ===
| |
| Deployment Services Server Role enables you to remotely deploy and update linux hosts over the network.
| |
|
| |
| * Katello - links to PRD?
| |
|
| |
| === Domain Controller ===
| |
|
| |
| installs FreeIPA and its deps ([https://lists.fedoraproject.org/pipermail/server/2013-November/000417.html])
| |
|
| |
| === Failover Clustering Services Server Role ===
| |
| Failover Clustering Services Server Role enables you to create a group of independent computers that work together to increase the availability of applications and services.
| |
|
| |
| * Corosync - links to PRD?
| |
|
| |
| === File and Storage Services Server Role ===
| |
| File and Storage Services Server Role enables you to create and manage network-attached storage file system.
| |
|
| |
| installs both NFS and Samba and makes them easy to configure ([https://lists.fedoraproject.org/pipermail/server/2013-November/000417.html])
| |
|
| |
| * GlusterFS - links to PRD?
| |
| * iSCSI - links to PRD?
| |
| * NFSv4 - links to PRD?
| |
|
| |
| === High Availability and Load Balancing Services Server Role ===
| |
| High Availability and Load Balancing Services Server Role enables you to load balances network traffic as well as adding additional servers as the load increases.
| |
|
| |
| * HAProxy - links to PRD?
| |
| * LVS - links to PRD?
| |
| * Corosync - links to PRD?
| |
|
| |
| === High Performance Services Server Role ===
| |
| High Performance Services Server Role enables you to run high-performance computing.
| |
|
| |
| * I guess what OSGDC recommends and links to PRD?
| |
|
| |
| === Lightweight Directory Services Server Role ===
| |
| Lightweight Directory Services Server Role enables you to provide flexible support for directory-enabled applications.
| |
|
| |
| * 389ds - links to PRD?
| |
| * Samba4 AD - links to PRD?
| |
|
| |
| === Media Streaming Services Server Role ===
| |
| Media Streaming Services Server Role enables you to stream live audio/video media content over networks.
| |
|
| |
| * Flumotion - links to PRD?
| |
| * Erlyvideo - links to PRD?
| |
|
| |
| === Network Services Server Role ===
| |
|
| |
| Network Services Server Role enables you to deploy network services in your infrastructure.
| |
|
| |
| * Tftp - links to PRD?
| |
| * ISC Bind - links to PRD?
| |
| * ISC DHCP - links to PRD?
| |
|
| |
| === OpenStack server ===
| |
|
| |
| installs openstack ([https://lists.fedoraproject.org/pipermail/server/2013-November/000416.html])
| |
|
| |
| === Telephony Services Server Role ===
| |
| Telephony Services Server Role enables you to telephony switching and private branch exchange service in your network.
| |
|
| |
| * Asterisk - links to PRD?
| |
|
| |
| === Virtualization Services Server Role ===
| |
| The virtualization Server Role enables you to create a virtualized server computing environment to improve the efficiency of your computing resources by utilizing more of your hardware resources.
| |
|
| |
| * libvirt - link to PRD?
| |
|
| |
| === Web Directory Services Server Role ===
| |
| Web Directory Services enables you to share information with users on the internal or internet.
| |
|
| |
| * httpd - links to PRD?
| |
| * nginx - links to PRD?
| |
