Kief Morris - Infrastructure as Code: Managing Servers in the Cloud
Here you can read online Kief Morris - Infrastructure as Code: Managing Servers in the Cloud full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2016, publisher: O’Reilly Media, genre: Computer / Science. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:
Romance novel
Science fiction
Adventure
Detective
Science
History
Home and family
Prose
Art
Politics
Computer
Non-fiction
Religion
Business
Children
Humor
Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.
- Book:Infrastructure as Code: Managing Servers in the Cloud
- Author:
- Publisher:O’Reilly Media
- Genre:
- Year:2016
- Rating:5 / 5
- Favourites:Add to favourites
- Your mark:
Infrastructure as Code: Managing Servers in the Cloud: summary, description and annotation
We offer to read an annotation, description, summary or preface (depends on what the author of the book "Infrastructure as Code: Managing Servers in the Cloud" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.
Virtualization, cloud, containers, server automation, and software-defined networking are meant to simplify IT operations. But many organizations adopting these technologies have found that it only leads to a faster-growing sprawl of unmanageable systems. This is where infrastructure as code can help. With this practical guide, author Kief Morris of ThoughtWorks shows you how to effectively use principles, practices, and patterns pioneered through the DevOps movement to manage cloud age infrastructure.
Ideal for system administrators, infrastructure engineers, team leads, and architects, this book demonstrates various tools, techniques, and patterns you can use to implement infrastructure as code. In three parts, youll learn about the platforms and tooling involved in creating and configuring infrastructure elements, patterns for using these tools, and practices for making infrastructure as code work in your environment.
- Examine the pitfalls that organizations fall into when adopting the new generation of infrastructure technologies
- Understand the capabilities and service models of dynamic infrastructure platforms
- Learn about tools that provide, provision, and configure core infrastructure resources
- Explore services and tools for managing a dynamic infrastructure
- Learn specific patterns and practices for provisioning servers, building server templates, and updating running servers
Kief Morris: author's other books
Who wrote Infrastructure as Code: Managing Servers in the Cloud? Find out the surname, the name of the author of the book and a list of all author's works by series.
Infrastructure as Code: Managing Servers in the Cloud — read online for free the complete book (whole text) full work
Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Infrastructure as Code: Managing Servers in the Cloud" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.
Font size:
Interval:
Bookmark:
by Kief Morris
Copyright 2016 Kief Morris. All rights reserved.
Printed in the United States of America.
Published by OReilly Media, Inc. , 1005 Gravenstein Highway North, Sebastopol, CA 95472.
OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://safaribooksonline.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com .
Editor: Brian Anderson | Indexer: Judy McConville |
Production Editor: Kristen Brown | Interior Designer: David Futato |
Copyeditor: Amanda Kersey | Cover Designer: Karen Montgomery |
Proofreader: Jasmine Kwityn | Illustrator: Rong Tang and Rebecca Demarest |
- June 2016: First Edition
- 2016-06-07: First Release
See http://oreilly.com/catalog/errata.csp?isbn=9781491924358 for release details.
The OReilly logo is a registered trademark of OReilly Media, Inc. Infrastructure as Code, the cover image, and related trade dress are trademarks of OReilly Media, Inc.
While the publisher and the author have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the author 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-491-92435-8
[LSI]
Infrastructure and software development teams are increasingly building and managing infrastructure using automated tools that have been described as infrastructure as code. These tools expect users to define their servers, networking, and other elements of an infrastructure in files modeled after software source code. The tools then compile and interpret these files to decide what action to take.
The DevOps movement is mainly about culture and collaboration between software developers and software operations people. Tooling that manages infrastructure based on a software development paradigm has helped bring these communities together.
Managing infrastructure as code is very different from classic infrastructure management. Ive met many teams who have struggled to work out how to make this shift. But ideas, patterns, and practices for using these tools effectively have been scattered across conference talks, blog posts, and articles. Ive been waiting for someone to write a book to pull these ideas together into a single place. I havent seen any sign of this, so finally took matters into my own hands. Youre now reading the results of this effort!
in 1992. This led to Unix system administration and then to building and running hosted software systems (before we called it SaaS, aka Software as a Service) for various companies, from startups to enterprises. Ive been on a journey to infrastructure as code the entire time, before Id ever heard the term.
Things came to a head with virtualization. The story of my stumbling adoption of virtualization and the cloud may be familiar, and it illustrates the role that infrastructure as code has to play in modern IT operations.
I was thrilled when my team got the budget to buy a pair of beefy HP rack servers and licenses for VMware ESX Server back in 2007.
We had in our offices server racks around 20 1U and 2U servers named after fruits (Linux servers) and berries (Windows database servers) running test environments for our development teams. Stretching these servers to test various releases, branches, and high-priority, proof-of-concept applications was a way of life. Network services like DNS, file servers, and email were crammed onto servers running multiple application instances, web servers, and database servers.
So we were sure these new virtual servers would change our lives. We could cleanly split each of these services onto its own virtual machine (VM), and the ESX hypervisor software would help us to squeeze the most out of the multicore server machines and gobs of RAM wed allocated. We could easily duplicate servers to create new environments and archive those servers that werent needed onto disk, confident they could be restored in the future if needed.
Those servers did change our lives. But although many of our old problems went away, we discovered new ones, and we had to learn completely different ways of thinking about our infrastructure.
Virtualization made creating and managing servers much easier. The flip side of this was that we ended up creating far more servers than we could have imagined. The product and marketing people were delighted that we could give them a new environment to demo things in well under a day, rather than need them to find money in the budget and then wait a few weeks for us to order and set up hardware servers.
A year later, we were running well over 100 VMs and counting. We were well underway with virtualizing our production servers and experimenting with Amazons new cloud hosting service. The benefits virtualization had brought to the business people meant we had money for more ESX servers and for shiny SAN devices to feed the surprising appetite our infrastructure had for storage.
But we found ourselves a bit like Mickey Mouse in The Sorcerers Apprentice from Fantasia. We spawned virtual servers, then more, then even more. They overwhelmed us. When something broke, we tracked down the VM and fixed whatever was wrong with it, but we couldnt keep track of what changes wed made where.
Well, a perfect hit!
See how he is split!
Now theres hope for me,
and I can breathe free!
Woe is me! Both pieces
come to life anew,
now, to do my bidding
I have servants two!
Help me, O great powers!
Please, Im begging you!
Excerpted from Brigitte Dubiels translation of Der Zauberlehrling (The Sorcerers Apprentice) by Johann Wolfgang von Goethe
As new updates to operating systems, web servers, app servers, database servers, JVMs, and various other software packages came out, we would struggle to install them across all of our systems. We would apply them successfully to some servers, but on others the upgrades broke things, and we didnt have time to stomp out every incompatibility. Over time, we ended up with many combinations of versions of things strewn across hundreds of servers.
We had been using configuration automation software even before we virtualized, which should have helped with these issues. I had used CFEngine in previous companies, and when I started this team, I tried a new tool called Puppet. Later, when spiking out ideas for an AWS infrastructure, my colleague Andrew introduced Chef. All of these tools were useful, but particularly in the early days, they didnt get us out of the quagmire of wildly different servers.
The problem was that, although Puppet (and Chef and the others) should have been set up and left running unattended across all of our servers, we couldnt trust it. Our servers were just too different. We would write manifests to configure and manage a particular application server. But when we ran it against another, theoretically similar app server, we found that different versions of Java, application software, and OS components would cause the Puppet run to fail, or worse, break the application server.
Font size:
Interval:
Bookmark:
Similar books «Infrastructure as Code: Managing Servers in the Cloud»
Look at similar books to Infrastructure as Code: Managing Servers in the Cloud. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.
Discussion, reviews of the book Infrastructure as Code: Managing Servers in the Cloud and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.