Your Debian-based data center in a box
The DebOps project provides a set of general-purpose Ansible roles that can be used to manage Debian or Ubuntu hosts. In addition, a default set of Ansible playbooks can be used to apply the provided roles in a controlled way, using Ansible inventory groups.
The roles are written with a high customization in mind, which can be done using Ansible inventory. This way the role and playbook code can be shared between multiple environments, with different configuration in to each one.
Services can be managed on a single host, or spread between multiple hosts. DebOps provides support for different SQL and NoSQL databases, web servers, programming languages and specialized applications useful in a data center environment or in a cluster. The project can also be used to deploy virtualization environments using KVM/libvirt, Docker or LXC technologies to manage virtual machines and/or containers.
You can find out more about DebOps features on the project's documentation page.
Create an Ansible Controller host based on Debian Stretch and configure it with DebOps:
vagrant up && vagrant ssh
cd src/controller ; debopsThe configuration relies heavily on your Vagrant environment. Having a real domain is benefical. The box can be used to manage other Debian hosts as well.
See the Vagrantfile for more details and configuration variables.
Start a Docker container which acts as an Ansible Controller host with DebOps support, based on Debian Stretch:
docker run -it debops/debopsYou can use configuration in the src/controller subdirectory to try out DebOps against the container, or create your own DebOps project directory using debops-init command.
See the Dockerfile for more details about using DebOps in a Docker container.
DebOps requires a Python 2.7 environment and Ansiible 2.3+ to work correctly. Read the INSTALL.rst file for specific installation instructions.
Ansible uses SSH to connect to and manage the hosts. DebOps enforces the SSH security by disabling password authentication, therefore using SSH keys to connect to the hosts is strongly recommended. This can be changed using the inventory variables.
During initial deployments you might find that the firewall created by DebOps blocked you from accessing the hosts. Because of that it's advisable to have an out-of-band console access to the host which can be used to login and troubleshoot the connection.
Create a new environment within a DebOps "project directory", add some hosts in the Ansible inventory and run the default DebOps playbook against them to configure them:
# Create a new environment
debops-init ~/src/projects/my-environment
cd ~/src/projects/my-environment
# Modify the 'ansible/inventory/hosts' file to suit your needs, for example
# uncomment the local host to configure it with DebOps
# Run the full playbook against all hosts in the inventory
debops
# Run the common playbook against specific host in the inventory
debops common -l <hostname>You should read the Getting Started with DebOps guide for a more in-depth explanation of how the project can be used to manage multiple hosts via Ansible.
Create a fork of this repository and clone it to your workstation. Create a development DebOps environment and symlink the forked repository in it. Now you can create new playbooks/roles in the forked repository and see their results in the development environment.
git clone git@github.com:<username>/debops ~/src/github.com/<username>/debops
cd ~/src/github.com/<username>/debops
git remote add upstream https://github.com/debops/debops.git
debops-init ~/src/projects/debops-devel
cd ~/src/projects/debops-devel
ln -s ~/src/github.com/<username>/debops debopsYou can pull latest changes to the project from the upstream repository:
cd ~/src/github.com/<username>/debops
git checkout master
git fetch upstream
git rebase upstream/masterRead the DEVELOPMENT.rst file for more details about the DebOps development process.
DebOps development is done via a distributed model. New features and changes are prepared in a fork of the official repository and are published to the original repository via GitHub pull requests. PRs are reviewed by the DebOps developer team and if accepted, are merged in the main repository.
GPG-signed git commits are preferred to ensure authenticity.
Read the CONTRIBUTING.rst file for more details about how to contribute to DebOps.
The DebOps project is licensed under the GNU General Public License 3.0. You can find full text of the license in the LICENSE file.