Log in | Back to darenet.org
Share

Infrastructure

m (Reverted edits by Admin (Talk); changed back to last version by Secretagent)
m
Line 2: Line 2:
<h3><font color="#003366">Thank you for your interest in helping DareNET!</font></h3>
<h3><font color="#003366">Thank you for your interest in helping DareNET!</font></h3>
-
We greatly appreciate your interest in helping DareNET grow and your willingness to contribute to that process. However, we feel it is necessary to point out, and that you realize, that DareNET is not a convential IRC network.
+
We appreciate your interest and willingness to contribute your time and resources towards helping DareNET grow. It's important for you to realize that DareNET does not operate the way most conventional IRC networks operate. Servers are hosted, not linked. They are maintained remotely from central sites using ssh and scp. Configuration files, motds and other necessary files are generated via an automated script at a central location, and new servers are either staged as binary files or recompiled on the server account, depending on architecture and other factors.
-
{{Headerbox_blue
+
We will happily acknowledge your contribution publicly, however, as a general rule, we only provide an O-line for the server's administrator. Any other individuals need to apply for a DareNET staff position and their applications will recieve the same consideration as those of other users. When a staff application is accepted, no minimum level of privilege is guaranteed or offered. Information on network governance can be found here.
-
| text = <h4><font color="#003366">How DareNET Differs:</font></h4>
+
-
* Our servers are maintained by our Server Management team remotely from central sites using SSH/SCP. This team consists of our server managers, server administrators and server operators.
+
Regardless, hosting a DareNET server helps the network and the community and we appreciate that you are considering it.
-
* New configurations files are generated via an automated script and distributed from a central location. The IRC daemon may be ''rehashed'' remotely to apply any configuration changes.
+
<h3><font color="#990000">System Specifications & Connectivity Requirements</font></h3>
-
* New servers are either staged as binary files or recompiled on the server account, depending on architecture and other factors.
+
{| class="wikitable" width="97%" style="font-size: 90%; text-align: left;"
-
 
+
|-
-
<h4><font color="#003366">Additionally, Our Promises:</font></h4>
+
| '''Required'''
-
 
+
| '''Desired'''
-
* We DO ALLOW server administrators to choose their own server operators, provided they follow our [[Policies|current policies]].
+
| '''Notes'''
-
 
+
|-
-
* We DO NOT gurantee any minimum level of privilege on the network. However, we'll happily acknowledge your contribution publicly. A server's staff may apply for various staff positions; their applications receive the same consideration as those of other users.
+
| FreeBSD 5.x+ or Linux 2.6
-
 
+
| multilib is desired for 64-bit machines.
-
* Servers may need to be delinked or rehubbed at any time. We cannot always provide notice before such actions are taken, but certainly try to do so in all circumstances.
+
|
-
}}
+
|-
-
Regardless, hosting a DareNET server helps the network and the community and we appreciate that you are considering it.
+
| Pentium4 or better
-
 
+
| 64-bit multi-core
-
<h3><font color="#990000">Hardware & Connectivity Requirements</font></h3>
+
| Generally, Intel or other compatible hardware is preferred.
-
 
+
|-
-
The listed hardware and connectivity requirements are extremely generous. Our goal is to ensure that each server exhibits the best possible connectivity and responsiveness.
+
| 512MB or more of RAM
-
 
+
| 1.5G or more
-
* '''Minimum Bandwidth.''' The server must NOT be running on a broadband or dial-up connection. Preferably, it should be on a multihomed network, in order to ensure high reliability and low latency. We must also be able to verify that your server is on a multihomed network, via BGP announcements.
+
|
-
 
+
|-
-
* '''Processor.''' A 1GHz processor or better. Generally, Intel or other compatible hardware is preferred and makes life a bit easier for our Server Management team, but it is not a hard and fast rule.
+
|}
-
 
+
'''Minimum Bandwidth'''<br>
-
* '''Memory.''' 512MB or more of RAM is required.
+
The server must NOT be running on a broadband or dial-up connection. Preferably, it should be on a multihomed network, in order to ensure high reliability and low latency. We must also be able to verify that your server is on a multihomed network, via BGP announcements.
-
 
+
-
* '''Disk Space.''' Space usage for logs may vary from system to system, and on what all you actually intend to log. In general, it is best to leave appreciable amounts of free space.
+
-
 
+
-
* '''Hours of Operation.''' 24-7, 365 days, reliable operation is a must.
+
-
 
+
-
* '''Multiple Uses.''' Dedicated servers are generally preferred; although, we do not require that the machine be dedicated. However, all server must adequately address any and all security concerns and be sufficient to properly run ircd. We advise against running critical applications on the same host; if you do, please plan to monitor resource usage (including allocation of memory and processor time). We make every effort to provide timely notification of problems, but we're a volunteer organization running a 24-7 network and staff may not always be available as needed.
+
-
 
+
-
* '''Disallowed Hosts.''' Unfortunately, due to unreliable performance or just plain bad customer service, we cannot accept paid links from the following providers at this time: FDC Servers, Santrex.net and Managed.com.
+
<h3><font color="#003366">Software-related Requirements</font></h3>
<h3><font color="#003366">Software-related Requirements</font></h3>
-
The folowing list details the software-related requirements for DareNET servers. Again, we have tried to pay particular attention to providing room for expansion with minimum effort on the part of server administrators / hosting organizations.
+
{| class="wikitable" width="97%" style="font-size: 90%; text-align: left;"
 +
|-
 +
| '''Required'''
 +
| '''Desired'''
 +
| '''Notes'''
 +
|-
 +
| GNU bash
 +
| zsh
 +
| Shell scripts for server operations assume the availability of this shell.
 +
|-
 +
| GNU Awk (gawk)
 +
|
 +
| The awk utility interprets a special-purpose programming language that makes data-reformatting jobs easy. Our lsync program requires this.
 +
|-
 +
| GNU screen
 +
|
 +
| This utility is frequently used to run sessions which can be detached automatically at disconnection. Our Server Management team frequently uses this.
 +
|-
 +
| GNU bison 2.4.1
 +
|
 +
|
 +
|-
 +
| Perl 5.6+
 +
|
 +
|
 +
|-
 +
| Compiletime toolchan
 +
| gcc 3.2+ and gdb
 +
|
 +
|-
 +
| vi or equivalent editor
 +
| vim 7.x
 +
| Emacs may be helpful
 +
|-
 +
| Network time daemon
 +
| ntpd
 +
| The server host should be synced to a time server at all times.
 +
|-
 +
| Openssh daemon
 +
|
 +
| We require a recent openssh daemon, ssh2 protocol only.
 +
|-
 +
| OpenSSL 0.9.8k
 +
|
 +
| Our servers support SSL client connections using the OpenSSL toolkit.
 +
|-
 +
| SVN 1.6.x
 +
|
 +
| Our ircd codebase is consistently evolving and changes are applied on a rapid basis; SVN helps make updating easy!
 +
|-
 +
|}
-
* '''FreeBSD or GNU/Linux.''' Our current servers run either FreeBSD or GNU/Linux. While other excellent open source / free software operating systems exist and have been shown to work with our server software, the use of these two operating systems simplifies network operations. FreeBSD 6.x or later or the Linux 2.4.23+ kernel are required.
+
<h3><font color="#990000">System Configuration</font></h3>
-
* '''The bash shell.''' Shell scripts for server operations assume the availability of this shell.
+
Where possible we look for dedicated machines with root access, however, this is not a requirement. We will consider different setups; however, all servers must adequately address any and all security concerns and be sufficient to properly run ircd. We will require:
-
* '''GNU Awk (gawk).''' The awk utility interprets a special-purpose programming language that makes it possible to handle simple data-reformatting jobs with just a few lines of code. Our lsync program assumes the availabilty of this utility.
+
* '''Account Access.''' The server daemon (ircd-darenet) runs as a user program under a vanilla end-user account (frequently called "darenet"), with no setuid or special privilege. We require that our Server Management team have access to the account via password, and preferably SSH keys.
-
* '''GNU Wget.''' Certain programs/scripts for server operations assume the availability of this package.
+
* '''Core File Limit.''' Our ircd code base continues to evolve, and we may require this handy debugging tool at times. DareNET servers will produce very large core files, so the limit should be accordingly high - at least 1GB or so.
-
* '''Screen.''' The GNU screen utility is frequently used to run sessions which can be detached automatically at disconnection. Our Server Management team frequently uses this utility.
+
<h3><font color="#003366">Other Requirements</font></h3>
-
* '''Perl 5.x.''' Perl 5.6+ is preferred.
+
While servers are configured and maintained by our Server Management team, and we don't require active involvement from the server administrator, we ask that:
-
* '''Compile toolchan facilities.''' These should include ''gcc'' and ''gdb'', as well as any required binary utilities. We currently require gcc 3.2.
+
* Server Administrators ensure that we have up-to-date contact information, on and offline.
 +
* Server Administrators stay subscribed to the darenet-admins mailing list (low traffic, announcements only).
 +
* Server Administrators endeavour to give us ample advance warning about network, hardware or software upgrades and maintenance which may affect the network.
 +
* Server Administrators communicate unexpected downtime/maintenance ASAP.
-
* '''A slection of editors.''' Joe, ar and vi are highly preferred. Emacs may be helpful.
+
<h3><font color="#990000">Applying to Link/Host a Server</font></h3>
-
* '''IRC client.''' This is mostly for testing. Irssi is preferred. If no other clients are available, ircII is an acceptable minium.
+
Before applying to link/host a server, you should take time to read over our current policies. Please do not apply unless you are in full agreement with our policies and practices. Additionally, you may find it helpful to consult with a member of our Server Management team prior to applying. Feel free to ask any questions you may have in #routing or by emailing routing@darenet.org. Regardless, the formal application process begins when you submit an email containing the following information to routing@darenet.org.
-
* '''Core files.''' Expect core files on ocassion. Core file size limits should be generous. Our ircd code base continues to evolve, and, as such, we will need this handy debugging resource.
+
* '''Contact Information''' -- Please include your full name, email address and telephone number. List the best times to contact you (including time zone).
 +
* '''Sponsor''' -- Who should we credit for the server? Provide name(s) of organizations/individuals. If you'd like a link placed on our site, with logo, include that as well.
 +
* '''Geographical Location of Server''' -- City, state/province and country.
 +
* '''Hardware, Software, Bandwidth and Hosting''' -- Please describe the system you are offering to link/host, including where the machine is hosted and the type of arrangement you have with the hosting provider (e.g. co-located, sponsored, etc).
 +
* '''IP Address''' -- This will allow us to perform latency and route checking.
-
* '''Network time daemon.''' Preferred daemons are either ''xntpd'' or ''nptd'', with local access via {x}ntpdc to get server status. The server host should be synced to a time server at all times, and should have backup servers. It is recommended you specify groups of three servers (with a minimum of at least one such group) to sync time from. It is essential you start up ntpd in your init scripts. It is also essential that you run ''ntpdate'', part of the package, at startup before starting ntpd.
+
DareNET's Server Management team liaisons try to respond to all server application requests within 48 hours, unless other circumstances or team business dictate a longer period to elapse. The Server Management team is in recess over major holiday periods, such as Christmas/Yule/Hanukkah and New Years. Application requests received during these periods may not receive a response until the team returns.
-
* '''Account access.''' The server daemon (ircd-darenet) runs as a user program under a vanilla end-user account (frequently called ''"darenet"''), with no setuid or special privilege. We require that our Server Management team ''(e.g. server managers)'' have access to the account via password, and ssh public key. Root access to the machine is highly desirable, since it makes it easier for us to double-check initial configuration and resolve problems in an emergency; although, this is not required.
+
All applications will be given the same considerations and we regret that we may not always be able to accept a server offer for whatever reason.
-
 
+
-
* '''Opensshd dameon.''' We require a recent opensshd daemon, ssh2 protocol only; account access via ssh and scp. All access to the server account will use ssh. The scp program is required to transfer files. Access to the account by public key should be allowed, as should access by password.
+
-
 
+
-
* '''OpenSSL toolkit.''' Our servers support SSL client connections using the OpenSSL toolkit.
+
-
 
+
-
* '''SVN.''' Our ircd code base is consistently evolving and changes are applied to the network on a rapid basis; therefore, we require SVN be installed to aide in easily updating servers.
+
-
 
+
-
<h3><font color="#990000">Applying to Link</font></h3>
+
-
 
+
-
Before applying to link a server to DareNET, you should take the time to read over our [[Policies|current policies]]. You, and any of your staff, should be in agreement with our current policies and practices. Additionally, you may find it helpful to consult with our Server Management team (#routing or [mailto:routing@darenet.org routing@darenet.org]). They will be able to answer any questions or concerns you might have, and guide you through the linking process.
+
-
 
+
-
Regardless, the formal application process is begun by completing and submitting a server link application, which is available at [http://www.darenet.org/linkapp http://www.darenet.org/linkapp].
+
-
 
+
-
{| class="wikitable" width="100%" style="font-size: 85%; text-align: left;"
+
-
|'''NOTE:''' Upon application submission, you agree to consent to a port scan and other unobtrusive probes to verify that the above listed requirements have been met.
+
-
|}
+

Revision as of 05:56, 4 June 2009

Thank you for your interest in helping DareNET!

We appreciate your interest and willingness to contribute your time and resources towards helping DareNET grow. It's important for you to realize that DareNET does not operate the way most conventional IRC networks operate. Servers are hosted, not linked. They are maintained remotely from central sites using ssh and scp. Configuration files, motds and other necessary files are generated via an automated script at a central location, and new servers are either staged as binary files or recompiled on the server account, depending on architecture and other factors.

We will happily acknowledge your contribution publicly, however, as a general rule, we only provide an O-line for the server's administrator. Any other individuals need to apply for a DareNET staff position and their applications will recieve the same consideration as those of other users. When a staff application is accepted, no minimum level of privilege is guaranteed or offered. Information on network governance can be found here.

Regardless, hosting a DareNET server helps the network and the community and we appreciate that you are considering it.

System Specifications & Connectivity Requirements

Required Desired Notes
FreeBSD 5.x+ or Linux 2.6 multilib is desired for 64-bit machines.
Pentium4 or better 64-bit multi-core Generally, Intel or other compatible hardware is preferred.
512MB or more of RAM 1.5G or more

Minimum Bandwidth
The server must NOT be running on a broadband or dial-up connection. Preferably, it should be on a multihomed network, in order to ensure high reliability and low latency. We must also be able to verify that your server is on a multihomed network, via BGP announcements.

Software-related Requirements

Required Desired Notes
GNU bash zsh Shell scripts for server operations assume the availability of this shell.
GNU Awk (gawk) The awk utility interprets a special-purpose programming language that makes data-reformatting jobs easy. Our lsync program requires this.
GNU screen This utility is frequently used to run sessions which can be detached automatically at disconnection. Our Server Management team frequently uses this.
GNU bison 2.4.1
Perl 5.6+
Compiletime toolchan gcc 3.2+ and gdb
vi or equivalent editor vim 7.x Emacs may be helpful
Network time daemon ntpd The server host should be synced to a time server at all times.
Openssh daemon We require a recent openssh daemon, ssh2 protocol only.
OpenSSL 0.9.8k Our servers support SSL client connections using the OpenSSL toolkit.
SVN 1.6.x Our ircd codebase is consistently evolving and changes are applied on a rapid basis; SVN helps make updating easy!

System Configuration

Where possible we look for dedicated machines with root access, however, this is not a requirement. We will consider different setups; however, all servers must adequately address any and all security concerns and be sufficient to properly run ircd. We will require:

  • Account Access. The server daemon (ircd-darenet) runs as a user program under a vanilla end-user account (frequently called "darenet"), with no setuid or special privilege. We require that our Server Management team have access to the account via password, and preferably SSH keys.
  • Core File Limit. Our ircd code base continues to evolve, and we may require this handy debugging tool at times. DareNET servers will produce very large core files, so the limit should be accordingly high - at least 1GB or so.

Other Requirements

While servers are configured and maintained by our Server Management team, and we don't require active involvement from the server administrator, we ask that:

  • Server Administrators ensure that we have up-to-date contact information, on and offline.
  • Server Administrators stay subscribed to the darenet-admins mailing list (low traffic, announcements only).
  • Server Administrators endeavour to give us ample advance warning about network, hardware or software upgrades and maintenance which may affect the network.
  • Server Administrators communicate unexpected downtime/maintenance ASAP.

Applying to Link/Host a Server

Before applying to link/host a server, you should take time to read over our current policies. Please do not apply unless you are in full agreement with our policies and practices. Additionally, you may find it helpful to consult with a member of our Server Management team prior to applying. Feel free to ask any questions you may have in #routing or by emailing routing@darenet.org. Regardless, the formal application process begins when you submit an email containing the following information to routing@darenet.org.

  • Contact Information -- Please include your full name, email address and telephone number. List the best times to contact you (including time zone).
  • Sponsor -- Who should we credit for the server? Provide name(s) of organizations/individuals. If you'd like a link placed on our site, with logo, include that as well.
  • Geographical Location of Server -- City, state/province and country.
  • Hardware, Software, Bandwidth and Hosting -- Please describe the system you are offering to link/host, including where the machine is hosted and the type of arrangement you have with the hosting provider (e.g. co-located, sponsored, etc).
  • IP Address -- This will allow us to perform latency and route checking.

DareNET's Server Management team liaisons try to respond to all server application requests within 48 hours, unless other circumstances or team business dictate a longer period to elapse. The Server Management team is in recess over major holiday periods, such as Christmas/Yule/Hanukkah and New Years. Application requests received during these periods may not receive a response until the team returns.

All applications will be given the same considerations and we regret that we may not always be able to accept a server offer for whatever reason.

Retrieved from "http://wiki.darenet.org/Infrastructure"