dougbtv

#!/bin/bash

# -------------------------------------------------------
# - Deletes networks created by ansible-openshift       -
# - Author: Doug Smith - twitter @dougbtv               -
# -------------------------------------------------------

# What's the cluster name?
CLUSTER_NAME="test_cluster"

dougbtv

author	comments	date	layout	slug	title	category
dougbtv	true	2016-10-31 11:35:00 -0500	post	openshift-on-openstack-easy-mode	OpenShift-on-OpenStack - Part 1 - "Easy Mode"	nfvpe

content here, etc... blah blah.

dougbtv

#!/bin/bash

# Definitions....
EXTERNAL_SUBNET_NAME=ext-net
INTERNAL_SUBNET_NAME=int
ROUTER_NAME=router1
POOL_START=100
POOL_END=120
INTERNAL_CIDR=30.0.0.0/24
DNS_SERVERS=8.8.8.8

dougbtv

# We run tempest in this topology instead of ping test.
# We set introspection to true and use only the minimal amount of nodes
# for this job, but test all defaults otherwise.
control_memory: 8192
compute_memory: 12288

undercloud_memory: 16384

compute_vcpu: 4
compute_disk: 100

dougbtv

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: flannel
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-flannel-cfg

dougbtv

<?xml version="1.0" encoding="utf-8"?><gpx creator="Garmin Desktop App" version="1.1" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/WaypointExtension/v1 http://www8.garmin.com/xmlschemas/WaypointExtensionv1.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd http://www.garmin.com/xmlschemas/GpxExtensions/v3 http://www8.garmin.com/xmlschemas/GpxExtensionsv3.xsd http://www.garmin.com/xmlschemas/ActivityExtension/v1 http://www8.garmin.com/xmlschemas/ActivityExtensionv1.xsd http://www.garmin.com/xmlschemas/AdventuresExtensions/v1 http://www8.garmin.com/xmlschemas/AdventuresExtensionv1.xsd http://www.garmin.com/xmlschemas/PressureExtension/v1 http://www.garmin.com/xmlschemas/PressureExtensionv1.xsd http://www.garmin.com/xmlschemas/TripExtensions/v1 http://www.garmin.com/xmlschemas/TripExtensionsv1.xsd http://www.garmin.com/xmlschemas/TripMetaDataExtensions/v1 http://

dougbtv

Trying kuryr kubernetes

Using CentOS 7

[stack@droctagon4 devstack]$ cat /etc/redhat-release 
CentOS Linux release 7.3.1611 (Core) 

Following the steps using video in this article

dougbtv

What's the story?

A Kubernetes liveness probe tells Kubernetes if a given pod is alive or dead using a custom command (as opposed to default behavior where if a foreground process in a container has terminated, it stops the container which is how it would know the container is alive/dead)

My current knowledge tells me that the lowest possible livenessSeconds setting is 1 second.

According to the Kubernetes API defaults.go file, there is apparently a default of 10 seconds if you enter a value of zero.

I tried to posit (ahem wishfully think ahem) that zero may have meant "as often as possible" but, this experiment and research has shown otherwise.

dougbtv

# General system setup
yum update -y
reboot
yum install docker
systemctl enable docker
systemctl start docker
docker ps
docker -v
yum install -y wget

dougbtv

# Create the clusterrole and clusterrolebinding:
# $ kubectl create -f kube-flannel-rbac.yml
# Create the pod using the same namespace used by the flannel serviceaccount:
# $ kubectl create --namespace kube-system -f kube-flannel.yml
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: flannel
rules: