1 User logs into FlexiScale Control Panel or API

2 User specifies their VDS (memory, operating system, storage capacity)

3 FlexiScale’s Provisioning System creates a new VDS
in <1 minute

4 User gets login to VDS
and can start using it

1 User logs into FlexiScale Control Panel or API

2 User specifies their revised VDS requirements (memory, operating system, storage capacity)

3 User can immediately restart server or schedule it for a later time to apply changes

1 User logs into FlexiScale Control Panel or API

2 User instructs the VDS
to stop

3 VDS gets stopped, VDS costs cease immediately but storage data remains intact

1 The FlexiScale Management Station detects that a physical server CPU is overloaded

2 It then selects one or more VDSs to be re-distributed
to other servers

3 Next, it identifies suitable physical target servers

4 Selected source VDSs are automatically migrated to
the physical target servers without the user noticing any downtime or major performance decrease

5 The overall CPU workload in the server with the initial problem resumes to normal levels

1 The FlexiScale Management Station detects a physical
server failure

2 It then determines which
VDSs were running on the failed server

3 For each of these VDSs
a new physical target server
gets selected

4 All VDSs get automatically re-started on their new physical target servers in <5 minutes (virtual disks get remapped
to new server as well)