Difference between revisions of "Linking"

From Xertion Wiki
Jump to navigation Jump to search
(Created page with "The Xertion IRC network shall henceforth be called simply "Xertion" or "the network". ==Definition of a Testlink== A testlink is a temporary status for new servers on the net...")
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The Xertion IRC network shall henceforth be called simply "Xertion" or "the network".
+
{{Ambox
 +
|type = notice
 +
|image =
 +
|issue='''<span style="color:red">Sorry, the Xertion IRC Network is NOT currently accepting link applications at this time.</span><br />'''
 +
|fix=However, you are still welcome to fill out and submit the link application at the bottom of this page. If we open up link applications again, we'll consider it at that time. Thanks for your interest!
 +
}}
  
==Definition of a Testlink==
 
A testlink is a temporary status for new servers on the network. A new server will be linked to a regular hub like all other servers matching its region. The duration of a testlink is at least three weeks (21 days).
 
  
During testlink, the following restrictions apply: No IRC Operator that was introduced by linking said server shall receive any permissions with services unless agreed otherwise with Kaishiro.
 
  
After these first three weeks, the initial testlink time, the Network Owners will make a decision on whether or not to keep the server around; one of three results is possible:
+
This page describes Xertion's linking policies and the linking process.
* The server is rejected. Staff introduced by the link may be kept or not, depending on whether they are a valuable asset to the network.
 
* The server is kept in testlink for another while; the added duration must be fixed and not exceed 42 days.
 
* The server is promoted to full link. All restrictions will be removed promptly.
 
  
==Application for Linking a Server==
+
==Linking process==
Anyone may request to link to Xertion. Links from existing opers will be preferred but may not introduce new staff unless agreed otherwise with Kaishiro.
+
When a server is accepted for linking, it starts off as a test link. A test link is a temporary status assigned to new servers linked to the network. It helps us make sure that new servers are stable and can adhere to our linking policies. During a test link, the server will be linked to one of our hub servers closest to its region. It will have a DNS entry added but will not enter rotation right away. In addition, any IRC operator introduced to staff by way of linking a server will NOT receive any permissions with network services, unless all network owners unanimously agree.
  
After submitting your application, you will get a response on IRC in a private message by Kaishiro. He will inform you whether or not your application was accepted or not; all decisions are final.
+
After the initial test link period is up (at least 3 weeks), the network's upper management (network owners and root administrators) will come together, provide input on the server's observed stability and conformity to network linking policy, and come to one of the following 3 decisions:
 +
* '''Link rejected''' - the link is rejected and terminated. A detailed explanation will be given if this is the case. If the link introduced an IRC operator to network staff, he/she '''may''' be retained on staff if they are determined to be a valuable asset to the network.
 +
* '''Test link continued''' - the link remains in test link status for an additional duration not to exceed 42 days. If necessary, an explanation as to why we require an extended test link status for the server will be given.
 +
* '''Link accepted''' - the link has passed test link status and is promoted to full link. Any restrictions applied during test link phase are removed immediately.
 +
 
 +
==Linking policies==
 +
Any user may request to link to Xertion. Links from existing network staff are preferred but are generally not permitted to introduce new staff unless network ownership agrees.
 +
 
 +
Before filling out and sending the form at the end of this page, you should read all of the following requirements and recommendations. Obviously, anything listed under Requirements is a '''must''' to even be considered to link. Items listed under Recommendations are preferred, but '''not''' required for consideration.
  
All following requirements and recommendations are subject to change at a moment's notice.
 
 
===Requirements to Link===
 
===Requirements to Link===
* Home servers need not apply, no matter how great you think your hardware/connectivity may be.
+
* Your server CANNOT be:
* Your server must either be a VPS, a dedicated server or colocated.
+
** A home server with any kind of connection, no matter how good you think your hardware or connectivity is.
* You must have root access on the server and follow requests to install software during the initial setup of the link.
+
** Hosted with TelVPS or FDCServers (this is due to unreliable service, poor performance, unreliable customer support, or otherwise poor reputation)
* You should be able to provide at least 2Mbps down and up and provide a monthly traffic of about a gigabyte.
+
** Linked to another network at the same time
* Your server must be running Linux, OpenBSD or FreeBSD. No Windows or OS X servers whatsoever and you must be capable of doing basic administration tasks on your own (roughly to the point of LPIC-1).
+
** Running Windows or OS X - we only accept Linux, OpenBSD, or FreeBSD.
* Your server may not link to another network at the same time.
+
*** Software such as Cygwin or Ubuntu On Windows is '''NOT''' considered Linux and thus will not be considered.
* Your server must have an x86_64 architecture CPU with at least 1GHz. Your server must have at least 256MB of RAM.
+
** An IRC shell server - it must be a VPS, a dedicated server, or a colocated server. If a VPS, it must not be OpenVZ, it must instead be KVM (preferred), Xen, or VMware.
* You must have an IPv4 IP address that you can dedicate to the network; ports should be possible to open as necessary for client and server connections.
+
* You must have full root access to the server and you must be able to follow requests to install software components during initial link setup.
* Your server must use ntp to synchronize its time accurately. Failure to do so will be a reason to reject your application or delink your server prematurely. If you are linking a VPS and ntp is not an option, make sure you can prove that your time is reliable.
+
* You must be capable of doing basic server administration tasks on your own, at least to the point of LPIC-1.
* You, the server administrator, must speak English relatively fluently. This applies to any IRC Operators you may wish to bring as well.
+
* Your server must meet the following hardware and network connectivity requirements:
 +
** x86_64 (64-bit) CPU and architecture, clocked at 1 GHz or greater. i686 (32-bit) architecture/CPUs are still acceptable but 64-bit setups will have much higher preference.
 +
** 1 GB RAM or better, 2 GB or greater highly preferred
 +
** One IPv4 address that can be dedicated to the IRC network, with as many ports as possible open for client and server connections.
 +
** 100 Mbps or greater network connectivity + throughput
 +
** 1 GB or greater monthly bandwidth allotment, 2+ GB allotment highly preferred
 +
** Disk size 24 GB or greater
 +
* Server must run NTP (not ntpdate) and must accurately synchronize its time. Correct time is CRITICAL to proper IRC server operation (otherwise all sorts of nasty things can occur), and therefore an inability to keep correct time will lead to either automatic rejection of your application or premature delink.
 +
* You must speak English relatively fluently, and any IRC operators you bring with you must also speak English.
 +
* Your server name must use our domain name (xertion.org), we will not accept other domains. No exceptions.
 +
 
  
 
===Recommendations===
 
===Recommendations===
* Your server should not be hosted by OVH or FDC.
+
These server recommendations are a plus, but are '''not''' required to link:
* Your server should have native IPv6, at least one IP.
+
 
* Your server should have a secondary IPv4 address; it might be used for setting up a webchat instance. If you are alright with that, please specify so.
+
* Have native IPv6 connectivity
* Your server should not run any software for personal use (this includes, but is not limited to, GUIs/X11 and torrenting programs).
+
* Don't run resource-intensive programs such as GUIs (X11), torrenting programs, etc.
* You should be able to provide the account for the IRCd linked to the network with sudo access temporarily for the initial setup to make it easier on us.
+
* Can provide network account on the server with temporary sudo access to set up any software and libraries we may need for the IRCd.
* You should add no operators if possible; it increases the likelihood of a link.
+
** Alternatively, install at least gnutls + gnutls-bin + gnutls-dev, Perl, g++/gcc (clang is also acceptable on FreeBSD), make and all other essential compilation and linker tools, as well as a text editor like nano or vi(m).
* Bonus points for being part of the datacenter.
+
* Don't add any additional IRC operators other than yourself if possible.
* To make our life easier, please install: gnutls and gnutls-dev, g++ (On FreeBSD: clang is also alright), make and all other essential compilation tools, Perl (5.8.0+), vi.
+
* HUGE plus if your server is part of the datacenter.
  
 
==Form==
 
==Form==
If you are interested in linking, please fill out this form and submit it using e-mail to [mailto:admin@xertion.org the staff]. Failure to fill out the entire form will automatically lead to rejection of your application.
+
'''<span style="color:red">The Xertion IRC Network is not currently accepting link applications at this time, though you may still fill out the form below for future consideration.</span>'''
  
  IPv4 address(es), comma separated:  
+
If you are interested in linking, and you meet all the requirements outlined in the Requirements section above, please fill out this form and submit it via e-mail to [mailto:admin@xertion.org the staff]. Failure to fill out the entire form will automatically lead to rejection of your application. Please provide as much information as possible when filling out each field.
  IPv6 address(es), comma separated; if you have a whole prefix, supply only the IP(s) available for the network:  
+
 
  Hosting provider:  
+
  IPv4 address(es), comma separated:
  Hosting type: [ ] Colocation, [ ] Dedicated Server, [ ] VPS
+
  IPv6 address(es), comma separated; if you have a whole prefix, supply only the IP(s) available for the network:
  Location (Country, [if US: state], region):  
+
  Hosting provider:
  Processor (number of CPUs, model, speed, cores):  
+
  Hosting type: [ ] Colocation, [ ] Dedicated Server, [ ] VPS/VM
  RAM:  
+
  Location (Country, [if US: state], region):
  Line speed:  
+
  Processor (number of CPUs, model, speed, cores):
  Monthly bandwidth:  
+
  RAM:
  Disk space (total/free; state if there is a quota for the user):  
+
  Line speed:
  Operating system (if Linux distribution name as well, version):  
+
  Monthly bandwidth:
 +
  Disk space (both total and free, in GB):
 +
  Operating system (if Linux, include distribution name and version as well):
 
  Server admin:
 
  Server admin:
   Nick:  
+
   Nickname:
   E-mail address (if not the same you're sending this e-mail from):  
+
   E-mail address (if different from this email address):
 +
  Date of birth:
 +
  Experience with IRC (years/months):
 +
  Additional spoken languages (if other than English, leave blank if none):
 +
Additional operator (leave this section blank if no additional operators):
 +
  Nick:
 
   Date of birth:
 
   Date of birth:
   Experience with IRC:  
+
   Experience with IRC:
   Languages (do not list English):
+
   Spoken languages (if other than English, leave blank if none):
Additional operator:
+
  Desired server name (must use network domain, e.g. <name>.xertion.org):
  Nick:
+
  Special notes (place an X in all that apply):
  Date of birth:
+
  [ ] I, the server administrator, have physical access to the machine (this means that you can physically touch the server)
  Experience with IRC (do not list English):  
 
  Desired server name:  
 
  Special notes:
 
  [ ] I, the server administrator, have physical access to the machine.
 
 
  [ ] I, the server administrator, wish to become an IRC Operator on the Xertion network.
 
  [ ] I, the server administrator, wish to become an IRC Operator on the Xertion network.
 
  [ ] Other people have root on the server (list if applicable with nick and e-mail):
 
  [ ] Other people have root on the server (list if applicable with nick and e-mail):
  For the following questions, please use as much space as you need -- don't be concerned about writing too much, worry about writing too little.
+
[ ] Other special notes not listed or covered in this form, specify:
How have you been involved in Xertion so far?
+
  For the following questions, please use as much space as you need. You needn't be concerned about writing too much, but at the same time you should write enough to sufficiently answer each one.
Why do you think that your server should link to Xertion?
+
  How have you been involved in Xertion so far?
What are your personal technical skills with *NIX and networking?
+
  Why do you want to link your server to Xertion?
 +
  What are your personal technical skills with *NIX and networking?

Revision as of 06:40, 7 May 2017


This page describes Xertion's linking policies and the linking process.

Linking process

When a server is accepted for linking, it starts off as a test link. A test link is a temporary status assigned to new servers linked to the network. It helps us make sure that new servers are stable and can adhere to our linking policies. During a test link, the server will be linked to one of our hub servers closest to its region. It will have a DNS entry added but will not enter rotation right away. In addition, any IRC operator introduced to staff by way of linking a server will NOT receive any permissions with network services, unless all network owners unanimously agree.

After the initial test link period is up (at least 3 weeks), the network's upper management (network owners and root administrators) will come together, provide input on the server's observed stability and conformity to network linking policy, and come to one of the following 3 decisions:

  • Link rejected - the link is rejected and terminated. A detailed explanation will be given if this is the case. If the link introduced an IRC operator to network staff, he/she may be retained on staff if they are determined to be a valuable asset to the network.
  • Test link continued - the link remains in test link status for an additional duration not to exceed 42 days. If necessary, an explanation as to why we require an extended test link status for the server will be given.
  • Link accepted - the link has passed test link status and is promoted to full link. Any restrictions applied during test link phase are removed immediately.

Linking policies

Any user may request to link to Xertion. Links from existing network staff are preferred but are generally not permitted to introduce new staff unless network ownership agrees.

Before filling out and sending the form at the end of this page, you should read all of the following requirements and recommendations. Obviously, anything listed under Requirements is a must to even be considered to link. Items listed under Recommendations are preferred, but not required for consideration.

Requirements to Link

  • Your server CANNOT be:
    • A home server with any kind of connection, no matter how good you think your hardware or connectivity is.
    • Hosted with TelVPS or FDCServers (this is due to unreliable service, poor performance, unreliable customer support, or otherwise poor reputation)
    • Linked to another network at the same time
    • Running Windows or OS X - we only accept Linux, OpenBSD, or FreeBSD.
      • Software such as Cygwin or Ubuntu On Windows is NOT considered Linux and thus will not be considered.
    • An IRC shell server - it must be a VPS, a dedicated server, or a colocated server. If a VPS, it must not be OpenVZ, it must instead be KVM (preferred), Xen, or VMware.
  • You must have full root access to the server and you must be able to follow requests to install software components during initial link setup.
  • You must be capable of doing basic server administration tasks on your own, at least to the point of LPIC-1.
  • Your server must meet the following hardware and network connectivity requirements:
    • x86_64 (64-bit) CPU and architecture, clocked at 1 GHz or greater. i686 (32-bit) architecture/CPUs are still acceptable but 64-bit setups will have much higher preference.
    • 1 GB RAM or better, 2 GB or greater highly preferred
    • One IPv4 address that can be dedicated to the IRC network, with as many ports as possible open for client and server connections.
    • 100 Mbps or greater network connectivity + throughput
    • 1 GB or greater monthly bandwidth allotment, 2+ GB allotment highly preferred
    • Disk size 24 GB or greater
  • Server must run NTP (not ntpdate) and must accurately synchronize its time. Correct time is CRITICAL to proper IRC server operation (otherwise all sorts of nasty things can occur), and therefore an inability to keep correct time will lead to either automatic rejection of your application or premature delink.
  • You must speak English relatively fluently, and any IRC operators you bring with you must also speak English.
  • Your server name must use our domain name (xertion.org), we will not accept other domains. No exceptions.


Recommendations

These server recommendations are a plus, but are not required to link:

  • Have native IPv6 connectivity
  • Don't run resource-intensive programs such as GUIs (X11), torrenting programs, etc.
  • Can provide network account on the server with temporary sudo access to set up any software and libraries we may need for the IRCd.
    • Alternatively, install at least gnutls + gnutls-bin + gnutls-dev, Perl, g++/gcc (clang is also acceptable on FreeBSD), make and all other essential compilation and linker tools, as well as a text editor like nano or vi(m).
  • Don't add any additional IRC operators other than yourself if possible.
  • HUGE plus if your server is part of the datacenter.

Form

The Xertion IRC Network is not currently accepting link applications at this time, though you may still fill out the form below for future consideration.

If you are interested in linking, and you meet all the requirements outlined in the Requirements section above, please fill out this form and submit it via e-mail to the staff. Failure to fill out the entire form will automatically lead to rejection of your application. Please provide as much information as possible when filling out each field.

IPv4 address(es), comma separated:
IPv6 address(es), comma separated; if you have a whole prefix, supply only the IP(s) available for the network:
Hosting provider:
Hosting type: [ ] Colocation, [ ] Dedicated Server, [ ] VPS/VM
Location (Country, [if US: state], region):
Processor (number of CPUs, model, speed, cores):
RAM:
Line speed:
Monthly bandwidth:
Disk space (both total and free, in GB):
Operating system (if Linux, include distribution name and version as well):
Server admin:
 Nickname:
 E-mail address (if different from this email address):
 Date of birth:
 Experience with IRC (years/months):
 Additional spoken languages (if other than English, leave blank if none):
Additional operator (leave this section blank if no additional operators):
 Nick:
 Date of birth:
 Experience with IRC:
 Spoken languages (if other than English, leave blank if none):
Desired server name (must use network domain, e.g. <name>.xertion.org):
Special notes (place an X in all that apply):
[ ] I, the server administrator, have physical access to the machine (this means that you can physically touch the server)
[ ] I, the server administrator, wish to become an IRC Operator on the Xertion network.
[ ] Other people have root on the server (list if applicable with nick and e-mail):
[ ] Other special notes not listed or covered in this form, specify:
For the following questions, please use as much space as you need. You needn't be concerned about writing too much, but at the same time you should write enough to sufficiently answer each one.
 How have you been involved in Xertion so far?
 Why do you want to link your server to Xertion?
 What are your personal technical skills with *NIX and networking?