After setting my personal site, bengo.is, up in a fit of indieweb-inspiration in May, it quickly fell into disarray. I was hosting on Google Cloud , but after awhile my debit card expired, I accrued a balance due, and they shut down my project until I paid up. Fair enough.
I had set it all up in a really complicated way as an excuse to play with kubernetes, so it unnecessarily used three VMs that were costing $30/month anyway, which I didn’t want to pay for. So I let it go…
With a personal domain refusing all connections, I attended the Homebrew Website Club on November 18 and quietly felt like a total loser. I had to return to my former glor — well, existence — glory can come later.
I set aside some time the following weekend to get the web server back up. It ought to be easily rebuildable, because containerization. How hard could it be? It turns out if you don’t pay Google, they get frustrated and suspicious. My account had been flagged for fraud. No matter what I clicked in the gcloud console, I saw this roadblock:
I accessed the Account Verification form. It required uploading the following verification documents:
One non-expired, government-issued identification
One document with your billing address dated within the last four months that shows the same address on file in your Billing account (if you can’t remember the billing address in your account, or you have multiple, use your most recent home address).
I looked around for a way to just go ahead and change my billing info and pay any balance due. As far as I can tell there is no way to get to the billing section of the console with your account in this state, which is dumb.
My father’s first rule of business is “Don’t make it hard for me to pay you”, and Google Cloud violates it.
So I scrounged around and compiled the documents to prove my billing address (it doesn’t help that I have moved since May), found an image editing program, edited out account numbers, submitted the form, and waited… and waited… I received no email confirmation.
How long will it take to verify my information? The process should take 24 hours. In rare cases, it may take 3–5 business days. You’ll receive an email as soon as your information is verified.
That was a week ago. Three days ago I sent something through the gcloud console’s built-in feedback form about how I was confused and just want to gcloud. Nothing.
Fully blocked, I gave up on that suspended gcloud project. What was a nerd to do? I considered, briefly, starting another gcloud project from scratch, as well as falling back to AWS like I use at work. There are tons of other VPS providers that would work just fine, but don’t have all the cloudy features I’d like to learn anyway for more web-scale projects. I decided to give up, eat some apple pie, and continue trying later.
The next day I was watching videos from the OpenStack Summit in Tokyo about a month ago. I stumbled upon “Pure Simplicity of Containers on OpenStack” by Adrian Otto, Product Architect at Rackspace. It turned out to be the launch announcement of Carina , “An easy-to-use, instant-on, native container environment” (by Rackspace).
The best part was that it featured his ten year-old son using docker to deploy a container to the cloud. The second best part was that it looked nice and easy. The third best part is that it’s currently free. I signed up for the beta and got an email invite right away.
I logged in and saw a simple dashboard with a single affordance, “Add cluster”. I clicked and used the two-input form to name it “bengo-web” and enabled autoscale (sounds useful).
Then I did the following:
- Click “Get Access” and download a .zip of stuff for my cluster
- Unzipped to ~/carina/bengo-web
- Opened terminal:
⚡ cd ~/dev/bengo-web # My site source code
⚡ . ~/carina/bengo-web/docker.env # Set Docker env vars to my carina cluster
⚡ docker build -t bengo-web . # Build my site to container image
⚡ docker run --detach --name bengo-web --publish 80 bengo-web
⚡ open "http://$(docker port bengo-web 80)"
And I was staring at my site on the public internet. Woah.
It seemed too good to be true. All I needed was my domain pointing there. I asked the (nascent) Carina community. But then I just remembered how to DNS. I changed my A record to point to the IP from docker port bengo-web 80 instead of my gcloud Zone.
Now bengo.is back. And I am happy.
Carina is awesome so far for this sort of personal (or prototyping) use case where you just need to run a process published on a port somewhere in the cloud. It’s free for now, which is right in my budget. I’m really looking forward to seeing how they grow this product. The last time I was this impressed, it was with Heroku’s git push simplicity. And this is even faster.
The future of application development in the cloud is going to be fun. And fast.
In my further research, I learned that Carina is likely ‘just’ an opaque productization of OpenStack Magnum.
Magnum is an OpenStack API service developed by the OpenStack Containers Team making container orchestration engines such as Docker and Kubernetes available as first class resources in OpenStack. Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs that image in either virtual machines or bare metal in a cluster configuration.
The project launchpad shows that Adrian Otto is not just a sales dude that delegates the hard pitch work to his son. He’s also the project’s top contributor (by almost a factor of 2!), and has been actively helping diagnose and delegate bugs in the last week. Kudos to him and Rackspace for contributing this under an Apache license for the rest of us to use and learn from.
Originally published at bengo.is on November 29, 2015.