Create Accounts

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

  • With an AHV, AWS, Azure, or GCP (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.

Attention

Before creating a Frame account, be sure to review and understand the network configuration requirements discussed in further detail in Network Configuration Requirements.

Infrastructure

Public Cloud

When creating a Frame account in public cloud, the Customer or Organization Administrator may choose from one of four different network deployments. Account creation instructions for each type of network deployment 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. rame 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 ontaining the Frame account workload VMs.

Note

Administrators creating new accounts with Frame base images may find that account creation takes longer when a new base image is available since the updated image needs to be applied.

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. Frame on AHV

Creating New Frame Accounts

  1. Customer/Organization Administrators can create new accounts by navigating to the Admin page and selecting the “Accounts” page listed on the left side of the console.

    ../../_images/accountslist.png
  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.

    ../../_images/createaccount0.png

    Organization

    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 of the URL for users to access the login page. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct123

    Cloud Provider

    Select the desired cloud or IaaS (Infrastructure-as-a-Service) provider for your account.

    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

    For Frame networking, select this checkbox to specify a specific VPC/VNET CIDR. This is important to ensure you do not have overlapping CIDRs, if you plan to connect this network to another network through a peer, VPN, or other private connection. Be sure to specify the value in CIDR notation (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-provsioned network resources (e.g., peers, VPNs, gateways, etc.) attached to the Frame-provisioned VPC/VNET.

    CIDR

    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.

    Attention

    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.

    ../../_images/createaccount0_private.png

    Organization

    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 of the URL for users to access the login page. 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.

    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

    The Customer or Organization Administrator can specify a specific VPC/VNET CIDR in CIDR notation by selecting Customize VPC settings. This is important to ensure you do not have overlapping CIDRs, if you plan to connect this network to another network through a peer, VPN, or other private connection. Be sure to specify the value in CIDR notation (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-provsioned network resources (e.g., peers, VPNs, gateways, etc.) attached to the Frame-provisioned VPC/VNET.

    CIDR

    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.

    ../../_images/createaccount0_private_sga.png

    Organization

    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 andLaunchpad.

    Account URL

    This editable field designates the unique identifier of the URL for users to access the login page. 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.

    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.

    Number of SGA instances

    If 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.

    VPC CIDR

    Specify the workload VPC/VNET CIDR in CIDR notation. CIDR must be a minimum of /24.

    SGA CIDR

    Specify the SGA VPC/VNET CIDR in CIDR notation. CIDR must be a minimum of /24.

    SGA Instance 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-4

    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. All workload VMs will only have private IP addresses.

    Attention

    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.

    ../../_images/createaccount0_CM.png

    Organization

    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 andLaunchpad.

    Account URL

    This editable field designates the unique identifier of the URL for users to access the login page. The format for the string referenced above would appear as: https://console.nutanix.com/frame/customer/org/test-acct-custom

    Cloud Provider

    Select the desired cloud or IaaS (Infrastructure-as-a-Service) provider for your account.

    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 registered public cloud account.

    Workload Subnet

    Pick the subnet(s) from the list of subnets in the specified VPC or VNET within the registered public cloud account.

    Security groups (AWS)

    Pick the security group(s) from the list of security groups in the registered AWS cloud account.

    Private Mode

    Keep this box checked to ensure that all newly-provisioned machines in the VNET/VPC specified will not have public IPs.

    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.

    ../../_images/createaccount0_ahv.png

    Organization

    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 of the URL for users to access the login page. 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 Nutanix Cloud Provider for your account.

    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.

    ../../_images/createaccount1.png

    Frame/BYO base image

    If you have already configured your organization or customer entity with a BYO base image, you can select the “Bring your own base image” radio buttonand use your custom base image here. Otherwise, select Use Frame base image.

    Base image family

    Select the base server type/version (AMI) for the account. The options for image family vary depending on the cloud provider.

    Instance type

    Select the system type of the Sandbox upon account creation. The system type can be modified at a later time from the Dashboard of the account.

    Disk size

    Use the slider or the editable field next to it to specify the initial Sandbox disk capacity upon account creation. We recommend you start with the smallest disk sizesince you can always increase the Sandbox disk size in the Dashboard.

    Initial capacity

    Use the slider to specify the number of workload VMs you would like provisioned upon account creation. You can adjust capacity settings any timeafter account creation.

    Persistent Desktop

    This toggle will enable “Persistent Desktops” for your account. If you wish to deliver non-persistent desktops or individual applications to your users, do not select the Persistent Desktop option.

  1. 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.

    ../../_images/createaccount2.png

Troubleshooting

When creating new accounts, the Frame platform automatically provisions new resources on the underlying infrastructure of your cloud account. It is important to understand this process in order to effectively debug issues such as these: