Skip to content

Adding Software Pallets

Jump to bottom
Joe Kaiser edited this page Jan 25, 2018 · 5 revisions

Adding Software Pallets

There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.

Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.

All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.

RPM-only pallets are the simplest to create.

RPM-only Pallet

Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.

Creating pallet from a URL.

Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)

If I have a url, I can use that with my create mirror command to get the packages.

Here's the epel url: Again, go to your biggest directory:

# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/

Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.

# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.

At some point you'll see this output:

Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.

Creating pallet from a repoid.

Sometimes there's an application you want to install, and a repoconfig file exists for it.

For this example we'll use Apache Cassandra.

Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.

Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.

# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:

  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:

# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.

Do the add/enable pallet dance:

# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.

All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.

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" + '
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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('^' + ".*" + '
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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('^' + ".*" + '
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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" + '
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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('^' + ".*" + '
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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('^' + ".*" + '
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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); }
})();
})();
Adding Software Pallets · Teradata/stacki Wiki · GitHub
Skip to content
Adding Software Pallets
Jump to bottom

Joe Kaiser edited this page Jan 25, 2018
·
5 revisions
Adding Software Pallets
There may come a point where it makes sense to create your own pallets. There are three types: RPM only, configuration only, and configuration + RPMS.
Pallets allow you to install and configure applications you have created or downloaded. It's a simple way to keep multiple versions or to do patching/upgrading.
All pallets come in the ISO format. They can be pulled from the web for OS distributions or created from a directory or remote yum/zypper repository by mirroring.
RPM-only pallets are the simplest to create.
RPM-only Pallet
Creating an RPM-only pallet is simple and assumes your frontend has access to the internet. If not, put up a VirtualBox frontend on your desktop/laptop and create the pallets there and then put them on the real frontend.
Creating pallet from a URL.
Let's say I want all of EPEL. (This is actually easier to do with repoconfig/repoid from EPEL but I want an example.)
If I have a url, I can use that with my create mirror command to get the packages.
Here's the epel url:
Again, go to your biggest directory:
# cd /export

Mirror using the url=https://mirrors.sonic.net/epel/7/x86_64/Packages/
Note: When you use a "url=" parameter stack create mirror uses "wget" and NOT reposync. Use the "url" for RPMS not in actual repositories with a repoconf/repoid.
# stack create mirror url=https://mirrors.sonic.net/epel/7/x86_64/Packages/ name=epel version=20171128 quiet=false

Wait a looonnnnnggggg time.
At some point you'll see this output:
Creating disk1 (0.00MB)...
Writing repo data
Spawning worker 0 with 883 pkgs
Workers Finished
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Generating sqlite DBs
Sqlite DBs complete
Copying graph and node XML files
Building ISO image for disk1

Which means the ISO is built.
Creating pallet from a repoid.
Sometimes there's an application you want to install, and a repoconfig file
exists for it.
For this example we'll use Apache Cassandra.
Go to the Cassandra install docs. You'll notice about half-way down they give you the repoconfig you'll need to get this from yum.
Cut and paste that and put it in a file. I've put it in /export/cassandra.repo.
# cat /export/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1cat
gpgkey=https://www.apache.org/dist/cassandra/KEYS

Let's do a few things:
  • I'm going to feed the name of this file to "repoconfig" parameter to get all the needed Cassandra RPMs.
  • The version is "311x" because that's the lastest version of Cassandra.
  • The "repoid", in this case "cassandra," tells "create mirror" the repo to pull from. Some repoconfigs might have more than one stanza - CentOS-Base.repo is a good example.
# stack create mirror name=apache-cassandra version=311x repoconfig=/export/cassandra.repo repoid=cassandra quiet=false

Now breathe. In/out. Long deep breaths. Or, hell, just go get another cup of coffee. When it's done you should see something like this:
# ls cassandra
apache-cassandra-311x-redhat7.x86_64.disk1.iso cassandra-3.11.1-1.noarch.rpm cassandra-tools-3.11.1-1.noarch.rpm roll-apache-cassandra.xml

Note, the directory is the name of the "repoid" and the newly created file is in this directory.
Do the add/enable pallet dance:
# stack add pallet cassandra/apache-cassandra-311x-redhat7.x86_64.disk1.iso
Copying apache-cassandra 311x-redhat7 to pallets ...
# stack enable pallet apache-cassandra
Cleaning repos: CentOS-7-redhat7 CentOS-Updates-7.4_20171128-redhat7 apache-cassandra-311x-redhat7 epel stacki-5.0_20171128_b0ed4e3-redhat7
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos

Now you can use the Apache Cassandra RPMs on the cluster. Use a cart and <stack:package> tags to add the software and <stack:file> tags to add config files, and <stack:script> tags to enable the service and configure any other dependences.
All this set-up can be found in the Apache Cassandra docs and can be converted to your cart xml.
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