Search
Lori MacVittie - Two Different Socks
You are here: DevCentral > Weblogs

posted on Thursday, February 19, 2009 4:55 AM

The focus of cloud and virtualization discussions today revolve primarily around hypervisors, virtual machines, automation, network and application network infrastructure; on the dynamic infrastructure necessary to enable a truly dynamic data center.

In all the hype we’ve lost sight of the impact these changes will have on other critical IT systems such as network systems management (NSM) and application performance management (APM).

You know their names: IBM, CA, Compuware, BMC, HP. There are likely one or more of their systems monitoring and managing applications and systems in your data center right now. They provide alerts, notifications, and the reports IT managers demand on a monthly or weekly basis to prove IT is meeting the service-level agreements around performance and availability made with business stakeholders.

In a truly dynamic data center, one in which resources are shared in order to provide the scalability and capacity needed to meet those service-level agreements, IP addresses are likely to become as mobile as the applications and infrastructure that need them. An application may or may not use the same IP address when it moves from one location to another; an application will use multiple IP addresses when it scales automatically and those IP addresses may or may not be static.

It is already apparent that DHCP will play a larger role in the dynamic data center than it does in a classic data center architecture. DHCP is not often used within the core data center precisely because it is not guaranteed. Oh, you can designate that *this* MAC address is always assigned *that* dynamic IP address, but essentially what you’re doing is creating a static map that is in execution no different than a static bound IP address. And in a dynamic data center, the MAC address is not guaranteed precisely because virtual instances of applications may move from hardware to hardware based on current performance, availability, and capacity needs.

The problem then is that NMS and APM is often tied to IP addresses. Using aging standards like SNMP to monitor infrastructure and utilizing agents installed at the OS or application server layer to collect performance data that is ultimately used to generate those eye-candy charts and reports for management. These systems can also generate dependency maps, tying applications to servers to network segments and their support infrastructure such that if any one dependent component fails, an administrator is notified.

And it’s almost all monitored based on IP address.

When those IP addresses change, as more and more infrastructure is virtualized and applications become more mobile within the data center, the APM and NMS systems will either fail to recognize the change or, more likely, “cry wolf” with alerts and notifications stating an application is down when in truth it is running just fine.

The potential to collect erroneous data is detrimental to the ability of IT to show its value to the business, prove its adherence to agreed upon service-level agreements, and to the ability to accurately forecast growth.

NMS and APM will be affected by the dynamic data center; they will need to alter the basic premise upon which they have always acted: every application and network device and application network infrastructure solution is tied to an IP address.

The bonds between IP address and … everything are slowly being dissolved as we move into an architectural model that abstracts the very network foundations upon which data centers have always been built and then ignores it. While in many cases the bond between a device or application and an IP address will remain, it cannot be assumed to be true.

The days of IP-based management are numbered, necessarily, and while that sounds ominous it is really a blessing in disguise. Perhaps the “silver lining in the cloud”, even. All the monitoring and management that goes on in IT is centered around one thing: the application. How well is it performing, how much bandwidth does it need/is it using, is it available, is it secure, is it running. By forcing the issue of IP address management into the forefront by effectively dismissing IP address as a primary method of identification, the cloud and virtualization have done the IT industry in general a huge favor. The dismissal of IP address as an integral means by which an application is identified, managed, and monitored means there must be another way to do it. One that provides more information, better information, and increased visibility into the behavior and needs of that application.

NMS and APM, like so many other IT systems management and monitoring solutions, will need to adjust the way in which they monitor, correlate, and manage the infrastructure and applications in the new, dynamic data center. They will need to integrate with whatever means is used to orchestrate and manage the ebb and flow of infrastructure and applications within the data center.

The coming network and data center revolution - the move to a dynamic infrastructure and a dynamic data center - will have long-term effects on the systems and applications traditionally used to manage and monitor them. We need to start considering the ramifications now in order to be ready before it becomes an urgent need.

Follow me on Twitter View Lori's profile on SlideShare friendfeedicon_facebook AddThis Feed Button Bookmark and Share


Reblog this post [with Zemanta]


Feedback

2/19/2009 5:46 AM
Gravatar Your talking about IP Address Management (IPAM) where using DHCP and DNS, at a minimum, you can dynamically manage your address space both fixed and static by mapping MAC, IP, DNS name in real time. Vendors like INS, acquired by BT, Infoblox, Bluecat, and Metainfo have been beating this drum for a long time. Looks like the market is starting to go their way.
Mike Fratto
2/19/2009 6:10 AM
Gravatar @Mike,

True. And using something IF-MAP and a separate server you can react to the assignment of an IP address. Problem is I don't think NMS and APM are currently thinking they need to react to these changes. But if they did, they could transition from monitoring/managing a static infrastructure to a dynamic one fairly easily.

That assumes, of course, that IF-MAP is accepted by a wider set of solution providers across the system management stack.

Lori
Lori MacVittie
2/19/2009 6:27 AM
Gravatar You could sustain the legacy platforms for a while by creating a proxy to map between the NMS/APM "known targets" and their functional replacements in the real world. The proxy would either work with remote agents or the apps themselves to control what's going where. As long as it's taking the NMS commercial space to understand application delivery, I am not hopeful they'll figure this out any time soon.
Jason Rahm
2/19/2009 6:46 AM
Gravatar I see. Yeah, I don't think NMS and APM software is as dynamic. But you don't need IF-MAP for IPAM. For an NMS, IF-MAP is redundant as a data source, I think. The NMS want's to be authoritative and so discovers it's own stuff. They could publish to an IF-MAP server. What the NMS systems need to do is ignore the IP address altogether and just use domain names. Historically though, orgs haven't been disciplined in managing there DNS and that needs to change. With the coming of IPv6, I think that will start to happen.
Mike Fratto
2/19/2009 6:49 AM
Gravatar Good point. Who is (or becomes) the authoritative source for where things are. As complicated as IDM and determining authoritative sources and who/what is authorized to change.

But I think you're right, between IPv6 and dynamic environments, DNS management is going to change and become a more critical component of a smoothly operating data center.
Lori MacVittie
3/1/2009 7:52 PM
Gravatar Lori.. I think that some kind of world wide unique id (wwuid) will rise for VMs. Conceivably, this could be a highly structured IP address with PSTN-like assignment rules. I would say there's a decent case for IPv6 in there. A colleague of mind would rather put off IPv6 and just do it with IPv4 (hIPv4).

Regardless of whether it happens with IP, I think wwuid's for VMs are inevitable. When we get to interclouds, etc., the ability to globally identify and track VMs for the entirely of their existences will be important. I want lojack for my VMs. I want to be able to shut them down at command, no matter where they are. I want audit trails for what they are doing, when, and where. Etc.
Aneel
4/27/2009 3:24 AM
Gravatar We
Lori MacVittie

Let Me Know What You Think


Please use the form below if you have any comments, questions, or suggestions.

Title:
 
Name:
 
Email: (so we can show your gravatar)
Website:
Comment: Allowed tags: blockquote, a, strong, em, p, u, strike, super, sub, code
 
Please add 4 and 7 and type the answer here:

Blog Stats

Posts:979
Comments:1685
Stories:0
Trackbacks:583
  

Image Galleries

  

Application Delivery

  

Cloud Computing

  

Random

  

Security

  

Chat Catcher

82,243 Members in 102 Countries and Growing!

Join DevCentral Today!

About DevCentral

DevCentral has been a successful, thriving community for many years. We have always strived to bring you the best technical documentation, discussion forums, blogs, media and much more that we can.

So dive in, get familiar with DevCentral. We hope you like it, we hope it makes your job easier, and lets you get that much more power out of the community. To learn more, make sure to check out the Getting Started section. And if you have any problems, or think something could be easier to use, drop us a line to let us know.

Got It !

We've received your comment and transmitted it directly to DevCentral HQ.

Thanks for taking time to let us know what's on your mind. At DevCentral | Community Matters!

Get In Touch With Us

Have questions, suggestions or just want to get something off your chest?

Use our handy form below to Direct Connect with DevCentral Mission Control.

Send Us Feedback       or