> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/askedgi/deployment-and-installation/deployment/multi-vm.md).

# Multi-VM

This article describes the infrastructure requirements for deploying OvalEdge in a Proof of Concept (POC) environment. It outlines the required virtual machine specifications, network and port configurations, software prerequisites, and deployment artifacts to ensure a successful installation.

This article is intended for IT and infrastructure teams responsible for preparing the environment prior to OvalEdge installation.

### Scope

This article covers the following areas:

* Virtual machine specifications
* Network and port requirements
* Software versions and dependencies
* Deployment artifacts and ownership

### Virtual Machine Specifications

OvalEdge recommends deploying the platform across multiple virtual machines to ensure scalability, performance, and separation of concerns.

**Recommended VM Layout**

| VM Name | Purpose                     | RAM   | vCPU | Storage (SSD) |
| ------- | --------------------------- | ----- | ---- | ------------- |
| VM1     | OvalEdge Application Server | 32 GB | 8    | 200 GB        |
| VM2     | OvalEdge + Elasticsearch    | 32 GB | 8    | 200 GB        |
| VM3     | askEdgi Service             | 16 GB | 4    | 200 GB        |
| VM4     | Database Server (MySQL)     | 32 GB | 8    | 200 GB        |

{% hint style="info" %}

* Deploy OvalEdge core services and Elasticsearch on separate virtual machines for optimal performance.
* Host the MySQL database on a dedicated server.
* Ensure all virtual machines are provisioned with SSD storage.
  {% endhint %}

### Network and Port Configuration

**Required Port Access**

Ensure the following ports are open and accessible between the specified virtual machines:

| Source VM     | Target VM      | Port | Purpose                     |
| ------------- | -------------- | ---- | --------------------------- |
| VM1, VM2, VM3 | VM4 (Database) | 3306 | MySQL database connectivity |
| VM1, VM3      | VM2            | 9200 | Elasticsearch communication |

#### Network Requirements

* Whitelist the IP addresses of all OvalEdge-related virtual machines.
* Allow bidirectional communication where applicable.
* Ensure firewall rules do not block internal service communication.

### Software Specifications

Install the following software and versions on the respective virtual machines.

**Supported Software Versions**

| Component            | Supported Version        |
| -------------------- | ------------------------ |
| Operating System     | Ubuntu 24.04             |
| MySQL                | 8.4.x                    |
| OvalEdge Application | Latest supported version |
| Apache Tomcat        | 10.1.5x                  |
| ElasticSearch        | 9.3x                     |
| Java                 | OpenJDK 21               |
| Python               | 3.13.x                   |
| Poetry               | 2.1.2                    |

{% hint style="info" %}

* Use only OvalEdge-certified software versions.
* Ensure Java and Python environments are configured before application deployment.
* Elasticsearch must be installed and running before initiating metadata ingestion.\ <br>
  {% endhint %}

### Deployment Artifacts

#### Artifacts Provided by the OvalEdge Team

The OvalEdge team supplies the following artifacts:

* OvalEdge application .war file
* Master scripts for initial database setup
* Valid OvalEdge license key
* Crontab configuration for cleaning temporary and cached data

#### Artifacts Provided by the Customer

The customer is responsible for providing the following:

* **SSL certificate** mapped to the OvalEdge application domain
  * Enables HTTPS communication
  * Ensures encrypted data transmission
  * Aligns with enterprise security and compliance requirements

### Network Architecture

The following diagram represents the high-level network architecture for the OvalEdge POC deployment.

<figure><img src="/files/RVJUE4hQiHCVOVgsVJ9O" alt=""><figcaption></figcaption></figure>

## Conclusion

This article defines the infrastructure and prerequisite requirements for deploying OvalEdge in a POC environment. Completing these requirements ensures a secure, stable setup and prepares the environment for successful application installation and operation.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/askedgi/deployment-and-installation/deployment/multi-vm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.