Skip to main content

Introduction to AppScale and Google App Engine - Part 2

In my previous post I tried to install appscale on a virtualbox installation but it failed. In this post I am going to try the same installation on a Google Compute Engine instance following the appscale. Notice that I'm going to install on GCE and not GAE. The current theme is appscale and so I have not switched over to GAE yet.

Here are the instructions for installing appsacle on GCE.
  • install gcloud SDK
  • create an oath cred
  • add appscale image to your repo
    • gcloud command is buggy... you have to specify the project id
    • $ gcloud config set project VALUE
  • install appscale tools
  • config and start appscale
  • shutdown appscale
I was able to install appscale on GCE and I was able to open the dashboard just to see what was there.  appscale is very interested in selling you a license to use hawkeye and there was something in there for monit but I did not follow it.  There was even a limit to the type of machine that you could install onto; so there was no possibility to install on google's f1-micro; which is probably a good thing for production but for development... meh.

The sample code can be located here although I have not tried anything yet. I have not checked the restart times yet but that's in the plan. Once I deleted my instance using the GCE console tools there seemed to be a disconnect that could not be corrected from the command line. The appscale status command and appscale down could not agree on the state of the instance.

I did not actually install my sample application. I figure that would be for my next attempt in part 3 where I'm interested in trying the installation commands with a local VMware installation and then repeating with CoreOS.


I managed to get the system to start working again by deleting everything in my local $HOME/appscale folder.  Once that folder was cleaned up I was able to re-create the environment on the server. appscale up

Then, instead of deleting the instance from the GCE console I did it from the command line with an appscale down command on the terminal. This worked fine but when I tried to perform a subsequent appscale up command I received some general errors about keys already in use. So clearly I need to delete the folder between invocations.

** appscale clean does not work in the GCE mode.

One thing that is also missing... in a production environment when there are multiple applications in the domain then you need to be able to export the configuration so that the entire environment can be restored. appscale does not appear to be able to provide that info. GCE+CoreOS uses a version of the cloud-init file that allows you to restore your running environment.


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…