From Fedora Project Wiki
< Server
m (adding simo comments about db from https://lists.fedoraproject.org/pipermail/server/2013-October/000226.html) |
m (add simo question about frameworks https://lists.fedoraproject.org/pipermail/server/2013-October/000226.html) |
||
| Line 19: | Line 19: | ||
# Provide simple setup of a file-server (on par with Windows). | # Provide simple setup of a file-server (on par with Windows). | ||
# Platform for deploying web applications with high-value frameworks. | # Platform for deploying web applications with high-value frameworks. | ||
#* Ruby on Rails | #* Frameworks: | ||
#* Django | #** Ruby on Rails | ||
#* Turbogears | #** Django | ||
#* Node.js | #** Turbogears | ||
# Make Fedora the best platform to deploy JBoss applications. | #** Node.js | ||
#* (Are we going to do this via Software Collections? The main issue I see with these is that various apps requires at times, conflicting versions of the same base framework/language. --simo ) | |||
# Make Fedora the best platform to deploy JBoss applications. | |||
# Come up with standardized mechanisms for centralized monitoring | # Come up with standardized mechanisms for centralized monitoring | ||
# Come up with standardized mechanisms for centralized configuration and management | # Come up with standardized mechanisms for centralized configuration and management | ||
Revision as of 16:24, 31 October 2013
This is a draft document!
This document is a work-in-progress draft and has not been agreed upon yet.
This document is a work-in-progress draft and has not been agreed upon yet.
Discussion
- Users of Fedora server will be able to install - at their option - a select set of software with graphical interfaces, and they will be able to successfully use these graphical interfaces via trusted X-forwarding (ssh -Y). [1]
- The set of GUI software that should be installable and usable via trusted X-forwarding on Fedora Server will be defined by the Server working group. [2]
- Draft list of GUI software to be supported.
- Provide a platform for acting as a node in an OpenStack rack.
- Provide a platform and simple setup for certain infrastructure services, e.g.
- FreeIPA Domain Controller
- BIND DNS
- DHCP
- Database server (both free and commercial).
- (Should Fedora care about proprietary ones? We shouldn't be hostile, but neither cater for them too much, most of the contributors wouldn't have the means to do it anyway, and proprietary vendors can better install on RHEL and interact with RH. --simo)
- Samba Ad Domain Controller
- (that is mostly blocked due to upstream work, and I am not sure we can do much here, beyond encouraging upstream. --simo)
- Provide simple setup of a file-server (on par with Windows).
- Platform for deploying web applications with high-value frameworks.
- Frameworks:
- Ruby on Rails
- Django
- Turbogears
- Node.js
- (Are we going to do this via Software Collections? The main issue I see with these is that various apps requires at times, conflicting versions of the same base framework/language. --simo )
- Frameworks:
- Make Fedora the best platform to deploy JBoss applications.
- Come up with standardized mechanisms for centralized monitoring
- Come up with standardized mechanisms for centralized configuration and management
- Simple enrollment into FreeIPA and Active Directory domains
- Provide the best platform for secure application deployment
- Isolation of OS from applications
- Isolation of applications from each other
- Isolation of application users from each other
- Management of application resource consumption
- Simplify management and deployment.[1]
- Deliver the world's best leading edge DevOps platform.