Chat now with support
Chat with Support

Foglight Capacity Director 5.7.5 - User Guide

Using Foglight Capacity Director Getting Started Tab Current Capacity Tab Resource Utilization Tab Scenario Modeler Tab Server Purchase Tab Infrastructure Organizations Tab Performance Tuning Tab Changes and DRS Rules Tab Cloud Model Tab Report Tab

Editing a Planned Change

Foglight Capacity Director allows you to edit the existing planned changes, as needed.

The Settings dialog box appears.
NOTE: The Settings dialog box varies from the following change types: Model a Cluster Addition, Model a Host Addition, Add Virtual Machines, Model a Host Decommission, Decommission Virtual Machines, Model a Host Movement, and Move Virtual Machines. For more information, see Adding a Planned Change.
Edit the values as needed, and click Save. For detailed information about the available fields, refer to Adding a Planned Change .

Deleting a Planned Change

Foglight Capacity Director allows you to remove the existing planned changes that you do not want to deploy.

In the Confirm delete planned changes dialog box, click Confirm.




Cloud Model Tab

The Cloud Model view helps you understand costs and risks caused by migrating virtual machine workloads to any MSP, Cloud, or IaaS offering. Simply enter the proposed destinations that are under review, like Azure A2 Small, select the virtual machines that have been designated for a cloud migration and input the level of acceptable performance risk for CPU, Memory, Disk IO and Network. Review the destinations that are to be modeled and click Run Model. The Cloud Model view includes the following elements:

Select Virtual Machines: Lists available virtual machines in the selected virtual center or datacenter, and provides the capability to search VMs as needed.
Performance Risk: Allow to specify the percentage of breaches that customer accepted and helps ensure a balance between costs and performance (currently the default value is 10%, the range should be between 0 and 100). Risk is measured by understanding how often a virtual machine exceeds the proposed destinations available resources. For example, by setting a value of 10% for CPU, the risk algorithm will assess how often a virtual machine exceeds the proposed destination resources and count each breach of the available resources based on historic performance. If the VM, for the selected timeframe, breaches the available resources for more than 10% of the time, then the VM is deemed to not fit and will be excluded from the cloud model due to insufficient CPU resources.
Information icon: Click this icon to pop up the dialog box with details explaining how Cloud Model works.
Cloud Instances pane: Allow to add or edit the hardware specification and unit cost of your proposed IaaS subscriptions, such as Azure, AWS EC2. IaaS subscriptions are supported to import or export as a .CSV file.
Run Model button: Click this button to start the recommendation analysis based on historical performance metrics for the specified values (including selected virtual machines, performance risks, selected Cloud Instances, and the modeling scenario).
Model Outcome pane: Lists migration recommendations and resources fit analysis. In addition, this pane shows migration risks caused by restricted hardware resources, including CPU Demand, Memory Consumed, Disk IOPs, Disk Size, and Unable to Model information.

To access the Cloud Model view:

On the navigation panel, under Dashboards, click Capacity Director.
The Capacity Director dashboard opens.
The Cloud Model view appears at the bottom of the Capacity Director dashboard.

Cloud Instances pane

The Cloud Instance table locates in the middle of the Cloud Model view offers the following menus:

Lists the detailed information about all Cloud instances that are available in the selected vCenter or datacenter.

Name. The provider name of the Cloud instance.
Tier. The name of tier.
Instance Type. The type of Cloud instance.
VMs to Migrate. The number of VMs that can be migrated to the Cloud. This value is not available until you click Run Model and get analysis result.
Total Cost. The total cost associated with VM migration. This value is not available until you click Run Model and get analysis result.
Unit Cost. The cost per unit.
CPU Cores. The number of CPU cores.
CPU Speed. The CPU speed.
Memory. The memory size.
Disk Size. The size of disk.
IO Rate(IOPs). The measurement of input/output performance that is used to characterize computer storage devices.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating