CMDB-360 LaunchPad
Deploy — or “launch” — any number of CMDB-360 Satellites from a single host. A proprietary integration ties Docker directly into the Base Station portal for a simple, seamless deployment experience.
Container-based Satellite deployment
One host, many Satellites
Satellites are the discovery and data-access software that gives you visibility into the assets you manage. LaunchPad is the virtualization layer that makes deploying them efficient — run multiple Satellite instances on a single virtual machine or server instead of standing up a separate VM for each one.
- Launch any number of Satellites from one LaunchPad, limited only by compute & memory
- Runs any CMDB-360 Satellite container image, pulled automatically from Docker Hub
- Proprietary management software integrates Docker with the Base Station GUI
- Automatic Docker Swarm support — managed for you by the integration
- Point-and-click deployment from the CMDB-360 portal — no command line required
- Pre-built cloud Marketplace and VMware template images with Docker pre-installed
- Outbound-only HTTPS — no inbound ports required
- Optional private OCI Container Registry for locked-down environments
Introducing LaunchPad
Two ways to run LaunchPad
Every CMDB-360 Base Station ships with a companion Base LaunchPad ready for use. Add Remote LaunchPads inside customer environments to extend discovery wherever your assets live.
Base LaunchPad
Installed alongside your Base Station and set up during initial onboarding. It is commingled — not tied to a single account — and is ideal for Satellites that gather discovery data over a public API, such as the OCI, AWS and Azure public-cloud Satellites.
Remote (customer) LaunchPad
Deployed inside a customer’s datacenter or cloud tenancy and associated with that customer account — every Satellite launched from it belongs to the customer. Stand up one Remote LaunchPad per customer environment to keep discovery and data local to them.
Available on every major marketplace
The preferred path is a pre-built appliance with Docker and the LaunchPad tools already installed. LaunchPad is on the OCI, AWS and Azure marketplaces today, with Google Cloud arriving soon — or install it yourself on any supported Linux host.
Cloud Marketplace appliance
Pre-built images on OCI, AWS and Azure (Google Cloud coming soon) with Docker already installed and configured — the simplest, preferred option.
VMware virtual template
Drop the ready-made VMware template into your vSphere environment to bring LaunchPad online inside an on-premises datacenter.
Linux installer
Provision your own VM or server and run the graphical Installer. Supported on Oracle Linux 8 & 9 and Ubuntu 20.04 & 22.04 (ARM and x86_64).
On a self-provisioned host you install the Docker server first (it is already present on the pre-built and Marketplace images). Then download the installer with wget https://control.cmdb360.com/downloads/Launchpad-Installer.$(arch), make it executable, and run it with sudo.
A simple two-step setup
LaunchPad is provisioned in the Base Station portal and then connected from the host with a single token — the graphical installer handles the rest.
1 · Provision in the Base Station
Open the LaunchPads menu in CMDB-360, click New LaunchPad, name it and assign it to an account (the Base LaunchPad is the only exception). Save, then copy the Access Token from the Overview tab.
2 · Run the graphical installer
On the LaunchPad host, run the installer as root or with sudo. Choose an install directory (default /opt/launchpad), enter your Base Station host (SSL port 443 by default) and the Access Token, then submit. After a 2–5 minute install, reboot and the LaunchPad is ready.
Re-running the installer at any time lets you re-point a LaunchPad at a different Base Station or refresh its token — no rebuild required.
How LaunchPad protects customer data
LaunchPad needs only outbound HTTPS to Docker Hub to pull Satellite images and to your Base Station — no inbound ports are required. Satellites launched on a Remote LaunchPad keep customer discovery data inside the customer’s own environment, in keeping with the CMDB-360 Base Station & Satellite model.
Outbound-only by default
LaunchPad reaches out to Docker Hub (docker.io) over HTTPS to download Satellite container images. Allow outbound traffic on your VCN subnet — nothing inbound is needed.
Private OCI Container Registry option
If your security policy forbids outbound traffic to Docker Hub, LaunchPad can instead pull Satellite images from a private OCI Container Registry in your own tenancy — managed by the CMDB-360 Support Team through a tightly scoped OCI user.
Related
Launch your first Satellite
Deploy LaunchPad from the OCI, AWS or Azure marketplace — or talk to us about the right path for your environment.
Talk to us →