Get Virtualized

521 views
443 views

Published on

Tomorrow, and tomorrow, and tomorrow,
Creeps in this petty pace from day to day,
To the last syllable of recorded time;
And all our yesterdays have lighted fools
The way to dusty death. Out, out, brief candle!
Life's but a walking shadow, a poor player,
That struts and frets his hour upon the stage,
And then is heard no more. It is a tale
Told by an idiot, full of sound and fury,
Signifying nothing.

Middleware and virtualization. Now with added Shakespeare! Read on...

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
521
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Tomorrow, and tomorrow, and tomorrow, Creeps in this petty pace from day to day, To the last syllable of recorded time; And all our yesterdays have lighted fools The way to dusty death. Out, out, brief candle! Life's but a walking shadow, a poor player, That struts and frets his hour upon the stage, And then is heard no more. It is a tale Told by an idiot, full of sound and fury, Signifying nothing. So we’re interested in computing cycles - centralised computing, distributed computing, super-distributed computing... and I also happen to interested in my fellow countryman Shakespeare. Who 306 years ago wrote that life itself is, "a poor player, that struts and frets his hour upon the stage, And then is heard no more." To paraphrase the great bard... Every dog has it's day, in the future everyone will be famous for 15 minutes, and, then applying that to the current trends towards mash-ups and enterprise social computing, and situational applications where we’re talking about bringing up an application, using it to solve a problem and then throwing it away... Was Shakespeare the first SOA architect? Did he forsee each application having it’s 15 minutes of fame – strutting and fretting upon the stage– but then he also knew that nothing gets thrown away in the world of enterprise software. In the world of legacy software. Do you have applications running in your shop that you wish that you didn’t? In fact, I think Shakespeare knew a lot about the IT industry, for here I am, today’s idiot full of sound and fury. My name is Sean Boiling… So let’s start with a definition. Virtualization is a technique for abstracting the physical characteristics of computing resources in order to more easily leverage hardware systems, applications, operating systems, networks, graphics, data or storage so they can be repurposed based on customer need. And why is that important?
  • Well it’s important because of this… SOA, and with thanks to ZapThink, the lego block analogy to explain SOA. Service Orientated Architecture is a business approach for leveraging IT capabilities as business resources to meet the changing needs of the business in agile, cost-effective ways, and is thus critically relevant to today's business. But taking all the admittedly technical benefits of SOA, including loose coupling, composability, and reusability, and placing them in a sufficiently explanatory business context has always been a difficult challenge. As with any analogy, the parallels only go so far, but with Lego blocks, there are four positive salient characteristics -- and four negative ones -- that serve to illustrate both the power as well as the drawbacks of SOA to any audience. The Four Advantages of Lego Blocks The four characteristics of Lego blocks that are most appropriate for illustrating the strengths of business Services in the context of SOA are the following: * Lego blocks are interoperable. Yes, it's all about the bumps. Because the blocks all have standard bumps, any Lego block will fit into any other Lego block. Standards-based interfaces are the secret to the blocks' interoperability -- or to be more precise, it's the Service contract that matters. After all, we've had decades of standards-based interfaces of various sorts and that hasn't gotten us that close to the Lego vision. * Lego blocks are unbreakable. When was the last time you saw half a Lego block? Even the most rambunctious three-year-old can't damage the things. Clearly, the business would appreciate it if IT could deliver capabilities that were as unbreakable as Lego blocks. Now, it's not that Lego blocks are truly unbreakable, but rather, that the Lego Group designed them with significant robustness in mind. And that's what we want from SOA -- a design for robustness. The key is that it's the architecture of the Lego block that makes it strong enough for a three-year-old, just as IT needs to function in a way that's robust enough for business. * Lego blocks are composable. One Lego block by itself is no fun at all. The whole point to the toy is taking many of them and assembling them to meet the need of the day, just as the business wishes to compose Services into applications that implement business processes in a flexible way. * Lego blocks are reusable. On the one hand, you can build one structure with your blocks, then disassemble it and reuse the blocks to build something else. Another way of looking at reusability is to consider the colors of the blocks. If you consider, say, all red blocks to represent customer information Services, for example, then you can easily use red blocks in many different structures, just as you can compose customer information Services into many business processes. There's little the business wants from IT that doesn't fall under the four characteristics above. The business cares little for how the blocks are constructed or why they do what they do. The business simply wants composable, reusable, interoperable, unbreakable components they can leverage in flexible ways to meet their changing needs. The Downside of Lego Blocks… As with any good analogy, the parallels extend beyond the positives, and also help highlight some of the limitations of SOA. Here are four examples: * Lego blocks' strengths pose business challenges for their manufacturer. The blocks' unbreakability, reusability, and composability have actually caused their own share of problems, as well. Once a family buys enough Lego blocks for thei r first kid, after all, they're usually set for life. As a result, sales of Lego blocks have waned over time, leading the company to roll out special kits with the intention of having children assemble a castle or a spaceship or what have you once, and set it on a shelf. In other words, the vendor talks about interoperability and reusability, but really wants to lock you in so that you have to keep buying products from them. Sound familiar? * Structures built from Lego blocks are only so strong. If you compare Lego blocks to, say, Meccano. Meccano was harder to work with and less flexible in its capabilities, but once you had that bridge or skyscraper constructed, it wasn't going anywhere, and you could virtually climb on the thing. The larger you build a structure with Lego blocks, however, the more fragile it gets. In other words, loose coupling comes at a price. While tightly coupled interfaces reduce flexibility and reusability, they also can increase efficiency. Loose coupling, on the other hand, can limit the efficiency of the implementation. * Lego blocks are interoperable with each other, but not with other kinds of toys. This characteristic of Lego blocks might provide a warning about the pros and cons of building on a single platform, but the more interesting story here is that loose coupling occurs on multiple levels. You can have loosely coupled interactions on the wire and message protocol levels, and still be tightly coupled on the semantic level. True loose coupling is far more complex and subtle than bumps on Lego blocks! * Lego blocks are for children, but children couldn't build Legoland. All parents think the structures their little ones build with their Lego blocks are the best in the world, of course, but to build the large structures you find in the Legoland theme park, you need architecture. Without architecture, a box of Lego blocks is nothing more than a box of toys, and without architecture, a bunch of Services is little more than, well, a bunch of Services. Only with a broad design and the discipline to follow it can companies expect to get the full value out of their Services over time.
  • To paraphrase another great thinker and orator from hundreds of years ago
  • “ There is no why, there is do or not do”. Now Yoda actually said try, not why, but I’ll happily change a word for my purposes. There is no why to virtualisation. It’s a good idea. Getting more out of our limited resources is a good thing. Do you hear that noise in the background? That’s virtualization coming, get on or get out of the way! SOA has given you these reusable components that you can mash-up and use them and reuse them in new and flexible ways, and you need an infrastructure to support that. A virtualized infrastructure. A fluid architecture, needs a fluid infrastructure.
  • A chain is only as strong as it's weakest link... how do SOA and Virtualisation play together? Here I am and I’ve made my new accounting application <CLICK>, it's SOA enabled, and it's so great that people - other developers - want to reuse it. But, that application lives on a piece of physical hardware somewhere so my application is limited by that hardware in how far it can scale out. I built my app for 1000 users but as it gets reused by others I've made myself a problem - these services aren't just made from pixie dust that you can snatch out of the ether - they are physical apps that live on a server somewhere. A fluid architecture needs a fluid infrastructure...
  • As my service gets more widely used in the traditional world without virtualization <CLICK> response time goes up and there’s all this server utilisation unused… Drop in a Hypervisor <CLICK> and as my user traffic increases response time remains acceptable and I’m able to make use of that unused and under used capacity.
  • It's a little known fact that applications running virtualised run slower than if they were running natively. There's another layer of abstraction, another layer of delay. We don't think our customers would go for this – it’s difficult for us to say here’s all this efficiency oh and by the way are you willing to take a 20% performance hit on your applications? So we've invested in getting Java applications to be as high performance as possible in the virtual environment...
  • Efficiency wise we said that VMWare has done a great job in getting server utilisation up from 6%, 7% to 20, 25%... can we do better? Is there a way of increasing that, making the most of the applications themselves. And then from a management and maintenance point of view you’ve got these OS stacks with a full OS and a full JVM and a full application server and a full application in every single container and the maintenance and management of that is pretty tough… So you add a hypervisor and that’s great you get a layer of abstraction and shoring of resources and pooling around the hardware… but what you really want to do is you want to turn this thing into an appliance, and make the infrastructure as fluid as possible, treating these things as appliances that you can switch on and off as easy as your toaster.
  • So what did we do... We announced this thing called Liquid VM. We looked at the environment and saw that the Hypervisor does a lot of thing that an OS does, so can we stretch our Java Virtual Machine to run directly on the Hypervisor without an OS and what would that do for us? Well in the traditional world the OS and the JVM fight for the same resources... when an app is running out of memory the OS finds out about it and starts passing stuff off to cache, then the JVM finds out about it and immediately wants to do a garbage collection... it's like two guys standing with their backs to each other digging a hole and throwing mud into each others hole. You’ll get there in the end, you’ll dig your hole but it’s harder than it should be because you’re fighting against each other the whole time. And then performance wise, can we remove one of these layers of abstraction? So, we came up with Liquid VM - it's basically the BEA JRockit Virtual Machine with extensions and it runs directly in the Hypervisor - no need for an OS. And this does a couple of things - helps with performance, and gets us some efficiency back 'cause we've got rid of the OS and got rid of that other guy digging a hole behind us, really squeezing more into those boxes, doubling the workload that you can handle. And then what we did was take Liquid VM and WLS and certified them together to create WLS-VE. Creating that virtual appliance, with none of the management and administration overhead that you would otherwise have.
  • So let's have a look
  • These are the results of some lab tests we did that the CEO of VMWare - Diane Green - is using in her presentations. <<CLICK>> This is an industry standard Java SpecJBB test on 8core Itanium hardware, same test, same machine, just different OS and virtualisation approach. 1 core, 2 core etc... all good... we’re a little bit ahead and we’re happy with that. Then we get to 5 cores… because LiquidVM is basically a single purpose OS we still grow… because RedHat is a multi tenant OS once they get up past 4 cores they have to start swapping like crazy to satisfy all the cores and requirements on the box – we don’t. You think maybe that they’ll run flat from there but sadly not, they went down we went up. So, double the efficiency out of the box, if you were getting 40% you can now get 80%, if you were getting 60%... no you can’t get 120%, but you get the idea, you can see the linear scalability, and performance improved, we can run an app 40% faster in this way than virtualised in the standard way... and we're aiming to prove now that you can run an app faster in Liquid VM than you can natively. And this is completely unique to BEA. Every other vendor working around virtualisation is looking at management under virtualisation they're not looking at efficiency - we are all about providing that rock solid, yet fluid, application infrastructure.
  • But we've not ignored management, we’ve got the engine, Liquid VM and WLS-VE, we wanted to make sure that we also gave you a product to mange administer and maintain that engine so you could manage QOS, SLA’s etc… we've got Liquid Operations Control that gives you management, administration and SLA alerts etc… across the infrastructure.
  • You take an application, you wrap an SLA around it and then you throw your pixie dust into the cloud and hope everything happens – well no, what LOC does is that it automatically identified a breach of the SLA and will shift resources to fix it. So the benefits are: Efficiency - higher performance, cost reduction, better utilisation. Simplicity - SOA means that you don't know what your load is going to be when you sprinkle that pixie dust over your applications. You need a virtual infrastructure that is firstly, more efficient, and secondly you can stand up and switch on as easy as toasting a slice of bread. Control, being able to manage and monitor the virtual instance and their clustering, caching etc...
  • So where are we with this stuff today? I’m always keen to learn from other areas, other industries, to draw parallels and lessons from what has happened elsewhere. So I took how we get news, how we look at pictures and how we listen to popular music and compared that to where we are in computing for the enterprise with SOA, Web 2,0 and Virtualisation… News… cave drawing, someone is chipping away in their cave and they cut their finger, wipe it on the wall and start painting. But if you want to know the story of today’s hunt or weather then you have to go there to see it. Thousands of years later a monk wanders into the cave and takes a carving of what’s there, takes it back to the monastery for the other monks to see – yes a wider audience but you still have to go there. Some sort of mobility, tapestries, then printing and the first newspaper, now we’re getting somewhere, websites and then the evil point cast. Remember this? A screen saver that updated with live news (and ads) over the internet as the day went on… banned by most corporates because of the masses of bandwidth it consumed. But this was a turning point, it showed us that you could mash things up, compose an application form many services. And then we’ve had iterations from this, My Yahoo and now into something like Digg, really delivering participation. Taking the media away from the physical, virtualising it and allowing the consumer to control it at the front end.
  • If we do the same walk for images… we start in the cave again, then painting, black and white photos, colour photo, a photo album – what’s a photo album if it’s not a mash-up, a composite application made up of a book and my photo’s, but it’s still tied to the media… then this innovation comes along around jpegs and the internet, mosaic browser, and then freeing consumption from the physical media, I’ve got flickr and I can do what I like.
  • Same for popular music… pop started with The Beatles in the Cavern Club in Liverpool… but just like the cave drawing you had to go there to see them... radio, vinyl, 8-track – anyone have one of these? Mix tape… again, what’s a mix tape? It’s a mash-up, it’s the same as the photo album… it’s the blank cassette tape and my choice of what I load on to that tape, and it’s exciting ‘cause it’s personalized and dynamic and if you’re of a certain age you had one given to you or you made one for a friend and you might still have one in the spare room or in the garage in that pile of stuff you’ve been meaning to clean out for years… by the way, if you do have one, throw it out. It’s rubbish, the media is useless and you probably don’t even have a way of playing it anymore. And then innovation, MP3 compression, napster, iTunes. We’ve released the experience/the consumption from the physical media it was delivered on. LastFM and Pandora. Pandora is an automated music recommendation and Internet radio service created by the Music Genome Project. Users enter a song or artist that they enjoy, and the service responds by playing selections that are musically similar. Users provide feedback on the individual song choices — approval or disapproval — which Pandora takes into account for future selections. And it matches across 4oo musical attributes to come up with a choice, such as rhythm syncopation, key tonality, vocal harmonies and displayed instrumental proficiency.
  • Now where are we… mainframe, desktop, portability, distributed computing, SOA, Web 2.0… Now it gets interesting. If you level this… I think we’re here. We’re pre-napster, we’re at the photo album, point cast stage. We’ve created this innovation around virtualization, dual core, multi core, Web 2.0 & Enterprise Social Computing and now we have the opportunity to really unlock it, really unleash the power that all this innovation gives you in how you deliver applications to run your business.
  • So released from location, push for mobility, composition, released from the medium and then virtualized and explosive growth. And then the other stuff in red is the stuff we’re thinking about… so we’re here with SOA and Web 2.0, and we’re here with digital music and images and some of the big issues are digital rights management, digital watermarks, putting in place the structures and processes to organize and manage and control and bring governance, making sure that you have an infrastructure underneath that you can reuse and that allows you to innovate around the customer… and I think drawing that parallel can give us an idea about where this is going to go, and an idea about the types of applications that we’ll be building or using.
  • So, in summary… Everybody wants to run their business more efficiently... and be agile… but with effective governance and controls… and that’s what weblogic does… mission critical application infrastructure that is efficient, agile, governed and sustainable… and we will make sure that we continue to innovate our products to enable your innovation around this next-generation of application infrastructure. WLS-VE is miles ahead of anything that anyone else is doing in this space.
  • And I wanted to finish up with a picture, something that illustrates what I’m trying to get across… Have you ever seen this? Kite surfing? Completely mad… We had perfectly good surfboards and perfectly good kites and some bright spark said let’s puts the two together and race around the water in gale force winds and make sure that we don’t crash into each other. Amazing sport, and my point here is that is you limit yourself to conventional wisdom, if you limit yourself to what you know then the new and innovative will never exist. So thinking about where we are and the platform we provide to enable innovation, as an organisation we want to help you get to that next level, unlock the limits of convention, move forward. Think about it, if you were pre-napster and you were talking about Pandora or Last FM you would go into an insane asylum. Listen to how you would sound, “no believe me please, the computer will know what record you want to listen to next and will play it for you, only they won’t be records because we’ll have converted them into a series of electric impulses, the amplitude of each of which represents a logical 1 (pulse present) or a logical 0 (pulse absent). So you’ll be listening to all these zeroes and ones…” See what I mean? But it’s here. And now it’s everyday. What is going to be everyday tomorrow?
  • Get Virtualized

    1. 1. Get Virtualized Sean Boiling – BEA April 2008
    2. 3. Why Virtualization?
    3. 4. “ There is no why. There is do, or not do.”
    4. 5. A Chain Is As Strong As Its Weakest Link <ul><li>Benefits of SOA </li></ul><ul><li>Reuse of application assets </li></ul><ul><li>Reduce development cost </li></ul><ul><li>Increased business agility </li></ul><ul><li>Extensible computing paradigm </li></ul>Application A Application B Application Infrastructure Service Infrastructure Dedicated and Silo’ed Deployments Application Mash-Up Sales Dashboard Services Catalog
    5. 6. Virtualization is Essential to SOA Application A Application Infrastructure Service Infrastructure Response Time User Traffic <ul><li>Virtualization </li></ul><ul><li>Abstract software from underlying hardware </li></ul><ul><li>Target application instances to resource pool </li></ul><ul><li>Horizontally scale to meet demand </li></ul>Server Utilization Hypervisor Application Mash-Up Resource Pool
    6. 7. Performance, Efficiency and Maintenance Challenged With Virtualizing Java <ul><li>Even with Virtualization </li></ul><ul><li>Each S/W layer still needs maintenance and mgmt. </li></ul><ul><li>Redundant copies of OS and S/W reduces efficiency </li></ul>Multiple layers of abstraction between application & hardware OS APP AppSrvr OS APP AppSrvr OS APP AppSrvr OS APP AppSrvr JVM JVM JVM JVM Hypervisor
    7. 8. Virtualized Software Appliances Simplify Application Deployment and Maintenance <ul><li>Software Appliances </li></ul><ul><li>‘ Black Box’ approach </li></ul><ul><li>One click deployments </li></ul><ul><li>Elimination of redundancies </li></ul><ul><li>Simplified maintenance </li></ul>Fully integrated S/W stack runs single application only APP APP APP APP Hypervisor
    8. 9. Efficiency with Control of Java Applications Services Deployed in Middleware Appliances <ul><li>VMware Infrastructure </li></ul><ul><li>Pools server resources </li></ul><ul><li>Device drivers & resource control </li></ul><ul><li>Container isolation & portability </li></ul><ul><li>BEA LiquidVM </li></ul><ul><li>Virtualized Java container w/o OS </li></ul><ul><li>Reduced memory consumption </li></ul><ul><li>Enables Java applic. appliances </li></ul><ul><li>WebLogic Server Virtual Ed. </li></ul><ul><li>Virtual software appliance for WLS </li></ul><ul><li>Pre-configured, integrated, tested </li></ul><ul><li>Rapid deployment on virtual pool </li></ul>OS APP WLS OS APP WLS OS APP WLS OS APP WLS JVM JVM JVM JVM LVM LVM LVM LVM APP WLS APP WLS APP WLS APP WLS Liquid VM Liquid VM Liquid VM Liquid VM LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS Hypervisor App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE
    9. 10. Let’s see it then!
    10. 11. Do More Total Work With WLS-VE in LiquidVM Over Standard Virtualized OS Container Virtual Machines Total Throughput (ops/s) Total Throughput (ops/s) Virtual Machines Oops <ul><li>3-Tier client-server Java benchmark measuring num. of business transactions per sec. (SPECjBB) </li></ul><ul><li>Intel Xeon 3.2 GHz, 2 GB RAM, VMware ESX 3.0, BEA LiquidVM 1.1, BEA JRockit R27.3, BEA WLS 9.2 MP2, RHEL 4.0. </li></ul><ul><li>Each VM allocated 1 vCPU and 1 GB vMem. JVM -Xmx=800MB, 135 MB live data. </li></ul>Java on LiquidVM Java on Linux 3 1 2 4 5 6 7 8 3 1 2 4 5 6 7 8
    11. 12. LOC Enables New Level Application SLAs With Complete Deployment Flexibility Application Infrastructure Service Infrastructure Virtualized Resource Pool SLA Alert Application Mash-Up Sales Dashboard Exec Dashboard
    12. 13. Customer Benefit Summary <ul><li>Control </li></ul><ul><ul><li>Business agility through application governance </li></ul></ul><ul><li>Simplicity </li></ul><ul><ul><li>Pre-configured software appliances </li></ul></ul><ul><li>Efficiency </li></ul><ul><ul><li>Cost reduction through virtualization and consolidation </li></ul></ul>Key BEA Differentiators OS APP WLS OS APP WLS OS APP WLS OS APP WLS JVM JVM JVM JVM LVM LVM LVM LVM APP WLS APP WLS APP WLS APP WLS Liquid VM Liquid VM Liquid VM Liquid VM LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS LVM APP WLS Hypervisor App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE App WLS VE
    13. 14. A Passage In Time News Tapestry Cave Drawings Wood Carving Point-cast 1 st News Paper My Yahoo Virtually Inexhaustible resource & possibilities 1 st News Website
    14. 15. A Passage In Time Images 1 st B&W Photo Cave Drawings Painting Photo Album 1 st Color Photo Jpeg Virtually Inexhaustible resource & possibilities
    15. 16. A Passage In Time Music Vinyl Live Radio Mix Tape 8Track MP3 On-line libraries Virtually Inexhaustible resource & possibilities
    16. 17. A Passage In Time Enterprise Apps Green Screen Distributed Client Server Mobile SOA
    17. 18. A Passage In Time Leveling Images News Music Consumer Participation Need For Greater Controls & Process Broader Audience/Influence Cost Efficiencies Breakthrough Technologies Globalization Volume Market Enterprise Apps Vinyl Live Radio Mix Tape 8Track MP3 On-line libraries Virtually Inexhaustible resource & possibilities 1 st B&W Photo Cave Drawings Painting Photo Album 1 st Color Photo Jpeg Virtually Inexhaustible resource & possibilities Tapestry Cave Drawings Wood Carving Point-cast 1 st News Paper My Yahoo Virtually Inexhaustible resource & possibilities 1 st News Website Green Screen Distributed Client Server Mobile SOA Released From Location Drive For Mobility Released From Medium Virtualized Composition
    18. 19. Closing Thoughts <ul><li>Business Efficiencies Critical </li></ul><ul><li>Agility is key </li></ul><ul><li>But Sustainability & Controls are Crucial </li></ul><ul><li>BEA WebLogic – Rock Solid Mission Critical Applications Infrastructure </li></ul><ul><ul><li>Open, Scalable & Smart, Enabling Your Innovation ! </li></ul></ul>‘ Unlock the limits of convention ’
    19. 20. Everyday Tomorrow

    ×