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

Pack maintenance


Now that we have created a brand-new component and a pack, we must maintain them. In general, there are various things we can do to maintain our new pack (and existing packs) in OneOps, such as adding extra attributes, disabling the pack, setting policies and so on. As mentioned earlier we can add extra attributes to metadata.rb to get more input from users and make the installation more interactive. A good guideline is to look at the default.rb file in the attributes directory. This file provides the default value for a lot of variables that are not explicitly supplied when we construct our assembly.

As you can see, we can very well offer the installation directory as well as db_user and db_password as input fields to the user, thus allowing them more control over the installation. You have two ways of disabling a pack. One is by setting the option ignore to true or false in the pack. If set to true the pack is not reloaded or updated in OneOps. The second way is using...