From jesusr at redhat.com Tue Oct 2 14:01:59 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 02 Oct 2018 10:01:59 -0400 Subject: [Ansible-service-broker] Automation Broker IRC meeting October 2, 2018 Message-ID: <39dbf7ed9ab3b4785b5c223cc75e2986e0f6c25a.camel@redhat.com> Here is this weeks IRC meeting summary. You can checkout the full logs of all the meetings since May in github: https://github.com/openshift/ansible-service-broker/tree/master/docs/meetings/2018 ================================= #asbroker: Automation broker 10/2 ================================= Meeting started by jmrodri at 13:31:54 UTC. The full logs are available at asbroker/2018/asbroker.2018-10-02-13.31.log.html . Meeting summary --------------- * News (jmrodri, 13:33:11) * bundle-lib release 0.2.14 was released on Sept 7, 2018. (jmrodri, 13:34:14) * LINK: https://github.com/automationbroker/bundle-lib/releases/tag/0.2.14 (jmrodri, 13:34:23) * automation-broker 1.3.19-1 released Sept 20, 2018 (jmrodri, 13:35:19) * 1.3 is now in release-1.3 branch (jmrodri, 13:35:33) * master is now the 4.0 tree (jmrodri, 13:35:40) * work has been done on operators for the automation broker and the template broker. (jmrodri, 13:39:30) * apb directory moved to ansible_role (jmrodri, 13:39:39) * new make target build-operator (jmrodri, 13:39:57) * catasb users can flip some switches to get OLM cluster (jmrodri, 13:40:16) * Previous Actions (jmrodri, 13:41:10) * none to review, moving along (jmrodri, 13:41:15) * bugs/issues triage (jmrodri, 13:41:20) * bundle-lib has 1 new issue (jmrodri, 13:41:33) * Make `Organization` registry config section a list (jmrodri, 13:41:42) * LINK: https://github.com/automationbroker/bundle-lib/issues/166 (jmrodri, 13:41:49) * ACTION: jmrodri add bundle-lib issue to a release target (jmrodri, 13:43:13) * automation broker has 4 new issues (jmrodri, 13:43:40) * APIV2 adapter should accept token with name "token" (jmrodri, 13:43:57) * LINK: https://github.com/openshift/ansible-service-broker/issues/1097 (jmrodri, 13:44:03) * Documentation recommendation to use --routing-suffix/--hostname with oc cluster up is broken for Mac (jmrodri, 13:45:59) * LINK: https://github.com/openshift/ansible-service-broker/issues/1087 (jmrodri, 13:46:12) * ACTION: jmrodri take issue 1087 on broker side (jmrodri, 13:47:10) * minishift can't start using origin 3.10 + OAB (jmrodri, 13:47:27) * LINK: https://github.com/openshift/ansible-service-broker/issues/1076 (jmrodri, 13:47:34) * ACTION: ernelson to look at minishift issue against broker (1076) (jmrodri, 13:50:15) * apb CLI command returns status 404 for all sub commands (jmrodri, 13:50:42) * LINK: https://github.com/openshift/ansible-service-broker/issues/1071 (jmrodri, 13:50:48) * ACTION: dymurray look into issue 1071 (jmrodri, 13:52:01) * RFE: add rate limiter to the broker?s API handler (jmrodri, 13:52:14) * LINK: https://github.com/openshift/ansible-service-broker/issues/1098 (jmrodri, 13:52:21) * ACTION: jmrodri write up proposal for rate limiter feature (jmrodri, 13:53:19) * Right now there are 28 upstream issues against the broker marked for release 1.4 (aka OCP 4.0) (jmrodri, 13:54:00) * Features (jmrodri, 13:54:23) * None at the moment (jmrodri, 13:54:32) * Open Discussion (jmrodri, 13:54:39) Meeting ended at 13:57:04 UTC. Action Items ------------ * jmrodri add bundle-lib issue to a release target * jmrodri take issue 1087 on broker side * ernelson to look at minishift issue against broker (1076) * dymurray look into issue 1071 * jmrodri write up proposal for rate limiter feature Action Items, by person ----------------------- * dymurray * dymurray look into issue 1071 * ernelson * ernelson to look at minishift issue against broker (1076) * jmrodri * jmrodri add bundle-lib issue to a release target * jmrodri take issue 1087 on broker side * jmrodri write up proposal for rate limiter feature * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jmrodri (69) * brokerbot (44) * ernelson (10) * dymurray (9) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From cmoullia at redhat.com Mon Oct 22 13:17:21 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 22 Oct 2018 15:17:21 +0200 Subject: [Ansible-service-broker] Can't delete a serviceInstance on okd 3.10 Message-ID: Hi. We can't delete a serviceInstance on okd 3.10 where ASB has been deployed using Openshift Ansible playbook Here is the response's returned by the broker when we do a "oc delete serviceinstance" - https://goo.gl/QCvpuD How can I resolve that ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Mon Oct 22 13:52:11 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Mon, 22 Oct 2018 15:52:11 +0200 Subject: [Ansible-service-broker] Can't delete a serviceInstance on okd 3.10 In-Reply-To: References: Message-ID: As there are issues with github, here is the content published on another site https://pastebin.com/PaSxnMn7 On Mon, Oct 22, 2018 at 3:17 PM Charles Moulliard wrote: > Hi. > > We can't delete a serviceInstance on okd 3.10 where ASB has been deployed > using Openshift Ansible playbook > > Here is the response's returned by the broker when we do a "oc delete > serviceinstance" - https://goo.gl/QCvpuD > > How can I resolve that ? > > Regards > > Charles > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Tue Oct 23 07:22:21 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 23 Oct 2018 09:22:21 +0200 Subject: [Ansible-service-broker] Best approach to delete serviceInstance created/owned by a CRD Message-ID: Hi, We have developed a CRD responsible, with the help of an operator, to create k8s resources such as serviceInstance, serviceBinding and secret. When the serviceInstance, serviceBinding are created, we add ownerReferences to allow the CRD to do the garbage collection of such resources. Example oc get serviceinstance/my-postgresql-db -o yaml apiVersion: servicecatalog.k8s.io/v1beta1 kind: ServiceInstance metadata: creationTimestamp: 2018-10-22T16:23:16Z deletionGracePeriodSeconds: 0 deletionTimestamp: 2018-10-23T07:11:42Z finalizers: - kubernetes-incubator/service-catalog generation: 2 labels: app: my-spring-boot-service name: my-spring-boot-service name: my-postgresql-db namespace: my-spring-app ownerReferences: - apiVersion: component.k8s.io/v1alpha1 blockOwnerDeletion: true controller: true kind: Component name: my-spring-boot-service uid: c7aee0ee-d616-11e8-9b27-08002710b4d8 ... Unfortunately, when we delete the CRD, the secret is deleted but not the ServiceInstance & serviceBinding which are marked for deletion The status mentions such info for the serviceInstance - lastTransitionTime: 2018-10-23T07:00:04Z message: All associated ServiceBindings must be removed before this ServiceInstance can be deleted reason: DeprovisionBlockedByExistingCredentials status: "False" type: Ready and for the serviceBinding Warning UnbindCallFailed 3m (x63 over 18m) service-catalog-controller-manager Error unbinding from ServiceInstance "my-spring-app/my-postgresql-db" of ClusterServiceClass (K8S: "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql-apb") at ClusterServiceBroker "openshift-automation-service-broker": Status: 403; ErrorMessage: ; Description: User does not have sufficient permissions; ResponseError: okd version used : 3.11 Question : - Can we use "ownerReferences" to delete from a CRD the service's k8s resources ? - What is the alternative if we can use "ownerReferences" ? - How can we force to delete such k8s resources ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From shurley at redhat.com Tue Oct 23 12:19:07 2018 From: shurley at redhat.com (Shawn Hurley) Date: Tue, 23 Oct 2018 08:19:07 -0400 Subject: [Ansible-service-broker] Best approach to delete serviceInstance created/owned by a CRD In-Reply-To: References: Message-ID: I think I would question using an operator to create serviceInstances and serviyBindings. I think doing it this way has one too many abstraction and is not going to play super nice. Also, I assume the problem is the broker your using requires the secret to do some cleanup and/unbind the user? In this case I would use owner references but I would use a finalized to handle the clean up. This means deleting the binding then the instance then the secret in that order to make sure everything goes well. As for force deleting, I don?t think that any code should be doing that automatically. Force delete should be a user action. To do this you delete the finalizer kubernetes-incubator/service-catalog on the service binding and the service instance. Thanks, Shawn Hurley On Tue, Oct 23, 2018 at 3:23 AM Charles Moulliard wrote: > Hi, > > We have developed a CRD responsible, with the help of an operator, to > create k8s resources such as serviceInstance, serviceBinding and secret. > When the serviceInstance, serviceBinding are created, we add > ownerReferences to allow the CRD to do the garbage collection of such > resources. > > Example > > oc get serviceinstance/my-postgresql-db -o yaml > apiVersion: servicecatalog.k8s.io/v1beta1 > kind: ServiceInstance > metadata: > creationTimestamp: 2018-10-22T16:23:16Z > deletionGracePeriodSeconds: 0 > deletionTimestamp: 2018-10-23T07:11:42Z > finalizers: > - kubernetes-incubator/service-catalog > generation: 2 > labels: > app: my-spring-boot-service > name: my-spring-boot-service > name: my-postgresql-db > namespace: my-spring-app > ownerReferences: > - apiVersion: component.k8s.io/v1alpha1 > blockOwnerDeletion: true > controller: true > kind: Component > name: my-spring-boot-service > uid: c7aee0ee-d616-11e8-9b27-08002710b4d8 > ... > > Unfortunately, when we delete the CRD, the secret is deleted but not the > ServiceInstance & serviceBinding which are marked for deletion > > The status mentions such info for the serviceInstance > > - lastTransitionTime: 2018-10-23T07:00:04Z > message: All associated ServiceBindings must be removed before this > ServiceInstance > can be deleted > reason: DeprovisionBlockedByExistingCredentials > status: "False" > type: Ready > > and for the serviceBinding > > Warning UnbindCallFailed 3m (x63 over 18m) > service-catalog-controller-manager Error unbinding from ServiceInstance > "my-spring-app/my-postgresql-db" of ClusterServiceClass (K8S: > "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql-apb") at > ClusterServiceBroker "openshift-automation-service-broker": Status: 403; > ErrorMessage: ; Description: User does not have sufficient > permissions; ResponseError: > > okd version used : 3.11 > > Question : > - Can we use "ownerReferences" to delete from a CRD the service's k8s > resources ? > - What is the alternative if we can use "ownerReferences" ? > - How can we force to delete such k8s resources ? > > 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 Oct 23 13:16:41 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Tue, 23 Oct 2018 15:16:41 +0200 Subject: [Ansible-service-broker] Best approach to delete serviceInstance created/owned by a CRD In-Reply-To: References: Message-ID: On Tue, Oct 23, 2018 at 2:19 PM Shawn Hurley wrote: > I think I would question using an operator to create serviceInstances and > serviyBindings. I think doing it this way has one too many abstraction and > is not going to play super nice. > > Also, I assume the problem is the broker your using requires the secret to > do some cleanup and/unbind the user? > >From what I have been able to investigate this morning, the serviceBindings (which contains a reference to a ServiceInstance) must be first deleted before to delete the ServiceInstance. When we delete the serviceBindings, then all the secret referenced (= having a ownerReference to the serviceBinding) will be then deleted. By consequence, I have implemented the same logic within the operator if a CRD is deleted, then we delete the serviceBindings linked to the serviceInstance name defined within the CRD and finally the serviceInstance [1] [1] https://goo.gl/WtNJ8v > In this case I would use owner references but I would use a finalized to > handle the clean up. This means deleting the binding then the instance then > the secret in that order to make sure everything goes well. > To be able to use owner references, then we need a way to define the order, otherwise the resources will not be necessarily deleted according tothis order : serviceBindings > secrets > serviceInstance but instead in parallel serviceInstance, serviceBindings,... > > As for force deleting, I don?t think that any code should be doing that > automatically. Force delete should be a user action. To do this you delete > the finalizer kubernetes-incubator/service-catalog on the service binding > and the service instance. > > Thanks, > > Shawn Hurley > > On Tue, Oct 23, 2018 at 3:23 AM Charles Moulliard > wrote: > >> Hi, >> >> We have developed a CRD responsible, with the help of an operator, to >> create k8s resources such as serviceInstance, serviceBinding and secret. >> When the serviceInstance, serviceBinding are created, we add >> ownerReferences to allow the CRD to do the garbage collection of such >> resources. >> >> Example >> >> oc get serviceinstance/my-postgresql-db -o yaml >> apiVersion: servicecatalog.k8s.io/v1beta1 >> kind: ServiceInstance >> metadata: >> creationTimestamp: 2018-10-22T16:23:16Z >> deletionGracePeriodSeconds: 0 >> deletionTimestamp: 2018-10-23T07:11:42Z >> finalizers: >> - kubernetes-incubator/service-catalog >> generation: 2 >> labels: >> app: my-spring-boot-service >> name: my-spring-boot-service >> name: my-postgresql-db >> namespace: my-spring-app >> ownerReferences: >> - apiVersion: component.k8s.io/v1alpha1 >> blockOwnerDeletion: true >> controller: true >> kind: Component >> name: my-spring-boot-service >> uid: c7aee0ee-d616-11e8-9b27-08002710b4d8 >> ... >> >> Unfortunately, when we delete the CRD, the secret is deleted but not the >> ServiceInstance & serviceBinding which are marked for deletion >> >> The status mentions such info for the serviceInstance >> >> - lastTransitionTime: 2018-10-23T07:00:04Z >> message: All associated ServiceBindings must be removed before this >> ServiceInstance >> can be deleted >> reason: DeprovisionBlockedByExistingCredentials >> status: "False" >> type: Ready >> >> and for the serviceBinding >> >> Warning UnbindCallFailed 3m (x63 over 18m) >> service-catalog-controller-manager Error unbinding from ServiceInstance >> "my-spring-app/my-postgresql-db" of ClusterServiceClass (K8S: >> "1dda1477cace09730bd8ed7a6505607e" ExternalName: "dh-postgresql-apb") at >> ClusterServiceBroker "openshift-automation-service-broker": Status: 403; >> ErrorMessage: ; Description: User does not have sufficient >> permissions; ResponseError: >> >> okd version used : 3.11 >> >> Question : >> - Can we use "ownerReferences" to delete from a CRD the service's k8s >> resources ? >> - What is the alternative if we can use "ownerReferences" ? >> - How can we force to delete such k8s resources ? >> >> 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 rhallise at redhat.com Wed Oct 24 22:14:42 2018 From: rhallise at redhat.com (rhallise at redhat.com) Date: Wed, 24 Oct 2018 22:14:42 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Every 2 weeks from 9:30am to 10:30am on Tuesday (EDT) (ansible-service-broker@redhat.com) Message-ID: <000000000000212e8d057900d0a4@google.com> This event has been changed. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Every 2 weeks from 9:30am to 10:30am on Tuesday Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=Mmt0NjY4czJ2dm85aHJpcHY2Z25udGp2bDggYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbTRjODViMTk1MTVlMmJkNTY4ZWQ4OWVhYWI1MTAzZjBkZWVmZmNhYjE&ctz=America%2FNew_York&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: 1767 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1807 bytes Desc: not available URL: From fabrice.chaillou at orange.com Fri Oct 26 08:30:41 2018 From: fabrice.chaillou at orange.com (fabrice.chaillou at orange.com) Date: Fri, 26 Oct 2018 08:30:41 +0000 Subject: [Ansible-service-broker] Openshift Ansible Broker (AOB) : How to manage database service outside Openshift ? Message-ID: <32756_1540542641_5BD2D0B1_32756_41_1_97DAF141B356734CA07E147A87355C808FF07CDB@OPEXCLILMA2.corporate.adroot.infra.ftgroup> Hello, I saw this video yesterday about the use of Ansible Service Broker to provision database service on VM servers (outside Openshift). https://www.redhat.com/en/about/videos/how-use-openshift-ansible-service-broker-for-infrastructure-automation But I see anything about it in your official Openshift documentation. https://docs.openshift.com/container-platform/3.11/apb_devel/index.html I don't understand. Best Regards. Fabrice CHAILLOU Database Expert Leader DBEI Team Manager Orange/TGI/OLS/IVA/IAC/DBEI Phone : +33 1.61.38.44.43 Site OLS Guyancourt - Room 2B21 fabrice.chaillou at orange.com DBEI Mail : DL OLS DBEI DBEI Site : http://dbei.si.fr.intraorange/ NoSQL Plazza : https://plazza.orange.com/groups/nosql _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmatthew at redhat.com Fri Oct 26 13:26:31 2018 From: jmatthew at redhat.com (John Matthews) Date: Fri, 26 Oct 2018 09:26:31 -0400 Subject: [Ansible-service-broker] Openshift Ansible Broker (AOB) : How to manage database service outside Openshift ? In-Reply-To: <32756_1540542641_5BD2D0B1_32756_41_1_97DAF141B356734CA07E147A87355C808FF07CDB@OPEXCLILMA2.corporate.adroot.infra.ftgroup> References: <32756_1540542641_5BD2D0B1_32756_41_1_97DAF141B356734CA07E147A87355C808FF07CDB@OPEXCLILMA2.corporate.adroot.infra.ftgroup> Message-ID: Hi Fabrice, What kind of information would help you? The key concept to take-away from APBs and the Automation Broker is that it allows you a path to publish your Ansible code to a user on OpenShift via the Service Catalog. In the example you ask about, provisioning a VM that is off cluster you would need to write an ansible playbook/role that does the work you want of provisioning on a VM. Once you have a playbook/role doing the work you want, you would then build that into an APB, noting the parameters you want published to an end-user, how you want to handle inventory/credentials/etc. Think of the Automation Broker/APB as the path of taking your work and publishing it to an end user on OpenShift. I'd recommend taking a look at the below docs: Getting Started APB Developer Guide As you run into questions you can reach us on freenode #asbroker or this list Best, On Fri, Oct 26, 2018 at 8:44 AM wrote: > Hello, > > > > I saw this video yesterday about the use of Ansible Service Broker to > provision database service on VM servers (outside Openshift). > > > https://www.redhat.com/en/about/videos/how-use-openshift-ansible-service-broker-for-infrastructure-automation > > > > But I see anything about it in your official Openshift documentation. > > https://docs.openshift.com/container-platform/3.11/apb_devel/index.html > > > > I don?t understand. > > > > Best Regards. > > > > *Fabrice CHAILLOU* > > *Database Expert Leader* > > *DBEI Team Manager* > > Orange/TGI/OLS/IVA/IAC/DBEI > > Phone : +33 1.61.38.44.43 > > Site OLS Guyancourt ? Room 2B21 > > *fabrice.chaillou at orange.com * > > DBEI Mail : *DL OLS DBEI * > > DBEI Site : http://dbei.si.fr.intraorange/ > > NoSQL Plazza : https://plazza.orange.com/groups/nosql > > > > > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > _______________________________________________ > 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 jesusr at redhat.com Tue Oct 30 01:00:29 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 30 Oct 2018 01:00:29 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Every 2 weeks from 10am to 10:30am on Tuesday (EDT) (ansible-service-broker@redhat.com) Message-ID: <000000000000414311057967b64b@google.com> This event has been changed. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Every 2 weeks from 10am to 10:30am on Tuesday Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * jesusr at redhat.com - creator * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=Z2M2NWo1YzFtNDY2c242MjFoczM3dG9ocjggYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbThmZjUyMzE3ZjZiYjY5MjhjZWUxZmJlYjZiNTQzNTAzMjc4ZmUxNjY&ctz=America%2FNew_York&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: 1651 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1688 bytes Desc: not available URL: From jesusr at redhat.com Tue Oct 30 01:00:29 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 30 Oct 2018 01:00:29 +0000 Subject: [Ansible-service-broker] Updated invitation: Automation Broker IRC meeting @ Every 2 weeks from 9:30am to 10:30am on Tuesday from Tue Aug 21 to Mon Oct 29 (EDT) (ansible-service-broker@redhat.com) Message-ID: <00000000000040becf057967b63e@google.com> This event has been changed. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Every 2 weeks from 9:30am to 10:30am on Tuesday from Tue Aug 21 to Mon Oct 29 Eastern Time - New York (changed) Calendar: ansible-service-broker at redhat.com Who: * rhallise at redhat.com - organizer * ccpeng-team * ansible-service-broker at redhat.com Event details: https://www.google.com/calendar/event?action=VIEW&eid=Mmt0NjY4czJ2dm85aHJpcHY2Z25udGp2bDggYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbTRjODViMTk1MTVlMmJkNTY4ZWQ4OWVhYWI1MTAzZjBkZWVmZmNhYjE&ctz=America%2FNew_York&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: 1790 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 1830 bytes Desc: not available URL: From jesusr at redhat.com Tue Oct 30 01:03:18 2018 From: jesusr at redhat.com (Jesus Rodriguez) Date: Mon, 29 Oct 2018 21:03:18 -0400 Subject: [Ansible-service-broker] Broker community meeting time changed Message-ID: Over the past few meetings we've only needed 30 minutes to host the meeting. Our team has a conflict for the first half hour and instead of canceling I decided to shift it to 10-10:30am ET. Sincerely, jesus ?Sent from BlueMail ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesusr at redhat.com Tue Oct 30 14:17:03 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 30 Oct 2018 10:17:03 -0400 Subject: [Ansible-service-broker] Automation Broker IRC meeting logs Message-ID: <729e510baf03de662d4db160e35d34b39146b666.camel@redhat.com> You can find all of the meeting logs in the ansible-service-broker repo in the docs/meetings directory: https://github.com/openshift/ansible-service-broker/tree/master/docs/meetings/2018 ======================================== #asbroker: Automation Broker IRC meeting ======================================== Meeting started by jmrodri at 14:03:02 UTC. The full logs are available at asbroker/2018/asbroker.2018-10-30-14.03.log.html . Meeting summary --------------- * Attendance (jmrodri, 14:03:09) * News (jmrodri, 14:04:22) * Automation Broker IRC meeting time change, it will not be from 10:00am ET to 10:30am ET. (jmrodri, 14:04:50) * bundle-lib release 0.2.15 and 0.1.9 (jmrodri, 14:05:44) * LINK: https://github.com/automationbroker/bundle-lib/releases/tag/0.2.15 (jmrodri, 14:05:55) * LINK: https://github.com/automationbroker/bundle-lib/releases/tag/0.1.9 (jmrodri, 14:06:03) * automation-broker 1.4.2-1 released 10/25 (jmrodri, 14:06:35) * Fixed a network policy bug in release 1.1 (OCP 3.9), 1.2 (OCP 3.10), 1.3 (OCP 3.11), and master (4.0) (jmrodri, 14:06:47) * Review Previous Actions (jmrodri, 14:07:21) * jmrodri add bundle-lib issue to a release target - NO CHANGE (jmrodri, 14:07:47) * jmrodri take issue 1087 on broker side - NO CHANGE (jmrodri, 14:07:54) * ernelson to look at minishift issue against broker (1076) - NO CHANGE (jmrodri, 14:08:02) * dymurray look into issue 1071 - NO CHANGE (jmrodri, 14:08:09) * jmrodri write up proposal for rate limiter feature - NO CHANGE (jmrodri, 14:08:15) * Bugs/Issue Triage (jmrodri, 14:08:32) * there were no new issues that came in for bundle-lib (jmrodri, 14:08:46) * automation broker has 1 new issue (jmrodri, 14:08:56) * Broker ansible locks up determining if local_openshift_enabled (jmrodri, 14:09:03) * LINK: https://github.com/openshift/ansible-service-broker/issues/1105 (jmrodri, 14:09:12) * LINK: https://github.com/openshift/ansible-service-broker/issues?q=is%3Aissue+is%3Aopen+label%3A%223.12+%7C+release-1.4%22 (jmrodri, 14:10:19) * ACTION: jmrodri close old broker issues (jmrodri, 14:10:46) * Open Discussion (jmrodri, 14:11:17) * Github found a security vulnerability. I would think we should remove asbcli from the repo to fix this. It?s not used by anything anymore. (jmrodri, 14:11:25) Meeting ended at 14:12:48 UTC. Action Items ------------ * jmrodri close old broker issues Action Items, by person ----------------------- * jmrodri * jmrodri close old broker issues * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jmrodri (37) * brokerbot (28) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From jesusr at redhat.com Tue Oct 30 14:25:15 2018 From: jesusr at redhat.com (jesusr at redhat.com) Date: Tue, 30 Oct 2018 10:25:15 -0400 Subject: [Ansible-service-broker] Removing asbcli Message-ID: <676c2addc44e085f57d25c17de2a4eda9e916116.camel@redhat.com> Github found a vulnerability with the version of the python requests library used by asbcli. Instead of trying to make asbcli work with a new python requests I opted to simply delete asbcli. If you object to this please comment on the PR explaining why you would like to keep it. If no one objects by Tuesday November 6th, I will merge the PR. The vulnerability report can be found: https://github.com/openshift/ansible-service-broker/network/alert/scripts/asbcli/requirements.txt/requests/open The PR can be found here: https://github.com/openshift/ansible-service-broker/pull/1125 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 | +---------------------------------------------+