Create Environment

Define the setup, then provision when ready.

Create environment

Complete required fields first. Advanced options are available below.

Ticket IDProfile

Setup typePresetCustom topology

Search preset (name, customer, tags)Preset

Manage presets

Custom preset saved from custom topology builder. · 2 node(s)

Customer: ACME Corp

This preset already includes a custom topology: 1 Async replica cluster, 0 MaxScale node(s), 2 total host(s), 0 link(s).

Advanced: Provider, retention, timezone, notes

Provider

Deployment profileColocated (shared host)Tarball (myharem)All nodes as separate instances on one shared, always-available host. Cheapest and fastest to provision; faithful for version, config, SQL, replication and Galera-logic repros.Tarball via myharem is forced: a single host cannot hold several RPM/DEB versions of MariaDB at once (fixed package paths, ports and systemd unit).Colocated (dynamic VM)Tarball (myharem)Same placement, but on a VM created for this environment and destroyed when you decommission it. Pausing stops the VM, so it costs nothing idle.Tarball via myharem is forced: a single host cannot hold several RPM/DEB versions of MariaDB at once (fixed package paths, ports and systemd unit).Isolated VMs (one VM per node)Tarball (myharem)A dedicated VM per node, created and torn down with the environment. Needed when the repro involves per-node OS state, network partitions, latency or host failure.One node per VM is what makes repo install (dnf/apt) possible, which is the point of this profile: real systemd units, SELinux contexts, /var/lib/mysql and the distro’s own galera-4 build — the bugs a tarball repro cannot reproduce.Interim: The repo install path is not built yet, so nodes are still deployed from tarballs via myharem. You get per-node OS, network and failure isolation, but not package-level fidelity.

Retention (days)Primary timezoneAssigned engineer timezones (comma-separated)Presence challenge timeout (minutes)Notes

Sign in

Create Environment

Create environment