m (add remote authentication criterion) |
(create server role requirements section, add initial role criterion) |
||
| Line 32: | Line 32: | ||
==== SELinux configuration ==== | ==== SELinux configuration ==== | ||
Unless explicitly specified otherwise, after system installation SELinux must be enabled and in enforcing mode. | Unless explicitly specified otherwise, after system installation SELinux must be enabled and in enforcing mode. | ||
{{hidden|header=References|content= | |||
* Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06 | |||
* Test case: TODO | |||
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} | |||
{{anchor|server-role-requirements}} | |||
=== <span style="text-decoration:underline">Server Role requirements</span> === | |||
The requirements in this section are understood to cover the behaviour of both supported roles themselves and the server role framework they use. ''Supported roles'' are defined as the roles promoted as supported in the Fedora Server release under test. | |||
{{anchor|role-deployment}} | |||
==== Role deployment ==== | |||
It must be possible to deploy supported roles successfully both at install time and post-install. | |||
{{hidden|header=Successful deployment|content="Successful" deployment consists of installing the correct set of default packages for the role, and performing initial configuration of the role, including appropriate firewall configuration for network-accessible roles.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} | |||
{{hidden|header=References|content= | {{hidden|header=References|content= | ||
* Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06 | * Part of [https://lists.fedoraproject.org/pipermail/server/2014-June/001198.html initial Server release criteria proposal], 2014-06-06 | ||
* Test case: TODO | * Test case: TODO | ||
|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} | |headerstyle=background:#e5e5e5|fw1=normal|ta1=left}} | ||
Revision as of 22:42, 13 June 2014
Remote authentication
It must be possible to join the system to a FreeIPA or Active Directory domain at install time and post-install, and the system must respect the identity, authentication and access control configuration provided by the domain.
The install-time capability is not required to be interactive (i.e. it is acceptable for it to be possible by kickstart only).
This criterion is understood to mandate that there must be no requirement for a local user account to be created during install or first boot of a Server system.
- Part of initial Server release criteria proposal, 2014-06-06
- Test case: TODO
Post-install requirements
System log forwarding
It must be possible to forward system logs between two systems running the release, using rsyslog.
This criterion assumes a working network connection between the machines, appropriate firewall configuration, and a fairly straightforward rsyslog configuration. A more exotic configuration failing is unlikely to be considered a violation of this criterion.
- Part of initial Server release criteria proposal, 2014-06-06
- Test case: TODO
Firewall configuration
After system installation without explicit firewall configuration, the system firewall must be active on all non-loopback interfaces. The only ports which may be open to incoming traffic are port 22 and any ports associated with server Roles selected during installation. Supported install-time firewall configuration options must work correctly.
To explain the last part of this criterion - it is possible to include firewall configuration options in a kickstart-driven installation, and the criterion requires that those options work as expected. The options considered to be 'supported' are those documented at Anaconda/Kickstart#firewall. The case of a conflict between role-specified and manually-specified firewall configuration is not considered to be covered by these criteria.
- Part of initial Server release criteria proposal, 2014-06-06
- Test case: TODO
SELinux configuration
Unless explicitly specified otherwise, after system installation SELinux must be enabled and in enforcing mode.
- Part of initial Server release criteria proposal, 2014-06-06
- Test case: TODO
Server Role requirements
The requirements in this section are understood to cover the behaviour of both supported roles themselves and the server role framework they use. Supported roles are defined as the roles promoted as supported in the Fedora Server release under test.
Role deployment
It must be possible to deploy supported roles successfully both at install time and post-install.
"Successful" deployment consists of installing the correct set of default packages for the role, and performing initial configuration of the role, including appropriate firewall configuration for network-accessible roles.
- Part of initial Server release criteria proposal, 2014-06-06
- Test case: TODO