Virtual Machine Lifecycle Management. The example of CernVM

Transcription

1 Virtual Machine Lifecycle Management The example of CernVM

2 INTRODUCTION - What is a virtual machine lifecycle - Current Implementation - Ideal Solution

3 INTRODUCTION What is a Virtual Machine Lifecycle Collect Software Build Appliance Define Configuration Test Builds Deploy & Manage Publish

4 INTRODUCTION Current Implementation Collect Software Build Appliance Define Configuration Test Builds Manual configuration Deploy & Manage Publish

5 INTRODUCTION Current Implementation Collect Software Build Appliance Manual collection of software Define Configuration Test Builds Manual configuration Deploy & Manage Publish

6 INTRODUCTION Current Implementation Collect Software Build Appliance Manual collection of software Using a custom tool: ibuilder Define Configuration Test Builds Manual configuration Deploy & Manage Publish

7 INTRODUCTION Current Implementation Collect Software Build Appliance Manual collection of software Using a custom tool: ibuilder Define Configuration Manual configuration Test Builds Manually testing the images on every hypervisor Deploy & Manage Publish

8 INTRODUCTION Current Implementation Collect Software Build Appliance Manual collection of software Using a custom tool: ibuilder Define Configuration Manual configuration Test Builds Manually testing the images on every hypervisor Deploy & Manage Publish Manual publish

9 INTRODUCTION Current Implementation Collect Software Build Appliance Manual collection of software Using a custom tool: ibuilder Define Configuration Manual configuration Test Builds Manually testing the images on every hypervisor Deploy & Manage Publish VMWare vsphere & Amazon Cloud Manual publish

10 INTRODUCTION Problems As the project is getting bigger, it s not possible to do all those steps manually Each phase of the lifecycle requires a different software There is no unified solution Commercial licenses for the software involved on every step make the whole process very expensive

11 INTRODUCTION Commercial Software Building: rbuilder Not supporting SLC any more Managing: VMWare vsphere Ideal but too expensive Again, no unified solution

12 INTRODUCTION Ideal solution Each component is independent They connect with each other seamlessly into a single solution They can all be managed from a single, userfriendly interface They can communicate with each other to perform automated jobs Components can be added on demand It s open source

13 ARCHIPEL Closest open-source starting point

14 ARCHIPEL Features Virtual Machine and Hypervisor manager written in python and Objective-J Uses a distributed agent/client architecture Provides a powerful browser-based front-end Requires no server-side scripting Modular design Can be extended It uses open-source components It is based on the XMPP (Jabber) protocol Widely used, and tested (Google Chat, ichat, Facebook Chat) Can be clustered

15 ARCHIPEL Architecture Agents Agent Hypervisor A Agent Hypervisor B Virtual Machine Hypervisor A Virtual Machine Hypervisor B Virtual Machine Hypervisor B XMPP XMPP XMPP Server ejabberd BOSH XMPP Chat Client Chat Client Archipel GUI Client

16 ARCHIPEL How can Archipel be extended Agents and clients can easily be created since they are using a wide-spread protocol with many implementations (XMPP) Custom front-ends can be added on the existing front-end, due to it's modular design Since all of the components are using the same transport, they can also talk with each other.

17 ARCHIPEL Problems Poor documentation regarding the module development (Official documentation It's under construction) Heavy front-end Cannot run on portable devices

18 PROGRESS Development and current status

19 PROGRESS Our additions Agent Agent Agents Hypervisor A Hypervisor B Agent Virtual Machine Hypervisor A XMPP Repository Virtual Machine Hypervisor B XMPP XMPP Server ejabberd XMPP Image Builder Virtual Machine Hypervisor B BOSH Image Tester Archipel GUI New Agents Client

20 PROGRESS Our additions Agent Agent Agents Hypervisor A Hypervisor B Agent Virtual Machine Hypervisor A XMPP Repository Virtual Machine Hypervisor B XMPP XMPP Server ejabberd XMPP Image Builder Virtual Machine Hypervisor B BOSH Image Tester Archipel GUI Client PicoClient GUI Client New client for portable devices

21 PROGRESS Our additions Agent Agent Agents Hypervisor A Hypervisor B Agent Virtual Machine Hypervisor A XMPP Repository Virtual Machine Hypervisor B XMPP XMPP Server ejabberd XMPP Image Builder Virtual Machine Hypervisor B BOSH Image Tester New frontend modules for the new agents Archipel GUI Client PicoClient GUI Client

22 PROGRESS Our additions Agents Agent Hypervisor A Agent Hypervisor B Enable Inter-Agent communication Agent Virtual Machine Hypervisor A XMPP Repository Virtual Machine Hypervisor B XMPP XMPP Server ejabberd XMPP Image Builder Virtual Machine Hypervisor B BOSH Image Tester Archipel GUI PicoClient GUI Client Client

23 PROGRESS Our additions New agents that cover the first stages of the VM Lifecycle Software Collection: Repository agent Image Building: Building agent (ibuilder) Image Testing: Testing agent (Taper) New front-end for portable devices New front-end modules for Archipel GUI Enable Inter-Agent communication

24 PROGRESS What is done so far We have submitted a patch to the Archipel team that allows us to create custom modules on the front-end. The patch was accepted and it's on the current release. We have created a minimal perl agent that can wrap existing components into Archipel-Compatible agents. Despite the poor documentation, we managed to create some front-end modules, and a skeleton that can be used as a starting point to create other modules. We have created a modular, lightweight client that can run on portable devices.

25 PROGRESS Perl Agent (iagent) Minimal starting point for new Archipel- Compatible Agents Modular design Based on PoE Single-threaded Multitasking New messaging additions on PoE Broadcasting with module hierectary LDAP Authentication

26 PROGRESS Message Broadcast Perl Agent (iagent) XMPP Module XMPP XMPP Server ejabberd Authentication Module User module(s) iagent

27 PROGRESS ibuilder Module Agent Uses iagent Command-line interface to ibuilder Connection to ibuilder database Client ArchipelClient front-end to define probjects, prepare and initiate builds

28 PROGRESS ibuilder Module

29 PROGRESS ibuilder Module

30 PROGRESS ibuilder Module

31 PROGRESS PicoClient Lightweight browser-based client for portable devices UI based on Sencha Touch framework Modular system similar to Archipel Client HTML5 offline-capable Compatible with the existing archipel agents Provides native application look-and-feel for iphone, ipad, Android and BlackBerry

32 PROGRESS PicoClient

33 PROGRESS PicoClient

34 DEMONSTRATION Archipel Client: Pico Client:

35