Macduff macduff23

How to Build and Install a Monero Node on a Debian-based System

Hello. In this document, we will walk through the steps of building and hosting your own Monero node from source on a Debian-based Linux system. These systems include Raspbian, Debian (9 and above), and Ubuntu (18.04 and above). This tutorial assumes that you are capable of accessing the ROOT terminal of your Debian-based system, and are capable of getting your system online if necessary. You may plan on using an external storage device to store the blockchain, this tutorial will include the optional steps to support external storage. Alternatively, this setup procedure can also accomodate users looking to host a pruned blockchain with restricted storage space.

Here are some useful links for reaching this prerequisite if you do not currently have access to a Debian-based system that meets the recommended system requirements.

How to spawn a VPS in the Linode Cloud Platform
[How to spawn a VP

Ingress MetalLB

Out of the box, the MicroK8s distribution of ingress-nginx installed as the MicroK8s addon ingress binds to ports 80+443 on the node's IP address using a hostPort, as we can see here:

microk8s kubectl -n ingress describe daemonset.apps/nginx-ingress-microk8s-controller
Name:           nginx-ingress-microk8s-controller
Selector:       name=nginx-ingress-microk8s

% VXLAN lab based on OpenVSwitch and LXD containers

Preamble

The very first idea when I started writing this lab was to illustrate the Virtual Extensible LAN (VXLAN) technology. Now that OpenVSwitch configuration is smoothely integrated in the Debian networking configuration files, this should have resulted in somewhat easy-to-read gist.

Adding sub-interface and IP Addresses using NetPlan on Ubuntu 18.04

Edit `/etc/netplan/*.yml`

network:
  version: 2
  # renderer: NetworkManager
  ethernets:
 eth0:

Install Rancher 2.0 HA by using self signed certificates (+ intermediate) and Layer 4 Loadbalancer (TCP)

Warning: the RKE install method is only supported up to v2.0.8!

This gist describes how to setup Rancher 2 HA, by using self signed certificates (with intermediate) and a Layer 4 Loadbalancer (TCP)

Requirements

Linux OS
OS Binaries

First install fish shell on your system

sudo apt-get update
sudo apt-get install fish

Or install fish via ppa

sudo apt-add-repository ppa:fish-shell/release-2
sudo apt-get update

sudo apt-get install fish``

	# -- mode: ruby --
	# vi: set ft=ruby :

	VAGRANTFILE_API_VERSION = "2"
	Vagrant.require_version ">=1.7.0"


	$bootstrap_ovn = <<SCRIPT

	# Add repo for where we can get OVS packages

	#!/bin/sh
	###
	# MicroK8s + Rancher installer
	##

	# 如果您的環境不是在 GCP 請自行調整以下兩個變數
	EXTERNAL_IP=$(curl -s 169.254.169.254/computeMetadata/v1beta1/instance/network-interfaces/0/access-configs/0/external-ip)
	PROJECT_ID=$(curl -s 169.254.169.254/computeMetadata/v1beta1/project/project-id)

	sudo snap install microk8s --channel=1.18 --classic

	# Install microk8s from the edge channel (Rancher requires Helm 2.15.1 or above)
	sudo snap install microk8s --classic
	# Enable useful plugins
	sudo microk8s.enable dns dashboard storage ingress helm

	# Allow running priviledged Pods (required by Rancher's `cattle-node-agent`)
	sudo sh -c 'echo "--allow-privileged=true" >> /var/snap/microk8s/current/args/kube-apiserver'
	sudo systemctl restart snap.microk8s.daemon-apiserver.service

	# Setup and install Tiller (part of Helm)

	---
	- hosts: all
	tasks:
	- name: Install prerequisites for Docker repository
	apt:
	name: ['apt-transport-https', 'ca-certificates', 'curl', 'gnupg2', 'software-properties-common']
	update_cache: yes

	- name: Add Docker GPG key
	apt_key: