Skip to main content

Register your GCP Compute with NodeOps Network

Compute comes in all shapes and sizes. Cloud providers such as the Google Cloud Platform are a great way to spin up Compute with little effort.

This guide demonstrates how you can use your GCP-powered Compute and register it with NodeOps Network.

tip

GCP hands out credits to new users. This means that anyone can provide Compute and earn gNODE in the NodeOps Network!

Prerequisites

  • Gmail account
  • Wallet
  • GCP credits or billing to support a VM of the minimum requirements
Requirements

Apply storage in the correct ratio to the number of vCPUs provided to a mimimum:

Machines must

Comply with the minimum hardware and port requirements:

  • CPUs or vCPUs: ≥2
    • GB RAM: ≥4
    • SSD storage: ≥80GB NVMe Storage
    • Network bandwidth: ≥1Gbps unlimited
    • Uptime: ≥ 99%
    • OS: Debian (12+) or Ubuntu (22.04+) installation with Linux kernel 6.0+, updated with the latest security patches
  • Allow traffic on ports:
    • UDP 8472
    • TCP 10250
    • UDP 51820
    • UDP 51821
  • Run the Protocol at root
Machines must not:
  • Run additional workloads
  • Have third-party applications or monitoring agents installed
  • Enable SWAP
  • Be exposed to intervention with the workload or machines
Run at root

NodeOps Network's integration must be run directly on a machine at root:

  • You can't run it in Docker
  • Don't run it on a homelab

Step 1. Prepare the network rules

1.1 Sign up or log in to your Google Cloud account and create a new project.

1.2 Navigate to Firewall policies and click Create firewall policy.

1.3 Name the policy and give it a useful description, click Create.

Show me
GCP Compute engine

1.4 Click Create Firewall rule.

Show me
GCP Compute engine

1.5 Set the following and click Save.

  • Priority, if you are new to this, follow our example of 100
  • Leave other properties as default
  • Scroll down to Source filters and set the IPV4 to 0.0.0.0/0
  • [Optionally] restrict the traffic to the following ports:
    • UDP: 8472, 51820, 51821
    • TCP: 10250
Show me
GCP Compute engineGCP Compute engine
important

Setting IPV4 ranges to 0.0.0.0/0 allows all inbound and outbound traffic, which means anyone can attempt to access your services, potentially leading to unauthorized access. Specifying the ports helps to restrict the allowed traffic to only the services or Protocols that use these ports. Unless you are experienced setting up firewall rules, we do NOT recommend using this GCP project for any critical purpose as, without further configuration, this network rule will apply to all Compute instances you create in this VPC network (Virtual Private Cloud).

Step 2. Create the Compute

2.1 Navigate to Compute Engine.

Show me
GCP Compute engine

2.2 Navigate to VM instances and click +Create Instance.

Show me
GCP vm instancescreate GCP vm instance

2.3 From Machine configuration, select for example, E2.

Setup a machine to meet the minimum requirements.

Show me
configure GCP machine 2CPUs min 4vCPUs

2.4 Click Change and add storage to minimum requirements.

Show me
configure GCP machine storage to 80+GB

2.5 Configure firewalls to allow HTTP/HTTPS.

Show me
configure GCP machine 2vCPUs and 80GB

2.6 Click Create

Step 3. Register on NodeOps Marketplace

3a. Register a as a provider

To register as a provider, follow the Get Started guides:

3b. Register a machine

  1. Logged in to the Cloud Marketplace > Compute > + Farm Compute.
Show me
Navigate the Marketplace dash from Compute to Farm Compute
  1. Select Add My Own Machine > Continue > Determine how many machines > Continue.
Show me
Determine how many high-availability Machines you will make available to NodeOps Network. Determine how many high-availability Machines you will make available to NodeOps Network.
  1. Sign the 2 transaction requests in your wallet.

Congratulations, the Protocol has registered your Machine and provided it with a unique identifier.

  1. Copy the setup code: from the All or the Pending tab, click Setup > Copy.

Refresh the page if your Machine doesn't appear in the tab.

Show me
Copy the secret and command required to be run on your Machine to make it available to the verifiable Compute layer on NodeOps Cloud Marketplace.

Step 4. Connect NodeOps Network to your GCP Compute

4.1 Add sudo to your command to allow NodeOps Network read and write access to your GCP machine.

curl -L https://get.atlasnetwork.dev | sh -s - 9zvmdvJ****SECRET*****w9PHZwP

becomes

sudo curl -L https://get.atlasnetwork.dev | sudo sh -s - 9zvmdvJ****SECRET*****w9PHZwP

4.2 From the GCP dashboard, navigate to VM instances, click SSH and Authorize to SSH-in-browser connect to your VM.

Show me
SSH into GCP VMAuthorize SSH into VM

4.3 Paste your edited code snippet in the terminal provided and press Enter on your keyboard to run.

Show me
run code outcome

Step 5. Activate your machine on NodeOps Network

5.1 From the NodeOps Network dashboard, find your GCP machine in the "AWAITING-STAKE" state.

5.2 Continue by clicking "Stake."

Show me
Stake

5.3 Confirm the transaction in your wallet.

Show me
Confirm stake transaction in wallet

5.4 Your Machine's state changes to "CONFIGURING" and then to "ACTIVE."

Congratulations! You're providing decentralized Compute orchestrated by NodeOps Network's Protocol on Arbitrum.

Troubleshooting

Q. Can I check why my machine is not transitioning to active state? A. Yes. From the machine terminal, and run the following command to check if you're facing any issue or if you haven't met the requirements.

journalctl -fu atlas*