NOTICE: For legacy Stacki Pro / StackIQ Enterprise support — the email address is deprecated. Please use either Slack (preferred) or to access our legacy support ticketing system.
Python C Makefile Shell CSS C++
Latest commit 41e7fa7 Nov 21, 2017 Joe Kaiser Joe Kaiser Closes #171
Make "stack create mirror" chatty if you throw quiet=false.

alt tag

Why Bare Metal Provisioning?

Automation and consistency across Linux infrastructure is hard. Our goal is to make Linux installations of heterogeneous hardware across 10s to 1000s of machines fast, flexible, and absolutely consistent. The Stacki default installation process will bring bare metal infrastructure (or VMs) to a ping and a prompt. The frontend machine has password-less SSH access to the backend machines on first boot, and the repositories on the frontend act as YUM repositories for all backend machines. All machines will be at the latest kernel and RPM revisions of the OS and installed applications.

Stacki initial installations are relatively fast and simple, but may not completely reflect site-specific desired state. Configuration can be layered on using advanced features to customize local environments. The speed of installation/reinstallation Stacki provides allows convergence to a known/desired configuration of resources that reflect local needs. Deployed across the infrastructure, you’ve just made the complex simple and repeatable for existing or new infrastructure.

What is Stacki?

Stacki is a CentOS/RHEL/Ubuntu bare metal install tool that can take your servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. Stacki does this at scale, so deploying 1000+ servers is no more complex than deploying one. Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC etc.). Stacki has a long history, and is in use at some of the most demanding organizations in the world.

What does Stacki do?

  • Configure RAID controllers and partitioning (both customizable). This means you never have to touch a monitor and keyboard to customize the RAID configuration on machines, not even once. Set-up the RAID controller configuration via spreadsheet, ingest it, and install. The RAID will be configured on first installation with no human interaction required.
  • Install OS.
  • Configure OS.
  • Configure networking. This includes configuring multiple network interfaces, multiple network types: IB, 10G, 1G, and authenticated SSH password-less access at boot.
  • Leave you to be productive, to focus on more interesting problems.

With Stacki, machines are disposable. Everything is built from the ground up programmatically so recovering from disasters just means rebuilding your servers. Machines are disposable but data is not. After the initial installation, data is preserved across reinstalls. Data drives are reformatted only by deliberate action. A reinstall is a refresh of the OS and/or application software while data on disk is preserved. Stacki delivers certainty. If you’re configuring individual machines on a daily basis without automation, you’re losing. Our goal is to keep you from having to configure individual servers and always knowing the answer to: “What state are my servers in?” Once your servers are installed with Stacki, augment them with your favorite configuration toolset – be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown – you don’t have throw away work already done. Although, once you see what it can do, some of that post-install configuration management may be easily replaced during installation.


Stacki for CentOS

Stacki is CentOS first, this is where all of our develop starts. You should start here as well before wandering of into Ubuntu and Pi land.

Stacki 4.0 CentOS 6.x

Stacki 4.0 CentOS 7.3

Stacki for Ubuntu (Trusty, Wily, Xenial, or Yakkety)

You asked, we listened, and now we’re releasing Stacki Ubuntu into the open source Stacki tree. You can now automatically install Ubuntu via a preseed network installation to boot backend machines from a Stacki frontend. The only thing you have to do is prep your frontend. It's latest release now does multi-disk partitioning and multiple network interface configuration. We are starting to make a better preseed. In the meantime, follow the GitHub README and the requirements below to get started.


  • A Stacki frontend with Stacki 4.0. It likely won’t work on anything less than 4.0.
  • Stacki-ubuntu-frontend Pallet (MD5 = 55ba30652556994860d5f492cba48939)
  • Stacki-ubuntu-backend Pallet (MD5 = 694ff792eabf27fbdded062316e174b3)
  • Ubuntu-Server iso from Xenial, minor version 1,2, or 3 (e.g., ubuntu-16.04-server-amd64.iso)

Stacki Ace (CentOS 7 for ARM)

Stacki Ace is the new open-source port of Stacki to the Raspberry Pi providing the quickest way to go from one Raspberry Pi with nothing installed to a fully functioning cluster. There is a “Stacki” Pallet that is built from the Stacki open-source repository and there is a new “Stacki-ace” Pallet that we created to specifically support the Pi.

Once you have the required Raspberry Pis and the hardware, download the stacki-centos.img and ISOs (MD 5 checksum) below, and follow the GitHub README to get started.

Hardware Requirements



All users should start with the following link to ‘stacki-centos.img’:

After you build your frontend Pi, copy the following ISOs to your frontend:

Download and execute