Welcome!

If everyone is thinking the same, someone isn't thinking

Lori MacVittie

Subscribe to Lori MacVittie: eMailAlertsEmail Alerts
Get Lori MacVittie via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: DevOps Journal

DevOpsJournal: Blog Feed Post

F5 Friday: A Network Heatwave That’s Good For Operations

f5friday

The grab bag of awesome that is network-side scripting is, in general, often overlooked. Generally speaking “network gear” isn’t flexible, nor is it adaptable, and it certainly isn’t extensible. But when you put network-side scripting into the mix, suddenly what was inflexible and static becomes extensible and dynamic. In many cases if you’ve ever said “I wish that thing could do X” well, in the case of application delivery it probably can – you just have to learn how.

The how, in the case of F5, is iRules.

iRules is network-side scripting, so it’s executing “in the network” as it were, as data is traversing from client to server and server to client. iRules lets you intercept data (it’s event-driven) and then, well, what do you want to do to it? You can transform it, apply conditional policies, log it, search it, reject it. Being network-side means you have context, and with context you can do a lot of application, location, and client-specific “things” to data and requests and sessions. Being “in the network” means you have access to the full network stack. If you need IP header information, you can get that. If you need  image application-specific information from within the request or response, you can get that. The entire stack is available to inspect and can ultimately be used to instruct BIG-IP.

iRules figures prominently into F5’s vision of cloud computing as one component of the dynamic control plane necessary to realize the benefits of cloud computing and virtualization. It figures prominently into agile operations and the ability to respond rapidly to datacenter events, and it’s integral to emerging switching and routing architectures based on content and context, such as message-based load balancing and content-based routing. 

I don’t often get a chance to cook up iRules myself any more so those who do – and are masters at it – make me just a bit jealous. And it’d be hard to find someone in our kitchen that makes me greener than DevCentral’s own Colin Walker.

He’s done it again, and I can’t say enough good things about this solution. Not only is it hot (pun intended) it’s highly applicable to a variety of uses that go beyond just generating eye-candy for operations. What makes it really interesting is the use of an external service to generate a dynamic view of real-time operations. Colin is leveraging Google’s charting API and relying on the confidence of GeoLocation data based on our integration with Quova to enable a real-time visual display of the locations from which HTTP requests are being received by a BIG-IP. It’s dynamic integration, it’s Infrastructure 2.0, it’s devops, it’s just … cool.


BUT “COOL” ISN’T ON THE LIST OF ACCEPTABLE BUSINESS JUSTIFICATIONS for TECHNOLOGY

Now you might thinking "Lori, that’s cool but what practical use does this have?”

Let’s consider for a moment… real-time business decisions. When California lights up because a high volume of customers are interested in X product, perhaps it’s worth injecting special promo codes just for them to encourage more purchases. And yes, using iRules you can get that kind of data – whether by extracting from a URI or via the ability to inspect the application data itself. Consider security implications – that extra traffic coming from a location you generally don’t see lit up might be an attack, or indicative of bot activity. Consider optimization and acceleration. Because iRules is context-aware, you can not only see the requests but specific data about them, like round-trip times and network bandwidth. You might dynamically apply acceleration policies based on sudden increases in latency either automatically based on the collected data or manually because you’ve added that label to the chart via Google’s API and you can see what conditions look like out there. 

Because it’s displaying data in real time, it enables agile operations which empowers not only IT but the business to make decisions that can turn a negative situation positive, or a positive situation even, well, positiver.

You can read about the full solution – including the iRules script – in this tech tip from Colin. And of course the iRules wiki here on DevCentral is an invaluable resource for exploring what you can do with network-side scripting.


Related blogs & articles:

Follow me on Twitter    View Lori's profile on SlideShare  friendfeed icon_facebook

AddThis Feed Button Bookmark and Share

Read the original blog entry...

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.