Welcome to Dell, EMC Storage Resource Manager.
Use Cases Demo Series, Chargeback Reporting.
Reference Dell Knowledge Article # 183385.
This video will provide an overview of SRM
brief demonstration of chargeback reporting
and additional resources for further reading.
SRM is Dell EMC’s on-prem Storage Resource Management Solution
for heterogeneous compute
network and storage environments, both physical and virtual.
It provides visibility into the physical
and virtual relationships to ensure consistent service levels.
SRM key use cases are capacity planning, performance troubleshooting
configuration compliance
chargeback reporting, and a workload analysis.
We will now focus on chargeback reporting.
With SRM chargeback reporting
we can charge for total storage consumption
of an application
charge for storage based on storage type, which can be block, file, object or cloud.
In case of a block storage, charge per host
hypervisor and virtual machine.
And for all of the mentioned, charge per service level.
In case of a block storage, cost is calculated per LUN capacity
and is configurable within each SLA tier.
It requires solution pack for block chargeback.
For file storage
there is a single SLA tier called NAS
with configurable cost which is calculated per file system and quota.
Object and cloud storage cost is calculated per bucket
and is collected from array as a metric.
Object Storage requires solution pack for Dell
EMC ECS, Atmos and Centera
while cloud storage requires solution pack for Amazon S3.
Before we move to a demo
let’s see use case with application chargeback
on a block storage.
The volume on the Array #1 is mapped to application cluster
and it is considered as a primary capacity.
There are two local replica capacities on Array #1
which are mapped to development and backup application servers
as well as remote replica capacity on Array #2.
Some of these capacities is replica capacity.
Total capacity that is considered for application cluster
is computed as a sum of primary and replica capacity.
The block chargeback computations are performed automatically
within the SRM component called Chargeback Processor.
It runs once per day
and generates chargeback metrics per host
hypervisor and virtual machine.
Metrics include primary and total capacities, used and presented.
Let’s now see SRM chargeback reporting demonstrated.
Chargeback reports are located under Operations Report node.
First four report types are related to block chargeback.
The rest are object in file.
Let’s see chargeback by group report
which gives capacity per group of devices and per SLA.
Group creation is done within block chargeback grouping
and admin UI where besides defaults groups for hypervisor physical hosts
and virtual machines, we can set custom groups.
Service levels are defined for LUNs within service level by LUNs
where each SLA is defined by its unit cost
performance threshold values and set of rules.
Let’s go back to chargeback by group report.
It has four sub reports
primary used and presented, and total used and presented.
Select all VM guests group for primary used capacity report.
It has capacity of 35 TB
spread over five SLAs
and its total cost, for single virtual machine.
We see its SLA cost in primary used capacity
which can be written on LUNs and on VMDK files on DataStore.
Navigate to VMs topology view to see its general information
such as Hostname, OS, Memory, CPUs, Hypervisor DataStore Fabricant Array.
Capacity report is what we need for VMs chargeback.
2 TB is primary used capacity written to LUNs
into virtual disks on Datastore.
2.3 TB is primary presented capacity of LUNs
and virtual disks to host.
Total used and presented capacities
add snapshot and log files to virtual disk capacities.
We are now on file chargeback by group report
which shows service level chargeable capacities for all file shares
that is quotas and file systems per components group.
Group creation is done within file chargeback grouping and admin UI
where besides default groups for file-based storage
we can set custom made groups.
For example, Isilon, which is defined by set of rules.
Service level is defined within service level by file share
where default NAS SLAs is defined by set of rules and unit cost.
Let’s see object chargeback report.
It has four subreports.
Chargeback by namespace, top ten namespaces by cost
cost over time and chargeback by service level.
Now, check single namespace with its total cost of $292
downloaded and uploaded volume of data
number of objects, 3.5 million and capacity per service level.
From the namespace, drill down to its buckets
where we have variety of metrics
such as used capacity, number of objects per bucket
data downloaded, uploaded and cost.
There are several properties such as Virtual Data Center
Owner, Replication Group and Service Level.
We saw in previous reports
that namespace and bucket chargeback values
are reported per service level.
Here is where we create them.
For example, SLA name remote protected is defined by name, cost per gigabyte
costs per download, upload gigabyte
and set of rules based on bucket part type.
Let's see chargeback by service level
for selected namespace with associated used capacity and costs.
Now, check top ten buckets by cost
for selected namespace.
Return to top-level reports
and let’s check top ten namespaces by cost then cost over time, where upload/download
then cost over time, where upload/download
used in total capacity costs are plotted
and chargeback by service level report
gives costs per service level across all namespaces.
This is the end of the video.
For more SRM videos, white papers and other documents
please consult following resources.
Thank you for watching.