DOCSLIB.ORG

Open Community: Opensolaris, Open Source, and the Future of Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open Community: Opensolaris, Open Source, and the Future of Software Sun Net Talk On Demand: Open Community: OpenSolaris, Open Source, and the Future of Software [1 February 2006] Length : 42 minutes Sharing destroys...barriers, that is. Hear the latest on OpenSolaris and open source, and why participation, community, and sharing are the future of software. Check out this Sun Net Talk on Demand as Sun experts survey the fast-changing open source landscape. Learn how Sun's open source philosophy is driving such innovations as the Solaris Enterprise System, and why OpenSolaris.org has racked up 26,000 downloads, 10,000 members, and 32 community projects in just six months. Net Talk Agenda • Software Economic Upheaval • Myths of Open Source • Open Source Business Strategies • The Effect on Solaris • The OpenSolaris Community • Participate! Speakers: • Hal Stern, CTO Sun Software • Simon Phipps, Chief Open Source Officer • Stephen Hahn, Senior Staff Engineer, Solaris Kernel Development 1 From communications.sun.com/dialog/eventdescription.do#1 30 March 2006 Open Community: OpenSolaris, Open Source, and the Future of Software Get Offers Feedback Program Console Features Segments List Save Slides Speakers Hal Stern Chief Technology Officer Software Group Simon Phipps Chief Open Source Officer Stephen Hahn Senior Staff Engineer Kernel Development Group Software Economic Upheaval • Open source as mechanism • Initial vs. incremental innovation • Distribution vs. compensation • Coase's Penguin Open Source In A Nutshell • A community of developers • Sharing a code commons • Creating “wealth” from the commons • Enriching the commons in the process • The “craft guilds” rediscovered... • ... Connected Capitalism Dealing With The Mythology • Contribution • Anarchy • Security • Administration • Survival OSS Business Strategies 1) “Dual” License > Differentiation of 6) Stewardship open source and > Drives standards, commercial developer capture > Add value to base & sell 2) Subscription 5) Embedded > Combined > Use as a minor offering of part within software and another product support 3) Hosted 4) Consulting > Software as a > Enterprise service integration > With or without consulting data DNA Triangle Moti vation License Governance Most Freedom for Most People • Class A Licenses – Promote freedom to innovate – Does not protect the commons • Class B Licenses – Balances both freedoms – Protects the commons – Leaves innovators free to do their work • Class C Licenses – Promote constant growth of the commons – Limit the freedom of the developer Sun's Activities • Open source projects – OpenSolaris, OpenSSO, NetBeans, Glassfish, Jini, JXTA, OpenOffice.org... • Open standards work – OASIS OpenDocument Format (ISO)... • Software user interfaces – GNOME, accessibility... • Patents covenants to create “open space” Architecture and Rate of Change • Maintaining architecture stability • Accommodating high rate of change • “Waistlines” for innovation Developing as a Community • Openness presents a challenge: 20 years of software development that worked – How to change safely? – Not that much distance on shared values • Needs communication – Explain and modify existing tools and processes – Learn about newer tools and development models – Describe architecture and influence on design • Being explored by cross-community team Effect on Solaris Why does openness matter? ● New and earliest chance to affect product development or evaluate risk to current use ● Direct communication with implementors ● Active technical contributors can influence technical programs Intent is to extend participation in a predictable software development process • A credible inquiry should result in a timely and appropriate resolution The OpenSolaris Community Browse Source code FAQs Communities Discussions Download Source Code Binaries Tools Participate IRC #opensolaris Discussions Blogs Communities User Groups Buttons By the Numbers 10,000+ Members (1000+ Sun) 32 community projects 55 submissions, 17 integrations 24 user groups worldwide 26,000+ downloads SchilliX, BeleniX community distros available FreeBSD DTrace port underway Data available at http://opensolaris.org/os/community/marketing/metrics/ Participate! opensolaris.org USE interesting profile blog IMPROVE evangelize del.icio.us/tag/opensolaris EVANGELIZE user groups (OSUGs) irc # opensolaris flickr opensolarisenthusiast buttons Final Thoughts Hal Stern Chief Technology Officer Software Group Simon Phipps Chief Open Source Officer Stephen Hahn Senior Staff Engineer Kernel Development Group Next Steps OpenSolaris community site http://opensolaris.org/ OpenSolaris primary discussion list [email protected] Open Source www.sun.com/opensource Open Standards www.sun.com/standards Speaker blogs http://blogs.sun.com/ {stern,webmink,sch} Hear from the Experts Sun Online Discussion Programs Sun Net Talk Series Online, on demand seminars sun.com/nettalk Sun Expert Exchange Live chat forums sun.com/expertexchange Thank You! Sun Expert Exchange “OpenSolaris Participation, Licensing, and Innovation” Wednesday, February 1, 2006 (Q): How does the OpenSolaris team expect important kernel updates to flow to the various distributions? Linux is terrible in that an important bug gets fixed in mainline, but the distros have to backport the patch themselves (sometimes they never do). Stephen Lau (A): This is indeed a problem we see upcoming. One thing we have talked about is figuring out a way to track bugs upstream from bugs.opensolaris.org to various other distributions bug trackers (like Nexenta for example). Currently, most distributions pull the ON kernel source periodically which brings in the most current kernel updates. So if we have upstream bug tracking, it will enable us to at least notify upstream distributions that an important bug has been fixed in mainline. Obviously, we can't force them to pull in the bugfix. This becomes more complicated once Nevada is released as a stable "Solaris 11" and we release security fixes/patches - and this is something we definitely need to think about. (Q): What is your thought on contributing code to open source product that's "owned" or "managed" or "shared" by competitors? From a different angle, to develop OpenSolaris on Power, do you want help from IBM? If so, what will you do to make that happen? (i.e. why would IBM do that) Liane Praza (A): Sun has contributed to a number of open source projects which are sponsored by competitors (e.g. Derby). From an OpenSolaris perspective, we're happy to include anyone who wants to contribute and can sign a contributor agreement! There's already a thriving community working on getting OpenSolaris running on PowerPC. (Q): Can OpenSolaris be built in several different ways to meet the special needs of database servers or web site servers, etc? This will make system administrators' work much easier. Thanks! Al Hopper (A): In general, you don't need a specific build of OpenSolaris to support different and varied workloads. There has been a long term goal within OpenSolaris to eliminate requirements for tuning of kernels. There is also an active community interested in building a "minimal" OpenSolaris which could be used in embedded applications and small memory type appliances. Typical applications would be dedicated firewalls etc. Search for "appliance" at opensolaris.org . (Q): Any chance Open Solaris can be run on a SUNpci3 card in a Sparc based box? Stephen Lau (A): Solaris 10 supports SunPCI3 as a host. I'm not sure if it is supported as a client. But Solaris 10 was supported on a SunPCI3, so I would hope we would continue to support it. If it doesn't, we would certainly like to know why so we could fix it. If you try it and it doesn't work, please file a bug so we can work on it. (Q): Does Solaris support superpaging? Dan Price (A): Yes, very well. We tend to call them "large" pages, so it took us a while to work out what you meant. The answer is yes, we support them for heap, stack, text and the kernel nucleus is allocated from a large page (typically 4MB). On our newest SPARC systems, we support 8K, 64K, 512K, 4M, 32M, and 256M pages, and the system will by default automatically supply them to applications as needed. On Opteron systems, we support 4K and 2M pages. You can always find out what pages are supported by using the “pagesize -a” command. (Q): Why has Linux compatibility (Janus project) taken so long to be available in OpenSolaris? Liane Praza (A): The BrandZ project is the name of the project we're pursuing to support running native Linux (and other types of) applications. It doesn't yet meet the criteria for integrating into the Nevada consolidation (it's not done yet!), so remains a separate project. We encourage you to look around the community for more information. (Q): Can you point to any commercial uses of OpenSolaris today and any web sites powered by OpenSolaris ?? Dan Price (A): I think the question is better phrased as: is anyone running a web site using an OpenSolaris distribution? The answer is yes, at least for users of "Nevada" which is Sun's SX distribution. That said, I don't know that I can disclose the name of that company without lawyers in my office :) . (Q): There is not much literature on OpenSolaris Internal to help interested hackers, as compared to Linux. Are there any portals that are built to consider this matter? Stephen Lau (A): Please see my answer I just posted on the Nevada community for some references. The Solaris Internals book is also a great reference. We would love to see more documentation/literature on this though. The Documentation community is probably the best place to discuss literature/docs. (Q): What build of JDS is supported on Nevada 31? Liane Praza (A): Sun does not offer support for any Nevada releases currently. However, JDS based on Gnome 2.6 is included in Nevada 31. The new JDS based on Gnome 2.10 is available through the JDS community. (Q): What is the advantage of pushing Xen for Solaris instead of using Zones? Dan Price (A): We're not pushing Xen instead of Zones. We're planning to do both. The goal is to offer our customers a portfolio of virtualization products, and help them to pick the ones best suited to their specific needs.
Load more

Recommended publications
  • Solaris Und Opensolaris Eine Sinnvolle Alternative?
    Solaris und OpenSolaris Eine sinnvolle Alternative? Wolfgang Stief best Systeme GmbH MUCOSUG, GUUG e. V. [email protected] 2009-11-23 Agenda OpenSolaris, Solaris Express, Solaris Community Edition Das „Open“ in OpenSolaris Community, Lizenzen, Projects Features Container/Zones, ZFS, DTrace, Crossbow ... Und warum dann nicht gleich Linux? Solaris und OpenSolaris – eine sinnvolle Alternative? pg 2 OpenSolaris? Enterprise PowerNetwork ManagementVirtualization Installation Open Containers Storage CIFS Security Network- DTraceNetwork Based ZFS Auto- Packaging Predictive Magic Self Healing Hardware Time Optimizaton Slider Solaris und OpenSolaris – eine sinnvolle Alternative? pg 3 OpenSolaris Binary Distribution http://www.opensolaris.com stabiler, getester Code Support möglich erscheint ca. 2x jährlich, x86 und SPARC aktuelle Pakete (GNOME etc.), Installer neues Paketformat, Repositories ähnlich Debian aktuell (noch) 2009.06 Solaris und OpenSolaris – eine sinnvolle Alternative? pg 4 OpenSolaris Source Code http://www.opensolaris.org ab Juni 2005: zunächst DTrace, dann sukzessive weitere Teile aktive Community Source Browser OpenGrok http://src.opensolaris.org/ Features werden in „Projects“ entwickelt Community Release 2-wöchentlich (b127) „BFU“ nach Bedarf (blindingly fast upgrade) Solaris und OpenSolaris – eine sinnvolle Alternative? pg 5 OpenSolaris Community Launch am 14. Juni 2005 mehrere Distributionen aus der Community Schillix, Belenix, Nexenta, Milax, StormOS, OSUNIX Stand Frühjahr 2009 (ca. 3½ Jahre): → 116.000 registrierte Mitglieder
    [Show full text]
  • BIONIX – a Solaris Based Platform for Computational Biology Abhishek Pratap1 Prateek Singh2
    BIONIX – a Solaris based Platform for Computational Biology Abhishek Pratap1 Prateek Singh2 1 VIT University, Vellore, TN 632014 India [email protected] 2 VIT University, Vellore, TN 632014 India [email protected] Keywords: Live CD, operating system, Integrated Workbench, Software. Bionix is an integrated software workbench, developed for bioinformaticians and computational biologists. Bioinx is a remastered version of Belenix with open source based bioinformatics applications being integrated with the kernel. The fact that distinguishes Bionix from other open source software’s is the performance based on the most advanced operating system technology, Solaris platform with feature like ZFS(128 bit File System), DTrace (Dynamic Tracing Framework), Zones (Multiple application can run in isolation), SMF (Service Management Framework for handling dependencies). There has been significant reduction in the boot time and memory requirements with on the fly compression techniques being used. It is independent of host operating system. It may provide an ad-hoc solution where no Solaris is installed and has the capability of forming a virtual cluster lab in minutes with auto network detection. The entire Emboss package has been remodeled with graphical user interface and onscreen help options, the NCBI toolkit with all flavors of blast and utilities like entrez search and sequin where a biologist can search or submit a sequence without going to web interface, molecular visualization tools like RasMol and Garlic; and a Perl module, bioperl for application development. The work on parallel computing with Bionix is in progress. The entire project has been coordinated with Asia Pacific Science and Technology Center, Sun Microsystems, Singapore.
    [Show full text]
  • Planning Guide
    Oracle AutoVue 20.2, Client/Server Deployment Planning Guide March 2012 Copyright © 1999, 2012, Oracle and/or its affiliates. All rights reserved. Portions of this software Copyright 1996-2007 Glyph & Cog, LLC. Portions of this software Copyright Unisearch Ltd, Australia. Portions of this software are owned by Siemens PLM © 1986-2012. All rights reserved. This software uses ACIS® software by Spatial Technology Inc. ACIS® Copyright © 1994-2008 Spatial Technology Inc. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Govern- ment, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "com- mercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations.
    [Show full text]
  • Dynamic Integration of Mobile JXTA with Cloud Computing for Emergency Rural Public Health Care
    Osong Public Health Res Perspect 2013 4(5), 255e264 http://dx.doi.org/10.1016/j.phrp.2013.09.004 pISSN 2210-9099 eISSN 2233-6052 - ORIGINAL ARTICLE - Dynamic Integration of Mobile JXTA with Cloud Computing for Emergency Rural Public Health Care Rajasekaran Rajkumar*, Nallani Chackravatula Sriman Narayana Iyengar School of Computing Science and Engineering, VIT University, Vellore, India. Received: August 21, Abstract 2013 Objectives: The existing processes of health care systems where data collection Revised: August 30, requires a great deal of labor with high-end tasks to retrieve and analyze in- 2013 formation, are usually slow, tedious, and error prone, which restrains their Accepted: September clinical diagnostic and monitoring capabilities. Research is now focused on 3, 2013 integrating cloud services with P2P JXTA to identify systematic dynamic process for emergency health care systems. The proposal is based on the concepts of a KEYWORDS: community cloud for preventative medicine, to help promote a healthy rural ambulance alert alarm, community. We investigate the approaches of patient health monitoring, emergency care, and an ambulance alert alarm (AAA) under mobile cloud-based cloud, telecare or community cloud controller systems. JXTA, Methods: Considering permanent mobile users, an efficient health promotion mHealth, method is proposed. Experiments were conducted to verify the effectiveness of P2P the method. The performance was evaluated from September 2011 to July 2012. A total of 1,856,454 cases were transported and referred to hospital, identified with health problems, and were monitored. We selected all the peer groups and the control server N0 which controls N1,N2, and N3 proxied peer groups.
    [Show full text]
  • Asesor Profesional: - Carrera: Licenciatura En Informática
    Título: Redes inalámbricas ad-hoc autoconfigurables. Caso de estudio e implementación Autores: Marcos Mazzini Director: Ing. Luis Marrone Codirector: Lic. Paula Venosa Asesor profesional: - Carrera: Licenciatura en Informática Cualquier computadora portátil medianamente moderna ya cuenta con una placa de red inalámbrica y soporte para redes ad-hoc o sea que cada placa de red puede reenviar datos a cualquier otra que esté a su alcance sin necesidad de un nodo centralizado, pero esta configuración no viene por defecto en los distintos sistemas operativos y en general se requiere instalar y configurar software adicional para que la comunicación sea simple para el usuario no experto. Con la idea de facilitar el aprovechamiento del hardware con el que cuentan estas computadoras, se investigaron las tecnologías existentes que permiten configurar las placas de red en modo ad-hoc, asignar direcciones IP en forma descentralizada, resolver nombres de forma descentralizada y anunciar servicios de cada computadora en un entorno de red. Con esta información se derivó una versión Live CD de Linux con aplicaciones para redes preconfiguradas, soporte para placas de red Wi-Fi y modo ad-hoc preconfigurado de modo que si dos o más notebooks bootean este sistema puedan intercambiar archivos, compartir información, chatear y visualizar remotamente los escritorios y utilizar aplicaciones de red entre ellas sin ninguna necesidad de configurar, instalar o modificar los sistemas existentes y sin necesidad de conectarse a un Access Point. Wi-Fi Ad-Hoc LiveCD Linux Cigarra Conectar Igualdad Se verificó que las tecnologías analizadas son Debian Live Zeroconf Avahi mDNS Link Local IP compatibles y que resuelven la funcionalidad esperada.
    [Show full text]
  • Solving Quarto with JXTA and JNGI
    Solving Quarto with JXTA and JNGI Matthew Shepherd University of Texas at Austin Abstract. This paper presents an implementation of a grid-based autonomous quarto player. The implementation uses the JNGI framework which itself is written on top of JXTA. 1 Introduction Quarto is a game reminiscent of tic-tac-toe. It is played with sixteen unique pieces on a four-by-four square board. Each piece is large or small, black or white, solid or hollow and square or round. The game begins with an empty board and all sixteen pieces available. Two players take successive turns with the first player choosing an available piece. That piece is given to the second player who places it on an empty spot on the board. The roles reverse and the process repeats. A player wins by placing the final piece in a row, column or diagonal where all four pieces have at least one attribute in common. For example, the winner might place a piece that completes a row of four black pieces or a column of four round pieces. My goal was to write an implementation of the game and an autonomous program for a human player to compete against. The program performs an exhaustive search of possible moves in order to find the most appropriate one. If the program were to perform the search on the first move of the game, the sixteen available pieces and sixteen empty squares would combine to produce a (16!)^2 search space. Eliminating the moves that take place after a game has already been won reduces that number, but a single processor would still not be sufficient to perform such a task in a reasonable amount of time.
    [Show full text]
  • Adventures with Illumos
    > Adventures with illumos Peter Tribble Theoretical Astrophysicist Sysadmin (DBA) Technology Tinkerer > Introduction ● Long-time systems administrator ● Many years pointing out bugs in Solaris ● Invited onto beta programs ● Then the OpenSolaris project ● Voted onto OpenSolaris Governing Board ● Along came Oracle... ● illumos emerged from the ashes > key strengths ● ZFS – reliable and easy to manage ● Dtrace – extreme observability ● Zones – lightweight virtualization ● Standards – pretty strict ● Compatibility – decades of heritage ● “Solarishness” > Distributions ● Solaris 11 (OpenSolaris based) ● OpenIndiana – OpenSolaris ● OmniOS – server focus ● SmartOS – Joyent's cloud ● Delphix/Nexenta/+ – storage focus ● Tribblix – one of the small fry ● Quite a few others > Solaris 11 ● IPS packaging ● SPARC and x86 – No 32-bit x86 – No older SPARC (eg Vxxx or SunBlades) ● Unique/key features – Kernel Zones – Encrypted ZFS – VM2 > OpenIndiana ● Direct continuation of OpenSolaris – Warts and all ● IPS packaging ● X86 only (32 and 64 bit) ● General purpose ● JDS desktop ● Generally rather stale > OmniOS ● X86 only ● IPS packaging ● Server focus ● Supported commercial offering ● Stable components can be out of date > XStreamOS ● Modern variant of OpenIndiana ● X86 only ● IPS packaging ● Modern lightweight desktop options ● Extra applications – LibreOffice > SmartOS ● Hypervisor, not general purpose ● 64-bit x86 only ● Basis of Joyent cloud ● No inbuilt packaging, pkgsrc for applications ● Added extra features – KVM guests – Lots of zone features –
    [Show full text]
  • Extensions of JADE and JXTA for Implementing a Distributed System
    EXTENSIONS OF JADE AND JXTA FOR IMPLEMENTING A DISTRIBUTED SYSTEM Edward Kuan-Hua Chen A THESIS SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF APPLIED SCIENCE School of Engineering Science O Edward Kuan-Hua Chen 2005 SIMON FRASER UNIVERSITY Spring 2005 All rights reserved. This work may not be reproduced in whole or in part, by photocopy or other means, without the permission of the author. APPROVAL Edward Kuan-Hua Chen Master of Applied Science Extensions of JADE and JXTA for Implementing a Distributed System EXAMINING COMMITTEE Chair: John Jones Professor, School of Engineering Science William A. Gruver Academic Supervisor Professor, School of Engineering Science Dorian Sabaz Technical Supervisor Chief Technology Officer Intelligent Robotics Corporation Shaohong Wu External Examiner National Research Council Date Approved: April 8, 2004 SIMON FRASER UNIVERSITY PARTIAL COPYRIGHT LICENCE The author, whose copyright is declared on the title page of this work, has granted to Simon Fraser University the right to lend this thesis, project or extended essay to users of the Simon Fraser University Library, and to make partial or single copies only for such users or in response to a request from the library of any other university, or other educational institution, on its own behalf or for one of its users. The author has further granted permission to Simon Fraser University to keep or make a digital copy for use in its circulating collection. The author has further agreed that permission for multiple copying of this work for scholarly purposes may be granted by either the author or the Dean of Graduate Studies.
    [Show full text]
  • Peer-To-Peer Virtualized Services
    International Journal on Advances in Internet Technology, vol 4 no 3 & 4, year 2011, http://www.iariajournals.org/internet_technology/ 89 Peer-to-Peer Virtualized Services David Bailey and Kevin Vella University of Malta Msida, Malta Email: [email protected], [email protected] Abstract—This paper describes the design and operation advance a rethink of general purpose operating system of a peer-to-peer framework for providing, locating and architecture. consuming distributed services that are encapsulated within The performance hit commonly associated with virtual- virtual machines. We believe that the decentralized nature of peer-to-peer networks acting in tandem with techniques such ization has been partly addressed on commodity computers as live virtual machine migration and replication facilitate by recent modifications to the x86 architecture [3], with both scalable and on-demand provision of services. Furthermore, AMD and Intel announcing specifications for integrating the use of virtual machines eases the deployment of a wide IOMMUs (Input/Output Memory Management Units) with range of legacy systems that may subsequently be exposed upcoming architectures. While this largely resolves the issue through the framework. To illustrate the feasibility of running distributed services within virtual machines, several computa- of computational slow-down and simplifies hypervisor de- tional benchmarks are executed on a compute cluster running sign, virtualized I/O performance will remain mostly below our framework, and their performance characteristics are par until I/O devices are capable of holding direct and evaluated. While I/O-intensive benchmarks suffer a penalty concurrent conversations with several virtual machines on due to virtualization-related limitations in the prevailing I/O the same host.
    [Show full text]
  • Guía De Instalación Y Uso De Belenix
    Guía de instalación y uso de Belenix Notas de uso BeleniX se inicia desde un CD y es bastante fácil de entender. No obstante, algunas notas ayudan a utilizarlo: 1. Al arrancarlo, se solicita realizar dos acciones: seleccionar la distribución del teclado, y si se prefiere el modo de línea de comandos o la GUI de XWindows. 2. Tras el arranque, es posible alternar entre el modo de línea de comandos y la GUI. El comando "startgui" inicia los servicios de Xserver y abre el escritorio de Xfce. El comando "stopgui" detiene los servicios de Xserver y vuelve al modo de línea de comandos. 3. BeleniX solicita un nombre de usuario y contraseña en el inicio de sesión de la línea de comandos. De forma predeterminada, el nombre de usuario es "root" y la contraseña "belenix". En el escritorio de la GUI todavía no se solicita ningún nombre de usuario ni contraseña. 4. Al iniciar el escritorio de la GUI por primera vez, aparece en pantalla el mensaje de seguimiento "Call Stack of Bad Caller". Este mensaje no genera ningún error; se trata de un problema conocido del controlador de apertura que utiliza una API de núcleo obsoleta. 5. BeleniX montará automáticamente las particiones reconocidas del disco duro en /mnt. La primera partición FAT se montará en /mnt/fat0, y así sucesivamente. De modo similar, los segmentos UFS se montarán en /mnt/solaris0..n. Es una función de recuperación. 6. Asimismo, BeleniX intentará utilizar un segmento de intercambio en el disco duro si ya hay una partición de Solaris con el intercambio configurado.
    [Show full text]
  • Open Source Software Packages
    Hitachi Ops Center V. 10.3.1 Open Source Software Packages Contact Information: Hitachi Ops Center Project Manager Hitachi Vantara LLC 2535 Augustine Drive Santa Clara, California 95054 Name of Product/Product Version License Component aesh 2.4 Apache License, Version 2.0 aesh Extensions 1.8 Apache License, Version 2.0 aesh Readline 2.0 Apache License, Version 2.0 aesh Terminal API 2.0 Apache License, Version 2.0 @angular-builders/custom- 8.0.0-RC.0 The MIT License webpack @angular-devkit/build-angular 0.800.0-rc.2 The MIT License @angular-devkit/build-angular 0.803.25 The MIT License @angular-devkit/core 7.3.8 The MIT License @angular-devkit/schematics 7.3.8 The MIT License @angular/animations 7.2.15 The MIT License @angular/animations 8.2.14 The MIT License @angular/cdk 7.3.7 The MIT License Name of Product/Product Version License Component @angular/cli 8.0.0 The MIT License @angular/cli 8.3.25 The MIT License @angular/common 7.2.15 The MIT License @angular/common 8.2.14 The MIT License @angular/compiler 7.2.15 The MIT License @angular/compiler 8.2.14 The MIT License @angular/compiler-cli 8.2.14 The MIT License @angular/core 7.2.15 The MIT License @angular/forms 7.2.13 The MIT License @angular/forms 7.2.15 The MIT License @angular/forms 8.2.14 The MIT License @angular/forms 8.2.7 The MIT License @angular/language-service 8.2.14 The MIT License @angular/platform-browser 7.2.15 The MIT License @angular/platform-browser 8.2.14 The MIT License Name of Product/Product Version License Component @angular/platform-browser- 7.2.15 The MIT License
    [Show full text]
  • Decentralized Grid Services on P2P Networks: a Case Study
    Decentralized Grid Services on P2P Networks: A Case Study FREDRIK SÖDERSTRÖM Master of Science Thesis Stockholm, Sweden 2005 IMIT/LECS-2005-05 Decentralized Grid Services on P2P Networks: A Case Study FREDRIK SÖDERSTRÖM Exam iner Assoc. Prof. Vladim ir Vlassov (IM IT/KTH) Master of Science Thesis Stockholm, Sweden 2005 IMIT/LECS-2005-05 Abstract Computers have been connected to networks for a long time. Traditional networks usually provide only simple services. To keep up with the ever- increasing demand for computing resources, like processing power and storage, there is a need to leverage more power from existing networks. One way of managing all resources of large networks, and letting multiple organizations share these resources with each other, is called Grid comput- ing. In this thesis, we examine one of the services that is necessary for a Grid, namely resource discovery, a mechanism for finding the available re- sources on a network. Resource discovery services are often designed to rely on some kind of central repository where all resources must be regis- tered. But this approach does not work well in very large networks, be- cause the central repository will become a bottleneck. Resource discovery can also be decentralized, and we suggest that it should be built on peer-to- peer technology to achieve maximum scalability. Using JXTA, a peer-to- peer platform, and the Globus Toolkit for Grid services, we create and evaluate a prototype implementation of a distributed discovery service. Acknowledgments I would like to thank my father, Håkan Söderström, for helping me with a number of bugs and reading drafts of the report.
    [Show full text]