Any machine running Cudo Miner receives a unique identifier to individually designate it in the Web Console when it is connected to the service for the first time.
Ordinarily, the application stores this in the host operating system’s credentials store or keyring. This means that each time Cudo Miner is started, it can keep and maintain its state in the Web Console, persisting across updates or reinstalls.
In situations where a machine does not have persistent storage, or for some other reason runs statelessly, this usually results in a new device in the web console each time the machine or the Cudo Miner application is started.
To address this, Cudo now offers a stateless device persistence feature to allow such machines to keep their identity in the web console.
The following steps describe how to set up this feature:
- While logged into the web console, go to the ‘Settings’ page and click the ‘Generate’ button next to the ‘Access key’ field. Then save your settings.
This key will be used to authenticate the Cudo Miner application against your organization, such that it is authorized to supplant and assume the identity of an existing device.
- In the master build that you are using to re-image or net-boot the target machines, where you have Cudo Miner installed, you will edit the command-line used to launch Cudo Miner to include the following options:
· --autoenrol-identity-trait macaddress
· --autoenrol-access-key .
Where ” is the same organization login username you would normally type into the miner, and ” is the key you created earlier.
Note that at present, the only uniquely-identifying trait we support is the device’s ethernet MAC address. We use the address associated with whichever network hardware your default route is currently accessed via.
- The first time your target machines start after implementing the persistence feature, a new device will be created against each one’s unique identity. Subsequent times they are started, they should re-assume the originally-created device identity.