New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Broker APB source to project #939
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worked successfully for me on first try using install.yml. Great work!
|
Here is the run after doing EXIT_CODE=$(${CMD} get pod -n ${APB_NAME} "${APB_NAME}" -o go-template="{{ range .status.containerStatuses }}{{.state.terminated.exitCode}}{{ end }}")Here is the output of make deploy |
|
This is how I brought up my cluster using these commands in a #oc cluster up --enable=service-catalog,router,registry,web-console,persistent-volumes
oc cluster up --routing-suffix=172.17.0.1.nip.io --public-hostname=172.17.0.1 --base-dir=/tmp/openshift.local.clusterup --tag=latest --image=docker.io/openshift/origin-\${component}:\${version} --enable=service-catalog,template-service-broker,router,registry,web-console,persistent-volumes,sample-templates,rhel-imagestreams
oc login -u system:admin
oc new-project ansible-service-broker
#cat template-sample-broker.yaml | oc process -n samplebroker -f - | oc create -f - |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't work for me.
|
@jmrodri I ran into this problem initially with my Can you confirm that you have that deploy script? Based on the line number bash is reporting, I think you are using the right one. I am just struggling to recreate. |
|
Nevermind. I was able to recreate. working on a fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VISIACK, tried to scan most of this and it looks sane to me. I have tested locally with a make deploy and make undeploy with an oc cluster up based cluster. I also used this in a vanilla k8s-dind cluster I was using for my namespaced broker demo, so I have reasonable confidence in it working. Nice job @djzager!
| @@ -0,0 +1,31 @@ | |||
| --- | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need this file after this is merged into the broker? is there a way to run travis only when files under apb get changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's useless once this is merged. I just didn't want to lose it because I'm hoping to merge it into ${PROJECT_ROOT}/.travis.yml in some future PR
| scope: Namespaced | ||
| names: | ||
| plural: bundlebindings | ||
| singular: bundleebinding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is double ee here a typo?
(now exists in couple more yamls: https://github.com/openshift/ansible-service-broker/search?q=bundleebinding
and in OperatorHub.io: https://github.com/operator-framework/community-operators/blob/master/community-operators/automationbroker/bundlebindings.crd.yaml
and some other repos: https://github.com/search?q=bundleebinding&type=Code)
bundleebinding <- double ee is probably typo, compare to kind: BundleBinding Reported on openshift/ansible-service-broker#939 (comment)
Currently, the broker-apb and the broker are loosely coupled. They are not specifically tied together, except the broker-apb using
latestby default. In the future, we want a couple of things for our broker and broker-apb:Allowing the broker-apb source to live with the broker project gives us more flexibility going forward as changes are introduced to either 1) the way the broker is deployed (CRDs as a recent example) 2) the broker itself.
Fixes: #912 #931 #969