From Fedora Project Wiki
mNo edit summary |
mNo edit summary |
||
Line 17: | Line 17: | ||
#* question about how to track installs like gem installs | #* question about how to track installs like gem installs | ||
# Compatibility with deployment systems (e.g., install server roles via central admin console like Satellite Server / Spacewalk) | # Compatibility with deployment systems (e.g., install server roles via central admin console like Satellite Server / Spacewalk) | ||
# Offline installs of roles |
Revision as of 16:11, 19 November 2013
Initial Goals
- Automated ("mass") install within a larger Linux infrastructure (e.g. PXE is an option, may have LDAP/IPA)
- Manual install without a supporting infrastructure (e.g. the very first Linux server)
- Guided role installation (eg. Server Roles should be installable by a junior administrator with little difficulty)
- Where possible, existing servers and installed roles should be upgradable to new releases with minimal involvement by the admin
- Producing an upgrade compatibilty matrix at least for the roles we say we feature.
- Roles should be installable at install time (e.g. in Anaconda) and post-install.
Deferred Goals
- Replication of an existing server (Based on discussion, not sure this is needed... deferred for later)
- etckeeper and augeas was noted here
- question about how to track installs like gem installs
- Compatibility with deployment systems (e.g., install server roles via central admin console like Satellite Server / Spacewalk)
- Offline installs of roles