1. THE EVOLUTION
OF VIRTUAL
MENTALITY
Darrell Hyde
Director of Architecture, Hosting.com
1 © Hosting.com | This document is confidential and proprietary.

2. 2 © Hosting.com | This document is confidential and proprietary.

3. Our Foundation
* **
* *
*
* 2012 * 2012 Deployments
Deployments
* 2013 Deployments
3 © Hosting.com | This document is confidential and proprietary.

4. Cloud Enterprise Overview
Launched in 2009
Built on VMware vShpere 5
Powered by:
 Juniper MX / EX Routing and Switching
 EMC CX4 and VNX Storage
 Dell R-Series Servers
Supporting over 2600 VMs across over 180
physical servers
Distributed across 5 locations
4 © Hosting.com | This document is confidential and proprietary.

5. VIRTUAL MENTALITY 1.0
VS.
VIRTUAL MENTALITY 2.0
5 © Hosting.com | This document is confidential and proprietary.

6. Virtual Mentality 1.0
Adapt old service delivery mechanisms to
fit virtual infrastructure
Treat virtual machines like physical
machines
Force customers to understand physical
network topology
6 © Hosting.com | This document is confidential and proprietary.

7. Service Delivery Goals
Complete service parity
Firewall + IDS
VPN
Load Balancing
Hybrid from the start
Customers can spin up VMs in existing VLANs
New VMs can live behind existing firewalls
New VMs can live in existing SLB pools
7 © Hosting.com | This document is confidential and proprietary.

8. How did we get there?
8 © Hosting.com | This document is confidential and proprietary.

9. How did we get there?
9 © Hosting.com | This document is confidential and proprietary.

10. How did we get there?
10 © Hosting.com | This document is confidential and proprietary.

11. What problems did this create?
Complicated layer 2 topology
“You guys have a lot of VLANs.”
Pain for customers who want to adopt in-
line services
Increased operational overhead
Tight coupling of services with network
topology
High rate of change
11 © Hosting.com | This document is confidential and proprietary.

12. Virtual Mentality 2.0
Leverage the hypervisor to offload
services
Less dependency on network topology
Simpler provisioning experience for
customers
12 © Hosting.com | This document is confidential and proprietary.

13. Cloud Firewall
Security policy decoupled from network
topology
Customers can provision and manage the
product independent of network topology
Zero-impact install experience
Self-service user interface
13 © Hosting.com | This document is confidential and proprietary.

14. Best of Breed Technology and Approach
VLANs & Physical Traditional Purpose Built
1 Segmentation 2 Security Agents 3 Virtual Security
VM1 VM2 VM3 VM1 VM2 VM3 VM1 VM2 VM3
ESX/ESXi Host
ESX/ESXi Host
ESX/ESXi Host
VS VS
Virtual Security Layer
VS
HYPERVISOR HYPERVISOR
HYPERVISOR
Regular Thick Agent for FW
Complex VLAN networking; Lacks Tedious agent installation on each Seamless hypervisor integration;
hypervisor visibility; High overhead VM; significant performance issues Optimized performance; Dynamic
security
14 © Hosting.com | This document is confidential and proprietary.

15. Shared Customer Pod
15 © Hosting.com | This document is confidential and proprietary.

16. Shared Customer Pod
16 © Hosting.com | This document is confidential and proprietary.

17. Shared Customer Pod
17 © Hosting.com | This document is confidential and proprietary.

18. Shared Customer Pod
18 © Hosting.com | This document is confidential and proprietary.

19. Easily Scales to Support Growth
19 © Hosting.com | This document is confidential and proprietary.

20. Provides Additional Security at Layer 2
20 © Hosting.com | This document is confidential and proprietary.

21. User Experience
1. Simple ordering process
Less than 15 clicks from order to secure
Ready to manage in less than 10 minutes
2. Group VMs based on role or application
3. Create policies
21 © Hosting.com | This document is confidential and proprietary.

22. Step 1: Ordering
22 © Hosting.com | This document is confidential and proprietary.

23. Step 2: Create groups
23 © Hosting.com | This document is confidential and proprietary.

24. Step 3: Create policies
24 © Hosting.com | This document is confidential and proprietary.

25. Step 3: Create policies
25 © Hosting.com | This document is confidential and proprietary.

26. Step 3: Create policies
26 © Hosting.com | This document is confidential and proprietary.

27. Conclusion
• Hypervisor isn’t just another endpoint on
your network – it’s an extension of it
• Customers think of security in terms of
applications, not networks
• Virtualization allows you to decouple
services from the network
27 © Hosting.com | This document is confidential and proprietary.

28. Thank you!
Questions?
Darrell Hyde – darrell@hosting.com
28 © Hosting.com | This document is confidential and proprietary.