OLVM Satellite
Discover the virtual machines and hosts managed by an Oracle Linux Virtualization Manager (KVM) platform through its REST API.
Oracle Linux Virtualization Manager
OLVM resources brought into the CMDB
- Virtual machines managed by OLVM
- Their identity, configuration & status from the Manager
- Each VM rolled into the CMDB as a managed asset
- The OLVM (KVM) hosts that run those VMs
- Host details as reported by the Manager
- Read via the Manager REST API — never the hosts or VMs directly
Deploy alongside your OLVM Manager
Run the OLVM Satellite as a Docker container or install it on any supported Linux host — ideally within the same network as the OLVM Manager server, so all data stays inside the customer’s network boundary.
Docker image
Pull the public CMDB-360 OLVM Satellite image from Docker Hub and run it on any host that already has Docker installed.
Universal Installer
Install on any Oracle Linux 8/9 or Ubuntu 20.04/22.04 host (ARM or x86_64) with the graphical Installer or the non-interactive AutoInstaller for scripted setups.
We recommend deploying the Satellite within the same IP space as the OLVM Manager server so sensitive data stays inside the customer’s network boundary — though it can run anywhere that can reach the Manager and has outbound access to the Base Station. Minimum footprint: 1 vCPU, 4 GB RAM, 10 GB disk, and no inbound ports are required.
A simple two-step setup
When you deploy with the Installer or AutoInstaller, configuration is handled for you. Otherwise the on-instance tools walk you through two steps.
1 · Connect to the Base Station
Using the AdminTool, point the Satellite at your MSP’s CMDB-360 Base Station with its URL and the unique access token issued for the Satellite. These are held in an encrypted config.yml, then services are restarted.
2 · Connect to OLVM
Run the ConfigTool and enter your OLVM host URL (including the port if needed) and a read-only OLVM user and password. Save, and the Satellite begins discovery and reports rosters to the Base Station.
The Satellite needs only read-only access to the OLVM Manager, and you can disable discovery of any resource type from the Satellite scheduler — or turn off the on-demand detail channel entirely — so it only ever sees what you choose to expose.
How the OLVM Satellite protects data
The OLVM Satellite runs inside the customer’s data center and never touches the hosts or virtual machines directly — it reads only from the OLVM Manager REST API and sends non-sensitive rosters to the CMDB-360 Base Station. Detailed information is streamed on demand and only while a user is viewing a record, so nothing proprietary is stored outside the environment.