DOCSLIB.ORG

A Trust System for the Opensuse Build Service

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Trust System for the Opensuse Build Service Bachelor Thesis A Trust System for the openSUSE Build Service Saarland University Faculty of Natural Sciences and Technology I Department of Computer Science submitted by Marko Jung on 17th April 2009 Supervisor Professor Dr.-Ing. Thorsten Herfet Advisor Dr. Michael Schröder Reviewers Professor Dr.-Ing. Thorsten Herfet Professor Dr. Joachim Weickert Statement under Oath & Declaration of Consent I hereby confirm under oath that I have written this thesis on my own and that I have not used any other media or materials than the ones referred to in this thesis. I agree to make both versions of my thesis (with a passing grade) accessible to the public by having them added to the library of the Computer Science Department. Saarbrücken, 17th April 2009. Marko Jung Contents 1 Introduction 1 1.1 openSUSE Build Service . .1 1.2 Trust ......................................................3 1.2.1 Definitions of Trust . .4 1.2.2 Properties of Trust . .5 1.2.3 Trust Metrics . .6 1.3 Aim of the Study . .7 1.4 Outline of the Thesis . .7 2 Notation and Terminology9 2.1 Notation . .9 2.2 Terminology . .9 3 State of the Art 11 3.1 Classification of Trust Metrics . 12 3.1.1 Network Perspective . 12 3.1.2 Computation Locus . 13 3.1.3 Link Evaluation . 13 3.1.4 Selection Method . 14 3.2 Trust Metrics . 14 3.2.1 PageRank . 15 3.2.2 EigenTrust . 16 3.2.3 Advogato . 19 3.2.4 TidalTrust . 21 3.2.5 Appleseed . 23 4 Architecture 29 4.1 openSUSE Build Service Terminology . 29 4.2 Major Components of the openSUSE Build Service . 31 4.3 Trust for Software Packages . 34 4.4 User-specific Trust . 35 v 4.5 Design of the openSUSE Trust Server . 36 4.5.1 Management of Trust Relations . 37 4.5.2 Management and Storage of Trust Formulae . 39 4.5.3 Solving of Trust Formulae using Appleseed . 40 5 Validation 43 5.1 Artificial Networks . 43 5.1.1 Random Graphs . 43 5.1.2 Small-world Model . 48 5.1.3 Model of Barabási and Albert . 52 5.2 Advogato Real-world Network . 58 5.2.1 Data Sets . 59 5.2.2 Leave-one-out Cross-validation . 61 6 Discussion 65 6.1 Computation of Trust using the Appleseed Trust Metric . 65 6.2 Validation using artificially generated Networks . 67 6.3 Validation using the Advogato Data Set . 68 7 Outlook 71 A Mathematical Symbols and Functions 73 B Appleseed Example 75 C Trust Metric Algorithms 77 C.1 The PageRank Algorithm . 77 C.2 EigenTrust Algorithms . 78 C.2.1 Simple non-distributed EigenTrust . 78 C.2.2 Basic EigenTrust . 78 C.2.3 Distributed EigenTrust . 79 C.3 Advogato . 80 C.4 TidalTrust . 81 C.5 Appleseed . 83 D Further Simulations using the Small-world Model 85 D.1 Rewiring Probability p=0.30 ..................................... 86 D.2 Rewiring Probability p=0.45 ..................................... 88 D.3 Rewiring Probability p=0.60 ..................................... 90 D.4 Rewiring Probability p=0.75 ..................................... 92 D.5 Rewiring Probability p=0.90 ..................................... 94 Acknowledgements 97 Bibliography 99 List of Figures 1.1 openSUSE Build Service web-client . .2 3.1 Properties of Trust Metrics . 12 3.2 Scalar vs Group Trust Metrics . 13 3.3 PageRank: Simplified PageRank Calculation . 15 3.4 Advogato: Graph conversion . 20 3.5 Advogato: Calculation of the Network Flow . 22 3.6 TidalTrust: Determination of the Trust Threshold . 22 3.7 Appleseed: Node Chains . 24 3.8 Appleseed: Rank Sinks . 24 3.9 Appleseed: Normalisation Issue . 24 3.10 Appleseed: Backward Propagation . 24 3.11 Appleseed: Distribution of Trust and Distrust . 27 4.1 Example for an openSUSE Build Service Project . 30 4.2 Major Components of the openSUSE Build Service . 32 4.3 openSUSE Trust Service Web-Interface listing Trust Relations . 37 4.4 openSUSE Trust Service Web-Interface presenting a Trust Value . 41 5.1 Random Graphs: Example . 44 5.2 Random Graphs: General statistics . 46 5.3 Random Graphs: Maximal distributed Trust . 47 5.4 Random Graphs: Maximal distributed Trust vs discovered Nodes . 47 5.5 Small-world Model: Example . 48 5.6 Small-world Model: General Statistics . 50 5.7 Small-world Model: Maximal distributed Trust . 51 5.8 Small-world Model: Maximal distributed Trust vs discovered Nodes . 51 5.9 Model of Barabási and Albert: Example . 53 5.10 Model of Barabási and Albert using linear preferential Attachment: General Statistics . 54 5.11 Model of Barabási and Albert using quadratic preferential Attachment: General Statistics . 55 5.12 Model of Barabási and Albert using linear preferential Attachment: Maximal distributed Trust . 56 5.13 Model of Barabási and Albert using linear preferential Attachment: Maximal distributed Trust vs discovered Nodes . 56 5.14 Model of Barabási and Albert using quadratic preferential Attachment: Maximal distributed Trust . 57 5.15 Model of Barabási and Albert using quadratic preferential Attachment: Maximal distributed Trust vs discovered Nodes . 57 5.16 Advogato Data Set: Maximal distributed Trust vs discovered Nodes . 59 5.17 Advogato Data Set: General Statistics . 60 5.18 Advogato Data Set: Histograms for general Statistics . 60 5.19 Advogato Data Set: ROC Plots . 63 5.20 Advogato Data Set: Sensitivity vs Specificity Plot and Recall vs Precision Plot . 63 B.1 Appleseed: Test Network . 75 D.1 Small-world Model: General Statistics (p = 0.30) . 86 D.2 Small-world Model: Maximal distributed Trust (p = 0.30) . 87 D.3 Small-world Model: Maximal distributed Trust vs discovered Nodes (p = 0.30) 87 D.4 Small-world Model: General Statistics (p = 0.45) . ..
Load more

Recommended publications
  • KDE E.V. Quarterly Report 2008Q3/Q4
    Quarterly Report Q3/2008 & Q4/2008 solid accounting and valuable organizational skills month after month, year after year. As such, I am more than confident in his stepping into the President's chair. Cornelius will also benefit from the solid board members that have helped us build KDE e.V. over the past few years into what it has become. We should all be quite proud of what we have achieved Dear KDE e.V. member, within this organization. It has never been as robust, professional and effective. In the spirit of continuous When one is busy, time flies by quicker than one expects. improvement, I am equally sure we will be able to say the They say the same thing happens when you're having fun. same thing in five years time. When I look at the calendar and realize that we're already into the second month of 2009, I'm struck with just how I would also take this opportunity to ask each and every quickly 2008 melted away. It's safe to say that we were one of the members of our society to examine their own both hard at work and having fun in the process. involvement within KDE e.V. It operates smoothly only because we have members who step up and help get things Going forward, we have a series of very exciting programs done. We achieve things together that we can not achieve underway, probably not least of which is a new Individual alone. Supporting Members program. We also have the Gran Canaria Desktop Summit, which is an experiment in co- These activities range from the simple task of voting (and locating Akademy with GUADEC.
    [Show full text]
  • KDE E.V. Quarterly Report 2005Q3 (Issue 1)
    KDE e.V. Quarterly Report October 2005 .init() KDE League Wrap Up After a post-aKademy email exchange and an in-person meeting Dear KDE e.V. member, with Andreas Pour in San Diego, there is forward momentum on the matter of dealing with the remnants of the KDE League. We At the enjoyable and successful aKademy 2005 in Spain, KDE are currently waiting upon Andreas to draft a letter of indemnity for e.V. took several important strides forward in its ongoing the transfer of the remaining funds so as to be able to move evolution. Among these decisions was the election of a new forward. We have a deadline of Dec 31st at which time Andreas board consisting of two new members and two incumbents. will no longer be associated with the KDE League in an official Those of us on the board thank everyone for their vote of capacity, making recovering the funds that much more difficult confidence and are looking to do our best to reward that trust. after the deadline. Much more than electing a new board was accomplished, Board Business and Processes however. The e.V. voted to start a trio of working groups focused The new board is now functioning and the day-to-day tasks on marketing, technical issues, and the human-computer carried out by previous members have been picked up by their interface. The e.V. also moved for greater openness (this report replacements. An in person meeting of the board is scheduled for being an example of that) as well as more financial and physical the 4th and 5th of December.
    [Show full text]
  • The Korganizer Handbook
    The KOrganizer Handbook Carlos Leonhard Woelz Milos Prudek Paul E. Ahlquist, Jr. Jürgen Nagel Michel Boyer de la Giroday Developer: Reinhold Kainhofer Developer: Cornelius Schumacher Developer: Preston Brown Reviewer: Lauri Watts The KOrganizer Handbook 2 Contents 1 Introduction 7 2 Five-minute Fly-over Course of KOrganizer9 2.1 Entering Events . .9 2.2 Entering To-dos . .9 2.3 Adding Journal Entries . 10 2.4 Rescheduling Events . 10 2.5 Rescheduling or Editing To-dos . 10 2.6 Conclusion . 10 3 Importing, Exporting, and Managing Calendars 11 3.1 Calendar Resources . 11 3.2 Importing, Exporting and Maintaining Calendars . 13 3.2.1 Importing Calendars . 13 3.2.2 Exporting Calendars . 13 3.2.3 Maintaining Your Calendars . 13 3.3 Downloading Using Get Hot New Stuff . 14 4 Views and Filters 15 4.1 KOrganizer Views . 15 4.1.1 What’s Next View . 16 4.1.2 Event List View . 16 4.1.3 Agenda View . 16 4.1.3.1 Day View . 17 4.1.3.2 Next X Days View . 17 4.1.3.3 Week View . 17 4.1.3.4 Work Week View . 17 4.1.4 Month View . 18 4.1.5 Timeline View . 18 4.1.6 To-do List . 18 4.1.7 Journal View . 19 4.2 Tags.............................................. 19 4.3 Filters . 19 4.4 Searching . 19 The KOrganizer Handbook 5 Entering Data 21 5.1 Events . 21 5.1.1 General Tab . 22 5.1.2 Attendees Tab . 23 5.1.3 Reminder Tab . 24 5.1.4 Recurrence tab .
    [Show full text]
  • Config.Xml File Part I
    KIWI Building OS images and Appliances Robert Schweikert Software Engineer Consultant Novell Welcome and Introduction Who am I •Robert Schweikert • Work in ISV Engineering team – Work closely with IBM – Work on appliances with other ISVs as time permits • Contribute to Kiwi • Contribute to the openSUSE project • Active member of the LSB work group • Nuts about soccer © August 7, 2010 Novell Inc. 3 What is covered ? Outline (1/2) •Welcome and Introduction •Preliminaries • What is Kiwi • Setting up a Kiwi build • High level Kiwi image build process overview • Kiwi documentation resources • Using the Kiwi build environment •Using Kiwi • The Kiwi configuration tree • Kiwi configuration – the config.xml file part I © August 7, 2010 Novell Inc. 5 Outline (2/2) • Kiwi configuration – the config.xml file part II • Exploring image types • Kiwi configuration – the config.sh file • Kiwi configuration – the images.sh file • The overlay file system • What is an appliance • Build an appliance •Summary •Final Questions, Thoughts, Comments © August 7, 2010 Novell Inc. 6 Preliminaries What is Kiwi •It's a Fruit •It's a Bird •It's someone from New Zealand •It is a Linux image build system • Kiwi is an open source project hosted at kiwi.berlios.de licensed under GPL v2 with roots in the openSUSE build service. • Kiwi is mostly written in Perl • Kiwi is the engine behind SUSE Studio © August 7, 2010 Novell Inc. 8 Setting up a Kiwi build environment •root access is required •Kiwi is part of the openSUSE standard repository •Kiwi is part of the SLE-SDK • Add the SDK as a repository through YaST • Detailed description at http://www.novell.com/communities/node/10464/step-step-guide-set-kiwi-build-environment-sle •Live on the bleeding edge http://download.opensuse.org/repositories/Virtualization:/Appliances/ •In YaST or via zypper search for kiwi, install the packages © August 7, 2010 Novell Inc.
    [Show full text]
  • SUSE Brainshare Template 2004
    openSUSE – The Project Martin Lasarsch Michael Löffler SUSE Linux Products GmbH Overview • Goals • What is the openSUSE project? • What changed since last year? • What will change in the Future? Feb. 2007 2 Goals • distribution • open development • developers from the community • best distribution Feb. 2007 3 What is the openSUSE project? • Communication - Wiki - Mailinglists - IRC • Distribution - released version - alpha/beta/rc - factory - bugzilla • openSUSE Build Service (OBS) - web, gui, cli frontend - Builds for: 9.3-10.2, SLE, Factory Fedora, Mandriva, Debian, Ubuntu Feb. 2007 - x86, x86_64 4 What changed since last year? • Communication - Wiki - new Languages, new Layout, Splashpage - 1500 pages, 16 languages - Mailinglists - migration from @suse.de to @opensuse.org - internal lists moved to public (dist, packager) - new webinterface for archive, new lists - IRC - more, special purpose meetings (yast, community) - #opensuse, #opensuse-project Feb. 2007 5 What changed since last year? • Distribution - SUSE Linux 10.1 - openSUSE 10.2 - more bugs from outside - less bugs for 10.2 - more bandwith for download peaks Feb. 2007 6 What changed since last year? • openSUSE Build Service - public - 100% open source now! - new webinterface (search, monitor) - new clients, osc, richclient - more targets - link projects - Factory sync - build against updates Feb. 2007 7 Challenges • zmd 10.1 • M$/Novell deal • Money • openSUSE office • opensource build service • more SUSE/Novell people working on the project Feb. 2007 8 Ideas for the future? • sponsoring (hardware, money) • guiding principles • local communities • Linux hardware database • rating system obs • distribution in buildservice • easier obs integration in distribution • integration of internal autobuild with obs • merchandising Feb. 2007 9 Q&A General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product.
    [Show full text]
  • SUSE Linux Enterprise Server
    SUSE Best Practices How to Modify a Package in the Open Build Service Quilting with OSC SUSE Linux Enterprise Server Josef Moellers, Senior Developer SUSE Linux Enterprise Network Services, SUSE 1 How to Modify a Package in the Open Build Service This document leads you through the process of modifying a software package in the Open Build Service (OBS) using the osc and quilt tools. It also discusses simple error cases, based upon the author’s own experiences, but it does not attempt to be a full manual or to cover all options. The steps described here should work well, but if you encounter any diculties, you should consult the manuals or ask an expert for help. This document does not intend to provide a guide for the Open Build Service. If you want to learn more about OBS, visit the project’s Web page at http://openbuildservice.org/ and read the specic documentation there http://openbuildservice.org/help/ Publication Date: March 13, 2018 Contents 1 Introduction: Open Build Service and the Tools osc and quilt 3 2 Repositories and Projects 5 3 Package 10 4 Getting the Package 11 5 Working on the Sources 15 6 Build the Package 22 7 Test 23 8 Submit 23 9 Propagate a patch 24 10 Conclusion 25 11 Legal Notice 26 12 GNU Free Documentation License 27 2 How to Modify a Package in the Open Build Service 1 Introduction: Open Build Service and the Tools osc and quilt The Open Build Service command line client osc is a tool developed to interact with OBS servers.
    [Show full text]
  • SUSE® Linux Enterprise Adopting Upstream Innovation
    Open Enterprise & Open Community openSUSE & SLE – Empowering Each Other Richard Brown openSUSE Chairman [email protected] Contents ● Introduction to the openSUSE Project ● Looking Back - 2014 and before ● Rolling into the Future with Tumbleweed ● openSUSE and SUSE Linux Enterprise ● Closing the gap with one giant Leap.. 2 Introduction to openSUSE 3 openSUSE ● Open Source Community Project sponsored by SUSE ● Founded 9th August 2005 ● “Promotes the use of Linux everywhere” ● Produces the openSUSE distribution 4 11 years old! CC-BY lawrencedesign @ flickr.com 5 Q Q wicked snapper Evergreen 6 openSUSE distribution ● Consumer/'Conservative Enthusiast' focus ● Successor to the 'SUSE® Linux' Boxed distribution ● First release was 'SUSE Linux 10.0' in October 2005 ● Renamed 'openSUSE' with 10.2 in December 2006 ● openSUSE 13.2 was released on 4th November 2014 ● Our 14th release! ● Over 7000 source packages (& many more in OBS) 7 8 Before Nov 2014 - A bit of a muddle.. openSUSE Factory • Development Branch (Constant Updates) openSUSE Tumbleweed • ‘Partially Rolling’ (Frozen Base + Updates) openSUSE • Regular Releases (Every 8-12 months) openSUSE Evergreen • 'Long Duration Support' (Patches for extra years) 9 Time for Reflection “Who are we making this for?” “Why should I use openSUSE?” “Why should I contribute to openSUSE?” “What makes openSUSE special?” 10 “The openSUSE Project is a worldwide effort that promotes the use of Linux everywhere.” - openSUSE wiki 11 Areas of Strength Tools • Open Build Service • openQA • YaST • Etc.. Packages • Broad Variety Distributions • Tumbleweed • Regular Release 12 “Man is a tool-using animal. Without tools he is nothing, with tools he is all” - Thomas Carlyle 13 Building Linux Better Open Build Service started in February 2006 Used to build the openSUSE® & SUSE® distributions Can also build packages for other distributions (Fedora/Red Hat, Ubuntu, Debian, Arch, etc) Also used by ownCloud, Linux Foundation, VideoLAN (VLC), Dell, Cray, Intel and more.
    [Show full text]
  • Gl615 Linux for Unix Administrators Rhel7 Sles12
    EVALUATION COPY Unauthorized Reproduction or Distribution Linux for Unix AdministratorsProhibited Student Workbook EVALUATION COPY Unauthorized Reproduction GL615 LINUX FOR UNIX ADMINISTRATORS RHEL7 SLES12 or Distribution The contents of this course and all its modules and related materials, including handouts to audience members, are copyright ©2017 Guru Labs L.C. No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including, but not limited to, photocopy, photograph, magnetic, electronic or other record, without the prior written permission of Guru Labs. This curriculum contains proprietary information which is for the exclusive use of customers of Guru Labs L.C., and is not to be shared with personnel other than those in attendance at this course. This instructional program, including all material provided herein, is supplied without any guarantees from Guru Labs L.C. Guru Labs L.C. assumes no liability for damages or legal action arising from Prohibited the use or misuse of contents or details contained herein. Photocopying any part of this manual without prior written consent of Guru Labs L.C. is a violation of federal law. This manual should not appear to be a photocopy. If you believe that Guru Labs training materials are being photocopied without permission, please email [email protected] or call 1-801-298-5227. Guru Labs L.C. accepts no liability for any claims, demands, losses, damages, costs or expenses suffered or incurred howsoever arising from or in connection with the
    [Show full text]
  • Excerps for Unixdive
    Android Android (As of 2015, Android has the largest installed base of all operating systems world-wide) Largely from https://en.wikipedia.org/wiki/Android_(operating_system) Android, Inc. was founded in Palo Alto, California in October 2003 by Andy Rubin (co-founder of Danger), Rich Miner (co-founder of Wildfire Communications, Inc.), Nick Sears (once VP at T-Mobile), and Chris White (headed design and interface development at WebTV to develop, in Rubin's words, "smarter mobile devices that are more aware of its owner's location and preferences". In July 2005, Google acquired Android Inc. for at least $50 million, whose key employees, including Rubin, Miner and White, stayed at the company after the acquisition. On November 5, 2007, the Open Handset Alliance, a consortium of technology companies including Google, device manufacturers such as HTC, Sony and Samsung, wireless carriers such as Sprint Nextel and T-Mobile, and chipset makers such as Qualcomm and Texas Instruments, unveiled itself, with a goal to develop open standards for mobile devices. That day, Android was unveiled as its first product, a mobile device platform built on the Linux kernel. The first commercially available smartphone running Android was the HTC Dream, released on October 22, 2008. Android's source code is released by Google under open source licenses, although most Android devices ultimately ship with a combination of open source and proprietary software, including proprietary software required for accessing Google services. Android is popular with technology companies that require a ready-made, low-cost and customizable operating system for high-tech devices. Its open nature has encouraged a large community of developers and enthusiasts to use the open-source code as a foundation for community-driven projects, which add new features for advanced users or bring Android to devices originally shipped with other operating systems.
    [Show full text]
  • Linux Distributions
    04_776130 ch01.qxp 2/2/07 10:11 PM Page 1 Working with Linux One of the biggest stumbling blocks when writing software for Linux is understanding what Linux is and is not. Linux means different things to different people. Technically, Linux itself is an operating system kernel written by the Finnish born Linus Torvalds, though most people today casually refer to an entire Linux-based system by the same name. In just a few years, Linux has risen from obscurity and become widely accepted by some of the largest and most powerful com- puting users on the planet. Linux is now a big-money, enterprise-quality operating system. It’s used in some of the largest supercomputers and also many of the smallest gadgets, which you would never expect to have Linux underneath. Yet for all its prevalence — for such a big name in modern computing — Linux isn’t owned by any one corporation that pulls the strings. Linux is so successful because of the many thousands of developers around the world who constantly strive to make it better. They, like you, are interested in writing high-quality software that draws upon the experience of others within the Linux community. Whatever Linux means to you, you’re reading this book because you’re interested in learning more about becoming a professional Linux programmer. As you embark on this journey, you will find it helpful to tool yourself up with an understanding of the different flavors of Linux, how to get going in developing for them, and how working with Linux differs from working with many other popular platforms on the market today.
    [Show full text]
  • PC Magazine® Linux® Solutions
    PC Magazine® Linux® Solutions Joe Merlino PC Magazine® Linux® Solutions Joe Merlino PC Magazine® Linux® Solutions PC Magazine® Linux® Solutions Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2006 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN-13: 978-0-471-77769-4 ISBN-10: 0-471-77769-2 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 1B/SY/QT/QW/IN No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions. Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation.
    [Show full text]
  • Alternative Linux Distributions for POWER Processor-Based Systems a Review of Unsupported Linux Distributions Running on POWER5
    Alternative Linux distributions for POWER processor-based systems A review of unsupported Linux distributions running on POWER5 ........ John Engel & Brent Baude IBM eServer Solutions Enablement January 2006 © Copyright IBM Corporation, 2006. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders Table of Contents Abstract..................................................................................................................................... 4 Introduction .............................................................................................................................. 4 Distribution test environments................................................................................................ 4 Standalone with a video card................................................................................................................... 4 Standalone with a serial console ............................................................................................................. 5 Logical partition........................................................................................................................................ 5 IBM-related software packages ............................................................................................... 6 iprutils....................................................................................................................................................... 6 ppc64utils and librtas ..............................................................................................................................
    [Show full text]