Doug Smith dougbtv

Referring to "global namespaces" using Multus CNI in OpenShift

This demonstrates using a cross-namespace reference in OpenShift to refer to net-attach-defs in the openshift-multus namespace from another namespace.

See the additional pod.yml and net-attach-def.yaml files included in this gist.

Using latest OCP from CI (4.9 master)

Clearing IP allocations manually with Whereabouts

This outlines a process for clearing IP address allocations with Whereabouts manually. This clears all allocations, you could be more surgical about it, however, this is efficient if it's possible.

NOTE I have another procedure somewhere which has fancy bash commands to make this easier, and is fully tested, however, in theory this "should just work" (you've heard that before)

Overview

Stop all pods which use Multus + Whereabouts (if possible)
Clear IP allocations

Flatten and verify on Matic blockscout explorer

I was having trouble verifying my contracts on the Matic blockscout explorer when they were using included files such as the openzepplin libraries.

I found that I was not having good luck with the truffle-flattener, so I went out seeking something else.

I wound up using: https://github.com/DaveAppleton/SolidityFlattery -- which I found from this openzeppelin thread.

You'll need to install golang and configure your gopath.

all-in-one-example

---
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: centos-runtimeconfig-def
spec:
  config: '{

First, type the Konami code into your terminal, then...

Create a user, then create a password for the user...

oc create user doug
htpasswd -c -B -b /tmp/doughtpass doug s00persecret

Create an ident yaml...

First create the resources.yml to create a service account, RBAC & bindings for it, as well as a pod that uses the downward API to get its own name...

kubectl create -f resources.yml

Now you can exec into the pod...

$ kubectl exec -it toolpod -- /bin/bash

SR-IOV with OpenShift Virtualization

We're going to use SR-IOV technology with OpenShift Virtualization. Today we're going to cover looking at the SR-IOV network attachment definitions, spinning up VMs associated with those, and then we'll make a SIP phone call over the VMs (because we're all bored of a ping test!)

Notably, this gist does not cover installing the SR-IOV Operator, configuring the SR-IOV operator.

The NetworkAttachmentDefinition (which defines an intent to attach additional networks to pods in Kubernetes, which you typically see by the presence of an additional network interface) that we use here is the one [provided by default by the SR-IOV network operator](https://docs.openshift.com/container-platform/4.5/netw

	const axios = require('axios');

	// Server URL
	const server = "http://192.168.50.201:5000/api/v1/generate";

	// Generation parameters
	// Reference: https://huggingface.co/docs/transformers/main_classes/text_generation#transformers.GenerationConfig
	const data = {
	'prompt': 'recommend a cheese please',
	"max_new_tokens": 100,

	---
	kind: DaemonSet
	apiVersion: apps/v1
	metadata:
	name: multus-additional-cni-plugins
	namespace: kube-system
	annotations:
	kubernetes.io/description: \|
	This daemon installs and configures auxiliary CNI plugins on each node.
	spec:

	#!/usr/bin/env bash

	DEBUG=true
	# LOGFILE=/tmp/seamless.log

	# Outputs errors to stderr
	errorlog () {
	>&2 echo $1
	}