Account Creation

Frame Customer and Organization Administrators can create and manage multiple accounts from their Admin console. Each account is created:

• With an AHV, AWS, Azure, GCP or IBM (Infrastructure as a Service, IaaS) cloud account,
• In an on-premises datacenter (if created with an AHV Cloud Account) or a public cloud region (if created with an IaaS Cloud Account),
• In a virtual network (VLAN, VPC, or VNET),
• Non-persistent or persistent, and
• Having its own base image, unique set of applications, URLs, application and/or desktop Launchpads, and properties.

:::caution

Infrastructure

Public Cloud

When creating a Frame account in public cloud (AWS, Azure, GCP, or IBM), the Customer or Organization Administrator may choose from one of four different network deployments. Account creation instructions for each network deployment model are provided in the next section.

• Frame-Managed Networking (Public network): all workload VMs have public IP addresses. Frame Platform creates the VNET or VPC.
• Frame-Managed Networking (Private network): all workload VMs have private IP addresses. Frame Platform creates the VNET or VPC.
• Frame-Managed Networking (Private network with Streaming Gateway Appliance (SGA)): all workload VMs have private IP addresses with one public IP address. Frame Platform creates the two VNETs or VPCs (one for the workload VMs and the second for up to 4 SGA VMs).
• Customer-Managed Networking: all workload VMs have private IP addresses. The customer is solely responsible for configuring and managing the network containing the Frame account workload VMs, routing between end users and the workload VMs, and creation of the SGA (if required).

AHV Infrastructure

When creating a Frame account on AHV infrastructure, the Customer or Organization Administrator creates the Frame account in an existing VLAN in the registered AHV Cloud Account. If the customer requires the SGA to support users accessing the workload VMs from the Internet without a VPN, they will deploy the SGA VM(s) independently in a DMZ LAN.

• Customer-Managed Networking (Private network): all workload VMs have private IP addresses. The customer is solely responsible for configuring and managing the network containing the Frame account workload VMs and routing between end users and the workload VMs.
• Customer-Managed Networking (Private network with Streaming Gateway Appliance (SGA): all workload VMs have private IP addresses. The customer is solely responsible for configuring and managing the networks containing the Frame account workload VMs and SGA VM(s) and routing between end users and the SGA VM(s) and between the SGA VM(s) and the workload VMs.

Create a New Frame Account Entity

1. Administrators with the appropriate role can create new accounts by selecting Accounts in the left-hand menu from the Customer or Organization Dashboard in their Admin Console.

2. Click the Create Account link located on the upper right portion of the screen. The first set of parameters to specify will determine the infrastructure, location, and networking option for the Frame account.

Use the tabs below to find instructions for each network deployment configuration:

Customers who wish to rapidly create a Frame account on the public cloud infrastructure for users accessing the virtualized applications/desktops from the Internet can choose this option. This procedure will provision a Frame account with the network requirements and architecture as defined in Public Cloud (Default) Network Requirements. All workload VMs will have public IP addresses.

Field/Button	Description
Organization	If account created at the customer level, this field is visible. Select or search for the top-level organization the account will reside under.
Account Name	Frame automatically generates an account name for you, but you can edit this field if desired. The account name will be displayed in the account Dashboard and Launchpad.
Account URL	This editable field designates the unique identifier for the account, when referencing the account in a URL. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct-123
Cloud Provider	Select the desired cloud or IaaS (Infrastructure-as-a-Service) provider for your account.
Cloud Account	Select the desired cloud account to use, if there is more than one cloud account for that cloud provider.
Region	Specify the desired datacenter you would like the account to be created in.
Networking	Select Frame-Managed Networking
Network Type	Select Public Network.
Customize VPC  Settings	Select to specify a VPC/VNET CIDR. If left unchecked, a randomized CIDR (e.g., 10.{0-255}.0.0/18) will be used. To connect this VPC/VNET to another network (peer, VPN, etc.), use a non-overlapping CIDR (e.g., 10.0.0.0/20, 192.168.0.0/24). You can change the CIDR later in Dashboard > Settings > Networking, provided no network resources are attached.

Customers who wish to create a Frame account on the public cloud infrastructure for users accessing the virtualized applications/desktops through a private network can choose this option. This procedure will provision a Frame account with the network requirements and architecture as defined in Public Cloud with Private Networking. All workload VMs will only have private IP addresses.

Networking and routing must be configured to reach the workload VMs, otherwise the customer will not be able to access the Sandbox, Utility Servers, or production VMs.

Field/Button	Description
Organization	If account created at the customer level, this field is visible. Select or search for the top-level organization the account will reside under.
Account Name	Frame automatically generates an account name for you, but you can edit this field if desired. The account name will be displayed in the account Dashboard and Launchpad.
Account URL	This editable field designates the unique identifier for the account, when referencing the account in a URL. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct-private
Cloud Provider	Select the desired cloud or IaaS (Infrastructure-as-a-Service) provider for your account.
Cloud Account	Select the desired cloud account to use, if there is more than one cloud account for that cloud provider.
Region	Specify the desired datacenter you would like the account to be created in.
Networking	Select Frame-Managed Networking
Network Type	Select Private Network.
Customize VPC Settings	Select this checkbox to specify a specific VPC/VNET CIDR. If you plan to connect this VPC/VNET to another network through a peer, VPN, or other private connection, you need to specify a non-overlapping CIDR (e.g., 10.0.0.0/20, 192.168.0.0/24). The VPC/VNET CIDR can be changed after the Frame account is created under Dashboard, Settings, Networking, as long as there are no customer-provisioned network resources (e.g., peers, VPNs, gateways, etc.) attached to the Frame-provisioned VPC/VNET. Note: If left unchecked, a randomized /16 CIDR from the 10.0.0.0/8 range will be used. <img style="scale:80%," class="no-zoom" id="vpc-settings"src={image} alt="VPC Settings"/> </td> </tr>

Customers who wish to create a Frame account on the public cloud infrastructure for users accessing the virtualized applications/desktops through a single public IP address can choose this option. This procedure will provision a Frame account with the network requirements and architecture as defined in Public Cloud with Private Networking and SGA. All workload VMs will only have private IP addresses.

Field/Button	Description
Organization	If account created at the customer level, this field is visible. Select or search for the the top-level organization the account will reside under.
Account Name	Frame automatically generates an account name for you, but you can edit this field if desired. The account name will be displayed in the account Dashboard and Launchpad.
Account URL	This editable field designates the unique identifier for the account, when referencing the account in a URL. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct-sga
Cloud Provider	Select the desired cloud or IaaS (Infrastructure-as-a-Service) provider for your account.
Cloud Account	Select the desired cloud account to use, if there is more than one cloud account for that cloud provider.
Region	Specify the desired datacenter you would like the account to be created in.
Networking	Select Frame-Managed Networking
Network type	Select Private Network with SGA
SGA Version	Select SGA 3.5 to automatically deploy one or more SGA 3.5 VMs or SGA 4 to attach this Frame account to an existing SGA 4 cluster.
Number of SGA instances	If SGA 3.5 is selected and 2 or more SGA instances are requested, Frame will automatically provision a load balancer in front of the SGA VMs. These SGA VMs will run 24x7x365.
Customize VPC Settings	Select this checkbox to specify specific CIDRs for the workload VPC and the SGA VPC (SGA 3.5 only). If you do not enable this feature and specify a CIDR, Frame will set the workload CIDR to a randomized IP address range of 10.{0-255}.0.0/18 and the SGA CIDR is 172.16.0.0/24. If you plan to connect the workload VPC/VNET to another network through a peer, VPN, or other private connection, you need to specify a non-overlapping CIDR (e.g., 10.0.0.0/20, 192.168.0.0/24). The VPC/VNET CIDR can be changed after the Frame account is created under Dashboard, Settings, Networking, as long as there are no customer-provisioned network resources (e.g., peers, VPNs, gateways, etc.) attached to the Frame-provisioned VPC/VNET.
VPC CIDR	Specify the workload VPC/VNET CIDR in CIDR notation. CIDR must be a minimum of /24.
SGA CIDR	If SGA 3.5 is selected, specify the SGA VPC/VNET CIDR in CIDR notation. CIDR must be a minimum of /24.

:::info

SGA Instance types

Types

Frame Platform will provision SGA VM(s) on the following instance/machine types. These VMs will run 24x7 since users need to be able to access the workload VMs at any time.

• AWS: c5.xlarge
• Azure: D4 v3
• GCP: e2-standard-2 (SGA 3), e2-standard-4 (SGA 4)
• IBM: cx3d-4x10 (SGA 4 only)

:::

Customers who wish to create a Frame account on the public cloud infrastructure in an existing network (VPC or VNET) can choose this option. The existing VPC or VNET must comply with the network requirements and architecture as defined in Public Cloud with Private Networking. By default, all workload VMs will only have private IP addresses.

Until the customer configures networking, security groups, and routing to reach these workload VMs, the customer will not be able to access the Sandbox, Utility Servers, or production VMs.

Field/Button	Description
Organization	If account created at the customer level, this field is visible. Select or search for the top-level organization the account will reside under.
Account Name	Frame automatically generates an account name for you, but you can edit this field if desired. The account name will be displayed in the account Dashboard and Launchpad.
Account URL	This editable field designates the unique identifier for the account, when referencing the account in a URL. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct-customer-networking
Cloud Provider	Select the desired cloud or IaaS (Infrastructure-as-a-Service) provider for your account.
Cloud Account	Select the desired cloud account to use, if there is more than one cloud account for that cloud provider.
Region	Specify the desired datacenter you would like the account to be created in.
Networking	Select Customer-Managed Networking.
Virtual Private Network (VPC)	Specify the desired VPC/VNET from the list of the existing VPCs/VNETs in the specified region for the registered public cloud account.
Workload Subnet	Pick the subnet(s) from the list of subnets in the specified VPC or VNET.
Security groups (AWS only)	Pick the security group(s) from the list of security groups for the specified AWS VPC.
Assign public IP addresses to created machines	If you select this option, all newly-provisioned machines in the VNET/VPC will have public IP addresses, in addition to private IP addresses.
Use Streaming Gateway	Select this option and specify the existing SGA 4 cluster that will be attached to this Frame account.

:::info

Azure Infrastructure

While an Azure security group is not required in the above Frame account creation workflow, an Azure security group must be provisioned on the VNET/subnet before Frame account creation. Specific inbound/outbound rules will be dependent on how the Frame traffic is routed, as defined in Public Cloud with Private Networking.

:::

Customers who wish to create a Frame account on the AHV infrastructure must choose this option. The AHV cluster and VLAN configuration comply with the network requirements and architecture as defined in Frame on AHV. All workload VMs will only have private IP addresses.

Field/Button	Description
Organization	If account created at the customer level, this field is visible. Select or search for the top-level organization the account will reside under.
Account Name	Frame automatically generates an account name for you, but you can edit this field if desired. The account name will be displayed in the account Dashboard and Launchpad.
Account URL	This editable field designates the unique identifier for the account, when referencing the account in a URL. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct-ahv
Cloud Provider	Select the desired AHV-based Nutanix Cloud Provider for your account.
Cloud Account	Select the desired cloud account to use, if there is more than one cloud account for that cloud provider.
Region	Specify the desired datacenter or cluster you would like the account to be created in.
Virtual Network	Specify the desired VLAN from the list of the existing VLANs in the registered AHV Cloud Account. With Frame accounts on AHV, the CIDR block is defined in Prism Central/Prism Element and not within Frame.

3. After selecting the Next button, you will be asked to specify the Frame account configuration.

^{* The AWS infrastructure must either be customer-managed (BYO) or Dizzion-provided (Complete customers only). Legacy Frame customers using Frame IaaS are not eligible.}

4. Review the configuration you have specified in the first two steps of the account creation wizard and click Create in the bottom right corner of the window. Once the operation is complete, the new account will populate in the accounts list.

Troubleshooting