Skip to main content

VKernel Creates Chargeback Calculator and Methodology to Help Organizations Solve the Chargeback Challenge in a Virtualized Datacenter

In a virtual datacenter where numerous departments utilize shared resources many organizations are facing the challenge of figuring out what rate to charge users for memory, CPU, storage and network. Also challenging is how to recover costs for other expenses such as administrative fees, software licensing and cooling costs. While most organizations agree that utility based chargeback is the way to go help is desperately needed. VKernel has "cracked the code" and created a chargeback calculator and methodology to solve the chargeback challenge.
The chargeback calculator takes into consideration many variables including; ESX hosts, storage and network devices, all associated costs, number of user departments/cost centers, who is using the resource, profit margins (if needed) and cost recovery timeframe. Automatically, the calculator outputs the rates an organization should be charging per day for memory, CPU, storage and network.
The calculator is designed to be used on an ongoing basis. As changes to an organizations’ infrastructure occur the calculator rolls that information into the existing formula and recalculates the rates.


Go to V-Kernel!
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more