31,19 €
Mehr erfahren.
- Herausgeber: Packt Publishing
- Kategorie: Wissenschaft und neue Technologien
- Sprache: Englisch
Walmart’s OneOps is an open source DevOps platform that is used for cloud and application lifecycle management. It can manage critical and complex application workload on any multi cloud-based infrastructure and revolutionizes the way administrators, developers, and engineers develop and launch new products.
This practical book focuses on real-life cases and hands-on scenarios to develop, launch, and test your applications faster, so you can implement the DevOps process using OneOps.
You will be exposed to the fundamental aspects of OneOps starting with installing, deploying, and configuring OneOps in a test environment, which will also come in handy later for development and debugging. You will also learn about design and architecture, and work through steps to perform enterprise level deployment. You will understand the initial setup of OneOps such as creating organization, teams, and access management. Finally, you will be taught how to configure, repair, scale, and extend applications across various cloud platforms.
Das E-Book können Sie in Legimi-Apps oder einer beliebigen App lesen, die das folgende Format unterstützen:
Seitenzahl: 240
Veröffentlichungsjahr: 2017
Ähnliche
Table of Contents
Practical OneOps
Practical OneOps
Copyright © 2017 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.
First published: April 2017
Production reference: 1070417
Published by Packt Publishing Ltd.
Livery Place
35 Livery Street
Birmingham
B3 2PB, UK.
ISBN 978-1-78646-199-5
www.packtpub.com
Credits
Author
Nilesh Nimkar
Copy Editors
Dipti Mankame
Safis Editing
Reviewer
Andy Cohan
Project Coordinator
Judie Jose
Commissioning Editor
Pratik Shah
Proofreader
Safis Editing
Acquisition Editor
Vijin Boricha
Indexer
Pratik Shirodkar
Content Development Editor
Abhishek Jadhav
Graphics
Kirk D'Penha
Technical Editor
Aditya Khadye
Production Coordinator
Shantanu Zagade
About the Author
Nilesh Nimkar has 18 years of experience in the IT industry, where he worked as a Release Manager for 13 years with the world's top banks, hedge funds, and data providers, such as Interactive Data, Deutsche Bank, Bridgewater Associates, Barclays, Bank of America, Merrill Lynch, UBS, and Oracle.
During his time at various banks and hedge funds, he was involved in various large-scale automation projects.
He likes to play with cloud and orchestration technologies, such as OpenStack, Docker, and Vagrant. He likes to read through code and reverse-engineer products. He also has a Master's degree in Information Systems from the University of Phoenix and a Bachelor of Science (physics) from the University of Mumbai. He is a certified Financial Information Associate, Mongo DBA, Mongo Developer, Oracle DBA, and Hadoop Admin.
I would like to thank my wife and daughter for putting up with my late nights working on the book. I would like to thank my mom who instilled in me a love for reading. A big thanks to Vijin and Abhishek from Packt, without whom this book would not have seen the light of the day.
Finally, thanks to the team at Walmartlabs for releasing an excellent product as open source, being patient with me, and answering my endless stream of questions.
About the Reviewer
Andy Cohan is a seasoned systems architect, developer, and leader with 30 years of experience in designing and building business information systems. He currently leads the Eastern region for Avalon Consulting, LLC, a big data and digital transformation firm based near Dallas, TX.
www.PacktPub.com
For support files and downloads related to your book, please visit www.PacktPub.com.
Did you know that Packt offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.PacktPub.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at [email protected] for more details.
At www.PacktPub.com, you can also read a collection of free technical articles, sign up for a range of free newsletters and receive exclusive discounts and offers on Packt books and eBooks.
https://www.packtpub.com/mapt
Get the most in-demand software skills with Mapt. Mapt gives you full access to all Packt books and video courses, as well as industry-leading tools to help you plan your personal development and advance your career.
Why subscribe?
Customer Feedback
Thanks for purchasing this Packt book. At Packt, quality is at the heart of our editorial process. To help us improve, please leave us an honest review on this book's Amazon page at https://www.amazon.com/dp/1786461994.
If you'd like to join our team of regular reviewers, you can e-mail us at [email protected]. We award our regular reviewers with free eBooks and videos in exchange for their valuable feedback. Help us be relentless in improving our products!
Preface
OneOps is complex yet easy to use PaaS Application Lifecycle Management software built by Walmart Labs, which is owned by Walmart. Walmart uses OneOps to manage its e-commerce infrastructure sites, such as walmart.com and Sam's Club. However, before switching to OneOps any updates to Walmart's infrastructure were huge tasks and required complex planning and execution. Updates were done every two months, required hundreds of manual steps and considerable resources, and left a lot of room for errors. This also made testing quite difficult. This is common scenario in a lot of organizations where legacy products can run and become bloated and monolithic to the point of being unmanageable. Organizations become complacent and are either afraid of or are resistant to change, opting instead to maintain the status quo, most of the time at a terrible cost to productivity. This all started to change with the advent of DevOps. While DevOps is about fostering a cooperative culture among teams, it begins by giving increased control to developers over their own applications. DevOps is also about enabling rapid changes across all environments at the speed of development. Walmart used OneOps to implement the DevOps paradigm, allowing them to move from their monolithic bi-monthly deployments to rapidly evolving 1000 deployments per day across their global e-commerce infrastructure. OneOps abstracts the underlying cloud infrastructure from the developers irrespective of the tools and technologies they use. OneOps also allows developers to define their application along with the infrastructure requirements in a easy to use generic GUI, which it then translates to whichever cloud the application gets deployed to. This avoids being locked in to a cloud vendor, allowing companies to benefit from having redundancies for their applications and to also benefit from competitive cloud vendor technologies and pricing. OneOps also provides services such as monitoring, auto-scaling, and auto-repair for deployed applications. And best of all, it's available for free under open source.
In this book, we will explore the practical aspects of OneOps from the point of view of a DevOps engineer. Irrespective of whether you have been asked to evaluate OneOps as a potential technology to implement as an abstraction on your cloud infrastructure or if you are doing a enterprise deployment of OneOps, you will find something useful in this book. We will start with the basics such as various ways of installing a test installation of OneOps. We will then look at the architecture of OneOps and the various components that comprise the backend. We will then see how to create and deploy and assembly. We will also look at a few practical deployment scenarios. By the end of the book you should not only understand how to install and configure OneOps, but also be comfortable with the architecture and various components of OneOps. You will also learn advanced tasks, such as how to add new components to OneOps, how to add unsupported and custom clouds, and how to interact with OneOps using the REST API.
What this book covers
Chapter 1, Getting Started with OneOps, shows various ways to install OneOps as a standalone system. It shows how to use the Amazon Machine Image as well as the Vagrant Image to install your own OneOps copy as a sandbox for development, testing or even production. It will also introduce you to some key OneOps concepts.
Chapter 2, Understanding the OneOps Architecture, gives a detailed view of the OneOps backend architecture. It gives an overview of all the backend services, their purposes, and how they all work together. It will also introduce you to a couple of handy utilities that will enable you to look at the backend CMS data.
Chapter 3, OneOps Application Life Cycle, takes you on your first steps towards Application Lifecycle Management using OneOps. You will take your first steps in OneOps by creating and configuring a cloud and adding services under it. You will then design an assembly by using readymade packs provided by OneOps. You will also learn how to create environments and how to transition your assembly across the environments. Finally, you will learn how to monitor your assembly.
Chapter 4, OneOps Enterprise Deployment, deals with enterprise deployment of OneOps. It will show you the things you will have to consider before planning an enterprise deployment. It will also show you how to use OneOps to install an enterprise version of OneOps, which parameters to configure, how to configure backups, among other things. You will also learn more about the configuration of individual services.
Chapter 5, Practical Deployment Scenario, will show you a very common and practical deployment scenario and walk you through it. You will be using OneOps to deploy a load balanced website consisting of Apache HTTPD, Tomcat, and Mysql. We will build on top of this architecture to add SSL to the website. After adding SSL, we will then be adding autorepair and autoscaling and enabling the applications to be deployed to multiple clouds. We will also look at various common errors and get a feel for how to resolve them.
Chapter 6, Managing Your OneOps, will show you how to upgrade your OneOps installation with minimal downtime. You will learn how to upgrade OneOps both for Standalone and Enterprise installation. You will also learn how to configure database backups. This chapter will also show you how to handle and configure security groups.
Chapter 7, Working with Functional Components, tells you in detail about the functional components of OneOps, namely the circuit and inductor. You will find out how to build, install, and configure an inductor. You will also get an introduction to circuits and learn how to configure them.
Chapter 8, Building Components for OneOps, starts with a brief recap of OneOps architecture. It will show you how OneOps can be extended by creating your own components by introducing components to you. You will also get familiar with the concepts of platforms and assemblies in this chapter.
Chapter 9, Adding and Managing OneOps Components, will have you create a new OneOps component step by step and add it to your OneOps instance. You will also be installing and testing the new component and updating the CMS to reflect it. You will also be creating a new platform pack. This chapter will also teach you how to maintain your components, maintain your platform packs, and add monitoring to your components.
Chapter 10, Adding Your Own Cloud to OneOps, teaches you to add a previously unsupported cloud to OneOps. Although OneOps comes with quite a few clouds supported out of the box, this chapter shows you how to add an unsupported cloud step by step. It will tell you all the things you need to consider when adding a custom cloud and then show you how to add a compute instance by adding support for DigitalOcean droplets. It will also show you how to add monitoring for your droplets.
Chapter 11, Integrating with OneOps Using API, shows how you can leverage the functionality of OneOps from other applications using the REST API. It shows you how to create and transition an assembly using easy to understand scripts written in Ruby that calls the REST API provided by OneOps.
What you need for this book
This book assumes you have basic knowledge of Linux Operating System. It also assumes you have basic knowledge of DevOps practices. This book will go from the basic setup to the advanced setup of OneOps and its related functions. All the configurations and tasks mentioned in this book will work on a basic standalone setup and have been tested as such. So, to run anything from this book you will need at least a standalone setup on your desktop, laptop, or in the cloud. The most common way to set up is, as mentioned in Chapter 1, Getting Started with OneOps, to install VirtualBox and then Vagrant and then follow the instructions provided by OneOps. The following hardware resources are required to run OneOps:
The following software is needed to run OneOps:
Internet connectivity is required to connect to, install, and manager other clouds.
Who this book is for
This book is for those who want to accelerate their deployments. This book is for those who want to get away from monolithic builds and deployments. This book is for those who want to give more control to developers while making developers responsible for their own applications in all environments. This book is for those who want more visibility in their application process across the spectrum. This book is for those who love automation. This book is for those who want to embrace DevOps, or for those who just want to take it for a drive. No prior knowledge of anything is assumed.
Conventions
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "The next lines of code read the link and assign it to the to the BeautifulSoup function."
A block of code is set as follows:
monitors => { 'Log' => {:description => 'Log', :source => '', :chart => {'min' => 0, 'unit' => ''},Any command-line input or output is written as follows:
$ aws ec2 create-key-pair --key-name OneOpsAuth --query 'KeyMaterial' --output 'text' > OneOpsAuth.pemNew terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Select a region you want to add. Currently supported regions are US-East-1, US-West-1, and US-West-2"
Note
Warnings or important notes appear in a box like this.
Tip
Tips and tricks appear like this.
Reader feedback
Feedback from our readers is always welcome. Let us know what you think about this book-what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of. To send us general feedback, simply e-mail [email protected], and mention the book's title in the subject of your message. If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.
Customer support
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Downloading the example code
You can download the example code files for this book from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
You can download the code files by following these steps:
Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:
The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Practical-OneOps. We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!
Downloading the color images of this book
We also provide you with a PDF file that has color images of the screenshots/diagrams used in this book. The color images will help you better understand the changes in the output. You can download this file from https://www.packtpub.com/sites/default/files/downloads/PracticalOneOps_ColorImages.pdf.
Errata
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books-maybe a mistake in the text or the code-we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at [email protected] with a link to the suspected pirated material.
We appreciate your help in protecting our authors and our ability to bring you valuable content.
Questions
If you have a problem with any aspect of this book, you can contact us at [email protected], and we will do our best to address the problem.
Chapter 1. Getting Started with OneOps
Since you are reading this book, you are probably keen to get up-and-running with OneOps. Deploying OneOps in an enterprise environment is a complex task. It is always prudent to start with a test installation. A test installation allows you to test all the features in isolation without affecting your current network and applications. You can also use a test installation as your developer sandbox.
A fully fledged OneOps installation consists of lot of moving parts and complex configurations. Fortunately, almost all of these are automated and for the test install they come in nice little bundles. This chapter will show you two ways to configure a test installation that can also be used as developer sandbox. We will then see how to configure our first installation of OneOps. The two ways you can install OneOps are:
Amazon AMI
There are multiple reasons why you may want to run OneOps on AWS rather than your own infrastructure. Running on AWS offloads all your infrastructure management needs to Amazon so you can focus on delivery. This is crucial for you if you want to keep your DevOps team small. If the rest of your infrastructure, services, and application are also on AWS, it makes strategic sense to have your management software on AWS too. Finally, AWS provides easy options for redundancy and scalability. The downside of this option is that you cannot add your own custom cloud that runs on your own premises without considerable configuration, for example, a VPN tunnel.
OneOps provides a basic AMI in the public marketplace on Amazon AWS. This AMI comes with some basic configuration already in place to get you up-and-running. Instantiating OneOps on AWS is the quickest way you can get up and running with OneOps. There are two ways you can do this. They are as follows:
Knowing how to spin up the OneOps AMI from the command line comes in handy as you can make it a part of your automation or DevOps delivery chain later.
Note
You can find more details on installing the AWS command line tool here:http://docs.aws.amazon.com/cli/latest/userguide/installing.html.
Once you have the command line tool installed, the first step is to generate a keypair, which you will use to connect to the new instance you will spin up.
Note the GroupId of the group that you just created as we will need it when we open up ports. We will now open up access to ports 22 and 3000, port 22 so you can SSH to it remotely and 3000 because the OneOps frontend is a Ruby on Rails application and is accessible on port 3000.
$ aws ec2 authorize-security-group-ingress --group-id sg-903004f8 --protocol tcp --port 22 --cidr 0.0.0.0/0 $ aws ec2 authorize-security-group-ingress --group-id sg-903004f8 --protocol tcp --port 3000 --cidr 0.0.0.0/0Note that we opened up access to the whole world on port 22 and 3000 by giving access to 0.0.0.0/0. If you always login from a fixed set of IP addresses, such as a corporate network, you might want to secure your installation by giving access to that set of IP addresses only.
Finally verify that your security group was created successfully and the permissions were applied correctly.$ aws ec2 describe-security-groups --group-id sg-05e2847d { "SecurityGroups": [ { "IpPermissionsEgress": [ { "IpProtocol": "-1", "IpRanges": [ { "CidrIp": "0.0.0.0/0" } ], "UserIdGroupPairs": [], "PrefixListIds": [] } ], "Description": "OneOps Security Group", "IpPermissions": [ { "PrefixListIds": [], "FromPort": 22, "IpRanges": [ { "CidrIp": "0.0.0.0/0" } ], "ToPort": 22, "IpProtocol": "tcp", "UserIdGroupPairs": [] }, { "PrefixListIds": [], "FromPort": 3000, "IpRanges": [ { "CidrIp": "0.0.0.0/0" } ], "ToPort": 3000, "IpProtocol": "tcp", "UserIdGroupPairs": [] } ], "GroupName": "OneOps-sg", "VpcId": "vpc-45e3af21", "OwnerId": "377640004228", "GroupId": "sg-05e2847d" } ] }Finally, we are almost ready to launch the AMI. However, for that we need the instance ID for the correct AMI. OneOps AMI names are structured as OneOps-basic-preconf-v* where * is 1.1, 1.2.
To find the latest version of image available run the command following:$ aws ec2 describe-images --filter "Name=name,Values=OneOps*" --query 'Images[*].{Name:Name,ID:ImageId}' [ { "Name": "OneOps-basic-preconf-v1.3", "ID": "ami-076c416d" }, { "Name": "OneOps-basic-preconf-v1.2", "ID": "ami-fc1b3996" } ]Once you have the AMI ID, you are now ready to launch the OneOps instance.
Run the following command to launch the AMI instance.$ aws ec2 run-instances --image-id ami-076c416d --count 1 --instance-type m4.large --key-name OneOpsAuth --security-group-ids sg-05e2847d { "OwnerId": "377640004228", "ReservationId": "r-e8a1e943", "Instances": [ { "Hypervisor": "xen", "PublicDnsName": "", "VpcId": "vpc-45e3af21", "RootDeviceName": "/dev/sda1", "StateReason": { "Message": "pending", "Code": "pending" }, "ProductCodes": [], "ClientToken": "", "Architecture": "x86_64", "SubnetId": "subnet-2311d009", "State": { "Name": "pending", "Code": 0 }, "PrivateIpAddress": "172.31.56.32", "InstanceId": "i-4af1d7c9", "SecurityGroups": [ { "GroupId": "sg-05e2847d", "GroupName": "OneOps-sg" } ], "EbsOptimized": false, "VirtualizationType": "hvm", "KeyName": "OneOpsAuth", "Placement": { "AvailabilityZone": "us-east-1b", "Tenancy": "default", "GroupName": "" }, "StateTransitionReason": "", "ImageId": "ami-076c416d", "Monitoring": { "State": "disabled" }, "SourceDestCheck": true, "InstanceType": "m4.large", "BlockDeviceMappings": [], "RootDeviceType": "ebs", "PrivateDnsName": "ip-172-31-56-32.ec2.internal", "NetworkInterfaces": [ { "PrivateIpAddress": "172.31.56.32", "PrivateIpAddresses": [ { "PrivateIpAddress": "172.31.56.32", "Primary": true, "PrivateDnsName": "ip-172-31-56- 32.ec2.internal" } ], "MacAddress": "12:a5:58:7e:f5:f1", "VpcId": "vpc-45e3af21", "Groups": [ { "GroupId": "sg-05e2847d", "GroupName": "OneOps-sg" } ], "OwnerId": "377649884228", "SourceDestCheck": true, "Attachment": { "DeleteOnTermination": true, "AttachTime": "2016-03-24T19:53:13.000Z", "Status": "attaching", "DeviceIndex": 0, "AttachmentId": "eni-attach-9a96416b" }, "PrivateDnsName": "ip-172-31-56-32.ec2.internal", "Status": "in-use", "Description": "", "SubnetId": "subnet-2311d009", "NetworkInterfaceId": "eni-2aeed90f" } ], "LaunchTime": "2016-03-24T19:53:13.000Z", "AmiLaunchIndex": 0 } ], "Groups": []}image-id is the ID you obtained from the previous query for the latest image version (in this case v1.3). The key name is the new key you created and the security group is the group you created. Replace the values in the preceding command as needed. Make sure the InstanceType is m4.large as OneOps needs at least 8 GB of memory to run. The image will also attach two block devices to the instance for storage. Give the instance a few minutes to start. Lastly tag the instance with a tag called OneOps so you can easily find it. For this you will need the InstanceId. For example, in the previous output, you can see the InstanceId for the instance created above is i-4af1d7c9.
That's it! Now look up the public IP of your instance and connect to it at port 3000. You should see the OneOps login screen.
$ aws ec2 describe-instances --filter "Name=tag:Name,Values=OneOps"{"Reservations": [ { "Groups": [], "OwnerId": "377649884228", "ReservationId": "r-e8a1e943", "Instances": [ { "PublicIpAddress": "54.86.6.251", "State": { "Code": 16, "Name": "running" }, "Architecture": "x86_64", "LaunchTime": "2016-03-24T19:53:13.000Z", "SubnetId": "subnet-2311d009", "ProductCodes": [], "PrivateIpAddress": "172.31.56.32", "Monitoring": { "State": "disabled" }, "PrivateDnsName": "ip-172-31-56-32.ec2.internal", "NetworkInterfaces": [ { "Groups": [ { "GroupId": "sg-05e2847d", "GroupName": "OneOps-sg" } ], "OwnerId": "377649884228", "NetworkInterfaceId": "eni-2aeed90f", "SourceDestCheck": true, "SubnetId": "subnet-2311d009", "PrivateIpAddress": "172.31.56.32", "Status": "in-use", "MacAddress": "12:a5:58:7e:f5:f1", "VpcId": "vpc-45e3af21", "Description": "", "PrivateDnsName": "ip-172-31-56-32.ec2.internal", "PrivateIpAddresses": [ { "Association": { "PublicIp": "54.86.6.251", "IpOwnerId": "amazon", "PublicDnsName": "ec2-54-86-6-251.compute- 1.amazonaws.com" }, "PrivateDnsName": "ip-172-31-56-32.ec2.internal", "PrivateIpAddress": "172.31.56.32", "Primary": true } ], "Attachment": { "DeviceIndex": 0, "AttachTime": "2016-03-24T19:53:13.000Z", "AttachmentId": "eni-attach-9a96416b", "DeleteOnTermination": true, "Status": "attached" }, "Association": { "PublicIp": "54.86.6.251", "IpOwnerId": "amazon", "PublicDnsName": "ec2-54-86-6-251.compute- 1.amazonaws.com" } } ], "ImageId": "ami-076c416d",
