Machine statuses
TL;DR
- Provided Machines may occupy various states
- Rented Machines have a different lifecycle
tip
Follow the Get Started to provide machines that you own or control.
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 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 |
Rented Machines
Consumers may rent entire Machines from the network. Renters can monitor the health of machines. However, they don't have the same perspective over the Machine as the Provider.
Notice that a Machine you rent has the Occupied label which differentiates it from any Machine that you provide to the Network.
Show me
What next?
- Browse the FAQ
- If you lack the Compute resources, but want to have a try either:
- Follow the guide to Farm Compute from the Marketplace
- Follow the guide to set up GCP Compute in the Marketplace