v1k0d3n

---
# Using unsupported SR-IOV NICs w/OpenShift
apiVersion: v1
kind: ConfigMap
metadata:
  name: unsupported-nic-ids
  namespace: openshift-sriov-network-operator
data:
  X520: 8086 154d 10ed
  X540: 8086 154d 10ee

v1k0d3n

#Set hostname
hostnamectl set-hostname lb01-server.example.com

#Remove all network configuration
nmcli con del eno{1,2,3,4}

#Configure bonding
nmcli con add type bond con-name bond0 ifname bond0 mode active-backup
nmcli con add type bond-slave con-name eno1 ifname eno1 master bond0
nmcli con add type bond-slave con-name eno2 ifname eno2 master bond0

v1k0d3n

How do I dropdown?

This is how you dropdown.

<details>
<summary>How do I dropdown?</summary>
<br>
This is how you dropdown.

v1k0d3n

How To Update All Python Packages

• List Outdated Packages
• Update All Python Packages
  • Windows
  • Linux
• Update Specific Packages On Windows Or Linux
• References

List Outdated Packages

v1k0d3n

##Dockerfile
FROM centos:7
RUN yum update -y && yum install -y wget perl openssl-devel dmidecode

RUN wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash
RUN yum install -y srvadmin-idracadm7

RUN cp /opt/dell/srvadmin/bin/idracadm7 /usr/local/bin/racadm

##Build via... (run inside somedir/Dockerfile)

v1k0d3n

OpenShift Assisted Installer w/Calico as Default CNI

Red Hat quietly released a new method for installing bare metal OpenShift clusters via a tool called Assisted-Installer (or Assisted-Service). What makes this service really unique is that it reduces the infrastructure requirements for deploying bare metal clusters (i.e. PXE/UEFI, web servers, etc). Reduction of these legacy bare metal requirements opens up some interesting opportunities for carrier-based deployments such as RAN, MEC, uCPE, Content Delivery, and many other Edge or FE types of solutions.

Of course, there's a straightforward user-interface which can be leveraged, but I think what is most interesting about the Assisted-Service centers around customizations through it's REST API. This is in fact what I'm going to cover in this blog.

So how does this all work for bare metal without UEFI, DHCP and other traditional bootstrapping methods, you might ask? The Assisted-Installer is used to produce a LiveISO which includes a call-back URL for the

v1k0d3n

• Combine the pull secrents from Quay and the one from the local registry

jq -s '.[0] * .[1]' pull-secret.json local-auth.json  > pull-secret-2.json

• Mirror relrease

export AIRGAP_SECRET_JSON='pull-secret-2.json'

v1k0d3n

#!/bin/sh
# profile patches are cumulative: http://blogs.vmware.com/vsphere/2013/10/are-esxi-patches-cumulative.html
# favour update over install: http://www.v-front.de/2013/05/quickest-way-to-update-your-standalone.html
esxcli network firewall ruleset list | grep httpClient
# Enable http:
esxcli network firewall ruleset set -e true -r httpClient
# List updates:
esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
# Only relevant updates:
esxcli software sources profile list --depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | sort | grep -w standard | grep "ESXi-5.1.0-20"

v1k0d3n

Synology NAS - How to make a program run at startup
The other day I created a little node.js project to keep track of some finances. Synology has a node.js package but that just installs the tools - it has no 'container' or any other support to drop files and have it run automagically. Maybe one day.

In the meantime, you can start your project when you SSH into the NAS. My project has a 'www' script which bootstraps my project, so to start I simply type 'node bin/www' from the project directory. But, it only runs while I'm logged in, and if I log out for any reason, the process dies. That's hardly useful when I'm away from home, or on a different PC. So I decided to have a look at starting my project as a Linux service.

After doing a lot of research into how Synology does services, and a few failed attempts at init scripts, I found that Synology DSM (since version 5 perhaps) bundles Upstart, which is a neat little tool to deal with services on Linux. It's most prevalent on Debian and derivatives (notably Ub

v1k0d3n

Setup CoreDNS w/ etcd backend

Why CoreDNS

[CoreDNS][coredns] was designed from the ground up to provide robust, plugin-based DNS server for use in cloud environments. Namely, it serves as the default primary service discovery mechanism for Kubernetes.

Using CoreDNS allows us to have a lightweight DNS server on RockNSM (11 Mb binary is all that's needed!) to facilitate multi-node service discovery. Alternatively, if another existing DNS service is available, this can be used instead. Aligning with the way the Kubernetes manages service discovery also allows us to build new RockNSM features in parallel with the coming Kubernetes support.

RockNSM Application