From cmoullia at redhat.com Mon Sep 3 12:56:57 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 3 Sep 2018 14:56:57 +0200 Subject: [Ansible-service-broker] Tool to create a class/plan and package a project as a service Message-ID: Hi Does a tool exists to convert a project (= Spring Boot Java Application) into a class to be published in a catalog using Ansible format (APB) or CRD / operator ? IDea : - Create a class : spring-boot-app - Define a plan for the class exposing some parameters : endpoints, ... - Package the project as APB or install it using CRD/Operator with the catalog Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From ernelson at redhat.com Tue Sep 4 12:53:53 2018 From: ernelson at redhat.com (Erik Nelson) Date: Tue, 4 Sep 2018 08:53:53 -0400 Subject: [Ansible-service-broker] Tool to create a class/plan and package a project as a service In-Reply-To: References: Message-ID: Hi Charles, The short answer is no; I'm not aware of anything that will take an arbitrary type of project and generate an APB or CRD/operator. The closest we probably have would have been the `apb init` command from the apb v1 tool, which would really only generate a basic skeleton project for you to fill in the details. bundle-lib (https://github.com/automationbroker/bundle-lib) contains code that will parse APBs and convert them into OSB ServiceClasses for the catalog, but you need to already have an APB spec that has been base64 encoded and embedded as part of an image's metadata. - Erik On Mon, Sep 3, 2018 at 8:58 AM Charles Moulliard wrote: > Hi > > Does a tool exists to convert a project (= Spring Boot Java Application) > into a class to be published in a catalog using Ansible format (APB) or CRD > / operator ? > > IDea : > > - Create a class : spring-boot-app > - Define a plan for the class exposing some parameters : endpoints, ... > - Package the project as APB or install it using CRD/Operator with the > catalog > > Regards > > Charles > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Sep 10 16:37:15 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 10 Sep 2018 18:37:15 +0200 Subject: [Ansible-service-broker] minishift + origin 3.10 can't start with OAB' s option enabled Message-ID: Hi, Do we have an issue with OAB as minishift can't start anymore using origin 3.10 + OAB [1] ? ... E0910 12:01:24.765147 2101 interface.go:34] Failed to install "automation-service-broker": timed out waiting for the condition I0910 12:01:24.765845 2101 interface.go:41] Finished installing "centos-imagestreams" "openshift-image-registry" "sample-templates" "openshift-web-console-operator" "openshift-router" "persistent-volumes" "automation-service-broker" "openshift-service-catalog" Error: timed out waiting for the condition [1] https://gist.github.com/cmoulliard/9c99457defc55f60d5326640a3d4b63a#file-gistfile1-txt-L43 Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From ernelson at redhat.com Mon Sep 10 16:57:16 2018 From: ernelson at redhat.com (Erik Nelson) Date: Mon, 10 Sep 2018 12:57:16 -0400 Subject: [Ansible-service-broker] minishift + origin 3.10 can't start with OAB' s option enabled In-Reply-To: References: Message-ID: Hi Charles, I'm not aware of any issues filed; I would probably lodge this against the openshift/ansible-service-broker repo. It looks like the underlying issue is the 'oc cluster up' command. We'll have to reproduce it with a 3.10 oc and see what the underlying cause is. On Mon, Sep 10, 2018 at 12:38 PM Charles Moulliard wrote: > Hi, > > Do we have an issue with OAB as minishift can't start anymore using origin > 3.10 + OAB [1] ? > > ... > E0910 12:01:24.765147 2101 interface.go:34] Failed to install > "automation-service-broker": timed out waiting for the condition > I0910 12:01:24.765845 2101 interface.go:41] Finished installing > "centos-imagestreams" "openshift-image-registry" "sample-templates" > "openshift-web-console-operator" "openshift-router" "persistent-volumes" > "automation-service-broker" "openshift-service-catalog" > Error: timed out waiting for the condition > > [1] > https://gist.github.com/cmoulliard/9c99457defc55f60d5326640a3d4b63a#file-gistfile1-txt-L43 > > Regards > > Charles > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Sep 10 17:03:12 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 10 Sep 2018 19:03:12 +0200 Subject: [Ansible-service-broker] minishift + origin 3.10 can't start with OAB' s option enabled In-Reply-To: References: Message-ID: Many thanks. Ticket created : https://github.com/openshift/ansible-service-broker/issues/1076 On Mon, Sep 10, 2018 at 6:57 PM, Erik Nelson wrote: > Hi Charles, > > I'm not aware of any issues filed; I would probably lodge this against the > openshift/ansible-service-broker repo. It looks like the underlying issue > is the 'oc cluster up' command. We'll have to reproduce it with a 3.10 oc > and see what the underlying cause is. > > On Mon, Sep 10, 2018 at 12:38 PM Charles Moulliard > wrote: > >> Hi, >> >> Do we have an issue with OAB as minishift can't start anymore using >> origin 3.10 + OAB [1] ? >> >> ... >> E0910 12:01:24.765147 2101 interface.go:34] Failed to install >> "automation-service-broker": timed out waiting for the condition >> I0910 12:01:24.765845 2101 interface.go:41] Finished installing >> "centos-imagestreams" "openshift-image-registry" "sample-templates" >> "openshift-web-console-operator" "openshift-router" "persistent-volumes" >> "automation-service-broker" "openshift-service-catalog" >> Error: timed out waiting for the condition >> >> [1] https://gist.github.com/cmoulliard/9c99457defc55f60d5326640a3d4b6 >> 3a#file-gistfile1-txt-L43 >> >> Regards >> >> Charles >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Sep 10 18:41:38 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 10 Sep 2018 20:41:38 +0200 Subject: [Ansible-service-broker] No APB catalog is available for orign 3.10 Message-ID: Hi When we deploy OAB using the ansible playbook on origin 3.10, the catalog is empty and APB pod doesn't report an issue. What could be the problem ? ansible-playbook -i inventory/cloud_host openshift-ansible/playbooks/openshift-service-catalog/config.yml -e ansible_service_broker_install=true --> Using config file mounted to /etc/ansible-service-broker/config.yaml ============================================================ == Creating Ansible Service Broker... == ============================================================ time="2018-09-10T17:38:44Z" level=info msg="Ansible Service Broker Version: 1.3.10" time="2018-09-10T17:38:44Z" level=info msg="Initializing clients..." time="2018-09-10T17:38:44Z" level=info msg="OpenShift version: v3.10.0+e3465d0-44" time="2018-09-10T17:38:44Z" level=info msg="Kubernetes version: v1.10.0+b81c8f8" time="2018-09-10T17:38:44Z" level=info msg="Empty AuthType. Assuming credentials are defined in the config... " time="2018-09-10T17:38:44Z" level=info msg="== REGISTRY CX == " time="2018-09-10T17:38:44Z" level=info msg="Name: dh" time="2018-09-10T17:38:44Z" level=info msg="Type: dockerhub" time="2018-09-10T17:38:44Z" level=info msg="Url: " time="2018-09-10T17:38:44Z" level=info msg="Empty AuthType. Assuming credentials are defined in the config... " time="2018-09-10T17:38:44Z" level=info msg="== REGISTRY CX == " time="2018-09-10T17:38:44Z" level=info msg="Name: localregistry" time="2018-09-10T17:38:44Z" level=info msg="Type: local_openshift" time="2018-09-10T17:38:44Z" level=info msg="Url: " ============================================================ == Starting Ansible Service Broker... == ============================================================ time="2018-09-10T17:38:44Z" level=info msg="Initiating Recovery Process" time="2018-09-10T17:38:44Z" level=info msg="Recovery complete" time="2018-09-10T17:38:44Z" level=info msg="recover called" time="2018-09-10T17:38:44Z" level=info msg="Broker configured to bootstrap on startup" time="2018-09-10T17:38:44Z" level=info msg="Attempting bootstrap..." time="2018-09-10T17:38:44Z" level=info msg="AnsibleBroker::Bootstrap" time="2018-09-10T17:38:44Z" level=info msg="0 specs deleted" time="2018-09-10T17:38:47Z" level=info msg="Bundles filtered by white/blacklist filter:\n\t-> ansibleplaybookbundle/kubevirt-ansible\n\t-> ansibleplaybookbundle/hello-world-apb\n\t-> ansibleplaybookbundle/rocketchat-apb\n\t-> ansibleplaybookbundle/rds-postgres-apb\n\t-> ansibleplaybookbundle/etherpad-apb\n\t-> ansibleplaybookbundle/wordpress-ha-apb\n\t-> ansibleplaybookbundle/hello-world-db-apb\n\t-> ansibleplaybookbundle/pyzip-demo-apb\n\t-> ansibleplaybookbundle/hastebin-apb\n\t-> ansibleplaybookbundle/jenkins-apb\n\t-> ansibleplaybookbundle/pyzip-demo-db-apb\n\t-> ansibleplaybookbundle/thelounge-apb\n\t-> ansibleplaybookbundle/manageiq-apb\n\t-> ansibleplaybookbundle/nginx-apb\n\t-> ansibleplaybookbundle/mediawiki-apb\n\t-> ansibleplaybookbundle/postgresql-apb\n\t-> ansibleplaybookbundle/mysql-apb\n\t-> ansibleplaybookbundle/mariadb-apb\n\t-> ansibleplaybookbundle/s2i-apb\n\t-> ansibleplaybookbundle/es-apb\n\t-> ansibleplaybookbundle/kibana-apb\n\t-> ansibleplaybookbundle/prometheus-apb\n\t-> ansibleplaybookbundle/awx-apb\n\t-> ansibleplaybookbundle/photo-album-demo-api-apb\n\t-> ansibleplaybookbundle/photo-album-demo-app-apb\n\t-> ansibleplaybookbundle/photo-album-demo-ext-api-apb\n\t-> ansibleplaybookbundle/iscsi-demo-target-apb\n\t-> ansibleplaybookbundle/mongodb-apb\n\t-> ansibleplaybookbundle/keycloak-apb\n\t-> ansibleplaybookbundle/virtualmachines-apb\n\t-> ansibleplaybookbundle/proxy-config-apb\n\t-> ansibleplaybookbundle/mssql-remote-apb\n\t-> ansibleplaybookbundle/dynamic-apb\n\t-> ansibleplaybookbundle/mssql-apb\n\t-> ansibleplaybookbundle/eclipse-che-apb\n\t-> ansibleplaybookbundle/manageiq-runner-apb\n\t-> ansibleplaybookbundle/import-vm-apb\n\t-> ansibleplaybookbundle/kubevirt-apb\n\t-> ansibleplaybookbundle/v2v-apb\n\t-> ansibleplaybookbundle/vnc-desktop-apb\n\t-> ansibleplaybookbundle/galera-apb\n\t-> ansibleplaybookbundle/openshift-logging-apb\n\t-> ansibleplaybookbundle/rhpam-apb\n\t-> ansibleplaybookbundle/tiller-apb\n\t-> ansibleplaybookbundle/standalone-cinder-apb\n\t-> ansibleplaybookbundl e/gluster-s3object-apb\n\t-> ansibleplaybookbundle/origin-ansible-service-broker\n\t-> ansibleplaybookbundle/hello-world\n\t-> ansibleplaybookbundle/mediawiki123\n\t-> ansibleplaybookbundle/apb-base\n\t-> ansibleplaybookbundle/ansible-service-broker\n\t-> ansibleplaybookbundle/apb-tools\n\t-> ansibleplaybookbundle/manageiq-apb-runner\n\t-> ansibleplaybookbundle/py-zip-demo\n\t-> ansibleplaybookbundle/mediawiki\n\t-> ansibleplaybookbundle/asb-installer\n\t-> ansibleplaybookbundle/apb-assets-base\n\t-> ansibleplaybookbundle/photo-album-demo-app\n\t-> ansibleplaybookbundle/helm-bundle-base\n\t-> ansibleplaybookbundle/origin\n\t-> ansibleplaybookbundle/photo-album-demo-api\n\t-> ansibleplaybookbundle/deploy-broker\n\t-> ansibleplaybookbundle/vnc-client\n\t-> ansibleplaybookbundle/origin-service-catalog\n\t-> ansibleplaybookbundle/vnc-desktop\n\t-> ansibleplaybookbundle/origin-deployer\n\t-> ansibleplaybookbundle/origin-docker-registry\n\t-> ansibleplaybookbundle/origin-haproxy-router\n\t-> ansibleplaybookbundle/origin-pod\n\t-> ansibleplaybookbundle/origin-sti-builder\n\t-> ansibleplaybookbundle/origin-recycler\n" time="2018-09-10T17:38:47Z" level=info msg="Validating specs..." time="2018-09-10T17:38:47Z" level=info msg="All specs passed validation!" time="2018-09-10T17:38:47Z" level=info msg="Bundles filtered by white/blacklist filter:\n\t-> openshift/dotnet\n\t-> openshift/dotnet-runtime\n\t-> openshift/httpd\n\t-> openshift/jenkins\n\t-> openshift/mariadb\n\t-> openshift/mongodb\n\t-> openshift/mysql\n\t-> openshift/nginx\n\t-> openshift/nodejs\n\t-> openshift/perl\n\t-> openshift/php\n\t-> openshift/postgresql\n\t-> openshift/python\n\t-> openshift/redis\n\t-> openshift/ruby\n\t-> openshift/wildfly\n" time="2018-09-10T17:38:47Z" level=info msg="Validating specs..." time="2018-09-10T17:38:47Z" level=info msg="All specs passed validation!" time="2018-09-10T17:38:47Z" level=info msg="Broker successfully bootstrapped on startup" time="2018-09-10T17:38:47Z" level=info msg="Listening on https://[::]:1338" time="2018-09-10T17:38:47Z" level=info msg="Ansible Service Broker Starting" Regards CHARLES MOULLIARD SOFTWARE ENGINEER MANAGER SPRING(BOOT) Red Hat cmoulliard at redhat.com M: +32-473-604014 @cmoulliard -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Tue Sep 11 05:31:07 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 11 Sep 2018 07:31:07 +0200 Subject: [Ansible-service-broker] Why some bundles are blacklisted Message-ID: Hi I have installed ASB on origin 3.10 and some bundles such as postgresql db are blacklisted when we use release-1.2 of ASB time="2018-09-11T05:28:21Z" level=info msg="Bundles filtered by white/blacklist filter:\n\t-> openshift/dotnet\n\t-> openshift/dotnet-runtime\n\t-> openshift/httpd\n\t-> openshift/jenkins\n\t-> openshift/mariadb\n\t-> openshift/mongodb\n\t-> openshift/mysql\n\t-> openshift/nginx\n\t-> openshift/nodejs\n\t-> openshift/perl\n\t-> openshift/php\n\t-> openshift/postgresql\n\t-> openshift/python\n\t-> openshift/redis\n\t-> openshift/ruby\n\t-> openshift/wildfly\n" How can we enable such bundles ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Tue Sep 11 09:37:54 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 11 Sep 2018 11:37:54 +0200 Subject: [Ansible-service-broker] Failed validation for the following reason: [ APB Spec version [1.0.0] out of bounds 1.0 <= 1.0 ]. Message-ID: Hi, With he latest image of the APBs or Broker deployed on origin 3.10 using command "oc cluster up", we can't use anymore some DB such as Postgresql time="2018-09-11T09:14:08Z" level=warning msg="Spec [ postgresql-apb ] failed validation for the following reason: [ APB Spec version [1.0.0] out of bounds 1.0 <= 1.0 ]. It will not be made available." Broker log : https://gist.github.com/cmoulliard/789b36c015f927f66a8ec4d1c58400d0#file-gistfile1-txt-L379 Is there a workaround ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From ernelson at redhat.com Tue Sep 11 13:27:56 2018 From: ernelson at redhat.com (Erik Nelson) Date: Tue, 11 Sep 2018 09:27:56 -0400 Subject: [Ansible-service-broker] Why some bundles are blacklisted In-Reply-To: References: Message-ID: Hi Charles, If you check the broker's configmap (oc edit configmap broker-config -n ), you should see a section for registry configuration with white/black list regex. The image names need to match on the whitelist pattern otherwise they will be filtered. I believe the default pattern is .*-apb, so none of those image names will pass. Alternatively, you could just set it to ".*" and it will allow all of them through. If you change the configmap, just note you will need to redeploy the broker for those changes to be picked up. Either delete the broker's pod, or rollout the latest broker dc in the namespace. On Tue, Sep 11, 2018 at 1:32 AM Charles Moulliard wrote: > Hi > > I have installed ASB on origin 3.10 and some bundles such as postgresql db > are blacklisted > when we use release-1.2 of ASB > > time="2018-09-11T05:28:21Z" level=info msg="Bundles filtered by > white/blacklist filter:\n\t-> openshift/dotnet\n\t-> > openshift/dotnet-runtime\n\t-> openshift/httpd\n\t-> > openshift/jenkins\n\t-> openshift/mariadb\n\t-> openshift/mongodb\n\t-> > openshift/mysql\n\t-> openshift/nginx\n\t-> openshift/nodejs\n\t-> > openshift/perl\n\t-> openshift/php\n\t-> openshift/postgresql\n\t-> > openshift/python\n\t-> openshift/redis\n\t-> openshift/ruby\n\t-> > openshift/wildfly\n" > > How can we enable such bundles ? > > Regards > > Charles > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Tue Sep 11 13:45:12 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 11 Sep 2018 15:45:12 +0200 Subject: [Ansible-service-broker] Why some bundles are blacklisted In-Reply-To: References: Message-ID: That works. Thanks On Tue, Sep 11, 2018 at 3:27 PM, Erik Nelson wrote: > Hi Charles, > > If you check the broker's configmap (oc edit configmap broker-config -n > ), you should see a section for registry configuration > with white/black list regex. The image names need to match on the whitelist > pattern otherwise they will be filtered. I believe the default pattern is > .*-apb, so none of those image names will pass. Alternatively, you could > just set it to ".*" and it will allow all of them through. If you change > the configmap, just note you will need to redeploy the broker for those > changes to be picked up. Either delete the broker's pod, or rollout the > latest broker dc in the namespace. > > On Tue, Sep 11, 2018 at 1:32 AM Charles Moulliard > wrote: > >> Hi >> >> I have installed ASB on origin 3.10 and some bundles such as postgresql >> db are blacklisted >> when we use release-1.2 of ASB >> >> time="2018-09-11T05:28:21Z" level=info msg="Bundles filtered by >> white/blacklist filter:\n\t-> openshift/dotnet\n\t-> >> openshift/dotnet-runtime\n\t-> openshift/httpd\n\t-> >> openshift/jenkins\n\t-> openshift/mariadb\n\t-> openshift/mongodb\n\t-> >> openshift/mysql\n\t-> openshift/nginx\n\t-> openshift/nodejs\n\t-> >> openshift/perl\n\t-> openshift/php\n\t-> openshift/postgresql\n\t-> >> openshift/python\n\t-> openshift/redis\n\t-> openshift/ruby\n\t-> >> openshift/wildfly\n" >> >> How can we enable such bundles ? >> >> Regards >> >> Charles >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Sep 17 08:52:16 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 17 Sep 2018 10:52:16 +0200 Subject: [Ansible-service-broker] Reduce the size of the docker images Message-ID: Hi, Is it possible to reduce the size of the docker images of (origin-ansible-service-broker, automation-broker-apb) which are needed for local development using okd (oc cluster up) or minishift as currently we have to download around 3.5GB docker.io/ansibleplaybookbundle/origin-ansible-service-broker release-1.2 06e8666456d5 3 months ago 1.94 GB docker.io/automationbroker/automation-broker-apb latest b543b29013ac 4 months ago 1.59 GB Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmontleo at redhat.com Mon Sep 17 12:47:22 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Mon, 17 Sep 2018 08:47:22 -0400 Subject: [Ansible-service-broker] Reduce the size of the docker images In-Reply-To: References: Message-ID: There definitely seems to be some disparity between the release-1.2 and latest ansible-service-broker. David, any insight to why they'd be so different? docker.io/ansibleplaybookbundle/origin-ansible-service-broker latest 99556e8a258a 2 weeks ago 530 MB docker.io/ansibleplaybookbundle/origin-ansible-service-broker release-1.2 06e8666456d5 3 months ago 1.94 GB I see the same with release-1.2/latest vs. 3.11: docker.io/automationbroker/automation-broker-apb v3.11 f14390c16e9c 2 weeks ago 570 MB docker.io/automationbroker/automation-broker-apb latest b543b29013ac 4 months ago 1.59 GB docker.io/automationbroker/automation-broker-apb release-1.2 b543b29013ac 4 months ago 1.59 GB I wonder if the larger ones were built from source for some reason? On 9/17/18 4:52 AM, Charles Moulliard wrote: > Hi, > > Is it possible to reduce the size of the docker images of > (origin-ansible-service-broker, automation-broker-apb) which are needed > for local development using okd (oc cluster up) or minishift as > currently we have to download around 3.5GB > > docker.io/ansibleplaybookbundle/origin-ansible-service-broker > > ?release-1.2? ? ? ? ?06e8666456d5? ? ? ? 3 months ago? ? ? ? 1.94 GB > docker.io/automationbroker/automation-broker-apb > > latest? ? ? ? ? ? ? b543b29013ac? ? ? ? 4 months ago? ? ? ? 1.59 GB > > Regards > > Charles > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From jmontleo at redhat.com Mon Sep 17 14:10:33 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Mon, 17 Sep 2018 10:10:33 -0400 Subject: [Ansible-service-broker] Reduce the size of the docker images In-Reply-To: References: Message-ID: I built a origin-ansible-service-broker:release-1.2 image from RPM that should help some. I just did a very quick test, but it looks to work OK. docker.io/ansibleplaybookbundle/origin-ansible-service-broker release-1.2 df4d13885a37 9 minutes ago 483 MB I'm not sure how the v3.10/release-1.2 automation-broker-apb was built. I may have to wait until David get's back to sync with him so we can sort it out if I can't figure it out. On 9/17/18 8:47 AM, Jason Montleon wrote: > There definitely seems to be some disparity between the release-1.2 and > latest ansible-service-broker. David, any insight to why they'd be so > different? > > docker.io/ansibleplaybookbundle/origin-ansible-service-broker > ???????????????????? latest????????????? 99556e8a258a??????? 2 weeks > ago???????? 530 MB > docker.io/ansibleplaybookbundle/origin-ansible-service-broker > ???????????????????? release-1.2???????? 06e8666456d5??????? 3 months > ago??????? 1.94 GB > > I see the same with release-1.2/latest vs. 3.11: > docker.io/automationbroker/automation-broker-apb > v3.11?????????????? f14390c16e9c??????? 2 weeks ago???????? 570 MB > docker.io/automationbroker/automation-broker-apb > latest????????????? b543b29013ac??????? 4 months ago??????? 1.59 GB > docker.io/automationbroker/automation-broker-apb > release-1.2???????? b543b29013ac??????? 4 months ago??????? 1.59 GB > > I wonder if the larger ones were built from source for some reason? > > On 9/17/18 4:52 AM, Charles Moulliard wrote: >> Hi, >> >> Is it possible to reduce the size of the docker images of >> (origin-ansible-service-broker, automation-broker-apb) which are >> needed for local development using okd (oc cluster up) or minishift as >> currently we have to download around 3.5GB >> >> docker.io/ansibleplaybookbundle/origin-ansible-service-broker >> >> ??release-1.2? ? ? ? ?06e8666456d5? ? ? ? 3 months ago? ? ? ? 1.94 GB >> docker.io/automationbroker/automation-broker-apb >> latest >> ? ? ? ? b543b29013ac? ? ? ? 4 months ago? ? ? ? 1.59 GB >> >> Regards >> >> Charles >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From jesusr at redhat.com Tue Sep 18 13:07:57 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 18 Sep 2018 09:07:57 -0400 Subject: [Ansible-service-broker] CANCELED Automation Broker IRC meeting Message-ID: <94a32cff8c467fcc82ed867616a8dfe4422416c4.camel@redhat.com> There were no new topics to discuss this morning, so we're canceling the IRC meeting. Sincerely, jesus -- jesus m. rodriguez | jesusr at redhat.com principal software engineer | irc: zeus red hat systems management | 919.754.4413 (w) rhce # 805008586930012 | 919.623.0080 (c) +---------------------------------------------+ | "you will be assimilated; | | resistance is futile" | | -- Borg | +---------------------------------------------+ From simon.ruegg at vshn.ch Thu Sep 20 07:48:49 2018 From: simon.ruegg at vshn.ch (=?UTF-8?Q?Simon_R=c3=bcegg?=) Date: Thu, 20 Sep 2018 09:48:49 +0200 Subject: [Ansible-service-broker] Missing _apb_provision_creds variable Message-ID: <26d07a3d-9ea8-1fd1-20a0-24da4802ea8a@vshn.ch> Hi all, I'm running the ansible-service broker on OpenShift container platform v3.9 with the following image: 'registry.access.redhat.com/openshift3/ose-ansible-service-broker:v3.9' I developed and tested an APB locally against a v3.9 "oc cluster up" which worked perfectly fine. Once I deployed it on the OCP cluster, the deprovisioning playbook failed due to the _apb_provision_creds variable being undefined. Is there any difference in those two versions? How am I supposed to access the provisioned credentials? Thanks for your help, Simon R?egg System Engineer VSHN AG | Neugasse 10 | CH-8005 Z?rich T: +41 44 545 53 00 | M: +41 78 770 35 13 | https://vshn.ch -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From jmontleo at redhat.com Thu Sep 20 13:29:17 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Thu, 20 Sep 2018 09:29:17 -0400 Subject: [Ansible-service-broker] Missing _apb_provision_creds variable In-Reply-To: <26d07a3d-9ea8-1fd1-20a0-24da4802ea8a@vshn.ch> References: <26d07a3d-9ea8-1fd1-20a0-24da4802ea8a@vshn.ch> Message-ID: <0e5e9b53-251f-a360-3b7a-6650afbae85d@redhat.com> Hi Simon, What method did you use to install the Broker in your 3.9 oc cluster up environment? If you can run oc describe against the broker pod and see what is specified in for the image we can get a better idea if you're using a broker version that would differ from 'registry.access.redhat.com/openshift3/ose-ansible-service-broker:v3.9' On 9/20/18 3:48 AM, Simon R?egg wrote: > Hi all, > > I'm running the ansible-service broker on OpenShift container platform > v3.9 with the following image: > 'registry.access.redhat.com/openshift3/ose-ansible-service-broker:v3.9' > > I developed and tested an APB locally against a v3.9 "oc cluster up" > which worked perfectly fine. Once I deployed it on the OCP cluster, the > deprovisioning playbook failed due to the _apb_provision_creds variable > being undefined. Is there any difference in those two versions? How am I > supposed to access the provisioned credentials? > > > Thanks for your help, > > Simon R?egg > System Engineer > > VSHN AG | Neugasse 10 | CH-8005 Z?rich > T: +41 44 545 53 00 | M: +41 78 770 35 13 | https://vshn.ch > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From cmoullia at redhat.com Thu Sep 27 14:54:54 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 27 Sep 2018 16:54:54 +0200 Subject: [Ansible-service-broker] Default's plan per service Message-ID: Hi Is it possible to know which plan is the default to be used if a user doesn't select it when it will create a service instance ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: