Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/compute/docs/instances/create-vm-from-custom-image below:

Create an instance from a custom image | Compute Engine Documentation

that exists only in your project.

An instance contains a bootloader, a boot file system, and an OS image. You can create custom images from source disks, images, snapshots, or images stored in Cloud Storage and use these images to create instances. By default, a custom image belongs only to the project in which it was created.

This predefined role contains the permissions required to create an instance from a custom image. To see the exact permissions that are required, expand the Required permissions section:

1. In the Google Cloud console, go to the Create an instance page.

   Go to Create an instance

   If prompted, select your project and click Continue.

   The Create an instance page appears and displays the Machine configuration pane.

2. In the Machine configuration pane, do the following:

   1. In the Name field, specify a name for your instance. For more information, see Resource naming convention.

   2. Optional: In the Zone field, select a zone for this instance.

      The default selection is Any. If you don't change this default selection, then Google automatically chooses a zone for you based on machine type and availability.

   3. Select the machine family for your instance. The Google Cloud console then displays the machine series that are available for your selected machine family. The following machine family options are available:

      • General purpose
      • Compute optimized
      • Memory optimized
      • Storage optimized
      • GPUs

   4. In the Series column, select the machine series for your instance.

      If you selected GPUs as the machine family in the previous step, then select the GPU type that you want. The machine series is then automatically selected for the selected GPU type.

   5. In the Machine type section, select the machine type for your instance.

3. In the navigation menu, click OS and storage. In the Operating system and storage pane that appears, configure your boot disk by doing the following:

   1. Click Change. The Boot disk pane appears and displays the Public images tab.
   2. Click Custom images. The Custom images tab appears.
   3. To select the image project, click Change, and then select the project that contains the image.
   4. In the Image list, select the image that you want to import.
   5. In the Boot disk type list, select the type of the boot disk.
   6. In the Size (GB) field, specify the size of the boot disk.
   7. Optional: For Hyperdisk Balanced boot disks, specify values for the Provisioned IOPS and Provisioned throughput fields.
   8. Optional: For advanced configuration options, expand the expand_more Show advanced configurations section.
   9. To confirm your boot disk options and return to the Operating system and storage pane, click Select.

4. In the navigation menu, click Networking. In the Networking pane that appears, do the following:

   1. Go to the Firewall section.

   2. To permit HTTP or HTTPS traffic to the instance, select Allow HTTP traffic or Allow HTTPS traffic.

      The Compute Engine adds a network tag to your instance and creates the corresponding ingress firewall rule that allows all incoming traffic on tcp:80 (HTTP) or tcp:443 (HTTPS). The network tag associates the firewall rule with the instance. For more information, see Firewall rules overview in the Cloud Next Generation Firewall documentation.

5. Optional: Specify other configuration options. For more information, see Configuration options during instance creation.

6. To create and start the instance, click Create.

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. Run the gcloud compute instances create command to create an instance with a custom image:

   gcloud compute instances create VM_NAME \
       --image-project IMAGE_PROJECT \
       IMAGE_FLAG \
       --subnet SUBNET
   

   Replace the following:

   • VM_NAME: the name of the VM
   • IMAGE_PROJECT: the ID of the Google Cloud project that contains the image
   • IMAGE_FLAG: specify one of the following:
     • Use the --image IMAGE_NAME flag to specify a custom image.

       For example, --image my-debian-image-v2.

     • If you created your custom images as part of a custom image family, use the --image-family IMAGE_FAMILY_NAME flag to specify that custom image family.

       This creates the VM from the most recent, non-deprecated OS image and OS version in your custom image family. For example, if you specify --image-family my-debian-family, Compute Engine creates a VM from the latest OS image in your custom my-debian-family image family.

     Note: Compute Engine uses the default image family and project if you don't specify an image, for example debian-10 and debian-cloud, respectively.

   • SUBNET: if the subnet and instance are in the same project, replace SUBNET with the name of a subnet that is in the same region as the instance.

1. In the Google Cloud console, go to the VM instances page.

   Go to VM Instances

2. Click Create instance.
3. Specify the parameters you want.
4. At the top or bottom of the page, click Equivalent code, and then click the Terraform tab to view the Terraform code.

Before trying this sample, follow the Go setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Go API reference documentation.

To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.

Before trying this sample, follow the Java setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Java API reference documentation.

To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.

Before trying this sample, follow the Node.js setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Node.js API reference documentation.

To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.

Before trying this sample, follow the Python setup instructions in the Compute Engine quickstart using client libraries. For more information, see the Compute Engine Python API reference documentation.

To authenticate to Compute Engine, set up Application Default Credentials. For more information, see Set up authentication for a local development environment.

The process for creating an instance with a custom image in the API is the same as if you were creating an instance with a publicly available image.

To create the instance from a custom image, use the instances.insert method.

POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instances

{
   "machineType":"zones/MACHINE_TYPE_ZONE/machineTypes/MACHINE_TYPE",
   "name":"VM_NAME",
   
   "disks":[
      {
         "initializeParams":{
            "sourceImage":"projects/IMAGE_PROJECT/global/images/IMAGE"
         },
         "boot":true
      }
   ],
   
   
   "networkInterfaces":[
      {
         "network":"global/networks/NETWORK_NAME"
      }
   ],
   
  
   "shieldedInstanceConfig":{
      "enableSecureBoot":"ENABLE_SECURE_BOOT"
   }
}

Replace the following:

• PROJECT_ID: ID of the project to create the VM in
• ZONE: zone to create the VM in
• MACHINE_TYPE_ZONE: zone containing the machine type to use for the new VM
• MACHINE_TYPE: machine type, predefined or custom, for the new VM
• VM_NAME: name of the new VM
• IMAGE_PROJECT: name of the project that contains the custom image
• IMAGE: specify one of the following:
  • IMAGE: name of your custom image. For example, "sourceImage": "projects/my-project-1234/global/images/my-debian-image-v2".
  • IMAGE_FAMILY: if you created your custom images as part of a custom image family, specify that custom image family.

    This creates the VM from the most recent, non-deprecated OS image in your custom image family. For example, if you specify "sourceImage": "projects/my-project-1234/global/images/family/my-debian-family", Compute Engine creates a VM from the latest version of the OS image in the custom my-debian-family image family.

• NETWORK_NAME: the VPC network that you want to use for the VM. You can specify default to use your default network.

• ENABLE_SECURE_BOOT: Optional: If you chose an image that supports Shielded VM features, Compute Engine, by default, enables the virtual trusted platform module (vTPM) and integrity monitoring. Compute Engine does not enable Secure Boot by default.

  If you specify true for enableSecureBoot, Compute Engine creates a VM with all three Shielded VM features enabled. After Compute Engine starts your VM, to modify Shielded VM options, you must stop the VM.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4