User:Adamwill/Draft server release criteria

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.

Non-interactive only OK

The install-time capability is not required to be interactive (i.e. it is acceptable for it to be possible by kickstart only).

No local account requirement

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.

References

• 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.

Details

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.

References

• 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 (ssh), port XX (Cockpit web interface), and any ports associated with server Roles selected during installation. Supported install-time firewall configuration options must work correctly.

Install time configuration

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.

References

• 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.

References

• Part of initial Server release criteria proposal, 2014-06-06
• Test case: TODO

Cockpit management interface

Unless explicitly specified otherwise, after system installation the Cockpit web management interface must be running and accessible on its default port (XX).

References

• 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 initial deployment time (during installation, or via a tool running on first boot after install, or both) and post-install.

Successful deployment

"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.

References

• Part of initial Server release criteria proposal, 2014-06-06
• Test case: TODO

Role service query

It must be possible to query supported roles for a list of services provided by the role, including information as to which are running and/or enabled.

References

• Part of initial Server release criteria proposal, 2014-06-06
• Test case: TODO

Role firewall configuration

It must be possible to query supported roles for a list of network ports the role operates on, and whether those ports are firewalled. It must be possible to open and close these ports using the server role interface.

References

• Part of initial Server release criteria proposal, 2014-06-06
• Test case: TODO