There are two parts to networking within QEMU:
- The virtual network device that is provided to the guest (e.g. a PCI network card).
- The network backend that interacts with the emulated NIC (e.g. puts packets onto the host's network).
#!/usr/bin/env bash | |
set -e | |
if [ $# != 3 ]; then | |
echo 'Usage: nc-tcp-forward.sh $FRONTPORT $BACKHOST $BACKPORT' >&2 | |
exit 1 | |
fi |
sudo apt-get install autoconf automake libtool curl make g++ unzip -y
git clone https://github.com/google/protobuf.git
cd protobuf
git submodule update --init --recursive
./autogen.sh
./configure
make
make check
sudo make install
# Kubernetes clusters using preemtible instances | |
## Motivation | |
People experimenting with kubernetes clusters on the GKE not | |
necessarily have money to keep a full cluster on at all time. GKE | |
clusters can be easily resized, but this still incurs in the full | |
instance cost when the cluster is up. | |
Google has added preemptible instances that are ideal for many |
for i in $(kubectl get csr | grep Pending | awk '{ print $1 }' ) ; do kubectl certificate approve $i; sleep 1; done |
package main | |
import ( | |
"fmt" | |
"os" | |
"os/signal" | |
"time" | |
"golang.org/x/net/context" | |
) |
Kubernetes is great! It helps many engineering teams to realize the dream of SOA (Service Oriented Architecture). For the longest time, we build our applications around the concept of monolith mindset, which is essentially having a large computational instance running all services provided in an application. Things like account management, billing, report generation are all running from a shared resource. This worked pretty well until SOA came along and promised us a much brighter future. By breaking down applications to smaller components, and having them to talk to each other using REST or gRPC. We hope expect things will only get better from there but only to realize a new set of challenges awaits. How about cross services communication? How about observability between microservices such as logging or tracing? This post demonstrates how to set up OpenTracing inside a Kubernetes cluster that enables end-to-end tracing between serv