ziwon

# Download the VDI from https://cdn.amazonlinux.com/os-images/latest/
# Doc is at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html  
# Be sure you have config/meta-data and config/user-data ready as per the below
# change ec2-user's password to your password

$ cat config/meta-data

local-hostname: amazonlinux.onprem

# eth0 is the default network interface enabled in the image. You can configure

ziwon

Getting started with Linux kernel development

Prerequisites

The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.

It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.

Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.

ziwon

Keybase proof

I hereby claim:

• I am ziwon on github.
• I am ziwon (https://keybase.io/ziwon) on keybase.
• I have a public key whose fingerprint is EB95 E596 FCC0 7C72 EE62 CCD7 81A8 2D6E 1ABC 9F7A

To claim this, I am signing this object:

ziwon

sudo yum install graphviz -y
sudo pip install aws-visualizer
profilename=worldskills
profileregion=us-east-1

rm -rf target/$profilename
mkdir -p target/$profilename/default
mkdir -p target/$profilename/securitygroups
mkdir -p target/$profilename/subnets

ziwon

google cloud shell을 이용해서 proxy 서버로 사용해서 공짜로 vpn처럼 이용하기

google cloud shell은 public ip가 없는 private ip만 있는 container입니다. 즉 외부 접근은 google client들을 통해서만 접근이 가능한데 이런 자원들을 가지고 외부에 접근 하는 proxy만드는 법에 대한 소개입니다.

MYNOTEBOOK 이 내가 접속하고 있는 chrome을 띄울 pc라고 보시면 됩니다. 물론 보통은 포트포워딩 해서 접속 할 수 있게 열어야 한다고 보시면 됩니다.

docker run -ti \

ziwon

#!/bin/bash

create_user_cert(){
    USER=$1
    CERTS_PATH=/etc/kubernetes/pki/users/${USER}
    echo "Creating certificates for user ${USER}"
    mkdir -p ${CERTS_PATH}
    openssl genrsa -out ${CERTS_PATH}/${USER}.key 2048
    openssl req -new -key ${CERTS_PATH}/${USER}.key -subj "/CN=${USER}" -out ${CERTS_PATH}/${USER}.csr
    openssl x509 -req -in ${CERTS_PATH}/${USER}.csr -CA /etc/kubernetes/pki/ca.crt -CAkey /etc/kubernetes/pki/ca.key -CAcreateserial -out ${CERTS_PATH}/${USER}.crt

ziwon

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

ziwon

#!/bin/sh

if [ "$EUID" -ne 0 ]; then 
	echo -e "\nPlease run as root\neg. sudo $0 \n"
	exit
fi

GITHUB_USERNAME="ebal"

cd `mktemp -d`

ziwon

Producer

Setup
bin/kafka-topics.sh --zookeeper esv4-hcl197.grid.linkedin.com:2181 --create --topic test-rep-one --partitions 6 --replication-factor 1
bin/kafka-topics.sh --zookeeper esv4-hcl197.grid.linkedin.com:2181 --create --topic test --partitions 6 --replication-factor 3

Single thread, no replication

bin/kafka-run-class.sh org.apache.kafka.clients.tools.ProducerPerformance test7 50000000 100 -1 acks=1 bootstrap.servers=esv4-hcl198.grid.linkedin.com:9092 buffer.memory=67108864 batch.size=8196

ziwon

# GIT aliases for ~/.gitconfig file
# @author Grzegorz Korba <[email protected]>
# Credits: Miscellaneous places on the Internet...

# GitFlow related sections
[gitflow "branch"]
    master = master
    develop = develop
[gitflow "prefix"]
    feature = feature/