From Fedora Project Wiki
No edit summary
No edit summary
Line 17: Line 17:


== Benefit to Fedora ==
== Benefit to Fedora ==
 
* Security - lower the attack surface by installing only necessary packages
* Security - lower the attack surface by installing only necessary packages
* Performance - faster installation and less running services
* Performance - faster installation and less running services
* Storage - installation is less than 500MB
* Storage - installation is less than 500MB
* Package dependencies - package dependencies are regularly watched
* Package dependencies - package dependencies are regularly watched
* Fedora on servers - encourage users to use Fedora on server and support other distributions based on Fedora like Red Hat Enterprise Linux or CentOS
 
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->


== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
* Regularly perform installations during Fedora cycle and whatch for:
** disk usage
** packages dependencies
** running services
** SUID/SGID binaries
* Push new package profile into anaconda. This might require support from release engineering and anaconda stuff.


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
There is no need for special hardware to test this feature.  
 
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.


A good "how to test" should answer these four questions:
You can use bare metal or virtual environment for installation. Since there is no anaconda option yet, use this kickstart. The kickstart package set covers the @core group plus minimal number of extra packages. The kickstart file includes some security tweaks that are not mandatory for this feature.


0. What special hardware / data / etc. is needed (if any)?
What are the expected result?
1. How do I prepare my system to test this feature? What packages
* Disk usage of "/" mount point is less than 500MB
need to be installed, config files edited, etc.?
* Package list is subset of following package list
2. What specific actions do I perform to check that the feature is
* List of running services is subset of following list of services
working like it's supposed to?
* List of SUID binaries is subset of following list of SUID binaries
3. What are the expected results of those actions?
* List of SGID binaries is subset of following list of SGID binaries
-->


== User Experience ==
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Users will have have several options (anaconda/kickstart) to perform minimal platform installation. Their installations will be finished quickly. There will be minimal number of packages after they are ready with customizations. The whole system will be less vulnerable by attack.


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
* anaconda
* comps


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
This feature is not critical. Even if the criteria in test section are not exactly met we can live with that and improve it later. I don't expect any problems with anaconda and comps, but if there are any, we can abandon this way and provide at least the kickstart file in some other package.


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
There is no need for documentation on this feature. I'm gonna provide all the details on this page.
*
 
=== Filed Bugs ===
* https://bugzilla.redhat.com/show_bug.cgi?id=483018
* https://bugzilla.redhat.com/show_bug.cgi?id=483019
* https://bugzilla.redhat.com/show_bug.cgi?id=482899
* https://bugzilla.redhat.com/show_bug.cgi?id=480014


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
* ToDo!


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 
* Similar approach https://fedoraproject.org/wiki/SIGs/Server


[[Category:FeaturePageIncomplete]]
[[Category:FeaturePageIncomplete]]

Revision as of 15:58, 16 February 2009

Features/MinimalPlatform

Summary

Minimal platform will enable user to perform tiny installation. This installation is later used to create minimalistic server or desktop appliance.

Owner

Current status

  • Targeted release: Fedora 41
  • Last updated: (February 13 2009)
  • Percentage of completion: 50%

Detailed Description

The goal of the feature is to provide anaconda option to perform this kind of tiny installation. It would be also very nice to have a kickstart available somewhere(appliance-tools), so it can be used in automated installation.

Benefit to Fedora

  • Security - lower the attack surface by installing only necessary packages
  • Performance - faster installation and less running services
  • Storage - installation is less than 500MB
  • Package dependencies - package dependencies are regularly watched
  • Fedora on servers - encourage users to use Fedora on server and support other distributions based on Fedora like Red Hat Enterprise Linux or CentOS

Scope

  • Regularly perform installations during Fedora cycle and whatch for:
    • disk usage
    • packages dependencies
    • running services
    • SUID/SGID binaries
  • Push new package profile into anaconda. This might require support from release engineering and anaconda stuff.

How To Test

There is no need for special hardware to test this feature.

You can use bare metal or virtual environment for installation. Since there is no anaconda option yet, use this kickstart. The kickstart package set covers the @core group plus minimal number of extra packages. The kickstart file includes some security tweaks that are not mandatory for this feature.

What are the expected result?

  • Disk usage of "/" mount point is less than 500MB
  • Package list is subset of following package list
  • List of running services is subset of following list of services
  • List of SUID binaries is subset of following list of SUID binaries
  • List of SGID binaries is subset of following list of SGID binaries

User Experience

Users will have have several options (anaconda/kickstart) to perform minimal platform installation. Their installations will be finished quickly. There will be minimal number of packages after they are ready with customizations. The whole system will be less vulnerable by attack.

Dependencies

  • anaconda
  • comps

Contingency Plan

This feature is not critical. Even if the criteria in test section are not exactly met we can live with that and improve it later. I don't expect any problems with anaconda and comps, but if there are any, we can abandon this way and provide at least the kickstart file in some other package.

Documentation

There is no need for documentation on this feature. I'm gonna provide all the details on this page.

Filed Bugs

Release Notes

  • ToDo!

Comments and Discussion

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/MinimalPlatform&oldid=78771"