17
Copyright CohesiveFT 2010 Cohesive Flexible Technologies 1 Server Motion Options Cloud Camp London Patrick Kerpan, CTO CohesiveFT

pat kerpan stateless server motion cloud camp

Embed Size (px)

Citation preview

Page 1: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2010

Cohesive Flexible Technologies

1

Server Motion OptionsCloud Camp London

Patrick Kerpan, CTO CohesiveFT

Page 2: pat kerpan stateless server motion cloud camp

Confidential CohesiveFT 2010 2

Server Motion:What if I want to move this topology 4000 miles in a couple minutes?

Example cluster:

- MySQL Clustered Storage

- Multiple MySQL Servers and Cluster Managers

- GlassFish J2EE Server Clustered with Admin Node

- Java Petstore App

• Typical of Enterprise “POA” - plain old applications

• Failure resilient but still somewhat hardwired

• What if I want 10 exact copies of this topology for testing, quickly?

• What if I want to shutdown and relaunch in a different cloud segment, quickly, exactly?

• What type of “live migration” can I do?

MySQL Cluster Nodes

MySQL Servers

MySQL Cluster Managers

GlassfishAdmin

GlassfishClusterNodes

Page 3: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009 3

Server Motion(homogeneous infra)

Load on serverNetwork Distance

Network Identity/LocationUnderlying Hardware (CPU)

Access to SAN/Network StorageState

Page 4: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009 4

Load on serverNetwork Distance

Network Identity/LocationUnderlying Hardware (CPU)

Access to SAN/Network StorageState

Server Motion x Lots

Topology Motion(homogeneous infra)

Page 5: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009 5

Server Motion (xcloud)Load on server

Network DistanceNetwork Identity/Location

Underlying Hardware (CPU)Access to SAN/Network Storage

State

Hypervisor TypeAPI

Page 6: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009 6

Topology Motion (xcloud)

Load on serverNetwork Distance

Network Identity/LocationUnderlying Hardware (CPU)

Access to SAN/Network StorageState

Server Motion x Lots x LOTS

Hypervisor FormatAPI

Page 7: pat kerpan stateless server motion cloud camp

7Copyright CohesiveFT 2009

Enterprise Topologies and Server Motion

Page 8: pat kerpan stateless server motion cloud camp

cfffffcfffff

Copyright CohesiveFT 2009

My last cloud camp I was told “Enterprises have to re-architect EVERYTHING for the cloud...they have....it is called POA!

Page 9: pat kerpan stateless server motion cloud camp

cfffffcfffff

9Copyright CohesiveFT 2009

“STATE” is the monster

Database File Store

Big state across large distances runs into physics

Page 10: pat kerpan stateless server motion cloud camp

cfffffcfffff

10

Copyright CohesiveFT 2009

As a result, like most people, we come up with solutions....

My beautiful, clean bedroom floor!

Page 11: pat kerpan stateless server motion cloud camp

cfffffcfffff

11

Copyright CohesiveFT 2009

...that push the mess into the cornerwe don’t look in! (much)

Page 12: pat kerpan stateless server motion cloud camp

12

Copyright CohesiveFT 2009

Summary of Server MotionConsiderations/Constraints

Page 13: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009

cfffffcfffff

13

VMotion Considerations

VMotion is one way to do Server Motion - if you are willing to conform to some significant constraints in exchange

VMotion hasn’t tackled Topology/Cluster Motion significantly yet, although broadly nothing stopping it

VMotion will be able to tackle the distance problem IFF- you have 10 gigE (have you priced up UK to US 10gigE?)- you run Cisco Nexus 7000+

Even upon tackling “distance” via addition of some new constraints, VMotion doesn’t handle “monster state”- In any available, practicable scenario with or without VMotion, this needs to be

handled idiosyncratically at the application or organizational level

VMotion requires special infrastructure that’s only purpose is VMotion

Page 14: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009

cfffffcfffff

14

Stateless Server Motion

Stateless Server Motion is another way to do Server Motion - 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

Stateless Server Motion is predominantly for Topology/Cluster Motion

It is indifferent to network distance if you have assembly time and boot time automation- Cloud agnostic- Hypervisor/Virtual Infra agnostic

Like VMotion, doesn’t handle “monster state”- In any available, practicable scenario both Stateless Server Motion and VMotion,

require this to be handled idiosyncratically at the application or organizational level

Stateless Server Motion uses capabilities that are there as part of your overall cloud architecture

Page 15: pat kerpan stateless server motion cloud camp

15

Copyright CohesiveFT 2009

Which is “better”?

Page 16: pat kerpan stateless server motion cloud camp

Copyright CohesiveFT 2009

cfffffcfffff

16

“Horses for Courses”

Cisco OTV, EMC Vplex, VMware VMotion is for cloud/virtual infra providers, whether Enterprise IT or outside service provider- If my infra is VMware, then I hope they use it. - 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.

Stateless Server Motion is for me (cloud user, application owner) and my topologies.- I want to “follow the moon” for lower electricity costs- I want to DR- I want to test- I want to scale

Page 17: pat kerpan stateless server motion cloud camp

17

Copyright CohesiveFT 2009

Thanks