One of my new year's resolutions is to be less reliant on Google by this time next year. I've wanted to do this for a long time, I'm sure many others do as well once we realize what's involved and why those services are free. However it requires time, maybe in some cases money, and most of all a loss of functionality because there's no denying Google builds great stuff. In the end I'm generally just complacent and end up accempting the warm embrace of slick free services harvesting every possible detail about me to power advertising.
Two years since a post here is pretty abysmal. Not so coincidentally my last post was just around the time I was asked to lead a new OpenShift team being formed to build a project that would power OpenShift Dedicated, our managed Kubernetes offering at Red Hat. Our project was intended to provide an API to drive the provisioning/deprovisioning/reshaping of OpenShift clusters. Originally it was called Cluster Operator and essentially wrapped the Ansible playbooks we used for everything in OpenShift 3.
Last weekend I decided to play around with my old workstation that's just been sitting around powered off for years now, mostly replaced by a RaspBerry Pi3 which handles most of my home network and storage. The workstation is from around 2009, isn't particularly fast but has 6GB of RAM and doesn't consume much power if you yank the video card. I have a small Rails 4 app running as a backend for one of my Android pet projects, and thought it might be fun to repurpose this machine to host it on OpenShift.
For my work on OpenShift I wanted a way to use my local workstation as a test cluster with vms for a master and multiple nodes. Ideally it would be possible to quickly teardown and rebuild the whole cluster, but I also want reliable hostnames (and IPs) across each rebuild. This post outlines a way to do this with Fedora (25 as of writing) and Vagrant. The key to getting Fedora configured such that the hostnames and DNS will work is this post by Dominic Cleal.
I'm currently working on an Ansible role to deploy an application to OpenShift. My application template uses a BuildConfig with a dockerStrategy, so when a build is run it runs against a remote git repo and branch. I wanted my role to ensure that the current deployed application is up to date with the git branch, so we can push changes to that branch and whenever ansible runs it will know to reprocess
I've just uploaded a v1.11 release of NetWorth, my personal finance / net worth tracking / budgeting app for Android. This is a pet project, just modelling how I thought and have learned about personal finance and retirement planning. I was hoping to do a grand 2.0 release but as ever time evaporates and I couldn't quite get there yet. However I did manage to find some time for a lot of nice improvements and figured it was worth pushing them out until I get working on it again.
On my personal VPS I host a handful of websites accessed from a variety of domains and sub-domains, as well as a few more involved webapps such as tt-rss. Historically applications that cross multiple programming languages and databases have been a terrible pain to deploy and keep running on a private server, but since containers have arrived this has become a lot easier. On my server, I wanted to have a web server listening on the standard http/https ports proxying traffic for a variety of sites and applications, based on the domain/sub-domain in the request.
tito 0.6.10 was tagged and built this morning, brought to you almost entirely by the newest tito committer skuznets. Changelog Do not undo tags when git state is dirty (email@example.com) Parse options in tito init (firstname.lastname@example.org) Only use rpmbuild --noclean if it is supported (email@example.com) Explicitly define indicies in formatting statements (firstname.lastname@example.org) Achieve quiet output from rpmbuild without passing --quiet (email@example.com) Update the MANIFEST.in (firstname.lastname@example.org) Correctly pass verbosity options through the builder CLI
I've just pushed a release of tito 0.6.9 with the following changes: Simplified version and release update logic (email@example.com) Added --use-release flag for tito tag (firstname.lastname@example.org) Fix typos/errors in man pages (email@example.com) Explain how automatic tagging was done (firstname.lastname@example.org) Add support for bumping version for Cargo projects (email@example.com) Right now this is available in my Copr repo, and builds are on their way for Fedora and EPEL. My thanks to all who contributed patches!
A demonstration of upgrading an entire OpenShift cluster without application downtime.