Google Africa Developer Scholarship Phase II - list of completed sample qwiklabs for Google Cloud Practice Project.
Screenshot are organized based on the Course Title, each link takes to the screenshot of the qwicklab completed.
-
Google Cloud Platform Fundamentals - Core Infrastructure
- Google Cloud Fundamentals: Getting Started with Cloud Marketplace
- Google Cloud Fundamentals: Getting Started with Compute Engine
- Google Cloud Fundamentals: Getting Started with Cloud Storage and Cloud SQL
- Google Cloud Fundamentals: Getting Started with GKE
- Getting Started with App Engine
- Google Cloud Fundamentals: Getting Started with Deployment Manager and Cloud Monitoring
- Google Cloud Fundamentals: Getting Started with BigQuery
-
Essential Google Cloud Infrastructure: Foundation
-
Essential Google Cloud Infrastructure: Core Services
-
Elastic Google Cloud Infrastructure: Scaling and Automation
-
Getting Started With Application Development on Google Cloud
-
Google Cloud Platform Big Data and Machine Learning Fundamentals
- Explore a BigQuery Public Dataset
- Recommend Products using ML with Cloud SQL and Dataproc
- Predict Visitor Purchases with a Classification Model with BigQuery ML
- Create a Streaming Data Pipeline for a Real-Time Dashboard with Cloud Dataflow
- Classify Images with Pre-built ML Models using Cloud Vision API and AutoML
Bellow are sample of selected laboratories translated from web Console click, drag and drop instructions to 100% command line instructions.
Instructions are based on first the laboratory name then step by step commands to be excuted in the Cloud Shell.
First, set default zone to the one set by qwicklab assigned zone which is us-central1-a in my case.
gcloud config set compute/zone us-central1-a
Create a virtual machine named my-vm-1 on GCP Console (translated to command)
gcloud beta compute instances create my-vm-1 \
--zone=us-central1-a --machine-type=n1-standard-1 \
--subnet=default --network-tier=PREMIUM --maintenance-policy=MIGRATE \
--tags=http-server --image=debian-10-buster-v20200902 --image-project=debian-cloud \
--boot-disk-size=10GB --boot-disk-type=pd-standard --boot-disk-device-name=instance-1 \
--no-shielded-secure-boot --no-shielded-vtpm --no-shielded-integrity-monitoring --reservation-affinity=any
Create another virtual machine to test connection connection between two virtual machines in the same network.
gcloud compute instances create "my-vm-2" \
--machine-type "n1-standard-1" \
--image-project "debian-cloud" \
--image "debian-9-stretch-v20190213" \
--subnet "default"
Connect to my-vm-2 using SSH from the cloud shell.
gcloud beta compute ssh --zone "us-central1-a" "my-vm-1"
check if connection to my-vm-1 works or not using ping command.
ping -c 4 my-vm-2
Install the Nginx web server on my-vm-1.
sudo apt-get update -y && \
sudo apt-get install nginx-light -y
Use the Linux sed command to display a custom message to the home page of the web server, from Welcome to nginx! to Hi from my full name.
sed -i 's/Welcome to nginx!/Hi from Tsegaye Mekonnen/g' /var/www/html/index.nginx-debian.html
Confirm if the web server is serving your new page updated page. At the command prompt on my-vm-1, execute this command:
curl http://my-vm-1/
Login to the second virtual machine and confirm if the page from my-vm-1 is accessible.
gcloud compute ssh my-vm-2 --zone us-central1-a --internal-ip
curl http://my-vm-1/
End of laboratory for Google Cloud Fundamentals: Getting Started with Compute Engine.
In this lab, a Cloud Storage bucket is created to place an image in it. Compute Engine is configured to use a database managed by Cloud SQL. An application running in this lab, is configured as a web server with PHP, a web development environment that is the basis for popular blogging software.
First deploy a web server VM instance
gcloud beta compute instances create bloghost \
--zone=us-central1-a --machine-type=n1-standard-1 --subnet=default \
--metadata=startup-script=apt-get\ update$'\n'apt-get\ install\ apache2\ php\ php-mysql\ -y$'\n'service\ apache2\ restart \
--tags=http-server --image=debian-9-stretch-v20200902 \
--image-project=debian-cloud --boot-disk-size=10GB \
--boot-disk-type=pd-standard --boot-disk-device-name=bloghost
For convenience, enter your chosen location into an environment variable called LOCATION
export LOCATION=US
In Cloud Shell, the DEVSHELL_PROJECT_ID environment variable contains the current project ID. Enter this command to make a bucket named as the project ID:
gsutil mb -l $LOCATION gs://$DEVSHELL_PROJECT_ID
Retrieve a banner image from a publicly accessible Cloud Storage location to be used in a sample PHP web application for later.
gsutil cp gs://cloud-training/gcpfci/my-excellent-blog.png my-excellent-blog.png
Copy the file from cloud shell to the storage bucket permanenetly named after the project ID.
gsutil cp my-excellent-blog.png gs://$DEVSHELL_PROJECT_ID/my-excellent-blog.png
Modify the Access Control List of the sample image object so that it is readable by everyone, will have accsessible publick url as https://storage.googleapis.com/$DEVSHELL_PROJECT_ID/my-excellent-blog.png.
gsutil acl ch -u allUsers:R gs://$DEVSHELL_PROJECT_ID/my-excellent-blog.png
Create the Cloud SQL instance console translation to command:
gcloud sql instances create blog-db \
--tier=db-n1-standard-2 --zone=us-central1-a \
--database-version=MYSQL_5_7
Set a Root user password sample as pass1234.
gcloud sql users set-password root --host=% --instance blog-db \
--password pass1234
when the command finshes running we can try if our cloud SQL instance is working using the user root and the password just given in the upper command.
gcloud sql connect blog-db2 --user=root --quiet
type the password and play with the mysql dattabase by trying some commands
show databases;
create database sampleDB;
use sample DB;
exit;
ADD another USER ACCOUNT to the cloud SQL instance
gcloud sql users create blogdbuser \
--host=% --instance=blog-db \
--password=pass1234
Add the Public IP address of the above VM instance created in the first step so that our VM instance could access the cloud SQL istance and store some data.
gcloud sql instances patch blog-db \
--authorized-networks=35.224.39.178/32
Configure a PHP application in a Compute Engine instance to use Cloud SQL:
Firstly, ssh into the bloghost VM instance
gcloud beta compute ssh --zone "us-central1-a" "bloghost"
Create index.php file inside document root of the web serve since apache2 webserver is installed in the startup script of the program in the first step.
sudo touch /var/www/html/index.php
Make index.php file accesible by granting full permission so that we could modify it's contenet.
sudo chmod 777 /var/www/html/index.php
write muptiple lines of PHP code to test if the Cloud SQL instance connects to our bloghost VM instance. IP address should match to the Public IP of the bloghost VM instance.
sudo cat << EOF >> /var/www/html/index.php
<html>
<head><title>Welcome to my excellent blog</title></head>
<body>
<h1>Welcome to my excellent blog</h1>
<?php
\$dbserver = "35.192.162.183";
\$dbuser = "blogdbuser";
\$dbpassword = "pass1234";
// In a production blog, we would not store the MySQL
// password in the document root. Instead, we would store it in a
// configuration file elsewhere on the web server VM instance.
\$conn = new mysqli(\$dbserver, \$dbuser, \$dbpassword);
if (mysqli_connect_error()) {
echo ("Database connection failed: " . mysqli_connect_error());
} else {
echo ("Database connection succeeded.");
}
?>
</body></html>
EOF
Restart the web server, so that it could reflect the changes made to the file.
sudo service apache2 restart
check if the database connection works by using the command line terminal based browser program.
curel http://bloghost/index.php
Our Database connection succeeded. It's time now to try if our application could access data from the cloud storage.
Add the following line to add reference to file in the fifith line after the website header <h1>Welcome to my excellent blog</h1>.
sed -i '5i\<img src="https://storage.googleapis.com/qwiklabs-gcp-03-2d1188a512a4/my-excellent-blog.png" />' /var/www/html/index.php
use a terminal based web browser to check if we have both the Database connection succeeded and our image url.
curel http://bloghost/index.php
or use your web browser to check the sample PHP application intagrated with Database and Object storage as.
http://35.192.162.183/index.php
End of laboratory for Google Cloud Fundamentals: Getting Started with Cloud Storage and Cloud SQL.
Google Cloud Virtual Private Cloud (VPC) provides networking functionality to Compute Engine virtual machine (VM) instances, Kubernetes Engine containers, and the App Engine flexible environment.
There are 4 Ingress firewall rules for the default network, we can explore this laboratory by deleting each of them one by one or together by passing each name to one delete command.
- default-allow-icmp
- default-allow-rdp
- default-allow-ssh
- default-allow-internal
gcloud compute firewall-rules delete default-allow-icmp
gcloud compute firewall-rules delete \
default-allow-internal \
default-allow-rdp \
default-allow-ssh
Delete the default network
There is a single automode default network for each project, in this laboratory we delete it, and we create our own network.
gcloud compute networks delete default
Try to create a VM instance
Since there is no more network any atempt to create any VM instance will fail.
gcloud compute instances create instance-1 \
--zone=us-central1-a --machine-type=n1-standard-1 \
--image=debian-9-stretch-v20200902 \
--image-project=debian-cloud --boot-disk-size=10GB \
--boot-disk-type=pd-standard --boot-disk-device-name=bloghost
The above command should fail becuse there is no network to assosiate instance-1 with, we cannot create a VM instance without a VPC network.
gcloud compute networks create mynetwork \
--subnet-mode=auto --bgp-routing-mode=regional
The above created network mynetwork have standard firewall rules that deny-all-ingress and allow-all-egress rules because they are implied. We can further create firewall rules to allow ICMP, internal, RDP, and SSH rules to the network mynetwork.
gcloud compute firewall-rules create mynetwork-allow-icmp \
--network=mynetwork --direction=INGRESS --source-ranges=0.0.0.0/0 --action=ALLOW --rules=icmp
gcloud compute firewall-rules create mynetwork-allow-rdp \
--network=mynetwork --direction=INGRESS --source-ranges=0.0.0.0/0 --action=ALLOW --rules=tcp:3389
gcloud compute firewall-rules create mynetwork-allow-ssh \
--network=mynetwork --direction=INGRESS --source-ranges=0.0.0.0/0 --action=ALLOW --rules=tcp:22
Since we have an automode VPC network and firewalls, we can create VM instances from here.
gcloud beta compute instances create mynet-us-vm \
--zone=us-central1-c --machine-type=n1-standard-1 \
--network=mynetwork
we could create another VM in another Region in europe-west1.
gcloud beta compute instances create mynet-eu-vm \
--zone=europe-west1-c --machine-type=n1-standard-1 \
--subnet=mynetwork \
To prevent new subnets automatically created as new regions become available, we can convert our automode network it to a custom mode network.
gcloud compute networks update mynetwork \
--switch-to-custom-subnet-mode
Create a custom mode network called managementnet with a subnet managementsubnet-us`` for us-central1`` region in the IP range of 10.130.0.0/20.
gcloud compute networks create managementnet --subnet-mode=custom --bgp-routing-mode=regional
gcloud compute networks subnets create managementsubnet-us --range=10.130.0.0/20 --network=managementnet --region=us-central1
Create another custom mode network named privatenet with two subnets privatesubnet-us and privatesubnet-eu
gcloud compute networks create privatenet --subnet-mode=custom
gcloud compute networks subnets create privatesubnet-us \
--network=privatenet --region=us-central1 --range=172.16.0.0/24
gcloud compute networks subnets create privatesubnet-eu \
--network=privatenet --region=europe-west1 --range=172.20.0.0/20
To list the available VPC networks(3 CUSTOM mode networks), run the following command
gcloud compute networks list
To list the available VPC subnets (sorted by VPC network):
gcloud compute networks subnets list --sort-by=NETWORK
A firewall rule to allow SSH, ICMP, and RDP ingress traffic to VM instances on the managementnet network can be created as follows.
gcloud compute firewall-rules create managementnet-allow-icmp-ssh-rdp \
--direction=INGRESS --network=managementnet \
--action=ALLOW --rules=tcp:22,tcp:3389,icmp \
--source-ranges=0.0.0.0/0
Create the firewall rules for privatenet
gcloud compute firewall-rules create privatenet-allow-icmp-ssh-rdp \
--direction=INGRESS --network=privatenet \
--action=ALLOW --rules=icmp,tcp:22,tcp:3389 \
--source-ranges=0.0.0.0/0
To list all the firewall rules (sorted by VPC network) created in the current Project can be viewed as:
gcloud compute firewall-rules list --sort-by=NETWORK
We can create new Virtual Machines in the network of our preference.
gcloud beta compute instances create managementnet-us-vm \
--zone=us-central1-c --machine-type=f1-micro \
--subnet=managementsubnet-us
gcloud compute instances create privatenet-us-vm --zone=us-central1-c --machine-type=f1-micro --subnet=privatesubnet-us
gcloud compute instances list --sort-by=ZONE
By SSH to the mynet-us-vm instance, we can check connecting to all the vM instance in diffrent subnets and regions using Public and private IP adress.
gcloud beta compute ssh --zone "us-central1-c" "mynet-us-vm"
Using Public IP addres of the VM instances
- mynet-eu-vm
- managementnet-us-vm
- privatenet-us-vm
works all fine cause ping the external IP address of all VM instances, even though they are in either a different zone or VPC network.
ping -c 3 35.187.95.35
ping -c 3 34.123.69.192
ping -c 3 34.122.154.13
You can ping the internal IP address of mynet-eu-vm because it is on the same VPC network as the source of the ping (```mynet-us-vm``), even though both VM instances are in separate zones, regions, and continents!
ping -c 3 10.132.0.2
But tring to ping internal IP address of managementnet-us-vm and privatenet-us-vm returns a 100% packet loss, because they are in separate VPC networks from the source of the ping (mynet-us-vm), even though they are all in the same zone, us-central1-c.
ping -c 3 172.16.0.2
ping -c 3 10.130.0.3
End of laboratory VPC Networking.