Create non-ULL Compute Engine instances for auxiliary workloads

Private Preview — ULL Solution

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

ULL Solution is available only to approved exchange operators and their exchange participants. If you are an approved exchange participant, contact [e-mail] to request access.

This page describes how to create non-Ultra Low Latency (ULL) Compute Engine instances by using U4S machine types from the U4S machine series.

You can create non-ULL instances in the private zones supported by ULL Solution for close proximity to ULL instances. You can use non-ULL instances to provide data or services to ULL instances, or to send and receive Cloud Multicast traffic.

Before you begin

Before you create non-ULL compute instances, see the following sections.

Create a VPC network

If you haven't already, create a VPC network for your instance as described in Configuration overview for ULL Solution.

Ensure that the network has a subnet in the region in which you plan to create your instance.

Set your project

Set the gcloud CLI to use your project. Alternatively you can include the --project=PROJECT_ID flag for each command in the following procedures.

    gcloud config set project PROJECT_ID

Replace PROJECT_ID with the ID of your project.

Create a non-ULL instance

This section describes how to create a new non-ULL instance to use for auxiliary workloads.

For general information about creating compute instances, including additional configuration options, see Create and start a Compute Engine instance.

gcloud

To create a non-ULL instance, use the compute instances create command.

gcloud compute instances create INSTANCE_NAME \
    --zone=ZONE \
    --machine-type=MACHINE_TYPE \
    --image-project=IMAGE_PROJECT \
    --image=IMAGE_NAME \
    --network=NETWORK \
    --subnet=SUBNET

Replace the following values:

• ZONE: the zone in which to create the instance
• INSTANCE_NAME: a name for the instance
• MACHINE_TYPE: the U4S machine type to use for the instance.
• IMAGE_PROJECT: the image project. For testing during Preview, use the image project provided by Google. See Operating system support for U4 machine types.
• IMAGE_NAME: the image name. For testing during Preview, use the image provided by Google. See Operating system support for U4 machine types.
• NETWORK, SUBNET: the general-purpose VPC network and subnet in which to host the instance.

What's next

• If you plan to use the non-ULL instance as a multicast consumer for Cloud Multicast, see Configure an existing instance to be a multicast consumer in the Cloud Multicast documentation.
• To synchronize your instance system clock to the physical NIC clock of its host server, see Configure accurate time.