Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.
Awesome Lists | Featured Topics | Projects
https://github.com/Cyclenerd/google-cloud-server-on-demand

▶️ Server on Demand Appliance (Google Compute Engine) - Cloud Build with Terraform and Ansible Showcase
https://github.com/Cyclenerd/google-cloud-server-on-demand
ansible automation google-cloud-build google-cloud-platform google-compute-engine internet-of-things iot linux python raspberry-pi terraform
Last synced: about 2 months ago
JSON representation
▶️ Server on Demand Appliance (Google Compute Engine) - Cloud Build with Terraform and Ansible Showcase
Host: GitHub
URL: https://github.com/Cyclenerd/google-cloud-server-on-demand
Owner: Cyclenerd
License: apache-2.0
Created: 2022-12-05T18:38:46.000Z (almost 2 years ago)
Default Branch: master
Last Pushed: 2024-05-21T08:18:55.000Z (4 months ago)
Last Synced: 2024-06-08T22:35:52.913Z (3 months ago)
Topics: ansible, automation, google-cloud-build, google-cloud-platform, google-compute-engine, internet-of-things, iot, linux, python, raspberry-pi, terraform
Language: HCL
Homepage:
Size: 4.01 MB
Stars: 11
Watchers: 2
Forks: 0
Open Issues: 0
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project

README

        # Server on Demand Appliance (Google Compute Engine)

**Get your own Google Compute Engine virtual machine (VM) with the simple push of a button.**

![Image: Server on Demand Appliance at DIGITAL X 2023](./img/soda-gce-digitalx-2023.jpg)

This project is intended to show how quickly and easily virtual machines can be configured and set up using Google Cloud and Infrastructure as Code (IaC) tools.

You have the choice between four Linux based operating systems.

You trigger a continuous integration / continuous deployment (CI/CD) pipeline by pressing a button.

A virtual machine is then provisioned and installed for you in the Google Cloud.

In the background, [Google Cloud Build](https://cloud.google.com/build) uses [Terraform](https://www.terraform.io/) and [Ansible](https://www.ansible.com/) to build your own VM.

You will get your own user login data printed on a receipt and you can log in via SSH after a few minutes.

![Image: Terraform and Ansible](./img/terraform_ansible_logo.jpg)

This project also shows you how well the Google Cloud can scale.

Tested with over 150 VMs. [700 VMs](./QUOTA.md) is the default limit.

## 🤔 Why

I saw the Shells on Demand Appliance "SODA" from National Upcycled Computing Collective (NUCC) at the DEF CON 30 conference in Las Vegas. Unfortunately not in person but in this [YouTube video](https://www.youtube.com/watch?v=e69zcwISo3Y).

TL;DR: It's a vending machine. You pay, press a button and get your own virtual machine (VM).

![Image: Shells on Demand Appliance at DEF CON 30](./img/soda-las_vegas.jpg)

*Image Source: [@strangepartscom](https://twitter.com/strangepartscom/status/1558566808205987840/), [@Zhoratrope](https://twitter.com/Zhoratrope/status/1558160122957799424)*

I was quite impressed and excited by the idea. I wanted something like this too. Unfortunately, I don't have enough space and I don't even have a real vending machine either.

Thanks to Google and the Internet, the hardware does not have to be physically located in a vending machine. The hardware can be located in one of the many [Google Cloud data centers](https://gcloud-compute.com/regions.html). This saves a lot of space and you only need the buttons and a thermal receipt printer to have a similar setup to the SODA vending machine. That's exactly what I did with this project.

## 🚀 Technology

![Badge: Google Cloud](https://img.shields.io/badge/Google%20Cloud-%234285F4.svg?logo=google-cloud&logoColor=white)

![Badge: Terraform](https://img.shields.io/badge/Terraform-%235835CC.svg?logo=terraform&logoColor=white)

![Badge: Packer](https://img.shields.io/badge/Packer-02A8EF.svg?logo=packer&logoColor=white)

![Badge: Ansible](https://img.shields.io/badge/Ansible-%231A1918.svg?logo=ansible&logoColor=white)

![Badge: Raspberry Pi](https://img.shields.io/badge/Raspberry%20Pi-C51A4A?logo=Raspberry-Pi)

The following technologies are used:

Google Cloud Platform

- [x] [Compute Engine](https://cloud.google.com/compute)

- [x] [Operating system images](https://cloud.google.com/compute/docs/images/os-details)

	- [x] [Debian GNU/Linux](https://en.wikipedia.org/wiki/Debian)

	- [x] [Ubuntu LTS](https://en.wikipedia.org/wiki/Ubuntu)

	- [x] [Fedora Linux](https://en.wikipedia.org/wiki/Fedora_Linux)

	- [x] [openSUSE](https://en.wikipedia.org/wiki/OpenSUSE)

- [x] [Cloud Storage](https://cloud.google.com/storage)

- [x] [Cloud Source Repositories](https://cloud.google.com/source-repositories)

- [x] [Cloud Pub/Sub](https://cloud.google.com/pubsub)

- [x] [Cloud Build](https://cloud.google.com/build)

	- [x] [Docker Container image](https://github.com/Cyclenerd/cloud-tools-container#readme)

- [x] [Cloud Function](https://cloud.google.com/functions)

- [x] [Artifact Registry](https://cloud.google.com/artifact-registry)

- [x] [Cloud DNS](https://cloud.google.com/dns)

- [x] [Cloud Firewall](https://cloud.google.com/firewalls)

- [x] [Cloud Logging and Monitoring](https://cloud.google.com/monitoring)

- [x] [Cloud Scheduler](https://cloud.google.com/scheduler)

- [x] [Identity and Access Management (IAM)](https://cloud.google.com/iam)

- [x] [Resource Manager](https://cloud.google.com/resource-manager)

Terraform

- [x] [Google provider](https://registry.terraform.io/providers/hashicorp/google/)

- [x] [Archive provider](https://registry.terraform.io/providers/hashicorp/archive/)

- [x] [Local provider](https://registry.terraform.io/providers/hashicorp/local/)

Packer

- [x] [Google Cloud Platform](https://developer.hashicorp.com/packer/integrations/hashicorp/googlecompute)

- [x] [Ansible](https://developer.hashicorp.com/packer/integrations/hashicorp/ansible)

Ansible

- [x] apt

- [x] command

- [x] copy

- [x] dnf

- [x] file

- [x] get_url

- [x] git

- [x] uri

- [x] user

- [x] zypper

Raspberry Pi

- [x] [Raspberry Pi OS](https://www.raspberrypi.com/software/operating-systems/)

- [x] [Python 3](https://www.python.org/)

All components put together correctly result in the Server on Demand Appliance Google Cloud version.

## 🪄 Process of creating a VM

![Badge: Fedora](https://img.shields.io/badge/Fedora-51A2DA.svg?logo=fedora&logoColor=white)

![Badge: Ubuntu](https://img.shields.io/badge/Ubuntu-E95420.svg?logo=ubuntu&logoColor=white)

![Badge: Debian](https://img.shields.io/badge/Debian-A81D33.svg?logo=debian&logoColor=white)

![Badge: openSUSE](https://img.shields.io/badge/openSUSE-73BA25.svg?logo=opensuse&logoColor=white)

https://user-images.githubusercontent.com/176242/205736692-b19bca68-a94c-4e95-8c32-79a9f7dfc7a9.mp4

[📺 YouTube Video](https://www.youtube.com/watch?v=9a_9sfi7aaU)

In order to create a VM, many steps are carried out.

Everything goes very fast.

While the user is already holding his paper with login information,

further steps are executed in the cloud.

[![Drawing: SODA Google Compute Engine version](./img/soda-gcp.png)](./img/soda-gcp.png)

**Raspberry Pi:**

1. User presses one of the four buttons

	* 🔵 Blue : Fedora Linux

	* 🟡 Yellow : Ubuntu LTS

	* 🔴 Red : Debian GNU/Linux

	* 🟢 Green : openSUSE

2. Message is published to Cloud Pub/Sub topic

3. Paper receipt with login information is printed

**Google Cloud Platform:**

3. Pub/Sub triggers Cloud Build

4. A Cloud Build job is started

	1. Cloud Build downloads [Docker container image](https://github.com/Cyclenerd/cloud-tools-container) with tools (Google Cloud CLI, Terraform, Ansible)

	1. Required scripts are loaded from the Cloud Source Repository

	1. Pub/Sub message is read and evaluated

5. Terraform creates the infrastructure

	* Static public IP is registered

	* DNS entry is created

	* VM with disk and operating system is created

	* Custom OS image is used

	* Cloud Scheduler to destroy infrastructure is scheduled

	* Terraform state is stored in a Google Cloud Storage bucket

6. Ansible takes care of configuring the operating system

	* Set up user (username and password)

### Machine configuration

The following configuration is used by default:

* Machine type: [`e2-micro`](https://gcloud-compute.com/e2-micro.html)

	* vCPU: 2 shared Intel (x86/64)

	* Memory: 1 GB

* Disk:

	* Type: [Balanced persistent disk](https://cloud.google.com/compute/docs/disks#disk-types) (SSD)

	* Size: 25 GB

* External IP address: Premium

* Region: [`europe-west1`](https://gcloud-compute.com/europe-west1/e2-micro.html) (Belgium) 

**Costs:**

Estimated cost per `e2-micro` VM, without guarantee:

|                  | $ 1h     | $ 3h   |

|------------------|----------|--------|

| CPU and memory   | `0.0092` | `0.03` |

| Disk (25GB)¹     | `0.0034` | `0.01` |

| Static public IP | `0.0034` | `0.01` |

| **Total**        | `0.0160` | `0.05` |

¹ Balanced persistent disk: 0.1 USD per 1 GB and month,

25 GB per month = 2.50 USD,

one month = 730 hours,

2.50 USD / 730h = 0.0034 USD,

0.0034 USD * 3h = 0.010 USD for 25 GB for 3h

There are other small costs for:

* Cloud Build build time

* Source Repository users

* Cloud Scheduler jobs

* Cloud DNS managed zone

* Network Internet egress traffic

Source: [Google Cloud Pricing Calculator](https://cloud.google.com/products/calculator/#id=7b564b38-e2c4-43bc-8e50-9a21b71d0c48)

## 🚀 Setup

### 1. Clone

Clone this repository:

```bash

git clone https://github.com/Cyclenerd/google-cloud-shells-on-demand.git

cd google-cloud-shells-on-demand

```

### 2. Google Cloud Platform

Please follow the instructions in the folder [gcp](./gcp/README.md).

```bash

cd gcp

```

### 3. Raspberry Pi

Please follow the instructions in the folder [pi](./pi/README.md).

```bash

cd pi

```

## 🔦 Further functions

In addition to creating the infrastructure, there are a few other functions.

### Automatic expiration

After a defined time (default 3 hours), your VM and its entire infrastructure will be deleted.

![Image: Cloud Scheduler](./img/destroy.png)

This is triggered by a Cloud Scheduler set up during the creation of the VM.

A Cloud Build job then takes care of the destruction of the VM and its infrastructure.

This works because an extra separate Terraform state is saved for each VM.

You can adjust the expiration time (minutes) in `terraform.tfvars` in the `gcp` directory.

```text

# Expires in minutes

expires = "180"

```

### Back on

After logging in to your VM via SSH, you can become root.

Then you can do anything, even shut down the VM:

```bash

sudo poweroff

```

![Image: Cloud Build](./img/on-again.png)

If you do this, a event will be saved in the Google Cloud audit log and a new Cloud Build job will be triggered.

This Cloud Build job then starts your VM again. Feel free to test it 😊.

### Cloud Build notifications

Get notified via [Discord](https://discord.com/) and/or [Pushover](https://pushover.net/) when a Cloud Build job is failed (`ERROR`) or timed out (`TIMEOUT`).

#### Discord

Get notified via [Discord](https://discord.com/):

![Image: Discord](./img/cloudbuild-discord.png)

1. Create an Discord webhook URL for your Discord channel: 

	

	The webhook URL should look similar to the following:

	```text

	https://discord.com/api/webhooks/[WEBHOOK-ID]/[WEBHOOK-TOKEN]

	```

1. Add the Discord webhook URL to `terraform.tfvars` in `gcp` directory:

	

	```text

	discord-webhook-url = "https://discord.com/api/webhooks/[WEBHOOK-ID]/[WEBHOOK-TOKEN]"

	```

1. Deploy Cloud Function

	

	```bash

	terraform apply

	```

You can test the notification with the manual Cloud Build trigger `simulate-error`.

#### Pushover

Get notified via [Pushover](https://pushover.net/):

![Image: Pushover](./img/cloudbuild-pushover.png)

1. Register your application, set its name and upload an icon, and get an API token in return: 

	Example icon:

	![Image: Pushover icon](./img/button-icon-72x72.png)

	*MazeNL77, [CC BY 3.0](https://creativecommons.org/licenses/by/3.0), via [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Perspective-Button-Stop-icon.png)*

1. Add your Pushover user/group key (not e-mail address) and the application's API token/key to `terraform.tfvars` in `gcp` directory:

	

	```text

	pushover-user-key = "[PUSHOVER-USER-KEY]"

	pushover-api-token = "[PUSHOVER-API-TOKEN]"

	```

1. Deploy Cloud Function

	

	```bash

	terraform apply

	```

You can test the notification with the manual Cloud Build trigger `simulate-error`.

### Raspberry Pi CPU temp. monitoring

The CPU of the Raspberry Pi can get hot in the wooden box.

For safety and documentation, the CPU temperature is logged and can be monitored.

![Image: CPU temp. monitoring](./img/temp-monitoring.png)

### Monitoring dashboards

Two custom monitoring dashboards are set up:

#### Raspberry Pi

![Image: Raspberry Pi monitoring dashbaord](./img/monitoring-dashboard-raspi.png)

#### VMs

![Image: VMs monitoring dashbaord](./img/monitoring-dashboard-vms.png)

### Artifact Registry repository

You can use the Artifact Registry as a location for the Docker container image.

The image then does not have to be downloaded from Docker Hub during the Cloud Build jobs.

![Image: Copy container](./img/copy-image.png)

1. Copy the image by running the manual trigger `copy-image`.

1. Replace `cyclenerd/cloud-tools-container:latest` with `[LOCATION]-docker.pkg.dev/[PROJECT_ID]/cointainer/cloud-tools-container:latest` in the Cloud Build YAML files (i.e. [`create.yml`](./cloudbuild/create.yml)) in folder the [cloudbuild](./cloudbuild/).

1. Push changes to Cloud Source repository:

	```bash

	git push cloudsource

	```

## ❤️ Contributing

Have a patch that will benefit this project?

Awesome! Follow these steps to have it accepted.

1. Please read [how to contribute](CONTRIBUTING.md).

1. Fork this Git repository and make your changes.

1. Create a Pull Request.

1. Incorporate review feedback to your changes.

1. Accepted!

## 📜 License

All files in this repository are under the [Apache License, Version 2.0](LICENSE) unless noted otherwise.

Please note:

* No warranty

* No official Google product