Skip to content

Overview

Jump to bottom
Chris Ladd edited this page Oct 11, 2019 · 11 revisions

Putting real electrons on real silicon since 199....a long time.

"Stacki" = Stack Installer

We install all your stack.

And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."

Yeah, whatever - what is it?

Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.

Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.

Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).

Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.

What it does is simple:

  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.

What it produces is complex:

  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.

Linux

Stacki supports Red Hat and its variants, and also SLES. We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.

Applications

The following is a list of some of the applications that Stacki is used to deploy:

  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes

If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.

Does Stacki fit?

Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.

If you:

  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.

Then we might not be what you need. Take a look at:

Checkout our Google Group or our Slack Team for any support or other questions.

Want to contribute to this Wiki? Fork it and send a pull request.

Stacki Documentation

Clone this wiki locally

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
Overview · Teradata/stacki Wiki · GitHub
Skip to content
Overview
Jump to bottom

Chris Ladd edited this page Oct 11, 2019
·
11 revisions
Putting real electrons on real silicon since 199....a long time.
"Stacki" = Stack Installer
We install all your stack.
And it's pronounced "Stack-ee" not "Stack-eye" or "Stuh-kai."
Yeah, whatever - what is it?
Stacki is a CentOS/RHEL/SLES bare metal install tool that takes servers from bare hardware (or virtual hardware) to working Linux, ready to install applications. It doesn't install images of OSs, it installs the OS with native kickstart, preseed or autoyast.
Stacki parallelizes at scale - deploying 1000+ servers is no slower or complex than deploying one.
Advanced users can use Stacki to install applications (Hadoop, OpenStack, HPC, Docker, Kubernetes...ad nauseum).
Stacki has a long history and is in use at places like Teradata, Verizon, Salesforce, and Ebay.
What it does is simple:
  1. Install OS.
  2. Configure OS.
  3. Configure RAID controllers and partitioning (customizable - never touch a keyboard and monitor for RAID setup again)
  4. Configure networking (Including multiple interfaces, multiple network types: IB, 10G, 1G)
  5. Provides power on to ping and a prompt with password-less SSH access.
What it produces is complex:
  1. One source of truth for your data center - a stacki frontend.
  2. Disposable machines, just like VMs Everything is built from the ground up programmatically - recovering from disasters just means rebuilding your servers.
  3. Doesn't dispose of data. After 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.
  4. Certainty. If you're configuring individual machines on a daily basis without automation, you're losing. Stacki allows you to stop configuring individual servers and always know the state of your data center.
  5. DevOps integration. Servers are installed with Stacki and can be augmented with DevOps infrastructure - be it shell scripts, Salt, Chef, Puppet, CFEngine, Ansible, or homegrown. Don't throw away work already done.
Linux
Stacki supports Red Hat and its variants, and also SLES.
We generally develop on SLES since it is Teradata's focus, but we always test on CentOS/RHEL to give you the choice for your base operating system. We have also seen Oracle Linux and Scientific Linux deployed.
Applications
The following is a list of some of the applications that Stacki is used to deploy:
  • Big Data: Cloudera, Hortonworks, MapR, Pivotal, BigInsights, Spark, Storm, Cassandra, MongoDB, RabbitMQ, R, Mesos, Splunk
  • Cloud: OpenStack (RHEL-OSP, community OpenStack, RDO), CloudStack
  • HPC: Torque, Slurm, MOAB, MPI, UGE/OGS/SGE, PBS, CUDA, LSF, PGI
  • Filesystems: Ceph, GPFS, GlusterFS
  • Hardware: Intel, Supermicro, Dell, IBM, HP, Cisco UCS, white box
  • Good Stuff: Puppet, Ansible, Chef, Salt, CFEngine, Intel Developer Tools, VirtualBox, Docker, Kubernetes
If you can do it in Linux, Stacki can automate it and deploy it over hundreds of machines.
Does Stacki fit?
Look, Stacki isn't needed by everyone for everything. We're focused on installing clusters fast and at scale as part of the iterated data center.
If you:
  • Install a small number of machines. (Five, five is a small number.)
  • Install machines once and then forget about them. (Unicorns)
  • Don't reinstall to get a known good state. (You don't like certainty.)
  • Don't provision/re-provision and marshal resources based on client need.
  • Already have configuration DevOps tools in place that does most of the work.
  • Are doing straight HPC (Rocks is probably still best for that.)
  • Time is of no essence for you.
Then we might not be what you need. Take a look at:
Checkout our Google Group or our Slack Team for any support or other questions.
Want to contribute to this Wiki? Fork it and send a pull request.
Stacki Documentation
Clone this wiki locally