Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
[Gist Page] | |
info.redhatgov.io | |
[Lab Guide] | |
http://redhatgov.io/workshops/openshift_101_dcmetromap/ | |
[OpenShift Console] | |
https://master.ocp-naps.redhatgov.io:8443/console | |
[Terminal] |
source kops | |
export BUCKET_NAME=devops23-$(date +%s) | |
export KOPS_STATE_STORE=s3://$BUCKET_NAME | |
aws s3api create-bucket \ | |
--bucket $BUCKET_NAME \ | |
--create-bucket-configuration \ | |
LocationConstraint=$AWS_DEFAULT_REGION |
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" |
#!/bin/bash | |
# | |
# This script configures WordPress file permissions based on recommendations | |
# from http://codex.wordpress.org/Hardening_WordPress#File_permissions | |
# | |
# Author: Michael Conigliaro <mike [at] conigliaro [dot] org> | |
# | |
WP_OWNER=www-data # <-- wordpress owner | |
WP_GROUP=www-data # <-- wordpress group | |
WP_ROOT=$1 # <-- wordpress root directory |
<?php | |
/** | |
* ICS.php | |
* ======= | |
* Use this class to create an .ics file. | |
* | |
* Usage | |
* ----- | |
* Basic usage - generate ics file contents (see below for available properties): |
This document shows how to deploy an OpenShift instance on a server using CodeReady Containers (crc) that can be accessed remotely from one or more client machines (sometimes called a "headless" instance). This provides a low-cost test and development platform that can be shared by developers. Deploying this way also allows a user to create an instance that uses more cpu and memory resources than may be available on his or her laptop.
While there are benefits to this type of deployment, please note that the primary use case for crc is to deploy a local OpenShift instance on a workstation or laptop and access it directly from the same machine. The headless setup is configured completely outside of crc itself, and supporting a headless setup is beyond the mission of the crc development team. Please do not ask for changes to crc to support this type of deployment, it will only cost the team time as they politely decline :)
The instructions here were tested with F