DOCSLIB.ORG

Openstack Operations Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Openstack Operations Guide www.it-ebooks.info www.it-ebooks.info OpenStack Operations Guide by Tom Fifield, Diane Fleming, Anne Gentle, Lorin Hochstein, Jonathan Proulx, Everett Toews, and Joe Topjian www.it-ebooks.info OpenStack Operations Guide by Tom Fifield, Diane Fleming, Anne Gentle, Lorin Hochstein, Jonathan Proulx, Everett Toews, and Joe Topjian Copyright © 2014 OpenStack Foundation. All rights reserved. Printed in the United States of America. Published by O'Reilly Media, Inc. , 1005 Gravenstein Highway North, Sebastopol, CA 95472. O'Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corpo‐ rate/institutional sales department: 800-998-9938 or [email protected] . Editors: Andy Oram and Brian Anderson Indexer: Judith McConville Production Editor: Kristen Brown Interior Designer: David Futato Copyeditor: John Pierce Cover Designer: Karen Montgomery Proofreader: Amanda Kersey Illustrator: Rebecca Demarest May 2014: First Edition Revision History for the First Edition 2014-04-21: First release See http://oreilly.com/catalog/errata.csp?isbn=9781491946954 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O'Reilly logo are registered trademarks of O'Reilly Media, Inc. OpenStack Operations Guide, the image of a crested agouti, and related trade dress are trademarks of O'Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O'Reilly Media, Inc., was aware of a trade‐ mark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con‐ tained herein. 978-1-491-94695-4 [LSI] www.it-ebooks.info Table of Contents Preface. xi Part I. Architecture 1. Example Architectures. 3 Example Architecture—Legacy Networking (nova) 3 Overview 4 Detailed Description 7 Optional Extensions 9 Example Architecture—OpenStack Networking 9 Overview 9 Detailed Description 11 Example Component Configuration 19 Parting Thoughts on Architectures 23 2. Provisioning and Deployment. 25 Automated Deployment 25 Disk Partitioning and RAID 26 Network Configuration 28 Automated Configuration 28 Remote Management 29 Parting Thoughts for Provisioning and Deploying OpenStack 29 Conclusion 30 3. Designing for Cloud Controllers and Cloud Management. 31 Hardware Considerations 32 Separation of Services 33 Database 34 iii www.it-ebooks.info Message Queue 34 Conductor Services 35 Application Programming Interface (API) 35 Extensions 36 Scheduling 36 Images 37 Dashboard 37 Authentication and Authorization 37 Network Considerations 38 4. Compute Nodes. 39 Choosing a CPU 39 Choosing a Hypervisor 40 Instance Storage Solutions 41 Off Compute Node Storage—Shared File System 42 On Compute Node Storage—Shared File System 42 On Compute Node Storage—Nonshared File System 43 Issues with Live Migration 43 Choice of File System 44 Overcommitting 44 Logging 45 Networking 45 Conclusion 45 5. Scaling. 47 The Starting Point 47 Adding Cloud Controller Nodes 49 Segregating Your Cloud 50 Cells and Regions 51 Availability Zones and Host Aggregates 51 Scalable Hardware 53 Hardware Procurement 53 Capacity Planning 54 Burn-in Testing 54 6. Storage Decisions. 55 Ephemeral Storage 55 Persistent Storage 55 Object Storage 55 Block Storage 57 OpenStack Storage Concepts 57 Choosing Storage Backends 58 iv | Table of Contents www.it-ebooks.info Commodity Storage Backend Technologies 60 Conclusion 62 7. Network Design. 63 Management Network 63 Public Addressing Options 64 IP Address Planning 64 Network Topology 65 VLAN Configuration Within OpenStack VMs 67 Multi-NIC Provisioning 67 Multi-Host and Single-Host Networking 67 Services for Networking 68 NTP 68 DNS 68 Conclusion 68 Part II. Operations 8. Lay of the Land. 71 Using the OpenStack Dashboard for Administration 71 Command-Line Tools 71 Installing the Tools 72 Administrative Command-Line Tools 72 Getting Credentials 73 Inspecting API Calls 75 Servers and Services 76 Diagnose Your Compute Nodes 78 Network Inspection 79 Users and Projects 80 Running Instances 81 Summary 82 9. Managing Projects and Users. 83 Projects or Tenants? 83 Managing Projects 84 Adding Projects 84 Quotas 85 Set Image Quotas 86 Set Compute Service Quotas 86 Set Object Storage Quotas 89 Set Block Storage Quotas 90 Table of Contents | v www.it-ebooks.info User Management 92 Creating New Users 92 Associating Users with Projects 93 Customizing Authorization 94 Users Who Disrupt Other Users 97 Summary 97 10. User-Facing Operations. 99 Images 99 Adding Images 99 Sharing Images Between Projects 100 Deleting Images 100 Other CLI Options 101 The Image Service and the Database 101 Example Image Service Database Queries 101 Flavors 101 Private Flavors 103 How Do I Modify an Existing Flavor? 103 Security Groups 104 General Security Groups Configuration 104 End-User Configuration of Security Groups 104 Block Storage 106 Block Storage Creation Failures 108 Instances 108 Starting Instances 108 Instance Boot Failures 109 Using Instance-Specific Data 110 Associating Security Groups 112 Floating IPs 112 Attaching Block Storage 113 Taking Snapshots 114 Live Snapshots 115 Instances in the Database 116 Good Luck! 117 11. Maintenance, Failures, and Debugging. 119 Cloud Controller and Storage Proxy Failures and Maintenance 119 Planned Maintenance 119 Rebooting a Cloud Controller or Storage Proxy 119 After a Cloud Controller or Storage Proxy Reboots 120 Total Cloud Controller Failure 120 Compute Node Failures and Maintenance 121 vi | Table of Contents www.it-ebooks.info Planned Maintenance 121 After a Compute Node Reboots 121 Instances 122 Inspecting and Recovering Data from Failed Instances 122 Volumes 125 Total Compute Node Failure 125 /var/lib/nova/instances 126 Storage Node Failures and Maintenance 127 Rebooting a Storage Node 127 Shutting Down a Storage Node 127 Replacing a Swift Disk 127 Handling a Complete Failure 128 Configuration Management 129 Working with Hardware 129 Adding a Compute Node 130 Adding an Object Storage Node 130 Replacing Components 130 Databases 131 Database Connectivity 131 Performance and Optimizing 131 HDWMY 132 Hourly 132 Daily 132 Weekly 132 Monthly 132 Quarterly 132 Semiannually 133 Determining Which Component Is Broken 133 Tailing Logs 133 Running Daemons on the CLI 134 Uninstalling 135 12. Network Troubleshooting. 137 Using “ip a” to Check Interface States 137 Visualizing nova-network Traffic in the Cloud 138 Visualizing OpenStack Networking Service Traffic in the Cloud 139 Finding a Failure in the Path 145 tcpdump 146 iptables 147 Network Configuration in the Database for nova-network 148 Manually Deassociating a Floating IP 148 Debugging DHCP Issues with nova-network 149 Table of Contents | vii www.it-ebooks.info Debugging DNS Issues 152 Troubleshooting Open vSwitch 153 Dealing with Network Namespaces 154 Summary 155 13. Logging and Monitoring. 157 Where Are the Logs? 157 Reading the Logs 158 Tracing Instance Requests 159 Adding Custom Logging Statements 160 RabbitMQ Web Management Interface or rabbitmqctl 161 Centrally Managing Logs 161 rsyslog Client Configuration 161 rsyslog Server Configuration 162 StackTach 163 Monitoring 163 Process Monitoring 164 Resource Alerting 165 Metering and Telemetry with Ceilometer 165 OpenStack-Specific Resources 166 Intelligent Alerting 167 Trending 168 Summary 169 14. Backup and Recovery. 171 What to Back Up 171 Database Backups 172 File System Backups 172 Compute 172 Image Catalog and Delivery 173 Identity 173 Block Storage 173 Object Storage 173 Recovering Backups 173 Summary 174 15. Customization. 175 Create an OpenStack Development Environment 175 Customizing Object Storage (Swift) Middleware 178 Customizing the OpenStack Compute (nova) Scheduler 184 Customizing the Dashboard (Horizon) 189 viii | Table of Contents www.it-ebooks.info Conclusion 189 16. Upstream OpenStack. 191 Getting Help 191 Reporting Bugs 192 Confirming and Prioritizing 193 Bug Fixing 194 After the Change Is Accepted 194 Join the OpenStack Community 194 How to Contribute to the Documentation 195 Security Information 195 Finding Additional Information 196 17. Advanced Configuration. 197 Differences Between Various Drivers 197 Implementing Periodic Tasks 198 Specific Configuration Topics 199 Security Configuration for Compute, Networking, and Storage 199 High Availability 199 Enabling IPv6 Support 199 Periodic Task Frequency for Compute 199 Geographical Considerations for Object Storage 200 18. Upgrades. 201 Pre-Upgrade Testing Environment 201 Preparing for a Rollback 202 Upgrades 203 How to Perform an Upgrade from Grizzly to Havana—Ubuntu 204 Impact on Users 204 Upgrade Considerations 204 Perform a Backup 204 Manage Repositories 204 Update Configuration Files 205 Upgrade Packages on the Controller Node 207 Stop Services, Update Database Schemas, and Restart Services on the Controller Node 207 Upgrade Packages and Restart Services on the Compute Nodes 208 Upgrade Packages and Restart Services on the Block Storage Nodes 209 How to Perform an Upgrade from Grizzly to Havana—Red Hat Enterprise Linux and Derivatives 210 Impact on Users 210 Upgrade Considerations 210 Table of Contents | ix www.it-ebooks.info Perform a Backup 210 Manage Repositories 211 Update Configuration
Load more

Recommended publications
  • LAMP and the REST Architecture Step by Step Analysis of Best Practice
    LAMP and the REST Architecture Step by step analysis of best practice Santiago Gala High Sierra Technology S.L.U. Minimalistic design using a Resource Oriented Architecture What is a Software Platform (Ray Ozzie ) ...a relevant and ubiquitous common service abstraction Creates value by leveraging participants (e- cosystem) Hardware developers (for OS level platforms) Software developers Content developers Purchasers Administrators Users Platform Evolution Early stage: not “good enough” solution differentiation, innovation, value flows Later: modular architecture, commoditiza- tion, cloning no premium, just speed to market and cost driven The platform effect - ossification, followed by cloning - is how Chris- tensen-style modularity comes to exist in the software industry. What begins as a value-laden proprietary platform becomes a replaceable component over time, and the most successful of these components finally define the units of exchange that power commodity networks. ( David Stutz ) Platform Evolution (II) Example: PostScript Adobe Apple LaserWriter Aldus Pagemaker Desktop Publishing Linotype imagesetters NeWS (Display PostScript) OS X standards (XSL-FO -> PDF, Scribus, OOo) Software Architecture ...an abstraction of the runtime elements of a software system during some phase of its oper- ation. A system may be composed of many lev- els of abstraction and many phases of opera- tion, each with its own software architecture. Roy Fielding (REST) What is Architecture? Way to partition a system in components
    [Show full text]
  • A Learner's Guide to Programming Using the Python Language.Pdf
    Advance Praise for Head First Programming “Head First Programming does a great job teaching programming using an iterative process. Add a little, explain a little, make the program a little better. This is how programming works in the real world and Head First Programming makes use of that in a teaching forum. I recommend this book to anyone who wants to start dabbling in programming but doesn’t know where to start. I’d also recommend this book to anyone not necessarily new to programming, but curious about Python. It’s a great intro to programming in general and programming Python specifically.” — Jeremy Jones, Coauthor of Python for Unix and Linux System Administration “David Griffiths and Paul Barry have crafted the latest gem in the Head First series. Do you use a computer, but are tired of always using someone else’s software? Is there something you wish your computer would do but wasn’t programmed for? In Head First Programming, you’ll learn how to write code and make your computer do things your way.” — Bill Mietelski, Software Engineer “Head First Programming provides a unique approach to a complex subject. The early chapters make excellent use of metaphors to introduce basic programming concepts used as a foundation for the rest of the book. This book has everything, from web development to graphical user interfaces and game programming.” — Doug Hellmann, Senior Software Engineer, Racemi “A good introduction to programming using one of the best languages around, Head First Programming uses a unique combination of visuals, puzzles, and exercises to teach programming in a way that is approachable and fun.” — Ted Leung, Principal Software Engineer, Sun Microsystems Praise for other Head First books “Kathy and Bert’s Head First Java transforms the printed page into the closest thing to a GUI you’ve ever seen.
    [Show full text]
  • Openstack Security Guide April 26, 2014 Current
    OpenStack Security Guide April 26, 2014 current OpenStack Security Guide current (2014-04-26) Copyright © 2013 OpenStack Foundation Some rights reserved. This book provides best practices and conceptual information about securing an OpenStack cloud. Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. http://creativecommons.org/licenses/by/3.0/legalcode i TM OpenStack Security Guide April 26, 2014 current Table of Contents Preface ................................................................................................ 11 Conventions ................................................................................. 11 Document change history ............................................................ 11 1. Acknowledgments ............................................................................. 1 2. Why and how we wrote this book ..................................................... 3 Objectives ...................................................................................... 3 How .............................................................................................. 3 How to contribute to this book ..................................................... 7 3. Introduction to OpenStack ................................................................. 9 Cloud types ................................................................................... 9 OpenStack service overview ......................................................... 11 4. Security Boundaries and Threats
    [Show full text]
  • Pydap Documentation Release 3.2
    Pydap Documentation Release 3.2 Roberto De Almeida May 24, 2017 Contents 1 Quickstart 3 2 Help 5 3 Documentation 7 3.1 Using the client..............................................7 3.2 Running a server............................................. 15 3.3 Handlers................................................. 18 3.4 Responses................................................ 22 3.5 Developer documentation........................................ 24 3.6 License.................................................. 34 4 Indices and tables 35 i ii Pydap Documentation, Release 3.2 Pydap is a pure Python library implementing the Data Access Protocol, also known as DODS or OPeNDAP. You can use Pydap as a client to access hundreds of scientific datasets in a transparent and efficient way through the internet; or as a server to easily distribute your data from a variety of formats. Contents 1 Pydap Documentation, Release 3.2 2 Contents CHAPTER 1 Quickstart You can install the latest version (3.2) using pip. After installing pip you can install Pydap with this command: $ pip install Pydap This will install Pydap together with all the required dependencies. You can now open any remotely served dataset, and Pydap will download the accessed data on-the-fly as needed: >>> from pydap.client import open_url >>> dataset= open_url('http://test.opendap.org/dap/data/nc/coads_climatology.nc') >>> var= dataset['SST'] >>> var.shape (12, 90, 180) >>> var.dtype dtype('>f4') >>> data= var[0,10:14,10:14] # this will download data from the server >>> data <GridType with
    [Show full text]
  • Comparison of Web Server Software from Wikipedia, the Free Encyclopedia
    Create account Log in Article Talk Read Edit ViewM ohrisetory Search Comparison of web server software From Wikipedia, the free encyclopedia Main page This article is a comparison of web server software. Contents Featured content Contents [hide] Current events 1 Overview Random article 2 Features Donate to Wikipedia 3 Operating system support Wikimedia Shop 4 See also Interaction 5 References Help 6 External links About Wikipedia Community portal Recent changes Overview [edit] Contact page Tools Server Developed by Software license Last stable version Latest release date What links here AOLserver NaviSoft Mozilla 4.5.2 2012-09-19 Related changes Apache HTTP Server Apache Software Foundation Apache 2.4.10 2014-07-21 Upload file Special pages Apache Tomcat Apache Software Foundation Apache 7.0.53 2014-03-30 Permanent link Boa Paul Phillips GPL 0.94.13 2002-07-30 Page information Caudium The Caudium Group GPL 1.4.18 2012-02-24 Wikidata item Cite this page Cherokee HTTP Server Álvaro López Ortega GPL 1.2.103 2013-04-21 Hiawatha HTTP Server Hugo Leisink GPLv2 9.6 2014-06-01 Print/export Create a book HFS Rejetto GPL 2.2f 2009-02-17 Download as PDF IBM HTTP Server IBM Non-free proprietary 8.5.5 2013-06-14 Printable version Internet Information Services Microsoft Non-free proprietary 8.5 2013-09-09 Languages Jetty Eclipse Foundation Apache 9.1.4 2014-04-01 Čeština Jexus Bing Liu Non-free proprietary 5.5.2 2014-04-27 Galego Nederlands lighttpd Jan Kneschke (Incremental) BSD variant 1.4.35 2014-03-12 Português LiteSpeed Web Server LiteSpeed Technologies Non-free proprietary 4.2.3 2013-05-22 Русский Mongoose Cesanta Software GPLv2 / commercial 5.5 2014-10-28 中文 Edit links Monkey HTTP Server Monkey Software LGPLv2 1.5.1 2014-06-10 NaviServer Various Mozilla 1.1 4.99.6 2014-06-29 NCSA HTTPd Robert McCool Non-free proprietary 1.5.2a 1996 Nginx NGINX, Inc.
    [Show full text]
  • Arxiv:1903.01950V2 [Cs.OS] 20 Nov 2019
    Pyronia: Intra-Process Access Control for IoT Applications Marcela S. Melara, David H. Liu, Michael J. Freedman Princeton University Abstract recognize_face() function could allow an attacker to steal the application’s private authentication token by upload Third-party code plays a critical role in IoT applications, this file to an unauthorized remote server. Meanwhile, the which generate and analyze highly privacy-sensitive data. application developer only expected recognize_face() to Unlike traditional desktop and server settings, IoT devices access the image file face.jpg. mostly run a dedicated, single application. As a result, This is an especially serious problem for IoT because vulnerabilities in third-party libraries within a process most devices run a single, dedicated application that has pose a much bigger threat than on traditional platforms. access to all sensors on the device. In other words, third- We present Pyronia, a fine-grained access control sys- party code does not run with least privilege [48]. tem for IoT applications written in high-level languages. Now, these threats are not IoT-specific. A large body of Pyronia exploits developers’ coarse-grained expectations prior research has sought to restrict untrusted third-party about how imported third-party code operates to restrict code in desktop, mobile, and cloud applications (e.g., [10, access to files, devices, and specific network destinations, 11,14,19,21,24,36,41,54,55,59,65 –67]). However, these at the granularity of individual functions. To efficiently traditional compute settings face more complex security protect such sensitive OS resources, Pyronia combines challenges. Mobile devices, desktops, and even IoT hubs, three techniques: system call interposition, stack inspec- run multiple mutually distrusting applications; further, tion, and memory domains.
    [Show full text]
  • Chaussette Documentation Release 1.3.0
    Chaussette Documentation Release 1.3.0 Tarek Ziade Sep 27, 2017 Contents 1 Usage 3 1.1 Running a plain WSGI application....................................3 1.2 Running a Django application......................................3 1.3 Running a Python Paste application...................................3 2 Using Chaussette in Circus 5 3 Using Chaussette in Supervisor7 4 Backends 9 5 Rationale and Design 11 6 Useful links 13 i ii Chaussette Documentation, Release 1.3.0 Chaussette is a WSGI server you can use to run your Python WSGI applications. The particularity of Chaussette is that it can either bind a socket on a port like any other server does or run against already opened sockets. That makes Chaussette the best companion to run a WSGI or Django stack under a process and socket manager, such as Circus or Supervisor. Contents 1 Chaussette Documentation, Release 1.3.0 2 Contents CHAPTER 1 Usage You can run a plain WSGI application, a Django application, or a Paste application. To get all options, just run chaussette –help. Running a plain WSGI application Chaussette provides a console script you can launch against a WSGI application, like any WSGI server out there: $ chaussette mypackage.myapp Application is <function myapp at 0x104d97668> Serving on localhost:8080 Using <class chaussette.backend._wsgiref.ChaussetteServer at 0x104e58d50> as a backend Running a Django application Chaussette allows you to run a Django project. You just need to provide the Python import path of the WSGI application, commonly located in the Django project’s wsgi.py file. For further information about how the wsgi. py file should look like see the Django documentation.
    [Show full text]
  • Red Hat Enterprise Linux 7 7.8 Release Notes
    Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Last Updated: 2021-03-02 Red Hat Enterprise Linux 7 7.8 Release Notes Release Notes for Red Hat Enterprise Linux 7.8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Red Hat Enterprise Linux 7 Migration Planning Guide
    Red Hat Enterprise Linux 7 Migration Planning Guide Migrating to Red Hat Enterprise Linux 7 Laura Bailey Red Hat Enterprise Linux 7 Migration Planning Guide Migrating to Red Hat Enterprise Linux 7 Laura Bailey Legal Notice Copyright © 2014 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission.
    [Show full text]
  • Porting Meego to LEON
    #orting $eeGo to LE&' Master of Science Thesis ()A' *ERT&'A Chalmers University of Technology University of Gothenburg Department of Computer Science and Engineering Göteborg, Sweden, August !"" The Author grants to Chalmers University of Technology and University of Gothenburg the non-e-clusive right to publish the .or/ electronically and in a non-commercial purpose make it accessible on the (nternet0 The Author warrants that he1she is the author to the .ork, and warrants that the .or/ does not contain te-t, pictures or other material that violates copyright law0 The Author shall, when transferring the rights of the .or/ to a third party 2for e-ample a publisher or a company3, ac/nowledge the third party about this agreement0 (f the Author has signed a copyright agreement with a third party regarding the .ork, the Author warrants hereby that he1she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the .or/ electronically and make it accessible on the (nternet0 #orting $eeGo to %E&' (van *ertona 4 (van *ertona, August !""0 E-aminer5 Arne Dahlberg Chalmers University of Technology University of Gothenburg Department of Computer Science and Engineering SE-6" 78 Göteborg Sweden Telephone 9 68 2!3:",;; "!!! Department of Computer Science and Engineering Göteborg, Sweden, August !"" POLITECNICO DI TORINO III Faculty of Information Engineering Master of Science in Computer Engineering Master Thesis Porting MeeGo To LEON Supervisor: Bartolomeo Montrucchio Candidate: Ivan Bertona August 2011 Abstract Portable multimedia devices are the flagship of a steadily growing market, from which the LEON/GRLIB hardware platform was excluded due to the lack of suitable software support.
    [Show full text]
  • Chaussette Documentation Release 1.3.0
    Chaussette Documentation Release 1.3.0 Tarek Ziade Apr 19, 2017 Contents 1 Usage 3 1.1 Running a plain WSGI application....................................3 1.2 Running a Django application......................................3 1.3 Running a Python Paste application...................................3 2 Using Chaussette in Circus 5 3 Using Chaussette in Supervisor7 4 Backends 9 5 Rationale and Design 11 6 Useful links 13 i ii Chaussette Documentation, Release 1.3.0 Chaussette is a WSGI server you can use to run your Python WSGI applications. The particularity of Chaussette is that it can either bind a socket on a port like any other server does or run against already opened sockets. That makes Chaussette the best companion to run a WSGI or Django stack under a process and socket manager, such as Circus or Supervisor. Contents 1 Chaussette Documentation, Release 1.3.0 2 Contents CHAPTER 1 Usage You can run a plain WSGI application, a Django application, or a Paste application. To get all options, just run chaussette –help. Running a plain WSGI application Chaussette provides a console script you can launch against a WSGI application, like any WSGI server out there: $ chaussette mypackage.myapp Application is <function myapp at 0x104d97668> Serving on localhost:8080 Using <class chaussette.backend._wsgiref.ChaussetteServer at 0x104e58d50> as a backend Running a Django application Chaussette allows you to run a Django project. You just need to provide the Python import path of the WSGI application, commonly located in the Django project’s wsgi.py file. For further information about how the wsgi. py file should look like see the Django documentation.
    [Show full text]
  • An Introduction to HTTP Fingerprinting Table of Contents
    An Introduction to HTTP fingerprinting Saumil Shah [email protected] 30th November, 2003 Table of Contents 1. Abstract 2. Theory of Fingerprinting 3. Banner Grabbing 4. Applications of HTTP Fingerprinting 5. Obfuscating the server banner string 6. Protocol Behaviour 6.1 HTTP Header field ordering 6.2 HTTP DELETE 6.3 Improper HTTP version response 6.3 Improper protocol response 6.5 Summary of test results 6.6 Choosing the right tests 7. Statistical and Fuzzy analysis 7.1 Assumptions 7.2 Terms and Definitions 7.3 Analysis Logic 8. httprint - the advanced HTTP fingerprinting engine 8.1 httprint signatures 8.2 httprint command line and GUI interfaces 8.3 Running httprint 8.4 The significance of confidence ratings 8.5 httprint Reports 8.6 Customising httprint 9. Trying to defeat HTTP Fingerprinting 10. Conclusion 11. References 1. Abstract HTTP Fingerprinting is a relatively new topic of discussion in the context of application security. One of the biggest challenges of maintaining a high level of network security is to have a complete and accurate inventory of networked assets. Web servers and web applications have now become a part of the scope of a network security assessment exercise. In this paper, we present techniques to identify various types of HTTP servers. We shall discuss some of the problems faced in inventorying HTTP servers and how we can overcome them. We shall also introduce and describe a tool, httprint, which is built using the concepts discussed in this paper. 2. Theory of Fingerprinting A fingerprint is defined as: 1. The impression of a fingertip on any surface; also: an ink impression of the lines upon the fingertip taken for the purpose of identification.
    [Show full text]