Network Servers

Current revision as of 18:32, 20 December 2009

Network servers are maintained by the Infrastructure Team, which is made up of Infrastructure Managers, Infrastructure Administrators and Server Administrators/Coordinators, 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 Infrastructure 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 Infrastructure Team will start to discuss the link. At the end of the phase, the Infrastructure 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 Infrastructure 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.

@@ Line 1: / Line 1: @@
-Network servers shall be maintained by their administrators and respective operators in conjunction with the Routing Team, and in accordance with policies established by the Routing Team.
+Network servers are maintained by the Infrastructure Team, which is made up of Infrastructure Managers, Infrastructure Administrators and Server Administrators/Coordinators, in accordance with published policies.
 == Link Requirements ==
-A complete list of hardware, bandwidth, and software-related requirements for network servers can be seen [[Routing|here]].
+A complete list of hardware, bandwidth, and software-related requirements for network servers can be seen [[Infrastructure|here]].
-== Link Applications ==
-Prospective server administrators interested in linking their server must file a link application, which can be found at [http://www.darenet.org/linkapp http://www.darenet.org/linkapp]. Upon receipt of a link application, the Routing Team will discuss the application for one week to determine the suitability of the prospective server. After discussion, voting will be held for 48 hours. A simple majority vote of the Routing Team is necessary to approve the application for a test link.
 == Test Link ==
-The test link phase lasts for four weeks unless earlier terminated by the Routing 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 will be set up for client access. The performance of the new server will be monitored, especially pertaining to network connectivity and handling of user load.
-During the last week of the test link phase, the Routing Team will discuss the link. At the end of the phase, the Routing Team will submit their notes to the Admins list for further review. The Admins will then have 48 hours to vote on whether to grant the server a permanent link, delink the server or extend the test link period for two weeks, after which they will vote again. A simple majority is required to approve any option.
+The test link phase lasts for four (4) weeks, unless earlier terminated by the Infrastructure 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 Infrastructure Team will start to discuss the link. At the end of the phase, the Infrastructure 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 Infrastructure 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]].