pat kerpan stateless server motion cloud camp

641 views
541 views

Published 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
641
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

pat kerpan stateless server motion cloud camp

  1. 1. Server Motion Options <ul><li>Cloud Camp London </li></ul><ul><li>Patrick Kerpan, CTO CohesiveFT </li></ul>
  2. 2. Server Motion: What if I want to move this topology 4000 miles in a couple minutes? <ul><li>Example cluster: </li></ul><ul><ul><li>MySQL Clustered Storage </li></ul></ul><ul><ul><li>Multiple MySQL Servers and Cluster Managers </li></ul></ul><ul><ul><li>GlassFish J2EE Server Clustered with Admin Node </li></ul></ul><ul><ul><li>Java Petstore App </li></ul></ul><ul><li>Typical of Enterprise “POA” - plain old applications </li></ul><ul><li>Failure resilient but still somewhat hardwired </li></ul><ul><li>What if I want 10 exact copies of this topology for testing, quickly? </li></ul><ul><li>What if I want to shutdown and relaunch in a different cloud segment, quickly, exactly? </li></ul><ul><li>What type of “live migration” can I do? </li></ul>MySQL Cluster Nodes MySQL Servers MySQL Cluster Managers Glassfish Admin Glassfish Cluster Nodes
  3. 3. Server Motion (homogeneous infra) Load on server Network Distance Network Identity/Location Underlying Hardware (CPU) Access to SAN/Network Storage State
  4. 4. Load on server Network Distance Network Identity/Location Underlying Hardware (CPU) Access to SAN/Network Storage State Server Motion x Lots Topology Motion (homogeneous infra)
  5. 5. Server Motion (xcloud) Load on server Network Distance Network Identity/Location Underlying Hardware (CPU) Access to SAN/Network Storage State Hypervisor Type API
  6. 6. Topology Motion (xcloud) Load on server Network Distance Network Identity/Location Underlying Hardware (CPU) Access to SAN/Network Storage State Server Motion x Lots x LOTS Hypervisor Format API
  7. 7. Enterprise Topologies and Server Motion
  8. 8. My last cloud camp I was told “Enterprises have to re-architect EVERYTHING for the cloud...they have....it is called POA!
  9. 9. “ STATE” is the monster Database File Store <ul><li>Big state across large distances runs into physics </li></ul>
  10. 10. As a result, like most people, we come up with solutions.... My beautiful, clean bedroom floor!
  11. 11. ...that push the mess into the corner we don’t look in! (much)
  12. 12. Summary of Server Motion Considerations/Constraints
  13. 13. VMotion Considerations <ul><li>VMotion is one way to do Server Motion </li></ul><ul><ul><li>if you are willing to conform to some significant constraints in exchange </li></ul></ul><ul><li>VMotion hasn’t tackled Topology/Cluster Motion significantly yet, although broadly nothing stopping it </li></ul><ul><li>VMotion will be able to tackle the distance problem IFF </li></ul><ul><ul><li>you have 10 gigE (have you priced up UK to US 10gigE?) </li></ul></ul><ul><ul><li>you run Cisco Nexus 7000+ </li></ul></ul><ul><li>Even upon tackling “distance” via addition of some new constraints, VMotion doesn’t handle “monster state” </li></ul><ul><ul><li>In any available, practicable scenario with or without VMotion, this needs to be handled idiosyncratically at the application or organizational level </li></ul></ul><ul><li>VMotion requires special infrastructure that’s only purpose is VMotion </li></ul>
  14. 14. Stateless Server Motion <ul><li>Stateless Server Motion is another way to do Server Motion </li></ul><ul><ul><li>Relatively few constraints, it can be done as part of existing cloud infra, requires rigorous automation of server definitions, rigorous automation boot time context, mechanism to quickly separate network location from identity </li></ul></ul><ul><li>Stateless Server Motion is predominantly for Topology/Cluster Motion </li></ul><ul><li>It is indifferent to network distance if you have assembly time and boot time automation </li></ul><ul><ul><li>Cloud agnostic </li></ul></ul><ul><ul><li>Hypervisor/Virtual Infra agnostic </li></ul></ul><ul><li>Like VMotion, doesn’t handle “monster state” </li></ul><ul><ul><li>In any available, practicable scenario both Stateless Server Motion and VMotion, require this to be handled idiosyncratically at the application or organizational level </li></ul></ul><ul><li>Stateless Server Motion uses capabilities that are there as part of your overall cloud architecture </li></ul>
  15. 15. Which is “better”?
  16. 16. “Horses for Courses” <ul><li>Cisco OTV, EMC Vplex, VMware VMotion is for cloud/virtual infra providers, whether Enterprise IT or outside service provider </li></ul><ul><ul><li>If my infra is VMware, then I hope they use it. </li></ul></ul><ul><ul><li>Server 53’s physical hardware looks like it is dying...it has nine VMs on it. Operations spins up 53-prime and uses VMotion to server motion the vm’s over...and one of them is mine, and I don’t notice...fine. </li></ul></ul><ul><li>Stateless Server Motion is for me (cloud user, application owner) and my topologies. </li></ul><ul><ul><li>I want to “follow the moon” for lower electricity costs </li></ul></ul><ul><ul><li>I want to DR </li></ul></ul><ul><ul><li>I want to test </li></ul></ul><ul><ul><li>I want to scale </li></ul></ul>
  17. 17. Thanks

×