vkmc

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

vkmc

--- 
services: 
  db: 
    environment: 
      MYSQL_DATABASE: wordpressdb
      MYSQL_PASSWORD: linuxchixar
      MYSQL_ROOT_PASSWORD: linuxchixar
      MYSQL_USER: linuxchixar
    image: "mysql:5.7"
    restart: always

vkmc

1. Get latest Raspbian Jessie + Pixel -> https://downloads.raspberrypi.org/raspbian_latest.torrent
2. Burn on MicroSD -> Suggested tool: https://etcher.io/
2. Get 3.5 TFT Display drivers http://www.spotpear.com/learn/EN/raspberry-pi/Raspberry-Pi-LCD/Drive-the-LCD.html. Most vendors use the same
3. Get Retropie source https://github.com/RetroPie/RetroPie-Setup.
4. Run ./retropie-setup.sh. Get ROMs for the desired emulators and store them under RetroPie/roms.
5. Get RPI FBCP (required to redirect to secondary framebuffer) -> https://github.com/tasanakorn/rpi-fbcp. Emustation won't run otherwise.
6. Compile (follow README instructions on the main repo) and run with ./fbcp
7. You should be able to run emulationstation and succeed.

vkmc

#!/bin/bash

## Derives from: http://giovannitorres.me/create-a-linux-lab-on-kvm-using-cloud-images.html

## Assumes you have a xenial cloud image in $DIR below, via e.g.
# wget https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img

# Take one argument from the commandline: VM name
if ! [ $# -eq 1 ]; then
    echo "Usage: $0 <node-name>"

vkmc

VPP
tap connect tap0
tap connect tap1
tap connect tap2
set interface state tap-0 up
set interface state tap-1 up
set interface state tap-2 up
set interface ip address tap-0 1::1/64
set interface ip address tap-1 2::1/64
set interface ip address tap-2 3::1/64

vkmc

D, S
1::/1, 2::/1
1::/1, 2::/2
1::/1, 2::/3
...
1::/1, 2::/128
1::/2,

vkmc

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄░░░░░░░░░
░░░░░░░░▄▀░░░░░░░░░░░░▄░░░░░░░▀▄░░░░░░░
░░░░░░░░█░░▄░░░░▄░░░░░░░░░░░░░░█░░░░░░░
░░░░░░░░█░░░░░░░░░░░░▄█▄▄░░▄░░░█░▄▄▄░░░
░▄▄▄▄▄░░█░░░░░░▀░░░░▀█░░▀▄░░░░░█▀▀░██░░
░██▄▀██▄█░░░▄░░░░░░░██░░░░▀▀▀▀▀░░░░██░░
░░▀██▄▀██░░░░░░░░▀░██▀░░░░░░░░░░░░░▀██░
░░░░▀████░▀░░░░▄░░░██░░░▄█░░░░▄░▄█░░██░
░░░░░░░▀█░░░░▄░░░░░██░░░░▄░░░▄░░▄░░░██░

vkmc

trove-taskmanager.conf

[DEFAULT]
# Show more verbose log output (sets INFO log level output)
verbose = True

# Show debugging output in logs (sets DEBUG log level output)
debug = False

# Update the service and instance statuses if the instances fails to become

vkmc

Trove on RHEL OSP 7.0
*********************

Deployment details
==================

PackStack all-in-one using Kilo packages on CentOS 7.

Precisely, we followed the instructions here https://www.rdoproject.org/Quickstart with
current sudo yum install -y https://rdoproject.org/repos/rdo-release.rpm.

vkmc

Debugging OpenStack components on DevStack
==========================================

By default, DevStack [0] uses GNU Screen [1] to display all the execution traces of the different components in the deployment.
Learning how to use the screen is crucial for the development process given that you will be able to have a better
understanding of what is going on under the hood.

This gist aims to be a cheatsheet for all the people getting started with OpenStack development using DevStack.

Connect to the screen session