Transferring ownership
The SC//Reliant™ platform supports the transfer of ownership of nodes. This is also referred to as divestiture. This feature provides a way for you to transfer ownership of one or more nodes to a new owner or franchisee. The ownership transfer process involves transferring all of the details and data associated with the node to the new owner. For nodes that are associated with a specific location, the location details are transferred as well.
The supported use cases for ownership transfer are:
- Transferring equipment from one owner to another within the same location.
- Transferring equipment from one owner to another in a new location.
Prerequisites
Before you start an ownership transfer, confirm the following.
- Both the current node you are transferring and the new node you are transferring to are created in SC//Reliant Platform Manager.
- The nodes in the transfer and the Puppet certificate authority (CA) server run the same version of the SC//Reliant Virtual Controller (RVC). If the versions are different, the transfer can fail during its pre-checks with an error such as
Failed to check the external connectivity: <server>: Unknown internal RVC server error.
Starting an ownership transfer
An ownership transfer can be initiated and monitored using the SC//Reliant Platform Manager. The following steps walk you through the process.
- Access and log in to the SC//Reliant Platform Manager at https://platform.reliant.io/.
- From the left navigation menu, choose Ownership Transfer.
- On the New Ownership Transfer page, do the following.
- For Current Store Number, enter the node number of the node to be transferred.
- For New Store Number, enter the node number of the node you are transferring to.
- For Post-Ownership Transfer Configuration, use the toggle to turn on or off the following settings.
- Enable Puppet Agent Post-Ownership Transfer - This option activates the Puppet agent after the transfer is completed, which resumes automated system management.
- For Cluster Management and Cleanup, use the toggle to turn on or off the following settings.
- Delete Nodes After Completion - This option removes the transferred nodes from their cluster.
- Deregister Old Node from Sensu - This option deregisters the transferred nodes from Sensu, which stops monitoring.
- Once all options are selected, choose Continue.
- On the confirmation page, verify the settings and choose Confirm & Start to begin the transfer.
- The Ownership Transfer page then shows the status of the transfer and its steps. Select a step to see its log, which you can use to troubleshoot a failed transfer. When the transfer finishes, the status changes to SUCCESS or FAILED.
Action scripts
When an ownership transfer is running, Platform Manager starts each step on the node it targets with the RVC ownership_transfer.execute method, and RVC runs the action script for that step. Steps that apply to each node, such as Cluster Wipe, run once for each node in the cluster, for example Cluster Wipe (red0) and Cluster Wipe (red1). While the transfer runs, Puppet is disabled on the nodes with the reason divestiture from <current node> to <new node> in progress. The following table lists each step, as it appears in Platform Manager, and the action script that it runs.
| Step | Description | Action script |
|---|---|---|
| Node PreCheck (node) | Verifying that the node has connectivity to the puppet server. | node_prechecks |
| Puppet Server Checks | Verifying that the puppet server has the required data and files for the nodes. | puppetserver_checks |
| Deregister Sensu Go (node) | Removing the node from the Sensu Go monitoring server. This step runs only when Deregister Old Node from Sensu is turned on. | deregister_sensu |
| Cluster Wipe (node) | Performing cleanup steps on the node to remove all cluster resources. | cluster_wipe |
| Certificate Cleanup on the PuppetServer | Performing puppet certificate cleanup on the puppet server. | certificate_cleanup |
| Certificate Cleanup (node) | Performing puppet certificate cleanup on the node. | certificate_cleanup |
| Change hostname (node) | Updating the hostname on the node. | change_hostname |
| Run Puppet (node) | Running the puppet agent on the node. The Puppet agent is run more than once, using the Puppet CA server. | run_puppet |
| Enable Cluster Maintenance Mode | Enabling maintenance mode for the cluster. | set_mode maintenance_mode=true |
| Disable Cluster STONITH | Disabling STONITH for the cluster. | set_mode stonith=false |
| Disable Cluster Maintenance Mode | Disabling maintenance mode for the cluster. | set_mode maintenance_mode=false |
| Check Cluster | Verifying all cluster resources are healthy and waiting for DRBD to sync. | check_cluster |
| Enable Cluster STONITH | Enabling STONITH for the cluster. | set_mode stonith=true |
| Enable Puppet (node) | Activating the puppet agent, which resumes automated system management. This step runs only when Enable Puppet Agent Post-Ownership Transfer is turned on. | set_mode puppet_agent=enable |