Inventor's Paradox

When using and tending an Openshift Origin cluster (for example, Origin version 3.7), it is normal to start the storage allocation in small sizes. However soon we find that storage for registry get filled up quickly with images from each build process. This post will show how to clean them up. Preparation before pruning First you need oc (origin client) binary and a user account with cluster administration capability. If the openshift docker registry  is installed inside the cluster without external access, then you also going to need OS access to one of the hosts inside the cluster. First step is to login to the cluster from your client or inside one of the hosts: oc login Prune steps Reading the documentation (https://docs.openshift.com/enterprise/3.0/admin_guide/pruning_resources.html) we find that the pruning starts at deployment, then builds, and last images. Pruning Deployment  Run this to preview which deployment are going to be pruned: oc adm pru...

This post is a place where I would note prices relating to Cloud Storage. As A consumer Amazon : S3 (Simple Storage Service) : $0.03 /GB/month for first TB  (ref: https://aws.amazon.com/s3/pricing/) Glacier : $0.01 /GB/month EC2 Elastic Block Storage : SSD $0.1 /GB/month  magnetic : $0.05 /GB/month  + $0.05 /million IO Google : (ref : https://cloud.google.com/storage/pricing) Standard Storage : $0.026 /GB/month, $0.01 /GB/month nearline   Microsoft sells: (ref : https://onedrive.live.com/about/en-us/plans/) 15 GB : free 100 GB : $1.99 /month (means  $0.019 /GB/month) 200 GB : $3.99 /month 1 TB : $7 / month (include Office 365) As a provider  SwiftStack controller : (http://itknowledgeexchange.techtarget.com/storage-soup/swiftstack-enters-software-defined-storage-race/) subscription : $10 / TB/month (means $0.01 /GB/month) EMC VIPR :  (http://silvertonconsulting.com/blog/2013/09/30/emc-vipr-virtues...

This post will describe the steps that I take to provide shared storage for OpenShift Origin M4 installation. There were some difficulties that must be solved by non standard methods. Requirement When hosting applications on Openshift Origin platform, we are confronted with a bitter truth : writing applications for cloud platforms requires us to avoid writing to local filesystems. There is no support for storage shared between gears. But we still need support multiple PHP applications that stores their attachment in the local filesystem with minimal code changes. So we need a way to quickly implement shared storage between gears of the same application. And maybe we could loosen the application isolation requirement just for the shared storage. Basic Idea The idea is to mount an S3 API-based storage on all nodes. And then each gear could refer to application's folder inside the shared storage to store and retrieve file attachments. My implementation uses an EMC VIPR shared ...

The internet has pampered our users by giving them 99.9% uptime. Now every corporation needs to have similar availability to 99.9%. One part of high availability solution is the storage. In the good old proven corner we have SAN and NAS storage solutions. They are not always highly available (you must ensure the system has more than one controller, in case one controller is broken, and RAID 5 is nowhere enough these days, choose RAID 6, and dont forget network rendundancy), but they are almost always expensive. In the era where IT Directors forced to think 'cost transformation', we always welcome cost-saving alternatives. New hardware developments influenced our infrastructure options, lets write the factors down: abundance of cheap gigabit ethernet card & router -> this allow us to forget expensive fiber connetivity, and allow us to leverage newly developed distributed systems. cheap large SATA drives -> large commodity storage for the masses Development o...