Ansible Service Broker
![Issue Count](https://codeclimate.com/github/fusor/ansible-service-broker/badges/issue_count.svg)
An Open Service Broker implementation.
Prerequisites
glide is used for dependency management. Binaries are available on the
releases page.
Packages
Our dependencies currently require development headers for btrfs and dev-mapper.
CentOS/RHEL/Fedora (sub dnf for Fedora):
sudo yum install device-mapper-devel btrfs-progs-devel
Setup
mkdir -p $GOPATH/src/github.com/fusor
git clone https://github.com/fusor/ansible-service-broker.git $GOPATH/src/github.com/fusor/ansible-service-broker`
cd $GOPATH/src/github.com/fusor/ansible-service-broker && glide install
Config
A broker is configured via a $ENV.config.yaml
file. Example files can be
found under etc/
. It's recommended to simply copy over etc/ex.dev.config.yaml
to etc/dev.config.yaml
, and edit as desired. scripts/runbroker.sh
should
handle providing the location to this file. Of course, this can be customized
or the configuration file can be specified by cli args as well.
Targets
make run
: Runs the broker with the default profile, configured via /etc/dev.config.yaml
make run-mock-registry
: Mock registry. Entirely separate binary.
make test
: Runs the test suite.
Note
Scripts found in /test
can act as manual Service Catalog requests until a larger
user scenario can be scripted.
AnsibleApp
The Ansible Service Broker is available as an ansibleapp itself; it
is automatically built from this repo's tag: ansible-service-broker:latest
.
Packaging related files are found in ansible/
, ansibleapp/
, ansibleapp.yml
,
and the Dockerfile
.
AnsibleApp's and their packaging process are documented in the
ansibleapp repo