Cluster (HA)
A production Exaba deployment is one or more clusters, and each cluster is many nodes, built for high availability. You prepare the site that the deployment runs on, and Exaba installs the deployment for you as a service. This page is the sequence, from the first email to a deployment in service.
For a first look, use Docker. The Docker image runs Exaba on one host. It is for evaluation only, and it is not a production deployment.
Onboarding
-
Contact Exaba. Email sales@exaba.com. Exaba works with you on your storage targets and your failure budget.
-
Accept the invitation to Exaba One. Exaba invites you during onboarding. Exaba One tracks the progress of the install, and the status of the deployment afterwards.
Prepare and install
-
Size and order the hardware. Hardware Sizing turns a capacity target into a node count. Ask Exaba to review your sizing before you order.
-
Prepare the site. Work through Site Preparation, with help from Exaba. Record each value in the install inventory as you go. The work is eight areas, and each one has its own page and its own check.
-
Exaba checks the machines. Before the install begins, Exaba runs validation scripts against the machines on the deployment network. See Pre-Install Validation.
-
Hand over to the installation service. Exaba installs the deployment. See Production Installation. This step is complete when the cluster runs and reports to Exaba One. The deployment is then in acceptance testing.
Go live and operate
-
Complete post-install together. Post-Install covers the acceptance checks and the handover to you. This step is complete when the deployment is ready to serve your customers. It is then in production.
-
Operate the deployment. The work from here is monitoring and upgrades. See Health & Monitoring, Upgrades, and Runbooks.
See also
- Architecture at a Glance: what a cluster is made of.
- Exaba One: the remote management and monitoring portal.
- Support: how to reach Exaba after the handover.