BYO GCP Account

Bring Your Own GCP Subscription to Frame

Xi Frame provides two options for using Google Cloud Platform (GCP) infrastructure. You can “Bring Your Own” (BYO) GCP subscription that you own and manage yourself or purchase Nutanix IaaS credits to use Nutanix-managed GCP subscription. When you bring your own (BYO) GCP subscription, you pay Google directly for infrastructure (your VMs, storage, networking, etc.) and only pay Xi Frame for the platform services.

Common reasons why you would bring your own GCP subscription are:

  • You wish to take advantage of existing billing arrangements with GCP for convenience and/or pricing. For example, your organization may already have certain GCP consumption commitments or pre-payments – you can use Frame to consume those resources on your own GCP account.

  • You want to have additional administrative control over your Xi Frame workloads for more detailed monitoring and metrics.

  • You want to configure other network integrations (VPN gateways, Interconnects) which you can’t do using Nutanix-managed GCP subscription.

  • You must meet industry-specific compliance regimes (e.g., HIPAA) that require you to fully manage and control your cloud resources.

Requirements

  • Ensure that you are an “Owner” of the GCP project you that you wish to use to host Xi Frame workloads.

  • Your GCP Account ID is the only piece of information required to integrate with the Xi Frame Platform, which can be found by going to the Dashboard of your GCP console.

Adding your GCP Cloud Account

BYO cloud accounts can be created either at the “customer” or “organization” tiers of Frame’s logical hierarchy. More information about Frame’s hierarchy concepts can be referenced here.

A BYO cloud account created at the “customer” (highest) tier will be accessible to all hierarchical children (“organizations” and their accounts). If you choose to add the BYO cloud account at the “organization” tier, the BYO cloud account will only be available to the chosen organization and any accounts underneath it. Customer Administrators can add a BYO cloud account at the Customer or Organization level while Organization Administrators may only add a BYO cloud account at the Organization tier.

Note

A particular cloud subscription can only be associated with a single entity on the Frame platform. If you associate your cloud subscription to one Organization, it cannot be associated with another Organization or Customer. If your use case requires that multiple Organizations will have access to your Azure subscription, you must associate the cloud account to your Customer entity.

GCP Cloud Account Registration Procedure

  1. Navigate to your Google Cloud Platform console by going to https://console.cloud.google.com/

  2. Locate and copy the Project ID found in your GCP console Dashboard.

    ../_images/GCPsetup1.png
  3. In a separate tab, navigate to your Xi Frame platform account. You can configure a new cloud provider on either the Org or Customer entity level. For this example, we will be configuring the GCP Cloud Account on the Organization level. Click the ellipsis listed to the right of the Org and select “Edit.”

    ../_images/GCPsetup1a.png
  4. Navigate to the “Cloud Accounts” tab and click “Add Cloud Account” in the upper right corner of the screen.

    ../_images/addnewcloud0.png
  5. The “Add new cloud account” window will appear. Select “Google” as your cloud provider.

    ../_images/GCPsetup3.png
  6. Enter a descriptive name for your GCP Cloud Account and select the desired regions for your Xi Frame workloads. You can select multiple regions if desired.

  7. Paste the Project ID you copied earlier from your GCP Console into the “Project ID” field.

  8. After entering your GCP Project ID, a new field will appear displaying a command. Copy the command to your clipboard.

  9. Next, click the “Prepare the Account with GCP Cloud Shell” button. A new tab will open, taking you to your GCP console.

  10. A prompt will appear asking for your permission to proceed. Click “Proceed.”

    ../_images/GCPsetup4.png
  11. After the Cloud Shell has initialized, paste the deployment command into the command shell and press “Enter.” Once the command has completed successfully, you can close the tab.

    ../_images/GCPsetup5.png
  12. Navigate back to your Xi Frame platform tab and click “Verify Cloud Account Setup” button. Once verified, a message will appear below the button informing you that the cloud account setup has been verified.

  13. Select your desired datacenters.

  14. Click the check box once you have read through the disclaimer, and then click “Create.”

Now that your GCP Cloud Account is created and accessible within Frame, you will be able to create Frame accounts using this BYO cloud account.

Resources Created During BYO GCP Cloud Account Creation

Xi Frame will immediately create multiple roles comprised of the minimum required permissions for Frame’s backend communication and orchestration. Xi Frame also enables Google’s Compute Engine and Cloud DNS APIs.

GCP Service Limits

By default, a newly created GCP account will impose certain service limits on available resources. Depending on the size of the Frame workload required, you will likely need to adjust the default limits imposed on the GCP account. If these limits are set to values that are lower than what is required by the Xi Frame platform, you can expect certain functions to either fail, or be substantially delayed. The requirements by Xi Frame for these service limits depends on the desired workload and required resources. The recommended service limit increases include the following:

Note

The following steps may not be necessary for smaller production environments or trial accounts.

Recommended GCP Resource Quota Limits

GCP Resource

Recommendation

Compute Engine

Frame recommends setting the GCP Compute Engine quota limit to 2.2x your expected max number of instances. The additional 20% will accommodate any additional resources such as Sandboxes, Utility servers, etc.

Persistent Disk

Frame provisions Google Persistent Disks for all workload VMs. These persistent disks are zonal SSDs. Typically, this resource does not need to be modified. If you have any concerns about capacity, we recommend 80 GiB per instance.

IP Addresses (regional and global)

Each region has a base IP limit for both static and in-use IP addresses. You will need at least 2 public IPs available per workload instance and one public IP per Sandbox/Utility Server VM.

VPCs

With GCP, only a single VPC is required (even for multiple regions).

GPU-backed Instances

We recommend increasing Compute Engine limits for GPU-backed instances to 2.2x your expected max number of instances. The additional 20% will accommodate any additional resources such as Sandboxes, Utility servers, etc.

We have created all new Business Account types on Xi Frame and we hope you will take this opportunity to transition your information and Accounts over to our new platform.

GCP Instance Types

Each IaaS provider has a unique naming scheme for their instance types. GCP names their instance types (or “machine types”) based on the “machine type families” they have created for specific workload use cases. More information about machine types and machine type families can be found in GCP’s official documentation.

For the latest GCP instances supported by Xi Frame, refer to Nutanix Xi Frame Pricing Page. Note that since you are bringing your own GCP account, your pricing may be different from that shown in the table.