From Fedora Project Wiki
mNo edit summary |
m (→Deferred Goals) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{admon/ | {{admon/tip | This is an accepted proposal. | This proposal was discussed in the 12 Nov 2013 meeting and accepted in the 19 Nov 2013 meeting. | ||
}} | }} | ||
| Line 6: | Line 6: | ||
# Automated ("mass") install within a larger Linux infrastructure (e.g. PXE is an option, may have LDAP/IPA) | # 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) | # Manual install without a supporting infrastructure (e.g. the very first Linux server) | ||
# Guided role installation (eg. Server Roles should be installable by | # Guided role installation (eg. Server Roles should be installable by an inexperienced administrator with little difficulty) | ||
# Where possible, existing servers and installed roles should be upgradable to new releases with minimal involvement by the admin | # 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. | # Producing an upgrade compatibilty matrix at least for the roles we say we feature. | ||
| Line 14: | Line 14: | ||
# Replication of an existing server (Based on discussion, not sure this is needed... deferred for later) | # 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) | # Compatibility with deployment systems (e.g., install server roles via central admin console like Satellite Server / Spacewalk) | ||
# Offline installs of roles (ie provide tools so products can just run an infrastructure helper that spits out an ISO) | |||
#* Use case would be a secure site that can't access the internet... they want to install a server + roles without direct net access. | |||
Latest revision as of 21:23, 19 November 2013
This is an accepted proposal.
This proposal was discussed in the 12 Nov 2013 meeting and accepted in the 19 Nov 2013 meeting.
This proposal was discussed in the 12 Nov 2013 meeting and accepted in the 19 Nov 2013 meeting.
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 an inexperienced 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 (ie provide tools so products can just run an infrastructure helper that spits out an ISO)
- Use case would be a secure site that can't access the internet... they want to install a server + roles without direct net access.