For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps.
Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end.
Recognizing also our responsibility to conser ve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine.
Manning Publications Co.
20 Baldwin Road
Development editor:Cynthia Kane
Technical development editor:Jerry Kuch PO Box 761
Shelter Island, NY 11964
ISBN: 9781617292927
Copyeditor:Sharon Wilkey
Proofreader:Melody Dolab
Technical proofreaders: Chris Schaefer, Yogesh Poojari
Typesetter:Dennis Dalinnik
Cover designer:Marija Tudor
Printed in the United States of America 12345678910–EBM–212019181716
For Sarah
forewordxv prefacexvii acknowledgementsxix about this bookxxi about the authorxxv about the cover illustrationxxvi PART 1HELLO,
MESOS
1
Introducing Mesos3
1.1Meet Mesos4
Understanding how it works5 ■ Comparing virtual machines and containers7 ■ Knowing when (and why) to use Mesos9
1.2Why we need to rethink the datacenter10 Partitioning of resources11 ■ Deploying applications12
Creating a schedule-based job154 ■ Creating a schedule-based job using Docker158
8.4Working with complex jobs160
Combining schedule-based and dependency-based jobs160 Visualizing job dependencies163
8.5Monitoring the output and status of Chronos jobs164
Job failure notifications and monitoring165 ■ Observing standard output and standard error via Mesos167
8.6Summary167
9 Deploying applications and managing scheduled tasks with Aurora169
9.1Introducing Aurora170
The Aurora scheduler171 ■ The Thermos executor and observer171 ■ The Aurora user and admin clients172 The Aurora domain-specific language173
9.2Deploying Aurora174
Trying out Aurora in a development environment175 Building and installing Aurora176 ■ Configuring Aurora178
9.3Deploying applications183
Deploying a simple application184 ■ Deploying a Docker-based application187
9.4Managing scheduled tasks189
Creating a Cron job189 ■ Creating a Docker-based Cron job190
9.5Administering Aurora192
Managing users and quotas192 ■ Performing maintenance194
9.6Summary195
10 Developing a framework196
10.1Understanding framework basics197
When and why would you write a framework?199 The scheduler implementation200 ■ The executor implementation202
10.2Developing a scheduler206
Working with the Scheduler API207 ■ Working with the SchedulerDriver209
10.3Developing an executor210
Working with the Executor API210 ■ Working with the executor driver212
10.4Running the framework213
Deploying in development213 ■ Considerations for a production deployment215
10.5Summary216
appendix ACase study: Mesosphere DCOS, an enterprise Mesos distribution217 appendix BList of Mesos frameworks and tools229 index237
foreword
If you ever want to see a man’s head explode, walk up to somebody whose job it is to manually configure and provision scores of servers inside a datacenter, and say the following: “Wow! It must be so easy, and so much fun, to keep track of what’s running on which machines.”
Or find a person who has spent years carrying a pager and responding to server outages and say, “Sounds like a stress-free job. At least it guarantees you get a good night’s sleep.”
The truth, of course, is that managing servers and other datacenter infrastructure has historically been difficult, tedious, and full of sleepless nights for the poor men and women charged with configuring all these machines and responding to failures whenever they strike. As companies started relying more heavily on information technology during the past 20 years, often housing one application per server (or, in recent years, virtual machine), the practice grew increasingly difficult. A few servers grew to dozens, dozens grew to hundreds, and hundreds sometimes grew to thousands.
Then the web blew up, fueled by incredibly popular services such as Google, Facebook, and Twitter. The mobile web, fueled by billions of smartphones, tablets, and other devices, followed shortly thereafter. Old ways of computing could no longer cut it in a world where millions of users might be on a site or app at any given time.
Inside datacenters, single-server databases (single-server everything, really) were rapidly replaced by distributed systems that could handle previously unimaginable volumes of data and traffic. Often, complex monolithic applications were replaced by microservices—collections of single-purpose services managed separately, then connected via API
to construct end-user applications. Scalability demands increased, but so did the learning curve for building these systems and the complexity of managing them.
Google famously solved this problem inside its own datacenters with a system called Borg, which ostensibly let most employees—systems administrators and developers alike—manage hundreds of thousands of servers like one big computer. Several years after Borg simplified operations at Google, the open source Apache Mesos project hit the scene and changed the lives of its users in similar ways. All of a sudden, the process of deploying, running, and managing complex distributed systems became much simpler; everything shares the same set of machines, and Mesos handles the legwork of matching workload requirements with available resources.
I experienced this shift firsthand as a software engineer at Twitter, where Mesos helped conquer the infamous fail whale and helped Twitter reach new heights of scalability and reliability. When I moved on to Airbnb in 2012, then a fast-growing startup just four years old, Mesos once again helped us grow our infrastructure—but not the complexity of it—along with our user base. I was so impressed with Mesos and its promise that I decided to start a company, Mesosphere, dedicated to making Mesos usable by mainstream enterprises.
As Mesos grew in popularity and Mesosphere grew in size, we set our sights on hiring the best Mesos engineers and practitioners around. When we saw the work Roger Ignazio had done building out a Mesos-based continuous integration platform at Puppet Labs, we knew we had to have him. Running scalable production systems at established companies is always valuable experience, and since joining Mesosphere, Roger’s experience has been a boon to the quality of our Mesos-based Datacenter Operating System technology and to our customers’ experiences with it.
With Mesos in Action, Roger lets anyone who is interested in Mesos and its ecosystem of technologies take advantage of his experience. The book is a great guide to getting a Mesos cluster running and installing your first frameworks, but also delves into more-advanced topics such as mastering powerful Mesos frameworks (including Marathon for container orchestration and Spark for big data analytics) and even building your own framework.
Whether you’re preparing to deploy Mesos or already have it running and want to improve your knowledge, you would be hard-pressed to find a better guide than Roger and a better book than Mesos in Action
FLORIAN LEIBERT COFOUNDER AND CEO, MESOSPHERE
preface
Apache Mesos began in 2009 as a research project at the University of California at Berkeley, led by Benjamin Hindman. Ben and his team wanted to improve datacenter efficiency by allowing multiple applications to share a single computing cluster, just like multiple applications can share the processor, memory, and hard drive in your laptop or workstation. But they wanted to do this across the many servers that make up a modern datacenter. After an initial implementation of 10,000 lines of C++ code, they published the paper Mesos: A Platform for Fine-Grained Resource Sharing in the Data Center in 2010.
Not long after, Ben joined Twitter and used Mesos to better scale its infrastructure, largely bringing an end to the era of the “fail whale” that became infamous as Twitter was rising in popularity and its servers couldn’t handle the demand from users. Although Twitter doesn’t publicly disclose the number of servers in its expansive infrastructure, online sources and firsthand knowledge from presentations put this somewhere in the ballpark of 10,000 Mesos nodes per cluster.
In December 2010, the Mesos project entered the Apache Incubator, an arm of the Apache Software Foundation that provides a means for projects to gain the full support of the ASF’s efforts. The Apache Mesos project graduated from the incubator in June 2013 and is now a top-level project.
In 2013, Ben—along with Florian Leibert and Tobi Knaup—founded Mesosphere. Mesosphere’s flagship product, the Datacenter Operating System (DCOS), commercializes the success of the open source project by providing a turnkey solution to enterprises looking to deploy applications and scale infrastructure as effortlessly as
other companies using Mesos, such as Airbnb, Apple, and Netflix. Mesosphere continues to be a major contributor to the open source Mesos project and provides Mesos packages and tools to the open source community.
My foray into the Mesos ecosystem and large-scale infrastructure began in 2014 when I started looking at using Mesos to share resources among multiple instances of Jenkins, the popular continuous integration framework. At the time, it seemed like Mesos was reserved for those who already knew about it; a lot of resources were available online but were hard to find, and there wasn’t a single canonical source of truth. There also weren’t any books covering Mesos. I wrote a couple of blog posts about my experience, and it seemed like other people were in the same boat I was in: wanting to know more about this project but not knowing where to start.
In January 2015, Manning reached out and asked if I’d be interested in writing a book about Mesos. Having never written a book before, the request seemed overwhelming at first. But I also saw it as an opportunity to write the book that I wished I had when I first started using Mesos. Fortunately, the team at Manning gave me the freedom to do just that.
I hope that you find Mesos in Action a valuable resource for deploying and administering Mesos clusters and improving the overall efficiency of your infrastructure, and that it allows your team—and your customers—to deploy applications to production quickly and easily.
OREGON
ROGER IGNAZIO PORTLAND,
acknowledgements
You’re reading the result of a yearlong effort to produce an in-depth book on the Apache Mesos project and ecosystem. Despite my name being on the cover, many people contributed to the final publication, people who would otherwise remain anonymous if I didn’t thank them here. I’m sure that my family, my friends, and my wife already know how much I appreciate their support through this endeavor.
First, I’d like to thank the Mesos community. In every interaction—at conferences, on the mailing lists, on IRC—everyone has been extremely helpful and kind. As of this writing, there are over 100 individual contributors to the Mesos code base, and even more people who volunteer their time on the Mesos mailing lists and chat rooms to answer questions and provide help. In addition to all the people I’ve had the pleasure of talking to at conferences and working with on a daily basis, I’d like to thank Ben Hindman, Florian Leibert, Thomas Rampelberg, Dave Lester, Christian Bogeberg, and Michael Hausenblas for all of their help. And I’d like to thank Florian for writing the foreword to this book.
Next, as if writing a book isn’t already a stressful and time-consuming task, I changed jobs about two-thirds of the way through writing. At Puppet Labs, I’d like to thank Scott Schneider, Colin Creeden, Cody Herriges, Eric Zounes, and Alanna Brown for their support. Before I even signed with Manning, I recall a moment when Scott asked if I really thought you could write an entire book about Mesos; as it turns out, you can! Many people behind the scenes helped review the book at various stages and provided feedback, including Al Rahimi, Clive Harber, Iain Campbell, Jeroen Benckhuijsen, John Guthrie, Ken Sipe, Luis Moux Domínguez, Marco Massenzio,
Mohsen Mostafar Jokar, Morgan Nelson, Nitin Gode, Odysseas Pentakalos, and Thomas Peklak. A special thank you goes out to Jerry Kuch and Chris Schaefer for their technical reviews, and to copy editor Sharon Wilkey for making a countless number of fixes to the original manuscript.
Last, but certainly not least, I need to thank my amazing team at Manning Publications. My editor, Mike Stevens, helped me get from “That sounds like a lot of jargon!” to a formal proposal and signed contract. Development editor Cynthia Kane ensured I was always providing the right amount of context (in both text and graphics), and helped me become a better writer and communicator. And finally, to my publisher Marjan Bace, who not only helped shape the book during the editorial board review, but also ultimately gave me the freedom to write the book that I wish I had when I first got started with Mesos. Thank you!
I’m grateful to all of the people who helped get the book to this point, and I apologize if I’ve forgotten to mention anyone here.
about this book
Mesos in Action is a practical guide to learning about and deploying Apache Mesos in a real-world setting. I provide a complete tour of the project—from a basic introduction that introduces Mesos and containers, to production-ready deployments that include high availability and framework authentication. I also provide real-world usage of popular (and open source!) Mesos applications that allow you to deploy applications and scheduled jobs on your Mesos cluster.
Although Mesos in Action is tailored for intermediate-to-advanced systems administrators, it’s well suited for various audiences. I’ve written the book in such a way that systems administrators, DevOps, application administrators, and software engineers alike will feel at home throughout the text. Although some knowledge of application deployments and software development is desirable, I’ve provided enough background that it isn’t strictly required, instead opting to teach you new skills that you can use to make teams—your own included—work smarter, not harder.
Roadmap
If you are a systems administrator or DevOps person looking to deploy your first Mesos cluster, you’ll want to pay particular attention to chapters 1 through 8. These chapters cover everything you need to know to get a cluster up and running, and cover a few ways you can use it to deploy applications and scheduled jobs. Chapter 10 may also be beneficial in helping you to understand how to write your own Mesosenabled applications. Otherwise, this book is divided into three parts.
Part 1 introduces the Apache Mesos project, compares containers to virtual machines, and presents a real-world use case for deploying a Mesos cluster.
■ Chapter 1 introduces the Mesos project. I cover key terms and components used throughout the book, introduce the architecture, and explain how deploying applications in containers is different from deployments in a traditional datacenter.
■ Chapter 2 builds upon the introduction provided in chapter 1 by running an Apache Spark data-processing job on the Mesos cluster. You’ll see a real-world workload running on the cluster and observe how the cluster behaves. You’ll also get a sense of how Mesos allows multiple applications to share cluster resources, leading to improved datacenter utilization.
Part 2 examines the Mesos fundamentals in detail, including installation and configuration, high availability, and monitoring.
■ Chapter 3 provides a soup-to-nuts approach for deploying Mesos on your own servers, whether they’re in your own datacenter or running on a cloud provider such as AWS or Azure. You’ll learn how to install and configure ZooKeeper, Mesos, and Docker, and should have a highly available cluster up and running by the end of the chapter.
■ Chapter 4 examines the fundamentals of the Mesos project. You’ll learn about the scalability, fault tolerance, high availability, and resource isolation that Mesos provides.
■ Chapter 5 provides a tour of how Mesos handles logs and how you can debug issues when they arise. I cover topics including the Mesos web interface, CLI, log file locations, and logging configuration.
■ Chapter 6 covers topics necessary for running Mesos in a production environment. This includes information about monitoring the Mesos and ZooKeeper clusters, as well as security and access control for users and frameworks alike.
Part 3 provides you with real-world uses for Mesos.
■ Chapter 7 introduces the open source Marathon framework, which allows you to deploy applications and long-running services in Linux and Docker containers across the cluster simply by specifying the amount of resources and number of instances you’d like.
■ Chapter 8 introduces the open source Chronos framework, which allows you to deploy scheduled jobs on the cluster using ISO 8601–formatted timestamps. Chronos allows jobs to run on a schedule, or allows them to be dependencies on other jobs, and supports tasks running in both Linux and Docker containers.
■ Chapter 9 introduces the open source Apache Aurora framework, which— similar to Marathon and Chronos—allows you to deploy both applications and scheduled jobs on a Mesos cluster. Where it differs, however, is that Aurora has
support for multiple users out of the box, and a sophisticated configuration language to match.
■ Chapter 10 provides a tour of the Mesos APIs, and includes an example (written in Python) of how to develop your own Mesos applications.
■ Appendix A provides a case study on Mesosphere’s Datacenter Operating System (DCOS), an enterprise-grade Mesos distribution, as well as a walk-through of how to set up a continuous deployment pipeline using DCOS, Jenkins, and Marathon.
■ Appendix B provides a list of Mesos-related projects known at the time of writing. These projects range from Mesos applications, to language bindings, to load-balancing and service-discovery tools. Each entry is accompanied by a short description and a link to additional information online.
Source code
The code for the examples and configuration files used throughout this book is available on GitHub, located at github.com/rji/mesos-in-action-code-samples. The code is also available from this book’s website, located at manning.com/books/mesos-in-action.
Much of the code for parts 1 and 2 of the book consists of configuration fragments designed to support or enhance the text. The code for part 3 includes examples of applications and data-processing jobs that are used to illustrate how you might run these workloads on your own infrastructure.
Typographical conventions
■ Italic typeface is used to introduce new terms.
■ Courier typeface is used to denote code samples and commands.
■ Code-line continuations are indicated by ➥.
Online and community resources
Many online and community resources are available for the Mesos project. First, and perhaps most important, you can find the latest documentation online at http:// mesos.apache.org/documentation/latest. For those interested in Mesos development and where the project is heading, it might be best to consult the project’s issue tracker, located at https://issues.apache.org/jira/browse/MESOS.
In addition to using these two resources, you can communicate and interact with other people in the Mesos community in the following ways:
■ Mailing lists —Several mailing lists relating to Mesos exist, but perhaps the two most important are the users and dev mailing lists. More info can be found on the Mesos project’s community page at http://mesos.apache.org/community.
■ IRC —Developers and users alike chat in the #mesos channel on irc.freenode.net.
■ Planet Mesos —An RSS aggregator for members of the Mesos community, Planet Mesos contains writings and presentations from project maintainers, contributors,
and conferences. The aggregator itself is available at http://planet.apache.org/ mesos. The team also operates a Twitter account that automatically updates when the RSS feed does; it can be found at https://twitter.com/PlanetMesos.
■ Twitter —The official Twitter feed for the project is located at https://twitter.com/ ApacheMesos.
■ MesosCon —Started in 2014, MesosCon is an annual conference organized by the Mesos community. It has hosted talks from some of the largest internet companies on how they use Mesos to solve scaling problems. More information is available at http://events.linuxfoundation.org/events/mesoscon.
Author Online
Purchase of Mesos in Action includes free access to a private web forum run by Manning Publications; you can make comments about the book, ask technical questions, and receive help from the author and from other users. To access the forum and subscribe to it, point your web browser to manning.com/books/mesos-in-action. This page provides information on how to get on the forum after you’re registered, what kind of help is available, and the rules of conduct on the forum.
Manning’s commitment to our readers is to provide a venue where a meaningful dialogue between individual readers and between readers and the author can take place. It’s not a commitment to any specific amount of participation on the part of the author, whose contribution to AO remains voluntary (and unpaid). We suggest you try asking the author some challenging questions lest his interest stray!
The Author Online forum and the archives of previous discussions will be accessible from the publisher’s website as long as the book is in print.
about the author
Roger Ignazio is an experienced systems engineer with a focus on distributed, fault-tolerant, and scalable infrastructure. He is passionate about improving productivity through better automation, tooling, and reporting. He’s currently a technical lead on the engineering team at Mesosphere, and lives in Portland, Oregon with his wife Sarah and their two cats.
about the cover illustration
On the cover of Mesos in Action is “Girl from Petrovo Polje, Dalmatia, Croatia.” The term “Polje” derives from the Slavic for “field” and is used to denote a large flat plain. Petrovo Polje is located in Dalmatia, a historical region of Croatia on the Adriatic coast. Dalmatia was once a province of the Roman Empire, and over its history has been fought over and controlled by the Goths, the Byzantines, the Venetians, and the Austro-Hungarian Empire. The illustration is taken from a reproduction of an album of Croatian traditional costumes from the mid-nineteenth century by Nikola Arsenovic, published by the Ethnographic Museum in Split, Croatia, in 2003. The illustrations were obtained from a helpful librarian at the Ethnographic Museum in Split, itself situated in the Roman core of the medieval center of that town: the ruins of Emperor Diocletian’s retirement palace from around AD 304. The book includes finely colored illustrations of figures from different regions of Croatia, accompanied by descriptions of the costumes and of everyday life.
Dress codes and lifestyles have changed over the last 200 years, and the diversity by region, so rich at the time, has faded away. It is now hard to tell apart the inhabitants of different continents, let alone of different hamlets or towns separated by only a few miles. Perhaps we have traded cultural diversity for a more varied personal life—certainly for a more varied and fast-paced technological life.
Manning celebrates the inventiveness and initiative of the computer business with book covers based on the rich diversity of regional life of two centuries ago, brought back to life by illustrations from old books and collections like this one.
Part 1
Hello, Mesos
What is Apache Mesos? How does Mesos compare to traditional datacenter architecture? How are containers different from virtual machines? Why might you use Mesos? These are questions that I begin to address in part 1. You’ll learn about the Apache Mesos project and its use of containers by comparing and contrasting these relatively new technologies to that of a traditional datacenter. You’ll also see a practical example of Mesos in action in the context of running an Apache Spark data-processing job on the cluster.
Another random document with no related content on Scribd:
*** END OF THE PROJECT GUTENBERG EBOOK SUNSHINE AND SHADOW, OR, PAUL BURTON'S SURPRISE ***
Updated editions will replace the previous one—the old editions will be renamed.
Creating the works from print editions not protected by U.S. copyright law means that no one owns a United States copyright in these works, so the Foundation (and you!) can copy and distribute it in the United States without permission and without paying copyright royalties. Special rules, set forth in the General Terms of Use part of this license, apply to copying and distributing Project Gutenberg™ electronic works to protect the PROJECT GUTENBERG™ concept and trademark. Project Gutenberg is a registered trademark, and may not be used if you charge for an eBook, except by following the terms of the trademark license, including paying royalties for use of the Project Gutenberg trademark. If you do not charge anything for copies of this eBook, complying with the trademark license is very easy. You may use this eBook for nearly any purpose such as creation of derivative works, reports, performances and research. Project Gutenberg eBooks may be modified and printed and given away—you may do practically ANYTHING in the United States with eBooks not protected by U.S. copyright law. Redistribution is subject to the trademark license, especially commercial redistribution.
START: FULL LICENSE
THE FULL PROJECT GUTENBERG LICENSE
PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK
To protect the Project Gutenberg™ mission of promoting the free distribution of electronic works, by using or distributing this work (or any other work associated in any way with the phrase “Project Gutenberg”), you agree to comply with all the terms of the Full Project Gutenberg™ License available with this file or online at www.gutenberg.org/license.
Section 1. General Terms of Use and Redistributing Project Gutenberg™ electronic works
1.A. By reading or using any part of this Project Gutenberg™ electronic work, you indicate that you have read, understand, agree to and accept all the terms of this license and intellectual property (trademark/copyright) agreement. If you do not agree to abide by all the terms of this agreement, you must cease using and return or destroy all copies of Project Gutenberg™ electronic works in your possession. If you paid a fee for obtaining a copy of or access to a Project Gutenberg™ electronic work and you do not agree to be bound by the terms of this agreement, you may obtain a refund from the person or entity to whom you paid the fee as set forth in paragraph 1.E.8.
1.B. “Project Gutenberg” is a registered trademark. It may only be used on or associated in any way with an electronic work by people who agree to be bound by the terms of this agreement. There are a few things that you can do with most Project Gutenberg™ electronic works even without complying with the full terms of this agreement. See paragraph 1.C below. There are a lot of things you can do with Project Gutenberg™ electronic works if you follow the terms of this agreement and help preserve free future access to Project Gutenberg™ electronic works. See paragraph 1.E below.
1.C. The Project Gutenberg Literary Archive Foundation (“the Foundation” or PGLAF), owns a compilation copyright in the collection of Project Gutenberg™ electronic works. Nearly all the individual works in the collection are in the public domain in the United States. If an individual work is unprotected by copyright law in the United States and you are located in the United States, we do not claim a right to prevent you from copying, distributing, performing, displaying or creating derivative works based on the work as long as all references to Project Gutenberg are removed. Of course, we hope that you will support the Project Gutenberg™ mission of promoting free access to electronic works by freely sharing Project Gutenberg™ works in compliance with the terms of this agreement for keeping the Project Gutenberg™ name associated with the work. You can easily comply with the terms of this agreement by keeping this work in the same format with its attached full Project Gutenberg™ License when you share it without charge with others.
1.D. The copyright laws of the place where you are located also govern what you can do with this work. Copyright laws in most countries are in a constant state of change. If you are outside the United States, check the laws of your country in addition to the terms of this agreement before downloading, copying, displaying, performing, distributing or creating derivative works based on this work or any other Project Gutenberg™ work. The Foundation makes no representations concerning the copyright status of any work in any country other than the United States.
1.E. Unless you have removed all references to Project Gutenberg:
1.E.1. The following sentence, with active links to, or other immediate access to, the full Project Gutenberg™ License must appear prominently whenever any copy of a Project Gutenberg™ work (any work on which the phrase “Project Gutenberg” appears, or with which the phrase “Project
Gutenberg” is associated) is accessed, displayed, performed, viewed, copied or distributed:
This eBook is for the use of anyone anywhere in the United States and most other parts of the world at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org. If you are not located in the United States, you will have to check the laws of the country where you are located before using this eBook.
1.E.2. If an individual Project Gutenberg™ electronic work is derived from texts not protected by U.S. copyright law (does not contain a notice indicating that it is posted with permission of the copyright holder), the work can be copied and distributed to anyone in the United States without paying any fees or charges. If you are redistributing or providing access to a work with the phrase “Project Gutenberg” associated with or appearing on the work, you must comply either with the requirements of paragraphs 1.E.1 through 1.E.7 or obtain permission for the use of the work and the Project Gutenberg™ trademark as set forth in paragraphs 1.E.8 or 1.E.9.
1.E.3. If an individual Project Gutenberg™ electronic work is posted with the permission of the copyright holder, your use and distribution must comply with both paragraphs 1.E.1 through 1.E.7 and any additional terms imposed by the copyright holder. Additional terms will be linked to the Project Gutenberg™ License for all works posted with the permission of the copyright holder found at the beginning of this work.
1.E.4. Do not unlink or detach or remove the full Project Gutenberg™ License terms from this work, or any files containing a part of this work or any other work associated with Project Gutenberg™.
1.E.5. Do not copy, display, perform, distribute or redistribute this electronic work, or any part of this electronic work, without prominently displaying the sentence set forth in paragraph 1.E.1 with active links or immediate access to the full terms of the Project Gutenberg™ License.
1.E.6. You may convert to and distribute this work in any binary, compressed, marked up, nonproprietary or proprietary form, including any word processing or hypertext form. However, if you provide access to or distribute copies of a Project Gutenberg™ work in a format other than “Plain Vanilla ASCII” or other format used in the official version posted on the official Project Gutenberg™ website (www.gutenberg.org), you must, at no additional cost, fee or expense to the user, provide a copy, a means of exporting a copy, or a means of obtaining a copy upon request, of the work in its original “Plain Vanilla ASCII” or other form. Any alternate format must include the full Project Gutenberg™ License as specified in paragraph 1.E.1.
1.E.7. Do not charge a fee for access to, viewing, displaying, performing, copying or distributing any Project Gutenberg™ works unless you comply with paragraph 1.E.8 or 1.E.9.
1.E.8. You may charge a reasonable fee for copies of or providing access to or distributing Project Gutenberg™ electronic works provided that:
• You pay a royalty fee of 20% of the gross profits you derive from the use of Project Gutenberg™ works calculated using the method you already use to calculate your applicable taxes. The fee is owed to the owner of the Project Gutenberg™ trademark, but he has agreed to donate royalties under this paragraph to the Project Gutenberg Literary Archive Foundation. Royalty payments must be paid within 60 days following each date on which you prepare (or are legally required to prepare) your periodic tax returns. Royalty payments should be clearly marked as such and sent to the Project Gutenberg Literary Archive Foundation at the address specified in Section 4, “Information
about donations to the Project Gutenberg Literary Archive Foundation.”
• You provide a full refund of any money paid by a user who notifies you in writing (or by e-mail) within 30 days of receipt that s/he does not agree to the terms of the full Project Gutenberg™ License. You must require such a user to return or destroy all copies of the works possessed in a physical medium and discontinue all use of and all access to other copies of Project Gutenberg™ works.
• You provide, in accordance with paragraph 1.F.3, a full refund of any money paid for a work or a replacement copy, if a defect in the electronic work is discovered and reported to you within 90 days of receipt of the work.
• You comply with all other terms of this agreement for free distribution of Project Gutenberg™ works.
1.E.9. If you wish to charge a fee or distribute a Project Gutenberg™ electronic work or group of works on different terms than are set forth in this agreement, you must obtain permission in writing from the Project Gutenberg Literary Archive Foundation, the manager of the Project Gutenberg™ trademark. Contact the Foundation as set forth in Section 3 below.
1.F.
1.F.1. Project Gutenberg volunteers and employees expend considerable effort to identify, do copyright research on, transcribe and proofread works not protected by U.S. copyright law in creating the Project Gutenberg™ collection. Despite these efforts, Project Gutenberg™ electronic works, and the medium on which they may be stored, may contain “Defects,” such as, but not limited to, incomplete, inaccurate or corrupt data, transcription errors, a copyright or other intellectual property infringement, a defective or damaged disk or other
medium, a computer virus, or computer codes that damage or cannot be read by your equipment.
1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGESExcept for the “Right of Replacement or Refund” described in paragraph 1.F.3, the Project Gutenberg Literary Archive Foundation, the owner of the Project Gutenberg™ trademark, and any other party distributing a Project Gutenberg™ electronic work under this agreement, disclaim all liability to you for damages, costs and expenses, including legal fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT EXCEPT THOSE PROVIDED IN PARAGRAPH
1.F.3. YOU AGREE THAT THE FOUNDATION, THE TRADEMARK OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE OR INCIDENTAL DAMAGES EVEN IF YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH DAMAGE.
1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you discover a defect in this electronic work within 90 days of receiving it, you can receive a refund of the money (if any) you paid for it by sending a written explanation to the person you received the work from. If you received the work on a physical medium, you must return the medium with your written explanation. The person or entity that provided you with the defective work may elect to provide a replacement copy in lieu of a refund. If you received the work electronically, the person or entity providing it to you may choose to give you a second opportunity to receive the work electronically in lieu of a refund. If the second copy is also defective, you may demand a refund in writing without further opportunities to fix the problem.
1.F.4. Except for the limited right of replacement or refund set forth in paragraph 1.F.3, this work is provided to you ‘AS-IS’, WITH NO OTHER WARRANTIES OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PURPOSE.
1.F.5. Some states do not allow disclaimers of certain implied warranties or the exclusion or limitation of certain types of damages. If any disclaimer or limitation set forth in this agreement violates the law of the state applicable to this agreement, the agreement shall be interpreted to make the maximum disclaimer or limitation permitted by the applicable state law. The invalidity or unenforceability of any provision of this agreement shall not void the remaining provisions.
1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation, the trademark owner, any agent or employee of the Foundation, anyone providing copies of Project Gutenberg™ electronic works in accordance with this agreement, and any volunteers associated with the production, promotion and distribution of Project Gutenberg™ electronic works, harmless from all liability, costs and expenses, including legal fees, that arise directly or indirectly from any of the following which you do or cause to occur: (a) distribution of this or any Project Gutenberg™ work, (b) alteration, modification, or additions or deletions to any Project Gutenberg™ work, and (c) any Defect you cause.
Section 2. Information about the Mission of Project Gutenberg™
Project Gutenberg™ is synonymous with the free distribution of electronic works in formats readable by the widest variety of computers including obsolete, old, middle-aged and new computers. It exists because of the efforts of hundreds of volunteers and donations from people in all walks of life.
Volunteers and financial support to provide volunteers with the assistance they need are critical to reaching Project
Gutenberg™’s goals and ensuring that the Project Gutenberg™ collection will remain freely available for generations to come. In 2001, the Project Gutenberg Literary Archive Foundation was created to provide a secure and permanent future for Project Gutenberg™ and future generations. To learn more about the Project Gutenberg Literary Archive Foundation and how your efforts and donations can help, see Sections 3 and 4 and the Foundation information page at www.gutenberg.org.
Section 3. Information about the Project Gutenberg Literary Archive Foundation
The Project Gutenberg Literary Archive Foundation is a nonprofit 501(c)(3) educational corporation organized under the laws of the state of Mississippi and granted tax exempt status by the Internal Revenue Service. The Foundation’s EIN or federal tax identification number is 64-6221541. Contributions to the Project Gutenberg Literary Archive Foundation are tax deductible to the full extent permitted by U.S. federal laws and your state’s laws.
The Foundation’s business office is located at 809 North 1500 West, Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up to date contact information can be found at the Foundation’s website and official page at www.gutenberg.org/contact
Section 4. Information about Donations to the Project Gutenberg Literary Archive Foundation
Project Gutenberg™ depends upon and cannot survive without widespread public support and donations to carry out its mission of increasing the number of public domain and licensed works that can be freely distributed in machine-readable form
accessible by the widest array of equipment including outdated equipment. Many small donations ($1 to $5,000) are particularly important to maintaining tax exempt status with the IRS.
The Foundation is committed to complying with the laws regulating charities and charitable donations in all 50 states of the United States. Compliance requirements are not uniform and it takes a considerable effort, much paperwork and many fees to meet and keep up with these requirements. We do not solicit donations in locations where we have not received written confirmation of compliance. To SEND DONATIONS or determine the status of compliance for any particular state visit www.gutenberg.org/donate.
While we cannot and do not solicit contributions from states where we have not met the solicitation requirements, we know of no prohibition against accepting unsolicited donations from donors in such states who approach us with offers to donate.
International donations are gratefully accepted, but we cannot make any statements concerning tax treatment of donations received from outside the United States. U.S. laws alone swamp our small staff.
Please check the Project Gutenberg web pages for current donation methods and addresses. Donations are accepted in a number of other ways including checks, online payments and credit card donations. To donate, please visit: www.gutenberg.org/donate.
Section 5. General Information About Project Gutenberg™ electronic works
Professor Michael S. Hart was the originator of the Project Gutenberg™ concept of a library of electronic works that could be freely shared with anyone. For forty years, he produced and
distributed Project Gutenberg™ eBooks with only a loose network of volunteer support.
Project Gutenberg™ eBooks are often created from several printed editions, all of which are confirmed as not protected by copyright in the U.S. unless a copyright notice is included. Thus, we do not necessarily keep eBooks in compliance with any particular paper edition.
Most people start at our website which has the main PG search facility: www.gutenberg.org.
This website includes information about Project Gutenberg™, including how to make donations to the Project Gutenberg Literary Archive Foundation, how to help produce our new eBooks, and how to subscribe to our email newsletter to hear about new eBooks.
