Network Servers

Revision as of 03:58, 2 December 2009

This page needs an update. Information posted here has been viewed as incorrect, incomplete, or out of date. Anyone is welcome to correct these flaws if this page has not been locked. Otherwise, contact a Support Team member and give them notice of this issue. Thank you.

Network servers are maintained by the Infrastructure Team, which is made up of server managers, server administrators and server operators, in accordance with published policies.

Link Requirements

A complete list of hardware, bandwidth, and software-related requirements for network servers can be seen here.

Test Link

The test link phase lasts for four (4) weeks, unless earlier terminated by the Server Management team. During this time, the new server will be linked to the network. For the first week, the server will not be added to the primary host records for client access. For the second two weeks, the server wil start accepting clients. The performance of the new server will be closely monitored, especially pertaining to network connectivity and handling of user load.

During the last week of the test link phase, the Server Management team will start to discuss the link. At the end of the phase, the Server Management team will hold a vote for 48 hours to determine one of the following possible outcomes:

• grant the server a permanent link.
• delink the server.
• extend the test link period for two (2) weeks.

A simple majority is required to approve any option. In the event the server is delinked, it's admin may reapply again after three (3) months, unless otherwise noted. If the test link is extended, after two weeks the Server Management team will vote again, except this time the options will only be to grant a permanent link, or delink.

Server Naming Convention

All servers linked to DareNET are expected to follow our standard naming convention. For more details and information, please read over our Server Naming Guidelines.