Lumeta Scouts are deployed by users in the same manner as Command Centers. The license keys, which Lumeta creates using your component's UUID, determine whether a Scout or a Command Center will be unpacked. See Deployment for the complete installation procedure. The OVF intended for use in deploying Scouts allocates fewer system resources because Scouts are small. The one intended for use in deploying Command Centers is relatively large. It is configured to allocate more resources to meet the Command Center's greater CPU, memory, and disk requirements. You may install an unlimited number of virtual Scouts and you may connect however many Scouts you need to your Command Center. You will need to input a unique license key from Lumeta, however, for each Scout you install. This is because each Scout needs a unique UUID. Each Command Center deploys with its own onboard Scout that cannot be disabled or deleted. This onboard Scout is referred to as "local" on the Lumeta GUI and in this documentation. Once deployed, Scouts are smaller, have a minimal GUI, and require fewer system resources. When you browse to a Scout's IP address, you'll see device identifiers, like this: The upgrade package for Scouts is the very same one you'll use to update your Command Center. Each release comes with one upgrade file that can be used for both. To upgrade a Scout:Upgrading a Scout
Device identifiers and a Upgrade Lumeta button display. This is the Scout's sole GUI.
The upgrade process takes place.
Overview
Content Tools