Internet Computer Wiki - User contributions [en]

RMU build Gen-1.5: IV. Best Practices - F. Enable GUI Access to OPNsense devices

2024-07-15T07:52:32Z

LouiseVelayo: add step to insert IPv6 host entries (this is needed for the rest of the steps in this page to work)

This page is part of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

Go back to the previous section: [[RMU build Gen-1.5: IV. Best Practices - E. Enable Remote Access to Servers Console|E. Enable Remote Access to Servers Console]]
==F. Enable GUI Access to OPNsense devices (Recommended)==
This process will guide you through adding access to the OPNsense GUI for device management over Teleport.

=== Add IPv6 Host Entries ===

# Add the IPv6 address of each OPNsense device to the end of the `/etc/hosts` file
<syntaxhighlight lang="bash">
<IPv6_of_1st_OPNsense_device> br2-fw01
<IPv6_of_2nd_OPNsense_device> br2-fw02
</syntaxhighlight>

=== Add Teleport Entries For GUI access to OPNsense firewalls ===

# Edit the <code>/etc/teleport.yaml</code> file on the RMU and add the following:<syntaxhighlight lang="yaml">
- name: <dc>-fw01
uri: https://[<IPv6_of_1st_OPNsense_device>]:443
public_addr: "<dc>-fw01.teleport.<dc>.<domain>"
insecure_skip_verify: true
rewrite:
redirect:
- "[<IPv6_of_1st_OPNSense_device>]"
- "<dc>-fw01.teleport.<dc>.<domain>"
labels:
dc: "<dc>"

- name: <dc>-fw02
uri: https://[<IPv6_of_2nd_OPNSense_device>]:443
public_addr: "<dc>-fw02.teleport.<dc>.<domain>"
insecure_skip_verify: true
rewrite:
redirect:
- "[<IPv6_of_2nd_OPNsense_device>]"
- "<dc>-fw02.teleport.<dc>.<domain>"
labels:
dc: "<dc>"
</syntaxhighlight>
# Reload the teleport server:<syntaxhighlight lang="yaml">
sudo systemctl reload teleport
</syntaxhighlight>
# Now, the GUI access should be visible inside the teleport[[File:Screen 1 teleport.jpg|800x800px]]
# And the OPNsense login page [[File:Screen 2 teleport.png|800x800px]]

RMU build Gen-1.5: IV. Best Practices - F. Enable GUI Access to OPNsense devices

2024-05-22T11:53:59Z

LouiseVelayo: fix indentation in teleport.yaml snippet

This page is part of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

Go back to the previous section: [[RMU build Gen-1.5: IV. Best Practices - E. Enable Remote Access to Servers Console|E. Enable Remote Access to Servers Console]]
==F. Enable GUI Access to OPNsense devices (Recommended)==
This process will guide you through adding access to the OPNsense GUI for device management over Teleport.

=== Add Teleport Entries For GUI access to OPNsense firewalls ===

# Edit the <code>/etc/teleport.yaml</code> file on the RMU and add the following:<syntaxhighlight lang="yaml">
- name: <dc>-fw01
uri: https://[<IPv6_of_1st_OPNsense_device>]:443
public_addr: "<dc>-fw01.teleport.<dc>.<domain>"
insecure_skip_verify: true
rewrite:
redirect:
- "[<IPv6_of_1st_OPNSense_device>]"
- "<dc>-fw01.teleport.<dc>.<domain>"
labels:
dc: "<dc>"

- name: <dc>-fw02
uri: https://[<IPv6_of_2nd_OPNSense_device>]:443
public_addr: "<dc>-fw02.teleport.<dc>.<domain>"
insecure_skip_verify: true
rewrite:
redirect:
- "[<IPv6_of_2nd_OPNsense_device>]"
- "<dc>-fw02.teleport.<dc>.<domain>"
labels:
dc: "<dc>"
</syntaxhighlight>
# Reload the teleport server:<syntaxhighlight lang="yaml">
sudo systemctl reload teleport
</syntaxhighlight>
# Now, the GUI access should be visible inside the teleport[[File:Screen 1 teleport.jpg|800x800px]]
# And the OPNsense login page [[File:Screen 2 teleport.png|800x800px]]

RMU build Gen-1.5: III. Maas - E. Configure CHCP Subnet on MaaS

2024-05-06T09:15:38Z

LouiseVelayo: fix typo "CHCP" -> "DHCP"

This page is part of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

Go back to the previous section: [[RMU build Gen-1.5: III. Maas - D. Initial Configuration of Maas Server|D. Initial Configuration of Maas Server]]
==E. Configure DHCP Subnet on MaaS==

# Select <code>Subnets</code> in the top Navigation Bar
# Select <code>10.10.100.0/24</code>
#*[[File:Screenshot 2024-01-05 at 12.32.48 PM.png|800px]]
#Select <code>Reserve Range</code> > <code>Reserve dynamic range</code>
#*[[File:Screenshot 2024-01-05 at 12.33.59 PM.png|alt=]]
#Set <code>Start IP address</code> to <code>10.10.100.53</code>
#Set <code>End IP address</code> to <code>10.10.100.99</code>
#Select <code>Reserve</code>
#*[[File:Screenshot 2024-01-05 at 12.35.41 PM.png|800px]]
# Select <code>Subnets</code> in the top Navigation Bar
#Select <code>untagged</code>
#*[[File:Screenshot 2024-01-05 at 12.32.48 PM.png|800px]]
#Select <code>Configure DHCP</code>
#*[[File:Screenshot 2024-01-05 at 12.41.42 PM.png|800px]]
# Ensure that <code>MAAS provides DHCP</code> is ticked
#Select <code>Provide DHCP from rack controller(s)</code>
#In the <code>Rack controller</code> dropdown select <code><dc>-maas</code> and select <code>Configure DHCP</code>
#*[[File:Screenshot 2024-01-05 at 12.45.04 PM.png]]

==Continue to next section: [[RMU build Gen-1.5: IV. Best Practices - A. Proxmox Security|IV. Best Practices - A. Proxmox Security]]==
Go to the index of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

RMU build Gen-1.5: III. Maas - C. Share Services Via Teleport

2024-05-06T09:05:40Z

LouiseVelayo: remove "<" and ">" from url to install teleport agent (including it results in an error).

This page is part of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

Go back to the previous section: [[RMU build Gen-1.5: III. Maas - B. Install Maas Software via APT|B. Install Maas Software via APT]]

== C. Share Services Via Teleport ==
Ref: https://www.youtube.com/watch?v=cvW4b96aPL0

=== On the <code>teleport</code> server: ===

# Create a short lived token to “invite” the MaaS application
#* <code>tctl tokens add --type=app,node --app-name=<dc>-maas --app-uri=<nowiki>http://localhost:5240</nowiki></code>
#* Take note of the <code>token</code> and <code>ca_pin</code> values

=== On the <code>maas server</code>: ===

# Install the Teleport agent:
#*<code>sudo curl <nowiki>https://goteleport.com/static/install.sh</nowiki> | bash -s <teleport version></code>
# create the Teleport application config:
#*<code>sudo teleport configure --output=file --proxy=<domain name>:443 --token=/var/lib/teleport/token --roles=app,node --app-name=<dc>-maas --app-uri=<nowiki>http://localhost:5240</nowiki></code>
#* [[File:Screenshot 2023-12-20 at 11.49.50 AM.png|800x800px]]
# Save the token generated on the Teleport server:
#*<code>sudo vi /var/lib/teleport/token</code>
#* [[File:Screenshot 2023-10-30 at 3.36.42 PM.png|800x800px]]
# Save the ca_pin generated on the Teleport server:
#*<code>sudo vi /var/lib/teleport/ca_pin</code>
#* [[File:Screenshot 2023-12-19 at 11.25.37 AM.png|800x800px]]
# Edit the <code>/etc/teleport.yaml</code> to update the <code>ca_pin</code> resource:
#*<code>sudo vi /etc/teleport.yaml</code>
#* Update the <code>ca_pin</code> resource with the file path to the token <code>/var/lib/teleport/ca_pin</code>
#* Add <code>labels:</code> section under <code>ssh_service:</code><syntaxhighlight lang="yaml">
labels:
dc: "<dc>"
login: "<admin user login>"
</syntaxhighlight>
#* Remove <code>commands:</code> section under <code>ssh_service:</code><syntaxhighlight lang="yaml">
commands:
- name: hostname
command: [hostname]
period: 1m0s
</syntaxhighlight>
#* Add <code>labels:</code> under <code>app_service: -> apps: -> <dc>-maas</code> service<syntaxhighlight lang="yaml">
- name: <dc>-maas
uri: http://localhost:5240
public_addr: ""
insecure_skip_verify: false
labels:
dc: "<dc>"
type: "maas"
</syntaxhighlight>
#* Sample <code>/etc/teleport.yaml</code> file<syntaxhighlight lang="yaml" line="1">
version: v3
teleport:
nodename: maas
data_dir: /var/lib/teleport
join_params:
token_name: /var/lib/teleport/token
method: token
proxy_server: teleport.<domain>:443
log:
output: stderr
severity: INFO
format:
output: text
ca_pin: /var/lib/teleport/ca_pin
diag_addr: ""
auth_service:
enabled: "no"
ssh_service:
enabled: "yes"
labels:
dc: "<dc>"
login: "maas"
proxy_service:
enabled: "no"
https_keypairs: []
https_keypairs_reload_interval: 0s
acme: {}
app_service:
enabled: "yes"
debug_app: false
apps:
- name: bo1-maas
uri: http://localhost:5240
public_addr: ""
insecure_skip_verify: false
labels:
dc: "<dc>"
type: "maas"
</syntaxhighlight>
# Add Teleport to <code>/etc/hosts</code>
#*<code>sudo vi /etc/hosts</code>
#* add an entry of <code>10.10.100.22 <Domain name of your teleport server></code> (what you made [[RMU build Gen-1.5: III. Maas - B. Install Maas Software via APT|here]])
#* [[File:Screenshot 2023-12-19 at 11.39.48 AM.png|800x800px]]
#* Save and quit the file
# Start the Teleport agent:
#* <code>sudo systemctl enable teleport</code>
#* <code>sudo systemctl start teleport</code>

==Continue to next section: [[RMU build Gen-1.5: III. Maas - D. Initial Configuration of Maas Server|D. Initial Configuration of Maas Server]]==
Go to the index of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

RMU build Gen-1.5

2024-04-17T07:50:26Z

LouiseVelayo: fix roman numerals (there were two "II")

''Process for building a new RMU to convert Gen-1 sites to Gen-1.5 sites.''

The following guide describes how DFINITY monitors their ICR Sites using the equipment that is already standard in most Gen-1.a sites. If you choose to follow this guide, completing everything up to [[RMU build Gen-1.5#IV. Best Practices|Best Practices]] will get you remote access to the RMU and the ability to add additional services via teleport. The [[RMU build Gen-1.5#IV. Best Practices|Best Practices]] section does introduce some services that greatly improve the overall experience such as being able to update firmware on all servers remotely.

Please be aware that this guide provides only the foundational steps for setting up a Gen1.5 RMU. It does not encompass comprehensive security hardening for the RMU, nor does it address system maintenance. Responsibility to ensure a secure and well-maintained environment rests with each Node Provider.

=== I. [[RMU build Gen-1.5: I. Prerequisites|Prerequisites]] ===

=== II. Proxmox ===
Once Proxmox is installed and reachable (Step II.A), the rest can be done remotely.
* A. [[RMU build Gen-1.5: II. Proxmox - A. Install Proxmox|Install Proxmox]]
* B. [[RMU build Gen-1.5: II. Proxmox - B. Update Proxmox|Update Proxmox]]
* C. [[RMU build Gen-1.5: II. Proxmox - C. Download CT Templates|Download CT Templates]]
* D. [[RMU build Gen-1.5: II. Proxmox - D. Download ISO Images|Download ISO Images]]
* E. [[RMU build Gen-1.5: II. Proxmox - E. Add LAN Network Device|Add LAN Network Device]]

=== III. Teleport ===
This service will provide you secure remote access to all of the services installed on your RMU.
* A. [[RMU build Gen-1.5: II. Teleport - A. Create Teleport CT|Create Teleport CT]]
* B. [[RMU build Gen-1.5: II. Teleport - B. Install Teleport Software|Install Teleport Software]]
* C. [[RMU build Gen-1.5: II. Teleport - C. Share RMU Services Via Teleport|Share RMU Services Via Teleport]]
* D. [[RMU build Gen-1.5: II. Teleport - D. Teleport Notes|Teleport Notes]]

=== IV. MaaS (Metal as a Service) ===

* A. [[RMU build Gen-1.5: III. Maas - A. Create Proxmox CT|Create Proxmox CT]]
* B. [[RMU build Gen-1.5: III. Maas - B. Install Maas Software via APT|Install MaaS Software via APT (for a Container)]]
* C. [[RMU build Gen-1.5: III. Maas - C. Share Services Via Teleport|Share Services Via Teleport]]
* D. [[RMU build Gen-1.5: III. Maas - D. Initial Configuration of Maas Server|Initial Configuration of MaaS Server]]
* E. [[RMU build Gen-1.5: III. Maas - E. Configure CHCP Subnet on MaaS|Configure DHCP Subnet on MaaS]]

=== V. Best Practices ===

* A. Recommended: [[RMU build Gen-1.5: IV. Best Practices - A. Proxmox Security|Proxmox Security]]
* B. Optional: [[RMU build Gen-1.5: IV. Best Practices - B. Install RACADM Tool on RMU|Install RACADM Tool On RMU (Dell Nodes)]]
* C. Recommended: [[RMU build Gen-1.5: IV. Best Practices - C. Dell OpenManage Enterprise|Dell OpenManage Enterprise (OME) (Dell Nodes)]]
* D. Recommended: [[RMU build Gen-1.5: IV. Best Practices - D. Update Firmware on SuperMicro Nodes|Update Firmware On SuperMicro Nodes]]
* E. Recommended: [[RMU build Gen-1.5: IV. Best Practices - E. Enable Remote Access to Servers Console|Enable Remote Access To Servers Console (Dell Nodes)]]
* F. Recommended: [[RMU build Gen-1.5: IV. Best Practices - F. Enable GUI Access to OPNsense devices|Enable GUI Access To OPNsense devices]]

=== VI. Reference Information ===

* [[RMU build Gen-1.5: V. Reference Information - Internal Network Layout|Internal Network Layout]]
* [[RMU build Gen-1.5: V. Reference Information - RMU Cabling|RMU Cabling]]
* [[RMU build Gen-1.5: V. Reference Information - Checking number of internal drives|Checking number of internal drives]]

ALLUSION BV

2024-04-09T06:16:44Z

LouiseVelayo: Upload PDFs

== Allusion Self-Declaration ==
SHA256 Allusion_SelfDeclaration.pdf: ce7805a31ef5f5830a9d6526762c6206b32e2450e82927d2840b57ae9caf7d28
[[File:Allusion SelfDeclaration.pdf|alt=Allusion - Self Declaration|thumb|Allusion - Self Declaration]]

== Allusion Proof of Identity ==
SHA256 Allusion_Incorporation_Certification_Predik.pdf: dec7a6a2654df1a7164b3dd2472f0fc1e13fabebbe7a5a85d490ee808426717a
[[File:Allusion Incorporation Certification Predik.pdf|alt=Allusion - Proof of Identity|thumb|Allusion - Proof of Identity]]

Louise Velayo

2024-04-09T06:15:08Z

LouiseVelayo: Upload PDFs and Add hash

== Self Declaration ==
SHA256 Hash: 2b425dbb1a6a4030157f0b0f9a6d2950f67b1fe72fb68ed088a6f3e4cd735694 Self-Declaration.pdf
[[File:Louise Velayo - Self Declaration.pdf|alt=Louise Velayo - Self Declaration|thumb|Louise Velayo - Self Declaration]]

== Proof of Identity ==
SHA256 Hash: 20b9d99195d7a157833fc399d6c94c05b6ba80fc43095f88002eab9b023dcebc Extract_1033133963.pdf
[[File:Extract 1033133963.pdf|alt=Louise Velayo - Proof of Identity|thumb|Louise Velayo - Proof of Identity]]

File:Extract 1033133963.pdf

2024-04-02T20:00:23Z

LouiseVelayo:

Proof of Identity - Louise Velayo

File:Louise Velayo - Self Declaration.pdf

2024-04-02T19:57:36Z

LouiseVelayo:

Louise Velayo - Self Declaration

Node Provider Self Declarations

2024-04-02T19:56:13Z

LouiseVelayo: add Louise Velayo Self Declaration Page

<blockquote>'''''NOTE: Please try to keep entries in this document alphabetically sorted, to reduce conflicts in edits.'''''

</blockquote>

[[43rd Big Idea Films, LLC]]

[[ACCUSET SOLUTIONS]]

[[Aitubi AG]]

[[Altimist Ltd]]

[[ALLUSION BV]]

[[ANYPOINT PTY LTD]]

[[AVRVM AG]]

[[Artem Horodyskyi|ARTEM HORODYSKIY]]

[[Bianca-Martina Rohner]]

[[Bigger Capital|Bigger Capital Pty Ltd]]

[[Bitapp]]

[[Bitmoon]]

[[Bohatyrov Volodymyr]]

[[Buldakova Rehina]]

[[CarbonTwelve]]

[[CocoMango LLC]]

[[Conic Ventures]]

[[Eastman_Ventures_Pty_Ltd|Eastan_Ventures_Pty_Ltd]]

[[Exaion]]

[[User:FenexLLC|FenexLLC]]

[[Ferndale International]]

[[Geeta Kalwani]]

[[GeoNodes LLC]]

[[George Bassadone]]

[[Geodd Pvt Ltd]]

[[User:James Wang|HashQuark]]

[[HoneyComb Capital|HoneyCob Capital]]

[[Icaria_Systems_Pty_Ltd|Icaria_Systes_Pty_Ltd]]

[[Illusions in Art Ltd]]

[[InfoObjects Inc]]

[[Ivanov Oleksandr]]

[[Karel Frank]]

[[Kontrapunt (Pty) Ltd]]

[[Krishna Enterprises]]

[[Krzysztof Żelazko]]

[[Katerina Karapuz]]

[[Louise Velayo]]

[[Ludens LLC]]

[[Lukas Helebrandt]]

[[Marc Johnson]]

[[Marvelous Web3]]

[[Maksym Ishchenko]]

[[:File:NODE-PROVIDER-SELF.pdf|ML SOLUTIONS LTD]]

[[Michael_and_Dominik_Peterer]]

[[Mariano Stoll]]

[[Neptune Partners]]

[[NODAL CAPITAL]]

[[Nova_LCC]]

[[NoviSystems|NoviSystems, LLC]]

[[Nataliia Nykyforak]]

[[Natalia Kulesha]]

[[Nikola Nikov]]

[[OneSixtyTwo Digital Capital]]

[[User:Soekawat|Origin Game]]

[[Paul Creasey]]

[[PindarTechnologyLimited]]

[[User:Powermetacorp|Power Meta Corporation]]

[[Privoxy Solutions, LLC.]]

[[Rivram Inc]]

[[Stamper Co., Ltd.]]

[[Serenity lotus limited]]

[[Technical University of Munich]]

[[Timur Rakhimzhan]]

[[Wolkboer (Pty) Ltd]]

[[WMA Investments Limited]]

[[VirtualHiveLtd|Virtual Hive Ltd]]

[[Vladyslav Popov]]

[[Zaboo d.o.o.]]

[[Zondax AG]]

[[User:Web3game|Web3game]]

[[User:Zenithcode|Zenith Code LLC]]

[https://wiki.internetcomputer.org/wiki/User:ZTLC_PTE_Ltd ZTLC_PTE_Ltd]

<references />

ALLUSION BV

2024-04-02T19:30:22Z

LouiseVelayo: add sha256 hash and pdf of allusion's self declaration and proof of identity documents

== Allusion Self-Declaration ==
SHA256 Allusion_SelfDeclaration.pdf: ce7805a31ef5f5830a9d6526762c6206b32e2450e82927d2840b57ae9caf7d28

== Allusion Proof of Identity ==
SHA256 Allusion_Incorporation_Certification_Predik.pdf: dec7a6a2654df1a7164b3dd2472f0fc1e13fabebbe7a5a85d490ee808426717a

File:Allusion Incorporation Certification Predik.pdf

2024-04-02T19:29:36Z

LouiseVelayo:

Allusion Self declaration

File:Allusion SelfDeclaration.pdf

2024-04-02T19:26:49Z

LouiseVelayo:

Allusion SelfDeclaration

RMU build Gen-1.5: II. Proxmox - A. Install Proxmox

2024-03-11T13:46:42Z

LouiseVelayo: Aviate Labs has created a brief instructional video to complement this step in the runbook. We're eager to share it with Node Providers who are interested in undergoing this procedure, providing a clear understanding of the on-site process. Additionally,

This page is part of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

Go back to the previous section: [[RMU build Gen-1.5: I. Prerequisites|Prerequisites]]
Have a quick look at this [https://www.youtube.com/watch?v=TvieZdDwSug instructional video] that was made based on the steps below!

==Install Proxmox==

#Insert your Proxmox USB drive that you made earlier into the RMU
#Ensure the RMU is powered off
#Plug the USB into the RMU
#Start the server and press the F11 key repeatedly to reach the Boot Menu.
#*[[File:01 - BIOS Boot Screen.jpg|800x800px]]
#Select the Flash Drive and press enter (screen may differ)
#*[[File:02 - Select USB Boot Media.jpg]]
#Select <code>Install Proxmox VE (Terminal UI)</code> and press enter
#*[[File:IKVM capture (31).jpg|800x800px]]
#Select <code>I agree</code> and press enter
#*[[File:04 - EULA.jpg|800x800px]]
#Select <code>Advanced options</code> and press enter
#*[[File:05 - Install Boot Disk.jpg|800x800px]]
#Select <code>ext4</code> and press enter to change this setting
#*Note: For SuperMicros with two internal drives , select <code>ZFS (RAID 1)</code> for SuperMicros with one drive select <code>ZFS (RAID 0)</code> <br />[[File:06 - Install Boot Disk - Select ZFS (RAID1).jpg|800x800px]]
#Select <code>Ok</code> and press enter
#*[[File:07 - Install Boot Disk - Accept ZFS.jpg|800x800px]]
#Select <code>Next</code> and press enter
#*[[File:08 - Start Installer.jpg|800x800px]]
# Select your Country, Timezone (Recommended UTC), and Keyboard layout
#*[[File:09 - Select Country.jpg|800x800px]] [[File:10 - Select System Timezone.jpg|800x800px]] [[File:11 - Select Keyboard Type.jpg|800x800px]]
# Select <code>Next</code> and press enter
#*[[File:12 - Continue Installer.jpg|800x800px]]
#Enter in a password, please make this a strong password, and store it in your password manager
# Enter in an email to receive alerts
#Select <code>Next</code> and press enter
#*[[File:13 - Set Root Password and Email.jpg|800x800px]]
#These instructions assume that you followed the RMU Cabling instructions earlier in the document
#Select the <code>Management Interface</code> and change it to <code>eno1</code> and press enter
#For <code>Hostname (FQDN):</code> input*<code><dc>-rmu.<domain></code> (if supporting multiple sites).* This will be the fully qualified domain name (FQDN) name for the RMU itself as added to the DNS in the Prerequisites section.
#For <code>IP address (CIDR):</code> enter the <code>External IP</code> and <code>Netmask</code> determined in the Prerequisites section
#*If you are unsure of what IP address, Netmask or Gateway to use, please contact your ISP.
#For <code>Gateway address:</code> enter in your public <code>Gateway</code> determined in the Prerequisites section
#*If you are unsure of what IP address, Netmask or Gateway to use, please contact your ISP.
#For <code>DNS Server</code> address: enter in <code>1.1.1.1</code>
#*[[File:IKVM capture (29).jpg|800x800px]]
#Select <code>Next</code> and press enter
#*[[File:IKVM capture (28).jpg|800x800px]]
#Look over to ensure all information is correct
#Select <code>Install</code> and press enter. Make sure it is checked to reboot after installation
#*If you set the boot order to boot off of the USB, then remove it before the reboot
#*[[File:IKVM capture (30).jpg|800x800px]]
#You should now see the login screen. If need be, you can login as root and use the password you set earlier
#Take note of the IP address and port shown on this screen
#*[[File:17 - Console Login.jpg|800x800px]]

== Continue to next section: [[RMU build Gen-1.5: II. Proxmox - B. Update Proxmox|B. Update Proxmox]] ==
Go to the index of the [[RMU build Gen-1.5|Gen-1.5 RMU build runbook]].

Node Provider Matrix channel

2023-11-30T15:19:12Z

LouiseVelayo: add DC's in which Allusion operates in

There is an open Matrix room (channel) that is intended to be a forum for potential and existing Node Providers as well as anybody else who would like to follow the node provider discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org

The runs runs on the open, public, and decentralized Matrix network. Matrix [https://matrix.org/clients/ has many clients] you can use. One of the popular clients is element.io, which is very similar to Slack, and offers a web UI, a [https://element.io/download desktop app], and a mobile app.

We strongly recommend that you add [https://ems-docs.element.io/books/element-cloud-documentation/page/element-settings an email address in the Element Profile settings] and to [https://element.io/help#settings3 enable notifications for missed messages].

If you are a Node Provider, please also add your Node Provider contact details on the Matrix room, to facilitate communication.
{| class="wikitable"
|+
!Node Provider Name
!Node Provider Id
!DC list
!Matrix aliases
|-
|1G
|7k7b7-4pzhf-aivy6-y654t-uqyup-2auiz-ew2cm-4qkl4-nsl4v-bul5k-5qe
|fm1
|
|-
|43rd Big Idea Films
|sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe
|hu1
|
|-
|87m Neuron, LLC
|eipr5-izbom-neyqh-s3ec2-52eww-cyfpg-qfomg-3dpwj-4pffh-34xcu-7qe
|pl1, dl1, lv1
|
|-
|9Yards Capital
|spp3m-vawt7-3gyh6-pjz5d-6zidf-up3qb-yte62-otexv-vfpqg-n6awf-lqe
|jv1, ch2, ny1
|
|-
|ACCUSET SOLUTIONS
|cp5ib-twnmx-h4dvd-isef2-tu44u-kb2ka-fise5-m4hta-hnxoq-k45mm-hqe
|gn1
|
|-
|Adam Dymecki
|n32q7-33lmk-m33tr-o5ltb-po6cb-tqqrr-2x6wp-pzhw7-ymizu-o3fyp-sqe
|
|
|-
|A Dog's Boutique, LLC
|uvawj-nnt3i-4ch3a-hruy4-hyfjn-7owvl-wgkli-uq2hd-e6lkq-v4b2o-4ae
|
|
|-
|Allusion
|rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae
|an1, br1, br2
|<nowiki>Paul De Cannière (Allusion), Roald | Aviate Labs, Louise Velayo | Aviate Labs</nowiki>
|-
|Anonstake
|kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae
|
|
|-
|ANYPOINT PTY LTD
|fwnmn-zn7yt-5jaia-fkxlr-dzwyu-keguq-npfxq-mc72w-exeae-n5thj-oae
|
|
|-
|Archery Blockchain SCSp
|7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe
|
|
|-
|Arjay LLC
|l2kri-jarwr-7whc4-pjdpn-n6hlb-45ltr-l6ghm-twttl-pcsvt-rynko-dqe
|
|
|-
|Artem Horodyskyi
|diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe
|
|
|-
|Aspire Properties
|2byzn-q2crt-hgczo-eruff-6p7af-pemor-n2z4z-6d2sd-wvdqa-yqvxb-mqe
|
|
|-
|Bigger Capital
|7a4u2-gevsy-5c5fs-hsgri-n2kdz-dxxwf-btcfp-jykro-l4y7c-7xky2-aqe
|me3, aw1
|Dallas W
|-
|Bitmoon
|mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe
|
|
|-
|Blockchain Development Labs
|7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae
|
|
|-
|BlockTech Ventures, LLC
|ks7ow-zvs7i-ratdk-azq34-zio2b-gbekj-qjicg-pfhp3-ovhgu-k5qql-dae
|
|
|-
|BLP22, LLC
|sma3p-ivkif-hz7nu-ngmvq-ibnjg-nubke-zf6gh-wbnfc-2dlng-l3die-zqe
|
|
|-
|Bohatyrov Volodymyr
|dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae
|
|
|-
|Boolean Bit, LLC
|qdj4d-76lh3-w2q5i-kwjcd-643pq-pk42d-cziag-4hkau-35gib-m7s33-6qe
|
|
|-
|Brener, Inc.
|2wxxr-qwylo-n7dhz-6co6m-iektd-vl7dn-ocvyc-xazaf-hbfxq-66spe-aae
|
|
|-
|Conic Ventures
|i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe
|
|
|-
|Coplus Limited
|jz47c-irtey-dr2nb-wienh-emhaz-jo6ua-gsbho-t2z5j-l7kbf-5i7p5-5ae
|
|
|-
|CRM52 Systems, LLC
|7nxxb-6qgm4-fftx3-xkwpj-sjrcm-tzmk5-dvuqk-l4ei4-3hvii-scwnj-tae
|
|
|-
|DFINITY Operations SA
|bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe
|mr1, sh1, zh2
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DFINITY USA Research LLC
|lq5ra-f4ibl-t7wpy-hennc-m4eb7-tnfxe-eorgd-onpsl-wervo-7chjj-6qe
|
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DFINITY USA Research LLC
|r2qgy-abcek-yc2ot-3powq-gayr6-4dibc-jvvfl-ri376-gmfmw-u2v7w-4qe
|bo1
| Katie Peters, sasa-tomic, Sven Fischer, eerokelly, garym-dfn, Radek Zakrzyk, Samuel Howard, Tomas Hlavacek, dfinityian, andrewbattat, Rudd-O, tthebst
|-
|DRMxTech Enterprises, LLC
|olgti-2hegv-ya7pd-ky2wt-of57j-tzs6q-ydrpy-hdxyy-cjnwx-ox5t4-3qe
|
|
|-
|Exaion
|xo7ih-nswlt-hbq3n-v5ixi-etu7j-sasg6-fjf4p-zx6or-cc7c3-pnh7t-2ae
|
|
|-
|Fidgitville Ventures LLC
|ob633-g55bt-y6pu5-5iby6-jmcvi-oylqs-q6ahw-cvecq-5ckeh-m4wws-nae
|
|
|-
|Finteck LLC
|x3zyd-pkcbf-5n3w2-n7uov-2qrbt-d3kfn-ojdd7-pxog5-vpqnt-6lex5-fqe
|
|
|-
|Fractal Labs AG
|wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae
|
|
|-
|Fritz Huie
|67gkg-gkgzz-g2ubz-3cc6h-jr3zm-twsii-7i325-r3gzr-kp2kh-dwxg6-pqe
|
|
|-
|FUM Capital, LLC
|zgupw-boshs-mg6kz-2ciwm-upk7g-igjpn-75t3p-np6g4-47l7q-nuefa-6qe
|
|
|-
|Geodd Pvt Ltd
|eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe
|
|
|-
|GeoNodes LLC
|5wedd-dwi2c-ybr2g-benav-qlgc7-vifbt-qz3ml-ymopp-uaide-ilpkb-tae
|
|
|-
|George Bassadone
|lksfo-j2smg-76m4c-jwasz-e5exl-gptsk-jvtc7-zvm34-ezk4g-p2xjt-dqe
|
|
|-
|Giant Leaf, LLC
|wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae
|
|
|-
|Goat, LLC
|p6fou-ngmgk-rxc6t-7ckzz-hojr2-kk6r3-xnlrk-ewzvu-g6xms-rfafz-zae
|
|
|-
|Goodsir, LLC
|myrs2-bc6j6-mydpr-2jmli-l45mu-35ybt-c34mo-kjpve-zmaao-ajusy-nqe
|
|
|-
|Honeycomb Capital (Pty) Ltd
|nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae
|
|honeycombcapital
|-
|Iancu Aurel
|i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae
|
|
|-
|Icaria Systems Pty Ltd
|ihbuj-erwnc-tkjux-tqtnv-zkoar-uniy2-sk2go-xfpkc-znbb4-seukm-wqe
|mn2
| Icarus
|-
|IC Pros
|srga3-cikqa-srnxx-rwejf-672jj-5o6qy-tuzsa-khds3-2ofjw-5gnew-mae
|
|
|-
|Illusions In Art (Pty) Ltd
|optdi-nwa4m-hly3k-6ua4n-sqyxf-yahvb-wps77-ddayn-r7zcz-edla5-7qe
|
|
|-
|InfoObjects
|7ws2n-wqorv-vmo4m-5e222-n42c3-hk43s-ei3kp-4hpbn-xlkzo-jgv7i-tqe
|
|
|-
|Internet Computer Explorer
|i7v7g-cwjtl-gzd2s-nt2ko-4d5su-vh64h-bqu4h-rio26-tbaej-dtj6d-fae
|
|
|-
|Ivanov Oleksandr
|ivf2y-crxj4-y6ewo-un35q-a7pum-wqmbw-pkepy-d6uew-bfmff-g5yxe-eae
|pa1,ma1, bt1, rg1, wy1, li1, ta2
|alexnod
|-
|Jeffrey Schnettler
|5zqo2-omblo-i7knq-qyrfu-mjccn-tljyd-qslab-b7ukn-7tshi-pbeke-pae
|
|
|-
|Jimmy Quach
|dzxyh-fo4sw-pxckk-kwqvc-xjten-3yqon-fm62b-2hz4s-raa4g-jzczg-iqe
|
|
|-
|Jonathan Ziskind
|qcs4o-yswwp-7ozhg-m2ago-ytjyl-zlckb-raykw-fi5hl-cflyt-4beyv-zqe
|
|
|-
|Joseph Stella
|f5wg2-kl4aq-cj4ym-nq7ul-i4kxy-t4x3x-yiyc5-3wlu6-opzwd-o5qes-hae
|
|
|-
|Karel Frank
|unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe
|jb1, jb2, sc1
|lerak
|-
|KLAW Media, LLC
|pcwis-xaq3p-xvasz-5cfws-oelni-xs72v-acbwz-umxnq-nb2bc-ziyuu-sqe
|
|
|-
|Kontrapunt (Pty) Ltd
|py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe
|
|
|-
|Krishna Enterprises
|zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae
|
|
|-
|Krishna Sriram
|sajvr-l5iok-rj6c2-r76co-k2mde-d3kir-pnmjs-443f6-lxto4-pu55q-uae
|
|
|-
|Lauren Dymecki Chickvara
|abscc-3lezh-oezci-5i3kz-pkwlc-ozz3r-5wv4n-htujn-rtajh-6cgyv-jae
|
|
|-
|Lukas Helebrandt
|efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe
|bn1
|@lukas:greensteps.cn
|-
|Luke Jacobson
|6dwst-olsa5-tagsr-jylgj-oicju-rf42e-o7job-gedre-fgoxt-7br62-jqe
|
|
|-
|Maksym Ishchenko
|4r6qy-tljxg-slziw-zoteo-pboxh-vlctz-hkv2d-7zior-u3pxm-mmuxb-cae
|bn1,ma2,bt1,rg1, wa1,ba1,ta1
|77676m
|-
|Marc Johnson
|xfvlz-qkgs4-xyeyx-lbke5-aarza-ovi52-wzpxl-3p27l-ov6ki-csxv6-qqe
|
|
|-
|Marvelous Web3
|7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe
|
|
|-
|Mary Ren
|vdzyg-amckj-thvl5-bsn52-2elzd-drgii-ryh4c-izba3-xaehb-sohtd-aae
|
|
|-
|MB Patrankos šūvis
|4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae
|
|
|-
|Mika Properties, LLC
|3siog-htc6j-ed3wz-sguhu-2objz-g5qct-npoma-t3wwt-bd6wy-chwsi-4ae
|
|
|-
|MI Servers
|izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe
|
|
|-
|Mitchel Guerra
|4anlt-yam7x-eodmx-ik7mo-nl3kx-t35fj-52hfy-uv4jj-u2iea-ntg76-pqe
|
|
|-
|Moon Block Ventures
|sdal5-w2c3d-p3buy-zieck-2wyuj-eu5bn-rkfe6-uuspi-o4n2b-gpei7-iae
|
|
|-
|Mostly Wholesome, Inc.
|ou3o7-akyjc-ldwd5-anyjn-l2buz-cwhbg-nehlc-abkde-qtc7w-fozdi-hae
|
|
|-
|Neptune Partners
|4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae
|
|
|-
|NoviSystems, LLC
|hk7eo-22zam-kqmsx-dtfbj-k5i6f-jg65h-micpf-2cztc-t2eqk-efgvx-vqe
|ny2, fm1
|novisystems
|-
|OneSixtyTwo Digital Capital
|6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe
|
|
|-
|Origin Game
|cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe
|
|
|-
|Palnu_Logistics
|pfcmh-uqedc-ijkjz-mdo35-bvprd-2vtlw-ktod5-npgfc-pgbq4-akaen-uqe
|
|
|-
|Paul Legato
|yr4eg-kwk3m-q44vj-ale35-2mtxk-5dyn7-vgppx-z6tcw-kzo4o-ezpm5-fqe
|
|
|-
|Peggy Shafaghi
|72idx-a7c3y-nrcwc-lboj4-mmsas-sfdpm-gq23i-h2yuy-lykcj-vrxn2-jqe
|
|
|-
|Philippe Chapparone
|2c4m6-25hos-qroi3-mk4aj-nog6s-zbzcv-ccpcc-cbv7s-sjy6p-bv3g5-fae
|
|
|-
|Pindar Technology Limited
|r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae
|
|
|-
|Power Meta Corporation
|4fedi-eu6ue-nd7ts-vnof5-hzg66-hgzl7-liy5n-3otyp-h7ipw-owycg-uae
|
|
|-
|Prayit Jain
|waj5k-wlyvv-jbj4n-vxwjm-dmkyg-uw2nl-ggojp-34kln-wgx3n-d7xih-5qe
|
|
|-
|Privoxy Solutions, LLC
|trxbq-wy5xi-3y27q-bkpaf-mhi2m-puexs-yatgt-nhwiy-dh6jy-rolw5-zqe
|
|
|-
|Rachel Dymecki
|chnsu-yaqt5-6osy5-au4zn-li6yu-nufmw-dewrt-utkiu-twd76-ujypw-rae
|
|
|-
|Richard Ma
|egb3e-rzi2e-vpsmm-akysp-l2owk-4dgst-b5hmg-xrkwa-cr3uk-zlzds-mae
|
|
|-
|Richard Suarez
|cmcjw-6c5ve-4zjnt-lipnl-2lp43-oh5wk-ewciz-xyvnv-m2rz5-hkm6a-hqe
|
|
|-
|Ricky Sidhu
|q22bo-3uyqa-jvtpt-gapjk-pseor-esx4a-zyb74-vzea4-o7nx2-tafgq-hae
|
|
|-
|Rishi Sachdev
|6tg64-cdfoh-kl35i-p6qti-sose3-746lr-jk5ex-phuvu-jfu3d-5svwa-7qe
|
|
|-
|Rivram Inc
|ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae
|nm1,mtl1
|@ritvick
|-
|Rodney Zorrilla
|bgprp-b2mnt-ci5in-57vuk-p7qvo-tj2tb-5w5su-qwenk-gbe77-mnuiq-sqe
|
|
|-
|Ronnie Pellizzari
|wwxec-c2gd2-bu5on-ktpwz-z2ph3-vlr4p-m7ztf-6ck7r-nt3r4-fxbdq-mae
|
|
|-
|Russell Ford
|p5jx4-lsrog-ep5o3-5uudg-opdg3-ur45z-xeefi-4ejfz-47t2k-riwfv-dae
|
|
|-
|Scott Hallock
|i6sxi-fks25-viets-mboa7-3i23b-qeocf-e57qj-ar6vy-2mchu-xb5vp-aqe
|
|
|-
|Shelburne Ventures, LLC
|a24zv-2ndbz-hqogc-ev63f-qxnpb-7ramd-usexl-ennaq-4om4k-sod6u-gae
|
|
|-
|Staking Facilities
|niw4y-easue-l3qvz-sozsi-tfkvb-cxcx6-pzslg-5dqld-ooudp-hsuui-xae
|
|
|-
|Starbase
|sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae
|
|
|-
|Starseed Technology, LLC
|ruxoj-jnqql-uau6o-xwrtb-ufde4-geddn-mnhni-wpew4-zhzi5-xjrxi-lqe
|
|
|-
|Sygnum Bank
|6r5lw-l7db7-uwixn-iw5en-yy55y-ilbtq-e6gcv-g22r2-j3g6q-y37jk-jqe
|
|
|-
|Tomahawk.vc
|ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae
|
|
|-
|Virtual Hive Ltd
|wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae
|
|
|-
|Vladyslav Popov
|3oqw6-vmpk2-mlwlx-52z5x-e3p7u-fjlcw-yxc34-lf2zq-6ub2f-v63hk-lae
|pa2,ma2,si1,rg1, wy1,li1,ta2
|vladyslav_p
|-
|Wancloud limited
|g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe
|hk1
|<nowiki>hashbamboo | HashQuark, Daniel | HashQuark</nowiki>
|-
|Web3game
|64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe
|
|
|-
|William Zelver
|usau7-upgoh-sg464-6qnso-lud42-nxho6-ith26-a2jhq-q5bgy-ajeou-4ae
|
|
|-
|Wolfhound LLC
|6mifr-stcqy-w5pzr-qpijh-jopft-p6jl3-n2sww-jhmzg-uzknn-hte4m-pae
|
|
|-
|Wolkboer (Pty) Ltd
|mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae
|jb3
|wolkboer
|-
|Zondax AG
|hzqcb-iiagd-4erjo-qn7rq-syqro-zztl6-cpble-atnkd-2c6bg-bxjoa-qae
|
|
|-
|ZTLC PTE LTD
|xsrwt-tl3tk-n3aya-rafh3-ta6xu-eviw5-ae5dg-2f3bf-siaab-wdwdo-dqe
|
|
|}

Node Provider Alerting Options

2023-11-06T09:04:41Z

LouiseVelayo: Add links to different versions of node monitor: the free hosted version and the open source code for NPs to clone and host on their own.

Node providers will want to set up alerting so they know as soon as one of their nodes or their data center goes down. As the owner of both the nodes and the data center, node providers have the freedom to set up this alerting using any method that suits their needs. Below are some options that can be used and built upon:

Node Monitor by [https://www.aviatelabs.co/ Aviate Labs]:

* [https://www.aviatelabs.co/node-monitor Free hosted version] - sign up and receive instant monitoring with zero setup required.

* [https://github.com/aviate-labs/node-monitor Open source code] - set up and host the application yourself.

[https://github.com/dfinity/nodeprovider-scripts/blob/main/node_monitor.sh DFINITY's basic Node Monitor]

Node Provider Documentation

2023-08-09T08:14:11Z

LouiseVelayo: Added link to "How to become a node provider: a step-by-step guide" page

==Introduction==

ICP runs on a [[Sovereign Network]] that is a governed by a DAO using [[Deterministic Decentralization | deterministic decentralization]] to maximize its [[Decentralization in ICP: Infrastructure Governance | decentralization]]. To be part of the ICP infrastructure, any potential node providers can submit NNS proposals to the DAO controlling the ICP blockchain. ICP community then votes on whether to include the node provider. Node providers invest in and operate the node hardware that powers the Internet Computer. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.

This article is the hub for ICP node provider documentation.


== How to become a Node Provider for the Internet Computer ==
Interested in becoming a Node Provider? Read this: [[How to Become a Node Provider: A Step-by-Step Guide]].

==Node Provider tokenomics & remuneration==
Node providers receive rewards (remuneration) for operating node machines that run the IC network. The single source of truth for node provider rewards is the NNS, where changes can only be made through NNS proposals adopted by the IC community.

This page summarizes the current node provider rewards and serves to discuss proposals for future reward models: [[Node Provider Remuneration]]

==Node machine hardware requirements==

Node machines on ICP network need to keep up with the requirements of the network, please see: [[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen-2 Node Machine Hardware]].

==Submitting proposal to join the network==

As part of the process to become a node provider, a candidate node provider has to declare their intent and self-identify so the ICP DAO can make an informed decision. Please see [[Node Provider Self-declaration]] for more info.

==Onboarding for accepted node providers==

===Gen-2 documentation===

These articles are for candidate node providers considering becoming node providers or node providers recently accepted by the ICP DAO. The term "Gen-2" refers to "Generation 2", which is the current set of protocols for new node providers.

* [[Node Provider Machine Hardware Guide]]
* [[Node Provider Networking Guide]]
* [[Node Provider Remuneration]]
* [[Node Provider Self-declaration]]
* [[Node Provider Onboarding]]
* [[IC-OS Installation Runbook]]
* [[Node Provider FAQ]]

===Node provider troubleshooting===
* [[Node Provider Troubleshooting]]

===Gen-1 documentation===
The first batch of ICP node providers joined under Gen-1 (Generation 1). These documents are for those legacy node providers.

* [[NitroKey HSM installation runbook|Legacy Node Onboarding for Gen-1 data centers set up with HSMs]]

==See also==

* [[Node Provider Matrix channel]]

How to Become a Node Provider: A Step-by-Step Guide

2023-08-09T07:09:03Z

LouiseVelayo: Added a visual to accompany the text that is already on the wiki.

This page serves as a guide designed to facilitate the process of becoming a Node Provider (NP) for the Internet Computer (IC) network. For those seeking to contribute to the network's decentralized infrastructure by hosting operational nodes, this guide offers a structured and informed approach. Drawing upon insights sourced from the IC wiki and discussions within the IC Forum, this page provides a visual overview of the step-by-step journey, accompanied with text that gives more information about each step. By adhering to this guide, potential NPs will confidently navigate the intricacies, ensuring they are well-prepared to establish their role as NPs for the IC.

NPs who have successfully completed this onboarding process are strongly encouraged to contribute their insights and wisdom to enhance this resource. Your valuable contributions can further enrich the guide. Collaboration is at the core of the Internet Computer community, and your participation can contribute to the success of new NPs!
[[File:IC NP roadmap v4.png|alt=Outline of the Procedure to Become an Internet Computer Node Provider|center|frameless|1063x1063px|Outline of the procedure to become an Internet Computer Node Provider]]

== 1. Gather DC and ISP quotes ==
The initial step in becoming a Node Provider (NP) revolves around establishing partnerships with Data Center(s) (DC) and Internet Service Provider(s) (ISP) to host operational IC nodes. For ensuring decentralization, it is highly beneficial to distribute nodes across multiple countries and data centers. Additionally, proposing new countries and/or data centers for hosting nodes can increase the likelihood of acceptance during the later stage (step 6). Although not as stringent, a similar principle applies to the selection of ISPs.

At present, there are no mandatory technical certifications required for DCs, but this might change in the future. The sole requirement is verifiability of the DC's location once its proposal is submitted in step 6, as stated in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/180 forum post].

'''Suggested approach:'''

# Visit the world map on the homepage of the [https://dashboard.internetcomputer.org/ IC dashboard]. Identify countries where there are no nodes in operation. For decentralization purposes, it is highly recommended to set up nodes in these countries.
# Check the “Data centers<nowiki>''</nowiki> page of the [https://dashboard.internetcomputer.org/centers IC dashboard] for the country of interest. Verify if there are any DCs in that region with IC nodes present. For better network decentralization, opt for data centers companies different from those already hosting IC nodes.
# Contact DCs and request a quote. This [https://docs.google.com/document/d/1-9rj9cEgOqMM3ZzXcniGfAyYkdN9oI8PngflokGazrY/edit?usp=sharing template] is an example request. Feel free to adapt it to your (local) needs.
#* The template is quite comprehensive but the key information that should be included in the DC’s quote are:
#*# Monthly Recurring Costs (MRC) of colocation (renting rack space within the data center)
#*# Non-Recurring Costs (NRC), like one-off setup fees
#*# Cost structure for the services provided by their hands & eyes team (if present)
# Contact ISPs and request a quote. This [https://docs.google.com/document/d/17b-OCFMitFGvCzcHX3Qopjyag2cB0GaZkv6wrIQEtZk/edit?usp=sharing template] is an example request. Feel free to adapt it.
#* Similar to the DCs, at this stage you are only interested in the MRC and NRC.
# If possible, visit the sites of the most promising data centers to assess suitability and professionalism of their staff.
# Utilize the received quotes to make a financial analysis according to the [[Node Provider Remuneration|Node Provider Remuneration Model]]. This will aid in determining the optimal number of nodes to host.
# Finalize a provisional contract with a selected data center. This contract can serve as supporting documentation for your declaration as a node provider (step 4).

To assist with any follow-up questions from data centers regarding the technical aspects of your project, refer to the documentation provided below.

# [[Node Provider Networking Guide|Networking guide]]
# [[Node Provider Machine Hardware Guide|Hardware specifications]]

== 2. Establish a (local) legal entity ==
While '''not mandatory''', establishing a legal entity as a Node Provider is highly recommended.

* Creating a legal entity provides protection in the event of any legal issues, debts, or liabilities related to the operation of these nodes. It safeguards your personal assets from being utilized to resolve such discrepancies.
* Moreover, operating under a legal entity enhances your credibility, increasing the likelihood of your proposal being accepted by the community.
* With a legal entity in place, you gain the ability to enter into contracts and agreements using the entity's name, offering an additional layer of protection for the legal relationships involved in running an IC node, such as the DC contract.

However, it's worth noting that running a node as an individual is also possible. The choice ultimately lies with you.

== 3. Order and setup your hardware wallet ==
As part of the onboarding process (Step 6), '''you will require a hardware wallet.''' Once you have acquired your hardware wallet, you can proceed to configure it by following the instructions provided [[Node Provider Onboarding#3.%20Setup%20your%20hardware%20wallet|here]]. Once these initial setup steps are finished, you will be prepared to move forward with the actions outlined in step 6.

== 4. Preparation of documents for NP self declaration ==
'''Anyone interested in becoming a node provider is required to submit a proposal to be voted on by the community.''' This begins with a self declaration where the following documents need to be prepared and submitted.

* Self declaration - A document to declare you intent to become a node provider
* Identity proof - Any document that proves the identity of the signers of the self-declaration to the community. Examples include:
** Proof of company registration through an official database
** Company registration/license
** ID/Passport

'''Both documents are mandatory.''' Templates for these documents can be found [[Node Provider Self-declaration|here]].

Some supporting documents that are not mandatory but would strengthen any node provider self declaration include:

* Company/personal website
* Link to Github account/organization
* Datacenter contract

'''Publish the documents to the [[Node Provider Self-declaration|self declaration page]] on the IC wiki.'''

== 5. Node provider onboarding to the Network Nervous System (NNS) ==
Now that you have your hardware wallet and also a DC contract in place, you can complete the steps outlined in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]] seamlessly.

Here are supplementary actions that should be completed following specific steps to optimize and streamline your onboarding experience:

* '''Once you have completed step 9''' on the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]], you will have successfully created a proposal that is waiting for the NNS to vote. To facilitate this process, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1nKy5hKiF72a4NCHvpgij-Np9pbtR5KOBbF1W6qr-nds/edit?usp=sharing template] for the post.
* '''Once your NP registration has been accepted''', you may complete step 10 on the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]]. At the end of this step, you will have successfully created a proposal to register your DC to the network (if it is a new DC). Similar to the previous step, to facilitate the voting process of your proposal, it is advised to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1Hg0tI9O5__Tp4qKrNKuTADsQT7Z47I6aAFXbiDimG_U/edit?usp=sharing template] for the post.

Once your NP and DC registration have been accepted, you may order the hardware (Step 6) for the nodes and have them delivered to the DC you registered so that they can be racked and stacked. This can be done while you complete the rest of the steps outlined in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]].

== 6. Order hardware ==
The hardware specifications can be found [[Node Provider Machine Hardware Guide|here]]. Note that buying the hardware has a lead time of up to 6 months.

Ordering the hardware directly after the acceptance of your NP and DC registration by the NNS is the safest option. However, in practice, if you are fully aware of the associated risks, ordering the hardware at an earlier stage can be done as well.

== 7. Rack and stack ==
Follow the instructions in the [[Gen-2 Data Center runbook|Gen-2 Data Center Runbook]], or provide them to the hands and eyes team on site so that the set-up of the nodes in the rack is according to community standards.

== 8. Onboard nodes to the IC ==
Now that your nodes have been racked and stacked, they can be added to the IC by following the steps outlined in the [[IC-OS Installation Runbook]].

Once this has been completed, you will have successfully completed step 12 in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]].

== 9. Add nodes to the reward configuration ==
Finally, '''you must complete step 13 in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]]'''. This step will create a proposal to add your nodes to the reward configuration. Once this proposal has been accepted, you will have successfully been onboarded as a node provider on the IC.

How to Become a Node Provider: A Step-by-Step Guide

2023-08-08T08:36:15Z

LouiseVelayo: Added a step by step instructions on how to become a node provider. From data center selection to onboarding nodes. This text accompanies a visual that was submitted to be on this page as well.

This page serves as a guide designed to facilitate the process of becoming a Node Provider (NP) for the Internet Computer (IC) network. For those seeking to contribute to the network's decentralized infrastructure by hosting operational nodes, this guide offers a structured and informed approach. Drawing upon insights sourced from the IC wiki and informed discussions within the IC Forum, this page provides an organized overview of the step-by-step journey. By adhering to this guide, potential NPs will confidently navigate the intricacies, ensuring they are well-prepared to establish their role as NPs for the IC.

NPs who have successfully completed this onboarding process are strongly encouraged to contribute their insights and wisdom to enhance this resource. Your valuable contributions can further enrich the guide. Collaboration is at the core of the Internet Computer community, and your participation can contribute to the success of new NPs!

== 1. Gather DC and ISP quotes ==
The initial step in becoming a Node Provider (NP) revolves around establishing partnerships with Data Center(s) (DC) and Internet Service Provider(s) (ISP) to host operational IC nodes. For ensuring decentralization, it is highly beneficial to distribute nodes across multiple countries and data centers. Additionally, proposing new countries and/or data centers for hosting nodes can increase the likelihood of acceptance during the later stage (step 6). Although not as stringent, a similar principle applies to the selection of ISPs.

At present, there are no mandatory technical certifications required for DCs, but this might change in the future. The sole requirement is verifiability of the DC's location once its proposal is submitted in step 6, as stated in this [https://forum.dfinity.org/t/the-state-and-direction-of-decentralization-nodes-on-the-internet-computer/9170/180 forum post].

'''Suggested approach:'''

# Visit the world map on the homepage of the [https://dashboard.internetcomputer.org/ IC dashboard]. Identify countries where there are no nodes in operation. For decentralization purposes, it is highly recommended to set up nodes in these countries.
# Check the “Data centers<nowiki>''</nowiki> page of the [https://dashboard.internetcomputer.org/centers IC dashboard] for the country of interest. Verify if there are any DCs in that region with IC nodes present. For better network decentralization, opt for data centers companies different from those already hosting IC nodes.
# Contact DCs and request a quote. This [https://docs.google.com/document/d/1-9rj9cEgOqMM3ZzXcniGfAyYkdN9oI8PngflokGazrY/edit?usp=sharing template] is an example request. Feel free to adapt it to your (local) needs.
#* The template is quite comprehensive but the key information that should be included in the DC’s quote are:
#*# Monthly Recurring Costs (MRC) of colocation (renting rack space within the data center)
#*# Non-Recurring Costs (NRC), like one-off setup fees
#*# Cost structure for the services provided by their hands & eyes team (if present)
# Contact ISPs and request a quote. This [https://docs.google.com/document/d/17b-OCFMitFGvCzcHX3Qopjyag2cB0GaZkv6wrIQEtZk/edit?usp=sharing template] is an example request. Feel free to adapt it.
#* Similar to the DCs, at this stage you are only interested in the MRC and NRC.
# If possible, visit the sites of the most promising data centers to assess suitability and professionalism of their staff.
# Utilize the received quotes to make a financial analysis according to the [[Node Provider Remuneration|Node Provider Remuneration Model]]. This will aid in determining the optimal number of nodes to host.
# Finalize a provisional contract with a selected data center. This contract can serve as supporting documentation for your declaration as a node provider (step 4).

To assist with any follow-up questions from data centers regarding the technical aspects of your project, refer to the documentation provided below.

# [[Node Provider Networking Guide|Networking guide]]
# [[Node Provider Machine Hardware Guide|Hardware specifications]]

== 2. Establish a (local) legal entity ==
While '''not mandatory''', establishing a legal entity as a Node Provider is highly recommended.

* Creating a legal entity provides protection in the event of any legal issues, debts, or liabilities related to the operation of these nodes. It safeguards your personal assets from being utilized to resolve such discrepancies.
* Moreover, operating under a legal entity enhances your credibility, increasing the likelihood of your proposal being accepted by the community.
* With a legal entity in place, you gain the ability to enter into contracts and agreements using the entity's name, offering an additional layer of protection for the legal relationships involved in running an IC node, such as the DC contract.

However, it's worth noting that running a node as an individual is also possible. The choice ultimately lies with you.

== 3. Order and setup your hardware wallet ==
As part of the onboarding process (Step 6), '''you will require a hardware wallet.''' Once you have acquired your hardware wallet, you can proceed to configure it by following the instructions provided [[Node Provider Onboarding#3.%20Setup%20your%20hardware%20wallet|here]]. Once these initial setup steps are finished, you will be prepared to move forward with the actions outlined in step 6.

== 4. Preparation of documents for NP self declaration ==
'''Anyone interested in becoming a node provider is required to submit a proposal to be voted on by the community.''' This begins with a self declaration where the following documents need to be prepared and submitted.

* Self declaration - A document to declare you intent to become a node provider
* Identity proof - Any document that proves the identity of the signers of the self-declaration to the community. Examples include:
** Proof of company registration through an official database
** Company registration/license
** ID/Passport

'''Both documents are mandatory.''' Templates for these documents can be found [[Node Provider Self-declaration|here]].

Some supporting documents that are not mandatory but would strengthen any node provider self declaration include:

* Company/personal website
* Link to Github account/organization
* Datacenter contract

'''Publish the documents to the [[Node Provider Self-declaration|self declaration page]] on the IC wiki.'''

== 5. Node provider onboarding to the Network Nervous System (NNS) ==
Now that you have your hardware wallet and also a DC contract in place, you can complete the steps outlined in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]] seamlessly.

Here are supplementary actions that should be completed following specific steps to optimize and streamline your onboarding experience:

* '''Once you have completed step 9''' on the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]], you will have successfully created a proposal that is waiting for the NNS to vote. To facilitate this process, it is best to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1nKy5hKiF72a4NCHvpgij-Np9pbtR5KOBbF1W6qr-nds/edit?usp=sharing template] for the post.
* '''Once your NP registration has been accepted''', you may complete step 10 on the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]]. At the end of this step, you will have successfully created a proposal to register your DC to the network (if it is a new DC). Similar to the previous step, to facilitate the voting process of your proposal, it is advised to create a post in this [https://forum.dfinity.org/t/new-node-provider-proposals/16643/69 forum thread] to raise awareness of your proposal. You can use this as a [https://docs.google.com/document/d/1Hg0tI9O5__Tp4qKrNKuTADsQT7Z47I6aAFXbiDimG_U/edit?usp=sharing template] for the post.

Once your NP and DC registration have been accepted, you may order the hardware (Step 6) for the nodes and have them delivered to the DC you registered so that they can be racked and stacked. This can be done while you complete the rest of the steps outlined in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]].

== 6. Order hardware ==
The hardware specifications can be found [[Node Provider Machine Hardware Guide|here]]. Note that buying the hardware has a lead time of up to 6 months.

Ordering the hardware directly after the acceptance of your NP and DC registration by the NNS is the safest option. However, in practice, if you are fully aware of the associated risks, ordering the hardware at an earlier stage can be done as well.

== 7. Rack and stack ==
Follow the instructions in the [[Gen-2 Data Center runbook|Gen-2 Data Center Runbook]], or provide them to the hands and eyes team on site so that the set-up of the nodes in the rack is according to community standards.

== 8. Onboard nodes to the IC ==
Now that your nodes have been racked and stacked, they can be added to the IC by following the steps outlined in the [[IC-OS Installation Runbook]].

Once this has been completed, you will have successfully completed step 12 in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]].

== 9. Add nodes to the reward configuration ==
Finally, '''you must complete step 13 in the [[Node Provider Onboarding#6.%20Get%20the%20node%20operator%20principal|node provider onboarding wiki page]]'''. This step will create a proposal to add your nodes to the reward configuration. Once this proposal has been accepted, you will have successfully been onboarded as a node provider on the IC.

File:IC NP roadmap v4.png

2023-08-07T14:36:20Z

LouiseVelayo:

A brief overview of the steps involved in becoming a node provider: from data center selection to adding your nodes to the reward configuration.

File:Node Provider Onboarding- Step-by-Step Overview.png

2023-08-07T14:29:04Z

LouiseVelayo:

A infographic to provide an overview of the steps required to become a node provider, starting from data center selection to registering your nodes on the reward configuration.