Skip to content

Commit bbaa29f

Browse files
julesvanriegithub-actions
andauthored
Trigger rebuild for VM setup changes (#337)
* Trigger rebuild for VM setup changes This PR on data-engineering changes the instructions: lewagon/data-engineering-setup#63 * setup guides generated --------- Co-authored-by: github-actions <github-actions@github.com>
1 parent ec110e5 commit bbaa29f

File tree

1 file changed

+8
-73
lines changed

1 file changed

+8
-73
lines changed

VM.md

Lines changed: 8 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -216,85 +216,20 @@ Go to your project [APIs dashboard](https://console.cloud.google.com/apis/dashbo
216216
- Compute Engine is now enabled on your project
217217

218218

219-
## Virtual Machine (VM)
220-
221-
**👌 Note: Skip to the next section if you already have a VM set up**
222-
223-
_Note: The following section requires you already have a [Google Cloud Platform](https://cloud.google.com/) account associated with an active [Billing account](https://console.cloud.google.com/billing)._
224-
225-
- Go to console.cloud.google.com > > Compute Engine > VM instances > Create instance
226-
- Name it `lewagon-data-eng-vm-<github_username>`, replace `<github_username>` with your own, e.g. `krokrob`
227-
- Region `europe-west1`, choose the closest one among the [available regions](https://cloud.google.com/compute/docs/regions-zones#available)
228-
229-
<img alt="gcloud-console-vm-create-instance" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-create-instance.png" width=500>
230-
- In the section `Machine configuration` under the sub-heading `Machine type`
231-
- Select General purpose > PRESET > e2-standard-4
232-
233-
<img alt="gcloud-console-vm-e2-standard4" src="https://wagon-public-assets.s3.eu-west-3.amazonaws.com/v9dv42llst8qjp2uj0d1yr00po1g" width=500>
234-
- Boot disk > Change
235-
- Operating system > Ubuntu
236-
- Version > Ubuntu 22.04 LTS x86/64
237-
- Boot disk type > Balanced persistent disk
238-
- Size > upgrade to 150GB
239-
240-
<img alt="gcloud-console-vm-ubunt" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-ubunt.png" width=500>
241-
- Open `Networking, Disks, ...` under `Advanced options`
242-
- Open `Networking`
243-
244-
<img alt="gcloud-console-vm-networking" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-networking.png" width=500>
245-
- Go to `Network interfaces` and click on `default default (...)` with a downward arrow on the right.
246-
247-
<img alt="gcloud-console-vm-network-interfaces" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-network-interfaces.png" width=500>
248-
- This opened a box `Edit network interface`
249-
- Go to the dropdown `External IPv4 address`, click on it, click on `RESERVE STATIC EXTERNAL IP ADDRESS`
250-
251-
<img alt="gcloud-console-vm-create-static-ip" src="https://wagon-public-assets.s3.eu-west-3.amazonaws.com/1ax09j2zld7x0lsvpp9p8ld8u5vc" width=300>
252-
- Give it a name, like "lewagon-data-eng-vm-ip-<github_username>" (replace `<github_username>` with your own) and description "Le Wagon - Data Engineering VM IP". This will take a few seconds.
253219

254-
<img alt="gcloud-console-reserve-static-ip" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-reserve-static-ip.png" width=300>
255-
256-
- You will now have a public IP associated with your account, and later to your VM instance. Click on `Done` at the bottom of the section `Edit network interface` you were in.
257-
258-
<img alt="gcloud-console-new-external-ip" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-new-external-ip.png" width=300>
259-
260-
### Public SSH key
261-
- Open the `Security` section
262-
263-
<img alt="gcloud-console-vm-security" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-security.png" width=300>
264-
- Open the `Manage access` subsection
265-
266-
<img alt="gcloud-console-manage-access" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-manage-access.png" width=200>
267-
- Go to `Add manually generated SSH keys` and click `Add item`
268-
269-
<img alt="gcloud-console-add-manual-ssh-key" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-add-manual-ssh-key.png" width=500>
270-
- In your terminal display your public SSH key:
271-
- Windows: navigate to where you created your SSH key and open `id_ed25519.pub`
272-
273-
- Mac/Linux users can use:
274-
```bash
275-
cat ~/.ssh/id_ed25519.pub
276-
# OR cat ~/.ssh/de-bootcamp.pub if you created a unique key
277-
```
278-
- Copy your public SSH key and paste it:
279-
280-
<img alt="gcloud-console-add-ssh-key-pub" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-add-ssh-key-pub.png" width=500>
281-
- On the right hand side you should see
282-
283-
<img alt="gcloud-console-vm-price-month" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-price-month.png" width=300>
284-
- You should be good to go and click `CREATE` at the bottom
220+
## Virtual Machine (VM)
285221

286-
<img alt="gcloud-console-vm-create" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-create.png" width=500>
287-
- It will take a few minutes for your virtual machine (VM) to be created. Your instance will show up like below when ready, with a green circled tick, named `lewagon-data-eng-vm-krokrob` (`krokrob` being replaced by your GitHub username).
222+
_Note: The VM setup requires a [Google Cloud Platform](https://cloud.google.com/) account associated with an active [Billing account](https://console.cloud.google.com/billing)_
288223

289-
<img alt="gcloud-console-vm-instance-running" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-instance-running.png" width=500>
290-
- Click on your instance
224+
ℹ️ In the guide, left click to drag the screenshots if necessary
291225

292-
<img alt="gcloud-console-vm-running" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-running.png" width=500>
293-
- Go down to the section `SSH keys`, and write down your username (you need it for the next section)
226+
ℹ️ You may adjust the aspect ratio of your browser window to see the full screenshots
294227

295-
<img alt="gcloud-console-vm-username" src="https://wagon-public-datasets.s3.amazonaws.com/data-engineering/setup/gcloud-console-vm-username.png" width=300>
228+
<a href="https://scribehow.com/embed/Create_a_Google_Cloud_VM_Instance_with_SSH_Key__1ohFlAbSR9yoG28S0PDfwg">
229+
<img src="https://github.com/lewagon/data-engineering-setup/blob/main/images/scribe_gcp_vm.png" alt="scribe gcp vm" width="500">
230+
</a>
296231

297-
Congrats, your virtual machine is up and running, it is time to connect it with VS Code!
232+
**👌 Follow [this guide](https://scribehow.com/embed/Create_a_Google_Cloud_VM_Instance_with_SSH_Key__1ohFlAbSR9yoG28S0PDfwg) or skip to the next section if you already have a VM set up**
298233

299234

300235
## Visual Studio Code

0 commit comments

Comments
 (0)