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

A look at packs


So far, we have explored the structure of a component that is a very standalone object. Once you have modeled your component, you will have to create a corresponding pack file under the packs directory, which resides under the same level as the components directory. The configuration and instructions found in the pack file define several things for a component, including not limited to the following:

  • What services and other components it depends on

  • Default values for attributes

  • Monitor and threshold definitions

  • Custom payload details

  • Relationships such as depends_on, managed_via, and secured_via

A pack also defines the order of execution of components and is used to string components together to make them more effective and reusable.

Once a pack is defined it can be synced with the CMS using the included knife command or the OneOps CLI.