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

Installing and testing the new component


Now that the new platform is showing up in the design phase, we can test it out by deploying it. To test it out you must have a cloud configured. By now you should have at least a test OneOps system configured for all your development and testing needs. Configuring a cloud should also be easy for you. So go ahead and create a test assembly. Add the freshly created OrientDB platform to it. When you are deploying a newly created platform for the first time, you should fully expect it to fail. It is rare that things will go right the first time. This is the reason you should be doing this in a test or development environment.

Note

Another reason to test in a development environment is that you can test with the latest and greatest code, that is, the master branch. That will ensure your code is compatible with the latest changes that OneOps will release. Since OneOps is an Open Source project you should also check in your changes to GitHub and file pull...