Emacs install I use emacs as my editor of choice, I can use others, but if I have to choose, then I choose emacs, it has always been a powerful choice that grew with the years, every time I look at it again I discover new things. I have a debian jessie (8.1) VM where I wanted to have the latest emacs, so I compiled it: Install dependencies: sudo aptitude update sudo aptitude install autoconf automake libtool texinfo build-essential xorg-dev libgtk2.

Things like conda make setting up complex python projects simpler, but create a whole parallel world. Sometime you want to just fix the current OS, and at most use virtualenvs (I dislike introducing too many layers). I have a debian jessie (8.1) VM (oldstable), and I wanted to have modern python 3 on it, so I decided to install the latest python (3.7.3). Install dependencies sudo apt-get install libreadline-gplv2-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev It turns out that the shipped openssl is too old to build the ssl module, so it is better to get the latest stable openssl and install it (I did it in my home):

Bringing Back Kubernetes The problem Shortly after having had my last day of work some issues came up and the kubernetes cluster went down. I began looking into it (a bit half heartily) and I began noticing some strange random issues. Monitoring the kube-system namespace I saw that flannel issues seemed to crop up quickly. There are several issues open regarding flannel failing #963, 1076,… and initially the real culprit wasn’t clear.

Reinstalling the Kubernetes Production Cluster The main reason for this is a critical Kubernetes bug. Here is a bit a log of what I did (to hopefully help me next time). This is mostly taken from kubernetes doc (1, 2) and tweaks I added. Master node: Basically the same as the Visualization Setup minus the tainting and coredns editing: # disable swap: swapoff -a # comment out swap lines (the command should do it, but I prefer manual edit) # sudo sed -i '/ swap / s/^\(.

Dev Kubernetes reinstall The main reason for this is a critical Kubernetes bug. Here is a bit a log of what I did (to hopefully help me next time). Development cluster extension I installed a new cluster on labdev3, mostly following what I did last time. But labdev4 was having issues, so I asked a clean image. It took a bit to have it up. Here is the process to add it to the Kubernetes cluster.

Kubernetes Kubernetes is central to NOMAD archive and analytics (see /nomad/Kubernetes). Every installation of kubernetes has been quite different (kubernetes evolves quickly). Here is the description of the latest (more manual) installation I did on CentOS for the remote visualization, mainly as a reference for me. This uses kubeadm something that has simplified the installation of kubernetes. update kubeadm (from https://kubernetes.io/docs/setup/independent/install-kubeadm/) cat <<EOF > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64 enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://packages.