Skip to content
Nandaja Varma edited this page Feb 26, 2016 · 16 revisions

gdeploy

gdeploy is a tool to set-up and deploy GlusterFS using Ansible over multiple hosts. (a.k.a yet another automation tool)

gdeploy uses the cool and awesome capabilities of Ansible to deploy on multiple servers whatever operation it is asked to. Initially, gdeploy used to be gluster deploy, which was basically a set of playbook files that lets you setup backend and create volumes. But the problem with playbooks is that, they are yamls, static, less user friendly(if the user is not familiar with ymls), and more over felt very hard coded to us. So we decided to build gdeploy, which takes in data from the user via a configuration file and fed it to Ansible playbooks and templates we have written (for out very own Ansible modules). So gdeploy's major job is to parse, validate, and formatting the user given data and call appropriate Ansible playbooks. Sounds pretty straight forward, right? Okay, enough with the hizzztory.

Oops! Almost forgot. gdeploy even has a REST API, just because every single tool has one. The REST API can be used instead of configuration files(although we wonder why anyone would). It is kind of beta right now, as it doesn't have an authorization/authentication mechanism and supports just JSONs in the current state of gdeploy.

Go ahead and browse the contents we have to know more about usages and internals.

##Table of Contents

  1. Usage
  2. Cooking the perfect configuration file
  3. Developer workflow
  4. Gluster deploy architecture
Clone this wiki locally