Zarządzanie Zasobami Gridowymi Z Użyciem Parawirtualizacji

Total Page:16

File Type:pdf, Size:1020Kb

Zarządzanie Zasobami Gridowymi Z Użyciem Parawirtualizacji Wydział Elektrotechniki, Automatyki, Informatyki i Elektroniki Akademii Górniczo-Hutniczej im. St. Staszica w Krakowie Zarządzanie zasobami gridowymi z użyciem parawirtualizacji Rozprawa doktorska Jacek Kosiński Promotor: prof. dr hab. inż. Krzysztof Zieliński Kraków, Styczeń 2009 Serdecznie dziękuję wszystkim osobom, które wspierały mnie w czasie pisania tej pracy. W szczególności chciałbym podziękować mojemu promoto- rowi Panu prof. dr hab. inż. Krzysztofowi Zielińskiemu za wszechstronną pomoc oraz wnikliwe i konstruktywne uwagi. Pragnę także podziękować za pomoc kolegom z Grupy Systemów Rozproszonych Katedry Informatyki AGH. Chciałbym także okazać wdzięczność mojej Rodzinie oraz Przyjaciołom za cierpliwość i zrozumienie wykazywane dla mojego zaangażowania w tę rozprawę. Jacek Kosiński Spis treści Podziękowania iii Spis rysunków ix Spis tabel xiii Kod źródłowy xv 1. Wprowadzenie 1 1.1. Definicje ...................................... 2 1.2. Cel rozprawy ................................... 9 1.3. Teza pracy .................................... 10 1.4. Zakres rozprawy ................................. 11 1.5. Osiągnięcia autora ................................ 11 1.6. Struktura pracy .................................. 12 2. Technologie leżące u podstaw pracy 15 2.1. Wirtualizacja systemów komputerowych .................... 15 2.1.1. Izolacja zasobów wirtualnego komputera . 18 2.1.2. Migracja maszyny wirtualnej ...................... 20 2.2. Wirtualizacja sieci komputerowej ........................ 23 2.2.1. Lokalna komunikacja sieciowa ...................... 24 2.2.2. Komunikacja w sieci rozległej ...................... 29 2.2.3. Zarządzanie komunikacją w wirtualnej sieci . 29 2.2.4. Migracja w wirtualnej sieci ....................... 31 2.2.5. Wirtualna sieć Ethernet ......................... 32 2.3. Implementacje technik wirtualizacji ....................... 33 2.3.1. UML — User Mode Linux ........................ 35 2.3.2. OpenVZ — Open Virtuozzo ....................... 36 2.3.3. Projekt Linux-VServer .......................... 38 2.3.4. KVM — Kernel Based Virtualization Driver . 39 2.3.5. Xen — Virtual Machine Monitor .................... 41 2.3.6. Porównanie technik wirtualizacji .................... 45 2.4. Podsumowanie .................................. 45 v vi Spis treści 3. Przedstawienie problemu i sformułowanie wymagań 49 3.1. Charakterystyka istniejących systemów Grid . 49 3.2. Główne założenia pracy ............................. 50 3.2.1. Dostosowanie środowiska do charakterystyki aplikacji . 51 3.2.2. Izolacja aplikacji i wsparcie dla jakości usługi . 51 3.2.3. Tworzenie wirtualnych topologii sieciowych . 52 3.2.4. Adaptowalność do zmiennych wymagań . 53 3.3. Analiza wymagań ................................. 54 3.3.1. Wymagania ogólne dla systemów zarządzania zasobami . 54 3.3.2. Wymagania funkcjonalne ........................ 56 3.3.3. Wymagania niefunkcjonalne ....................... 60 3.3.4. Klasy zastosowań systemu ........................ 62 3.4. Ogólna koncepcja realizacji systemu ...................... 62 3.5. Podsumowanie .................................. 63 4. Model systemu zarządzania zwirtualizowanymi zasobami 65 4.1. Model systemu .................................. 65 4.1.1. Wykorzystywane pojęcia i określenia . 67 4.1.2. Model statyczny wirtualnego Gridu ................... 69 4.1.3. Model dynamiczny wirtualnego Gridu . 74 4.1.4. Model systemu zarządzania zasobami . 78 4.2. Podsumowanie .................................. 81 5. Architektura systemu VGRMS 83 5.1. Podstawowe założenia projektowe ........................ 83 5.1.1. Komponenty pasywne systemu ..................... 83 5.1.2. Komponenty aktywne systemu ..................... 85 5.1.3. Hierarchiczna koncepcja zarządzania . 86 5.2. Warstwowa architektura systemu ........................ 91 5.2.1. Warstwa zasobów fizycznych ...................... 91 5.2.2. Warstwa wirtualizacji .......................... 92 5.2.3. Warstwa ekspozycji ........................... 93 5.2.4. Warstwa zarządzania ........................... 98 5.2.5. Warstwa prezentacji . 105 5.3. Konfiguracje systemu VGRMS . 108 5.4. Podsumowanie ..................................108 6. Implementacja systemu 111 6.1. Technologie implementacji elementów systemu VGRMS . 111 6.1.1. Implementacja głównych komponentów systemu . 112 6.1.2. Komponenty węzła VGRMS . 113 6.1.3. Zarządzanie wirtualną topologią sieciową . 122 6.2. Graficzny klient systemu VGRMS . 124 6.3. Organizacja implementacji ............................129 6.3.1. Propagacja zdarzeń w systemie . 132 Spis treści vii (207) 6.4. Podsumowanie ..................................133 7. Testy systemu 135 7.1. Metodologia testów ................................135 7.1.1. Konfiguracje testowe . 136 7.1.2. Scenariusze przeprowadzenia pomiarów . 140 7.1.3. Metryki wydajnościowe . 148 7.2. Ocena zastosowanych technologii . 152 7.2.1. Wydajność i optymalizacja procesu migracji . 152 7.3. Wyniki praktycznej weryfikacji właściwości systemu . 159 7.3.1. Eksperyment 1 — Zadane rozmieszczenie VM . 160 7.3.2. Eksperyment 2 — Optymalizacja komunikacji sieciowej . 163 7.3.3. Eksperyment 3 — Awaria fizycznego węzła . 167 7.3.4. Eksperyment 4 — Zastosowanie gwarancji QoS . 168 7.3.5. Eksperyment 5 — Wykorzystanie migracji VM . 171 7.4. Podsumowanie ..................................172 8. Podsumowanie 175 8.1. Weryfikacja tezy pracy ..............................175 8.2. Nowatorstwo pracy ................................176 8.3. Braki systemu ...................................177 8.4. Możliwości dalszego rozwoju . 177 A. Kod źródłowy głównych komponentów systemu 179 A.1. Komponenty zarządzania konfiguracją wirtualnych maszyn . 179 A.1.1. Obsługa parawirtualizacji środowiska Xen . 179 A.1.2. Zarządzanie wirtualną maszyną . 180 A.1.3. Zarządzanie wirtualnym Gridem . 181 A.2. Zarządzanie polityką działania systemu . 182 A.3. Monitorowanie wykorzystania zasobów . 183 B. Reguły modułu decyzyjnego 185 B.1. Przydział zasobów dla wirtualnych maszyn . 185 B.1.1. Przydział zasobów zgodnie z przyjętą polityką QoS . 186 B.2. Zarządzanie i obsługa migracji wirtualnych maszyn . 186 B.2.1. Monitorowanie parametrów środowiskowych . 187 B.2.2. Monitorowanie komunikacji sieciowej . 188 Bibliografia 189 Skorowidz 197 Definicje 201 Wykaz skrótów 203 Spis rysunków 1.1 Taksonomia stosowanych obecnie architektur typu Grid ........... 3 1.2 Poziomy wirtualizacji w systemach informatycznych ............. 7 1.3 Dwuetapowy model powiązań zasobów do aplikacji .............. 9 2.1 Tworzenie wirtualnej sieci z wykorzystaniem techniki przełączania . 25 2.2 Tworzenie wirtualnej sieci z wykorzystaniem technik tunelowania . 26 2.3 Tworzenie wirtualnej sieci z wykorzystaniem routingu . 27 2.4 Etapy zarządzania komunikacją sieciową wirtualnych maszyn . 30 2.5 Schemat budowy wirtualnej rozproszonej sieci Ethernet . 33 2.6 Obsługa migracji VM w wirtualnej sieci Ethernet . 34 2.7 Architektura wirtualizacji z nadzorcą ...................... 40 2.8 Architektura systemu KVM ........................... 41 2.9 Architektura systemu Xen ............................ 42 4.1 Klasyczny system zarządzania zasobami .................... 66 4.2 System zarządzania zwirtualizowanymi zasobami . 67 4.3 Przykład topologii fizycznej wirtualnego Gridu . 72 4.4 Pętla zarządzania dla modelu systemu ..................... 80 5.1 Możliwe powiązania komponentów aktywnych i pasywnych . 84 5.2 Taksonomia zasobów w środowiskach przetwarzania rozproszonego . 84 5.3 Hierarchiczna koncepcja zarządzania zasobami w systemie VGRMS . 86 5.4 Komponenty składowe lokalnego zarządcy zasobów . 87 5.5 Interakcje lokalnego zarządcy zasobów ..................... 88 5.6 Interakcje globalnego zarządcy zasobów .................... 90 5.7 Komponenty składowe globalnego zarządcy zasobów . 90 5.8 Warstwy funkcjonalne systemu zarządzania zasobami . 91 5.9 Komponenty składowe warstwy wirtualizacji . 93 5.10 Proces wyszukiwania komponentów systemu VGRMS . 95 5.11 Komponenty składowe warstwy ekspozycji ................... 96 5.12 Relacje pomiędzy głównymi komponentami zarządzania stanem i konfigu- racją fizycznego węzła .............................. 97 5.13 Hierarchia komponentów zarządzania systemu VGRMS . 99 5.14 Komponenty warstwy zarządzania systemu VGRMS . 100 ix x Spis rysunków 5.15 Funkcjonalność udostępniana przez repozytorium polityk zarządzania zaso- bami ........................................101 5.16 Reprezentacja informacji o aktualnym stanie węzła, wirtualnej maszyny i wirtualnego Gridu w postaci faktów przetwarzanych przez silnik regułowy 102 5.17 Reprezentacja informacji pochodzących z monitorowania komunikacji sie- ciowej w postaci faktów .............................102 5.18 Transformacja informacji o stanie infrastruktury do postaci faktów . 103 5.19 Interakcje komponentów systemu przy tworzeniu wirtualnego Gridu . 105 5.20 Sekwencja interakcji komponentów systemu podczas inicjalizacji konsoli za- rządzania .....................................106 5.21 Zarządzanie cyklem życia maszyny wirtualnej przez administratora z uży- ciem konsoli ....................................106 5.22 Tworzenie wirtualnego Gridu wykonywane przez administratora z użyciem konsoli .......................................107 5.23 Rodzaje zarządzania przydziałem zasobów w systemie VGRMS . 108 5.24 Rozmieszczenie komponentów systemu VGRMS w środowisku rozproszonym 109 6.1 Przechwytywanie zdarzeń środowiska Xen i podejmowanie odpowiednich akcji przez komponenty zarządzania stanem węzła . 114 6.2 Propagacja zdarzenia pomiędzy komponentami VGRMS o usunięciu
Recommended publications
  • (D-Suite) Version 5.0 Voting System
    700 Boulevard South Suite 102 Huntsville, AL 35802 Phone (256)713-1111 Fax (256)713-1112 Test Report for EAC 2005 VVSG 1.0 Certification Testing Dominion Voting Systems Democracy Suite (D-Suite) Version 5.0 Voting System EAC Project Number: DVS1601 Version: Revision A Date:1/6/17 TR-01-01-DVS-2016-01.01 Rev. A REVISIONS Revision Description Date NR Initial Release 12/2/16 A Address EAC Comments 1/6/17 TR-01-01-DVS-2016-01.01 Rev. A TABLE OF CONTENTS 1.0 INTRODUCTION.......................................................................................................................... 1 1.1 System Identification and Overview ................................................................................................ 1 1.1.1 Software .............................................................................................................................. 3 1.1.2 Hardware ........................................................................................................................... 12 1.1.3 Block Diagram .................................................................................................................. 14 1.1.4 System Limits ................................................................................................................... 15 1.1.5 Supported Languages ........................................................................................................ 16 1.1.6 Supported Functionality ...................................................................................................
    [Show full text]
  • Improving the Beaglebone Board with Embedded Ubuntu, Enhanced GPMC Driver and Python for Communication and Graphical Prototypes
    Final Master Thesis Improving the BeagleBone board with embedded Ubuntu, enhanced GPMC driver and Python for communication and graphical prototypes By RUBÉN GONZÁLEZ MUÑOZ Directed by MANUEL M. DOMINGUEZ PUMAR FINAL MASTER THESIS 30 ECTS, JULY 2015, ELECTRICAL AND ELECTRONICS ENGINEERING Abstract Abstract BeagleBone is a low price, small size Linux embedded microcomputer with a full set of I/O pins and processing power for real-time applications, also expandable with cape pluggable boards. The current work has been focused on improving the performance of this board. In this case, the BeagleBone comes with a pre-installed Angstrom OS and with a cape board using a particular software “overlay” and applications. Due to a lack of support, this pre-installed OS has been replaced by Ubuntu. As a consequence, the cape software and applications need to be adapted. Another necessity that emerges from the stated changes is to improve the communications through a GPMC interface. The depicted driver has been built for the new system as well as synchronous variants, also developed and tested. Finally, a set of applications in Python using the cape functionalities has been developed. Some extra graphical features have been included as example. Contents Contents Abstract ..................................................................................................................................................................................... 5 List of figures .........................................................................................................................................................................
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • Practical Debian Administration
    Practical Debian Administration Alexander Zangerl [email protected] Abstract Debian GNU/Linux offers a very rich and well-designed environment to a system administrator. This talk is about the most important tasks you will face on any Debian box, and how to deal with them most efficiently; I will also present some of the less well-known (but in my opinion still quite interesting) Debian-specific tools and approaches that can make administrating a Debian system very pleasant. 1 Debian in a Nutshell Debian is a free, volunteer-produced Linux/Unix Operating System Distribution. As I pointed out in some detail in a previous paper[1], Debian is very well suited for experienced Unix users as well as large scale environments for a variety of reasons; we might very well call Debian \The Distribution for Sysadmins by Sysadmins". The biggest difference[5] between Debian and other operating system distributions is that Debian uses a very extensive policy and stringent quality assurance processes which produce one well integrated operating system from thousands of disjunct little pieces of software. Other distributions recently have adopted apt as Debian's \killer app" as they perceive it, but in fact the real killer apps are the policy, the bug handling rules and methods, the security team and all the other codified consistency and quality measures. While people are using \apt-get into it!" as slogan for Debian, I'd rather something like \Policy makes Perfect". All that flexibility and the project size come at a price[6], too, but mostly that price is paid by the developers.
    [Show full text]
  • Game Data Packager
    game-data-packager A data-driven, cross-distribution installer for commercial game assets. Background ● Many old games were either re-released as free software or reverse engineered ➢ But most times it's only the game engine, not the data ● There well exists free alternative data sets for some games – FreeDoom (Doom I & II) – OpenTTD (Transport Tycoon Deluxe) – Lgeneral (Panzer General) ● Other engines, while being free software; are useless on their own, so they end up in alternate repositories: - Debian: contrib, or non-free if there's a non-commercial clause - Fedora: these goes in alternative RPMFusion repository Acquiring non-free data ● Most shareware games can only be distributed as a copy of the original archive; commercial game assets cannot be distributed at all. ● game-data-packager existed in Debian since 2005 as a tool that creates .deb packages for local use. ● Other distributions are providing similar scripts, that also involves wget, md5sum, unzip,… … and a lot of duplicated work. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=heretic1-wad ● Fedora & Mageia are using autodownloader that saves data in /home/. ● Each game engine has detailed instructions to follow by hand. Happy new year 2015 ● A new data-driven engine was committed to git around 2015/01/01 : – engine is written in Python3 – per-game definitions are stored in human-writable machine-readable YAML files. – a plug-in system can handle individual game quirks ● An authoring tool is then added, all the existing shell scripts got rewritten pretty fast. «
    [Show full text]
  • Practical Debian Administration
    Practical Debian Administration Alexander Zangerl Bond University az@ debian.org,bond.edu.au, ¡ Practical Debian – p.1 What is this all about? Things to get you going with your new Debian box Useful Gadgets (IMHO) Overall: How to deal with a Debian system efficiently Practical Debian – p.2 Who am I? Professional Bugbear for students at Bond Uni, QLD Debian Developer, one of >1000 volunteers Sysadmin by choice Practical Debian – p.3 What is Debian? “The Universal Operating System” a bunch of people with a common goal a mindset, expressed by some rules and policies an OS software distribution “The Distribution for Sysadmins by Sysadmins” Practical Debian – p.4 Getting Started You’re in a maze of twisty shell prompts . FS Layout: follows the Filesystem Hierarchy Standard config in /etc/, variable stuff in /var, . default web root in /var/www/ PIDfiles in /var/run/ /usr/local untouched but checked first in $PATH Practical Debian – p.5 Docs?! What Docs? All in /usr/share/doc/X/: debian: FAQ, constitution, general docs debian-policy: the nuts-and-bolts documents newbie-doc: Debian for Dummies? apt-howto(-en): Guide to apt every package: must have copyright and changelog.Debian, often also README.Debian Most docs gzipped: zmore wrapper is always installed Practical Debian – p.6 Tools Initially Encountered base-config: handles last stages of initial install e.g. root pwd setup, apt setup, . can be rerun safely at need. /usr/lib/base-config provides code snippets, run via runparts tasksel: coarse package selection tool only for installing big package groups ("tasks", eg. C Development) tasksel -t: shows apt-get call but doesn’t install.
    [Show full text]
  • MX-19.2 Users Manual
    MX-19.2 Users Manual v. 20200801 manual AT mxlinux DOT org Ctrl-F = Search this Manual Ctrl+Home = Return to top Table of Contents 1 Introduction...................................................................................................................................4 1.1 About MX Linux................................................................................................................4 1.2 About this Manual..............................................................................................................4 1.3 System requirements..........................................................................................................5 1.4 Support and EOL................................................................................................................6 1.5 Bugs, issues and requests...................................................................................................6 1.6 Migration............................................................................................................................7 1.7 Our positions......................................................................................................................8 1.8 Notes for Translators.............................................................................................................8 2 Installation...................................................................................................................................10 2.1 Introduction......................................................................................................................10
    [Show full text]
  • Industrial I/O and Video Solutions 8-1 Table of Contents
    1 Back to TOC Previous Next Table of Contents / Industrial I/O and Video Solutions 8-1 Table of Contents 8 Industrial I/O and Video Solutions 8-2 Industrial I/O 8-60 Intelligent Video Solutions Back to Top 2 Back to TOC Previous Next 8-2 Product Introduction Industrial I/O Advantech Data Acquisition and Control Solutions As a leading supplier of data acquisition products worldwide, Advantech offers a wide range of I/O devices with various interfaces and functions based on PC technology, from legacy ISA to modern USB and from signal-conditioning to graphical software tools. Advantech’s industrial I/O products are reliable, accurate, affordable, and suitable for many industrial automation applications (e.g., testing and measurement) and laboratory applications (e.g., monitoring, control, machine automation, and product testing). Signal Sensing Signal Conditioning Data Acquisition Signal Conditioners Embedded Computers Advantech’s signal conditioners provide sensor MIC-1800 series units are standalone embedded and signal conditioning on a per-module basis for computers with integrated data acquisition modules various types of sensors or signals. and signal conditioning to provide digital I/O, analog I/O, and counter functions. The palm-sized design with built-in terminals is suitable for space-limited applications. I/O Wiring Terminal Boards SuperSpeed USB 3.0 DIO Modules Equipment Sensor I/O wiring terminal boards offer convenient and SuperSpeed USB 3.0 digital I/O modules can be reliable signal wiring for a wide range of Advantech leveraged
    [Show full text]
  • Live Systems Manual
    Live Systems Manual Live Systems Project <[email protected]> Copyright © 2006-2014 Live Systems Project This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WAR- RANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see ‹http://www.gnu.org/licenses/›. The complete text of the GNU General Public License can be found in /usr/share/- common-licenses/GPL-3 file. ii Contents Contents About 2 About this manual 3 1. About this manual 3 1.1 For the impatient ............................... 3 1.2 Terms ..................................... 3 1.3 Authors .................................... 5 1.4 Contributing to this document ........................ 5 1.4.1 Applying changes ........................... 5 1.4.2 Translation .............................. 6 About the Live Systems Project 8 2. About the Live Systems Project 8 2.1 Motivation ................................... 8 2.1.1 What is wrong with current live systems .............. 8 2.1.2 Why create our own live system? .................. 8 2.2 Philosophy .................................. 9 2.2.1 Only unchanged packages from Debian “main” .......... 9 2.2.2 No package configuration of the live system ............ 9 2.3 Contact .................................... 9 User 10 Installation 11 3.
    [Show full text]
  • Check Your GNU / Linux Desktop for All Used "Evil" Non-Free ( Proprietary ) Software with VRMS
    Walking in Light with Christ - Faith, Computing, Diary Articles & tips and tricks on GNU/Linux, FreeBSD, Windows, mobile phone articles, religious related texts http://www.pc-freak.net/blog Check your GNU / Linux Desktop for all used "Evil" Non-free ( proprietary ) Software with VRMS Author : admin If you want to be strict on using only Free Software (in a as in freedom sense), just like Richard Stallman. You will be happy to know there is a tool in Linux called Virtual Richard Stallman ( vrms - report of installed non-free software ) :) On launch vrms simply lists, all software and software documentation installed on Debian GNU / Linux that is not 100% free software licenses / GPL compatbile. This is software installed via non-free package Debian repositories or somehow not sticking to the standards of Debian Free Software Guidelines. Of course living with 100% free software is only for the hard core free software evangelists and rarely there is someone who can use computer on daily basis without some bits of proprietary software like flashplugin-nonfree, Skype rar, unrar. I tried for a while living on only 100% free software but didn't succeeded cause some non-free software is still a must to be able to not detach from "Digital Society". Living on only free software is not easy especially if you want to have normal multimedia stuff on Desktop. Anyways even if you don't plan to purge your non-free software vrms is useful to list what free- software is installed on PC. noah:~# apt-cache show vrms|grep -i description Description-en: virtual Richard M.
    [Show full text]
  • Towards an Improved Regulatory Framework of Free Software : Protecting User Freedoms in a World of Software Communities and Egoverments Siewicz, K
    Towards an improved regulatory framework of free software : protecting user freedoms in a world of software communities and eGoverments Siewicz, K. Citation Siewicz, K. (2010, April 20). Towards an improved regulatory framework of free software : protecting user freedoms in a world of software communities and eGoverments. Meijers- reeks. E.M. Meijers Institute of Legal Studies, Leiden. Retrieved from https://hdl.handle.net/1887/15276 Version: Not Applicable (or Unknown) Licence agreement concerning inclusion of doctoral thesis in the License: Institutional Repository of the University of Leiden Downloaded from: https://hdl.handle.net/1887/15276 Note: To cite this publication please use the final published version (if applicable). Towards an Improved Regulatory Framework of Free Software Protecting user freedoms in a world of software communities and eGovernments Krzysztof Siewicz TTowards_an_Improved_def.inddowards_an_Improved_def.indd 1 223-02-20103-02-2010 10:49:0910:49:09 TTowards_an_Improved_def.inddowards_an_Improved_def.indd 2 223-02-20103-02-2010 10:49:1010:49:10 Towards an Improved Regulatory Framework of Free Software Protecting user freedoms in a world of software communities and eGovernments PROEFSCHRIFT Ter verkrijging van de graad van Doctor aan de Universiteit Leiden, op gezag van de Rector Magnificus prof. mr. P.F. van der Heijden, volgens besluit van het College voor Promoties te verdedigen op dinsdag 20 april 2010 klokke 15.00 uur door Krzysztof Siewicz Geboren te Warschau, Polen in 1979 TTowards_an_Improved_def.inddowards_an_Improved_def.indd 3 223-02-20103-02-2010 10:49:1010:49:10 Promotiecommissie: Promotores: Prof. dr. H. J. van den Herik Prof. mr. A. H. J. Schmidt Overige leden: Prof. dr.
    [Show full text]
  • Navigator Board Support Package (BSP) User's Guide for Pentek's
    USER’S GUIDE for Pentek’s Jade Family of Products Version 2.4 Pentek, Inc. One Park Way Upper Saddle River, NJ 07458 (201) 818−5900 http://www.pentek.com/ Copyright © 2017−2018 Manual Part Number: 800.48145 Rev: 2.4 − April 13, 2018 Navigator BSP User’s Guide Manual Revision History Date Version Comments 5/8/17 1.0 Initial Release 8/3/17 2.0 Version 2.0 release adds support for Models 71131 and 71841. Revised Sect 1.2, Sect 1.3.1, Sect 3.3.1, Sect 3.3.2, Sect 3.3.6, Sect 3.4.1, Sect 3.3, Sect 3.3.6.2, Sect 3.4.6.2, Sect 3.4.6.2, Sect 3.4.6.6, Sect 7.5, Sect 7.7, Sect 7.8, Sect 7.9, Sect 7.10, and Sect 9.2. Appendix A: added and updated command line arguments. Appendix C: revised code snippets in all scenarios; also revised Sect C.7. 10/4/17 2.1 Version 2.1 release adds support for Models 71821 and 71851. Added Sect 9.5 (for KB Case 1540). Revised -adcdatasrc, −dacdatamode, −dacdatasrc, −xfersize, and Sect A.3. 12/15/17 2.2 Version 2.2 release adds support for Model 71862. It also adds support for Models 7192/7192A/ 9192/9192A via the I2C interface on a Model 71841. Revised Sect 1.3.2, Sect 3.4, and Sect 8.3. In Appendix A, revised -adcdatasrc, −adcoption, −brdoption, −clkoption, −dacoption, −ddcoption, −dmaoption, −ducoption, −gateoption, −progoption, −syncoption, −vhost, −vport, and Sect A.3.
    [Show full text]