The DC Scope general menu is available at the top of the screen. This menu menu can be accessed from the various modules of the solution.
The DC Scope search bar is used to search for all the elements of the of the infrastructure or filter, if the latter is selected. The scope of the search includes: clusters, servers, virtual machines virtual machines, datastores and resource pools.
Filters and views
DC Scope can analyse the entire infrastructure or just a limited part of it. part of the infrastructure. To do this, filters must be created. which are a combination of element selection (selection view) and time view.
The activation of filters is done via your filter.
A data centre hosts a large number of virtual machines. Scanning all the virtual machines in a data centre in one block is therefore a a single block is therefore a difficult and in some cases irrelevant task (clustering of servers irrelevant (grouping servers by cluster, Folder, Tag view, Resource pool or folder, location etc.). Using the selection view, the user specifies the elements he/she to observe. The definition of the elements to be analysed is accessible via the button Selection View. To create a filter, click on the Create View button and follow the instructions of the wizard.
Click on the Create View button and follow the instructions of the the wizard. Note that there are already predefined periodic views: last 30D (last 30 days), last60D, last 180D, last360D.
You can of course create new ones.
Be careful, if you activate a filter with a period view in the past (e.g. March 2019), the architecture analysed will be the existing one on this period (for example you will not see the servers deployed after this date...).
Once the selection and period views are created, you can start creating your start creating your filter. Click on the Filter management menu to view the details of the filters created. By default, a filter All filter is created, which includes the information that DC Scope has collected since its installation and all infrastructure elements. To create a new filter, click on the the create filter button and follow the wizard. the wizard. The wizard will guide you through the creation process, asking you to select the The wizard will guide you through the creation process and ask you to select the Views to include in the filter. Once created, the filter will be available in the list along with the date of creation.
To create a shared filter from the Filter management section Click on the CREATE FILTER button and activate the shared filter option.
Only the root user can share filters with other DCScope users. Only the root user can create, edit or delete a shared filter. A so-called shared filter is visible in the filter list if the scope of items that has been assigned to the user includes the items of the shared filter.
The scope of the user Easyvirt contains servers A and B. The root user creates a shared filter containing server A, in this case the filter will be visible in the filter list of the Easyvirt user.
The root user creates a shared filter containing servers A, B and C, in which case the filter will not be visible in the filter list of the Easyvirt user.
Filters are activated via the Your selection filter button filter (Your filterwhere you will find a list of the filters you you have created.
DC Scope allows you to create filters and automatically track an element. For example, if a server is selected when the filter is created then any VMs created on that server will be automatically added to the automatically added to the filter. However, when the filter is created if some VMs of the server are selected but not all the VMs, then any new VM running on that server will not be added to the filter. This notion of automatic filtering is also valid for servers, clusters and datacenters.
The capacity planning settings allow you to customise the over-provisioning and reservation rates for infrastructure resources. By default, DC Scope applies the over-provisioning rates recommended by VMware, i.e. 4 VCPUs per logical core, 166% of memory capacity and 100% of storage capacity.
Compute / Storage reservation
These parameters allow you to specify a percentage of resources to be reserved, i.e. not used for capacity planning. For example, if you define a "Compute reservation" percentage of 20%, the capacity planning will consider that the processor and memory capacity of the infrastructure is 80%. The use of these parameters can be applied to various operations, such as a BCP/PRA. The available resources displayed in the capacity planning take this parameter into account. The same applies to the estimation of the number of virtual machines that can be created.
Allows you to estimate the number of virtual machines that can be created according to the capacities/uses of your infrastructure but also according to a particular VM template. You can estimate this number according to a template based on the average VM of your infrastructure or according to a template that you have defined yourself. You can define 3 different VM templates (e.g. small-big instance), allowing you to estimate the number of virtual machines according to your own criteria.
You have the possibility to choose the maps you want to display in the dashboard by checking or unchecking them.
You can define the working hours and days of your organisation. Once defined, you will be able to create filters that include only the hours and days your organisation works.
Please keep in mind that changing these settings will reset the databases specific to hours and days worked. Filters already created will provide the information from the day of the change.
A VM can have activity for many reasons, real need or not. Unused VMs almost always have some activity, even if it is very low (antivirus, update, etc.). (antivirus, update, backup, etc.) Therefore it is very difficult to identify the really useless VMs. To solve this To resolve this difficulty, DC Scope® uses the notion of noise, to ensure that no unnecessary VMs are forgotten. This notion of noise is represented by a percentage of points, which are discarded in the VM analysis. The noise can be set : 100%, 99,99%, 99,9%, 99%. (default 99%).
In addition to the noise, the behavioural analysis is performed according to a second parameter, the activity threshold. This defines the activity threshold that a VM must not exceed (default: 10%).
Thus, the coupling of these 2 parameters allows to determine precisely the activity of the VMs.
Graph on demand
In this section, you can define the default counters to display for each resource in the Graph on Demand module.
The "status" menu provides general information on the status of DC Scope, such as the licence, the connection status to vCenter / ESXi, the logs and the ability to upload updates directly from the interface. The colour of the flag indicates the general status:
- green: all is well
- orange: "warning" type alert (e.g. licence expiring)
- red: "critical" alert (e.g. a disconnection from a vCenter / ESXi)
The license validity period and the number of VMs allowed. The coloured dot indicates the status.
Status of connections to instances registered in DC Scope (vCenter/ESXi, vCloud Director). The coloured dot indicates the status: if red or orange, this means that a connection has been lost, and therefore no data recovery has taken place. (classic causes: account password change, IP address change).
Status of the vCenter / ESXi information records in the database. If red, the database does not contain recent data for a particular vCenter/ESXi. This "red" status is normal if you have just installed DC Scope (the hour after the vCenter/ESXi was registered) or if there has been a disconnection from the vCenter/ESXi.
Get DCScope status archive
Allows you to download various logs, especially necessary for support.
Upload DCScope update
Used to upload DC Scope updates.
From this menu, you can access the various DC Scope administration sections; for example, managing connections (VMware vCenter/ESXi, vCloud Director, AWS, Azure) or creating a new user.
User management (root)
By logging in with the rootaccount, the "User management" menu allows you to manage your users, their settings and their access to DC Scope features (groups, roles).
Note: LDAP configuration is carried out from the DC Scope VM administration console, accessible from the VMware console. The information to be entered is the LDAP server address and the group.
The wizard below allows you to create a new user:
- from an LDAP
The creation of a local account requires the following information:
- the user's name,
- the group to which the user belongs,
- the password
Users from AD/OpenLDAP
From LDAP, you can create several users at the same time. The steps are as follows:
- establish a connection to the AD.
- select the people and/or groups of people for whom you wish to create users (Note: creating a DC Scope user for an AD group will allow all members of this AD group to connect to it).
- select the DC Scope group to which the new DC Scope User will belong.
- the new user is created. It will be displayed in the list and will be of type 'ldap'.
By clicking on the 'Edit' link, you can change the user's group membership and password.
By clicking on the 'Delete' link, the user will be deleted.
In DC Scope, a group is an entity which has information shared by all the users in the group:
- an e-mail address,
- a currency (inherited from the root),
- a scope,
- a role
As for a user, you can edit the various information of the group or delete it.
User management (no root)
With an account other than rootthe "User management" menu only allows the modification of the password (if local user) and the group's email address.
The Cost management section allows you to enter the costs relating to the physical server, the fixed cost of virtual machines and the storage spaces (datastore). Only the root user can set the costs.
This is the cost per GB of a datastore. It is a generic cost and can be modified by clicking on the EDIT button.
By selecting the individual cost option, you can then assign a cost for each datastore. In this case the cost per datastore is no longer generic but specific.
In the case of individual cost selection, the QUICK TOOL SELECTION button allows you to select a set of elements and assign a cost to them. The APPLY button is used to save the changes.
The current selection informs you that the storage costs are assigned individually.
Corresponds to the cost of the physical server (ESX). This usually takes into account the cost of purchase, electrical maintenance and the cost of the server itself. The ratio corresponds to the distribution of costs between vcpu and vram assigned to virtual machines. It is defined by default at 40% for the vcpu and 60% for the vram. By changing the ratio, the cost to the vcpu and vram are automatically changed. In the same way, if the vcpu or vram cost is modified then the ratio is automatically modified to guarantee the physical server cost.
The generic cost can be modified by clicking on the EDIT button.
By selecting the individual cost option, you can then assign a cost to each server.
In the case of individual cost selection, the QUICK TOOL SELECTION button allows you to select a set of items and assign a cost to them. The APPLY button allows you to save the changes.
The CONFIRM UPDATE PROCESSING button is used to calculate the new DCScope data.
Corresponds to the fixed cost of a virtual machine. This is generic, modifiable and corresponds to the cost of maintenance, license, human costs, etc... All that is necessary to make a virtual machine function.
Each virtual machine can be assigned a different specific fixed cost by selecting the individual cost option. By modifying the cost of a virtual machine we no longer speak of generic cost but of specific cost.
In the case of individual cost selection, the QUICK TOOL SELECTION button allows you to select a set of items and assign them a cost. The APPLY button allows you to save the changes.
The TAG cost tab allows you to create a tag representing a cost and assign this tag to a set of virtual machines.
- The NEW TAG button allows you to create a tag and enter a cost
- assign the tag to virtual machines
Several tags can be assigned to a virtual machine, in this case the cumulative costs will be reported in the TAG cost section of the VM.
This interface lists the VMware instances (vCenter / ESXi, vCloud Director) and Cloud Providers (AWS, Azure) registered in DC Scope. You can view the information entered and register or unregister an instance.
vSphere Client Plug-in
DC Scope has a plugin which you can deploy within your vCenter (compatible with version 6.5 U2 and above). This plugin allows you to obtain information/analysis for ESXi and VMs directly from your vCenter.
The information available from the plugin is as follows:
- From the ESXi summary view:
* Number of virtual machines total, on, off. * Possible CPU and RAM saturation dates. * Graph of VM count evolution. * Graph of vCPU capacity/allocation. * Graph of RAM capacity/allocation.
- From the VM summary view:
2.1 VM summary sheet:
* VM behaviour (idle, busy, etc...). * Troubleshooting state. * VM cost. * Date of last modification.
2.2 Resizing proposal:
* Resize to vcpu. * Resize to ram.
This is where you manage your license: get your product key, request a license or register your new key.