Continuous Deployment of Pervasive Applications in Dynamic Environments

Total Page:16

File Type:pdf, Size:1020Kb

Continuous Deployment of Pervasive Applications in Dynamic Environments THÈSE Pour obtenir le grade de DOCTEUR DE L’UNIVERSITÉ DE GRENOBLE Spécialité : Informatique Arrêté ministériel : 7 août 2006 Présentée par Necati Ozan GÜNALP Thèse dirigée par Philippe LALANDA préparée au sein Laboratoire d’Informatique de Grenoble et de École Doctorale Mathématiques, Sciences et Technologies de l’Information, Informatique Déploiement continu des applications pervasives en milieux dynamiques Thèse soutenue publiquement le 13 Novembre 2014, devant le jury composé de : Mme Frédérique LAFOREST Professeur à Université de Saint Etienne, Présidente Mr Christian BECKER Professor at Universität Mannheim, Rapporteur Mr Frédéric WEIS Professeur à l’Université de Rennes, Rapporteur Mr Philippe LALANDA Professeur à Université Joseph Fourier, Directeur de thèse Mr Clément ESCOFFIER Ingénieure de Recherche, Université Joseph Fourier, Co-Encadrant de thèse Mr Vincent LESTIDEAU Maitre de Conférences, Université Joseph Fourier, Co-Encadrant de thèse Mr Levent GÜRGEN Ingénieure de Recherche, CEA-LETI, Co-Encadrant de thèse From too much love of living, From hope and fear set free, We thank with brief thanksgiving Whatever gods may be That no life lives for ever; That dead men rise up never; That even the weariest river Winds somewhere safe to sea. — Charles Swineburne, The Garden of Proserpine To my dear family and friends. Continuous deployment of pervasive applications in dynamic environments Abstract Driven by the emergence of new computing environments, dynamically evolving soft- ware systems makes it impossible for developers to deploy software with human-centric processes. Instead, there is an increasing need for automation tools that continuously deploy software into execution, in order to push updates or adapt existing software re- garding contextual and business changes. Existing solutions fall short on providing fault- tolerant, reproducible deployments that would scale on heterogeneous environments. This thesis focuses on enabling continuous deployment solutions for dynamic envi- ronments, such as Pervasive Computing environments. It adopts an approach based on a transactional, idempotent process for coordinating deployment actions. This thesis pro- poses a set of deployment tools, including a deployment manager capable of conducting deployments and continuously adapting applications according to the changes in the cur- rent state of the target platform. The implementation of these tools, Rondo, also allows developers and administrators to code application deployments thanks to a deployment descriptor DSL. Using the implementation of Rondo, the propositions of this thesis are validated in several industrial and academic projects by provisioning frameworks as well as installing applications and continuous recongurations. Résumé L’émergence des nouveaux types d’environnements informatiques amplie le besoin pour des systèmes logiciels d’être capables d’évoluer dynamiquement. Cependant, ces sys- tèmes rendent très dicile le déploiement de logiciels en utilisant des processus humains. Il y a donc un besoin croissant d’outils d’automatisation qui permettent de déployer et recongurer des systèmes logiciels sans en interrompre l’exécution. Le processus de dé- ploiement continu et automatisé permet de mettre à jour ou d’adapter un logiciel en exé- cution en fonction des changements contextuels et des exigences opérationnelles. Les solutions existantes ne permettent pas des déploiements reproductibles et tolérant aux pannes dans des environnements uctuants, et donc requérant une adaptation continue. Cette thèse se concentre en particulier sur des solutions de déploiement continu pour les plates-formes d’exécution dynamiques, tels que celle utilisé dans les environnements ubiquitaires. Elle adopte une approche basée sur un processus transactionnel et idem- potent pour coordonner les actions de déploiement. La thèse propose, également, un ensemble d’outils, y compris un gestionnaire de déploiement capable de mener des dé- ploiements discret, mais également d’adapter les applications continuellement en fonc- tion des changements contextuels. La mise en œuvre de ces outils, permet notamment aux développeurs et aux administrateurs de développer des déploiements d’applications grâce à un langage spécique suivant les principes de l‘infrastructure-as-code. En utilisant l’implantation de Rondo, les propositions de cette thèse sont validées dans plusieurs projets industriels et académiques à la fois pour l’administration de plates- formes ubiquitaires ainsi que pour l’installation d’applications et leurs recongurations continues. Contents Foreword 1 1 Introduction 3 1.1 Motivations ...................................... 4 1.2 Research Challenges ................................. 6 1.3 Contribution ..................................... 7 1.4 Dissertation Structure ................................ 8 2 Pervasive Computing 9 2.1 Introduction ...................................... 10 2.1.1 Evolution of Computing Environments . 10 2.1.2 Pervasive Computing ............................ 12 2.1.3 Context & Context-awareness ...................... 14 2.1.4 Motivating Examples ............................ 16 2.1.5 Research Domains ............................. 20 2.2 Characteristics of Pervasive Environments ................... 23 2.2.1 Distribution ................................. 23 2.2.2 Heterogeneity ................................ 24 2.2.3 Openness & Plural Authority ...................... 25 2.2.4 Dynamism .................................. 25 2.2.5 Autonomy .................................. 26 2.2.6 Summary ................................... 27 2.3 Characteristics of Pervasive Applications .................... 27 2.3.1 Resource Management ........................... 28 2.3.2 Data Orientation .............................. 29 2.3.3 Notion of Context ............................. 29 2.3.4 Adaptability ................................. 30 2.3.5 Security .................................... 31 2.3.6 Summary ................................... 31 2.4 Building Pervasive Applications .......................... 32 2.4.1 Development Tools ............................. 33 2.4.2 Runtime Tools & Middlewares ...................... 34 2.4.3 Management Tools ............................. 35 xii Contents 2.5 Conclusion....................................... 37 3 Software Deployment 39 3.1 Introduction ...................................... 40 3.1.1 Software Development Life Cycle .................... 40 3.1.2 Development Process Models ....................... 42 3.1.3 Summary ................................... 45 3.2 Software Deployment ................................ 46 3.2.1 Two Faces of Evolution .......................... 46 3.2.2 Definitions .................................. 48 3.2.3 Concepts ................................... 49 3.2.4 Deployment Activities ........................... 52 3.2.5 Deployment Roles ............................. 54 3.3 Issues on Software Deployment .......................... 55 3.3.1 Managing Dynamic Evolution ...................... 55 3.3.2 Maintaining Metadata Throughout the Life Cycle . 56 3.3.3 Managing Heterogeneous Environments . 57 3.3.4 Managing Dependencies .......................... 58 3.3.5 Planning and Coordinating Deployment Activities . 58 3.3.6 Ensuring Security .............................. 59 3.4 Software Deployment and Other Research Fields . 60 3.4.1 Software Architectures ........................... 60 3.4.2 Software Product Lines .......................... 61 3.4.3 Self-adaptive Software Systems ...................... 62 3.4.4 System Administration .......................... 63 3.4.5 Summary ................................... 64 3.5 Software Deployment Facilities .......................... 65 3.5.1 Characterization Framework ....................... 65 3.5.2 Evaluation Criteria ............................. 68 3.5.3 Single Target Deployment ......................... 69 3.5.4 Modular Execution Platforms ...................... 72 3.5.5 Distributed Deployment ......................... 75 3.5.6 Cloud Deployment ............................. 79 3.6 Conclusion ....................................... 83 4 Continuous Deployment 85 4.1 Introduction ...................................... 86 4.1.1 From Lean Development to Continuous Delivery . 86 4.1.2 Value Stream in Software Lifecycle ................... 87 4.1.3 Deployment Pipeline ............................ 88 4.2 Enabling Technologies for Continuous Deployment . 90 4.2.1 Source Code Management ......................... 90 Contents xiii 4.2.2 Automated Build .............................. 91 4.2.3 Continuous Integration .......................... 91 4.2.4 Artifact Management ............................ 93 4.2.5 Automated Deployment .......................... 93 4.2.6 Monitoring & Control Loop ....................... 94 4.3 Requirements for Continuous Deployment ................... 98 4.3.1 Platform Requirements .......................... 98 4.3.2 Process Requirements . 100 4.3.3 Language Requirements . 104 4.4 Positioning of Related Works . 106 4.4.1 Evaluation of Deployment Platforms . 106 4.4.2 Evaluation of Deployment Processes . 107 4.4.3 Evaluation on Deployment Descriptors . 108 4.5 Conclusion .......................................110 5 Proposition 111 5.1 Introduction ......................................112 5.1.1 Problem Statement .............................112 5.1.2 Research Objectives ............................114 5.1.3 Approach ...................................116 5.2 Formalization of Deployment Concepts . 118 5.2.1 Resource
Recommended publications
  • Observing the Clouds: a Survey and Taxonomy of Cloud Monitoring Jonathan Stuart Ward† and Adam Barker*†
    Ward and Barker Journal of Cloud Computing: Advances, Systems and Applications (2014) 3:24 DOI 10.1186/s13677-014-0024-2 RESEARCH Open Access Observing the clouds: a survey and taxonomy of cloud monitoring Jonathan Stuart Ward† and Adam Barker*† Abstract Monitoring is an important aspect of designing and maintaining large-scale systems. Cloud computing presents a unique set of challenges to monitoring including: on-demand infrastructure, unprecedented scalability, rapid elasticity and performance uncertainty. There are a wide range of monitoring tools originating from cluster and high-performance computing, grid computing and enterprise computing, as well as a series of newer bespoke tools, which have been designed exclusively for cloud monitoring. These tools express a number of common elements and designs, which address the demands of cloud monitoring to various degrees. This paper performs an exhaustive survey of contemporary monitoring tools from which we derive a taxonomy, which examines how effectively existing tools and designs meet the challenges of cloud monitoring. We conclude by examining the socio-technical aspects of monitoring, and investigate the engineering challenges and practices behind implementing monitoring strategies for cloud computing. Keywords: Cloud computing; Monitoring Introduction most accepted description of the general properties of Monitoring large-scale distributed systems is challeng- cloud computing comes from the US based National Insti- ing and plays a crucial role in virtually every aspect of tution of Standards and Technology (NIST) and other a software orientated organisation. It requires substantial contributors [3,4]: engineering effort to identify pertinent information and to • obtain, store and process that information in order for it On-demand self service: A consumer is able to to become useful.
    [Show full text]
  • Munin Documentation Release 2.999.10-Detached-2018-12-16-C13-G47debb5
    Munin Documentation Release 2.999.10-detached-2018-12-16-c13-g47debb5 The Munin project and its contributors Dec 16, 2018 Contents 1 Preface 3 1.1 What is Munin ?...........................................3 1.2 Conventions.............................................3 1.3 Further Information.........................................3 1.4 Bug Reporting Guidelines......................................6 1.5 Documenting Munin.........................................7 2 Tutorial 11 2.1 Getting Started............................................ 11 2.2 Wildcard Plugins........................................... 13 2.3 Using SNMP plugins......................................... 14 2.4 Let Munin croak alarm........................................ 15 2.5 Munin and Nagios.......................................... 20 2.6 Advanced Features.......................................... 24 2.7 Extraordinary Usage......................................... 25 2.8 Monitoring the “unreachable” hosts................................. 25 2.9 Troubleshooting........................................... 28 3 Munin’s Architecture 35 3.1 Overview............................................... 35 3.2 Components............................................. 36 3.3 Protocols............................................... 60 3.4 Syntax................................................ 62 3.5 API.................................................. 64 4 Munin Installation 65 4.1 Prerequisites............................................. 65 4.2 Installing Munin..........................................
    [Show full text]
  • Performance-Analyse in Großen Umgebungen Mit Collectd
    Performance-Analyse in großen Umgebungen mit collectd Performance-Analyse in großen Umgebungen mit collectd Sebastian tokkee\ Harl " <[email protected]> FrOSCon 2009 2009-08-22 Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Gliederung Was ist collectd? Wichtige Eigenschaften Wichtige Plugins Eigene Erweiterungen Uber¨ den Tellerrand Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Was ist collectd? I collectd sammelt Leistungsdaten von Rechnern I Leistungsdaten sind zum Beispiel: I CPU-Auslastung I Speichernutzung I Netzwerkverkehr I Daten werden erhoben, verarbeitet und gespeichert I H¨aufig: Darstellung als Graphen I Nicht verwechseln mit Monitoring! Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Kontakt I Homepage: http://collectd.org/ I Mailinglist: [email protected] I IRC: #collectd auf irc.freenode.net Web 2.0\: http://identi.ca/collectd I " Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften I Daemon I Freie Software (gr¨oßtenteils GPLv2) I Portierbar (Linux, *BSD, Solaris, . ) I Skalierbar (OpenWrt, . , Cluster / Cloud) I Effizient (Default-Aufl¨osung: 10 Sekunden) I Modular (Uber¨ 70 Plugins) Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften I Daemon I Freie Software (gr¨oßtenteils GPLv2) I Portierbar (Linux, *BSD, Solaris, . ) I Skalierbar (OpenWrt, . , Cluster / Cloud) I Effizient (Default-Aufl¨osung: 10 Sekunden) I Modular (Uber¨ 70 Plugins) Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften: 10-Sekunden-Aufl¨osung Performance-Analyse in großen Umgebungen mit collectd Was ist collectd? Wichtige Eigenschaften Wichtige Eigenschaften I Daemon I Freie Software (gr¨oßtenteils GPLv2) I Portierbar (Linux, *BSD, Solaris, .
    [Show full text]
  • Ubuntunet-Connect 2013
    UbuntuNet-Connect 2013 Transforming Education and Research Proceedings and Report of the 6th UbuntuNet Alliance Annual Conference 14 - 15 November 2013 Lemigo Hotel, Kigali, Rwanda Sponsors: .. ISSN 2223-7062 1 Proceedings Editors: Tiwonge Msulira Banda, Margaret E Ngwira and Rose Chisowa UbuntuNet Alliance Secretariat P.O. Box 2550 Lilongwe, Malawi Lilongwe, Malawi: UbuntuNet Alliance, 2013 www.ubuntunet.net i ISSN 2223-7062 Key title: Proceedings and report of the 6th UbuntuNet Alliance annual conference Abbreviated key title: Proc. rep. 6th UbuntuNet Alliance annu. conf. ii ACKNOWLEDGEMENTS UbuntuNet-Connect is made possible through the various roles that different people and organizations play. We would like to thank each one of them for their support. We wish to acknowledge with gratitude the work of the UbuntuNet-Connect reviewers who year by year give prompt feedback and ensure that the quality of accepted abstracts continues to rise. We also acknowledge the many people who submitted abstracts for the conference. Competition was tight in 2013 but if your abstract was not accepted this year, we encourage you to submit another abstract next year. The contribution of the Rwanda Ministry of Education and the Rwanda Development Board was ongoing and essential and is acknowledged with great appreciation. The Network Startup Resource Centre (NSRC) whose sponsorship funded the participation of the African presenters played a great role in the success of the conference To our Diamond Sponsors: XON; Gold Sponsors: AfricaConnect, NSRC, Liquid Telecomm and Government of Rwanda; Silver Sponsor: WIOCC; and Bronze Sponsors : Optelian, BSC (Broadband Systems Corporation ) and KBC (Kigali Bus Company), we thank you warmly for this investment in the future and request that you continue supporting UbuntuNet-Connect.
    [Show full text]
  • Lucas Nussbaum [email protected]
    Supervision - Monitoring Lucas Nussbaum [email protected] Licence professionnelle ASRALL Administration de systèmes, réseaux et applications à base de logiciels libres Lucas Nussbaum Supervision - Monitoring 1 / 51 Administrative stuff I Yes, this course is in English I will speak in French though Goal: get you used to reading technical documentation in English I This module: 6 slots of 3 hours Evaluation: practical work (TPs) + possibly exam Goals: F General knowledge of infrastructure monitoring F Master standard tools of the field F Know about the current trends in this field (e.g. impact of cloud and elasticity) I The other part of this module (Supervision - Annuaire) is totally independent (and with a different tutor: Fabien Pascale) Lucas Nussbaum Supervision - Monitoring 2 / 51 Introduction I Success criteria for sysadmins: infrastructure that just works Avoid incidents if possible If not possible, minimize downtime I How? Well-designed infrastructure Choose reliable technologies and software Add HA (high-availability), failover, redundancy, etc. I Not enough: Murphy’s law (Anything that can go wrong will go wrong) I Monitoring: Collect information about the state of the infrastructure Detect problems (before users have to report them) Predict problems Usual components: ; Probes to acquire data Database to store all measurements Dashboard to show results Notification system (email, SMS, etc.) Lucas Nussbaum Supervision - Monitoring 3 / 51 Example: Icinga https://nagios.debian.org/icinga/ – login: dsa-guest / password: dsa-guest Lucas Nussbaum Supervision - Monitoring 4 / 51 Example: graph from Munin I Disk usage on a server Lucas Nussbaum Supervision - Monitoring 5 / 51 Two sides of the same coin: Metrology Goal: collect lots of metrics about how the system behaves to track performance of the system over time telemetry I Example: collect statistics about; network traffic, HTTP req/s, disk I/Os, ..
    [Show full text]
  • 82103 QP Code:59232 Time : 2 ½ Hours Total Marks: 75
    F.Y.B.Sc. Computer Science Semester - I (C:75:25) Solution Set - December 2018 (03/12/2018) Subject Code: 82103 QP Code:59232 Time : 2 ½ Hours Total Marks: 75 Q1 Attempt All(Each of 5 marks) (15) a) Multiple Choice Questions 1) GPL stands for _______ i) Generle Public License ii) General Public License iii) Generic Public License iv) General Private License 2) Which of the following is not a phase of Life Cycle Paradigm / waterfall model? i) Analysis ii) Manufacturing iii) Design iv) Coding 3) _________ is the founder of FSF i) Richard Stallman ii) Denis Ritchie iii) Ken Thomson iv) All of these 4) __________ is a form of licensing in which an author surrenders some but not all rights under copyright law i) Copydown ii) License iii) Copyleft iv) Patent 5) The term BSD stands for ______________ i) Binary software distribution ii) Berkley software distribution iii) Binary software development iv) Berkley software development b) Fill in the blanks (Waterfall model, full, internationalization, Prototyping model, Firefox, localization, chrome, free hardware design, partial, open source software) 1) Waterfall model is a static, sequential and procedural approach in software engineering methodology. 2) full copyleft is when all parts of work can be modified by consecutive authors. 3) localization is the process of adapting software for a specific region or language by adding locale-specific components and translating text. 4) Firefox is a web browser project descended from Mozilla application suite. 5) free hardware design refers to design which can be freely copied, distributed, modified and manufactured. c) Short Answers: 1) What is free software? Ans: Free software or libre software is computer software distributed under terms that allow users to run the software for any purpose as well as to study, change, and distribute it and any adapted versions.
    [Show full text]
  • Munin Documentation
    Munin Documentation Release -limitsql − 2017 − 01 − 16 − c − g60eb51b The Munin project and its contributors January 17, 2017 Contents 1 Preface 3 1.1 What is Munin ?...........................................3 1.2 Conventions.............................................3 1.3 Further Information.........................................3 1.4 Bug Reporting Guidelines......................................5 1.5 Documenting Munin.........................................7 2 Tutorial 11 2.1 Getting Started............................................ 11 2.2 Wildcard Plugins........................................... 13 2.3 Using SNMP plugins......................................... 14 2.4 Let Munin croak alarm........................................ 15 2.5 Munin and Nagios.......................................... 20 2.6 Advanced Features.......................................... 24 2.7 Monitoring the “unreachable” hosts................................. 24 3 Munin’s Architecture 27 3.1 Overview............................................... 27 3.2 Components............................................. 28 3.3 Protocols............................................... 50 3.4 Syntax................................................ 52 3.5 API.................................................. 54 4 Munin installation 55 4.1 Prerequisites............................................. 55 4.2 Installing Munin........................................... 56 4.3 Initial configuration......................................... 58 4.4 Upgrade notes...........................................
    [Show full text]
  • Building a Better Network Monitoring System
    Building A Better Network Monitoring System A report submitted in fulfillment of the requirements for the degree of Bachelor of Computing and Mathematical Sciences with Honours at The University of Waikato by Brad Cowie Department of Computer Science Hamilton, New Zealand October 23, 2012 c 2012 Brad Cowie Abstract Network Monitoring Systems are essential in running the complex computer networks of today. They ensure all faults on the network are known and assist the network operator in fixing these faults. There are problems with the typical NMSs used for monitoring networks, both with the difficulty of configuration and the age of these systems. The popular NMSs in use today are either themselves old or extended from old systems designed a decade ago for monitoring much simpler and smaller networks. This project aims to plan and implement a system designed from the start to monitor a modern network and includes all tools in a single extendable system. By using today’s technologies and making good design decisions, this project aims to build a unified and fresh NMS that is easy to configure, maintain and use, streamlining the workflow of a network operator. Acknowledgements I would like to acknowledge and thank my supervisor Richard Nelson for su- pervising this project. Big thanks to the staff at the WAND research group for their support throughout the project, especially Shane Alcock and Brendon Jones for proofing parts of this report. Also to the past and present students of WAND, thanks for the support and tea breaks over the last number of years. Thanks also to Jamie Curtis for the suggestion of the project and motivation for carrying out this work.
    [Show full text]
  • Analysis and Evaluation of Network Management Solutions a Comparison of Network Management Solutions Suitable for Networks with 2,500+ Devices
    DEGREE PROJECT IN COMPUTER ENGINEERING, FIRST CYCLE STOCKHOLM, SWEDEN 2016 Analysis and Evaluation of Network Management Solutions A Comparison of Network Management Solutions Suitable for Networks with 2,500+ Devices MURAT GABDURAHMANOV and SIMON TRYGG KTH ROYAL INSTITUTE OF TECHNOLOGY INFORMATION AND COMMUNICATION TECHNOLOGY Analysis and Evaluation of Network Management Solutions A Comparison of Network Management Solutions Suitable for Networks with 2,500+ Devices Murat Gabdurahmanov and Simon Trygg 2016-06-16 Bachelor of Science Thesis Examiner Gerald Q. Maguire Jr. Academic adviser Anders Västberg KTH Royal Institute of Technology School of Information and Communication Technology (ICT) Department of Communication Systems SE-100 44 Stockholm, Sweden c Murat Gabdurahmanov and Simon Trygg, 16 June 2016 Abstract Some companies today are using sub-optimal and nearly obsolete management systems for their networks. Given the large number of different services that are demanded by users, there is a need to adapt the network structure to support the current and potential future demands. As a result, there is a need for new Network Management Solutions (NMSs). The aim of this thesis project is to help a company who uses a NMS called Local Area Network (LAN) Management Solution (LMS). LMS was designed by Cisco for managing LAN networks. However, the company’s demands are growing and they need to expand their network more than expected. Moreover, LMS is designed to only support devices by Cisco, whereas the company wants a universal solution with wide device support from many manufacturers. This thesis presents an analysis of their current system and suggests potential solutions for an upgrade that will meet all of the company’s demands and will have a long operating life.
    [Show full text]
  • CPS Operations Guide, Release 9.1.0 First Published: April 29, 2016 Last Modified: June 24, 2016
    CPS Operations Guide, Release 9.1.0 First Published: April 29, 2016 Last Modified: June 24, 2016 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • VUTLAN VT825 / Room Guard
    VUTLAN VT825 / Room Guard VT825 Environmental Monitoring Unit • CAN port for digital sensors • 8 Autosense RJ-12 ports for sensors • 4 dry contact inputs • USB port for web camera or for USB flash for saving logs • Two 12V 0.25A output • 100 Mbit Ethernet port • External chassis earthling • LEDs: power, relays, errors, CAN • Onboard temperature sensor (1%) • Internal GSM modem extension slot (GSM modem is ordered separately) • Internal “VT10 / 1-Wire extension” slot or internal “VT18 / Extension slot” (extensions are ordered separately) • Web interface • Virtual sensors & elements: Group, E-mail, SNMP trap, SNMP Get, SMS, SMS Gate, Web-to-SMS, IP cams, PINGs, Triggers, Timers, Dew point • SNMP traps, SMS & E-mail notifications • Supports SNMP v.1, v.2c, v.3 • Notifications: E-mail, SMS, Syslog, Event log, SNMP Trap, SNMP Get • Configurable embedded logic • Sensor graphing • FTP Backup, Radius, DynDNS, SNTP, SMTP, Mail Log, USB Flash log, SD Card Log • Multilanguage support VUTLAN VT825 / Room Guard Processor: ARM926EJ 300 MHz Ethernet 10/100 Mbit port OS: Linux 3.10.101 Built-in clock with time synchronization ROM: 512 Mbit NAND Flash RADIUS access with Login RAM: 64 Mb Device Management: Web, SNMP, manually via SMS Operating temperature: 0 to 60 °C Built-in watchdog timer Alert types: FTP, Syslog, SMTP or SNMP, SMS (GSM modem is ordered Storage temperature: –25 to 85 °C separately) Operating humidity: 0 to 90 %, non- condensing Network protocols: DHCP, HTTP, HTTPS, SNMP, SMTP, SSL, FTP, Storage humidity: 0 to 95 %, non-condensing VUTLAN VT825 / Room Guard VUTLAN VT825 / Room Guard Low alarm level Low warning level Normal level High warning level High alarm level VUTLAN VT825 / Room Guard VUTLAN VT825 / Room Guard VUTLAN VT825 / Room Guard AccelOps GroundWork Inc.
    [Show full text]
  • SUSE Linux Enterprise Server for SAP Applications 12 SP4 Guide Guide SUSE Linux Enterprise Server for SAP Applications 12 SP4
    SUSE Linux Enterprise Server for SAP Applications 12 SP4 Guide Guide SUSE Linux Enterprise Server for SAP Applications 12 SP4 Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, the authors, nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide ix 1 Overview ix 2 Available Documentation and Resources x 3 Giving Feedback xi 4 Documentation Conventions xi 1 What Is SUSE Linux Enterprise Server for SAP Applications? 1 1.1 Software Components 2 SUSE Linux Enterprise Server 2 • SUSE Linux Enterprise High Availability Extension 2 • Simplified SAP HANA System Replication Setup 3 • Installation Workflow 5 • Page-Cache
    [Show full text]