Set up BYO-GCP

A service account represents a Google service identity, such as code running on Compute Engine Virtual Machines (VMs), App Engine apps, or systems running outside Google.

1. In Google Cloud Platform, sign in as Project Editor.

2. Select Google Cloud Setup > IAM & Admin > Service Accounts > Create service account.
3. Enter a name and description for your service account. A service account ID and email address are auto-generated.
4. Click Create and Continue.
5. Select Grant this service account access to project.
6. Select Project > Editor access.

1. Select the name of your new service account.
2. Select the Keys tab.
3. Select Add Key > Create new key.
4. Create and download a JSON key. This will be a file named xxxx-nnnn.json in your downloads folder.

1. Within your Cameyo project, navigate to the Compute Engine | VM instances section.
2. Click Enable.

1. Navigate to https://online.cameyo.com/byo-gcp.
2. In Cloud Platform Details, paste your GCP service account's JSON.
3. Click Submit.
4. Complete the tasks in Create a server.

Cloud servers have an assigned performance level (Capacity).

1. Navigate to Servers . Your new server should be listed.

2. Select Details > Information > Capacity.

   Level	GCP Type	Virtual CPUs	Memory	Comment
   5	n1-standard-1	1	3.75 GB	No Internet access
   6	n1-standard-1	1	3.75 GB	Internet access
   7	n1-standard-2	2	7.50 GB
   8	n1-standard-4	4	15 GB
   9	n1-standard-8	8	30 GB
   10	n1-standard-16	16	60 GB

3. From the drop-down, select the required level for your server.

   Things to consider:

   • Level 5 is the capacity for a basic server (without Internet access).
   • Level 7 is the default level, used for typical servers used for line-of-business applications, such as Office, ERP, and other non-taxing applications.
   • Level 8 is the typical server level for more resource-intensive applications such as Adobe Photoshop.
   • Level 9 is the typical server level for servers running 3D applications like AutoCAD.
4. Click Set.
5. Click Save.

Adjust your Google Cloud capacity

Once your initial tests are done and if you intend to scale up capacity, it is important to check that your quota limitations are sufficient for Cameyo to work with.

1. Navigate to IAM & Admin.
2. Select Quotas.
3. Check that your target region has sufficient Compute Engine API resources, including:

• CPUs (note that this is the total number of CPUs, not just VMs).

• Persistent Disk SSD / Standard

• Snapshots

• Static IP addresses

Set up custom VPC and subnetworks

You can configure custom Virtual Private Cloud (VPC) and subnets for newly-created Google Cloud instances.

Option 1: Using BYO-GCP configuration

To specify a custom VPC and/or subnet for your Cameyo GCP project, proceed as following:

• Navigate to your Cameyo BYO GCP page: https://online.cameyo.com/byo-gcp
• Within the service account JSON, enter two additional fields: "CustomNetworks" with your VPC setting, and (optionally) "CustomSubNets" with your subnet.

Example:

VPC:          projects/project-8743643/global/my-custom-vpc
Subnets:   projects/project-8743643/regions/us-east1/subnetworks/my-trusted-subnet1

If you are using different subnetworks for different regions, contact support and we will help you set them up.

You can find the full RESTful name of your subnets by clicking on the REST link on their page and referring to the "selfLink" item:

Option 2: Using PowerTags

Custom VPC and subnets can be specified for newly-created machines using the special PowerTags !CLOUDVPC and optionally !CLOUDSUBNETS.

Example:

!CLOUDVPC=projects/project-8743643/global/networks/my-custom-vpc
!CLOUDSUBNETS=projects/project-8743643/regions/us-east1/subnetworks/my-trusted-subnet1

These PowerTags need to be specified prior to the server's creation, either at the company's level page or the cluster's.

There might be occasions where you do not want that an external IP address is created (Cloud Tunnel only). In this case you can specify:

!CLOUDIP=0

Configure custom resource tags and labels

You can configure custom tags and labels to be bound to created Google Cloud computing resources.