SC//Reliant Virtual Controller (RVC)

The SC//Reliant™ Virtual Controller (RVC) is a daemon that manages and orchestrates virtual instances and other services on each node. It has two components: the RVC server (the daemon running on the node) and the RVC command-line interface (CLI). The SC//Reliant API can be used to create an RVC job, dispatched to the target node through Remote Job Execution (RJE).

What RVC manages

RVC is the local control point for the following kinds of actions:

• Virtual machine lifecycle (create, start, stop, snapshot, backup, restore).
• Container lifecycle interactions delegated by the platform's container management.
• Cluster operations (status checks, enabling and disabling maintenance mode).
• Docker image management (pulls, tag updates).
• Diagnostic queries against the node.

How RVC is invoked

• From a node: an administrator logged into the node can run the rvc CLI to issue commands locally.
• From the SC//Reliant API: an RVC job is created via a POST to /api/jobs/rvc with the action, target type, and target hostnames in the payload. The job runs on the targeted nodes and returns a job ID for status tracking.

For an example of creating an RVC job programmatically, see Create a SC//Reliant Virtual Controller Job.

Related documentation

• Remote Job Execution (RJE): the dispatch mechanism RVC jobs run on.
• The CLI reference documents every RVC subcommand (cluster, KVM, Docker, Puppet, sys, ownership-transfer, shell, and the top-level RVC commands).