1. globo Xen in the Cloud
.com Marco Sinhoreli
marco.sinhoreli@corp.globo.com

2. Who is the globo.com?

3. In a globalized world, one needs to brave
new routes, break through frontiers, fly in
search of new horizons.

4. More about us
‣ Internet branch of the Globo Organizations, the
largest Latin America media conglomerate and 4th in
the world
‣ World record owner in internet votes on reality-show
‣ Largest audience for video streaming in the country
‣ Considered benchmark for high-volume web
distribution

5. The globo.com leads the Brazilian
internet audience in the main segments

6. Entertainment

7. Sports

8. News

9. Videos

10. Are 11 years
building systems to support millions of users

11. globo +
.com

12. Our statement about Xen

13. ‣ High performance hypervisor
‣ Security and reliability build-in and strong isolation
‣ Ready to cloud, standard-based API
‣ Proven technology and credibility
‣ Fully-engaged and global developer community
‣ Many leader technology vendors commited

14. globo.com cloud
project orquestra

15. Economic advantages

16. Power consumption

17. Energy save in the cloud
Power consumption average
300
225
150
75
watts/hour
0
Stand-alone Server (250 w/h) Virtualized Server (20 w/h)

18. Data Center space

19. Data Center occupation
Occupied space in percent
100
75
50
25
Percent
0
Stand-alone Server Virtualized Server

20. ‣ Cooling reduce
‣ Fast provisioning
‣ Resource consolidation
‣ Reduced Data Center TCO
‣ Increased ROI of projects

21. Architecture

23. Authorization service

24. ‣ Defines the polices to system access
‣ Each profile has a specific dashboard to:
‣ Physical resources management
‣ Business resources management
‣ Network resources management
‣ VM administration segmented per project

25. User requests

26. ‣ Sync calls are used to get informations about:
‣ VMs and Hosts
‣ RRDs to create the performance graphs
‣ Async calls are used to request actions like:
‣ VM creation, shutdown, start, stop
‣ Add host and pool creation
‣ Interact with NetAPI to set LBs and Switches

27. Queuing engine

28. ‣ Used to async processes
‣ The subscribers work in paralleling process to
instance resources in the cloud
‣ The users receive real-time information about the
queue consumption
‣ The users can manage the queue stopping,
resuming and removing tasks

29. NetworkAPI

30. ‣ Used to manage network physical resources
‣ Include VLANs in the switch port trunk
‣ Apply ACLs
‣ VIP and reals creation
‣ Maintain the relationship between server and
switch ports
‣ Pluggable and vendor agnostic

31. XAPI Integration

32. ‣ Layer to contact XCP servers
‣ Expose a VNC proxy with SSL and dynamic token
authentication to hosts and VMs consoles
‣ Translates all rest-full calls to XML-RPC using
xenapi.py

33. Roadmap

34. ‣ Multi-datacenter support
‣ Integrate with OpenStack project
‣ Expose an API to integrate with internal PaaS and
Data Center management system (Energy, Cooling,
etc)
‣ Multi storage repository support
‣ Dynamic live-migration and host shutdown/start
based in consumption

35. XCP evolution

36. ‣ Better velocity in XAPI requests
‣ Today, doing many requests in a pool, the performance
is harmed
‣ Pool ejection without restart the Host
‣ Inter-pool migration and storage repository shared
between pools
‣ Link the object uuid to the task in an async call
(need a new field to connect the objects)
‣ Ex: Async.VM.clean_shutdown(vm)
‣ In this case, the task for the async call, has a field with
the Vm uuid
‣ Master recover decision enabled in XCP

37. Open Source

38. ‣ All components used in project orquestra are
open source
‣ After executing the roadmap, migrate the project to
OpenStack and turn it open source
‣ Help the OpenStack project with our development
force

39. Demo

41. Thanks
Marco Sinhoreli
marco.sinhoreli@corp.globo.com