Ce contenu n'est pas disponible dans la langue sélectionnée.
4.2. Setting up Google Compute Engine
To set up Google Compute engine, perform the following steps:
4.2.1. SSH Keys
SSH keys must be generated and registered with the Google Compute Engine project to connect via standard SSH. You can SSH directly to the instance public IP addresses after it is generated.
- Generate an SSH key pair for use with Google Compute Engine using the following command:
# ssh-keygen -t rsa -f ~/.ssh/google_compute_engine
- In the Google Developers Console, click Computer > Compute Engine > Metadata > SSH Keys > Edit.
- Enter the output generated from
~/.ssh/google_compute_engine.pubfile, and click Save.
- To enable SSH agent to use this identity file for each new local console session, run the following command on the console:
# ssh-add ~/.ssh/google_compute_engine
- Adding the below line to your
~/.ssh/configfile helps you automate this command.IdentityFile ~/.ssh/google_compute_engine
- You can now connect via standard SSH to the new VM instances created in your Google Compute Engine project.
# ssh -i ~/.ssh/google_compute_engine <username>@<instance_external_ip>
The gcloud compute config-ssh command from the Google Cloud SDK populates your
~/.ssh/config file with aliases that allows simple SSH connections by instance name.
4.2.2. Setting up Quota
The minimum persistent disk quotas listed below are required for this deployment. It may be necessary to request a quota increase from Google.
- Local region (see US-CENTRAL1 illustration in Section 4.1.3, “Primary Storage Pool Configuration”)
- Total persistent disk reserved (GB) >= 206,000
- CPUs >= 100
- Remote region (see EUROPE-WEST1 illustration in Section 4.1.4, “Secondary Storage Pool Configuration”)
- Total persistent disk reserved (GB) >= 103,000
- CPUs >=40
