FROM gcr.io/google_appengine/python

RUN virtualenv /env

ENV VIRTUAL_ENV /env

ENV PATH /env/bin:$PATH

ADD requirements.txt /app/requirements.txt

RUN pip install -r /app/requirements.txt

ADD . /app

CMD honcho start -f /app/procfile $PROCESSES

.PHONY: all

all: deploy

.PHONY: create-cluster

create-cluster:

gcloud container clusters create bookshelf \

--scope "https://www.googleapis.com/auth/userinfo.email","cloud-platform"

.PHONY: create-bucket

create-bucket:

gsutil mb gs://$(GCLOUD_PROJECT)

gsutil defacl set public-read gs://$(GCLOUD_PROJECT)

.PHONY: build

build:

docker build -t gcr.io/$(GCLOUD_PROJECT)/bookshelf .

.PHONY: push

push: build

gcloud docker push gcr.io/$(GCLOUD_PROJECT)/bookshelf

.PHONY: template

template:

sed -i ".tmpl" "s/\$$GCLOUD_PROJECT/$(GCLOUD_PROJECT)/g" bookshelf-frontend.yaml

sed -i ".tmpl" "s/\$$GCLOUD_PROJECT/$(GCLOUD_PROJECT)/g" bookshelf-worker.yaml

.PHONY: deploy-frontend

deploy-frontend: push template

kubectl create -f bookshelf-frontend.yaml

.PHONY: deploy-worker

deploy-worker: push template

kubectl create -f bookshelf-worker.yaml

.PHONY: deploy

deploy: deploy-frontend deploy-worker

.PHONY: delete

delete:

kubectl delete rc bookshelf-frontend

kubectl delete rc bookshelf-worker

kubectl delete service bookshelf-frontend

This optional tutorial will walk you through how to deploy the Bookshelf sample application to [Google Container Engine](https://cloud.google.com/container-engine/). This tutorial is also applicable to [Kubernetes](http://kubernetes.io/) outside of Container Engine, but may require additional steps for external load balancing.

1. Create a project in the [Google Cloud Platform Console](https://console.cloud.google.com).

2. [Enable billing](https://console.cloud.google.com/project/_/settings) for your project.

3. [Enable APIs](https://console.cloud.google.com/flows/enableapi?apiid=datastore,pubsub,storage_api,logging,plus) for your project. The provided link will enable all necessary APIs, but if you wish to do so manually you will need Datastore, Pub/Sub, Storage, and Logging.

4. Install the [Google Cloud SDK](https://cloud.google.com/sdk)

$ curl https://sdk.cloud.google.com | bash

$ gcloud init

5. Install [Docker](https://www.docker.com/).

Create a cluster for the bookshelf application:

gcloud container clusters create bookshelf \

--scope "https://www.googleapis.com/auth/userinfo.email","cloud-platform" \

--num-nodes 2

gcloud container clusters get-credentials bookshelf

The scopes specified in the `--scope` argument allows nodes in the cluster to access Google Cloud Platform APIs, such as the Cloud Datastore API.

The bookshelf application uses [Google Cloud Storage](https://cloud.google.com/storage) to store image files. Create a bucket for your project:

gsutil mb gs://<your-project-id>

gsutil defacl set public-read gs://<your-project-id>

Modify config.py and enter your Cloud Project ID into the `PROJECT_ID` and `CLOUD_STORAGE_BUCKET` field. The remaining configuration values are only needed if you wish to use a different database or if you wish to enable log-in via oauth2, which requires a domain name.

Before the application can be deployed to Container Engine, you will need build and push the image to [Google Container Registry](https://cloud.google.com/container-registry/).

docker build -t gcr.io/your-project-id/bookshelf .

gcloud docker push gcr.io/your-project-id/bookshelf

The bookshelf app has two distinct "tiers". The frontend serves a web interface to create and manage books, while the worker handles fetching book information from the Google Books API.

`bookshelf-frontend.yaml` contains the Kubernetes resource definitions to deploy the frontend. **Update this file with your Project ID**, then use `kubectl` to create these resources on the cluster:

kubectl create -f bookshelf-frontend.yaml

Once the resources are created, there should be 3 `bookshelf-frontend` pods on the cluster. To see the pods and ensure that they are running:

kubectl get pods

If the pods are not ready or if you see restarts, you can get the logs for a particular pod to figure out the issue:

kubectl logs pod-id

Once the pods are ready, you can get the public IP address of the load balancer:

kubectl get services bookshelf-frontend

You can then browse to the public IP address in your browser to see the bookshelf application.

`bookshelf-worker.yaml` contains the Kubernetes resource definitions to deploy the worker. The worker doesn't need to serve web traffic or expose any ports, so it has significantly less configuration than the frontend. **Update `bookshelf-worker.yaml` file with your Project ID**, then use `kubectl` to create these resources on the cluster:

kubectl create -f bookshelf-worker.yaml

Once again, use `kubectl get pods` to check the status of the worker pods. Once the worker pods are up and running, you should be able to create books on the frontend and the workers will handle updating book information in the background.

apiVersion: v1

kind: ReplicationController

metadata:

name: bookshelf-frontend

spec:

replicas: 3

template:

metadata:

labels:

app: bookshelf

tier: frontend

spec:

containers:

- name: bookshelf-app

# Replace $GCLOUD_PROJECT with your project ID or use `make template`.

image: gcr.io/$GCLOUD_PROJECT/bookshelf

# This setting makes nodes pull the docker image every time before

# starting the pod. This is useful when debugging, but should be turned

# off in production.

imagePullPolicy: Always

# The PROCESSES environment variable is used by Honcho in the

# Dockerfile's CMD to control which processes are started. In this

# case, only the bookshelf process is needed.

env:

- name: PROCESSES

value: bookshelf

# The bookshelf process listens on port 8080 for web traffic by default.

ports:

- containerPort: 8080

---

apiVersion: v1

kind: Service

metadata:

name: bookshelf-frontend

labels:

app: bookshelf

tier: frontend

spec:

type: LoadBalancer

ports:

- port: 80

targetPort: 8080

selector:

app: bookshelf

tier: frontend

apiVersion: v1

kind: ReplicationController

metadata:

name: bookshelf-worker

spec:

replicas: 2

template:

metadata:

labels:

app: bookshelf

tier: worker

spec:

containers:

- name: bookshelf-app

# Replace $GCLOUD_PROJECT with your project ID or use `make template`.

image: gcr.io/$GCLOUD_PROJECT/bookshelf

# This setting makes nodes pull the docker image every time before

# starting the pod. This is useful when debugging, but should be turned

# off in production.

imagePullPolicy: Always

# The PROCESSES environment variable is used by Honcho in the

# Dockerfile's CMD to control which processes are started. In this

# case, only the worker process is needed.

env:

- name: PROCESSES

value: worker