Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Archipel Introduction - ejabberd SF Meetup

This is slide deck for talk given by Archipel Project Team, with Nicolas Ochem as speaker. It introduces the concept behind Archipel, a solution to manage and supervise virtual machines based on XMPP.

  • Identifiez-vous pour voir les commentaires

  • Soyez le premier à aimer ceci

Archipel Introduction - ejabberd SF Meetup

  1. 1. h t t p : / / a r c h i p e l p r o j e c t . o r g
  2. 2. General presentation Antoine Mercadal, project founder & lead developer
  3. 3. V i r t u a l i z a t i o n r e m i n d e r s Is it really mandatory ?
  4. 4. Benefits • Saves space, time, money and resources • Green IT • Simplify exploitation • Quick platform implementation You manage virtual computer as an application
  5. 5. The risks of virtualization • By definition, a virtual server doesn’t exist • A host crashes, a dozen of virtual machines crash • Need some virtual buttons and controls • Need feedback about health of virtual machines and hosts Need to communicate
  6. 6. t o d a y ’s Te c h n o l o g i e s no Java here
  7. 7. XMPP • Real-time and extensible communication protocol • Main usage : instant messaging (Google, Facebook etc.) • Free • Decentralized
  8. 8. Python • Flexible, powerful, performant and simple • Cross-platform (Linux/UNIX, Mac OS X et Windows) • Large components library • Open source
  9. 9. Cappuccino / Objective-J • Cocoa for Javascript, right from your browser • Allow to build powerful web application • Abstraction of underlaying javascript code • Very good performance • Open source
  10. 10. Libvirt • Unified layer to control virtual machines
 «Almost» unified • Support many virtualization engines
 KVM, XEN, ESX,VirtualBox, Hyper-V, OpenVZ, LXC... • Provides a Python library

  11. 11. What is exactly Archipel? • Orchestrator for virtualization
 It can be compared to Enomalism, oVirt, Proxmox, etc.
 • All is about real time 
 Everything is pushed, never pulled
 • Modular
 Near functionality free core and a set of modules
 • Scalable
 It is as easy to add or remove an hypervisor.
 • Open source
 No need for further explanation about that

  12. 12. Live migration Virtual machine creation PAE / ACPI / APIC huge pages User-to-user chat User-to-VM chat and control VNC to access virtual machines Packaging VMCasts registrationReal time statistics Beautiful GUI interface Cross platform Snapshotting VMCasts publication Cloning Virtual disk management Shared cd/dvd isos easy installation Live memory adjustment Hot CPU plug Avatar selection Group management Virtual machine autostart Virtual networks Lifecycle Logs Modular Features overview ?
  13. 13. I’m sure I know this ship... A r c h i t e c t u r e
  14. 14. Logical Architecture
  15. 15. XEP used in Archipel with • Every part of Archipel has it’s own JID and vCard Hypervisors,Virtual Machines, the users (through the UI) vCards are used to store entity type / custom informations
 • Virtual Machines use hypervisor node JID as resource This way you can know on which hypervisor the vm is hosted • PubSub for events, admin, roles and more Push mechanism to trigger actions on UI or agents. • UI settings are stored using XEP-0049 (private xml storage) And shared between UI sessions for different users • Service management is done through XEP-133 User management from the UI, except admin-list witch is done through XEP-0050
 when we have to deal with ejabberd ACLs • XML-RPC for Shared Roster Group Management (EJAB-1485) Auto-group for hypervisor and vms (no need to ask subscription for everyone)
 SRG management from the UI
  16. 16. Multi-site Architecture
  17. 17. Physical Architecture
  18. 18. Software Architecture
  19. 19. Agent Architecture
  20. 20. h t t p : / / a r c h i p e l p r o j e c t . o r g

×