Manage provided Compute
Follow the Get Started to provide machines that you own or control.
Manage machines on the NodeOps Cloud Marketplace
This guide assists Compute providers to understand the status of their machines on the NodeOps Cloud Marketplace, and to undertake basic troubleshooting.
Machine status
Once you have registered a machine on NodeOps Network, you can log into the provider dashboard and see the status of your machine/s. Status changes may be initiated by the provider or the Protocol:
| Status | Description | Active party |
|---|---|---|
| Awaiting Stake | In Testnet, follow the dummy staking flow by signing the required transaction in your wallet. In Mainnet, stake the required $NODE | Provider |
| Pending | A temporary state while the Protocol ensures that the machine with the registered secret identifier complies with the requirements. | Protocol-managed |
| Active | Once successfully registered, machines capable of carrying workload move to the active state and are ready to carry workloads | Protocol-managed |
| Inactive | Machines that have been decommissioned by the provider | Provider |
| Suspended | Machines that fail to comply with the requirements | Protocol-managed |
| Deleted | Machines that have been deleted by the provider | Provider |
| Non-schedulable | Flagged machines liable to be suspended | Provider with failover to Suspended/Protocol-managed |
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*
Copy error
An error such as cannot create regular file '/usr/local/bin/atlasnetwork-provider': Permission denied means you didn't create a user account at root for NodeOps Cloud with the correct permissions to run the code.
You can get around this on Ubuntu with sudo. That means:
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
Rejected machines
Your machine will be rejected if:
- It runs workloads in addition to the NodeOps Network assigned loads
- If SWAP is enabled
What next?
Consider:
- Browsing the FAQ
- If you lack the Compute resources, following the guide to set up GCP Compute in the Marketplace