Linking: Difference between revisions

From Xertion Wiki
Jump to navigation Jump to search
CuleX (talk | contribs)
emailconfirmed
40 edits
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..."
 
→‎Form: Uhh whoops, that's not supposed to be there, I need to learn to properly clean pages...
 
(36 intermediate revisions by 5 users not shown)
Line 1: Line 1:
The Xertion IRC network shall henceforth be called simply "Xertion" or "the network".
'''<span style="color:red">As of 12-Nov-2024, Xertion is no longer accepting new server links, for an indefinite time period. We simply do not have any need with the current load. Therefore, this page and the information on it has been deprecated and is no longer relevant. Sorry about that!</span><br />'''


==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.
This page describes Xertion's linking policies and the linking process. '''AGAIN, we are no longer accepting new server links for the foreseeable future. This page is maintained as legacy.'''
==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 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:
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:
* 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.
* '''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.
* The server is kept in testlink for another while; the added duration must be fixed and not exceed 42 days.
* '''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.
* The server is promoted to full link. All restrictions will be removed promptly.
* '''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.


==Application for Linking a Server==
==Linking policies==
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.
<s>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.</s>


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.
<s>Before filling out and sending the form at the end of this page</s>, 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===
<u>'''<u>NOTE: Your server must fulfill *ALL* of this section, or it will *NOT* be considered!</u>'''</u>
* Your server <u>'''CANNOT'''</u>:
** Be a home server with any kind of connection, no matter how good you think your hardware or connectivity is. Hosting a home server also tends to be against most residential ISP's terms of service.
** Be hosted with a provider known to us to have unreliable service, poor performance, unreliable customer support, or otherwise poor reputation (e.g FDCServers, TelVPS, VPSLink, etc).
** Be hosted with a provider that explicitly forbids the hosting of IRC servers in their Terms of Service/Acceptable Use Policy.
** Be linked to another network at the same time.
** Be running Windows, OS X, or anyBSD derivatives (FreeBSD/OpenBSD, etc).'''This is because our build scripts do not support these platforms.'''
*** NOTE: Software such as Cygwin or Ubuntu On Windows (aka 'Windows Subsystem for Linux") is '''NOT''' considered Linux!
** Be an IRC shell server - we don't care how reliable a shell provider it is.
 
* Your server <u>'''MUST'''</u>:
** <span>Be a VPS, a dedicated server, or a colocated server. If a VPS, it cannot be OpenVZ - please use KVM (preferred), Xen, LXC, LXD, or VMware.</span>
** Have full root access available<br />
** Meet the following hardware and network connectivity requirements (<span style="color: rgb(255, 0, 0);" data-mce-style="color: #ff0000;">'''failure to meet *ALL* of these requirements as outlined will result in automatic link rejection'''</span>):
*** '''CPU/processor:''' Must be a 64-bit CPU (x86_64) and architecture, clocked at 2 GHz or greater. 32-bit/i686 processors and/or userlands will NOT be accepted.
*** '''Memory:''' Must have 1.5 GB RAM or better (2 GB or greater highly preferred). '''<span style="color:green">We can make case-by-case exceptions for a VPS as long as it has a minimum of 512 MB.</span>'''
*** '''Operating System:''' Must be a GNU/Linux server derivative (Debian, Ubuntu, CentOS, Fedora, etc). '''Debian or Ubuntu is HIGHLY RECOMMENDED'''
*** '''IP Addresses:''' Must have '''*BOTH*''' one IPv4 address *'''AND*'''one IPv6 address, dedicated to the IRC network *ONLY*.
*** '''Ports:''' Must be able to open as many ports as we need for the network.
*** '''Bandwidth link speed:'''<u></u> Must have minimum 500 Mbps or greater network connectivity + throughput, 1 Gbps preferred.
*** '''Monthly bandwidth:''' Must have monthly bandwidth allotment of 500 GB or greater.
*** '''Disk:''' Must have at least 1 drive with minimum 40 GB space. Can be traditional HDD, or SSD of any kind. '''<span style="color:green">We can make case-by-case exceptions for a VPS as long as it has a minimum of 10 GB.</span>'''
** Run NTP/chrony ('''*NOT*''' ntpdate), and must prove it accurately synchronizes 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.<br />
** Have our domain name in its IRC server name (yourservername.xertion.org) - you can name it anything you like so long as it is appropriate and our domain name is present. We will NOT accept use of any other domain names in the IRC server name!


All following requirements and recommendations are subject to change at a moment's notice.
* You <u>'''MUST:'''</u>
===Requirements to Link===
** Be able to administer a Linux server entirely on your own, to at least the level of LPIC-1.
* Home servers need not apply, no matter how great you think your hardware/connectivity may be.
** Be able to follow requests to install software components during initial link setup.
* Your server must either be a VPS, a dedicated server or colocated.
** Speak English relatively fluently (any IRC operators you bring with you must also speak English).<br />
* You must have root access on the server and follow requests to install software during the initial setup of the link.
* You should be able to provide at least 2Mbps down and up and provide a monthly traffic of about a gigabyte.
* 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).
* Your server may not link to another network at the same time.
* Your server must have an x86_64 architecture CPU with at least 1GHz. Your server must have at least 256MB of RAM.
* 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.
* 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, the server administrator, must speak English relatively fluently. This applies to any IRC Operators you may wish to bring as well.


===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.
* No resource-intensive programs such as GUIs (X11), torrenting programs, etc running on the server
* 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.
* '''Specific GNU/Linux distribution is Ubuntu or Debian.'''
* Your server should not run any software for personal use (this includes, but is not limited to, GUIs/X11 and torrenting programs).
* Ability to provide the network account on the server with temporary sudo access so we can install any software and libraries we may need for the IRCd ourselves.
* 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.
** Alternatively, install at least these packages: libp11-kit-dev, libgmp-dev, pkg-config, Perl, g++/gcc, make and all other essential compilation and linker tools, as well as a text editor like nano or vi(m).
* You should add no operators if possible; it increases the likelihood of a link.
* No additional IRC operators other than yourself.
* Bonus points for being part of the datacenter.
* Server is part of the datacenter directly (HUGE plus!).
* 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.


==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"><strong><span style="color:red">As of 12-Nov-2024, Xertion is no longer accepting new server links, for an indefinite time period. We simply do not have any need with the current load. Therefore, this page and the information on it has been deprecated and is no longer relevant. Sorry about that! The form has thus been removed. We thank you for your interest.</span>'''</span></strong>
 
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
Location (Country, [if US: state], region):  
Processor (number of CPUs, model, speed, cores):
RAM:
Line speed:
Monthly bandwidth:
Disk space (total/free; state if there is a quota for the user):
Operating system (if Linux distribution name as well, version):
Server admin:
  Nick:
  E-mail address (if not the same you're sending this e-mail from):
  Date of birth:
  Experience with IRC:
  Languages (do not list English):
Additional operator:
  Nick:
  Date of birth:
  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.
[ ] 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.
How have you been involved in Xertion so far?
Why do you think that your server should link to Xertion?
What are your personal technical skills with *NIX and networking?

Latest revision as of 07:47, 12 November 2024

As of 12-Nov-2024, Xertion is no longer accepting new server links, for an indefinite time period. We simply do not have any need with the current load. Therefore, this page and the information on it has been deprecated and is no longer relevant. Sorry about that!


This page describes Xertion's linking policies and the linking process. AGAIN, we are no longer accepting new server links for the foreseeable future. This page is maintained as legacy.

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

NOTE: Your server must fulfill *ALL* of this section, or it will *NOT* be considered!

  • Your server CANNOT:
    • Be a home server with any kind of connection, no matter how good you think your hardware or connectivity is. Hosting a home server also tends to be against most residential ISP's terms of service.
    • Be hosted with a provider known to us to have unreliable service, poor performance, unreliable customer support, or otherwise poor reputation (e.g FDCServers, TelVPS, VPSLink, etc).
    • Be hosted with a provider that explicitly forbids the hosting of IRC servers in their Terms of Service/Acceptable Use Policy.
    • Be linked to another network at the same time.
    • Be running Windows, OS X, or anyBSD derivatives (FreeBSD/OpenBSD, etc).This is because our build scripts do not support these platforms.
      • NOTE: Software such as Cygwin or Ubuntu On Windows (aka 'Windows Subsystem for Linux") is NOT considered Linux!
    • Be an IRC shell server - we don't care how reliable a shell provider it is.
  • Your server MUST:
    • Be a VPS, a dedicated server, or a colocated server. If a VPS, it cannot be OpenVZ - please use KVM (preferred), Xen, LXC, LXD, or VMware.
    • Have full root access available
    • Meet the following hardware and network connectivity requirements (failure to meet *ALL* of these requirements as outlined will result in automatic link rejection):
      • CPU/processor: Must be a 64-bit CPU (x86_64) and architecture, clocked at 2 GHz or greater. 32-bit/i686 processors and/or userlands will NOT be accepted.
      • Memory: Must have 1.5 GB RAM or better (2 GB or greater highly preferred). We can make case-by-case exceptions for a VPS as long as it has a minimum of 512 MB.
      • Operating System: Must be a GNU/Linux server derivative (Debian, Ubuntu, CentOS, Fedora, etc). Debian or Ubuntu is HIGHLY RECOMMENDED
      • IP Addresses: Must have *BOTH* one IPv4 address *AND*one IPv6 address, dedicated to the IRC network *ONLY*.
      • Ports: Must be able to open as many ports as we need for the network.
      • Bandwidth link speed: Must have minimum 500 Mbps or greater network connectivity + throughput, 1 Gbps preferred.
      • Monthly bandwidth: Must have monthly bandwidth allotment of 500 GB or greater.
      • Disk: Must have at least 1 drive with minimum 40 GB space. Can be traditional HDD, or SSD of any kind. We can make case-by-case exceptions for a VPS as long as it has a minimum of 10 GB.
    • Run NTP/chrony (*NOT* ntpdate), and must prove it accurately synchronizes 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.
    • Have our domain name in its IRC server name (yourservername.xertion.org) - you can name it anything you like so long as it is appropriate and our domain name is present. We will NOT accept use of any other domain names in the IRC server name!
  • You MUST:
    • Be able to administer a Linux server entirely on your own, to at least the level of LPIC-1.
    • Be able to follow requests to install software components during initial link setup.
    • Speak English relatively fluently (any IRC operators you bring with you must also speak English).

Recommendations

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

  • No resource-intensive programs such as GUIs (X11), torrenting programs, etc running on the server
  • Specific GNU/Linux distribution is Ubuntu or Debian.
  • Ability to provide the network account on the server with temporary sudo access so we can install any software and libraries we may need for the IRCd ourselves.
    • Alternatively, install at least these packages: libp11-kit-dev, libgmp-dev, pkg-config, Perl, g++/gcc, make and all other essential compilation and linker tools, as well as a text editor like nano or vi(m).
  • No additional IRC operators other than yourself.
  • Server is part of the datacenter directly (HUGE plus!).

Form

As of 12-Nov-2024, Xertion is no longer accepting new server links, for an indefinite time period. We simply do not have any need with the current load. Therefore, this page and the information on it has been deprecated and is no longer relevant. Sorry about that! The form has thus been removed. We thank you for your interest.

Retrieved from "https://wiki.xertion.org/index.php?title=Linking&oldid=2513"