Presentation is loading. Please wait.

Presentation is loading. Please wait.

Workspaces for CE Management Kate Keahey Argonne National Laboratory.

Similar presentations

Presentation on theme: "Workspaces for CE Management Kate Keahey Argonne National Laboratory."— Presentation transcript:

1 Workspaces for CE Management Kate Keahey Argonne National Laboratory

2 06/22/05EGEE All Hands, Brno Why Workspaces? l We need to be able to dynamically create an execution environment on remote resources l The aspects of workspaces: u Quality of Service: isolation and enforcement u Quality of Life: providing the right configuration at the right time Ideal environment is deployed in just the right place Dream up an ideal environment magic happens run jobs

3 06/22/05EGEE All Hands, Brno What are Virtual Workspaces? l A description of an execution environment u Software configuration requirements l OSG worker node, submit node for a Grid3 cluster u Resource allocation requirements l Use exactly X memory, at least Y disk space, Z bandwidth… u Sharing and isolation properties l Unix account, sandbox, various kinds of virtual machines … u And others… l Basic workspace example : a Unix account on a remote machine l Workspace can be managed and refined u In terms of lifetime, meta-data, access policies… l A workspace can be deployed on a resource l Jobs can be deployed in a workspace l A workspace can have various implementations u Dynamic accounts & configuration tools l Pacman, SoftEnv, Softricity u Virtual Machines

4 06/22/05EGEE All Hands, Brno CPU = Pentium Memory = 1GB Disk = 20GB Find a resource advertising the required capability Binding Wrokspaces to Resources Client capability description CPU >= 60% Pentium Memory = 256 MB Reserve capability vw1 capability description CPU >= 30% Pentium Memory = 512 MB Reserve capability for vw2 workspace description CPU >= 60% Pentium Memory = 256 MB Software. = OSG SE v1 workspace description CPU >= 30% Pentium Memory = 512MB Software = exp Bind to reservation

5 06/22/05EGEE All Hands, Brno VW Implemenations: Virtual Machines l Advantages u Customizable software configuration l Library signature, OS, 64/32-bit architectures u Excellent enforcement potential l Enforcement on a sandbox rather than process level u Excellent isolation l Generally enhanced security, audit forensics u Pausing, serialization, and migration l VM images (include RAM), can be copied l Available implementations u Commercial (VMware) u Open source (Xen, UML) l Also support for Xen from XenSource and many Linux distributors l Xen is rapidly emerging as the most popular implementation u The fastest, freeest, the most open source, the most backed…

6 06/22/05EGEE All Hands, Brno The Need for Speed LXVU SPEC INT2000 (score) LXVU Linux build time (s) LXVU OSDB-OLTP (tup/s) LXVU SPEC WEB99 (score) Benchmark suite running on Linux (L), Xen (X), VMware Workstation (V), and UML (U)

7 06/22/05EGEE All Hands, Brno DRAG Benchmark Results l DRAG suite: FFT-based benchmark l Comparison (by Xuehai Zhang, UC): u Linux: machine runs native 2.6 Linux. u Dom0: machine runs Xen and domain 0. u DomU: machine runs Xen, domain 0 and a user domain. l Similar performance as native Linux u <3% degradation, but sometimes actually better than native Linux l More details at

8 06/22/05EGEE All Hands, Brno Deployment Concerns l Distribution/Installation u Para-virtualization (Xen) requires kernel modifications l Yes, but … everything else stays the same l Work in progress on making Xen part of Linux kernel u False information of its conclusion seen recently! l Support from many Linux distributors: Fedora, Debian, SUSE, Gentoo, Mandrake, etc. l Privilege level(Xen) u Domain0 is a privileged domain, not a good environment for sharing. u If Xen configuration is going to be permanent using DomainU is recommended l Performance impact needs to be considered

9 06/22/05EGEE All Hands, Brno The Xen of Enforcement l CPU u Schedulers: BVT, FBVT, Round Robin, Atropos/SEDF u May be selected at boot time; BVT is default u Borrowed Virtual Time (BVT) l Fair share of CPU based on weights assigned to the domains l Work-conserving u Simple Earliest Deadline First (SEDF) l Reserves absolute shares of CPU for domains l Memory u Memory size specified in a configuration file u Can be readjusted from domain0 l Disk u Export partitions u Logical Volume Manager (LVM) allows to grow and shrink the disk size l Networking u Standard Linux deployment tools: Domain0 can do traffic shaping for user domains.

10 06/22/05EGEE All Hands, Brno Workspace as a CE Environment CE WSS LCAS LCMAPS GRAM CE WSS LCAS LCMAPS GRAM headnode VW Manager CE WSS LCAS LCMAPS GRAM VW Manager CE broker

11 06/22/05EGEE All Hands, Brno Pros and Cons l Problems that VMs solve for us u Environment management l Configuration management u Running two different versions of CE software side-by-side l Enforcement and isolation u Graceful load management l Renegotiating the resource allocation l Live migration across nodes l Problems that VMs dont solve for us u Job management: jobs within an environment still need to be managed l Job throttling l Job persistence, restart, etc. u The cost of perfect enforcement l Each CE will run a copy of similar services leading to potential inefficiencies l There has been some work in sharing e.g. shared libraries between VMs, but is inconclusive right now

12 06/22/05EGEE All Hands, Brno Other things VMs are not helpful for… l Digestion l Walking your dog l Laundry l Most sports l Painting walls l Knitting l Grocery shopping (unless you shop via peapod)

13 06/22/05EGEE All Hands, Brno Meanwhile, in a galaxy far, far away… l Similar ideas in US projects u Edge Services l effort led by Frank Wuertherwein in the context of OSG/CMS u Management of submit nodes l work with Rob Gardner and Mike Wilde in the context of Grid3/Atlas l Requirements: u Install and manage a complex configuration l Easy upgrades based on pre-configured images, consistent configuration across sites, version management, etc. u Control of resources l Guaranteed dedicated use of resources u Flexible load balancing l Widening the interface to a cluster based on need

14 06/22/05EGEE All Hands, Brno Edge Services l Edge Services: Services executing on the edge of a private/public network boundary u Typical configuration of todays resources l Resources within a site are available only on a private network l Site can be accessed through a limited number of public addresses u Examples: CE, SE, GK, and others l Edge Services will be deployed in VM-based workspaces u Role-based deployment u Initially no advance reservations, no load balancing u A proof-of-concept activity l Draft document available: u bin/ShowDocument?docid=167 bin/ShowDocument?docid=167

15 06/22/05EGEE All Hands, Brno Submit Node Management l Similar to the Edge Service activity with particular emphasis on: u Configuration management l Configure once, copy and deploy many times u Load balancing: widening the submit bottleneck to clusters based on need Client

16 06/22/05EGEE All Hands, Brno Conclusions l Workspaces solve environment management problems u Configuration management l Configure once, copy and deploy many times l Upgrading service versions l Running conflicting or incompatible services side-by-side u Enforcement l Guaranteed resources with respect to other users l There seems to be a confluence of ideas u Similar ideas in three different contexts u Coincidence? l Workspaces do not solve job management problems u Which leads into subjects well talk about later…

Download ppt "Workspaces for CE Management Kate Keahey Argonne National Laboratory."

Similar presentations

Ads by Google