Full download ebooks at https://ebookmeta.

com

Operating OpenShift (Third Early Release) Rick

Rackow

For dowload this book click link below

https://ebookmeta.com/product/operating-openshift-third-
early-release-rick-rackow/

OR CLICK BUTTON

DOWLOAD NOW
More products digital (pdf, epub, mobi) instant
download maybe you interests ...

Operating OpenShift Second Early Release 1st Edition

Rick Rackow Manuel Dewald

https://ebookmeta.com/product/operating-openshift-second-early-
release-1st-edition-rick-rackow-manuel-dewald/

Operating OpenShift: An SRE Approach to Managing

Infrastructure (Third Early Release) Rick Rackow

https://ebookmeta.com/product/operating-openshift-an-sre-
approach-to-managing-infrastructure-third-early-release-rick-
rackow/

Architecting and Operating OpenShift Clusters:

OpenShift for Infrastructure and Operations Teams 1st
Edition William Caban

https://ebookmeta.com/product/architecting-and-operating-
openshift-clusters-openshift-for-infrastructure-and-operations-
teams-1st-edition-william-caban/

Learning OpenTelemetry (First Early Release) First

Early Release: 2023-04-27 Edition Austin Parker

https://ebookmeta.com/product/learning-opentelemetry-first-early-
release-first-early-release-2023-04-27-edition-austin-parker/
Azure Cookbook (4th Early Release) Fourth Early
Release: 2023-06-22 Edition Reza Salehi

https://ebookmeta.com/product/azure-cookbook-4th-early-release-
fourth-early-release-2023-06-22-edition-reza-salehi/

Building Knowledge Graphs (6th Early Release) Sixth

Early Release: 2023-04-24 Edition Jesus Barrasa

https://ebookmeta.com/product/building-knowledge-graphs-6th-
early-release-sixth-early-release-2023-04-24-edition-jesus-
barrasa/

Flutter & Dart Cookbook (Fifth Early Release) 1 /

2022-09-16: Fifth Early Release Edition Richard Rose

https://ebookmeta.com/product/flutter-dart-cookbook-fifth-early-
release-1-2022-09-16-fifth-early-release-edition-richard-rose/

Hands-on Healthcare Data (Early Release) 1 /

2021-10-26: First Early Release Edition Andrew Nguyen

https://ebookmeta.com/product/hands-on-healthcare-data-early-
release-1-2021-10-26-first-early-release-edition-andrew-nguyen/

Implementing MLOps (Early Release) Noah Gift

https://ebookmeta.com/product/implementing-mlops-early-release-
noah-gift/
 Operating OpenShift
An SRE Approach to Managing Infrastructure

With Early Release ebooks, you get books in their earliest form—
the author’s raw and unedited content as they write—so you can
take advantage of these technologies long before the official
release of these titles.

Rick Rackow and Manuel Dewald

Operating OpenShift
by Rick Rackow and Manuel Dewald
Copyright © 2022 Rick Rackow and Manuel Dewald. 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://oreilly.com). For more information, contact our
corporate/institutional sales department: 800-998-9938 or
[email protected].

Acquisitions Editor: John Devins

Development Editor: Corbin Collins

Production Editor: Ashley Stussy

Interior Designer: David Futato

Cover Designer: Karen Montgomery

Illustrator: Kate Dullea

November 2022: First Edition

Revision History for the Early Release
2022-05-16: First Release
2022-08-11: Second Release
2022-09-20: Third Release
See http://oreilly.com/catalog/errata.csp?isbn=9781098106393 for
release details.
The O’Reilly logo is a registered trademark of O’Reilly Media, Inc.
Operating OpenShift, the cover image, and related trade dress are
trademarks of O’Reilly Media, Inc.
The views expressed in this work are those of the authors, and do
not represent the publisher’s views. While the publisher and the
authors have used good faith efforts to ensure that the information
and instructions contained in this work are accurate, the publisher
and the authors disclaim all responsibility for errors or omissions,
including without limitation responsibility for damages resulting from
the use of or reliance on this work. Use of the information and
instructions contained in this work is at your own risk. If any code
samples or other technology this work contains or describes is
subject to open source licenses or the intellectual property rights of
others, it is your responsibility to ensure that your use thereof
complies with such licenses and/or rights.
978-1-098-10632-4
Dedication
To Linus
— R.R.

To Marie
— M.D.
Preface

In late December 2020, a Slack notification from Rick popped up on

Manuel’s laptop.
“You know what?” it said, “You and I, we’re going to write a book!”
“What are we going to write about?”
“Operating OpenShift!”
Fast-forward almost two years, and that very book is now before
your eyes.
The backstory is that over the past several years, more and more
people reached out to us to ask if we would be able to share some
of our OpenShift insights with them — to help them operate their
OpenShift clusters more efficiently.
At that time the two of us worked as site reliability engineers for
OpenShift clusters at Red Hat. Efficiently operating OpenShift
clusters was indeed our day-to-day challenge, and we had
accumulated a lot of knowledge and expertise. We used that
experience to create this book.
We divided the ten chapters of this book according to our personal
interests and depth of experience. Chapters 1, 3, 5, 8, 9 and 10 are
written by Manuel. Chapters 2, 4, 6, and 7 are by Rick.
We learned a lot more about OpenShift in the past two years
working on the book. Even with our experience operating OpenShift
at Red Hat, many of the tools for operating and automating
operations still required further research and experimentation. We’ve
done our best to compile the results of our experiments into simple
steps that you can follow to get started. Of course, you’ll need to
adjust the examples to apply them to your specific needs as soon as
you start using the tools.
All the examples use the simplified scenario of an arcade gaming
platform that you’ll deploy to your cluster as you follow the book.
You’ll find the resources of this example workload in the
corresponding GitHub repository.

Conventions Used in This Book

The following typographical conventions are used in this book:
Italic
Indicates new terms, URLs, email addresses, filenames, and file
extensions.

Constant width
Used for program listings, as well as within paragraphs to refer to
program elements such as variable or function names, databases,
data types, environment variables, statements, and keywords.

Constant width bold

Shows commands or other text that should be typed literally by
the user.

Constant width italic

Shows text that should be replaced with user-supplied values or
by values determined by context.

TIP
This element signifies a tip or suggestion.
 NOTE
This element signifies a general note.

WARNING
This element indicates a warning or caution.

Using Code Examples

Supplemental material (code examples, exercises, etc.) is available
for download at https://github.com/OperatingOpenshift.
If you have a technical question or a problem using the code
examples, please send email to [email protected].
This book is here to help you get your job done. In general, if
example code is offered with this book, you may use it in your
programs and documentation. You do not need to contact us for
permission unless you’re reproducing a significant portion of the
code. For example, writing a program that uses several chunks of
code from this book does not require permission. Selling or
distributing examples from O’Reilly books does require permission.
Answering a question by citing this book and quoting example code
does not require permission. Incorporating a significant amount of
example code from this book into your product’s documentation
does require permission.
We appreciate, but generally do not require, attribution. An
attribution usually includes the title, author, publisher, and ISBN. For
example: “Book Title by Some Author (O’Reilly). Copyright 2012
Some Copyright Holder, 978-0-596-xxxx-x.”
If you feel your use of code examples falls outside fair use or the
permission given above, feel free to contact us at
[email protected].

O’Reilly Online Learning

NOTE
For more than 40 years, O’Reilly Media has provided technology and
business training, knowledge, and insight to help companies succeed.

Our unique network of experts and innovators share their knowledge

and expertise through books, articles, and our online learning
platform. O’Reilly’s online learning platform gives you on-demand
access to live training courses, in-depth learning paths, interactive
coding environments, and a vast collection of text and video from
O’Reilly and 200+ other publishers. For more information, visit
http://oreilly.com.

How to Contact Us
Please address comments and questions concerning this book to the
publisher:

O’Reilly Media, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

800-998-9938 (in the United States or Canada)

707-829-0515 (international or local)

707-829-0104 (fax)
We have a web page for this book, where we list errata, examples,
and any additional information. You can access this page at
https://oreil.ly/operating-openshift-1e.
Email [email protected] to comment or ask technical
questions about this book.
For news and information about our books and courses, visit
https://oreilly.com.
Find us on LinkedIn: https://linkedin.com/company/oreilly-media
Follow us on Twitter: https://twitter.com/oreillymedia
Watch us on YouTube: https://www.youtube.com/oreillymedia

Acknowledgments
Over the past two years, a lot of people have been supportive of our
idea for this book, and we would like to thank everyone who helped
us stay motivated and finish this work.
We’d like to thank the following people who worked with us from the
O’Reilly’s team:
John Devins helped us finalize the book proposal and convinced the
right people that it’s worth to invest in the topic. Corbin Collins, our
development editor, was always the first to review our raw material
and patiently corrected our formatting and grammar mistakes. He
also always had an eye on our roadmap and reached out in time if
adjustments needed to be made. Along with him, we also want to
thank Sara Hunter for her thorough reviews and incredibly helpful
feedback.
Our technical editors Andrew Block and Bilgin Ibrayam were
incredibly helpful and contributed lots of good ideas to improve the
content. They even mentioned alternatives that we’d overlooked in
our research.
A lot of the research done for this book involved chatting with the
right people, both inside Red Hat and in the open source
communities, who have been hard at work on the respective
components covered in this book. We’d like to thank everyone who
helped us get things up and running.
Finally, we want to thank our families, Stephanie, Linus, Julia, and
Marie, who have been supportive of the idea from the beginning,
and helped us free up time to focus on writing this book and put up
with our moods when things didn’t go all too well.
This book would not exist without you.
Chapter 1. Introduction
Manuel Dewald

A NOTE FOR EARLY RELEASE READERS

With Early Release ebooks, you get books in their earliest form—
the author’s raw and unedited content as they write—so you can
take advantage of these technologies long before the official
release of these titles.
This will be the 1st chapter of the final book. Please note that
the GitHub repo will be made active later on.
If you have comments about how we might improve the content
and/or examples in this book, or if you notice missing material
within this chapter, please reach out to the editor at
[email protected].

Operating distributed software is a difficult task. It requires humans

with a deep understanding of the system they maintain. No matter
how much automation you create, it will never replace highly skilled
operations personnel.
OpenShift is a platform, built to help software teams develop and
deploy their distributed software. It comes with a large set of tools
that are built-in or can be deployed easily. While it can be of great
help to its users and can eliminate a lot of traditionally manual
operations burdens, OpenShift itself is a distributed system, that
needs to be deployed, operated, and maintained.
Many companies have platform teams that provide development
platforms based on OpenShift to software teams so the maintenance
effort is centralized and the deployment patterns are standardized
across the organization. These platform teams are shifting more and
more into the direction of Site Reliability Engineering (SRE) teams,
where software development practices are applied to operations
tasks. Scripts are replaced by proper software solutions that can be
tested more easily and deployed automatically using CI/CD systems.
Alerts are transformed from simple cause-based alerts like “a high
amount of memory is used on Virtual Machine 23” into symptom-
based alerts based on Service Level Objectives (SLO) that reflect
customer experience, like “processing of requests takes longer than
we expect it to.”
OpenShift provides all the tools you need to run software on top of it
with SRE paradigms, from a monitoring platform to an integrated
CI/CD system that you can use to observe and run both the software
deployed to the OpenShift cluster, as well as the cluster itself. But
still building the automation, implementing a good alerting strategy,
and finally debugging issues that occur when operating an OpenShift
cluster are difficult tasks that require skilled operations or SRE
staffing.
Even in SRE teams, traditionally a good portion of the engineers’
time is dedicated to manual operations tasks, often called toil. The
operations time should be capped, though, as the main goal of SRE
is to tackle the toil with software engineering.
O’Reilly published a series of books written by SREs at Google,
related to the core SRE concepts. We encourage you to take a look
at these books if you’re interested in details about these principles.
In the first book, Site Reliability Engineering, the authors mostly
speak from their experience as SREs at Google, suggesting to limit
the time working on toil to 50% of an engineering team’s time.

Traditional Operations Teams

The goal of having an upper limit for toil is to avoid shifting back into
an operations team where people spend most of the time working
down toil that accumulates with both the scale of service adoption
and the advancement of the software.
Part of the accumulating toil while the service adoption grows is the
number of alerts an operations team gets if the alerting strategy isn’t
ready for scaling. If you’re maintaining software that creates one
alert per day per tenant, keeping one engineer busy running 10
tenants, you will need to scale the number of on-call engineers
linearly with the number of tenants the team operates. That means
in order to double the number of tenants, you need to double the
number of engineers dedicated to reacting to alerts. These
engineers will effectively not be able to work on reducing the toil
created by the alerts while working down the toil and investigating
the issues.
In a traditional operations team that runs OpenShift as a
development platform for other departments of the company,
onboarding new tenants is often a manual task. It may be initiated
by the requesting team to open a ticket that asks for a new
OpenShift cluster. Someone from the operations team will pick up
the ticket and start creating the required resources, kick off the
installer, configure the cluster so the requesting team gets access,
and so forth. A similar process may be set up for turning down
clusters when they are not needed anymore. Managing the lifecycle
of OpenShift clusters can be a huge source of toil, and as long as
the process is mainly manual, the amount of toil will scale with the
adoption of the service.
In addition to being toil-packed processes, manual lifecycle and
configuration management are error-prone. When an engineer runs
the same procedure several times during a week, as documented in
a team-managed Wiki, chances are they will miss an important step
or pass a wrong parameter to any of the scripts, resulting in a
broken state that may not be discovered immediately.
When managing multiple OpenShift clusters, having one that is
slightly different from the others due to a mistake in the provisioning
or configuration process, or even due to a customer request, is
dangerous and usually generates more toil. Automation that the
team generated over time may not be tailored to the specifics of a
single snowflake cluster. Running that automation may just not be
possible, causing more toil for the operations team. In the worst
case, it may even render the cluster unusable.
Automation in a traditional ops team can often be found in a central
repository, that can be checked out on engineer devices so they can
run the scripts they need as part of working on a documented
process. This is problematic not only because it still needs manual
interaction and hence doesn’t scale well, but also engineer’s devices
are often configured differently. They can differ in the OS they use,
adding the need to support different vendors in the tooling, for
example by providing a standardized environment like a container
environment to run the automation.
But even then, the version of the scripts to run may differ from
engineer to engineer, or the script to run hasn’t been updated when
it should’ve been as a new version of OpenShift has been released.
Automated testing is something that is seldomly implemented for
operations scripts made to quickly get rid of a piece of toil. All this
makes automation in scripts that are running on developer machines
brittle.

How Site Reliability Engineering Helps

In an SRE team, the goal is to replace such scripts with actual
software that is versioned properly, has a mature release strategy,
has a continuous integration and delivery process, and runs from the
latest released version on dedicated machines, for example, an
OpenShift cluster.
Another random document with
no related content on Scribd:
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 DAMAGES - Except 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 non-profit
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.