Skip to content
LogScale Self-Hosted Deployment
Content was updated:May 17, 2024
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

# Installing On Bare Metal or Cloud Instance

> Bare-metal Deployment

> System Requirements

> Before installing LogScale in your own environment, you'll need to ensure that you have the supported system requirements (e.g., operating systems, Java).

> Preparing for Installation

> The linked page here explains how to prepare your operating system, including security, and disk and memory settings.

> Installing Native Kafka

> Installing a Kafka cluster.

> Installing LogScale

> Installing LogScale using self-installed Kafka cluster.

LogScale can be installed and deployed in self-hosted environments using either bare metal (directly onto physical machines) or onto cloud instances (such as Amazon ECS). Installation on these environments requires additional steps and configuration to prepare the systems, install the different components and then install LogScale.

LogScale is deployed as a cluster of machines, typically with a minimum of three nodes. These nodes operate together to provide the LogScale functionality. Higher ingest and retention volumes require larger clusters. A load balancer is placed in front of the cluster to provide a single URL endpoint for communicating with the cluster. A Kafka cluster is required by LogScale to support the ingestion and inter-node communication.

graph LR C[Client] subgraph LB [Load Balancer] direction LR P1[Proxy Host] P2[Proxy Host] P3[Proxy Host] end subgraph LC [LogScale Cluster] direction LR H1[LogScale Node] S1[Local Storage] H2[LogScale Node] S2[Local Storage] H3[LogScale Node] S3[Local Storage] end H1<-->S1 H2<-->S2 H3<-->S3 subgraph KC [Kafka Cluster] direction LR K1[Kafka Node] K2[Kafka Node] K3[Kafka Node] end BS([Block Storage]) C-->LB LB-->LC LC-->KC LC-->BS

The roles and requirements for a successful LogScale deployment:

- Kafka Cluster to support the ingest and communication between LogScale nodes. See Kafka Usage for more information.

- LogScale nodes.

- Load Balancer to provide a single access point and distribution of work across the LogScale cluster.

For background information on LogScale and the overall architecture, see LogScale Internal Architecture.

The full set of processes that needs to be followed is outlined below:

- System Requirements

  Identify the system requirements for the nodes where Kafka and LogScale will be installed.

- Preparing for Installation

  Prepare the hosts for installation by configuring the operating system, users and storage.

- Individual Node Configuration

  Each node in the cluster, in addition to the requirements and preparation sections, will need some additional considerations to ensure that the running systems are available and accessible on the network by ensuring firewalls and instances are configured correctly.

- Java

  LogScale is written in Scala and requires a Java Virtual Machine (JVM) to execute. This is bundled with Falcon LogScale distributions.

- Deploy an Apache Kafka Cluster

  LogScale uses Apache Kafka internally for queuing incoming messages, and for storing shared state between nodes.

  Depending on the environment, two choices are described here:

  - Use Installing Native Kafka if running on bare metal or self-hosted virtualized environment

  - Use Deploying Kafka using Amazon MSK if running in AWS

- Installing LogScale

  The LogScale software itself will need installing and configuration.

#### Enter search term