ansible-maas - Ansible Dynamic Inventory Script for Ubuntu MAAS 2.0 API

  •        15

An Ansible Dynamic Inventory Script for the Ubuntu MAAS 2.0 API. Primarily it will be called by Ansible itself with the --list or --host arguments, but additional arguments were implemented for administrators to take advantage of if desired.



Related Projects

terraform-inventory - Terraform State → Ansible Dynamic Inventory

  •    Go

This is a little Go app which generates a dynamic Ansible inventory from a Terraform state file. It allows one to spawn a bunch of instances with Terraform, then (re-)provision them with Ansible. It's very simple to add support for new providers. See pull requests with the provider label for examples.

terraform-provisioner-ansible - A provisioner for bootstrapping terraform resources with ansible

  •    Go

Terraform is a tool for automating infrastructure. Terraform includes the ability to provision resources at creation time through a plugin api. Currently, some builtin provisioners such as chef and standard scripts are provided; this provisioner introduces the ability to provision an instance at creation time with ansible. This provisioner provides the ability to apply host-groups, plays or roles against a host at provision time. Ansible is run on the host itself and this provisioner configures a dynamic inventory on the fly as resources are created.

ansible-coreos-bootstrap - [NOT MAINTAINED] bootstrap a coreos machine for control via ansible

  •    Python

In order to effectively run ansible, the target machine needs to have a python interpreter. Coreos machines are minimal and do not ship with any version of python. To get around this limitation we can install pypy, a lightweight python interpreter. The coreos-bootstrap role will install pypy for us and we will update our inventory file to use the installed python interpreter. Unlike a typical role, you need to configure Ansible to use an alternative python interpreter for coreos hosts. This can be done by adding a coreos group to your inventory file and setting the group's vars to use the new python interpreter. This way, you can use ansible to manage CoreOS and non-CoreOS hosts. Simply put every host that has CoreOS into the coreos inventory group and it will automatically use the specified python interpreter.

debops - DebOps - Your Debian-based data center in a box

  •    Shell

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. - Ansible dynamic inventory script for parsing Terraform state files

  •    Python

Make sure that you've annotated your resources with "tags" that correspond to the sshUser for the machine.

Inventory Management


Inventory management is an application to help small shops with inventory management. Inventory management also support purchase sales.

ansible-junos-stdlib - Junos modules for Ansible

  •    Python

Juniper Networks supports Ansible for managing devices running the Junos operating system (Junos OS). This role is hosted on the Ansible Galaxy website under the role Juniper.junos. The Juniper.junos role includes a set of Ansible modules that perform specific operational and configuration tasks on devices running Junos OS. These tasks include: installing and upgrading Junos OS, provisioning new Junos devices in the network, loading configuration changes, retrieving information, and resetting, rebooting, or shutting down managed devices. Please refer to the INSTALLATION section for instructions on installing this role. Since Ansible version >= 2.1, Ansible also natively includes core modules for Junos. The Junos modules included in Ansible core have names which begin with the prefix junos_. The Junos modules included in this Juniper.junos role have names which begin with the prefix juniper_junos_. These two sets of Junos modules can coexist on the same Ansible control machine, and an Ansible play may invoke a module from either (or both) sets. Juniper Networks recommends using the modules in this role when writing new playbooks that manage Junos devices.

ansible-for-devops - Ansible examples from Ansible for DevOps.

  •    Python

This repository contains Ansible examples developed to support different sections of Ansible for DevOps, a book on Ansible by Jeff Geerling. Most of the examples are full-fledged VM examples, which use Vagrant, VirtualBox, and Ansible to boot and configure VMs on your local workstation. Not all playbooks follow all of Ansible's best practices, as they illustrate particular Ansible features in an instructive manner.

ansible-tuto - Ansible tutorial

  •    Shell

This tutorial presents Ansible step-by-step. You'll need to have a (virtual or physical) machine to act as an Ansible node. A Vagrant environment is provided for going through this tutorial. Ansible is a configuration management software that lets you control and configure nodes from another machine. What makes it different from other management software is that Ansible uses (potentially existing) SSH infrastructure, while others (Chef, Puppet, ...) need a specific PKI infrastructure to be set up.

ansible-interactive-tutorial - Interactive Ansible tutorials with dead simple setup via Docker

  •    Shell starts 4 docker containers behind the scenes. 1 for running the tutorial itself and 3 as ansible nodes which behave exactly same as (virtual or physical) machines throughout the tutorial. ansible.tutorial is an alpine based tutorial container in which ansible and nutsh (a framework for creating interactive command line tutorials) are available.

eNMS - A vendor-agnostic NMS designed for network automation

  •    Python

eNMS is an open source web application designed to help automate networks graphically. Nodes and links can be created either one by one by specifying all properties manually, or all at once by importing an Excel spreadsheet. Once created, all objects are displayed in a sortable and searchable table, from which they can be edited and deleted. The dashboard provides a graphical overview of all objects with dynamic charts.

ansible-container - Ansible Container is a tool to build Docker images and orchestrate containers using only Ansible playbooks

  •    Python

Ansible Container is a tool for building Docker images and orchestrating containers using Ansible playbooks.Creates a directory ansible with files to get you started. Read the comments, and edit to suit your needs.

molecule - Molecule aids in the development and testing of Ansible roles.

  •    Python

Molecule is designed to aid in the development and testing of Ansible roles. Molecule provides support for testing with multiple instances, operating systems and distributions, virtualization providers, test frameworks and testing scenarios. Molecule is opinionated in order to encourage an approach that results in consistently developed roles that are well-written, easily understood and maintained. Molecule uses Ansible playbooks to exercise the role and its associated tests. Molecule supports any provider [1] that Ansible supports.

ansible-jenkins - Ansible playbook: Jenkins

  •    Groovy

ansible-jenkins is an Ansible role. Use this role to install Jenkins and install/update plugins. The code should reside in the roles directory of ansible ( See ansible documentation for more information on roles ), in a folder jenkins.

kafka-python - Python client for Apache Kafka

  •    Python

Python client for the Apache Kafka distributed stream processing system. kafka-python is designed to function much like the official java client, with a sprinkling of pythonic interfaces (e.g., consumer iterators).kafka-python is best used with newer brokers (0.9+), but is backwards-compatible with older versions (to 0.8.0). Some features will only be enabled on newer brokers. For example, fully coordinated consumer groups -- i.e., dynamic partition assignment to multiple consumers in the same group -- requires use of 0.9+ kafka brokers. Supporting this feature for earlier broker releases would require writing and maintaining custom leadership election and membership / health check code (perhaps using zookeeper or consul). For older brokers, you can achieve something similar by manually assigning different partitions to each consumer instance with config management tools like chef, ansible, etc. This approach will work fine, though it does not support rebalancing on failures. See <> for more details.

Network Asset Manager


Network Asset Manager is a Hardware and Software Inventory Management application. It is simple to use and collects information on all hardware and software components of your PC's and Servers on the network remotely.

Simple Inventory Management System

  •    DotNet

This simple inventory management system was designed by trainees at Sinuvera Technologies to get hands-on training over C#.NET. The system has multitude of features including multiple warehouse, various types of transactions, reports, etc. to make your daily inventory mgmt e...

ansible-elasticsearch - Ansible playbook for Elasticsearch

  •    Ruby

THIS ROLE IS FOR 5.x. FOR 2.x SUPPORT PLEASE USE THE 2.x BRANCH.The latest Elasticsearch versions of 5.x are actively tested. Only Ansible versions > 2.3.2 are supported, as this is currently the only version tested.

ansible-modules-core - Ansible modules - these modules ship with ansible

  •    Python

NOTE: As of Ansible 2.3, modules are now in the main Ansible repository.See the repo merge guide for more information.

ansible-modules-extras - Ansible extra modules - these modules ship with ansible

  •    Python

NOTE: As of Ansible 2.3, modules are now in the main Ansible repository.See the repo merge guide for more information.