Skip to main content

rancher very quick start

This is so easy and simple it makes me nuts:

  • download and install virtualbox
  • download and install vagrant
  • git clone
  • cd os-vagrant
  • vagrant up
  • vagrant ssh rancher-01
  • docker run -d -p 8080:8080 rancher/server
  • ifconfig (get the eth1 ipaddr)
  • open local browser:
  • click hosts (already by default view)
  • click + add host
  • review and click save settings
  • click custom
  • copy the command in step 3 omit the leading 'sudo'
  • exit (CTRL+D) the terminal session on rancher-01
  • vagrant ssh rancher-02
  • paste the command: docker run -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.5.2
  • exit (CTRL+D) the terminal session on rancher-02
  • vagrant ssh rancher-03
  • paste the command: docker run -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.5.2
  • you might have to refresh the browser a few times as the agent(s) startup
At this point you have a 3 node deployment of rancherOS with rancher server running on rancher-01 and rancher agent(s) running on nodes rancher-02 and rancher-03.

If you're an enterprise class user:
  • then you might need to increase the number of nodes in the Vagrantfile, redeploy, relink all of the agents and so on
  • you'll want to deploy your own registry server
  • and you might want to disable or intercept the public repos via some dns trickery
The rancher tooling does not include any OS or rancher tools for monitoring, health, alerting, logging and so on... so you really have to start bolting IoT (internet of things) onto your environment. It also depends on whether you want to self host these operations or add SaaS type operations.

One thing to note about any of these orchestration applications. (a) there is a certain amount of magnification (or Mandelbrot) that takes place between bare metal and containers; so keep an eye on the APIs because they may be the one constant. (b) you will still need bare metal servers to provide services that you do not want to be inside the VM or container. HA/load balancers, NTP, DNS, PXE server and storage servers come to mind.

PS: if you are going to run rancherVMs inside your containers then you gotta have huge bare metal hosts and you need a way to orchestrate the work as rancher leaves that to the user.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…