the evolution of speedycloud resources scheduling system

Post on 11-Jan-2017

164 Views

Category:

Technology

2 Downloads

Preview:

Click to see full reader

TRANSCRIPT

北京迅达云成科技有限公司 www.speedycloud.cn

Beijing SpeedyCloud Technology Co., Ltd., www.speedycloud.cn 2015.8 @

Beijing

WELCOME

The Evolution of SpeedyCloud Resources

Scheduling System

北京迅达云成科技有限公司 www.speedycloud.cn

What is a Scheduling System

北京迅达云成科技有限公司 www.speedycloud.cn

What does Scheduling System of Cloud Platform usually do?

北京迅达云成科技有限公司 www.speedycloud.cn

CloudServer

CloudStorage

SDNNetwork Firewall Other

ServicesLoadBalancing

CloudCDN

北京迅达云成科技有限公司 www.speedycloud.cn

北京迅达云成科技有限公司 www.speedycloud.cn

How?

Roman wasn’t built in one day

Let’s find out how it evolves from scratch!

北京迅达云成科技有限公司 www.speedycloud.cnScenario 1:

Description:Provision Cloud server for client using Web

Context:1. Have developers dedicated for

presentation layer2. Only develop back-end

business logics3. Parameters validation and

exceptions omitted

Web

DB Physical Server

1

23

45

6

Python + Django + ShellKVMMySQL

北京迅达云成科技有限公司 www.speedycloud.cn

Scenario 2:

Description:Long time waiting when client provisions several cloud servers

Solution: Change sequential allocation to multi-thread

北京迅达云成科技有限公司 www.speedycloud.cnScenario 3:

Description:Multi datacenters deployed to satisfy increasing customers; long time waiting occurred till timeout, but PDB can’t be used to debug

Solution:Change to multi-process from multi-thread

Web

DB Physical Server

Web

DB

Datacenter A

Datacenter B

Datacenter C

Datacenter D

Datacenter E

北京迅达云成科技有限公司 www.speedycloud.cnScenario 4:

Description:Failure occurred due to network jittering from some datacenters to control center, and control center can’t be notified even if cloud servers successfully were provisioned.Solution:

1. Change to BGP datacenter2. Message Queue introduced to

solve the timeout

Web

DB

Datacenter A

Datacenter B

Datacenter C

Datacenter D

Datacenter E

Datacenter B

Datacenter C

Datacenter D

Datacenter E

Web

DB

Datacenter A

MQ

Worker

北京迅达云成科技有限公司 www.speedycloud.cnScenario 5:

Description:1. More devices upgrades and

maintenances needed.2. Client resource application

need to be handled even when upgrading web front-end.

Datacenter B

Datacenter C

Datacenter D

Datacenter E

Web

DB

Datacenter A

MQ

Worker

Solution:1. Live migration of host and hot

patch for OS2. Add System Halt Status3. Add Node Halt Status

Datacenter B

Datacenter C

Datacenter D

Datacenter E

Web

DB

Datacenter A

MQ

Worker

Job Tracker

1. Add System Halt Status2. Add Node Halt Status

北京迅达云成科技有限公司 www.speedycloud.cn

Thanks!

Beijing SpeedyCloud Technology Co., Ltd.,

www.speedycloud.cn

top related