Book Image

Apache Mesos Cookbook

By : David Blomquist, Tomasz Janiszewski
Book Image

Apache Mesos Cookbook

By: David Blomquist, Tomasz Janiszewski

Overview of this book

Apache Mesos is open source cluster sharing and management software. Deploying and managing scalable applications in large-scale clustered environments can be difficult, but Apache Mesos makes it easier with efficient resource isolation and sharing across application frameworks. The goal of this book is to guide you through the practical implementation of the Mesos core along with a number of Mesos supported frameworks. You will begin by installing Mesos and then learn how to configure clusters and maintain them. You will also see how to deploy a cluster in a production environment with high availability using Zookeeper. Next, you will get to grips with using Mesos, Marathon, and Docker to build and deploy a PaaS. You will see how to schedule jobs with Chronos. We’ll demonstrate how to integrate Mesos with big data frameworks such as Spark, Hadoop, and Storm. Practical solutions backed with clear examples will also show you how to deploy elastic big data jobs. You will find out how to deploy a scalable continuous integration and delivery system on Mesos with Jenkins. Finally, you will configure and deploy a highly scalable distributed search engine with ElasticSearch. Throughout the course of this book, you will get to know tips and tricks along with best practices to follow when working with Mesos.
Table of Contents (15 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Enabling basic access authentication


In this recipe, you will learn how to enable HTTP basic authentication to limit a user who can access the Marathon API.

Getting ready

Before you start, ensure Marathon is up and running. Before applying any authentication, ensure you enabled SSL to protect secrets from eavesdropping.

How to do it...

Update the configuration with credentials:

echo MARATHON_HTTP_CREDENTIALS=username:password >> /etc/default/marathon

Check the API requires authentication:

curl -k https://localhost:8443/ping

The preceding command should return a 401 Unauthorized code, while the following command should work. From now, all interactions with Marathon require passing credentials:

curl -k -u username:password https://localhost:8443/ping

How it works...

When HTTP credentials are passed to Marathon, it checks HTTP request headers for credentials and compares them with those configured. When no credentials are provided or the provided credentials don't match, it returns a 401 error code...