Download
1 / 30
300 likes | 432 Vues
Chargeback in the Virtual World. Singapore, Q1 2013. Chargeback changes in the virtual world . It’s a shared Infrastructure. Apps Team or “Business” no longer own the infrastructure. Why should they pay for the “entire box” when they only have a slice?
E N D
Chargebackin the Virtual World • Singapore, Q1 2013
Chargeback changes in the virtual world • It’s a shared Infrastructure. • Apps Team or “Business” no longer own the infrastructure. • Why should they pay for the “entire box” when they only have a slice? • Bespoke system to standardized services • Emerging of 2-tier “Infrastructure” • VM level • Owned by Apps team. • Infra level. • Compute, Storage, Network, Security, Datacenter • Done by DC Infra team. • Clear SLA and boundary needs to be defined. • It is not just technical • It is also cultural, social, political, or whatever you want to label it.
Approach Decide what to charge Work out your cost Configure Chargeback You decide what to charge first, so when you work out your cost, you can allocate or classify it to the cost model.
Guideline • You want to keep the model simple • Actual utilisation can result in arguments • Certain areas such as Network utilisation and Storage IOPS are difficult item for financial management. • You want to encourage the right behaviour • Avoid Large VM • 1 VM, 1 OS, 1 App, 1 Instance model • Scale Out, not Scale Up • Right size, not oversized • This means charge will go up as VM gets larger. • Avoid Unique VM • Standards, not bespoke • Avoid Idle VM, as they still incur management cost. • Fee for VM creation • Fee for VM even though it’s not running.
What to charge This is a sample model. Your model might differ
Sample Cost Model • Define your goal • E.g. Provide a shared platform for 500 VM, growing at 10%/year, with DR, for the next 3 years. • Architect the solution • Leverage your VMware/Partner SE & PSO & TAM • Translate #VM into vCPU, vRAM, vDisk • You are not charging per VM, but per vCPU, vRAM and vDisk • Below is a sample example. • Year 1 500 VM = 1000 vCPU, 5000 GB vRAM, 10 TB vDisk • Year 2 +50 VM = 100 vCPU, 500 GB vRAM, 1 TB vDisk • Year 3 +60 VM = 120 vCPU, 600 GB vRAM, 2 TB vDisk • Define the hardware & software requirements • What you need on Year 1, Year 2, Year 3. • Server, Storage, Network, Guest OS, etc
Work out your Cost per Cost Bucket • Work out what you need and your Total Cost • Server: • Year 1: 50 ESX (2 x 10 cores, 128 GB RAM) Total Cost is $1M • Year 2: +5 ESX. Total is 55 ESXi host. • Year 3: +6 ESX • Storage: • Year 1: 10 TB Total Cost is $1M • Year 2: +1 TB. Total 11 TB • Year 3: +2 TB. Total 13 TB • Other costs • Year 1: Total Cost is $1M • Year 2 • Year 3
Sample Cost (Year 1 only) I’ve rounded the final numbers as users need to see a simple number. No CPU or RAM oversubscribed in this model to keep the formula simple. You should do ~1.5x. At 10:1 consolidation ratio, it has buffer for HA, FT, SRM. The model has buffer for IT VMs and IT cluster.
Sample Cost (Year 1 - 3) I’ve rounded the final numbers as users need to see a simple number. Year 2 and 3 costs include maintenance (S&S) of items bought in previous year.
Cost Comparison If you spread your charges (but not your cost) over 3 years, you will lose money in Year 1. If you charge all capital expense on Year 1, it will be high, and you will make too much profit in Year 2. That’s a business call you need to discuss with Finance.
Discussion Point What models will you adopt? How will you charge?
vCenter Chargeback: Configuration • Steps to implement the previous model • Configure Hierarchy to follow the Folder hierarchy • Create a Cost Model • Choose the Billing Policy “Fixed Cost and vCPU Cost and Memory Size” • Enter the Base Rate you work out earlier • Create a Fixed Cost • Map the Cost Model + Fixed Cost to your hierarchy • Schedule a report. • Make it monthly. • That’s it!
Generate Report Wait at least 24 hours to get 1 day worth of data
