Migrate your OpenShift Container to AWS Platform
Welcome to WordPress. This is your first post on a new server. Edit or delete it, then start writing!
Probably you have noticed that tagline when first installing a WordPress blog on your own or creating a new blog under WordPress.com domain. Welcome to WordPress.
Yes, this blog just migrated on September 2017 from my old hosting, OpenShift server from Red Hat. Previously, I was running this blog and its component from the OpenShift Cloud by Red Hat.
If you have read my few first post about the technology behind this blog, you probably know that OpenShift was giving free “cartridge” or free space instance inside their AWS server as a container. (Update on 2018 – all OpenShift platform is no longer free of charge)
Unfortunately, after OpenShift version 3 launched in September, as I was running on OpenShift version 2, the version was going to decommission. Exactly on 30 September 2017, the version 2 no longer be accessible and all customers need to migrate their account to the new version. But, with a new regulation, the basic plan needs the website owner to turn off their instance around 18 hours after 72 hours of runs (https://www.openshift.com/pricing/index.html).
This doesn’t make sense if you had an OpenShift version 2 that was giving you free and unrestricted uptime unless you have very minimal traffic or for a testing environment.
Before I do the new migration server, I was comparing few other options such as Heroku, AppFog, and other PaaS out there, but unfortunately, none serving hosted service built in like OpenShift. So my main focus for the new migration server is more towards hosting services/cloud services.
I compared few hosting services such as Amazon, Microsoft Azure, Google Cloud but seems the one giving me very good impression in the administration is Amazon. Moreover, in my day job as a DevOps, I heavily invested my time to administer in next-generation cloud based on AWS services. So it will be aligned with my expertise.
Therefore, this blog now is running solely on the AWS instances and I can do all of the administration by my own. The new migration server for this blog I can say considered as successful as I don’t need to make a lot of adjustment for it. One thing that I consider carefully is whether or not using Docker as our main platform or fresh install under machine itself.
So far the uptime for this blog almost nearly 99.9% without any hassle. Now I concentrate my learning process to AWS as that one is a next big demand in the IT industry.
2016 2017 about love advise blog business career Christmas 2016 chuck norris cloudflare consultant couple customer satisfaction ddclient disney dns domain dynamic dns email Feel Fullness Life food Grabcar guide Guide to Indonesia hard work how-to important Indonesia internet journey learn lesson life life purpose linux openshift relationship Singapore technology tips travel trick trip tutorial work