mcastelino

Trying Kata Containers with Firecracker (and QEMU)

Clearlinux bundles Kata Containers as well a firecracker.

To quickly experience how Kata Containers can be used to setup a cluster that can run Kubernetes with different types of isolation mechanisms we have created a simple developer enviornment. With this you can run workloads with runc (using cgroups, namespaces provided by the host kernel for isolation), Kata with QEMU/KVM (uses VT-x for isolation and QEMU as the hypervisor) and Kata with Firecracker (uses VT-x for isolation and the minimal Firecracker VMM).

detiber

Thoughts on future Kubeadm work required to streamline experience

Currently the kubeadm config and workflow is centered around a single control plane node and any number of worker nodes. This requires additional workarounds when trying to bootstrap and manage clusters with an HA control plane. I believe there is a path forward that would help streamline the effort required to stand up a fully managed HA control plane including etcd.

• Etcd Config Changes
  • Modify the local etcd config to have an additional parameter for exposing etcd ports or to expose the ports by default
  • Add a attribute to override the exposed advertised ip, preferably by choosing an interface to use for detection
• Make API Server Load Balancer config more explicit instead of just overriding the api config
  • Add new attribute to specify a load balancer, which will implicitly set the api config if not explicitly set
• Control Plane join/extend workflow

eggman

RaspberryPi SDIO

Spec

• BCM2835 ha two sdhost controllers.
• 1 sdhci : Arasan sdhci controller (SD / SDIO)
• 2 sdhost : custom sdhost controller (SD only, but better performance)
• RPi1 use sdhci for SD slot.
• RPi3 use sdhost for SD slot. RPi3 use sdhci for Wi-Fi.

pin

tomwwright

# perform a fresh install of Ubuntu 17.10

# upgrade the kernel to v4.13.10
mkdir ~/kernel-v4.13.10
cd ~/kernel-v4.13.10
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/linux-headers-4.13.10-041310_4.13.10-041310.201710270531_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/linux-headers-4.13.10-041310-generic_4.13.10-041310.201710270531_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.10/linux-image-4.13.10-041310-generic_4.13.10-041310.201710270531_amd64.deb
sudo dpkg -i *.deb

dungvtdev

CAP Theorem: Revisited

Written by Robert Greiner on August 14, 2014

The CAP Theorem states that, in a distributed system (a collection of interconnected nodes that share data.), you can only have two out of the following three guarantees across a write/read pair: Consistency, Availability, and Partition Tolerance - one of them must be sacrificed. However, as you will see below, you don’t have as many options here as you might think.

Consistency - A read is guaranteed to return the most recent write for a given client. Availability - A non-failing node will return a reasonable response within a reasonable amount of time (no error or timeout). Partition Tolerance - The system will continue to function when network partitions occur.

Brainiarc7

Using VAAPI's hardware accelerated video encoding on Linux with Intel's hardware on FFmpeg and libav

Hello, brethren :-)

As it turns out, the current version of FFmpeg (version 3.1 released earlier today) and libav (master branch) supports full H.264 and HEVC encode in VAAPI on supported hardware that works reliably well to be termed "production-ready".

luxas

#!/bin/bash
#
# This is a script for writing the latest Arch Linux ARM files to a SD Card
#
# Based on this tutorial
# http://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2
#
# Usage:
# sudo sh BuildArchLinuxARM.sh [your sd card here]
#

kachayev

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro