From cmoullia at redhat.com Fri Jun 1 07:28:14 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 1 Jun 2018 09:28:14 +0200 Subject: [Ansible-service-broker] Question about role's action and build role In-Reply-To: References: Message-ID: On Thu, May 31, 2018 at 10:10 PM, David Zager wrote: > Greetings Charles, > > First, to answer question #1. All of the actions available via the > ansible-kubernetes-modules > can be found in > the library > > folder of that project. This project is deprecated now in favor of the > kubernetes/openshift modules provided by Ansible 2.5. You may have noticed > a change to some of our APBs. Particularly mediawiki-apb > , > postgresql-apb > > , mysql-apb > , > and mariadb-apb > > to use k8s_raw > / > openshift_raw > > introduced in Ansible 2.5. These are great and all but share some of the > limitations as the ansible-kubernetes-modules. If you use apb-base:canary > it > includes the development version of Ansible (2.6) and used the dynamic > client which allows you to write Ansible that communicates more directly > with the kubernetes API server. Why is this significant? It allows you to > interact with CRDs, CRs, and aggregated APIs (something that was not > possible before). You should totally check out the k8s module > and the k8s > lookup plugin > . If you > want an example of these in action checkout the automation-broker-apb > (currently > in PR to be added to the broker project) or the hello-world-apb > > (currently in PR to update to Ansible 2.6). > >> This is agreat new change/feature which will also let us to package more easily Istio related applications which are using CRD ;-) > > You say, "Can we also use APB to do a build [2] ?" and I am intrigued. > This sounds like an interesting idea but I don't see well how this use case > would work in practice. Maybe you could elaborate on this in the form of an > issue that > we could talk about in more detail at the next ansible-service-broker > community meeting (Tuesday 9:30 AM EST)? > >> I will create a ticket but as you mentioned it could very hard to achieve or to work in practice. > > Thank you for the email and helping us improve the broker. I hope I was > able to add some useful info. > > Respectfully, > David Zager > > On Thu, May 31, 2018 at 3:34 PM Charles Moulliard > wrote: > >> Hi, >> >> Where are defined = coded all the actions available for APB's role such >> as "openshift_v1_deployment_config, openshift_v1_route, ..." (here maybe >> [1]) ? >> >> Can we also use APB to do a build [2] ? >> >> I don't think that this possible as the current actions [3] are : >> bind/unbind, provision/deprovision >> but that should be great to add a new action able to do a build from GIT >> source, using jenkinsfile, using binary stream of the current priject >> (source or jar) or using Dockerfile of the user >> >> [1] https://github.com/ansible/ansible-kubernetes- >> modules/tree/master/library >> [2] https://github.com/ansible/ansible-kubernetes- >> modules/blob/master/library/openshift_v1_build_config.py >> [3] https://docs.openshift.org/latest/apb_devel/writing/ >> reference.html#apb-devel-writing-ref-actions >> >> 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 fmontaldo3 at gmail.com Mon Jun 4 22:46:58 2018 From: fmontaldo3 at gmail.com (federico montaldo) Date: Mon, 4 Jun 2018 19:46:58 -0300 Subject: [Ansible-service-broker] help with ansible broker Message-ID: Hi, I followed the instruction to install ansible broker into minishfit. I made the following: minishift version minishift v1.15.1+f19ac09 CDK v3.4.0-2 oc cluster up --service-catalog=true oc login -u system:admin oc new-project ansible-service-broker curl -s https://raw.githubusercontent.com/openshift/ansible-service-broker/master/templates/simple-broker-template.yaml | oc process -n "ansible-service-broker" -f - | oc create -f - oc get clusterserviceclasses --all-namespaces -o custom-columns=NAME:.metadata.name,DISPLAYNAME:spec.externalMetadata.displayName | grep APB 0e991006d21029e47abe71acc255e807 Pyzip Demo (APB) 135bd0df0401e2fdd52fd136935014fb NGINX (APB) 1dda1477cace09730bd8ed7a6505607e PostgreSQL (APB) 5d0062cce443e5ecb8438ca5f664dcd7 Kibana (APB) 67042296c7c95e84142f21f58da2ebfe MariaDB (APB) 693cb128e68365830c913631300deac0 Pyzip Demo Database (APB) 6df7afbd132c094704b4a8bfd44378c0 ManageIQ (APB) 880ef3b4ba5fa8d80908e9974228e603 AWX (APB) 9f7da06f179b895a8ee5f9a3ce4af7ef Hello World (APB) a946a139a9308a59bf642ac52b4ba317 Wordpress-HA (APB) ab24ffd54da0aefdea5277e0edce8425 Hastebin (APB) aff6d7bb9c7f57c9ce8b742228e4caa3 Elasticsearch (APB) b43a4272a6efcaaa3e0b9616324f1099 Hello World Database (APB) ba9c2d4db404ce97111bea80225de968 RocketChat (APB) c65fbd4e701cb71d74fd2cc35e14432b Amazon RDS - PostgreSQL (APB) ca91b61da8476984f18fc13883ae2fdb Etherpad (APB) ddd528762894b277001df310a126d5ad MySQL (APB) eebf92c7670f30007a4b8db3a8166d5c The Lounge (APB) f4509733ca0636df3d69b6af53260160 Jenkins (APB) f6c4486b7fb0cdac4b58e193607f7011 Mediawiki (APB) f755257efed3e3d43c8b82afd0db1181 Prometheus (APB) When I tried to run apb list this error occur: apb list Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog ERROR: Failed broker request (get) https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog Exception occurred! local variable 'InsecureRequestWarning' referenced before assignment oc whoami system:admin oc login -u system:admin Logged into "https://127.0.0.1:8443" as "system:admin" using existing credentials. You have access to the following projects and can switch between them with 'oc project ': ansible-service-broker custom-broker default kube-public kube-service-catalog kube-system myproject openshift openshift-infra openshift-node openshift-template-service-broker openshift-web-console apb list Contacting the ansible-service-broker at: https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog ERROR: Failed broker request (get) https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog Exception occurred! local variable 'InsecureRequestWarning' referenced before assignment From ernelson at redhat.com Tue Jun 5 13:04:06 2018 From: ernelson at redhat.com (Erik Nelson) Date: Tue, 5 Jun 2018 09:04:06 -0400 Subject: [Ansible-service-broker] help with ansible broker In-Reply-To: References: Message-ID: Hi Federico, If you are using minishift, instead of manually installing the broker, I would recommend using our minishift addon: https://github.com/minishift/minishift-addons/tree/master/add-ons/ansible-service-broker It will take care of applying the correct permissions so that you can use the apb tool. Could you point me to the instructions that you used? I want to make sure they're up to date. Thanks for your feedback! On Mon, Jun 4, 2018 at 6:46 PM, federico montaldo wrote: > Hi, > > I followed the instruction to install ansible broker into minishfit. I > made the following: > > minishift version > minishift v1.15.1+f19ac09 > CDK v3.4.0-2 > > oc cluster up --service-catalog=true > oc login -u system:admin > oc new-project ansible-service-broker > curl -s https://raw.githubusercontent.com/openshift/ansible-service-broker/master/templates/simple-broker-template.yaml > | oc process -n "ansible-service-broker" -f - | oc create -f - > > oc get clusterserviceclasses --all-namespaces -o > custom-columns=NAME:.metadata.name,DISPLAYNAME:spec.externalMetadata.displayName > | grep APB > 0e991006d21029e47abe71acc255e807 Pyzip Demo (APB) > 135bd0df0401e2fdd52fd136935014fb NGINX (APB) > 1dda1477cace09730bd8ed7a6505607e PostgreSQL (APB) > 5d0062cce443e5ecb8438ca5f664dcd7 Kibana (APB) > 67042296c7c95e84142f21f58da2ebfe MariaDB (APB) > 693cb128e68365830c913631300deac0 Pyzip Demo Database (APB) > 6df7afbd132c094704b4a8bfd44378c0 ManageIQ (APB) > 880ef3b4ba5fa8d80908e9974228e603 AWX (APB) > 9f7da06f179b895a8ee5f9a3ce4af7ef Hello World (APB) > a946a139a9308a59bf642ac52b4ba317 Wordpress-HA (APB) > ab24ffd54da0aefdea5277e0edce8425 Hastebin (APB) > aff6d7bb9c7f57c9ce8b742228e4caa3 Elasticsearch (APB) > b43a4272a6efcaaa3e0b9616324f1099 Hello World Database (APB) > ba9c2d4db404ce97111bea80225de968 RocketChat (APB) > c65fbd4e701cb71d74fd2cc35e14432b Amazon RDS - PostgreSQL (APB) > ca91b61da8476984f18fc13883ae2fdb Etherpad (APB) > ddd528762894b277001df310a126d5ad MySQL (APB) > eebf92c7670f30007a4b8db3a8166d5c The Lounge (APB) > f4509733ca0636df3d69b6af53260160 Jenkins (APB) > f6c4486b7fb0cdac4b58e193607f7011 Mediawiki (APB) > f755257efed3e3d43c8b82afd0db1181 Prometheus (APB) > > When I tried to run apb list this error occur: > apb list > Contacting the ansible-service-broker at: > https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog > ERROR: Failed broker request (get) > https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog > Exception occurred! local variable 'InsecureRequestWarning' referenced > before assignment > > oc whoami > system:admin > > oc login -u system:admin > Logged into "https://127.0.0.1:8443" as "system:admin" using existing > credentials. > > You have access to the following projects and can switch between them > with 'oc project ': > > ansible-service-broker > custom-broker > default > kube-public > kube-service-catalog > kube-system > myproject > openshift > openshift-infra > openshift-node > openshift-template-service-broker > openshift-web-console > apb list > Contacting the ansible-service-broker at: > https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog > ERROR: Failed broker request (get) > https://asb-1338-ansible-service-broker.127.0.0.1.nip.io/openshift-automation-service-broker/v2/catalog > Exception occurred! local variable 'InsecureRequestWarning' referenced > before assignment > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker From jesusr at redhat.com Tue Jun 5 14:41:21 2018 From: jesusr at redhat.com (jesus m. rodriguez) Date: Tue, 05 Jun 2018 10:41:21 -0400 Subject: [Ansible-service-broker] Automation Broker Community Meeting June 5th, 2018 Message-ID: <1528209681.10090.2.camel@redhat.com> ======================================== #asbroker: Automation Broker 6/5 meeting ======================================== Meeting started by jmrodri at 13:31:36 UTC. The full logs are available at asbroker/2018/asbroker.2018-06-05-13.31.log.html . Meeting summary --------------- * attendance (jmrodri, 13:32:00) * News (jmrodri, 13:33:34) * bundle-lib 0.2.2 released on June 1st (jmrodri, 13:34:08) * LINK: https://github.com/automationbroker/bundle-lib/releases/tag/0.2.2 (jmrodri, 13:34:23) * SouthEast LinuxFest (SELF) (jmrodri, 13:35:42) * LINK: http://www.southeastlinuxfest.org// (jmrodri, 13:35:50) * Review Previous Actions (jmrodri, 13:38:37) * Binding errors are no longer displayed (jmrodri, 13:39:17) * LINK: https://github.com/openshift/ansible-service-broker/issues/941 (jmrodri, 13:39:20) * ACTION: jmrodri test issue 941 https://github.com/openshift/ansible-service-broker/issues/941 (jmrodri, 13:39:45) * shurley issue 813 (jmrodri, 13:40:06) * LINK: https://github.com/openshift/ansible-service-broker/issues/813 (jmrodri, 13:40:11) * ACTION: shurley shepherd issue 813 https://github.com/openshift/ansible-service-broker/issues/813 (jmrodri, 13:41:17) * BindInstance.Parameters use unclear (jmrodri, 13:41:32) * LINK: https://github.com/openshift/ansible-service-broker/issues/692 (jmrodri, 13:41:41) * jmrodri move 3.10 aligned features to 3.11 or 3.12 (jmrodri, 13:42:51) * jmrodri review PR 96 (bundle-lib) (jmrodri, 13:43:42) * LINK: https://github.com/automationbroker/bundle-lib/pull/96 (jmrodri, 13:43:46) * dymurray play around with the module and update the issue (jmrodri, 13:44:25) * Bug/Issue Triage (jmrodri, 13:46:25) * Error: Attempt to list APBs in the broker returned status 503 (jmrodri, 13:46:50) * LINK: https://github.com/openshift/ansible-service-broker/issues/974 (jmrodri, 13:46:52) * ACTION: ernelson to investigate issue 974 https://github.com/openshift/ansible-service-broker/issues/974 (jmrodri, 13:48:20) * Doc link for complicated parameters (jmrodri, 13:49:17) * LINK: https://github.com/openshift/ansible-service-broker/issues/973 (jmrodri, 13:49:19) * ACTION: maleck13 to investigate issue 973 https://github.com/openshift/ansible-service-broker/issues/973 (jmrodri, 13:52:48) * suggestion: move away from panic in the lib (bundle-lib) (jmrodri, 13:54:48) * LINK: ttps://github.com/automationbroker/bundle-lib/issues/94 (jmrodri, 13:54:55) * LINK: https://github.com/automationbroker/bundle-lib/issues/94 (jmrodri, 13:54:59) * ACTION: jmrodri to investigate issue 94 on bundle-lib (jmrodri, 13:55:56) * Possible use case for bundle-lib and operator framework (jmrodri, 13:56:41) * LINK: https://github.com/automationbroker/bundle-lib/issues/79 (jmrodri, 13:56:43) * ACTION: shurley to comment and close issue 79 (jmrodri, 13:58:51) * bundle package needs better test coverage (jmrodri, 14:00:05) * LINK: https://github.com/automationbroker/bundle-lib/issues/55 (jmrodri, 14:00:12) * ACTION: jmrodri review issue #2 on bundle-lib and verify if there are anymore items to be done (jmrodri, 14:03:34) * ACTION: shurley work with jmrodri to label and triage bundle-lib issues (jmrodri, 14:04:22) * ACTION: jmrodri work with shurley to add license to bundle-lib (jmrodri, 14:04:39) * Concept of making the broker aware of managed sharable multi-tenant services (jmrodri, 14:07:08) * LINK: https://github.com/openshift/ansible-service-broker/issues/979 (jmrodri, 14:07:13) * ACTION: maleck13 progress the spike around the broker and update the issue with further details (jmrodri, 14:26:15) * open discussions (jmrodri, 14:27:02) * Broker should not fail hard when registry names collide (jmrodri, 14:27:16) * LINK: https://github.com/openshift/ansible-service-broker/issues/813 (jmrodri, 14:29:52) * ACTION: jmrodri review PR 928 (jmrodri, 14:32:51) * ACTION: shurley review PR 928 (jmrodri, 14:32:56) Meeting ended at 14:33:06 UTC. Action Items ------------ * jmrodri test issue 941 https://github.com/openshift/ansible-service-broker/issues/941 * shurley shepherd issue 813 https://github.com/openshift/ansible-service-broker/issues/813 * ernelson to investigate issue 974 https://github.com/openshift/ansible-service-broker/issues/974 * maleck13 to investigate issue 973 https://github.com/openshift/ansible-service-broker/issues/973 * jmrodri to investigate issue 94 on bundle-lib * shurley to comment and close issue 79 * jmrodri review issue #2 on bundle-lib and verify if there are anymore items to be done * shurley work with jmrodri to label and triage bundle-lib issues * jmrodri work with shurley to add license to bundle-lib * maleck13 progress the spike around the broker and update the issue with further details * jmrodri review PR 928 * shurley review PR 928 Action Items, by person ----------------------- * ernelson * ernelson to investigate issue 974 https://github.com/openshift/ansible-service-broker/issues/974 * jmrodri * jmrodri test issue 941 https://github.com/openshift/ansible-service-broker/issues/941 * jmrodri to investigate issue 94 on bundle-lib * jmrodri review issue #2 on bundle-lib and verify if there are anymore items to be done * shurley work with jmrodri to label and triage bundle-lib issues * jmrodri work with shurley to add license to bundle-lib * jmrodri review PR 928 * maleck13 * maleck13 to investigate issue 973 https://github.com/openshift/ansible-service-broker/issues/973 * maleck13 progress the spike around the broker and update the issue with further details * shurley * shurley shepherd issue 813 https://github.com/openshift/ansible-service-broker/issues/813 * shurley to comment and close issue 79 * shurley work with jmrodri to label and triage bundle-lib issues * jmrodri work with shurley to add license to bundle-lib * shurley review PR 928 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jmrodri (128) * brokerbot (57) * maleck13 (44) * shurley (30) * mhrivnak (22) * ernelson (10) * philipgough (10) * dymurray (7) * fmontaldo3 (6) * dzager (4) * dwhatley (1) * leifmadsen (1) * Jmainguy (1) * fabianvf (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From jmatthew at redhat.com Wed Jun 6 13:17:01 2018 From: jmatthew at redhat.com (John Matthews) Date: Wed, 6 Jun 2018 09:17:01 -0400 Subject: [Ansible-service-broker] Automation Broker exposing OpenStack Services to K8S [Early discussions on openstack-dev] Message-ID: FYI, Below mailing list conversation may be of interest to folks. Initial discussions are beginning to explore the possibility of leveraging the Automation Broker for exposing OpenStack services into Kubernetes. http://lists.openstack.org/pipermail/openstack-dev/2018-June/131183.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From dzager at redhat.com Wed Jun 6 20:10:43 2018 From: dzager at redhat.com (David Zager) Date: Wed, 6 Jun 2018 16:10:43 -0400 Subject: [Ansible-service-broker] Sprint 149 Release Notes Message-ID: Bugs - Bug 1550418 - Return op token on depro in progress (#942) - Bug 1577144 - fixing logging so it is more clear (#949) - Bug 1577127 - adding back metrics (#948) - Bug 1576728 - Fixes multiple requests to a CR (#947) - Bug 1572129 - recover deprovision jobs (#953) - Bug 1578319 - send _apb* parameters to unbind (#959) - Bug 1581580 - skip if bind instance does not have credentials (#966) - Bug 1583064 - missing action causes many sandboxes (#971) - Bug 1585649 - wait group should be added to before go function is kicked off (#976) Other Enhancements - Allow Automation Broker to be useful when used as a dependency (#933) - bump bundle-lib to 0.1.5 (#937) - doc to show how to use broker via vendor (#940) - Update releases in README (#952) - update config.md for partner registry adapter (#950) - Replace latest with release-1.2 (#956) - Bump bundle lib to 0.1.8 (#968) -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbrookes at redhat.com Thu Jun 7 16:04:29 2018 From: cbrookes at redhat.com (Craig Brookes) Date: Thu, 7 Jun 2018 17:04:29 +0100 Subject: [Ansible-service-broker] service bundle plans roles and broker checks Message-ID: I know there was some discussion around an APB defining the roles needed to execute it. I was wondering would it be reasonable to specify a role at the plan level and have the broker check that the user provisioning the service using a given plan has the specified role. Ideally the plan would not show up for users without the role but it would still need to be checked at the broker level. This is something that I began thinking about while fleshing out the shared service spike I mentioned on the last broker irc meeting. Hopefully this makes sense without the context of the meeting. If more info needed please ask. -- Craig Brookes RHMAP @maleck13 Github -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Tue Jun 12 14:19:05 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Tue, 12 Jun 2018 10:19:05 -0400 Subject: [Ansible-service-broker] Automation Broker IRC Meeting June 12, 2018 Message-ID: ==================================== #asbroker: Automation Broker 6-12-18 ==================================== Meeting started by rhallisey at 13:31:44 UTC. The full logs are attached. Meeting summary --------------- * Attendance (rhallisey, 13:32:01) * News (rhallisey, 13:33:21) * Review Previous Actions (rhallisey, 13:36:32) * ernelson to investigate issue 974 (rhallisey, 13:37:05) * ACTION: community: review https://github.com/openshift/ansible-service-broker/issues/979 (rhallisey, 13:41:12) * Bugs/Issue triage (rhallisey, 13:42:29) * Features (rhallisey, 13:43:29) * LINK: https://github.com/openshift/ansible-service-broker/issues/979#issuecomment-396511919 (rhallisey, 13:43:38) * Allow role checks on plans / apbs (rhallisey, 13:43:57) * ACTION: maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 (rhallisey, 13:57:26) * LINK: https://github.com/openshift/ansible-service-broker/pull/928 (rhallisey, 13:58:39) * ACTION: community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 (rhallisey, 14:00:32) * Open Discussion (rhallisey, 14:01:50) * Better way to mock out getting a new executor - shurley (rhallisey, 14:02:34) * ACTION: jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 (rhallisey, 14:07:04) Meeting ended at 14:12:39 UTC. Action Items ------------ * community: review https://github.com/openshift/ansible-service-broker/issues/979 * maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 * community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 * jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 Action Items, by person ----------------------- * maleck13 * maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 * **UNASSIGNED** * community: review https://github.com/openshift/ansible-service-broker/issues/979 * community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 * jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 People Present (lines said) --------------------------- * rhallisey (46) * shurley (32) * maleck13 (32) * brokerbot (21) * philipgough (7) * mhrivnak (7) * dzager (6) * jmontleon (4) * fabianvf (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ==================================== #asbroker: Automation Broker 6-12-18 ==================================== Meeting started by rhallisey at 13:31:44 UTC. The full logs are available at asbroker/2018/asbroker.2018-06-12-13.31.log.html . Meeting summary --------------- * Attendance (rhallisey, 13:32:01) * News (rhallisey, 13:33:21) * Review Previous Actions (rhallisey, 13:36:32) * ernelson to investigate issue 974 (rhallisey, 13:37:05) * ACTION: community: review https://github.com/openshift/ansible-service-broker/issues/979 (rhallisey, 13:41:12) * Bugs/Issue triage (rhallisey, 13:42:29) * Features (rhallisey, 13:43:29) * LINK: https://github.com/openshift/ansible-service-broker/issues/979#issuecomment-396511919 (rhallisey, 13:43:38) * Allow role checks on plans / apbs (rhallisey, 13:43:57) * ACTION: maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 (rhallisey, 13:57:26) * LINK: https://github.com/openshift/ansible-service-broker/pull/928 (rhallisey, 13:58:39) * ACTION: community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 (rhallisey, 14:00:32) * Open Discussion (rhallisey, 14:01:50) * Better way to mock out getting a new executor - shurley (rhallisey, 14:02:34) * ACTION: jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 (rhallisey, 14:07:04) Meeting ended at 14:12:39 UTC. Action Items ------------ * community: review https://github.com/openshift/ansible-service-broker/issues/979 * maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 * community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 * jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 Action Items, by person ----------------------- * maleck13 * maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 * **UNASSIGNED** * community: review https://github.com/openshift/ansible-service-broker/issues/979 * community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 * jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 People Present (lines said) --------------------------- * rhallisey (46) * shurley (32) * maleck13 (32) * brokerbot (21) * philipgough (7) * mhrivnak (7) * dzager (6) * jmontleon (4) * fabianvf (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- 13:31:44 #startmeeting Automation Broker 6-12-18 13:31:44 Meeting started Tue Jun 12 13:31:44 2018 UTC. The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:31:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:31:44 The meeting name has been set to 'automation_broker_6-12-18' 13:31:44 rhallisey: startmeeting Meeting Agenda https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing 13:31:54 dzager, /usr/bin/entrypoint.sh: line 16: jq: command not found 13:32:01 #topic Attendance 13:32:01 rhallisey: topic 13:32:05 o/ 13:32:07 jmontleon: :) 13:32:19 need to install jq on your image? 13:32:22 o/ 13:32:26 o/ 13:32:31 \o 13:32:35 jmontleon: yup 13:32:36 Hi 13:33:01 ~~~~\o/~~~~^~~~~~ 13:33:21 #topic News 13:33:21 rhallisey: topic 13:33:35 nothing listed. I don't have anything personally 13:33:38 hey 13:33:40 Hi 13:33:45 hey maleck13 fabianvf 13:33:53 any news from folks? 13:34:12 quick bit 13:34:31 We had a good crowd at the SouthEast LinuxFest, maybe 60 or so in the room for a broker talk. 13:34:51 Good questions, and the stickers were very popular. ;) 13:34:55 Wow 13:35:01 nice 13:35:11 stickers? theres stickers :) 13:35:44 maleck13, we can ship you some 13:35:55 rhallisey: that would be awesome 13:36:32 #topic Review Previous Actions 13:36:32 rhallisey: topic 13:36:51 jmrodri, isn't here right now. Will skip his 13:37:05 #info ernelson to investigate issue 974 13:37:05 rhallisey: info 13:37:57 ernelson, should I carry this item for next week? 13:38:57 actually, instead of going through one by one 13:39:16 does anyone have a particular item they want to go over in current action items? 13:39:29 I do 13:39:50 The spike is around managed shared services. currently working on a doc that outlines the work, but added a comment to share the approach to provisioning that I am leaning towards 13:39:53 to get feedback 13:40:38 would appreciate any thoughts on that issue if ppl have to time to take a look 13:41:09 Will keep an eye out for that. 13:41:12 #action community: review https://github.com/openshift/ansible-service-broker/issues/979 13:41:12 rhallisey: action 13:41:24 thanks for that maleck13 13:41:46 maleck13: it is on my todo stack today :) 13:41:53 mhrivnak: shurley thanks 13:41:58 any more action items to review? 13:42:29 #topic Bugs/Issue triage 13:42:29 rhallisey: topic 13:42:44 no items listed here. Did folks have anything to add? 13:43:25 ok. Moving to features 13:43:29 #topic Features 13:43:29 rhallisey: topic 13:43:38 #link https://github.com/openshift/ansible-service-broker/issues/979#issuecomment-396511919 13:43:38 rhallisey: link 13:43:39 I don?nt have anyting 13:43:57 #info Allow role checks on plans / apbs 13:43:57 rhallisey: info 13:44:31 So this is mine and came up while fleshing out the managed shared services stuff 13:45:10 TLDR allow a role to be specified at the plan level, that specifies which role a user needs to provision a particular plan 13:45:36 and have the broker check that role if it is present 13:45:52 it seems like something the broker should do rather than the catalog? 13:46:20 this was alos on my to read to list 13:46:25 give me a second to read 13:47:36 my initial thought is that this would go in the catalog 13:48:00 I see the problem. So we asking for the broker to check, not that the requesting user has access to the sandbox role, but to the role that the APB has asked for 13:48:02 rhallisey: but does that not mean the brokers needs to know about k8s roles when sending back service classes 13:48:14 shurley: yes 13:48:38 so in this scenario we would need to use the plan?s role if presetn 13:48:41 rhallisey: I don't think brokers would all know about this 13:48:43 *present 13:48:47 yes 13:48:53 as the role for the service account grants 13:49:20 shurley: or perhaps just check the user doing the provision has the role 13:49:31 shurley: then allow the provision to go ahead as normal 13:49:52 Ok, something else that is on the backlog that is tagentally related is https://trello.com/c/fiOSsq1Q/123-5-revisit-replacing-subjectrulesreview-with-subject-access-rule-to-gain-ability-to-check-permissions-in-pure-k8s-as-well-as-open#comment-5ac7a023ac6bd35b2cc6a412 13:50:44 so checking if a user has a role is not really that good. 13:51:01 because they could be apart of a group that has the role permissions 13:51:48 ok 13:51:50 so instead we can use the aggregated roles which has been on the back log, and If we do this plus the change then this is something that could be possible in both k8s and openshift 13:52:20 * maleck13 goes to look up aggregated roles 13:52:40 I am not opposed to doing both but I think we need to do them together OR the trello card first IMO 13:53:14 dymurray mhrivnak dzager any thoughs on apb plan defining the role? 13:54:00 It has potential future use in the OpenShift ui if we can hide and show plans based on the users roles also 13:54:02 side point 13:54:36 I think I need to read up on this one some more. 13:54:54 As said in the issue it is part of the spike so not something required right now, but would be good to know if on a track that makes sense in the automation broker 13:55:08 I'm not able to visualize this with aggregated roles. Also need to read more into this 13:55:15 the apb plan defining the role? I think I need more here 13:55:16 If easier can set up a call to talk through the work we are doing 13:55:27 the big movement in the apb layout is to more of the ansible-galaxy format (ie. 1 role) 13:56:01 dzager: think role might be overloaded in this conversation 13:56:10 fabianvf: yes :) 13:56:13 maleck13: +1 might be a good time to discuss the above work if anyone has questions? 13:56:15 fabianvf: that helps 13:56:19 'role' = k8s role 13:56:51 call++ 13:56:59 ok so that is an action for me 13:57:26 #action maleck13: schedule a call with interested parties to discuss https://github.com/openshift/ansible-service-broker/issues/982 13:57:26 rhallisey: action 13:57:43 any more features to bring up folks? 13:58:16 maleck13, if you can throw the invite in the ML and folks can respond as they please would work 13:58:27 Just wanted to bring up this pr for conditional params again https://github.com/openshift/ansible-service-broker/pull/928 13:58:38 thanks for the visual ack shurley 13:58:39 #link https://github.com/openshift/ansible-service-broker/pull/928 13:58:39 rhallisey: link 13:58:55 Its not building because it has a dependency on a change in bundle-lib 13:59:04 Was wondering on the best way to handle this 13:59:26 we need to merge bundle lib and then need to do a release 13:59:46 then you should bump the release in your PR to the new bundle lib release 13:59:51 has been our current process 13:59:57 shurley: Sure thanks, so from my point of view there is nothing I need to do here as of now? 14:00:07 Right cool, just wanted to clarify 14:00:32 #action community: review https://github.com/automationbroker/bundle-lib/pull/70 and cut a release to unblock https://github.com/openshift/ansible-service-broker/pull/928 14:00:32 rhallisey: action 14:00:49 thanks philipgough 14:01:09 any more features to bring up? 14:01:50 #topic Open Discussion 14:01:50 rhallisey: topic 14:02:08 #info Better way to mock out getting a new executor 14:02:08 rhallisey: info 14:02:27 #undo 14:02:27 Removing item from minutes: INFO by rhallisey at 14:02:08 : Better way to mock out getting a new executor 14:02:34 #info Better way to mock out getting a new executor - shurley 14:02:34 rhallisey: info 14:02:55 is there an issue tracking is? 14:02:56 so, I have been working on adding unit tests to the places we have been ignoring 14:03:36 and I notice that the one of things that we just are not able to mock/encapsulate is the call to bundle.NewExecutor() 14:03:53 +1 14:04:10 which makes unit testing the jobs.go in broker/ pkg hard 14:04:28 hit a similar issue with the jobs in the broker. Solved with an interface that has NewProvisionJob etc 14:04:38 so my PR go it up to like 70ish percent and we can just say meh that is good enough 14:04:50 or we can refactor to make it better 14:05:16 but I have not seen jmrodri or ernelson who I assume will have strong opinions on this one so I don?t want to go to far down this road 14:06:03 Also, I think we need to make the work engine an interface 14:06:12 any objections to that? 14:06:24 shurley, what's the PR number? 14:06:40 983 14:07:04 #action jmrodri & ernelson: https://github.com/openshift/ansible-service-broker/pull/983 14:07:04 rhallisey: action 14:07:09 I imagine it would be similar to some of what was done here https://github.com/openshift/ansible-service-broker/pull/909 14:07:44 maleck13: Oh yeah, just like that 14:07:48 LOL 14:08:13 shurley: great minds :) 14:09:13 any other open discussion topics 14:09:16 looks like this might need a rebase but this makes broker.go completly unit testable I think 14:09:35 +1 14:09:37 shurley: it at least goes a long way 14:09:50 shurley: rebasing currently :) 14:10:20 I think this plus my pr I could uniti test broker.Provision 14:12:01 that?s all I had rhallisey 14:12:13 thanks shurley & maleck13 14:12:29 I think that's all folks. Thanks for coming today! 14:12:39 #endmeeting From cbrookes at redhat.com Tue Jun 12 15:25:49 2018 From: cbrookes at redhat.com (cbrookes at redhat.com) Date: Tue, 12 Jun 2018 15:25:49 +0000 Subject: [Ansible-service-broker] Invitation: managed shared services and the broker @ Fri Jun 15, 2018 4pm - 5pm (IST) (ansible-service-broker@redhat.com) Message-ID: <00000000000021cc6a056e737bb8@google.com> You have been invited to the following event. Title: managed shared services and the broker https://bluejeans.com/2730432953/ After the community meeting. Setting this up for those interested in learning more and understanding the issues. Would like to outline what we are looking into Discuss whether the automation broker is the right place for the work and also go through some of the ideas around implementation. Get general feedback Issues covering this work: https://github.com/openshift/ansible-service-broker/issues/979 https://github.com/openshift/ansible-service-broker/issues/982 General user story As an operator of a managed service, I want to be able to provision a service in a restricted namespace but allow any user in my cluster to provision a slice of that service without needing to know the specific location or credentials of the service. Roles user story As an operator of a managed service, I would like the option to restrict which users can request a slice of this service based on the roles the user has. When: Fri Jun 15, 2018 4pm ? 5pm Dublin Calendar: ansible-service-broker at redhat.com Who: * cbrookes at redhat.com - organizer * pgough at redhat.com * davmarti at redhat.com * pbrookes at redhat.com * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgyZWE1bjVjaGcgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjY2Jyb29rZXNAcmVkaGF0LmNvbThmNDhjMzgzZGNlZjdmOWEyNjY1Y2MyZDA5MGRmNjc2NjQyNzM2NzY&ctz=Europe%2FDublin&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2769 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2820 bytes Desc: not available URL: From jesusr at redhat.com Fri Jun 15 12:26:38 2018 From: jesusr at redhat.com (jesus m. rodriguez) Date: Fri, 15 Jun 2018 08:26:38 -0400 Subject: [Ansible-service-broker] Invitation: managed shared services and the broker @ Fri Jun 15, 2018 11am - 12pm (EDT) (jesusr@redhat.com) In-Reply-To: <0000000000001cc674056ead46d1@google.com> References: <0000000000001cc674056ead46d1@google.com> Message-ID: <88df6042-6795-4133-a867-03cfa024c1d2@redhat.com> I'm on PTO today, I'll be back on Monday Sincerely, Jesus ?Sent from Blue ? On Jun 15, 2018, 8:22 AM, at 8:22 AM, Craig Brookes wrote: >You have been invited to the following event. > >Title: managed shared services and the broker > >https://bluejeans.com/2730432953/ > >After the community meeting. Setting this up for those interested in >learning more and understanding the issues. > >Would like to outline what we are looking into > > >Discuss whether the automation broker is the right place for the work >and >also go through some of the ideas around implementation. > > >Discuss option of shared service broker > >Get general feedback > > >Issues covering this work: >https://github.com/openshift/ansible-service-broker/issues/979 >https://github.com/openshift/ansible-service-broker/issues/982 > >General user story >As an operator of a managed service, I want to be able to provision a >service in a restricted namespace but allow any user in my cluster to >provision a slice of that service without needing to know the specific > >location or credentials of the service. > >Roles user story >As an operator of a managed service, I would like the option to >restrict >which users can request a slice of this service based on the roles the >user >has. >When: Fri Jun 15, 2018 11am ? 12pm Eastern Time >Calendar: jesusr at redhat.com >Who: > * cbrookes at redhat.com - organizer > * davmarti at redhat.com > * jesusr at redhat.com > * pbrookes at redhat.com > * ansible-service-broker at redhat.com > * pgough at redhat.com > * rhallise at redhat.com > * ernelson at redhat.com > * shurley at redhat.com > >Event details: >https://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgyZWE1bjVjaGcgamVzdXNyQHJlZGhhdC5jb20&tok=MTkjY2Jyb29rZXNAcmVkaGF0LmNvbWRjYzAyYTk3MDEzOTI4YzBmM2Q5OGFlYjZkMjdhNDYwOTMzODM4NjE&ctz=America%2FNew_York&hl=en&es=1 > >Invitation from Google Calendar: https://www.google.com/calendar/ > >You are receiving this email at the account jesusr at redhat.com because >you >are subscribed for invitations on calendar jesusr at redhat.com. > >To stop receiving these emails, please log in to >https://www.google.com/calendar/ and change your notification settings >for >this calendar. > >Forwarding this invitation could allow any recipient to modify your >RSVP >response. Learn more at >https://support.google.com/calendar/answer/37135#forwarding From ernelson at redhat.com Fri Jun 15 13:03:29 2018 From: ernelson at redhat.com (Erik Nelson) Date: Fri, 15 Jun 2018 09:03:29 -0400 Subject: [Ansible-service-broker] Invitation: managed shared services and the broker @ Fri Jun 15, 2018 11am - 12pm (EDT) (jesusr@redhat.com) In-Reply-To: <88df6042-6795-4133-a867-03cfa024c1d2@redhat.com> References: <0000000000001cc674056ead46d1@google.com> <88df6042-6795-4133-a867-03cfa024c1d2@redhat.com> Message-ID: Also on PTO today. On Fri, Jun 15, 2018, 8:26 AM jesus m. rodriguez wrote: > I'm on PTO today, I'll be back on Monday > > Sincerely, > Jesus > > ?Sent from Blue ? > > On Jun 15, 2018, 8:22 AM, at 8:22 AM, Craig Brookes > wrote: > >You have been invited to the following event. > > > >Title: managed shared services and the broker > > > >https://bluejeans.com/2730432953/ > > > >After the community meeting. Setting this up for those interested in > >learning more and understanding the issues. > > > >Would like to outline what we are looking into > > > > > >Discuss whether the automation broker is the right place for the work > >and > >also go through some of the ideas around implementation. > > > > > >Discuss option of shared service broker > > > >Get general feedback > > > > > >Issues covering this work: > >https://github.com/openshift/ansible-service-broker/issues/979 > >https://github.com/openshift/ansible-service-broker/issues/982 > > > >General user story > >As an operator of a managed service, I want to be able to provision a > >service in a restricted namespace but allow any user in my cluster to > >provision a slice of that service without needing to know the specific > > > >location or credentials of the service. > > > >Roles user story > >As an operator of a managed service, I would like the option to > >restrict > >which users can request a slice of this service based on the roles the > >user > >has. > >When: Fri Jun 15, 2018 11am ? 12pm Eastern Time > >Calendar: jesusr at redhat.com > >Who: > > * cbrookes at redhat.com - organizer > > * davmarti at redhat.com > > * jesusr at redhat.com > > * pbrookes at redhat.com > > * ansible-service-broker at redhat.com > > * pgough at redhat.com > > * rhallise at redhat.com > > * ernelson at redhat.com > > * shurley at redhat.com > > > >Event details: > > > https://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgyZWE1bjVjaGcgamVzdXNyQHJlZGhhdC5jb20&tok=MTkjY2Jyb29rZXNAcmVkaGF0LmNvbWRjYzAyYTk3MDEzOTI4YzBmM2Q5OGFlYjZkMjdhNDYwOTMzODM4NjE&ctz=America%2FNew_York&hl=en&es=1 > > > >Invitation from Google Calendar: https://www.google.com/calendar/ > > > >You are receiving this email at the account jesusr at redhat.com because > >you > >are subscribed for invitations on calendar jesusr at redhat.com. > > > >To stop receiving these emails, please log in to > >https://www.google.com/calendar/ and change your notification settings > >for > >this calendar. > > > >Forwarding this invitation could allow any recipient to modify your > >RSVP > >response. Learn more at > >https://support.google.com/calendar/answer/37135#forwarding > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbrookes at redhat.com Fri Jun 15 13:09:12 2018 From: cbrookes at redhat.com (cbrookes at redhat.com) Date: Fri, 15 Jun 2018 13:09:12 +0000 Subject: [Ansible-service-broker] Updated invitation: managed shared services and the broker @ Mon Jun 18, 2018 4pm - 5pm (IST) (ansible-service-broker@redhat.com) Message-ID: <00000000000018cd90056eadec75@google.com> This event has been changed. Title: managed shared services and the broker https://bluejeans.com/2730432953/ After the community meeting. Setting this up for those interested in learning more and understanding the issues. Would like to outline what we are looking into Discuss whether the automation broker is the right place for the work and also go through some of the ideas around implementation. Discuss option of shared service broker Get general feedback Issues covering this work: https://github.com/openshift/ansible-service-broker/issues/979 https://github.com/openshift/ansible-service-broker/issues/982 General user story As an operator of a managed service, I want to be able to provision a service in a restricted namespace but allow any user in my cluster to provision a slice of that service without needing to know the specific location or credentials of the service. Roles user story As an operator of a managed service, I would like the option to restrict which users can request a slice of this service based on the roles the user has. When: Mon Jun 18, 2018 4pm ? 5pm Dublin (changed) Calendar: ansible-service-broker at redhat.com Who: * cbrookes at redhat.com - organizer * pgough at redhat.com * davmarti at redhat.com * pbrookes at redhat.com * ansible-service-broker at redhat.com * jesusr at redhat.com * ernelson at redhat.com * shurley at redhat.com * rhallise at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgyZWE1bjVjaGcgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjY2Jyb29rZXNAcmVkaGF0LmNvbThmNDhjMzgzZGNlZjdmOWEyNjY1Y2MyZDA5MGRmNjc2NjQyNzM2NzY&ctz=Europe%2FDublin&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3400 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3460 bytes Desc: not available URL: From jmatthew at redhat.com Fri Jun 15 13:16:50 2018 From: jmatthew at redhat.com (John Matthews) Date: Fri, 15 Jun 2018 09:16:50 -0400 Subject: [Ansible-service-broker] Updated invitation: managed shared services and the broker @ Mon Jun 18, 2018 4pm - 5pm (IST) (ansible-service-broker@redhat.com) In-Reply-To: <00000000000018cd90056eadec75@google.com> References: <00000000000018cd90056eadec75@google.com> Message-ID: <61419E3F-76D0-4F41-907F-BD8945E5BA6B@redhat.com> FYI the broker team has sprint planning Monday 11-12 est. if I?m converting time zone correct this invite would conflict > On Jun 15, 2018, at 9:09 AM, cbrookes at redhat.com wrote: > > > This event has been changed. > more details ? > managed shared services and the broker > When > Changed: Mon Jun 18, 2018 4pm ? 5pm Dublin > Calendar > ansible-service-broker at redhat.com > Who > ? > cbrookes at redhat.com - organizer > ? > pgough at redhat.com > ? > davmarti at redhat.com > ? > pbrookes at redhat.com > ? > ansible-service-broker at redhat.com > ? > jesusr at redhat.com > ? > ernelson at redhat.com > ? > shurley at redhat.com > ? > rhallise at redhat.com > > https://bluejeans.com/2730432953/ > After the community meeting. Setting this up for those interested in learning more and understanding the issues. > > Would like to outline what we are looking into > > > Discuss whether the automation broker is the right place for the work and also go through some of the ideas around implementation. > > > Discuss option of shared service broker > > Get general feedback > > > Issues covering this work: > https://github.com/openshift/ansible-service-broker/issues/979 > https://github.com/openshift/ansible-service-broker/issues/982 > > General user story > As an operator of a managed service, I want to be able to provision a service in a restricted namespace but allow any user in my cluster to provision a slice of that service without needing to know the specific location or credentials of the service. > > Roles user story > As an operator of a managed service, I would like the option to restrict which users can request a slice of this service based on the roles the user has. > > Going? Yes - Maybe - No more options ? > Invitation from Google Calendar > > You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. > > To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. > > Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More. > > > > _______________________________________________ > 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 cbrookes at redhat.com Fri Jun 15 13:51:53 2018 From: cbrookes at redhat.com (cbrookes at redhat.com) Date: Fri, 15 Jun 2018 13:51:53 +0000 Subject: [Ansible-service-broker] Updated invitation: managed shared services and the broker @ Wed Jun 20, 2018 4pm - 5pm (IST) (ansible-service-broker@redhat.com) Message-ID: <000000000000b37377056eae845e@google.com> This event has been changed. Title: managed shared services and the broker https://bluejeans.com/2730432953/ After the community meeting. Setting this up for those interested in learning more and understanding the issues. Would like to outline what we are looking into Discuss whether the automation broker is the right place for the work and also go through some of the ideas around implementation. Discuss option of shared service broker Get general feedback Issues covering this work: https://github.com/openshift/ansible-service-broker/issues/979 https://github.com/openshift/ansible-service-broker/issues/982 General user story As an operator of a managed service, I want to be able to provision a service in a restricted namespace but allow any user in my cluster to provision a slice of that service without needing to know the specific location or credentials of the service. Roles user story As an operator of a managed service, I would like the option to restrict which users can request a slice of this service based on the roles the user has. When: Wed Jun 20, 2018 4pm ? 5pm Dublin (changed) Calendar: ansible-service-broker at redhat.com Who: * cbrookes at redhat.com - organizer * pgough at redhat.com * davmarti at redhat.com * pbrookes at redhat.com * ansible-service-broker at redhat.com * jesusr at redhat.com * ernelson at redhat.com * shurley at redhat.com * rhallise at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgyZWE1bjVjaGcgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjY2Jyb29rZXNAcmVkaGF0LmNvbThmNDhjMzgzZGNlZjdmOWEyNjY1Y2MyZDA5MGRmNjc2NjQyNzM2NzY&ctz=Europe%2FDublin&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3400 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3460 bytes Desc: not available URL: From cbrookes at redhat.com Fri Jun 15 13:52:06 2018 From: cbrookes at redhat.com (Craig Brookes) Date: Fri, 15 Jun 2018 14:52:06 +0100 Subject: [Ansible-service-broker] Updated invitation: managed shared services and the broker @ Mon Jun 18, 2018 4pm - 5pm (IST) (ansible-service-broker@redhat.com) In-Reply-To: <61419E3F-76D0-4F41-907F-BD8945E5BA6B@redhat.com> References: <00000000000018cd90056eadec75@google.com> <61419E3F-76D0-4F41-907F-BD8945E5BA6B@redhat.com> Message-ID: Thanks for the heads up. 3rd time lucky hopefully On Fri, Jun 15, 2018 at 2:16 PM, John Matthews wrote: > FYI the broker team has sprint planning Monday 11-12 est. if I?m > converting time zone correct this invite would conflict > > > > On Jun 15, 2018, at 9:09 AM, cbrookes at redhat.com wrote: > > *This event has been changed.* > more details ? > > managed shared services and the broker > > *When* > *Changed: *Mon Jun 18, 2018 4pm ? 5pm Dublin > *Calendar* > ansible-service-broker at redhat.com > *Who* > ? > cbrookes at redhat.com - organizer > ? > pgough at redhat.com > ? > davmarti at redhat.com > ? > pbrookes at redhat.com > ? > ansible-service-broker at redhat.com > ? > jesusr at redhat.com > ? > ernelson at redhat.com > ? > shurley at redhat.com > ? > rhallise at redhat.com > > https://bluejeans.com/2730432953/ > > > After the community meeting. Setting this up for those interested in > learning more and understanding the issues. > > Would like to outline what we are looking into > > > Discuss whether the automation broker is the right place for the work and > also go through some of the ideas around implementation. > > > Discuss option of shared service broker > > Get general feedback > > > Issues covering this work: > https://github.com/openshift/ansible-service-broker/issues/979 > > https://github.com/openshift/ansible-service-broker/issues/982 > > > General user story > As an operator of a managed service, I want to be able to provision a > service in a restricted namespace but allow any user in my cluster to > provision a slice of that service without needing to know the specific > location or credentials of the service. > > Roles user story > As an operator of a managed service, I would like the option to restrict > which users can request a slice of this service based on the roles the user > has. > > Going? *Yes > > - Maybe > > - No > * > more options ? > > > Invitation from Google Calendar > > You are receiving this courtesy email at the account > ansible-service-broker at redhat.com because you are an attendee of this > event. > > To stop receiving future updates for this event, decline this event. > Alternatively you can sign up for a Google account at > https://www.google.com/calendar/ and control your notification settings > for your entire calendar. > > Forwarding this invitation could allow any recipient to modify your RSVP > response. Learn More > . > > > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > -- Craig Brookes RHMAP @maleck13 Github -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Tue Jun 19 13:19:25 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Tue, 19 Jun 2018 09:19:25 -0400 Subject: [Ansible-service-broker] No IRC meeting today Message-ID: I have a conflict today, so I'm going to cancel the meeting for this week. See you online, - Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbrookes at redhat.com Wed Jun 20 08:19:30 2018 From: cbrookes at redhat.com (cbrookes at redhat.com) Date: Wed, 20 Jun 2018 08:19:30 +0000 Subject: [Ansible-service-broker] Updated invitation: managed shared services and the broker @ Wed Jun 20, 2018 4pm - 5pm (IST) (ansible-service-broker@redhat.com) Message-ID: <00000000000040e26b056f0e75d8@google.com> This event has been changed. Title: managed shared services and the broker https://bluejeans.com/2730432953/ After the community meeting. Setting this up for those interested in learning more and understanding the issues. Would like to outline what we are looking into Discuss whether the automation broker is the right place for the work and also go through some of the ideas around implementation. Discuss option of a separate shared service broker using bundle-lib Get general feedback Issues covering this work: https://github.com/openshift/ansible-service-broker/issues/979 https://github.com/openshift/ansible-service-broker/issues/982 General user story As an operator of a managed service, I want to be able to provision a service in a restricted namespace but allow any user in my cluster to provision a slice of that service without needing to know the specific location or credentials of the service. Roles user story As an operator of a managed service, I would like the option to restrict which users can request a slice of this service based on the roles the user has. (changed) When: Wed Jun 20, 2018 4pm ? 5pm Dublin Calendar: ansible-service-broker at redhat.com Who: * cbrookes at redhat.com - organizer * pgough at redhat.com * davmarti at redhat.com * pbrookes at redhat.com * ansible-service-broker at redhat.com * jesusr at redhat.com * ernelson at redhat.com * shurley at redhat.com * rhallise at redhat.com - optional * mhrivnak at redhat.com - optional Event details: https://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgyZWE1bjVjaGcgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjY2Jyb29rZXNAcmVkaGF0LmNvbThmNDhjMzgzZGNlZjdmOWEyNjY1Y2MyZDA5MGRmNjc2NjQyNzM2NzY&ctz=Europe%2FDublin&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account ansible-service-broker at redhat.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3556 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3618 bytes Desc: not available URL: From dzager at redhat.com Wed Jun 20 20:54:04 2018 From: dzager at redhat.com (David Zager) Date: Wed, 20 Jun 2018 16:54:04 -0400 Subject: [Ansible-service-broker] Sprint 150 Release Notes Message-ID: There is now a `make deploy` target that will build the broker and the broker-apb before deploying the broker into a running cluster. You should check it out. If you want a specific version of the broker (ie. ansible-service-broker-1.3.4-1), the broker-apb is there for you here too. Simply update the install.yaml to use ansible-service-broker-1.3.4-1. Bugs - Bug 1578319 - send _apb* parameters to unbind (#960) - Bug 1581580 - skip if bind instance does not have credentials (#964) - Bug 1581580 - skip if bind instance does not have credentials (#965) - Bug 1583064 - missing action causes many sandboxes (#972) - Bug 1585649 - wait group should be added to before go function is kicked off (#977) Other Enhancements - Bump version for next release (#955) - dep prune vendor (#962) - Switch from go-logging to logrus (#961) - Add requested parameters when not in existing service instance (#935) - add v3.10 install method to README (#967) - Add Broker APB source to project (#939) - Make ci should not do deployment (#975) - Travis should run only for master/release branches (#978) - Bundle lib 0.2 (#946) - reformat tables to be readable without rendering (#980) - Bump bundle-lib to 0.2.3 (#981) - ensure initial state set when job started. reduce repition in job definitions. Allow jobs to be mocked out at broker level (#909) - Tie together container images of broker & broker-apb (#986) - Fix deployment stage (#987) - Remove tag from deployment (#988) - adding unit tests for broker package (#983) - Pass in namespace to runtime (#991) - Add hostname to test scripts (#985) - Use travis_tag on tag builds (#993) - Login for deploy on tag (#994) -------------- next part -------------- An HTML attachment was scrubbed... URL: From alpatel at redhat.com Tue Jun 26 19:30:40 2018 From: alpatel at redhat.com (Alaykumar Patel) Date: Tue, 26 Jun 2018 15:30:40 -0400 Subject: [Ansible-service-broker] Request for comments on spec-reconciliation proposal Message-ID: Hello everyone, I have submitted a pr here that adds a spec reconciliation proposal document. The proposal lists possible approaches that broker can take for different issues. Please comment on the preferable approach, if possible by 5:00 pm EST Wednesday. It also lists few ideas that were discussed that would solve problems immediately related to spec reconciliation. Thanks, Alay -------------- next part -------------- An HTML attachment was scrubbed... URL: