The AWS cluster configuration script Kubernetes comes with works pretty much flawlessly, with two exceptions. First, make sure you have
curl installed on the system you are bootstrapping the cluster from. And, second, make sure the
awscli package is recent.
The Debian AWS AMI does not come with
curl installed and the
awscli package is an old version:
aws-cli/1.4.2 Python/3.4.2 Linux/3.16.0-4-amd64).“ After running
pip install --upgrade awscli you should see a version at least:
aws-cli/1.10.24 Python/2.7.9 Linux/3.16.0-4-amd64 botocore/1.4.15.
I found a blog post by Aymerick describing how to build InfluxDB on a Raspberry Pi. Here’s what I did to get it working.
$ sudo apt-get install -y bison ruby2.1 ruby-dev build-essential
$ sudo gem2.1 install fpm
This installs gvm for the current user:
$ bash < <(curl -s -S -L https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer)
$ gvm install go1.4.3
$ gvm use go1.4.3 --default
Create an influxdb package set
$ gvm pkgset create influxdb
$ gvm pkgset use influxdb
$ go get github.com/sparrc/gdm
$ go get github.com/influxdata/influxdb
$ cd ~/.gvm/pkgsets/go1.4.3/influxdb/src/github.com/influxdata/influxdb
$ gdm restore
$ go clean ./...
$ go install ./...
./package.sh command did not work for me, so I settled for the
influx binaries in
There are multiple ways to limit SSH access to a machine. The one I’ve found most straight forward is to use PAM access rules. First, edit
/etc/pam.d/sshd and uncomment the line:
account required pam_access.so
The following rules allow
root from a local connection and deny all but users in the
-:ALL EXCEPT ssh:ALL
With this in place, managing SSH access is a matter of tweaking the
On Debian-based systems like Ubuntu it is possible for common programs to have multiple versions. The alternatives system is a way to manage what version is used when a command is run.
Vi, for example, can have multiple versions, and even variants such as
vim, installed. Recently I custom-compiled
vim in order to get CommandT working and realized that it broke if I ever ran
vi instead of
I fixed this by, first, adding
/usr/local/bin/vim as an alternative for
sudo update-alternatives --install /usr/bin/vi vi /usr/local/bin/vim 1
And subsequently set it as the alternative running the command:
sudo update-alternatives --config /usr/bin/vi