Skip to content

Instantly share code, notes, and snippets.

View sjenning's full-sized avatar

Seth Jennings sjenning

  • Red Hat
  • Austin, TX
View GitHub Profile
create VMs
git clone https://github.com/kubernetes-incubator/kargo.git
cd kargo
cp ~/inventory.cfg inventory/.
vi inventory.cfg
(copy IPs and save)
date
ansible-playbook -u centos -b -i inventory/inventory.cfg cluster.yml
date (show elapsed time)
[etcd]
10.42.10.206
[kube-master]
10.42.10.206
[kube-node]
10.42.10.221
10.42.10.223
#!/bin/bash
echo "Getting thin_ls runtimes"
for i in $(seq 0 9); do
sleep 15
dmsetup message /dev/mapper/*--pool 0 reserve_metadata_snap
/usr/bin/time thin_ls --no-headers -m -o DEV,EXCLUSIVE_BYTES /dev/mapper/*_tmeta >/dev/null
dmsetup message /dev/mapper/*--pool 0 release_metadata_snap
done
Title:
OpenShift Container Platform: What You Were Going to Build on top of Kubernetes Anyway
Summary:
Kubernetes is an open-source system for automating deployment, scaling, and management of containerized applications.
Distilled from Borg, Google's own internal application deployment system, the powerful primitives and simple design have
contributed to rapid adoption. Kubernetes works in terms of container images, not source code. This is a deliberate design
decision to restrict the scope of project and focus on creating a solid, scalable container deployment platform.
OpenShift picks up where Kubernetes leaves off. While developers like containers, they don't like to build, test, and manage
apiVersion: v1
kind: Pod
metadata:
name: busybox
spec:
containers:
- name: busybox
image: busybox
command:
- sleep
apiVersion: v1
kind: BuildConfig
metadata:
name: nodejs-ex-pipeline
labels:
app: nodejs-ex
annotations:
pipeline.alpha.openshift.io/uses: '[{"name": "nodejs-ex", "namespace": "", "kind": "DeploymentConfig"}]'
spec:
triggers:
#!/bin/bash
RELEASEVER=25
PACKAGES="bash dnf man passwd shadow-utils sudo vim-minimal iproute iputils bind-utils tar openssh-server openssh-clients procps-ng findutils"
set -euo pipefail
set -x
INSTALLROOT="$(mktemp -d)"
dnf -y --installroot "${INSTALLROOT}" --releasever "${RELEASEVER}" install ${PACKAGES}
#!/bin/bash
#set -x
CGROUPFS=/sys/fs/cgroup
CPUSET=$CGROUPFS/cpuset
CPUACCT=$CGROUPFS/cpu,cpuacct
cleanup() {
set +e
#!/bin/bash
# Attempt to recreate pod stuck in Terminating
STOP=0
function testrun {
while [ $STOP -eq 0 ]; do
project=$1
template=$2
Until packages hit repo:
curl -O https://kojipkgs.fedoraproject.org//packages/cri-o/1.0.0.alpha.0/0.git5dcbdc0.fc26.2/x86_64/cri-o-1.0.0.alpha.0-0.git5dcbdc0.fc26.2.x86_64.rpm
dnf install -y cri-o-1.0.0.alpha.0-0.git5dcbdc0.fc26.2.x86_64.rpm
Otherwise just:
dnf install -y cri-o
curl -L -O https://github.com/containernetworking/cni/releases/download/v0.5.2/cni-amd64-v0.5.2.tgz
mkdir -p /opt/cni/bin
tar xf cni-amd64-v0.5.2.tgz -C /opt/cni/bin/