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

Adding SSL to your HTTPD


So far, the communication between our client and Apache has not been encrypted. SSL is the standard used for end to end encryption on the Web. There are two ways you can add SSL to your assembly here. One is, you can add SSL to your Apache web server so that the traffic between your client and the web server is encrypted. Apache then decrypts the traffic. In our case, Apache is serving the static pages, whereas the dynamic content is passed on to Tomcat. In this scenario, the traffic between Apache and Tomcat remains unencrypted. This reduces the load on Tomcat. However, this also assumes that the network connection between Tomcat and the web server is secure.

Note

Please note how to secure the connection is left to you and not mentioned in this book.

In the second scenario, the connections to Tomcat are passed on as is and are decrypted at the Tomcat end. This complicates things a bit because now we have to deal with two SSL certificates: one at the Apache and another...