DOCSLIB.ORG

Bsync: Sistema Extensible Para La Sincronizaci´Ony Copia De Seguridad De ficheros Para Su Uso En Organizaciones

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Bsync: Sistema Extensible Para La Sincronizaci´Ony Copia De Seguridad De ficheros Para Su Uso En Organizaciones Escuela Polit´ecnicaSuperior Departamento de Inform´atica Proyecto de Fin de Carrera bsync: Sistema extensible para la sincronizaci´ony copia de seguridad de ficheros para su uso en organizaciones Javier Torres Ni~no Tutores Juan Miguel G´omezBerb´ıs Alejandro Rodr´ıguezGonz´alez 28 de Julio de 2011 2 Resumen En la actualidad existen muchos sistemas de sincronizaci´ony copia de segu- ridad de ficheros, pero la mayor´ıade ellos no comercializan el producto, optando por comercializar los servicios ofrecidos por medio de estos. Esto impide el uso de estas herramientas a entidades que necesiten que sus datos no salgan de su entorno, por lo que el objetivo de este Proyecto de Fin de Carrera es el dise~no y desarrollo de un sistema similar a estos otros productos. Se analizan las caracter´ısticasde los competidores, y se dise~naun programa que incluye en el n´ucleolas caracter´ısticasb´asicasy sea capaz de incluir to- das las caracter´ısticasadicionales mediante el uso de extensiones o plugins. Es precisamente esta extensibilidad la que caracteriza el sistema, permitiendo que un mismo producto pueda adaptarse a las necesidades de multitud de clientes, que pueden precisar, por ejemplo, de distintos sistemas de autenticaci´on(para integrar el sistema en la arquitectura existente) o utilizar la infraestructura para sincronizar m´asque ficheros. Palabras clave: sincronizaci´on,copia de seguridad, extensibilidad, plugins, sistemas distribuidos 3 4 Agradecimientos Es impensable dejar este proyecto sin unas breves l´ıneas en las que agradecer a todas las personas que me han soportado durante estos ´ultimoscinco a~nos,y especialmente los ´ultimosmeses. En primer lugar tengo que mencionar a todos los compa~nerosde clases con los que tanta risas he compartido, especialmente a todos los integrantes de vastralis, que tan unidos hemos estado estos ´ultimosa~nos.Sin vosotros no habr´ıalogrado llegar hasta aqu´ı. Tambi´enquiero recordar a mis amigos de toda la vida, ya sab´eisqui´enes sois. >Que ser´ıade m´ısin esas largas noches sentados todos alrededor de una mesa, jugando y de ch´achara? No puedo olvidar mencionar a todo el equipo docente que ha hecho posible que pueda completar este proyecto, sin vuestras ense~nanzasno tendr´ıani la mitad de conocimientos que he utilizado durante su realizaci´on.Llegu´ea la universidad creyendo que sab´ıabastante de inform´atica,ahora me voy con la certeza de no saber casi nada. Tambi´ense merecen una menci´onespecial mis compa~nerosde laboratorio, cotutores oficiales y extraoficiales de este proyecto. Sin vuestros consejos y lo que me aprend´ıde vosotros sobre el campo investigador, este proyecto habr´ıa sido muy distinto. Y en ´ultimolugar, aunque no por ello menos importante, a mi familia por introducirme en el mundo de la inform´aticaa la tierna edad de los 6 a~nos,a la que me he agarrado desde entonces, primero como hobby y despu´escomo profesi´on. Menci´onespecial para mi hermano por aguantar mi escaqueo generalizado de las tareas del hogar mientras terminaba de escribir esta memoria. A todos, muchas gracias Javier 5 6 ´Indice general I Introducci´on 15 1. Introducci´on 17 1.1. Motivaci´on . 17 1.2. Objetivos . 18 1.3. Metodolog´ıa. 19 1.4. Organizaci´onde este documento . 20 II An´alisisdel problema 23 2. Estado del arte 25 2.1. Copias de seguridad . 25 2.2. Sincronizaci´onde ficheros . 26 2.2.1. Sistemas de ficheros en red . 26 2.2.2. Sincronizaci´onperi´odicao mirroring de directorios . 27 2.2.3. Sincronizaci´oncon copia local . 27 3. An´alisis 29 3.1. Objetivos principales . 29 3.2. Extensibilidad . 30 3.3. Arquitectura de red . 31 3.3.1. Peer to peer total . 31 3.3.2. Peer to peer con localizador . 31 3.3.3. Cliente-Servidor . 32 3.3.4. Evaluaci´on . 32 3.4. Sincronizaci´onentre m´ultiplesusuarios . 33 3.5. Comunicaciones . 34 3.5.1. Requisitos . 34 3.5.2. Transporte . 34 3.5.3. Aplicaci´on. 35 3.6. Consistencia . 36 3.6.1. Pol´ıticapor defecto . 37 3.7. Almacenamiento de los datos . 39 3.8. Plataforma de desarrollo . 40 3.8.1. Alternativas . 40 3.8.2. Comparaci´on . 41 3.8.3. Decisi´on. 42 7 ´INDICE GENERAL III Dise~nodel prototipo 45 4. Dise~nodel protocolo 47 4.1. Multiplexado . 47 4.1.1. Formato del paquete . 47 4.1.2. Gesti´onde canales . 48 4.2. Protocolo de control . 49 4.2.1. Representaci´onde los datos . 50 4.2.2. Comandos . 51 4.3. Implementaci´onde los protocolos . 57 4.3.1. SocketChannel . 58 4.3.2. MultiplexerSocket . 58 4.3.3. MultiplexerSocketServer . 59 5. Dise~nodel cliente 61 5.1. Dise~nomodular . 61 5.2. Representaci´ondel ´arbol local . 63 5.3. Gesti´ondel ´arbol local . 65 5.4. Base de datos de metadatos . 66 5.5. Comunicaci´oncon el servidor . 69 5.5.1. ClientConnection . 69 5.5.2. ClientConnectionShare . 70 5.6. Funciones globales . 71 5.6.1. Configuraci´on. 71 5.6.2. Carga de plugins . 74 5.6.3. Interfaz con el usuario . 74 5.6.4. Gesti´onde conexiones . 74 6. Dise~nodel servidor 75 6.1. Dise~nomodular . 75 6.2. Base de datos . 76 6.2.1. Usuarios, shares y permisos . 76 6.2.2. Objetos: ficheros y directorios . 77 6.2.3. Datos hist´oricos . 78 6.2.4. Capa de acceso a datos . 78 6.3. Comparticiones . 79 6.4. Conexiones . 81 6.4.1. Autenticaci´ony apertura de shares . 81 6.4.2. Transferencias y almacenamiento . 81 6.4.3. Mantenimiento de la conexi´on. 83 6.5. Funciones globales . 83 7. Plugins 85 7.1. Caracter´ısticascomunes . 85 7.2. Monitoreo del sistema de ficheros . 87 7.2.1. Interfaz . 88 7.2.2. Plugin para Linux: inotify . 88 7.2.3. Plugin para Windows: ReadDirectoryChangesW . 90 7.2.4. Plugin para Mac OS X: FSEvents . 91 7.3. Autenticaci´on. 92 8 ´INDICE GENERAL 7.3.1. Interfaz . 92 7.3.2. Implementaci´on:PgCryptoAuthenticator . 93 7.4. Interfaz de usuario . 93 7.4.1. Carga din´amicade librer´ıasgr´aficas . 94 7.4.2. Interfaz . 94 7.4.3. Implementaci´on:MiniGui . 96 7.5. Otros plugins . 97 7.5.1. Modificaci´onde metadatos . 98 7.5.2. Modificaci´onde datos . 98 7.5.3. Transferencia de ficheros . 99 7.5.4. Comunicaci´onarbitraria . 99 8. Interfaz web 101 8.1. Plataforma de desarrollo . 101 8.2. Dise~no . 102 8.2.1. Modelo . 102 8.2.2. Vista . 102 8.2.3. Plantillas . 104 9. Seguridad y rendimiento 107 9.1. Hash de los datos . 107 9.1.1. Algoritmo de hash . 108 9.1.2. Ataques y dominio de colisi´on. 110 9.1.3. Decisi´on. 111 9.2. Almacenamiento de contrase~nas. 112 9.2.1. Cliente . 112 9.2.2. Servidor . 113 9.3. Seguridad de las comunicaciones . 113 9.4. Paralelismo . 114 9.4.1. Cliente . 114 9.4.2. Servidor . 116 IV Conclusiones y Presupuesto 117 10.Conclusiones 119 10.1. Trabajo futuro . 119 10.1.1. Acceso a comparticiones en otros servidores . 119 10.1.2. Seguridad en los plugins . 120 10.1.3. Publicaci´ony comercializaci´on . 121 10.2. Conclusiones personales . 121 11.Presupuesto 123 11.1. Gastos directos . 123 11.1.1. Gastos de personal . 123 11.1.2. Otros gastos directos . 123 11.2. Gastos indirectos, riesgo y beneficio . 124 11.3. Tabla resumen y totales . 125 9 10 ´Indice de figuras 1.1. Esquema del ciclo de desarrollo utilizado . 20 3.1. Arquitecturas de red . 32 3.2. Tr´aficode red en los distintos modelos de resoluci´onde conflictos 37 3.3. Se~nalesy slots . 43 4.1. Pila de protocolos de red . 47 4.2. Protocolo de multiplexado . 48 4.3. Protocolo de control . 50 4.4. Diagrama de clases simplificado para el protocolo de multiplexado 60 5.1. Diagrama de clases simplificado para el cliente . 62 5.2. Ejemplo de configuraci´onen el registro de Windows . 71 6.1. Base de datos del servidor . ..
Load more

Recommended publications
  • The Equifax Fiasco
    Security Now! Transcript of Episode #628 Page 1 of 28 Transcript of Episode #628 The Equifax Fiasco Description: This week we discuss last Friday's passing of our dear friend and colleague Jerry Pournelle; when AI is turned to evil purpose; whether and when Google's Chrome browser will warn of man-in-the-middle attacks; why Google is apparently attempting to patent pieces of a compression technology they did not invent; another horrifying router vulnerability disclosure including 10 zero-day vulnerabilities; an update on the sunsetting of Symantec's CA business unit; another worrying failure at Comodo; a few quick bits; an update on my one commercial product SpinRite; answering a closing-the-loop question from a listener; and a look at the Equifax fiasco. High quality (64 kbps) mp3 audio file URL: http://media.GRC.com/sn/SN-628.mp3 Quarter size (16 kbps) mp3 audio file URL: http://media.GRC.com/sn/sn-628-lq.mp3 SHOW TEASE: It's time for Security Now!. Steve Gibson is here. And he, you know, it's funny when something like the Equifax breach happens, I don't know about you, but I just wait all week just to hear what Steve has to say about it. Well, your wait is over. Equifax and a lot more coming up next on Security Now!. Leo Laporte: This is Security Now! with Steve Gibson, Episode 628, recorded Tuesday, September 12th, 2017: Equifax Fiasco. It's time for Security Now!, the show where we cover security, now, with this guy right here, Steven Gibson of the GRC, Gibson Research Corporation, GRC.com.
    [Show full text]
  • Automatic Program Repair Using Genetic Programming
    Automatic Program Repair Using Genetic Programming A Dissertation Presented to the Faculty of the School of Engineering and Applied Science University of Virginia In Partial Fulfillment of the requirements for the Degree Doctor of Philosophy (Computer Science) by Claire Le Goues May 2013 c 2013 Claire Le Goues Abstract Software quality is an urgent problem. There are so many bugs in industrial program source code that mature software projects are known to ship with both known and unknown bugs [1], and the number of outstanding defects typically exceeds the resources available to address them [2]. This has become a pressing economic problem whose costs in the United States can be measured in the billions of dollars annually [3]. A dominant reason that software defects are so expensive is that fixing them remains a manual process. The process of identifying, triaging, reproducing, and localizing a particular bug, coupled with the task of understanding the underlying error, identifying a set of code changes that address it correctly, and then verifying those changes, costs both time [4] and money. Moreover, the cost of repairing a defect can increase by orders of magnitude as development progresses [5]. As a result, many defects, including critical security defects [6], remain unaddressed for long periods of time [7]. Moreover, humans are error-prone, and many human fixes are imperfect, in that they are either incorrect or lead to crashes, hangs, corruption, or security problems [8]. As a result, defect repair has become a major component of software maintenance, which in turn consumes up to 90% of the total lifecycle cost of a given piece of software [9].
    [Show full text]
  • Jungledocs Documentation Release V1.0.1
    jungledocs Documentation Release v1.0.1 Sarah Scott Jul 24, 2017 Table Of Contents 1 What Is Jungle Disk? 1 1.1 Backup Solutions.............................................1 2 Setting Up Jungle Disk 3 2.1 System Requirements..........................................3 2.2 Installation................................................4 2.3 Administrator Setup...........................................7 3 Introduction to the Jungle Disk Client 13 3.1 Agent................................................... 13 3.2 Activity Monitor............................................. 18 3.3 Application Settings........................................... 20 3.4 Settings File............................................... 28 4 Backup Solutions 31 4.1 Network Drive.............................................. 31 4.2 Backup Vault............................................... 32 5 The Network Drive 33 5.1 Network Drive.............................................. 35 5.2 Local Drive Mapping........................................... 37 5.3 Previous Versions............................................ 39 6 Simple Backup 43 6.1 Simple Backup.............................................. 44 6.2 Backup Job................................................ 45 7 The Backup Vault 51 7.1 Backup Vault............................................... 54 7.2 Backup Job................................................ 54 7.3 Previous Versions............................................ 59 8 How Does The Backup Process Work? 61 8.1 Data De-Duplication..........................................
    [Show full text]
  • Register with Tarsnap Installation
    For the past year I've been working on Tarsnap GUI, an open source cross-platform frontend for the Tarsnap backup service. Tarsnap is an online, fully encrypted, deduplicated, online backup solution, that's been around for close to 10 years now (unlike other online backup offerings with a lifespan smaller than 5 years). Starting with day one, full source code for the client tools was available for review and to establish trust. A bug bounty program is available and any kind of reporting is taken seriously, promptly responded and adequately rewarded by the creator and principal developer of Tarsnap, Colin Percival. Tarsnap uses a prepaid model, you add credit to your account and you'll only pay for what you use and nothing more, no annual or monthly subscriptions. For the moment, the price per MB (SI notation) of storage (used monthly) and MB transferred is 250 picodollars each. The backend infrastructure is powered by AWS. Tarsnap was originally offered as a command-line suite of tools, in true allegiance to the Unix philosophy, very similar to the tar utility, for maximum flexibility and control over your backup routines and of great relevance for the server world. Die-hard Unix users and admins see no distinction between server administration and personal workstation and thus nothing is stopping you from backing up your personal machines and workstations the same way you would a networked server. Tarsnap GUI comes to the rescue here in filling whatever gap might be between the server and desktop workflows and for the people that like to keep real work inside the Terminal and all else contained in easy to use, slim, yet robust GUIs.
    [Show full text]
  • August 2009 Volume 34 Number 4
    AUGUST 2009 VOLUME 34 NUMBER 4 OPINION Musings 2 Rik Farrow FILE SYSTEMS Cumulus: Filesystem Backup to the Cloud 7 Michael VR able, SteFan SaVage, and geoffrey M. VoelkeR THE USENIX MAGAZINE PROGRAMMinG Rethinking Browser Performance 14 leo MeyeRoVich Programming Video Cards for ­Database Applications 21 tiM kaldewey SECURITY Malware to Crimeware: How Far Have They Gone, and How Do We Catch Up? 35 daVid dittRich HARDWARE A Home-Built NTP Appliance 45 Rudi Van dRunen CoLUMns Practical Perl Tools: Scratch the ­Webapp Itch with CGI::Application, Part 1 56 daVid n. blank-edelMan Pete’s All Things Sun: T Servers—Why, and Why Not 61 PeteR baeR galVin iVoyeur: Who Invited the Salesmen? 67 daVe JoSePhSen /dev/random 71 RobeRt g. Ferrell BooK REVIEWS Book Reviews 74 elizabeth zwicky et al. USEniX NOTES USENIX Lifetime Achievement Award 78 STUG Award 79 USENIX Association Financial Report for 2008 79 ellie young Writing for ;login: 83 ConfERENCES NSDI ’09 Reports 84 Report on the 8th International Workshop on Peer-to-Peer Systems (IPTPS ’09) 97 Report on the First USENIX Workshop on Hot Topics in Parallelism (HotPar ’09) 99 Report on the 12th Workshop on Hot Topics in Operating Systems (HotOS XII) 109 The Advanced Computing Systems Association aug09covers.indd 1 7.13.09 9:21:47 AM Upcoming Events 22n d ACM Sy M p o S i u M o n op e r A t i n g Sy S t e ms 7t H uSENIX Sy M p o S i u M o n ne t w o r k e d Sy S t e ms prinCipleS (SoSp ’09) de S i g n A n d iM p l e M e n t A t i o n (nSDI ’10) Sponsored by ACM SIGOPS in cooperation with USENIX Sponsored
    [Show full text]
  • Freenas® 11.2-U3 User Guide
    FreeNAS® 11.2-U3 User Guide March 2019 Edition FreeNAS® is © 2011-2019 iXsystems FreeNAS® and the FreeNAS® logo are registered trademarks of iXsystems FreeBSD® is a registered trademark of the FreeBSD Foundation Written by users of the FreeNAS® network-attached storage operating system. Version 11.2 Copyright © 2011-2019 iXsystems (https://www.ixsystems.com/) CONTENTS Welcome .............................................................. 8 Typographic Conventions ..................................................... 10 1 Introduction 11 1.1 New Features in 11.2 .................................................... 11 1.1.1 RELEASE-U1 ..................................................... 14 1.1.2 U2 .......................................................... 14 1.1.3 U3 .......................................................... 15 1.2 Path and Name Lengths .................................................. 16 1.3 Hardware Recommendations ............................................... 17 1.3.1 RAM ......................................................... 17 1.3.2 The Operating System Device ........................................... 18 1.3.3 Storage Disks and Controllers ........................................... 18 1.3.4 Network Interfaces ................................................. 19 1.4 Getting Started with ZFS .................................................. 20 2 Installing and Upgrading 21 2.1 Getting FreeNAS® ...................................................... 21 2.2 Preparing the Media ...................................................
    [Show full text]
  • Migrating Enterprise Storage Applications to the Cloud
    UNIVERSITY OF CALIFORNIA, SAN DIEGO Migrating Enterprise Storage Applications to the Cloud A dissertation submitted in partial satisfaction of the requirements for the degree Doctor of Philosophy in Computer Science by Michael Daniel Vrable Committee in charge: Professor Stefan Savage, Co-Chair Professor Geoffrey M. Voelker, Co-Chair Professor Bill Lin Professor Paul Siegel Professor Amin Vahdat 2011 Copyright Michael Daniel Vrable, 2011 All rights reserved. The dissertation of Michael Daniel Vrable is approved, and it is acceptable in quality and form for publication on micro- film and electronically: Co-Chair Co-Chair University of California, San Diego 2011 iii DEDICATION To my family, for all the support I’ve received. iv EPIGRAPH If I have seen further it is only by standing on the shoulders of giants. —Sir Isaac Newton v TABLE OF CONTENTS Signature Page . iii Dedication . iv Epigraph . .v Table of Contents . vi List of Figures . ix List of Tables . .x Acknowledgements . xi Vita ......................................... xiii Abstract of the Dissertation . xv Chapter 1 Introduction . .1 1.1 Cloud Computing Applications . .3 1.2 Contributions . .5 1.3 Organization . .6 Chapter 2 Background . .7 2.1 Cloud Providers . .7 2.1.1 Cloud Storage . .8 2.1.2 Cloud Computation . 12 2.2 Enterprise Storage Applications . 13 2.2.1 File System Backup . 14 2.2.2 Shared Network File Systems . 15 Chapter 3 Cumulus . 18 3.1 Related Work . 20 3.2 Design . 22 3.2.1 Storage Server Interface . 23 3.2.2 Storage Segments . 23 3.2.3 Snapshot Format . 24 3.2.4 Sub-File Incrementals .
    [Show full text]
  • Muuglines the Manitoba UNIX User Group Newsletter
    MUUGLines The Manitoba UNIX User Group Newsletter June 2011 Volume 23 No. 10 Next Meeting: June 14th, 2011 Upcoming Meetings Topic: Practical Security (Sean Cody) September 13th, 2011 For our last meeting of the season, Sean Cody will be We’ll start the 2011/2012 year with our first meeting speaking on Practical Security. The term “security” is on Tuesday, September 13th. Stay tuned (and make thrown around quite readily and its meaning has been sure you’re subscribed to one of the mailing lists) for diluted to being a product adjective as opposed to a details on that month’s presentation. process or mind set. This presentation will go over the basic theory of computer security and will attempt to Linux Kernel 3.0-RC1 Announced. equip you with the knowledge to properly evaluate computer security, products and mitigation strategies. As originally noted in a posting by Linus (http://lwn.net/Articles/445222/) the Linux kernel Where to find the Meeting branding is jumping a few points to 3.0. Meetings are held at the No, marketing firms aren’t searching for a new IBM offices at 400 internet buzzword. The kernel major revision number Ellice Ave. (between is getting renumbered to 3. Linus explains the Edmonton and Kennedy reasoning for the jump as “I can no longer [sic] Streets). When you comfortably count as high as 40.” arrive, you will have to sign in at the reception No big changes are actually expected. As usual, there desk. Please try to will be some driver updates and random fixes.
    [Show full text]
  • Freenas® 11.2-BETA2 User Guide
    FreeNAS® 11.2-BETA2 User Guide August 2018 Edition FreeNAS® is © 2011-2018 iXsystems FreeNAS® and the FreeNAS® logo are registered trademarks of iXsystems FreeBSD® is a registered trademark of the FreeBSD Foundation Written by users of the FreeNAS® network-attached storage operating system. Version 11.2 Copyright © 2011-2018 iXsystems (https://www.ixsystems.com/) CONTENTS Welcome .............................................................. 1 Typographic Conventions ..................................................... 2 1 Introduction 3 1.1 New Features in 11.2 .................................................... 3 1.2 Path and Name Lengths .................................................. 5 1.3 Hardware Recommendations ............................................... 5 1.3.1 RAM ......................................................... 6 1.3.2 The Operating System Device ........................................... 6 1.3.3 Storage Disks and Controllers ........................................... 7 1.3.4 Network Interfaces ................................................. 8 1.4 Getting Started with ZFS .................................................. 8 2 Installing and Upgrading 9 2.1 Getting FreeNAS® ...................................................... 9 2.2 Preparing the Media .................................................... 9 2.2.1 On FreeBSD or Linux ................................................ 10 2.2.2 On Windows .................................................... 10 2.2.3 On macOS .....................................................
    [Show full text]
  • Wire Security Whitepaper
    Wire Security Whitepaper Wire Swiss GmbH∗ July 19, 2021 Contents 1 Introduction 2 2 Registration 2 2.1 User Registration . .2 2.1.1 Registration by e-mail . .3 2.1.2 Registration by phone . .3 2.1.3 Passwords . .4 2.1.4 Password policy . .4 2.1.5 Further data . .4 2.2 Client registration . .5 2.2.1 Further data . .5 2.2.2 Metadata . .6 2.2.3 Notifications . .6 2.3 End-of-life of a client . .6 2.4 Push token registration . .7 3 Authentication 7 3.1 Tokens . .7 3.2 Login . .8 3.2.1 Password login . .8 3.2.2 SMS login . .9 3.3 Password Reset . .9 4 Messaging 9 4.1 End-to-end encryption . .9 4.1.1 Prekeys . .9 4.2 Message exchange and client discovery . 10 4.3 Assets . 10 4.4 Link previews . 12 4.5 Notifications . 12 ∗[email protected] 1 5 Calling 12 5.1 Call signaling . 12 5.2 Media transport . 13 5.3 Encryption . 13 5.3.1 1:1 calls . 13 5.3.2 Conference calls . 13 5.4 Encoding . 15 5.5 WebRTC . 15 6 Legal hold 15 6.1 Legal hold service . 15 6.2 Legal hold device . 16 6.3 Interaction . 16 7 Verification 16 8 Further encryption and protection 17 8.1 Transport encryption . 17 8.2 Local data protection . 17 8.3 App lock . 18 8.4 Backups . 18 A Cookie and access token format 18 1 Introduction Wire runs on Android and iOS devices, on Windows, macOS and Linux as well as on web in browsers.
    [Show full text]
  • Opinion Sysadmin File Systems Hardware Columns Book
    OCTOBER 2009 VOLUME 34 NUMBER 5 OPINION Musings 2 Rik Farrow SYSADMin Hey! I Have to Install and Maintain This Crap Too, Ya Know! 6 Thomas a. Limoncelli THE USENIX MAGAZINE XFS: The Big Storage File System­ for Linux 10 chRisToph hellwig Fixing on a Standard Language for UNIX Manuals 19 KrisTaps Dz˘ onsons FILE SYSTEMS Perspective: Semantic Data Management for the Home 24 BR anDon saL mon, Steven w. schLosseR, Lorrie FaiTh CranoR, anD GregoRy R. gangeR PROGRAMMinG Migration to Multicore: Tools That Can Help 32 Tasneem g. BRuTch HARDWARE Chips and Static Electricity 42 RuDi van DRunen COLUMNS Practical Perl Tools: Scratch the ­Webapp Itch with CGI::Application, Part 2 49 DaviD n. BLank-EdeLman Pete’s All Things Sun: VMware vSphere 4 vs. Microsoft Hyper-V R2 58 peTeR BaeR gaLvin iVoyeur: Packet-Level, Per-User Network Access Control and Monitoring 68 Dave Josephsen /dev/random 73 RoBert g. FerreLL BooK REVIEWS Book Reviews 76 ElizaBeTh zwicky eT aL. USEniX NOTES Nominating Committee for 2010 USENIX Board of Directors 79 Summary of USENIX Board of Directors Actions 79 Ellie young ConFEREncES 2009 USENIX Annual Technical Conference Reports 81 Report on the Workshop on Hot Topics in Cloud Computing (HotCloud ’09) 100 Report on BSDCan 2009: The Technical BSD Conference 107 The Advanced Computing Systems Association oct09covers.indd 1 9.4.09 10:19:48 AM Upcoming Events 23r d La r g e In s t a ll a t I o n sy s t e m ad m I n I s t r a t I o n 2010 In t e r n e t ne t w o r k ma n a g e m e n t Co n f e r e n C e (LISA ’09) wo r k s H o p (INM
    [Show full text]
  • Cloud Providers
    Basics of Cloud Computing – Lecture 2 Cloud Providers Satish Srirama Outline • Cloud computing services – recap • Amazon cloud services – Elastic Compute Cloud (EC2) – Storage services - Amazon S3 and EBS • Cloud managers • Eucalyptus 20/02/2018 Satish Srirama 2/40 Cloud Computing - Services • Software as a Service – SaaS Level of – A way to access applications Abstraction hosted on the web through your web browser SaaS • Platform as a Service – PaaS Facebook, Flikr, Myspace.com, – Provides a computing platform Google maps API, Gmail and a solution stack (e.g. LAMP) as a service PaaS • Infrastructure as a Service – Google App Engine, IaaS Force.com, Hadoop, Azure, – Use of commodity computers, Heroku, etc distributed across Internet, to IaaS perform parallel processing, distributed storage, indexing and Amazon EC2, Rackspace, mining of data GoGrid, SciCloud, etc. – Virtualization 20/02/2018 Satish Srirama 3/40 Cloud Infrastructure • Provisioning of computing resources – CPU, Memory, Processing – Basically an “Operating System” on demand • Usually billed on a per-hour usage model • Players in this space – Amazon EC2, Rackspace, GoGrid, Eucalyptus/Openstack based SciCloud • Management providers: RightScale, HybridFox, ElasticFox, Amazon Management Console 20/02/2018 Satish Srirama 4/40 Cloud Storage • Provisioning of data storage – Either file/object based or Database like functionality • Billed on bandwidth and storage consumed • Players in the space – Amazon S3, Amazon EBS – Amazon’s SimpleDB, Google’s BigTable, Apache Cassandra • Management
    [Show full text]