This is a follow up to my previous post Exploring Kubernetes. This time, I have expanded to a multi-node cluster. Here are a few notes and problems that I found along the way.
If you go potholing in the kubernetes releases, it isn't so bad. Here are my adventures trying to package, deploy and run containers on top of kubernetes (on Gentoo).
Recently, I've been working on ways to create OpenStack ready cloud images. While I do have acess to a local instance of OpenStack, sometimes it becomes necessary to test the images on a local machine to fine tune the boot process.
There's a cool trick where you can efficiently share a filesystem with a VM. Until Linux Containers beef up their security from first principals, hardware emulation is one of the stronger methods of locking down and isolating services.
This blog post is my reply to a recent blog post about rolling releases. I'm firmly in the Gentoo camp. For me, it's about knowledge and control over how my machines are setup and configured, with an emphasis on safety.
I've been playing with a parallella board. Here are my first impressions of what is hoped to be the future direction of massively parallel computing.
I really shouldn't be let near web development. Having said that, I've been spending more time writing and re-writing blog, rather than writing the blog posts themselves.
I haven't posted in a little while, so here's a nice juicy tutorial that I've been working on. There's some more news surrounding this, but I think that I'll start off with a Homemade Hypervisor for you to sink into.
You forgot to load xen backend modules. Guest domains will boot, but
are waiting for the host (dom0) to provide device implementations.
Python 3.4 is out today! So here is the third and final part in my series about some of the new shiny that comes with. The end goal is to be able to write non-blocking code without changing our synchronous habits. I'll start with a simple TCP server that listens for connections and spits out whatever is received. This should be familiar to anyone who is new to socket programming.
In my last post, I showed the basics of the new asyncio module brings to python programming. What a coroutine is, how to run them and getting the results back in ways that should be readable by most python programmers. The routines are quick examples how to get started, and hopefully can be used to eliminate some of the waiting that io-bound programs have.
I've been itching to play with some of the new features of python 3.4. The most anticipated feature is the new asynchronous module which should, the hope is, let us run concurrent code without going insane. This will be a code heavy post, with some very new features that the community at large hasn't really decided on any best practices yet. This will probably be a multi part series getting deeper into the intricacies of async programming in python. I haven't yet seen a good series of idioms yet, so this is mostly exploratory. This post will serve as an introduction to using async programming for the synchronously minded. Later I'll go into some of the extra APIs that let you really make the most of async programming. After that I'll try to make a third post about using these techniques to do something more practical than waiting for sleep().
Looks like dev-lang/python:3.4 is in Gentoo's portage tree. Currently masked for testing.
Two days ago, Jolla have released the second update to SailfishOS.
Here's an interesting consequence of threaded programming that I found in python today.
I can't believe that I haven't posted about this before, and I google around for it every time.
You may have noticed the change.
I've had the Pixel for a few months now. The most surprising thing that I've realised is how much time I have been using this without modifications. In the first month, I immediately dropped into devmode, installed Gentoo, Debian and my own builds of ChromiumOS.
In my quick review of systemd, I left a few points hanging for further elaboration.