Fix heading levels (warnings) and TOC

tmiddelkoop · Nov 8, 2021 · 10d6c3f · 10d6c3f
1 parent f06a0ca
commit 10d6c3f
Show file tree

Hide file tree

Showing 10 changed files with 121 additions and 137 deletions.
diff --git a/content/GCP/01_intro_to_cloud_console.ipynb b/content/GCP/01_intro_to_cloud_console.ipynb
@@ -7,7 +7,7 @@
     "tags": []
    },
    "source": [
-    "## Introduction to the GCP Cloud Console\n",
+    "# Introduction to the GCP Cloud Console\n",
     "\n",
     "Learner Questions\n",
     " * How do I find things in the web console?\n",
@@ -22,9 +22,9 @@
    "id": "3316c7f9-b0c8-4565-bdc6-7582c4f16127",
    "metadata": {},
    "source": [
-    "### The Who, What, and Where of the Cloud\n",
+    "## The Who, What, and Where 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."
+    "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."
    ]
   },
   {
@@ -34,7 +34,7 @@
     "tags": []
    },
    "source": [
-    "### Accounts (Authentication and Identity)\n",
+    "## Accounts (Authentication and Identity)\n",
     "\n",
     "The (Google) **Account** is the identity used to access the Google Cloud Platform web console and is in the form of an email address and is associated with an individual (the *who* is *you*!).  This is typically the account you use to access Google services associated with your institution and not your personal account.  This is the \"Who\" of the cloud.  We will now login to the Google Cloud Platform web console and verify our account.\n",
     "\n",
@@ -54,7 +54,7 @@
     "tags": []
    },
    "source": [
-    "#### Exercise\n",
+    "### Exercise\n",
     "\n",
     "Take a few moments to ask yourself the following questions:\n",
     " * What account are you currently using in the Google Cloud web console?\n",
@@ -69,7 +69,7 @@
    "id": "5cfe3d13-c050-49ee-873b-be823fda5b10",
    "metadata": {},
    "source": [
-    "### Projects\n",
+    "## 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",
     "\n",
@@ -87,7 +87,7 @@
     "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 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) \n",
     "\n",
-    "#### Exercise\n",
+    "### Exercise\n",
     "\n",
     "Take a few moments to ask yourself the following questions:\n",
     "  * What is the *name* of the Project you are currently using in the Google Cloud Platform web console?\n",
@@ -106,7 +106,7 @@
     "tags": []
    },
    "source": [
-    "### Services\n",
+    "## Services\n",
     "\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",
@@ -126,11 +126,10 @@
    "cell_type": "markdown",
    "id": "e955eb3a-4fdc-448b-aef8-ed1dbe2a73d9",
    "metadata": {
-    "jp-MarkdownHeadingCollapsed": true,
     "tags": []
    },
    "source": [
-    "### Everything Else\n",
+    "## Everything Else\n",
     "\n",
     "If you did not already notice, every page on the GCP web console has a blue navigation bar at the top of the page.  This can be used to quickly navigate to the page you need.\n",
     "\n",
@@ -159,7 +158,7 @@
     "tags": []
    },
    "source": [
-    "### Exercise\n",
+    "## Exercise\n",
     "\n",
     "Before we move on, do the following:\n",
     "* Double check that you are in the correct account and project that you will be using for this lesson.\n",

diff --git a/content/GCP/02_intro_to_compute_part1.ipynb → content/GCP/02_intro_to_compute.ipynb b/content/GCP/02_intro_to_compute_part1.ipynb → content/GCP/02_intro_to_compute.ipynb
@@ -7,7 +7,7 @@
     "tags": []
    },
    "source": [
-    "## Introduction to Cloud Compute (Google Compute Engine)\n",
+    "# Introduction to Cloud Compute (Google Compute Engine)\n",
     "\n",
     "Learner Questions\n",
     " * How do I compute in the cloud?\n",
@@ -36,7 +36,7 @@
     "tags": []
    },
    "source": [
-    "### Google Compute Engine\n",
+    "## Google Compute Engine\n",
     "\n",
     "To learn more about the Google Compute Engine service we will use the web console to create, explore, and destroy a Virtual Machine.  The ability to quickly create, explore, and then discard resources in the web-console is a powerful tool to explore a service.  After an initial exploration with the web-console, programmatic access using scripts or configuration management systems should be used.\n",
     "\n",
@@ -52,7 +52,7 @@
     "tags": []
    },
    "source": [
-    "### Allocate a VM Instance\n",
+    "## Allocate a VM Instance\n",
     "\n",
     "We will first create an *VM instance* with defaults to explore the Google Compute Engine service.\n",
     "\n",
@@ -77,7 +77,7 @@
    "id": "41c63432-a614-4a1e-9967-f49b68f9069e",
    "metadata": {},
    "source": [
-    "### Security\n",
+    "## Security\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*, which by *default* has access to all the resources that your Google Account does.\n",
     "\n",
@@ -97,7 +97,7 @@
     "tags": []
    },
    "source": [
-    "### Follow the Storage Allocation\n",
+    "## Follow the Storage Allocation\n",
     "\n",
     "Just as with security, we will audit (follow) the *VM instance* creation by examining at the project *activity*.\n",
     "\n",
@@ -118,7 +118,7 @@
     "tags": []
    },
    "source": [
-    "### Enumerate the VM Instances\n",
+    "## Enumerate the VM Instances\n",
     "\n",
     "To see an overview of resources in the project navigate to the **dashboard** and you will now see at least **1 instance** in the *resources* card under *Compute Engine*.\n",
     "\n",
@@ -135,7 +135,7 @@
     "tags": []
    },
    "source": [
-    "### Connect to the VM Instance\n",
+    "## Connect to the VM Instance\n",
     "\n",
     "To connect to the *VM Instance* we will use the cloud shell in the web console.  Open up a shell by clicking on the **Activate Cloud Shell** icon in the top blue bar if it is not already open.\n",
     "\n",
@@ -236,11 +236,10 @@
    "cell_type": "markdown",
    "id": "0362e76c-3f03-4299-8217-24a2f39ee503",
    "metadata": {
-    "jp-MarkdownHeadingCollapsed": true,
     "tags": []
    },
    "source": [
-    "### Delete the Storage - Exercise \n",
+    "## Delete the Storage - Exercise \n",
     "\n",
     "We will now complete the resource life-cycle by deleting the *VM Instance* we just created. Think about the process we did for creating the bucket and follow a similar one.  \n",
     "\n",
@@ -254,7 +253,7 @@
    "id": "85c697a1-25bc-4b57-9ab6-7c38b6dbbc89",
    "metadata": {},
    "source": [
-    "### References\n",
+    "## References\n",
     "  * Compute Engine Permissions (IAM): https://cloud.google.com/compute/docs/access/iam"
    ]
   }

diff --git a/content/GCP/04_intro_to_cli.ipynb b/content/GCP/04_intro_to_cli.ipynb
@@ -5,7 +5,7 @@
    "id": "5439e525-b985-495f-85a6-e4c8d7452956",
    "metadata": {},
    "source": [
-    "## Introduction to the gcloud CLI\n",
+    "# Introduction to the gcloud CLI\n",
     "\n",
     "Learner Questions\n",
     " * How do I use the Cloud CLI?\n",
@@ -30,7 +30,7 @@
    "id": "c4e1a4c5-7d28-483d-b27c-ef2afa4fb7e5",
    "metadata": {},
    "source": [
-    "### Cloud Automation\n",
+    "## Cloud Automation\n",
     "\n",
     "Now that Drew can create a bucket in the web console they wish to learn how to use tools to automate the process. Drew noticed that the web console could be used to upload and share objects but wishes to learn the command line so that they can automate the and document the process (it is much easier to document commands then describing and showing mouse clicks).\n",
     "\n",
@@ -48,7 +48,7 @@
    "id": "ce598878-1b1c-4e6b-9122-e679e84c7dbb",
    "metadata": {},
    "source": [
-    "### Open a Cloud Shell\n",
+    "## Open a Cloud Shell\n",
     "\n",
     "The Cloud Shell is an easy way to access Comand Line Interface (CLI) commands in a web browser.  Under the hood Cloud Shell is Debian running in a container with 5GB of no-charge persistent storage with most of the Google uti and a lot of other useful tools (git, docker, jq, Docker, etc.) installed by default.\n",
     "\n",
@@ -60,12 +60,12 @@
     "  * Note: You can open the Cloud Shell in a new tab by clicking on icon **Open in a New Window** on the far right of the Cloud Shell bar.\n",
     "\n",
     "\n",
-    "#### Opening Cloud Shell in a Tab - Optional\n",
+    "### Opening Cloud Shell in a Tab - Optional\n",
     "\n",
     " * Click the **Open in a New Window** icon on the far left of the \"Cloud Shell\" tab on the bottom to open up in a separate tab.  Hover the mouse over the icons to see their name/function.  **Note:** you may need to allow popups or enable popups for this website depending on the browser you use.  You can also pull up the tab to increase the shell screen size.\n",
     " * Click the **\"Close editor\"** button (the pencil icon in the top right of the window).\n",
     "\n",
-    "#### Advanced call-out\n",
+    "### Advanced call-out\n",
     "You can access the cloud shell from your laptop via `gcloud cloud-shell ssh` if you have the [Google Cloud SDK installed](https://cloud.google.com/sdk/docs/install).  Installing the Google Cloud SDK will also allow you to run `gcloud` and `gsutil` commands directly from your laptop, workstation, or cluster. *Pro-tip, you cannot use a service account to access the cloud shell.*"
    ]
   },
@@ -74,7 +74,7 @@
    "id": "e4fa29a6-7d8e-4591-af3f-8539b94b3bef",
    "metadata": {},
    "source": [
-    "### Verify the Configuration (Who, What, Where)"
+    "## Verify the Configuration (Who, What, Where)"
    ]
   },
   {
@@ -555,7 +555,7 @@
    "id": "270e0abb-d5e9-476a-af91-060cc0ea0349",
    "metadata": {},
    "source": [
-    "### Exercise\n",
+    "## Exercise\n",
     " * What command shows the project number? (hint: we used it already)\n",
     " * What is the name of this variable? (hint: it is case sensitive)\n",
     " * What command shows *just* the Project Number (hint: use `--format`)\n",
@@ -567,7 +567,7 @@
    "id": "bda44ee1-337a-447d-8377-e8f7ae563316",
    "metadata": {},
    "source": [
-    "### Advanced Call-Out: Formating Output.\n",
+    "## Advanced Call-Out: Formating Output.\n",
     "\n",
     "The following example shows how to output the configuration as `JSON`.  The command `jq` can also be used to parse the JSON data."
    ]

diff --git a/content/GCP/05_intro_to_cloud_storage.ipynb b/content/GCP/05_intro_to_cloud_storage.ipynb
@@ -5,7 +5,7 @@
    "id": "fb98ae89-8494-4fd7-aa97-44380424d68d",
    "metadata": {},
    "source": [
-    "## Introduction to Google Cloud Storage\n",
+    "# Introduction to Google Cloud Storage\n",
     "\n",
     "Learner Questions\n",
     " * How do I store data in the cloud?\n",
@@ -37,7 +37,7 @@
     "tags": []
    },
    "source": [
-    "### Google Cloud Storage\n",
+    "## Google Cloud Storage\n",
     "\n",
     "To learn more about the Google Cloud Storage service we will use the web console to create, explore, and destroy a Bucket.  The ability to quickly create, explore, and then discard resources in the web-console is a powerful tool to explore a service.  After an initial exploration with the web-console, programmatic access using scripts and programming languages should be used.\n",
     "\n",
@@ -53,7 +53,7 @@
     "tags": []
    },
    "source": [
-    "### Security\n",
+    "## Security\n",
     "\n",
     "Everything in the cloud requires permission (authorization).  Let's first verify that we have the permissions to create a bucket.  A Bucket (a resource) is created within a project and inheres permissions from it.\n",
     "\n",
@@ -73,7 +73,7 @@
     "tags": []
    },
    "source": [
-    "### Allocate Google Cloud Storage\n",
+    "## Allocate Google Cloud Storage\n",
     "\n",
     "Now that we have verified the permissions we can now create a bucket. Buckets are where objects are stored and have a globally unique name.\n",
     "\n",
@@ -108,7 +108,7 @@
     "tags": []
    },
    "source": [
-    "### Follow the Storage Allocation\n",
+    "## Follow the Storage Allocation\n",
     "\n",
     "Just as with security, we will audit (follow) the bucket creation by examining at the project *activity*.\n",
     "\n",
@@ -129,7 +129,7 @@
     "tags": []
    },
    "source": [
-    "### Enumerate the Buckets\n",
+    "## Enumerate the Buckets\n",
     "\n",
     "Now lets find and examine the bucket.  To view a bucket we do the following:\n",
     "\n",
@@ -147,7 +147,7 @@
     "tags": []
    },
    "source": [
-    "### Review what is Important\n",
+    "## Review what is Important\n",
     "\n",
     "It is always important to review what is important to you.  It may be cost, or keeping the data secure. Later on we will show how to monitor overall costs.\n",
     "\n",
@@ -162,11 +162,10 @@
    "cell_type": "markdown",
    "id": "0362e76c-3f03-4299-8217-24a2f39ee503",
    "metadata": {
-    "jp-MarkdownHeadingCollapsed": true,
     "tags": []
    },
    "source": [
-    "### Delete the Storage - Exercise \n",
+    "## Delete the Storage - Exercise \n",
     "\n",
     "We will now complete the resource life-cycle by deleting the bucket we just created. Think about the process we did for creating the bucket and follow a similar one.  \n",
     "\n",
@@ -180,7 +179,7 @@
    "id": "3a28e28d-1d70-44fa-a952-4f3506ea85ec",
    "metadata": {},
    "source": [
-    "### Discussion\n",
+    "## Discussion\n",
     "\n",
     "* What does the words \"Secure\", \"Allocate\", \"Follow\", and \"Enumerate\" Spell?\n",
     "* Why do you think we use this framework?"
@@ -191,7 +190,7 @@
    "id": "97d7ebc5-4a81-4f1a-aaf3-517adf70640a",
    "metadata": {},
    "source": [
-    "### Resources in Google Cloud Platform - Optional\n",
+    "## Resources in Google Cloud Platform - Optional\n",
     "\n",
     "Even though we only covered the Google Cloud Storage service in this episode, this process can be used for other *resources* allocated in the cloud.  The term *resource* is used for the \"things\" that live in a Project, such as compute, storage, and networking and other services.  Resources have the following characteristics:\n",
     "\n",
@@ -209,8 +208,7 @@
    "id": "85c697a1-25bc-4b57-9ab6-7c38b6dbbc89",
    "metadata": {},
    "source": [
-    "\n",
-    "### References\n",
+    "## References\n",
     "  * API reference https://cloud.google.com/storage/docs/reference/libraries\n",
     "  * Permissions (IAM): https://cloud.google.com/storage/docs/access-control/iam-permissions"
    ]