flowchart LR
A["Deploy the<br/>Virtual Appliance"] --> B["Configure the<br/>Virtual Appliance"]
B --> C["Register the<br/>Appliance"]
C --> D["Upgrade the<br/>Appliance<br/>(if available)"]
classDef required fill:#e8f0fe,stroke:#1a73e8,stroke-width:2px,color:#174ea6
classDef optional fill:#f1f3f4,stroke:#9aa0a6,stroke-width:2px,color:#3c4043,stroke-dasharray:5 3
class A,B,C required
class D optional
Deployment
The LF AI Platform is delivered as a virtual appliance: a pre-built virtual machine image that runs on customer infrastructure. Installation takes four stages, from deploying the appliance to connecting it to the Cloud Console, where appliances are registered, diagnosed, and upgraded.
More than one appliance can be deployed. For an organization spanning multiple network segments, sites, or regions, Plan the deployment first.
Deployment Targets
A separate image ships for each target platform. Choose the one that matches the target infrastructure:
- Deploy OVA on VMware vSphere.
- Deploy VHDX on Microsoft Hyper-V.
- Deploy AMI on Amazon Web Services (EC2).
- Deploy Azure Marketplace Image on Microsoft Azure.
Machine Specifications
The minimum machine specifications are comparable to an AWS c6i.xlarge EC2 instance:
| Resource | Minimum |
|---|---|
| Memory | 16 GB |
| CPU | 4 vCPUs |
| Disk | 64 GB |
Sizing Consideration
On most virtualization platforms, memory and CPU can be resized after deployment. Disk resizing is more involved and varies by platform, so allocate enough storage up front.
Network Requirements
Confirm the appliance has the following network access before deployment:
| Direction | Protocol / Port | Purpose |
|---|---|---|
| Outbound, appliance → internet | HTTPS (443) | Reach the Cloud Console to register the appliance, apply the license, and download upgrades. |
| Inbound, users → appliance | HTTPS (443) | Reach the appliance’s application UI at https://<appliance-ip>/ to configure it and complete registration. |
Behind a Proxy?
If the appliance’s network doesn’t have direct outbound internet access, Configure a proxy so it can reach the cloud Console.
Step 1: Deploy the Virtual Appliance
Deploy the virtual appliance from a virtual machine image onto the target infrastructure, creating the virtual machine that runs the platform.
Step 2: Configure the Virtual Appliance
On first boot, Configure the appliance by setting the time zone, network, hostname, and DNS so it has a static address and can join the network and be reachable.
Step 3: Register the Appliance
Register the appliance by generating a license and connecting it to the Cloud Console. Registration is required before the appliance can be used.
Step 4: Upgrade the Appliance
When an upgrade is available, Upgrade the appliance to bring its component services to the latest version. This stage is optional and applies only when a newer version exists. Upgrades are managed and run from the Cloud Console.