Create broker-apb dir, add install yaml

[djzager]

Originally, I had intended to bring in the entire broker-apb into this project so that I would be able to finish the versioning strategy blog post. All that really needs to exist for the blog post is the install.yaml. This PR adds that file where the broker-apb will live in the future without having to do all the work up front of moving the project, updating travis, and updating docker build automation.

[djzager]

Assuming that this is an acceptable strategy. I'll be adding similar files to the release-1.0 and release-1.1 branches.

[dymurray]

Looks sane to me

[eriknelson]

LGTM to me too; so this is a set of k8s objects and not an openshift template? Also, do we want a branded "ansible-broker" version? I guess I'm wondering...what do we call ourselves upstream, because we're in a weird spot right now where our home is openshift/ansible-service-broker, and now we're starting to use yet-another-name. @jmrodri thoughts?

[djzager]

LGTM to me too; so this is a set of k8s objects and not an openshift template?

Set of k8s objects that can just be used...kubectl create -f install.yaml to get a broker.

Also, do we want a branded "ansible-broker" version?

I can update the yaml to make everything ansible-service-broker (except the APB image) if that helps.

I guess I'm wondering...what do we call ourselves upstream, because we're in a weird spot right now where our home is openshift/ansible-service-broker, and now we're starting to use yet-another-name. @jmrodri thoughts?

I think this is a fair point, in Jason's PR to add the broker to origin you will see automation-service-broker.

[jmrodri]

so how do I use this to deploy my test broker image: docker.io/jmrodri/origin-ansible-service-broker:demo? trying to look ahead when template goes away.

[djzager]

@jmrodri My feeling is the best way, and the way that would make the template go away, would be for the whole broker-apb to be brought into this project. That would allow us to update the Makefile to 1) build the broker 2) build the broker-apb 3) provision with the broker-apb. I'm not certain that we would rely on this install.yaml for that, but that's how I believe we would deploy the broker in development.

Do we still intend to run the broker locally?

[jmrodri]

Okay with me. This makes sense.