Report of Contributions

Total Page:16

File Type:pdf, Size:1020Kb

Report of Contributions 5th EGEE User Forum Report of Contributions https://indico.cern.ch/e/69338 5th EGEE User F … / Report of Contributions Distributed parametric optimizatio … Contribution ID: 1 Type: Oral Distributed parametric optimization using the Geneva library Wednesday, 14 April 2010 14:00 (20 minutes) The Geneva library implements parallel and distributed parametric optimization algorithms, capa- ble of running on devices ranging from multi-core systems over clusters all the way to Grids and Clouds. The generic design makes Grid-resources available to user groups that have formerly not been exposed to such environments. Detailed analysis Geneva (’Grid-enabled evolutionary algorithms’) is a software library which enables users to solve large-scale parametric optimization problems on devices ranging from multi-core systems over clusters to Grids and Clouds. The generic design makes Geneva applicable to problem domains from a wide range of industrial and scientific application scenarios. From a user’s perspective, parallel and multi-threaded execution can be achieved just as easily as serial execution on a single CPU-core, and does not require the user’s evaluation functions to be aware of the parallel environ- ment. Performance and extensibility are at the core of the C++-based, object-oriented design. The software has been shown to run in parallel with 1000 clients on a Linux cluster, each contributing a fraction of the overall solution. Given suitably complex optimization problems, scalability is al- most linear. The code is available as Open Source, allowing customization under the terms ofthe Affero GPL v3. Conclusions and Future Work The optimization environment will be further expanded to become a clearing house ofdifferent optimization algorithms, all based on the same data structures and using the existing framework for Grid-aware parallelization. Impact The generic design makes Grid technologies accessible to users ranging from scientific toindustrial application domains. It thus has a strong potential to bring new user groups to the Grid. Keywords Optimization Grid Cloud URL for further information http://www.gemfony.com Justification for delivering demo and/or technical requirements (for demos) 1 5th EGEE User F … / Report of Contributions Distributed parametric optimizatio … The topic is sufficiently complex that it cannot be presented as a poster. Given sufficient network connectivity, a number of exa-catching demos can be presented. Primary author: Dr BERLICH, Ruediger (Steinbuch Centre for Computing, Karlsruhe Institute of Technology) Presenter: Dr BERLICH, Ruediger (Steinbuch Centre for Computing, Karlsruhe Institute of Technol- ogy) Session Classification: Computer Science Track Classification: Experiences from application porting and deployment September 27, 2021 Page 2 5th EGEE User F … / Report of Contributions Eliminating and preventing Grid S … Contribution ID: 2 Type: Poster Eliminating and preventing Grid Security Vulnerabilities to reduce security risk Monday, 12 April 2010 17:00 (3 minutes) The EGEE Grid Security Vulnerability Group was formed “to incrementally make the Gridmore secure and thus provide better availability and sustainability of the deployed infrastructure”. The aim is to eliminate vulnerabilities from the Grid and prevent new ones from being introduced, thus reducing the risk of security incidents. This poster alerts users and developers to both the activities of the this group and problems that may be caused by vulnerabilities. It is also intended to inform what they should do to avoid introducing vulnerabilities and report any their find. Impact At the time of writing, over 70 Grid Security Vulnerability bugs have been fixed since the activity started, and several pieces of less secure middleware have been taken out of use as more secure software comes into use. As far as we are aware, no major Grid Security incident within EGEE or collaborating projects has occured due to a vulnerability in Grid Middleware. This could be due to the fact that wehave successfully eliminated many vulnerabilities from the middleware, and successful in preventing new ones. It could also be due to hackers being less alert to Grids that other systems, or that the user community is particularly honest. Keywords Grid Security Vulnerability Risk URL for further information http://www.gridpp.ac.uk/gsvg/ Detailed analysis A system for handling Grid Security vulnerabilities was setup in 2006 at the beginning of EGEE- II. A Risk Assessment Team (RAT) was formed which currently has13 members from 10 different institutes to carry out this process, which is: - anyone may report an issue - the RAT investigates the issue - if valid the RAT carries out a Risk assessment putting each issue into 1 of 4 risk categories - Extremely Critical, High, Moderate, or Low. - a target date for resolution is set according to the risk - an advisory is issued when the issue is fixed, or on the target date Certain types of problem occur quite frequently - such as vulnerabilities resulting from incorrect file permissions, or failure to sanitize user input,. Suggestions for how to prevent new vulnerabil- ities entering the infrastructure will be made. September 27, 2021 Page 3 5th EGEE User F … / Report of Contributions Eliminating and preventing Grid S … Some members of the group are currently participating in an ‘Overall Security Risk Assessment’ which looks at high level risks to the infrastructure, data, and various parties. A summary the reasons for doing this, the strategy, and the outcome (assuming it is available in time) will be included on the poster. Conclusions and Future Work A good enthusiastic team has been handling Grid Security Vulnerabilities over the last 4 years, and many vulnerabilities have been eliminated from the deployed infrastructure. New types of vulnerabilities continue to be found and hackers get ever more ingenious in their quest to gain access to sites. This work therefore needs to continue into the future as grid technology increases it’s profile and hackers become more alert to this type of system and find new ways ofexploiting systems. Primary author: Dr CORNWALL, Linda Ann (Particle Physics-Rutherford Appleton Laborato- ry-STFC - Science &) Presenter: Dr CORNWALL, Linda Ann (Particle Physics-Rutherford Appleton Laboratory-STFC - Science &) Session Classification: Poster session Track Classification: National and international activities and collaborations September 27, 2021 Page 4 5th EGEE User F … / Report of Contributions ATLAS Distributed Computing in … Contribution ID: 4 Type: Oral ATLAS Distributed Computing in Spain and Portugal: from data challenges to real data Wednesday, 14 April 2010 12:00 (20 minutes) The ATLAS PIC cloud is composed of the Iberian sites: PIC (Tier-1), IFAE, IFIC, UAM, LIP-Lisbon, LIP-Coimbra and NCG-INGRID-PT (Tier-2s) and is finalising preparations for the LHC data taking. To achieve readiness for data taking, all sites has been involved in the ATLAS Distributed Comput- ing activities since early 2006: simulated event production, reprocessing, data and user analysis challenges and cosmic data taking. The evolution of the computing and operations activities from data challenges to the real data is described in this talk giving experiment and site experiences. Detailed analysis After the deployment of the required services for the experiment, the Iberian sites nowfacethe challenges associated with real data taking, and that is to provide a reliable service for data analysis for the world-wide scientific ATLAS community and particularity to the Iberian ATLAS scientists. The WLCG grid has been used so far by WLCG institute specialists and few scientists, butnowit must be a daily common “tool” for every single LHC scientist with the first real data of the LHC appearing at the sites. The ATLAS institutes committed to ATLAS in the Iberian cloud have been preparing sites for the data taking since 2006, and achieving good results in all the wide activities that WLCG and ATLAS have been conducting. In this talk we will an overview of the ATLAS ac- tivities in Spain and Portugal since 2006, following the evolution of the different tools/frameworks that have been adopted by the experiment and the sites while awaiting the LHC start-up. Conclusions and Future Work It has been a long road to have the first LHC data being analyzed at the sites. By the timeof the 2010 Users Forum, sites should be flooded with new users willing to run their jobs. Thereal challenge is coming soon, when all of this people will be really grid-aware. The work until now has been exhaustive with the Iberian sites participated in all distributed computing activities, and we are now ready to face the data processing challenges associated with real LHC data taking. Impact ATLAS distributed computing activities are reliant on the EGEE structure, the critical services abeing the catalogues (LFC), the transfers engine (FTS) and the Storage and Computing Elements that are crucial for the scientific community. Also ATLAS has important services running atevery ATLAS cloud, such as the pilot factories and Frontier/squid servers which were recently deployed. All of these mechanisms have to be in place and in high availability to ensure the correct flow of data, and the execution of MonteCarlo/data processing jobs and user analysis jobs. In this talk we present the status and operations model of the ATLAS PIC cloud, following the evolution of ATLAS distributed computing and the improvement of the quality of service, which resulted
Recommended publications
  • Common Tools for Team Collaboration Problem: Working with a Team (Especially Remotely) Can Be Difficult
    Common Tools for Team Collaboration Problem: Working with a team (especially remotely) can be difficult. ▹ Team members might have a different idea for the project ▹ Two or more team members could end up doing the same work ▹ Or a few team members have nothing to do Solutions: A combination of few tools. ▹ Communication channels ▹ Wikis ▹ Task manager ▹ Version Control ■ We’ll be going in depth with this one! Important! The tools are only as good as your team uses them. Make sure all of your team members agree on what tools to use, and train them thoroughly! Communication Channels Purpose: Communication channels provide a way to have team members remotely communicate with one another. Ideally, the channel will attempt to emulate, as closely as possible, what communication would be like if all of your team members were in the same office. Wait, why not email? ▹ No voice support ■ Text alone is not a sufficient form of communication ▹ Too slow, no obvious support for notifications ▹ Lack of flexibility in grouping people Tools: ▹ Discord ■ discordapp.com ▹ Slack ■ slack.com ▹ Riot.im ■ about.riot.im Discord: Originally used for voice-chat for gaming, Discord provides: ▹ Voice & video conferencing ▹ Text communication, separated by channels ▹ File-sharing ▹ Private communications ▹ A mobile, web, and desktop app Slack: A business-oriented text communication that also supports: ▹ Everything Discord does, plus... ▹ Threaded conversations Riot.im: A self-hosted, open-source alternative to Slack Wikis Purpose: Professionally used as a collaborative game design document, a wiki is a synchronized documentation tool that retains a thorough history of changes that occured on each page.
    [Show full text]
  • Návrh a Implementace Rozšíření Do Systému Phabricator
    Masarykova univerzita Fakulta informatiky Návrh a implementace rozšíření do systému Phabricator Diplomová práce Lukáš Jagoš Brno, podzim 2019 Masarykova univerzita Fakulta informatiky Návrh a implementace rozšíření do systému Phabricator Diplomová práce Lukáš Jagoš Brno, podzim 2019 Na tomto místě se v tištěné práci nachází oficiální podepsané zadání práce a prohlášení autora školního díla. Prohlášení Prohlašuji, že tato diplomová práce je mým původním autorským dílem, které jsem vypracoval samostatně. Všechny zdroje, prameny a literaturu, které jsem při vypracování používal nebo z nich čerpal, v práci řádně cituji s uvedením úplného odkazu na příslušný zdroj. Lukáš Jagoš Vedoucí práce: Martin Komenda i Poděkování Srdečně chci na tomto místě poděkovat vedoucímu mé diplomové práce RNDr. Martinu Komendovi, Ph.D. za cenné náměty a odborné vedení. Dále chci poděkovat Mgr. Matěji Karolyi za všestrannou po- moc při implementaci praktické části práce a Ing. Mgr. Janu Krejčímu za zpřístupnění testovacího serveru a technickou podporu. iii Shrnutí Diplomová práce se zabývá nástroji pro projektové řízení. V teore- tické části jsou vymezeny pojmy projekt a projektové řízení. Poté jsou představeny vybrané softwarové nástroje pro projektové řízení a je provedeno jejich srovnání. Pozornost je zaměřena na systém Phabrica- tor, který je v práci detailně popsán. V praktické části je navrženo rozšíření Phabricatoru na základě analýzy potřeb a sběru požadavků. Výsledkem je rozšířující modul po- skytující přehledné informace o úkolech z pohledu času a náročnosti, čímž zefektivní jejich plánování a proces týmové spolupráce. iv Klíčová slova projektové řízení, Phabricator, PHP, reportovací modul, SCRUM v Obsah 1 Projektové řízení 3 1.1 Projekt a projektové řízení ..................3 1.2 SW nástroje pro projektové řízení ...............4 1.3 Přehled nástrojů z oblasti řízení projektů ...........6 1.3.1 Phabricator .
    [Show full text]
  • Project Management Software March 2019
    PROJECT MANAGEMENT SOFTWARE MARCH 2019 Powered by Methodology CONTENTS 3 Introduction 5 Defining Project Management Software 6 FrontRunners (Small Vendors) 8 FrontRunners (Enterprise Vendors) 10 Runners Up 22 Methodology Basics 2 INTRODUCTION his FrontRunners analysis minimum qualifying score of 3.96 Tis a data-driven assessment for Usability and 3.91 for User identifying products in the Project Recommended, while the Small Management software market that Vendor graphic had a minimum offer the best capability and value qualifying score of 4.55 for Usability for small businesses. For a given and 4.38 for User Recommended. market, products are evaluated and given a score for Usability (x-axis) To be considered for the Project and User Recommended (y-axis). Management FrontRunners, a FrontRunners then plots 10-15 product needed a minimum of 20 products each on a Small Vendor user reviews published within 18 and an Enterprise Vendor graphic, months of the evaluation period. based on vendor business size, per Products needed a minimum user category. rating score of 3.0 for both Usability and User Recommended in both In the Project Management the Small and Enterprise graphics. FrontRunners infographic, the Enterprise Vendor graphic had a 3 INTRODUCTION The minimum score cutoff to be included in the FrontRunners graphic varies by category, depending on the range of scores in each category. No product with a score less than 3.0 in either dimension is included in any FrontRunners graphic. For products included, the Usability and User Recommended scores determine their positions on the FrontRunners graphic. 4 DEFINING PROJECT MANAGEMENT SOFTWARE roject management software and document management, as well Phelps organizations manage as at least one of the following: time and deliver projects on time, on tracking, budgeting, and resource budget and within scope.
    [Show full text]
  • A Wiki-Based Authoring Tool for Collaborative Development of Multimedial Documents
    MEDIA2MULT – A WIKI-BASED AUTHORING TOOL FOR COLLABORATIVE DEVELOPMENT OF MULTIMEDIAL DOCUMENTS Author Name * Affiliation * Address * Author Name * Affiliation * Address * * Only for Final Camera-Ready Submission ABSTRACT media2mult is an extension for PmWiki developed at our university. It provides functionality for embedding various media files and script languages in wiki pages. Furthermore media2mult comes with a cross media publishing component that allows to convert arbitrary wiki page sequences to print-oriented formats like PDF. This article gives an overview over the offered extensions, their functionality and implementation concepts. KEYWORDS wiki, multimedia, cross-media-publishing, authoring tool, XML 1. INTRODUCTION At least since the founding of the free web encyclopedia Wikipedia and its increasing popularity wiki web , wiki-wiki or just wiki are widely known terms in context of Web 2.0. However, their exact meaning often remains unclear. Sometimes wiki and Wikipedia are actually used synonymously. The crucial functionality of every wiki system is the possibility to edit wiki web pages directly inside a browser by entering an easy to learn markup language. Thus, manual uploads of previously edited HTML files are superfluous here. The user doesn't even have to know anything about HTML or external HTML editors. The browser- and server-based concept makes it possible that several authors can edit and revise common documents without the necessity of exchanging independently written and updated versions. Because most wiki systems offer an integrated version management system, authors can easily merge their changes and revert selected passages to former stages. Thus, accidentally or deliberately applied changes of protected or publicly accessible wiki pages can be taken back in a second.
    [Show full text]
  • The Opendaylight Open Source Project
    UNIVERSIDAD REY JUAN CARLOS Master´ Universitario en Software Libre Curso Academico´ 2014/2015 Proyecto Fin de Master´ The OpenDaylight Open Source Project Autor: Sergio Najib Arroutbi Braojos Tutor: Dr. Gregorio Robles 2 Agradecimientos A mi familia y a mi pareja, por su apoyo incondicional Al equipo de Libresoft de la Universidad Rey Juan Carlos, por su afan´ en ensenar˜ el que´ y el porque´ del Software Libre Dedicatoria Para todos aquellos´ que hacen posible el fenomeno´ del Software Libre 4 (C) 2014 Sergio Najib Arroutbi Braojos. Some rights reserved. This document is distributed under the Creative Commons Attribution-ShareAlike 3.0 license, available in http://creativecommons.org/licenses/by-sa/3.0/ Source files for this document are available at http://github.com/sarroutbi/MFP/opendaylight/ 6 Contents 1 Introduction 19 1.1 Terminology.................................... 19 1.1.1 Open Source Programmable Networking................ 19 1.2 About this document............................... 20 1.2.1 Document structure............................ 20 1.2.2 Scope................................... 21 1.2.3 Methodology............................... 21 2 Goals and Objectives 23 2.1 General Objectives................................ 23 2.2 Subobjectives................................... 23 2.2.1 Acquire competence on OpenDaylight project.............. 23 2.2.2 Analyze OpenDaylight project from an Open Source perspective.... 24 2.2.3 Statistics and measures of the OpenDaylight project.......... 24 3 OpenDaylight: A first view 25 3.1 OpenDaylight Project............................... 25 3.2 SDN........................................ 29 3.2.1 What is SDN?.............................. 29 3.2.2 SDN: Market share and expectations................... 31 3.3 NFV........................................ 34 3.3.1 What is NFV?.............................. 35 3.3.2 SDN/NFV relationship.......................... 36 3.3.3 NFV benefits..............................
    [Show full text]
  • Customization of an Enterprise Request Management System
    ISSN (Online) 2393-8021 ISSN (Print) 2394-1588 International Advanced Research Journal in Science, Engineering and Technology Vol. 2, Issue 2, February 2015 Customization of an Enterprise request Management System 1 2 3 4 Ashna Shah , Chinmay Balutkar , Bhargavee Singh , Rajesh. B. Singh Student, Computer Department, Sinhgad Institute Of technology, Lonavala, India 1,2,3 Associate Professor, Computer Department, Sinhgad Institute Of technology, Lonavala, India4 Abstract: Information provided in issue reports are relevant and complete in order to help resolve issues quickly. However, often such information trickles to developers after several iterations of communication between End user and reporters. This paper addresses the concerns of Customization of an Enterprise management system by proposing for handling of the issues such as bugs, query and enhancements. As a proof-of-concept, we also demonstrate a prototype interactive enterprise request management system that gathers relevant information from the user and identifies files that need to be fixed to resolve the issues. The main contribution of this application is in the domain of business as we are developing Enterprise request Management System. Keywords: Bugs, Issues, query, enhancement. I. INTRODUCTION The use of Enterprise Request Management Systems as a to the issue and again will report the issue to the reporter. tool to organize maintenance activities is widespread. The Developer then will handle the issues and will fix them. systems serve as a central repository for monitoring the This system will help to manage the issues in the business progress of issue reports, requesting additional information domain by fixing them. The issues might be a bug, query from reporters, and discussing potential solutions for or the enhancement.
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Executing Informal Processes
    Institute of Architecture of Application Systems Executing Informal Processes C. Timurhan Sungur, Uwe Breitenbücher, Frank Leymann, and Johannes Wettinger Institute of Architecture of Application Systems, University of Stuttgart, Germany {lastname}@iaas.uni-stuttgart.de C. Timurhan Sungur, Uwe Breitenbücher, Frank Leymann, and Johannes Wettinger. 2015. Executing Informal Processes. In Proceedings of iiWAS ’15, December 11-13, 2015, Brussels, Belgium. DOI: http://dx.doi.org/10.1145/2837185.2837225 @inproceedings: {Sungur2015a, author = {Sungur, Celal Timurhan and Breitenb\"ucher, Uwe and Leymann, Frank and Wettinger, Johannes}, title = {Executing Informal Processes}, booktitle = {The 17th International Conference on Information Integration and Web-based Applications {\&} Services, {IIWAS} '15, Brussels, Belgium, December 11-13, 2015}, year = {2015}, publisher = {ACM} } © ACM 2015 This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version is available at ACM: http://dx.doi.org/10.1145/2837185.2837225 Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Executing Informal Processes C. Timurhan Sungur, Uwe Breitenbücher, Frank Leymann, and Johannes Wettinger Institute of Architecture of Application Systems University of Stuttgart 70569 Stuttgart, Germany [email protected] ABSTRACT Keywords Processes involving knowledge workers, such as decision- Informal processes, agent-centered processes, human-centric making processes, research processes, development processes, processes, process execution, TOSCA, APIfication maintenance processes, etc.
    [Show full text]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • D2.3 Transport Research in the European Open Science Cloud 29
    Ref. Ares(2020)5096102 - 29/09/2020 European forum and oBsErvatory for OPEN science in transport Project Acronym: BE OPEN Project Title: European forum and oBsErvatory for OPEN science in transport Project Number: 824323 Topic: MG-4-2-2018 – Building Open Science platforms in transport research Type of Action: Coordination and support action (CSA) D2.3 Transport Research in the European Open Science Cloud Final Version European forum and oBsErvatory D2.3: Transport Research in the European Open Science Cloud for OPEN science in transport Deliverable Title: Open/FAIR data, software and infrastructure in European transport research Work Package: WP2 Due Date: 2019.11.30 Submission Date: 2020.09.29 Start Date of Project: 1st January 2019 Duration of Project: 30 months Organisation Responsible of Deliverable: ATHENA RC Version: Final Version Status: Final Natalia Manola, Afroditi Anagnostopoulou, Harry Author name(s): Dimitropoulos, Alessia Bardi Kristel Palts (DLR), Christian von Bühler (Osborn-Clarke), Reviewer(s): Anna Walek, M. Zuraska (GUT), Clara García (Scipedia), Anja Fleten Nielsen (TOI), Lucie Mendoza (HUMANIST), Michela Floretto (FIT), Ioannis Ergas (WEGEMT), Boris Hilia (UITP), Caroline Almeras (ECTRI), Rudolf Cholava (CDV), Milos Milenkovic (FTTE) Nature: ☒ R – Report ☐ P – Prototype ☐ D – Demonstrator ☐ O – Other Dissemination level: ☒ PU - Public ☐ CO - Confidential, only for members of the consortium (including the Commission) ☐ RE - Restricted to a group specified by the consortium (including the Commission Services) 2 | 53 European forum and oBsErvatory D2.3: Transport Research in the European Open Science Cloud for OPEN science in transport Document history Version Date Modified by (author/partner) Comments 0.1 Afroditi Anagnostopoulou, Alessia EOSC sections according to EC 2019.11.25 Bardi, Harry Dimopoulos documents.
    [Show full text]
  • Which Wiki for Which Uses
    Which wiki for which uses There are over 120 Wiki software available to set up a wiki plateform. Those listed below are the 13 more popular (by alphabetic order) wiki engines as listed on http://wikimatrix.org on the 16th of March 2012. The software license decides on what conditions a certain software may be used. Among other things, the software license decide conditions to run, study the code, modify the code and redistribute copies or modified copies of the software. Wiki software are available either hosted on a wiki farm or downloadable to be installed locally. Wiki software Reference Languages Wikifarm Technology Licence Main audience Additional notes name organization available available very frequently met in corporate environment. Arguably the most widely deployed wiki software in the entreprise market. A zero- Confluence Atlassian Java proprietary 11 confluence entreprise cost license program is available for non-profit organizations and open source projects aimed at small companies’ documentation needs. It works on plain DokuWiki several companies Php GPL2 50 small companies text files and thus needs no database. DrupalWiki Kontextwork.de Php GPL2+ 12 entreprise DrupalWiki is intended for enterprise use Entreprise wiki. Foswiki is a wiki + structured data + Foswiki community Perl GPL2 22 entreprise programmable pages education, public Wikimedia Php with backend MediaWiki is probably the best known wiki software as it is the MediaWiki GPLv2+ >300 wikia and many hostingservice, companies private Foundation and others database one used by Wikipedia. May support very large communities knowledge-based site MindTouchTCS MindTouch Inc. Php proprietary 26 SamePage partly opensource and partly proprietary extensions Jürgen Hermann & Python with flat tech savy MoinMoin GPL2 10+ ourproject.org Rather intended for small to middle size workgroup.
    [Show full text]
  • Monday, Oct 12, 2009
    Monday, Oct 12, 2009 Keynote Presentations Infrastructures Use, Requirements and Prospects in ICT for Health Domain Karin Johansson European Commission, Brussels, Belgium Progress in Integrating Networks with Service Oriented Architectures / Grids: ESnet's Guaranteed Bandwidth Service William E. Johnston Senior Scientist, Energy Sciences Network, Lawrence Berkeley National Laboratory, USA The past several years have seen Grid software mature to the point where it is now at the heart of some of the largest science data analysis systems - notably the CMS and Atlas experiments at the LHC. Systems like these, with their integrated, distributed data management and work flow management routinely treat computing and storage resources as 'services'. That is, resources that that can be discovered, queried as to present and future state, and that can be scheduled with guaranteed capacity. In Grid based systems the network provides the communication among these service-based resources, yet historically the network is a 'best effort' resource offering no guarantees and little state transparency. Recent work in the R&E network community, that is associated with the science community, has made progress toward developing network capabilities that provide service-like characteristics: Guaranteed capacity can be scheduled in advance and transparency for the state of the network from end-to-end. These services have grown out of initial work in the Global Grid Forum's Grid Performance Working Group. The services are defined by standard interfaces and data formats, but may have very different implementations in different networks. An ad hoc international working group has been implementing, testing, and refining these services in order to ensure interoperability among the many network domains involved in science collaborations.
    [Show full text]