The article previously hosted here is now published on my website: My ErgoDox Keyboard.
import time | |
import os | |
import logging | |
from daemon.runner import DaemonRunner | |
_base_path = "/path/to/daemon" | |
class MyApp(object): | |
""" | |
Define the required attributes |
import xmlrpclib | |
s = xmlrpclib.ServerProxy('http://localhost:9900') | |
print s.uptime() | |
users = s.users() | |
for user in users: | |
for login in users[user]: | |
print user, login |
# vim: tabstop=4 shiftwidth=4 softtabstop=4 | |
#!/usr/bin/python | |
import sys | |
import time | |
import logging | |
from daemon import runner | |
# | |
# An example daemon main logic application class. | |
# Just keep writing timestamps to a log file periodically. | |
# |
How to Install VNC on an AWS EC2 Centos 7.2 AMI | |
Reference: http://devopscube.com/how-to-setup-gui-for-amazon-ec2-rhel-7-instance/ | |
1. Update the server using the following command. | |
sudo yum -y update | |
2. Install the gnome GUI components using the following command. | |
sudo yum groupinstall -y "Server with GUI" |
Let's look at an example of how to launch a Kubernetes cluster from scratch on DigitalOcean, including kubeadm, an Nginx Ingress controller, and Letsencrypt certificates.
We'll be creating a four-node cluster (k8s-master, k8s-000...k8s-002), load balancer, and ssl certificates.
console.log("got here"); | |
var page = require('webpage').create(); | |
page.onConsoleMessage = function(msg) { | |
console.log(msg); | |
}; | |
page.open("http://facebook.com", function(status) { | |
if ( status === "success" ) { |
ETHERNET ADAPTOR HARDWARE ADDRESS REQUIREMENTS
When provisioning VMs for the cluster, the ethernet interfaces configured for each VM must use a MAC address from the VMware Organizationally Unique Identifier (OUI) allocation ranges:
00:05:69:00:00:00 to 00:05:69:FF:FF:FF
00:0c:29:00:00:00 to 00:0c:29:FF:FF:FF
00:1c:14:00:00:00 to 00:1c:14:FF:FF:FF
00:50:56:00:00:00 to 00:50:56:FF:FF:FF
This follows the documentation for mirroring images.
-
Download the images
- Use
dryrun.sh
to get the `ImageContentSourcePolicy`` needed for the disconnected cluster.
- Use
The values used for the destination registry, which are used for the ICSP, can be arbitrary and changed on the disconnected network to represent your scenario. This is useful if the hostnames / IPs are sensitive.