PI-Victor

### Keybase proof

I hereby claim:

  * I am pi-victor on github.
  * I am codeflavor (https://keybase.io/codeflavor) on keybase.
  * I have a public key whose fingerprint is 5BD3 4CAF 8241 BA18 13A6  CF8D 40D2 2757 71DE 3F44

To claim this, I am signing this object:

PI-Victor

Keybase proof

I hereby claim:

• I am pi-victor on github.
• I am codeflavor (https://keybase.io/codeflavor) on keybase.
• I have a public key ASDoBe20-YVhr2Yrq-y1C0zuXsGJnAce5AwjprNZ5SazAQo

To claim this, I am signing this object:

PI-Victor

node {
    // https://registry.hub.docker.com/_/maven/
    def maven32 = docker.image('maven:3.2-jdk-7-onbuild');
    
    stage 'Mirror'
    // First make sure the slave has this image.
    // (If you could set your registry below to mirror Docker Hub,
    // this would be unnecessary as maven32.inside would pull the image.)
    maven32.pull()
    // We are pushing to a private secure docker registry in this demo.

PI-Victor

Keybase proof

I hereby claim:

• I am pi-victor on github.
• I am pivictor (https://keybase.io/pivictor) on keybase.
• I have a public key whose fingerprint is 55ED 0FDA 39A2 678C 1DC4 8C5F 8CB3 1C72 BA2F 7028

To claim this, I am signing this object:

PI-Victor

package main

import (
	"context"
	"fmt"
)

type ErrCommandNotFound struct {
	command string
}

PI-Victor

# System authorization information
auth --enableshadow --passalgo=sha512
# Use CDROM installation media
cdrom
# Perform the kickstart installation in text mode
text
# X will not be configured
skipx
# Don't run the Setup Agent on first boot
firstboot --disable

PI-Victor

You had ONE JOB -- A Kubernetes job.

Let's take a look at how Kubernetes jobs are crafted. I had been jamming some kind of work-around shell scripts in the entrypoint* for some containers in the vnf-asterisk project that Leif and I have been working on. And that's not perfect when we can use Kubernetes jobs, or in their new parlance, "run to completion finite workloads" (I'll stick to calling them "jobs"). They're one-shot containers that do one thing, and then end (sort of like a "oneshot" of systemd units, at least how we'll use them today). I like the idea of using them to complete some service discovery for me when other pods are coming up. Today we'll fire up a pod, and spin up a job to discover that pod (by querying the API for info about it), and put info into etcd. Let's get the job done.

This post also exists as a [gist on github](https

PI-Victor

You had ONE JOB -- A Kubernetes job.

Let's take a look at how Kubernetes jobs are crafted. I had been jamming some kind of work-around shell scripts in the entrypoint* for some containers in the vnf-asterisk project that Leif and I have been working on. And that's not perfect when we can use Kubernetes jobs, or in their new parlance, "run to completion finite workloads" (I'll stick to calling them "jobs"). They're one-shot containers that do one thing, and then end (sort of like a "oneshot" of systemd units, at least how we'll use them today). I like the idea of using them to complete some service discovery for me when other pods are coming up. Today we'll fire up a pod, and spin up a job to discover that pod (by querying the API for info about it), and put info into etcd. Let's get the job done.

This post also exists as a [gist on github](https

PI-Victor

Kafka 0.11.0.0 (Confluent 3.3.0) added support to manipulate offsets for a consumer group via cli kafka-consumer-groups command.

1. List the topics to which the group is subscribed

kafka-consumer-groups --bootstrap-server <kafkahost:port> --group <group_id> --describe

Note the values under "CURRENT-OFFSET" and "LOG-END-OFFSET". "CURRENT-OFFSET" is the offset where this consumer group is currently at in each of the partitions.

2. Reset the consumer offset for a topic (preview)

PI-Victor

original https://unix.stackexchange.com/questions/257163/reduce-title-bar-height-in-gnome-3-gtk-3

After Gnome 3.20, .header-bar.default-decoration doesn't work.

You can put follow content into ~/.config/gtk-3.0/gtk.css:


/* shrink headerbars (don't forget semicolons after each property) */
headerbar {