From 90f95e303a936ae7c2a1afd631b4af7c3c7a02ef Mon Sep 17 00:00:00 2001 From: Timothy Middelkoop Date: Tue, 15 Feb 2022 21:16:12 +0000 Subject: [PATCH] GCP: Cleanup console and compute. --- content/GCP/01_intro_to_cloud_console.ipynb | 18 ++++++++-------- content/GCP/02_intro_to_compute.ipynb | 24 ++++++++++----------- 2 files changed, 21 insertions(+), 21 deletions(-) diff --git a/content/GCP/01_intro_to_cloud_console.ipynb b/content/GCP/01_intro_to_cloud_console.ipynb index d7a5d60..7740272 100644 --- a/content/GCP/01_intro_to_cloud_console.ipynb +++ b/content/GCP/01_intro_to_cloud_console.ipynb @@ -32,7 +32,7 @@ "id": "10be57f6", "metadata": {}, "source": [ - "## The Who, What, and Where of the Cloud\n", + "## The Who, Where, and What of the Cloud\n", "\n", "Before we get started we must first define, and find, a few key pieces of information about your environment that will be used throughout this lesson. This information is also important to ensure that this information is what you expect, otherwise you may use the wrong account or run or store things in the wrong place. It is important to be clear about these terms as they are often different in other cloud providers. We provide a [glossary of GCP terms](glossary.ipynb) for your reference." ] @@ -82,10 +82,10 @@ "source": [ "## Projects\n", "\n", - "Almost everything you will do within Google Cloud Platform must be associated with a **Project**. This is the \"Where\" of the cloud. You must have at least one Project and you can manage multiple Projects within a single (Google) Account. Always make sure you are working in the correct project!\n", + "Almost everything you will do within Google Cloud Platform must be associated with a **Project**. This is the \"**Where**\" of the cloud. You must have at least one Project and you can manage multiple Projects within a single (Google) Account. Always make sure you are working in the correct project!\n", "\n", "To find more information and change project settings\n", - " * Click on the \"Settings and Utilities button (kabob on the top right - see below) and then click on \"Project Settings\"\n", + " * Click on the \"Settings and Utilities button (**kabob** on the top right - see below) and then click on \"Project Settings\"\n", " ![kabob-project](img/kabob-project.png)\n", " * The Project Name is the human friendly description and can be changed.\n", " * The Project ID is set on project creation and cannot be changed. The Project ID is almost always used when specifying a project.\n", @@ -93,7 +93,7 @@ " \n", "For a Project to do anything useful it must also have an enabled Billing Account associated with it. An enabled Billing Account is a prerequisite for this lesson.\n", "\n", - "A Project, just like the word, should be associated with a real world project (for example a research effort or grant, lab, or your Ph.D. Project. etc). For Drew, this is the image processing project. In this way it is easier to track and allocate costs and to manage permissions and access for resources within the project.\n", + "A Project, just like the word, should be associated with a real world project (for example a research effort or grant, lab, or your Ph.D. Project. etc). For Drew, this is the image processing project. In this way it is easier to track and allocate costs and to manage permissions and access for resources within the project. Work in a project should have similar **people**, **lifecycle**, and **funding**.\n", "\n", "The active project is also shown next to the project icon (three hexagons) and clicking it brings up the project selection dialog. The current project has a check mark and the active project can be changed by clicking on the project name or double clicking the row.\n", " ![select-project](img/select-project.png) " @@ -128,7 +128,7 @@ "\n", "The web console is used to control and observe the cloud from the browser. It should only be used for simple and one-time tasks, exploring new services, accessing documentation, or for monitoring and debugging resources in the cloud. Programmatic control through the console, programming languages (for example Python), and other automation tools should be used for day to day activities to make the most out of the cloud and to help with the reproducibility of research and teaching.\n", "\n", - "The Navigation Menu (often called the hamburger) is used to navigate to the various products, which are also sometimes called services.\n", + "The Navigation Menu (often called the **hamburger**) is used to navigate to the various products, which are also sometimes called services.\n", "\n", "![hamburger-navigation](img/hamburger-navigation.png)\n", "\n", @@ -136,7 +136,7 @@ " * You can pin frequently used items on the top of this page by clicking on the pin icon. \n", " * Click the hamburger again to hide the Left Sidebar.\n", "\n", - "All the different products and services are the \"What\" of the cloud. We will start with compute, called *Google Compute Engine* in the next Episode. " + "All the different products and services are the \"**What**\" of the cloud. We will start with compute, called *Google Compute Engine* in the next Episode. " ] }, { @@ -149,9 +149,9 @@ "```{admonition} Exercise\n", "\n", "Take a few moments to navigate a few key services.\n", - " * Navigate to the \"Compute Engine\" service under the \"Compute\" product group.\n", - " * You will probably need to \"Enable\" this service first by clicking on the \"Enable\" button on the \"Compute Engine API\" page. This will only need to be done once per project.\n", - " * Navigate to \"Cloud Storage\" under the \"Storage\" product group and enable the service if necessary.\n", + " * Navigate to \"Cloud Storage\" under the \"Storage\" product group.\n", + " * You will probably need to \"Enable\" this service first by clicking on the \"Enable\" button on the \"Cloud Storage API\" page. This will only need to be done once per project.\n", + " * Navigate to the \"Compute Engine\" service under the \"Compute\" product group and enable the service if necessary.\n", "```" ] }, diff --git a/content/GCP/02_intro_to_compute.ipynb b/content/GCP/02_intro_to_compute.ipynb index fda48cd..cd7504d 100644 --- a/content/GCP/02_intro_to_compute.ipynb +++ b/content/GCP/02_intro_to_compute.ipynb @@ -67,7 +67,7 @@ "To create a VM Instance we do the following:\n", " * Click **Navigation Menu** -> **Compute Engine** (under Compute) -> **VM Instances** -> **+Create Instance** (just under the blue bar) to open the *Create an instance* page.\n", " * In the **New VM instance** tab on the left (selected by default) configure the *VM instance* as follows:\n", - " * For **Name**, enter a unique name for the instances (example: \"essentials-instance-1\")\n", + " * For **Name**, enter a unique name for the instances (example: \"**essentials-test-1**\")\n", " * For **Region** leave the default or select your \"home\" region. The region is the physical location where your data will reside. Your \"home\" region should be close to your work and should be the region you use most of the time.\n", " * For **Zone** leave the default (note how the name is constructed and that it is a separate data center) some zones have different capabilities.\n", " * In the **Machine configuration** section:\n", @@ -97,7 +97,7 @@ "id": "41c63432-a614-4a1e-9967-f49b68f9069e", "metadata": {}, "source": [ - "## Security\n", + "## More on Security (Optional)\n", "\n", "Everything in the cloud requires permission (authorization). Ordinary we would configure and check security first but in the case of exploring services it is often easier to do things out of order. We noted that the *VM instance* was created with the *Compute Engine default service account*, and if the \"Allow full access to all Cloud Api's\" scope is enable, then everyone on the VM has access to all the resources in your project.\n", "\n", @@ -125,9 +125,9 @@ "tags": [] }, "source": [ - "## Follow the VM Allocation\n", + "## Track VM Instance Creation\n", "\n", - "Just as with security, we will audit (follow) the *VM instance* creation by examining at the project *activity*.\n", + "We can track what is going on in our project by following the *VM instance* creation by examining at the project *activity* page on the project dashboard.\n", "\n", "To view the project activity we do the following:\n", "\n", @@ -147,7 +147,7 @@ "tags": [] }, "source": [ - "## Enumerate the VM Instances\n", + "## Find the VM Instances\n", "\n", "Now lets find and connect to the *VM Instance*.\n", " * Navigate to the Google Compute Engine page by clicking **Navigation Menu** -> **Compute Engine** (under Compute) -> **Instances**.\n", @@ -174,7 +174,7 @@ "\n", "To connect to the *VM instance* we enter the following command in the cloud shell:\n", "```\n", - "gcloud compute ssh essentials-instance-1\n", + "gcloud compute ssh essentials-test-1\n", "```\n", "\n", "If you have not used the cloud shell to connect to a *VM Instance* before you will probably be asked to create a new *ssh key*. The Compute Engine will use this key to allow you to access the *VM instance* in a secure manner. If this is the case you will see a message similar to the following:\n", @@ -223,15 +223,15 @@ "\n", "At this point the command will attempt to connect to the *VM Instance* and will ask the following question:\n", "```\n", - "Did you mean zone [us-central1-a] for instance: [essentials-instance-1] (Y/n)? n\n", + "Did you mean zone [us-central1-a] for instance: [essentials-test-1] (Y/n)? n\n", "```\n", "Answer \"n\".\n", "\n", "The command will now configure the instance to allow your ssh key and connect to it.\n", "\n", "```\n", - "No zone specified. Using zone [us-central1-a] for instance: [essentials-instance-1].\n", - "Updating project ssh metadata...working..Updated [https://www.googleapis.com/compute/v1/projects/class-essentials-instance-1].\n", + "No zone specified. Using zone [us-central1-a] for instance: [essentials-test-1].\n", + "Updating project ssh metadata...working..Updated [https://www.googleapis.com/compute/v1/projects/class-essentials-test-1].\n", "Updating project ssh metadata...done.\n", "Waiting for SSH key to propagate.\n", "Warning: Permanently added 'compute.74517428106645607' (ECDSA) to the list of known hosts.\n", @@ -240,7 +240,7 @@ "\n", "Once connected you will see the machine login banner and prompt similar to the following:\n", "```\n", - "Linux instance-1 4.19.0-17-cloud-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64\n", + "Linux essentials-test-1 4.19.0-17-cloud-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64\n", "\n", "The programs included with the Debian GNU/Linux system are free software;\n", "the exact distribution terms for each program are described in the\n", @@ -248,7 +248,7 @@ "\n", "Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\n", "permitted by applicable law.\n", - "learner@essentials-instance-1:~$\n", + "learner@essentials-test-1:~$\n", "```\n", "\n", "Congratulations you have now created a *VM Instance* and connected to it.\n", @@ -288,7 +288,7 @@ "```{admonition} Exercise\n", "\n", "* Try to delete the ***VM instance*** on your own\n", - "* Try to follow the process we just learned (hint: *follow* and *enumerate*)\n", + "* Try to follow the process we just learned (hint: *track* and *list*)\n", "```" ] },