App in a Box is a series of applications that are prebuilt and architected to demonstrate common application architectures and share projects that can repurposed to support your needs. Each one just requires one command to run and when the process is done, a fully function version of the app is available and running, ready to use or modify.
BasicLB is a simple infrastructure building script that sets up a cluster of VMs and puts a Load Balancer in front of them to expose publically:
Example sets up a simple static HTML site using NGINX, and load balances across your cluster.
Click on the link below to a copy of the source code in Cloud Shell. Once there, a single command will spin up a workng copy of the application in your project.
Also feel free to review the source code directly in github.
View source code
Use the links below to get more information on the piece we used in this Application. Choose how you learn best: video, product documentation, or interactive walkthrough.
Compute Engine is Google Cloud's Virtual technology. With it you can spin up many different configurations of VM to fit the shape of whatever computing needs you have.
Google Cloud Load Balancer allows you to place a load balancer in front of the Storage Bucket - allowing you to use SSL certificates, Logging and Monitoring.
The install script uses the gcloud and gsutil CLI tools to take an empty project and
install the application in it. The output should be a working application and a url to the
Cloud Run service for the front end.
./installGoogle Cloud Services are disabled in a project by default. In order to use any of the solutions here we have to activate the following:
gcloud services enable compute.googleapis.com
Creates a VM, installs some software on it, and deploys some code to it.
gcloud compute instances create $BASENAME-exemplar \
--zone $ZONE --machine-type "n1-standard-1" \
--image-project "debian-cloud" --image-family "debian-10" --boot-disk-size "200" \
--no-boot-disk-auto-delete --boot-disk-type "pd-standard" \
--boot-disk-device-name "$BASENAME-exemplar" --tags "http-server"
# Shhhhh VM's are cranky when then wake - this always errors the first time
# an ssh command is sent, so WE GONNA DO IT AGAIN
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo apt-get update -y"
printf "${BCYAN}Don't worry about this error. It seems like it's necessary${NC} \n"
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo apt-get update -y"
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo apt-get install nginx -y"
gcloud compute scp code/index.html $BASENAME-exemplar:~/ --zone=$ZONE
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo mv index.html /var/www/html/index.html"
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo chgrp root /var/www/html/index.html"
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo chown root /var/www/html/index.html"
gcloud compute ssh $BASENAME-exemplar --zone $ZONE --command="sudo chmod +r /var/www/html/index.html"IN,AVAILABILITY,YEARLY_PRICE
Deletes the VM we just created but doesn't delete the disk, which we use to create a Disk Image. This image will be used to make all of the VMs in the cluster.
gcloud compute instances delete $BASENAME-exemplar --zone $ZONE -q
gcloud compute images create $BASENAME-latest --family=$BASENAME \
--source-disk=$BASENAME-exemplar --source-disk-zone=$ZONE
Creates a Template of settings and configuration which will be the configuration for all of the VMs in the cluster. It uses the Disk Image we just created. Also note we add a startup script That script will customize the HTML that is served up by ever member of the cluster.
gcloud compute instance-templates create $BASENAME-template \
--create-disk=image=$BASENAME-latest,image-project=$PROJECT,size=200GB \
--tags "http-server" --metadata-from-file=startup-script=startup.sh
Actually requests N number of machines of the Instance Template to be mangaged as part of this group.
gcloud compute instance-groups managed create $BASENAME-mig \
--size $SIZE --template $BASENAME-template --zone $ZONE
gcloud compute instance-groups set-named-ports $BASENAME-mig \
--named-ports http:80 \
--zone $ZONE
Needed to bind a host to the domain name, and communicate in general on the Internet.
gcloud compute addresses create $BASENAME-ip \
--network-tier=PREMIUM --ip-version=IPV4 --global
This creates the load balancer and wires up helthcheks and backend services. These are configuration and settings that connect the Load Balancer to the Managed Instance Group.
gcloud compute health-checks create tcp $BASENAME-health-chk \
--port 80
gcloud compute firewall-rules create allow-health-check \
--allow tcp:80 \
--source-ranges 130.211.0.0/22,35.191.0.0/16 \
--network default
gcloud compute backend-services create $BASENAME-service \
--load-balancing-scheme=EXTERNAL \
--protocol=HTTP \
--port-name=http \
--health-checks=$BASENAME-health-chk \
--global
gcloud compute backend-services add-backend $BASENAME-service \
--instance-group=$BASENAME-mig \
--instance-group-zone=$ZONE --global
gcloud compute url-maps create $BASENAME-lb \
--default-service=$BASENAME-service
Creates the neccessary networking rules to point port 80 on the load balancer to the service we are running.
gcloud compute target-http-proxies create $BASENAME-lb-proxy \
--url-map=$BASENAME-lb
gcloud compute forwarding-rules create $BASENAME-http-lb-forwarding-rule \
--address=$BASENAME-ip --global --target-http-proxy=$BASENAME-lb-proxy \
--ports=80