ram-pi

Certificate CA Validation

The easy way

To validate a certificate agains a certificate authority you just have to run

openssl verify -trusted ca_root.pem -untrusted intermediate_ca.pem certificate.pem

You'll see a 'OK' message at the end of the output

ram-pi

#!/usr/bin/env bash

# example usage: ./offsets_mover.sh localhost:9092 client.1.properties localhost:9093 client.2.properties

# get bootstrap servers from args
BOOTSTRAP_SERVER=$1

# get properties file location from args
PROPERTIES_FILE=$2

ram-pi

#!/usr/bin/env bash

# example usage: ./ips.sh localhost:9092 /etc/kafka/consumer.properties

# get bootstrap servers from args
BOOTSTRAP_SERVER=$1

# get properties file location from args
PROPERTIES_FILE=$2

ram-pi

Enable memberOf attribute on an openldap server.

Source: https://www.brianshowalter.com/blog/installing-configuring-openldap

ram-pi

#!/usr/bin/env bash

# This script is used to failover all the mirror topics from one link to another
# Usage: ./run.sh <link_id>
# Example: ./run.sh link2

# prerequisites: 
# - install jq
# - install confluent cli
# - login to confluent cloud using "confluent login" and select the environment and cluster with "confluent env use xxx" and "confluent kafka cluster use xxx

ram-pi

using System;
using Confluent.Kafka;

class Program
{
    public static void Main(string[] args)
    {
        var conf = new ProducerConfig { 
            BootstrapServers = "localhost:9092",
            SecurityProtocol = SecurityProtocol.SaslPlaintext,

ram-pi

from socket import socket, AF_INET, SOCK_DGRAM
import time
import sys


host = "localhost"
port = 10514

UDPSock = socket(AF_INET, SOCK_DGRAM)

ram-pi

#!/usr/bin/env bash

# Usage: change_replication_factor.sh <bootstrap-server> <broker-list> <blacklist-prefixes> <min-isr> <extra-var> 
# Example: ./change_replication_factor.sh localhost:9092 1,2,3 _confluent,_schemas 2 --comment-config client.properties
# Example: export PATH=$PATH:/path/to/kafka/cli/bin ; ./change_replication_factor.sh localhost:9092 1,2,3 _confluent,_schemas 2 --comment-config client.properties
# Requires: jq, kafka-topics, kafka-reassign-partitions, kafka-configs
# Author: @ram-pi
# Version: 0.1
# Date: 2023-11-06
# Description: Change replication factor and min.insync.replicas for all topics in a Kafka cluster

ram-pi

#!/bin/bash

# ./sr_clean.sh https://myhost.confluent.cloud MY_KEY MY_SECRET ":." 

echo "Schema Registry URL: $1"
echo "Subjects Prefix: $4"

SR_URL=$1
API_KEY=$2
API_SECRET=$3

ram-pi

Adding 2 nodes to an existing 3-node ZooKeeper ensemble without losing the Quorum

Since many deployments may start out with 3 nodes and so little is known about how to grow a cluster from 3 memebrs to 5 members without losing the existing Quorum, here is an example of how this might be achieved.

In this example, all 5 nodes will be running on the same Vagrant host for the purpose of illustration, running on distinct configurations (ports and data directories) without the actual load of clients.

YMMV. Caveat usufructuarius.

Step 1: Have a healthy 3-node ensemble