Book Image

Practical OneOps

By : Nilesh Nimkar
Book Image

Practical OneOps

By: Nilesh Nimkar

Overview of this book

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.
Table of Contents (18 chapters)
Practical OneOps
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Best practices


Here are a few best practices to follow when using OneOps. Lots of these are suggested by the OneOps team in their official documentation. I have tried to provide justification for some of them where possible:

  • Follow a set naming convention for assembly names. OneOps sets some rules as to how you can name an assembly, such as no spaces. Also remember that your assembly name will become part of your FQDN after deployment, so choose a good assembly name.

  • Always add owner's e-mail ID to your assembly and enable watching. Be responsible for your own deployments. That's what DevOps is all about!

  • Be cognizant of the default values and tune them accordingly. Sometimes, the defaults will trip you up.

  • Choose good and descriptive platform names. A good suggestion is name them according to the platform you are adding, that is, if you are adding Postgres, then call it Postgres or Postgres-middleware.

  • Do not make changes directly to an instance, even if you can. You will cause configuration...