When increasing a tenant’s compute resources, evaluate if the needed increase can be added to an existing tenant node or scaling out with an additional node is necessary. The maximum resources that can be added to a single tenant node is determined by the cluster settings: Max RAM per machine and Max cores per machine for the cluster to which the tenant node is assigned.
In General, it is best to max out the compute resources assigned to each tenant node before adding an additional node; however, there may be situations where it will be better to balance resources between tenant nodes.
Example:
- A customer needs a total of 64GB RAM, and the max allowed on the cluster is 62GB.
- Rather than max out the first tenant node at 62GB and add a second node at only 2GB, it would be better to equally balance between 2 - each with 32GB RAM, as it would not be practical to run a node with only 2GB.
For additional guidance in planning tenant node resources, contact Support. Instructions below cover adding resources to an existing tenant node and adding another tenant node.
- From the tenant dashboard, click Nodes on the left menu.
- The node list appears. Double-click the desired node.
- The tenant node Dashboard appears.
- Click Edit on the left menu.
- Modify the Cores and/or RAM fields as desired.
- Click Submit.
- From the tenant dashboard, click Nodes on the left menu.
- Click New on the left menu.
- Select the number of Cores to provision to the tenant node.
- Select the amount of RAM to provision to the tenant node (can be specified in Gigabyte or Megabyte) NOTE: The system will always allow assignment of Cores/RAM to a tenant node regardless of how much RAM has already been provisioned; however, the resources must actually be available to power on the tenant node.
- Optionally, a Cluster can be selected on which to run the tenant, or it can be left at --Default -- (specified by System > Settings > Default cluster for tenant nodes).
- Optionally, a Failover cluster can be selected on which to run the tenant if the primary selected cluster is not available. Or it can be left at --Default -- (specified by System > Settings > Default cluster for tenant nodes)
- Setting a Preferred node is not typically recommended for tenant nodes. This is an advanced setting for tenant nodes; setting incorrectly can adversely affect built-in redundancy. Use this setting with care. Consult with Support for additional assistance, if needed.
- Optionally, a Description can be entered to record further information for this tenant node.
- Select desired On Power Loss setting:
- Last State - tenant will only be powered on if it was on at the time of power loss.
- Leave Off - tenant will not be powered on when power is restored (regardless of its state at the time of power loss).
- Power On - tenant will be powered on when power is restored (regardless of its state at the time of power loss).
- Click Submit.
- Navigate to the tenant dashboard.
- Click Add Storage on the left menu.
- Select the desired Tier from the dropdown list.
- Enter the desired amount of storage in the Provisioned field and select the desired unit of measure (B, KB, MB, GB, TB)
- Click Submit to add the provisioned storage.
- Navigate to the tenant dashboard.
- Scroll down to the Storage section.
- Click the Edit button (far right) for the desired tier.
- Change the Provisioned field to the total amount to be provisioned to the tenant. (For example, if the current amount is 50GB and you want to add 25GB, enter the new desired total: 75GB).
- Click Submit to save the change.
Need more Help? Email support@verge.io or call us at (855) 855-8300