Self-hosted Landscape

Self-hosted Landscape is the standalone edition of Landscape that you can install on premises, or in a public cloud.

Feature enhancements will be released in our scheduled release windows, which occur every April and October. Security patches and bug fixes will be provided outside of our scheduled release windows, at the earliest possible opportunity.

Landscape 23.03 manages all versions of Ubuntu from Xenial Xerus onwards. Landscape 23.03 will also manage up to 2 future Ubuntu releases, inclusive of the next interim release (Ubuntu 23.10) and the next LTS release (Ubuntu 24.04). Compatibility beyond this range to older and newer versions of Ubuntu is on a best effort basis, and is not guaranteed.

Installation

Self-hosted Landscape consists of two parts:

• database server
• application server

Depending on your deployment method, these may live on the same machine or different machines. Here is how you can get started:

Quickstart

• Quickstart, for when you don’t have Juju but quickly want to check out self-hosted Landscape. Not recommended for production environments when having more than 500 clients.

Juju deployed

• Juju deployed for a truly scalable deployment.

Manual installation

• Manual installation: for when you don’t have a suitable Juju environment but need a scalable deployment.

Installation requirements

System Requirements

The baseline compute power required to run Landscape is 4 GB of RAM and 20 GB of disk space.

• The landscape-server-quickstart package requires 2 vCPUs or one dual core processor
• The Juju based installation can be deployed on a single vCPU, but a minimum of 2 is recommended.

One machine with these specifications will run the landscape-server-quickstart package. When using Juju or manually installing across multiple machines, none of the machines should be configured below these baseline compute power specifications.

The operating system to run Landscape Server and its dependencies are Ubuntu Server 20.04 LTS or 22.04 LTS on amd64, arm64, s390x, or ppc64el CPU architectures.

Network access

Any machines you manage with Landscape should be able to access your Landscape installation over network ports 80/TCP (HTTP) and 443/TCP (HTTPS). You can optionally open port 22/TCP (SSH) as well for maintenance of your Landscape installation.

The machine(s) running as the application server will also need the following external network access:

• HTTPS access to usn.ubuntu.com in order to download the USN database and detect security updates. Without this, the available updates won’t be distinguished between security related and regular updates
• HTTP access to the public Ubuntu archives and changelogs.ubuntu.com, in order to update the hash-id-database files and detect new distribution releases. Without this, the release upgrade feature won’t work
• HTTPS access to landscape.canonical.com in order to query for available self-hosted Landscape releases. If this access is not given, the only drawback is that Landscape won’t display a note about the available releases in the account page.

If this external network access is unavailable, Canonical’s professional services include assistance with setting up Landscape in a fully air-gapped environment.

Unsupported Versions