Eye on Blades Blog: Trends in Infrastructure
Get HP BladeSystem news, upcoming event information, technology trends, and product information to stay up to date with what is happening in the world of blades.

The Insight Control Software guys get to strut their stuff at the HP Blades Tech Day (#hpbladesday)

By Chuck Klein


Now it was time for the bloggers to head to the Insight Software lab to see what HP does for managing data centers for power & cooling. John Schmitz, Ute Albert, and Tom Turicchi went over the System Insight Manager software (SIM) all the way up the management stack to Insight Dynamics. This is the software stack that allows system administrators to install, configure, monitor, and plan for BladeSystem chassis in the Datacenter.




Tom then gave a demonstration of how the Data Center Power Control part of Insight Control allows for data center managers to plan, monitor, cap and control the amount of energy and cooling is used by their infrastructure. Tom set up policies and rules to manage events that may happen in a Data Center from utility brown-outs to loss of cooling units. He also went over how you can monitor energy usage for the Data Center all the way down to each blade. This would allow you to better plan for capacity and where to install new blades.


The attendees wanted to know what couldn't be managed as they thought the list would be much shorter than reviewing what the software could do. So Tom went over that it managed only HP servers presently, that scripts could be used to manage or shutdown multi-tiered applications, network devices, and storage. These devices did not have the iLO2 ASIC chip in them and that was a foundational element that needed to be there.


Tom also went over a demo of what could be done to setup the event manager to respond to utility policies and help save companies money. He used an example from PG&E in California. That's all for now.


Integrating BladeSystem Matrix into a Chargeback or Billing system

I got a call last week enquiring how the IaaS APIs of BladeSystem Matrix (Matrix) could be used to integrate with a chargeback or billing system at a customer site. its a snowy day in Boulder and being a fair weather skier I thought I would spend a few moments and put together some examples of how you could do this.


How Matrix calculates a service cost


Matrix service templates are listed in the template catalog, which shows their name, a description of the service template, and an associated service cost. This cost is calculated by adding the individual costs of each of the service elements in the template together. For example, in a service template the service designer specifies costs for each class of server, for each GB of a class of storage, and for each IP address consumed on a class of subnet. The cost of the service is calculated by combining these unit costs with the amount of each type of resource consumed to create a total. The template catalog shows the cost to deploy the template. However, once the service is deployed, the user can choose to add additional storage, or perhaps choose to temporarily release (suspend) a server. When the user adds additional storage, their service cost will increase based on the template unit cost per GB of storage. Similarly when the user chooses to temporarily suspend a server, their service costs reduces, reflecting that they have reduced their resource consumption. I'm showing an example of the cost breakout chart in the Matrix template designer tool.



Linking to a charge back or billing system


The ListServices web service call can be used by an administrative user to return summary information about the services deployed in Matrix. The Web service return includes information on the current resource consumption cost of that service. Let's assume the IaaS provider wants to chargeback to their customers based on a 15 minute usage increment. They could use a single CRON job on their billing system to fetch usage information every 15 minutes, as shown in figure 2 below.



The content of the CRON job is shown in figure 3. Matrix 6.0 includes a handy CLI wrapper which I am going use in this example. The wrapper is written in Java, so I can run it on any machine and use the underlying web services to connect the Matrix environment. In my example I copied the ioexec.jar file from the Program Files/HP/Insight Orchestration/cli directory to my linux machine. You could also use your favorite wsdl2{java,perl,python,c,.net} tool or the wsdl import feature in Operations Orchestration to create something similar.


Here is my outline of the bash script:


 # sample charge back cron job
# Cron runs script every 15 minutes
#
###################################################################
# charge_owner: used to apply incremental charge to owner's account
# Inputs: service_name owner cost cost_units
# Returns: !=0 if owner has no more credit
function charge_owner
{
echo service $1 owner "$2" cost $3 $4
# insert commands to charge customer here!
return 0
}
###################################################################
# credit_denied: called when owner has no more credit on service
# Inputs: service_name owner
function credit_denied
{
echo suspend service $1 of owner $2
# Insert commands to handle over drawn customers here
# ioexec deactive service -s "$1" -c chargeback.conf
return 0
}


####################################################################
# process_chargeback
# Inputs: processes listServices output invoking charge_owner &
#         credit_denied to perform chargeback processing
function process_chargeback
{
while read -r LINE
do
    FIELD=${LINE#*services*.}
    FIELD=${FIELD%%=*}
    ARG="${LINE#*=}"
  
    case "$FIELD"
    in
         name)  service="$ARG";;
         cost.value)    cost="$ARG";;
         cost.units)    units="$ARG";;
         ownerName)     owner="$ARG";
                        charge_owner "$service" "$owner" "$cost" "$units"
                        if
                        then
                            credit_denied "$service" "$owner"  
                        fi;;
    esac
    :
done


}


ioexec list services -o raw -c chargeback.conf | process_chargeback


The script uses the ioexec wrapper to invoke the list Services web service call. I then pipe the results to process_chargeback  to parse the results extracting the service name, current charge rate and charge units, and service owner. The information is passed to the chargeback system via two functions charge_owner and credit_denied. The sample code has a stubbed version of charge_owner, which takes the service name, charge rate, charge units and owner arguments and simply echos them. This routine could be extended to insert the usage information into a database or pass it directly to a charge back system. If the routine returns a non-zero result (indicating an error), then the credit_denied routine is called. This is another stub which, for now, just echos the name of owner and the associated service. This could be extended, as shown, to do other operations - such as invoke the deactivateService web service call to shut down the service when the user has no more credit.


More Complex Scenarios


The example I've given is very simple, but hopefully is enough to get people started on their own integrations. Matrix has additional integration points that can trigger workflows to perform additional actions. An example of one of these triggers is the "Approval" workflow that is used to gate requests for new resource allocation in Matrix. This trigger point could be used to do a credit check on a customer prior to proceeding with a resource deployment operation.


I'd love feedback about the charge back or billing tools people use today, and what kind of out-of-the-box integrations would be most useful.

HP and Microsoft launch new integrated BladeSystem management offering

As HP continues the vision of "Open Systems" for the Adaptive Infrastructure and choice for our partners and customers, we announced an new integrated offering with Microsoft.

In a press release today:

"HP today announced HP Insight Control suite for Microsoft® System Center (HP ICE-SC), the industry’s first integrated management environment to lower infrastructure costs and improve uptime of HP server and Microsoft software environments.

By integrating the server management features of HP ProLiant and HP BladeSystem into Microsoft System Center consoles, administrators can gain increased visibility into, and greater control of, their technology environments. This enhanced visibility into the health of IT systems enables a faster response in the event of server failure, reducing the risk of downtime. By automating server deployments and updates, administrative productivity is also greatly improved.
A crucial part of the HP Adaptive Infrastructure strategy is to provide the strongest management experience for HP ProLiant and BladeSystem servers. The new HP ICE-SC enables administrators to monitor and respond to software and hardware events through the Microsoft System Center consoles. This includes:




  • Server health warnings and prefailure condition alerts with Microsoft System Center Operations Manager (SCOM) 2007;


  • Proactive virtual machine management using Microsoft System Center Virtual Machine Manager (SCVMM) 2008; and


  • Enhanced configuration management via Microsoft System Center Configuration Manager (SCCM) 2007.

HP ICE-SC also provides more than 25 performance and resource optimization tips for Microsoft SCVMM, including recommended actions for host system alerts and events. Greater insight into the relationship between host and virtual machines allows administrators to resolve potential server performance problems to maintain maximum uptime."

Here is the link to the entire press release:
http://www.hp.com/hpinfo/newsroom/press/2009/090428c.html

Designing infrastructure the way IT wants to work

We've been on the Adaptive Infrastructure journey at HP for several years now.  This week we are announcing an important milestone: BladeSystem Matrix.  We've been really thinking a lot about how customers use IT and ways we can optimize IT infrastructure to make it work better for them.  We recognize that infrastructure exists for applications, which exist for the business.  So we've taken a business and application perspective on how an infrastructure ought to operate.


Deploying an application typically requires an IT architect or team of architects to carefully design the entire infrastructure - servers, storage, network, virtual machines - and then hand off the design to a team of people to deploy, which typically takes several weeks.  This length of time is mostly an artifact of the way IT infrastructure is designed.  So we decided to change this with BladeSystem Matrix.  Now an architectural design is saved out as a template - servers, storage, virtual machines, network, server software image.  Then when it is time to provision an application, it's as easy as saying "make it so" - and in a matter of minutes, the Matrix's converged virtualized infrastructure is automatically configured and the application is ready to run.  In other words, the way it ought to be.


BladeSystem Matrix is the culmination of several years work at HP - creating an Adaptive Infrastructure that is simpler to buy, deploy and keep running optimally.  Applications are easier to provision, maintain, and migrate.  We've spent years proving out this architecture, not just in our labs but in real-world environments, with BladeSystem, Virtual Connect, and Insight Software - so we could learn how IT really operates - and more importantly - how it ought to operate.


Some people tell me Matrix's virtualization sounds sort of like a mainframe.  Others say that the portal interface reminds them of cloud IT.  I guess in a way they are all correct.  But unlike those environments, Matrix will run off-the-shelf x86 applications.  So I guess I've decided that Matrix is it's own thing.

Search
Showing results for 
Search instead for 
Do you mean 
Follow Us


About the Author(s)
  • More than 25 years in the IT industry developing and managing marketing programs. Focused in emerging technologies like Virtualization, cloud and big data.
  • I work within EMEA ISS Central team and a launch manager for new products and general communications manager for EMEA ISS specific information.
  • Hello! I am a social media manager for servers, so my posts will be geared towards HP server-related news & info.
  • HP Servers, Converged Infrastructure, Converged Systems and ExpertOne
  • WW responsibility for development of ROI and TCO tools for the entire ISS portfolio. Technical expertise with a financial spin to help IT show the business value of their projects.
  • I am a member of the HP BladeSystem Portfolio Marketing team, so my posts will focus on all things blades and blade infrastructure. Enjoy!
  • Luke Oda is a member of the HP's BCS Marketing team. With a primary focus on marketing programs that support HP's BCS portfolio. His interests include all things mission-critical and the continuing innovation that HP demonstrates across the globe.
  • Global Marketing Manager with 15 years experience in the high-tech industry.
  • Network industry experience for more than 20 years - Data Center, Voice over IP, security, remote access, routing, switching and wireless, with companies such as HP, Cisco, Juniper Networks and Novell.
  • 20 years of marketing experience in semiconductors, networking and servers. Focused on HP BladeSystem networking supporting Virtual Connect, interconnects and network adapters.
  • Greetings! I am on the HP Enterprise Group marketing team. Topics I am interested in include Converged Infrastructure, Converged Systems and Management, and HP BladeSystem.
Labels
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation