From cmoullia at redhat.com Thu Mar 1 05:39:11 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 1 Mar 2018 06:39:11 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: On Thu, Mar 1, 2018 at 12:42 AM, Shawn Hurley wrote: > Hi Charles, > > v3.7 should not be attempting to anything with network policies, can you > please double check the deployment config and tell us the version of the > image that is being deployed. > docker image used is : ansibleplaybookbundle/origin-ansible-service-broker:v3.7 > If it is 3.7 then we have another issue that we will need to solve. > > ansible_service_broker_image_tag should override the tag value, if that > is not working then we will need to do a deeper dive on the > openshift-ansible code. > > If you would like to just ?work around? this then you could add a cluster > role binding and role to grant access to the asb service account to > manipulate the network policies. > > Regards, > > Shawn Hurley > > On Feb 28, 2018, at 3:44 PM, Charles Moulliard > wrote: > > Hi, > > There is still an issue with the ansible playbook installing ASB on > openshift 3.7 > When the inventory is configured using these parameters > > git clone -b release-3.7 git at github.com:openshift/openshift-ansible.git > > openshift_enable_service_catalog=true > ansible_service_broker_registry_whitelist=['.*-apb$'] > ansible_service_broker_image_tag=v3.7 > > then, the following error is reported within the APB pod during > serviceinstance creation > > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d > [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy > object - User "system:serviceaccount:openshift-ansible-service-broker:asb" > cannot create networkpolicies.networking.k8s.io > in the namespace "project31": > User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot > create networkpolicies.networking.k8s.io > in project "project31" (post > networkpolicies.networking.k8s.io > )* > project "project31" (post networkpolicies.networking.k8s.io) > > As you can see, the clusterrole of asb-auth is still missing the following > info > https://goo.gl/HfJnj8 > > Can somebody fix the error please for ansible openshift 3.7 ? > > 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 Thu Mar 1 05:40:12 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 1 Mar 2018 06:40:12 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: I confirm that version 3.7 has been installed https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018-03-01%2006.39.40.png?dl=0 On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson wrote: > Charles, you guys are deploying upstream origin with > openshift-ansible? We discovered today thanks to your report that the > upstream openshift-ansible code was configured to default to "latest" > broker images, which is our 3.9 image. I will see if I can reproduce > your issue as well. > > +1 to shurley's comment, we have to confirm what version of the image > you are running, via tag. > > On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley wrote: > > Hi Charles, > > > > v3.7 should not be attempting to anything with network policies, can you > > please double check the deployment config and tell us the version of the > > image that is being deployed. If it is 3.7 then we have another issue > that > > we will need to solve. > > > > ansible_service_broker_image_tag should override the tag value, if that > is > > not working then we will need to do a deeper dive on the > openshift-ansible > > code. > > > > If you would like to just ?work around? this then you could add a cluster > > role binding and role to grant access to the asb service account to > > manipulate the network policies. > > > > Regards, > > > > Shawn Hurley > > > > On Feb 28, 2018, at 3:44 PM, Charles Moulliard > wrote: > > > > Hi, > > > > There is still an issue with the ansible playbook installing ASB on > > openshift 3.7 > > When the inventory is configured using these parameters > > > > git clone -b release-3.7 git at github.com:openshift/openshift-ansible.git > > > > openshift_enable_service_catalog=true > > ansible_service_broker_registry_whitelist=['.*-apb$'] > > ansible_service_broker_image_tag=v3.7 > > > > then, the following error is reported within the APB pod during > > serviceinstance creation > > > > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding > > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d > > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network policy > object > > - User "system:serviceaccount:openshift-ansible-service-broker:asb" > cannot > > create networkpolicies.networking.k8s.io in the namespace "project31": > User > > "system:serviceaccount:openshift-ansible-service-broker:asb" cannot > create > > networkpolicies.networking.k8s.io in project "project31" (post > > networkpolicies.networking.k8s.io) > > project "project31" (post networkpolicies.networking.k8s.io) > > > > As you can see, the clusterrole of asb-auth is still missing the > following > > info > > https://goo.gl/HfJnj8 > > > > Can somebody fix the error please for ansible openshift 3.7 ? > > > > Regards > > > > Charles > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > > _______________________________________________ > > 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 Thu Mar 1 05:57:56 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 1 Mar 2018 06:57:56 +0100 Subject: [Ansible-service-broker] ServiceInstance not deleted with origin-ansible-service-broker 3.7 Message-ID: Hi, When I try to delete a service instance in a project oc delete serviceInstance/dh-mysql-apb-dhn47 -n project31 --now=true serviceinstance "dh-mysql-apb-dhn47" deleted Then the project is marked for deletion but it will never been deleted https://www.dropbox.com/s/ad416m9364spy2m/Screenshot%202018-03-01%2006.55.53.png?dl=0 Is it a bug ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Thu Mar 1 12:35:55 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Thu, 1 Mar 2018 07:35:55 -0500 Subject: [Ansible-service-broker] ServiceInstance not deleted with origin-ansible-service-broker 3.7 In-Reply-To: References: Message-ID: Hey Charles. This issue is outlined here: https://github.com/openshift/ansible-service-broker/issues/666 In short, the catalog expects the broker cleans up all resources from a provision in order to be a successful deprovision. So, if you have an error in you deprovision, you can't cleanup a serviceinstance. Workarounds for this are 1) when using the CLI, change the name field in the serviceinstance template and recreated it or 2) when using the UI, create a new project and provision a new serviceinstance. -Ryan On Thu, Mar 1, 2018 at 12:57 AM, Charles Moulliard wrote: > Hi, > > When I try to delete a service instance in a project > > oc delete serviceInstance/dh-mysql-apb-dhn47 -n project31 --now=true > serviceinstance "dh-mysql-apb-dhn47" deleted > > Then the project is marked for deletion but it will never been deleted > > https://www.dropbox.com/s/ad416m9364spy2m/Screenshot% > 202018-03-01%2006.55.53.png?dl=0 > > Is it a bug ? > > 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 shurley at redhat.com Thu Mar 1 14:41:43 2018 From: shurley at redhat.com (Shawn Hurley) Date: Thu, 1 Mar 2018 09:41:43 -0500 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: Hello Charles, It appears that we have had a little mix up on the versions that we tagged. You are currently getting the canary version of the broker. We are working on rebuilding and re-tagging the correct images and will keep everyone informed with this email thread. Sorry about the mix up. Thanks, Shawn Hurley > On Mar 1, 2018, at 12:40 AM, Charles Moulliard wrote: > > I confirm that version 3.7 has been installed > > https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018-03-01%2006.39.40.png?dl=0 > > > On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson > wrote: > Charles, you guys are deploying upstream origin with > openshift-ansible? We discovered today thanks to your report that the > upstream openshift-ansible code was configured to default to "latest" > broker images, which is our 3.9 image. I will see if I can reproduce > your issue as well. > > +1 to shurley's comment, we have to confirm what version of the image > you are running, via tag. > > On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley > wrote: > > Hi Charles, > > > > v3.7 should not be attempting to anything with network policies, can you > > please double check the deployment config and tell us the version of the > > image that is being deployed. If it is 3.7 then we have another issue that > > we will need to solve. > > > > ansible_service_broker_image_tag should override the tag value, if that is > > not working then we will need to do a deeper dive on the openshift-ansible > > code. > > > > If you would like to just ?work around? this then you could add a cluster > > role binding and role to grant access to the asb service account to > > manipulate the network policies. > > > > Regards, > > > > Shawn Hurley > > > > On Feb 28, 2018, at 3:44 PM, Charles Moulliard > wrote: > > > > Hi, > > > > There is still an issue with the ansible playbook installing ASB on > > openshift 3.7 > > When the inventory is configured using these parameters > > > > git clone -b release-3.7 git at github.com:openshift/openshift-ansible.git > > > > openshift_enable_service_catalog=true > > ansible_service_broker_registry_whitelist=['.*-apb$'] > > ansible_service_broker_image_tag=v3.7 > > > > then, the following error is reported within the APB pod during > > serviceinstance creation > > > > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding > > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d > > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network policy object > > - User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot > > create networkpolicies.networking.k8s.io in the namespace "project31": User > > "system:serviceaccount:openshift-ansible-service-broker:asb" cannot create > > networkpolicies.networking.k8s.io in project "project31" (post > > networkpolicies.networking.k8s.io ) > > project "project31" (post networkpolicies.networking.k8s.io ) > > > > As you can see, the clusterrole of asb-auth is still missing the following > > info > > https://goo.gl/HfJnj8 > > > > Can somebody fix the error please for ansible openshift 3.7 ? > > > > Regards > > > > Charles > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > > _______________________________________________ > > 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 dzager at redhat.com Thu Mar 1 15:19:36 2018 From: dzager at redhat.com (David Zager) Date: Thu, 01 Mar 2018 15:19:36 +0000 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: Greetings Charles, The image in question, docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 has been updated to be built using the code from the release-1.0 branch of the broker project. Apologies for the trouble and thank you for helping us find the root cause. https://github.com/openshift/ansible-service-broker/pull/803 should prevent this from happening in the future. Respectfully, David Zager On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley wrote: > Hello Charles, > > It appears that we have had a little mix up on the versions that we > tagged. You are currently getting the canary version of the broker. > We are working on rebuilding and re-tagging the correct images and will > keep everyone informed with this email thread. Sorry about the mix up. > > Thanks, > > Shawn Hurley > > On Mar 1, 2018, at 12:40 AM, Charles Moulliard > wrote: > > I confirm that version 3.7 has been installed > > > https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018-03-01%2006.39.40.png?dl=0 > > > On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson wrote: > >> Charles, you guys are deploying upstream origin with >> openshift-ansible? We discovered today thanks to your report that the >> upstream openshift-ansible code was configured to default to "latest" >> broker images, which is our 3.9 image. I will see if I can reproduce >> your issue as well. >> >> +1 to shurley's comment, we have to confirm what version of the image >> you are running, via tag. >> >> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley wrote: >> > Hi Charles, >> > >> > v3.7 should not be attempting to anything with network policies, can you >> > please double check the deployment config and tell us the version of the >> > image that is being deployed. If it is 3.7 then we have another issue >> that >> > we will need to solve. >> > >> > ansible_service_broker_image_tag should override the tag value, if that >> is >> > not working then we will need to do a deeper dive on the >> openshift-ansible >> > code. >> > >> > If you would like to just ?work around? this then you could add a >> cluster >> > role binding and role to grant access to the asb service account to >> > manipulate the network policies. >> > >> > Regards, >> > >> > Shawn Hurley >> > >> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard >> wrote: >> > >> > Hi, >> > >> > There is still an issue with the ansible playbook installing ASB on >> > openshift 3.7 >> > When the inventory is configured using these parameters >> > >> > git clone -b release-3.7 git at github.com:openshift/openshift-ansible.git >> > >> > openshift_enable_service_catalog=true >> > ansible_service_broker_registry_whitelist=['.*-apb$'] >> > ansible_service_broker_image_tag=v3.7 >> > >> > then, the following error is reported within the APB pod during >> > serviceinstance creation >> > >> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network policy >> object >> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >> cannot >> > create networkpolicies.networking.k8s.io in the namespace "project31": >> User >> > "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >> create >> > networkpolicies.networking.k8s.io in project "project31" (post >> > networkpolicies.networking.k8s.io) >> > project "project31" (post networkpolicies.networking.k8s.io) >> > >> > As you can see, the clusterrole of asb-auth is still missing the >> following >> > info >> > https://goo.gl/HfJnj8 >> > >> > Can somebody fix the error please for ansible openshift 3.7 ? >> > >> > Regards >> > >> > Charles >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> > >> > >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> > > > _______________________________________________ > 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 Thu Mar 1 16:50:49 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Thu, 1 Mar 2018 11:50:49 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: Hey Folks, I added a new time for each day in the poll so can folks update the poll: https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST on Mon, Tue, Thurs, Fri and 10-11EST on Wed. -Ryan On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes wrote: > looking forward to this ! > > On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey > wrote: > >> Folks, >> >> The broker community has been talking about starting a weekly IRC >> meeting. The plan is to have folks gather in the Freenode channel >> (#asbroker) and go over things that have been happening in the community. >> Here's a link to the google doc >> >> with the format. >> >> The first order of business is to find a time that works. Can folks fill >> out the doodle poll with all >> the times that work for you and we'll select the time that most people can >> make it. If you want to add any times to the poll let me know. >> >> Thanks, >> - Ryan >> >> google doc: https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmB >> BZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing >> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd >> >> >> _______________________________________________ >> 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 ernelson at redhat.com Thu Mar 1 16:56:08 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 1 Mar 2018 11:56:08 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: Ryan, little late to the poll so there's really only tomorrow to vote one. Should I consider this just a vote for the time and day of the week? On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey wrote: > Hey Folks, > > I added a new time for each day in the poll so can folks update the poll: > https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST on Mon, > Tue, Thurs, Fri and 10-11EST on Wed. > > -Ryan > > On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes wrote: >> >> looking forward to this ! >> >> On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey >> wrote: >>> >>> Folks, >>> >>> The broker community has been talking about starting a weekly IRC >>> meeting. The plan is to have folks gather in the Freenode channel >>> (#asbroker) and go over things that have been happening in the community. >>> Here's a link to the google doc with the format. >>> >>> The first order of business is to find a time that works. Can folks fill >>> out the doodle poll with all the times that work for you and we'll select >>> the time that most people can make it. If you want to add any times to the >>> poll let me know. >>> >>> Thanks, >>> - Ryan >>> >>> google doc: >>> https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing >>> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd >>> >>> >>> _______________________________________________ >>> 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 > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > From shurley at redhat.com Thu Mar 1 17:09:05 2018 From: shurley at redhat.com (Shawn Hurley) Date: Thu, 01 Mar 2018 17:09:05 +0000 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: Hey everyone, This might be a new discussion but wanted to bring it up here. Should we draft or take a code of conduct for the community? I think this is something that we moght want to have in place before this hopefully grows. I would suggest that us No eother golangs or kubernetes community code of conduct would be a good thing. Thanks, Shawn Hurley On Thu, Mar 1, 2018 at 12:03 PM Erik Nelson wrote: > Ryan, little late to the poll so there's really only tomorrow to vote > one. Should I consider this just a vote for the time and day of the > week? > > On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey > wrote: > > Hey Folks, > > > > I added a new time for each day in the poll so can folks update the poll: > > https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST on > Mon, > > Tue, Thurs, Fri and 10-11EST on Wed. > > > > -Ryan > > > > On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes > wrote: > >> > >> looking forward to this ! > >> > >> On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey > >> wrote: > >>> > >>> Folks, > >>> > >>> The broker community has been talking about starting a weekly IRC > >>> meeting. The plan is to have folks gather in the Freenode channel > >>> (#asbroker) and go over things that have been happening in the > community. > >>> Here's a link to the google doc with the format. > >>> > >>> The first order of business is to find a time that works. Can folks > fill > >>> out the doodle poll with all the times that work for you and we'll > select > >>> the time that most people can make it. If you want to add any times > to the > >>> poll let me know. > >>> > >>> Thanks, > >>> - Ryan > >>> > >>> google doc: > >>> > https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing > >>> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > > > > > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > _______________________________________________ > 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 Thu Mar 1 17:09:21 2018 From: jesusr at redhat.com (jesus m. rodriguez) Date: Thu, 01 Mar 2018 12:09:21 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: <1519924161.15078.10.camel@redhat.com> That's how I voted, day of the week and time. jesus On Thu, 2018-03-01 at 11:56 -0500, Erik Nelson wrote: > Ryan, little late to the poll so there's really only tomorrow to vote > one. Should I consider this just a vote for the time and day of the > week? > > On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey > wrote: > > Hey Folks, > > > > I added a new time for each day in the poll so can folks update the > > poll: > > https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST > > on Mon, > > Tue, Thurs, Fri and 10-11EST on Wed. > > > > -Ryan > > From ernelson at redhat.com Thu Mar 1 17:12:00 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 1 Mar 2018 12:12:00 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: <1519924161.15078.10.camel@redhat.com> References: <1519924161.15078.10.camel@redhat.com> Message-ID: Thanks, revising my vote. On Thu, Mar 1, 2018 at 12:09 PM, jesus m. rodriguez wrote: > That's how I voted, day of the week and time. > > jesus > > On Thu, 2018-03-01 at 11:56 -0500, Erik Nelson wrote: >> Ryan, little late to the poll so there's really only tomorrow to vote >> one. Should I consider this just a vote for the time and day of the >> week? >> >> On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey >> wrote: >> > Hey Folks, >> > >> > I added a new time for each day in the poll so can folks update the >> > poll: >> > https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST >> > on Mon, >> > Tue, Thurs, Fri and 10-11EST on Wed. >> > >> > -Ryan >> > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker From rhallise at redhat.com Thu Mar 1 17:13:45 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Thu, 1 Mar 2018 12:13:45 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: <976EF8DB-49E4-417F-A651-5298322E04BA@redhat.com> Thanks for pointing that out Erik. This poll is just to find a weekly day and time that most folks think they can make. So you can ignore the dates and select the times that will work for you on a weekly basis. Sorry for the confusion. - Ryan > On Mar 1, 2018, at 11:56 AM, Erik Nelson wrote: > > Ryan, little late to the poll so there's really only tomorrow to vote > one. Should I consider this just a vote for the time and day of the > week? > >> On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey wrote: >> Hey Folks, >> >> I added a new time for each day in the poll so can folks update the poll: >> https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST on Mon, >> Tue, Thurs, Fri and 10-11EST on Wed. >> >> -Ryan >> >>> On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes wrote: >>> >>> looking forward to this ! >>> >>> On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey >>> wrote: >>>> >>>> Folks, >>>> >>>> The broker community has been talking about starting a weekly IRC >>>> meeting. The plan is to have folks gather in the Freenode channel >>>> (#asbroker) and go over things that have been happening in the community. >>>> Here's a link to the google doc with the format. >>>> >>>> The first order of business is to find a time that works. Can folks fill >>>> out the doodle poll with all the times that work for you and we'll select >>>> the time that most people can make it. If you want to add any times to the >>>> poll let me know. >>>> >>>> Thanks, >>>> - Ryan >>>> >>>> google doc: >>>> https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing >>>> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> From shurley at redhat.com Thu Mar 1 17:22:53 2018 From: shurley at redhat.com (Shawn Hurley) Date: Thu, 1 Mar 2018 12:22:53 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: <63D9405C-042F-4EBC-A6AD-D9BF7682258D@redhat.com> Well this makes no sense. * I would suggest that we use either golangs or kubernetes community code of conduct. * Links: https://github.com/cncf/foundation/blob/master/code-of-conduct.md https://golang.org/conduct Sorry about that, Shawn Hurley > On Mar 1, 2018, at 12:09 PM, Shawn Hurley wrote: > > Hey everyone, > > This might be a new discussion but wanted to bring it up here. > > Should we draft or take a code of conduct for the community? I think this is something that we moght want to have in place before this hopefully grows. I would suggest that us No eother golangs or kubernetes community code of conduct would be a good thing. > > Thanks, > > Shawn Hurley > > On Thu, Mar 1, 2018 at 12:03 PM Erik Nelson > wrote: > Ryan, little late to the poll so there's really only tomorrow to vote > one. Should I consider this just a vote for the time and day of the > week? > > On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey > wrote: > > Hey Folks, > > > > I added a new time for each day in the poll so can folks update the poll: > > https://doodle.com/poll/qu75f5xatq32wekd . The times are 11-12 EST on Mon, > > Tue, Thurs, Fri and 10-11EST on Wed. > > > > -Ryan > > > > On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes > wrote: > >> > >> looking forward to this ! > >> > >> On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey > > >> wrote: > >>> > >>> Folks, > >>> > >>> The broker community has been talking about starting a weekly IRC > >>> meeting. The plan is to have folks gather in the Freenode channel > >>> (#asbroker) and go over things that have been happening in the community. > >>> Here's a link to the google doc with the format. > >>> > >>> The first order of business is to find a time that works. Can folks fill > >>> out the doodle poll with all the times that work for you and we'll select > >>> the time that most people can make it. If you want to add any times to the > >>> poll let me know. > >>> > >>> Thanks, > >>> - Ryan > >>> > >>> google doc: > >>> https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing > >>> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > > > > > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > _______________________________________________ > 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 Thu Mar 1 17:28:11 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Thu, 1 Mar 2018 12:28:11 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: <63D9405C-042F-4EBC-A6AD-D9BF7682258D@redhat.com> References: <63D9405C-042F-4EBC-A6AD-D9BF7682258D@redhat.com> Message-ID: Good idea Shawn. I added it to the meeting agenda. On Thu, Mar 1, 2018 at 12:22 PM, Shawn Hurley wrote: > Well this makes no sense. > > * I would suggest that we use either golangs or kubernetes community code > of conduct. * > > Links: > https://github.com/cncf/foundation/blob/master/code-of-conduct.md > https://golang.org/conduct > > Sorry about that, > > Shawn Hurley > > > On Mar 1, 2018, at 12:09 PM, Shawn Hurley wrote: > > Hey everyone, > > This might be a new discussion but wanted to bring it up here. > > Should we draft or take a code of conduct for the community? I think this > is something that we moght want to have in place before this hopefully > grows. I would suggest that us No eother golangs or kubernetes community > code of conduct would be a good thing. > > Thanks, > > Shawn Hurley > > On Thu, Mar 1, 2018 at 12:03 PM Erik Nelson wrote: > >> Ryan, little late to the poll so there's really only tomorrow to vote >> one. Should I consider this just a vote for the time and day of the >> week? >> >> On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey >> wrote: >> > Hey Folks, >> > >> > I added a new time for each day in the poll so can folks update the >> poll: >> > https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST on >> Mon, >> > Tue, Thurs, Fri and 10-11EST on Wed. >> > >> > -Ryan >> > >> > On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes >> wrote: >> >> >> >> looking forward to this ! >> >> >> >> On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey >> >> wrote: >> >>> >> >>> Folks, >> >>> >> >>> The broker community has been talking about starting a weekly IRC >> >>> meeting. The plan is to have folks gather in the Freenode channel >> >>> (#asbroker) and go over things that have been happening in the >> community. >> >>> Here's a link to the google doc with the format. >> >>> >> >>> The first order of business is to find a time that works. Can folks >> fill >> >>> out the doodle poll with all the times that work for you and we'll >> select >> >>> the time that most people can make it. If you want to add any times >> to the >> >>> poll let me know. >> >>> >> >>> Thanks, >> >>> - Ryan >> >>> >> >>> google doc: >> >>> https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_ >> mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing >> >>> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd >> >>> >> >>> >> >>> _______________________________________________ >> >>> 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 >> > >> > >> > >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > > > _______________________________________________ > 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 ernelson at redhat.com Thu Mar 1 17:37:01 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 1 Mar 2018 12:37:01 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: <63D9405C-042F-4EBC-A6AD-D9BF7682258D@redhat.com> References: <63D9405C-042F-4EBC-A6AD-D9BF7682258D@redhat.com> Message-ID: +1, great suggestion. I think this is important. Is anyone familiar enough with these to describe the differences? On Thu, Mar 1, 2018 at 12:22 PM, Shawn Hurley wrote: > Well this makes no sense. > > * I would suggest that we use either golangs or kubernetes community code of > conduct. * > > Links: > https://github.com/cncf/foundation/blob/master/code-of-conduct.md > https://golang.org/conduct > > Sorry about that, > > Shawn Hurley > > > On Mar 1, 2018, at 12:09 PM, Shawn Hurley wrote: > > Hey everyone, > > This might be a new discussion but wanted to bring it up here. > > Should we draft or take a code of conduct for the community? I think this is > something that we moght want to have in place before this hopefully grows. I > would suggest that us No eother golangs or kubernetes community code of > conduct would be a good thing. > > Thanks, > > Shawn Hurley > > On Thu, Mar 1, 2018 at 12:03 PM Erik Nelson wrote: >> >> Ryan, little late to the poll so there's really only tomorrow to vote >> one. Should I consider this just a vote for the time and day of the >> week? >> >> On Thu, Mar 1, 2018 at 11:50 AM, Ryan Hallisey >> wrote: >> > Hey Folks, >> > >> > I added a new time for each day in the poll so can folks update the >> > poll: >> > https://doodle.com/poll/qu75f5xatq32wekd. The times are 11-12 EST on >> > Mon, >> > Tue, Thurs, Fri and 10-11EST on Wed. >> > >> > -Ryan >> > >> > On Wed, Feb 28, 2018 at 4:45 PM, Craig Brookes >> > wrote: >> >> >> >> looking forward to this ! >> >> >> >> On Wed, Feb 28, 2018 at 5:23 PM, Ryan Hallisey >> >> wrote: >> >>> >> >>> Folks, >> >>> >> >>> The broker community has been talking about starting a weekly IRC >> >>> meeting. The plan is to have folks gather in the Freenode channel >> >>> (#asbroker) and go over things that have been happening in the >> >>> community. >> >>> Here's a link to the google doc with the format. >> >>> >> >>> The first order of business is to find a time that works. Can folks >> >>> fill >> >>> out the doodle poll with all the times that work for you and we'll >> >>> select >> >>> the time that most people can make it. If you want to add any times >> >>> to the >> >>> poll let me know. >> >>> >> >>> Thanks, >> >>> - Ryan >> >>> >> >>> google doc: >> >>> >> >>> https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing >> >>> doodle poll: https://doodle.com/poll/qu75f5xatq32wekd >> >>> >> >>> >> >>> _______________________________________________ >> >>> 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 >> > >> > >> > >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > From shurley at redhat.com Thu Mar 1 17:58:12 2018 From: shurley at redhat.com (Shawn Hurley) Date: Thu, 1 Mar 2018 12:58:12 -0500 Subject: [Ansible-service-broker] Custom Resources As Storage Message-ID: Hello All, Recently a PR was merged that allows a broker to use CRDs to save its internal state. This is going to be quick rundown with a follow on PR coming to make this more clear in the documentation. Custom Resources that the broker uses 1. Bundles.automationbroker.io 2. servicebindings.automationbroker.io 3. serviceinstance.automationbroker.io 4. jobstate.automationbroker.io To turn on the CRD for storage you will need to edit the broker configmap: dao: type: ?crd? ??(can either leave the etcd stuff here or remove it) If people could please give this a try and create issues with the label storage that would be helpful for me to keep track of all the issues that have arisen from this change. Thanks, Shawn Hurley PR: https://github.com/openshift/ansible-service-broker/pull/795 Proposal: https://github.com/openshift/ansible-service-broker/blob/master/docs/proposals/custom_resources_definitions.md -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhrivnak at redhat.com Thu Mar 1 18:16:38 2018 From: mhrivnak at redhat.com (Michael Hrivnak) Date: Thu, 1 Mar 2018 13:16:38 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: On Thu, Mar 1, 2018 at 12:09 PM, Shawn Hurley wrote: > > Should we draft or take a code of conduct for the community? I think this > is something that we moght want to have in place before this hopefully > grows. > This one is very popular, and it is the origins for the Kubernetes/CNCF CoC. https://www.contributor-covenant.org/ -- Michael Hrivnak Principal Software Engineer, RHCE Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Fri Mar 2 12:44:03 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Fri, 2 Mar 2018 07:44:03 -0500 Subject: [Ansible-service-broker] Automation Broker Community Meeting In-Reply-To: References: Message-ID: Hey folks, Final reminder to fill out the doodle poll for the upstream IRC meeting. I'll plan on sending out an email at the end of the day with the final meeting time. https://doodle.com/poll/qu75f5xatq32wekd - Ryan On Thu, Mar 1, 2018 at 1:16 PM, Michael Hrivnak wrote: > > > On Thu, Mar 1, 2018 at 12:09 PM, Shawn Hurley wrote: > >> >> Should we draft or take a code of conduct for the community? I think this >> is something that we moght want to have in place before this hopefully >> grows. >> > > This one is very popular, and it is the origins for the Kubernetes/CNCF > CoC. > > https://www.contributor-covenant.org/ > > > -- > > Michael Hrivnak > > Principal Software Engineer, RHCE > > Red Hat > > _______________________________________________ > 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 Fri Mar 2 14:03:43 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 2 Mar 2018 15:03:43 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: We have redeployed using openshift-ansible playbook ASB using image v3.,7 and networkpolicies issue is still there On Thu, Mar 1, 2018 at 4:19 PM, David Zager wrote: > Greetings Charles, > > The image in question, docker.io/ansibleplaybookbundle/origin- > ansible-service-broker:v3.7 > > has been updated to be built using the code from the release-1.0 > branch > of the broker project. Apologies for the trouble and thank you for helping > us find the root cause. > > https://github.com/openshift/ansible-service-broker/pull/803 should > prevent this from happening in the future. > > Respectfully, > David Zager > > On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley wrote: > >> Hello Charles, >> >> It appears that we have had a little mix up on the versions that we >> tagged. You are currently getting the canary version of the broker. >> We are working on rebuilding and re-tagging the correct images and will >> keep everyone informed with this email thread. Sorry about the mix up. >> >> Thanks, >> >> Shawn Hurley >> >> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >> wrote: >> >> I confirm that version 3.7 has been installed >> >> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot% >> 202018-03-01%2006.39.40.png?dl=0 >> >> >> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson wrote: >> >>> Charles, you guys are deploying upstream origin with >>> openshift-ansible? We discovered today thanks to your report that the >>> upstream openshift-ansible code was configured to default to "latest" >>> broker images, which is our 3.9 image. I will see if I can reproduce >>> your issue as well. >>> >>> +1 to shurley's comment, we have to confirm what version of the image >>> you are running, via tag. >>> >>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>> wrote: >>> > Hi Charles, >>> > >>> > v3.7 should not be attempting to anything with network policies, can >>> you >>> > please double check the deployment config and tell us the version of >>> the >>> > image that is being deployed. If it is 3.7 then we have another issue >>> that >>> > we will need to solve. >>> > >>> > ansible_service_broker_image_tag should override the tag value, if >>> that is >>> > not working then we will need to do a deeper dive on the >>> openshift-ansible >>> > code. >>> > >>> > If you would like to just ?work around? this then you could add a >>> cluster >>> > role binding and role to grant access to the asb service account to >>> > manipulate the network policies. >>> > >>> > Regards, >>> > >>> > Shawn Hurley >>> > >>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard >>> wrote: >>> > >>> > Hi, >>> > >>> > There is still an issue with the ansible playbook installing ASB on >>> > openshift 3.7 >>> > When the inventory is configured using these parameters >>> > >>> > git clone -b release-3.7 git at github.com:openshift/ >>> openshift-ansible.git >>> > >>> > openshift_enable_service_catalog=true >>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>> > ansible_service_broker_image_tag=v3.7 >>> > >>> > then, the following error is reported within the APB pod during >>> > serviceinstance creation >>> > >>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network policy >>> object >>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>> cannot >>> > create networkpolicies.networking.k8s.io in the namespace >>> "project31": User >>> > "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>> create >>> > networkpolicies.networking.k8s.io in project "project31" (post >>> > networkpolicies.networking.k8s.io) >>> > project "project31" (post networkpolicies.networking.k8s.io) >>> > >>> > As you can see, the clusterrole of asb-auth is still missing the >>> following >>> > info >>> > https://goo.gl/HfJnj8 >>> > >>> > Can somebody fix the error please for ansible openshift 3.7 ? >>> > >>> > Regards >>> > >>> > Charles >>> > _______________________________________________ >>> > Ansible-service-broker mailing list >>> > Ansible-service-broker at redhat.com >>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>> > >>> > >>> > >>> > _______________________________________________ >>> > Ansible-service-broker mailing list >>> > Ansible-service-broker at redhat.com >>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>> > >>> >> >> >> _______________________________________________ >> 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 Fri Mar 2 14:12:05 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Fri, 2 Mar 2018 09:12:05 -0500 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: In case this helps Charles, a temporary work around would be to: oc edit clusterrole asb-auth and add: - apiGroups: ["network.openshift.io", ""] attributeRestrictions: null resources: ["clusternetworks", "netnamespaces"] verbs: ["get"] - apiGroups: ["network.openshift.io", ""] attributeRestrictions: null resources: ["netnamespaces"] verbs: ["update"] - apiGroups: ["networking.k8s.io", ""] attributeRestrictions: null resources: ["networkpolicies"] verbs: ["create", "delete"] Thanks, - Ryan On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard wrote: > We have redeployed using openshift-ansible playbook ASB using image v3.,7 > and networkpolicies issue is still there > > On Thu, Mar 1, 2018 at 4:19 PM, David Zager wrote: > >> Greetings Charles, >> >> The image in question, docker.io/ansibleplaybookbundl >> e/origin-ansible-service-broker:v3.7 >> >> has been updated to be built using the code from the release-1.0 >> branch >> of the broker project. Apologies for the trouble and thank you for helping >> us find the root cause. >> >> https://github.com/openshift/ansible-service-broker/pull/803 should >> prevent this from happening in the future. >> >> Respectfully, >> David Zager >> >> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley wrote: >> >>> Hello Charles, >>> >>> It appears that we have had a little mix up on the versions that we >>> tagged. You are currently getting the canary version of the broker. >>> We are working on rebuilding and re-tagging the correct images and will >>> keep everyone informed with this email thread. Sorry about the mix up. >>> >>> Thanks, >>> >>> Shawn Hurley >>> >>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >>> wrote: >>> >>> I confirm that version 3.7 has been installed >>> >>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018- >>> 03-01%2006.39.40.png?dl=0 >>> >>> >>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>> wrote: >>> >>>> Charles, you guys are deploying upstream origin with >>>> openshift-ansible? We discovered today thanks to your report that the >>>> upstream openshift-ansible code was configured to default to "latest" >>>> broker images, which is our 3.9 image. I will see if I can reproduce >>>> your issue as well. >>>> >>>> +1 to shurley's comment, we have to confirm what version of the image >>>> you are running, via tag. >>>> >>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>> wrote: >>>> > Hi Charles, >>>> > >>>> > v3.7 should not be attempting to anything with network policies, can >>>> you >>>> > please double check the deployment config and tell us the version of >>>> the >>>> > image that is being deployed. If it is 3.7 then we have another issue >>>> that >>>> > we will need to solve. >>>> > >>>> > ansible_service_broker_image_tag should override the tag value, if >>>> that is >>>> > not working then we will need to do a deeper dive on the >>>> openshift-ansible >>>> > code. >>>> > >>>> > If you would like to just ?work around? this then you could add a >>>> cluster >>>> > role binding and role to grant access to the asb service account to >>>> > manipulate the network policies. >>>> > >>>> > Regards, >>>> > >>>> > Shawn Hurley >>>> > >>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard >>>> wrote: >>>> > >>>> > Hi, >>>> > >>>> > There is still an issue with the ansible playbook installing ASB on >>>> > openshift 3.7 >>>> > When the inventory is configured using these parameters >>>> > >>>> > git clone -b release-3.7 git at github.com:openshift/opens >>>> hift-ansible.git >>>> > >>>> > openshift_enable_service_catalog=true >>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>> > ansible_service_broker_image_tag=v3.7 >>>> > >>>> > then, the following error is reported within the APB pod during >>>> > serviceinstance creation >>>> > >>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network policy >>>> object >>>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>> cannot >>>> > create networkpolicies.networking.k8s.io in the namespace >>>> "project31": User >>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>> create >>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>> > networkpolicies.networking.k8s.io) >>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>> > >>>> > As you can see, the clusterrole of asb-auth is still missing the >>>> following >>>> > info >>>> > https://goo.gl/HfJnj8 >>>> > >>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>> > >>>> > Regards >>>> > >>>> > Charles >>>> > _______________________________________________ >>>> > Ansible-service-broker mailing list >>>> > Ansible-service-broker at redhat.com >>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Ansible-service-broker mailing list >>>> > Ansible-service-broker at redhat.com >>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>> > >>>> >>> >>> >>> _______________________________________________ >>> Ansible-service-broker mailing list >>> Ansible-service-broker at redhat.com >>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>> >> > > _______________________________________________ > 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 dzager at redhat.com Fri Mar 2 14:24:05 2018 From: dzager at redhat.com (David Zager) Date: Fri, 02 Mar 2018 14:24:05 +0000 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: Something is not right here. The original error message posted was: [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy object - User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot create networkpolicies.networking.k8s.io in the namespace "project31": User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot create networkpolicies.networking.k8s.io in project "project31" (post networkpolicies.networking.k8s.io )* and it comes from https://github.com/openshift/ansible-service-broker/blob/ff1f14a421dbdab5834ebd994615081db0f09ac5/pkg/runtime/runtime.go#L225 but pkg/runtime/runtime.go does not exist in the v3.7 image: $ docker pull docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 Trying to pull repository docker.io/ansibleplaybookbundle/origin-ansible-service-broker ... sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: Pulling from docker.io/ansibleplaybookbundle/origin-ansible-service-broker Digest: sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b Status: Image is up to date for docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 $ docker run -it --entrypoint /bin/bash docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 bash-4.2$ ls $GOPATH/src/ github.com/openshift/ansible-service-broker/pkg/runtime hack.go # Furthermore, searching for that error message in the v3.7 image shows that error doesn't exist in the v3.7 image bash-4.2$ grep -r 'unable to create' $GOPATH/src/ github.com/openshift/ansible-service-broker/pkg The most likely cause for this is that the broker image was not updated. I am open to other possibilities, could you rule this one out please? Respectfully, David Zager On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey wrote: > In case this helps Charles, a temporary work around would be to: oc edit > clusterrole asb-auth > > and add: > > - apiGroups: ["network.openshift.io", ""] > attributeRestrictions: null > resources: ["clusternetworks", "netnamespaces"] > verbs: ["get"] > - apiGroups: ["network.openshift.io", ""] > attributeRestrictions: null > resources: ["netnamespaces"] > verbs: ["update"] > - apiGroups: ["networking.k8s.io", ""] > attributeRestrictions: null > resources: ["networkpolicies"] > verbs: ["create", "delete"] > > > Thanks, > - Ryan > > On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard > wrote: > >> We have redeployed using openshift-ansible playbook ASB using image v3.,7 >> and networkpolicies issue is still there >> >> On Thu, Mar 1, 2018 at 4:19 PM, David Zager wrote: >> >>> Greetings Charles, >>> >>> The image in question, >>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>> >>> has been updated to be built using the code from the release-1.0 >>> branch >>> of the broker project. Apologies for the trouble and thank you for helping >>> us find the root cause. >>> >>> https://github.com/openshift/ansible-service-broker/pull/803 should >>> prevent this from happening in the future. >>> >>> Respectfully, >>> David Zager >>> >>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley wrote: >>> >>>> Hello Charles, >>>> >>>> It appears that we have had a little mix up on the versions that we >>>> tagged. You are currently getting the canary version of the broker. >>>> We are working on rebuilding and re-tagging the correct images and will >>>> keep everyone informed with this email thread. Sorry about the mix up. >>>> >>>> Thanks, >>>> >>>> Shawn Hurley >>>> >>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >>>> wrote: >>>> >>>> I confirm that version 3.7 has been installed >>>> >>>> >>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018-03-01%2006.39.40.png?dl=0 >>>> >>>> >>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>> wrote: >>>> >>>>> Charles, you guys are deploying upstream origin with >>>>> openshift-ansible? We discovered today thanks to your report that the >>>>> upstream openshift-ansible code was configured to default to "latest" >>>>> broker images, which is our 3.9 image. I will see if I can reproduce >>>>> your issue as well. >>>>> >>>>> +1 to shurley's comment, we have to confirm what version of the image >>>>> you are running, via tag. >>>>> >>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>>> wrote: >>>>> > Hi Charles, >>>>> > >>>>> > v3.7 should not be attempting to anything with network policies, can >>>>> you >>>>> > please double check the deployment config and tell us the version of >>>>> the >>>>> > image that is being deployed. If it is 3.7 then we have another >>>>> issue that >>>>> > we will need to solve. >>>>> > >>>>> > ansible_service_broker_image_tag should override the tag value, if >>>>> that is >>>>> > not working then we will need to do a deeper dive on the >>>>> openshift-ansible >>>>> > code. >>>>> > >>>>> > If you would like to just ?work around? this then you could add a >>>>> cluster >>>>> > role binding and role to grant access to the asb service account to >>>>> > manipulate the network policies. >>>>> > >>>>> > Regards, >>>>> > >>>>> > Shawn Hurley >>>>> > >>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard >>>>> wrote: >>>>> > >>>>> > Hi, >>>>> > >>>>> > There is still an issue with the ansible playbook installing ASB on >>>>> > openshift 3.7 >>>>> > When the inventory is configured using these parameters >>>>> > >>>>> > git clone -b release-3.7 git at github.com >>>>> :openshift/openshift-ansible.git >>>>> > >>>>> > openshift_enable_service_catalog=true >>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>> > ansible_service_broker_image_tag=v3.7 >>>>> > >>>>> > then, the following error is reported within the APB pod during >>>>> > serviceinstance creation >>>>> > >>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network policy >>>>> object >>>>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>> cannot >>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>> "project31": User >>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>>> create >>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>> > networkpolicies.networking.k8s.io) >>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>> > >>>>> > As you can see, the clusterrole of asb-auth is still missing the >>>>> following >>>>> > info >>>>> > https://goo.gl/HfJnj8 >>>>> > >>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>> > >>>>> > Regards >>>>> > >>>>> > Charles >>>>> > _______________________________________________ >>>>> > Ansible-service-broker mailing list >>>>> > Ansible-service-broker at redhat.com >>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>> > >>>>> > >>>>> > >>>>> > _______________________________________________ >>>>> > Ansible-service-broker mailing list >>>>> > Ansible-service-broker at redhat.com >>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>> > >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Ansible-service-broker mailing list >>>> Ansible-service-broker at redhat.com >>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>> >>> >> >> _______________________________________________ >> 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 Fri Mar 2 19:33:11 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 2 Mar 2018 20:33:11 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: This is my fault as the docker image docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 wasn't updated and still the old one. I have redeployed and the problem is gone. Thanks On Fri, Mar 2, 2018 at 3:24 PM, David Zager wrote: > Something is not right here. The original error message posted was: > > [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy > object - User "system:serviceaccount:openshift-ansible-service-broker:asb" > cannot create networkpolicies.networking.k8s.io > in the namespace "project31": > User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot > create networkpolicies.networking.k8s.io > in project "project31" > (post networkpolicies.networking.k8s.io > )* > > and it comes from https://github.com/openshift/ > ansible-service-broker/blob/ff1f14a421dbdab5834ebd99461508 > 1db0f09ac5/pkg/runtime/runtime.go#L225 but pkg/runtime/runtime.go does > not exist in the v3.7 image: > > $ docker pull docker.io/ansibleplaybookbundle/origin- > ansible-service-broker:v3.7 > Trying to pull repository docker.io/ansibleplaybookbundle/origin- > ansible-service-broker ... > sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: > Pulling from docker.io/ansibleplaybookbundle/origin-ansible-service-broker > Digest: sha256:25026da783b7b8777f07fc90fefd03 > 7bb785424d5a7f364875e9df6d0321d76b > Status: Image is up to date for docker.io/ansibleplaybookbundle/origin- > ansible-service-broker:v3.7 > > $ docker run -it --entrypoint /bin/bash docker.io/ > ansibleplaybookbundle/origin-ansible-service-broker:v3.7 > bash-4.2$ ls $GOPATH/src/github.com/openshift/ansible-service- > broker/pkg/runtime > hack.go > # Furthermore, searching for that error message in the v3.7 image shows > that error doesn't exist in the v3.7 image > bash-4.2$ grep -r 'unable to create' $GOPATH/src/github.com/ > openshift/ansible-service-broker/pkg > > The most likely cause for this is that the broker image was not updated. I > am open to other possibilities, could you rule this one out please? > > Respectfully, > David Zager > > > > On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey wrote: > >> In case this helps Charles, a temporary work around would be to: oc edit >> clusterrole asb-auth >> >> and add: >> >> - apiGroups: ["network.openshift.io", ""] >> attributeRestrictions: null >> resources: ["clusternetworks", "netnamespaces"] >> verbs: ["get"] >> - apiGroups: ["network.openshift.io", ""] >> attributeRestrictions: null >> resources: ["netnamespaces"] >> verbs: ["update"] >> - apiGroups: ["networking.k8s.io", ""] >> attributeRestrictions: null >> resources: ["networkpolicies"] >> verbs: ["create", "delete"] >> >> >> Thanks, >> - Ryan >> >> On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard >> wrote: >> >>> We have redeployed using openshift-ansible playbook ASB using image >>> v3.,7 and networkpolicies issue is still there >>> >>> On Thu, Mar 1, 2018 at 4:19 PM, David Zager wrote: >>> >>>> Greetings Charles, >>>> >>>> The image in question, docker.io/ansibleplaybookbundle/origin- >>>> ansible-service-broker:v3.7 >>>> >>>> has been updated to be built using the code from the release-1.0 >>>> branch >>>> of the broker project. Apologies for the trouble and thank you for helping >>>> us find the root cause. >>>> >>>> https://github.com/openshift/ansible-service-broker/pull/803 should >>>> prevent this from happening in the future. >>>> >>>> Respectfully, >>>> David Zager >>>> >>>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley wrote: >>>> >>>>> Hello Charles, >>>>> >>>>> It appears that we have had a little mix up on the versions that we >>>>> tagged. You are currently getting the canary version of the broker. >>>>> We are working on rebuilding and re-tagging the correct images and >>>>> will keep everyone informed with this email thread. Sorry about the mix up. >>>>> >>>>> Thanks, >>>>> >>>>> Shawn Hurley >>>>> >>>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >>>>> wrote: >>>>> >>>>> I confirm that version 3.7 has been installed >>>>> >>>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot% >>>>> 202018-03-01%2006.39.40.png?dl=0 >>>>> >>>>> >>>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>>> wrote: >>>>> >>>>>> Charles, you guys are deploying upstream origin with >>>>>> openshift-ansible? We discovered today thanks to your report that the >>>>>> upstream openshift-ansible code was configured to default to "latest" >>>>>> broker images, which is our 3.9 image. I will see if I can reproduce >>>>>> your issue as well. >>>>>> >>>>>> +1 to shurley's comment, we have to confirm what version of the image >>>>>> you are running, via tag. >>>>>> >>>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>>>> wrote: >>>>>> > Hi Charles, >>>>>> > >>>>>> > v3.7 should not be attempting to anything with network policies, >>>>>> can you >>>>>> > please double check the deployment config and tell us the version >>>>>> of the >>>>>> > image that is being deployed. If it is 3.7 then we have another >>>>>> issue that >>>>>> > we will need to solve. >>>>>> > >>>>>> > ansible_service_broker_image_tag should override the tag value, if >>>>>> that is >>>>>> > not working then we will need to do a deeper dive on the >>>>>> openshift-ansible >>>>>> > code. >>>>>> > >>>>>> > If you would like to just ?work around? this then you could add a >>>>>> cluster >>>>>> > role binding and role to grant access to the asb service account to >>>>>> > manipulate the network policies. >>>>>> > >>>>>> > Regards, >>>>>> > >>>>>> > Shawn Hurley >>>>>> > >>>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard >>>>>> wrote: >>>>>> > >>>>>> > Hi, >>>>>> > >>>>>> > There is still an issue with the ansible playbook installing ASB on >>>>>> > openshift 3.7 >>>>>> > When the inventory is configured using these parameters >>>>>> > >>>>>> > git clone -b release-3.7 git at github.com:openshift/ >>>>>> openshift-ansible.git >>>>>> > >>>>>> > openshift_enable_service_catalog=true >>>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>>> > ansible_service_broker_image_tag=v3.7 >>>>>> > >>>>>> > then, the following error is reported within the APB pod during >>>>>> > serviceinstance creation >>>>>> > >>>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network >>>>>> policy object >>>>>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>> cannot >>>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>>> "project31": User >>>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>> cannot create >>>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>>> > networkpolicies.networking.k8s.io) >>>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>>> > >>>>>> > As you can see, the clusterrole of asb-auth is still missing the >>>>>> following >>>>>> > info >>>>>> > https://goo.gl/HfJnj8 >>>>>> > >>>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>>> > >>>>>> > Regards >>>>>> > >>>>>> > Charles >>>>>> > _______________________________________________ >>>>>> > Ansible-service-broker mailing list >>>>>> > Ansible-service-broker at redhat.com >>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>> > >>>>>> > >>>>>> > >>>>>> > _______________________________________________ >>>>>> > Ansible-service-broker mailing list >>>>>> > Ansible-service-broker at redhat.com >>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>> > >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Ansible-service-broker mailing list >>>>> Ansible-service-broker at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>> >>>> >>> >>> _______________________________________________ >>> 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 dzager at redhat.com Fri Mar 2 19:47:32 2018 From: dzager at redhat.com (David Zager) Date: Fri, 02 Mar 2018 19:47:32 +0000 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: No worries. You were essential to us realizing that what we thought were release specific broker images were not correct. Thank you for that and your patience throughout. On Fri, Mar 2, 2018, 14:33 Charles Moulliard wrote: > This is my fault as the docker image > docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 wasn't > updated and still the old one. > > I have redeployed and the problem is gone. Thanks > > On Fri, Mar 2, 2018 at 3:24 PM, David Zager wrote: > >> Something is not right here. The original error message posted was: >> >> [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy >> object - User "system:serviceaccount:openshift-ansible-service-broker:asb" >> cannot create networkpolicies.networking.k8s.io >> in the namespace "project31": >> User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >> create networkpolicies.networking.k8s.io >> in project "project31" >> (post networkpolicies.networking.k8s.io >> )* >> >> and it comes from >> https://github.com/openshift/ansible-service-broker/blob/ff1f14a421dbdab5834ebd994615081db0f09ac5/pkg/runtime/runtime.go#L225 but >> pkg/runtime/runtime.go does not exist in the v3.7 image: >> >> $ docker pull >> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >> Trying to pull repository >> docker.io/ansibleplaybookbundle/origin-ansible-service-broker ... >> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: >> Pulling from >> docker.io/ansibleplaybookbundle/origin-ansible-service-broker >> Digest: >> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b >> Status: Image is up to date for >> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >> >> $ docker run -it --entrypoint /bin/bash >> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >> bash-4.2$ ls $GOPATH/src/ >> github.com/openshift/ansible-service-broker/pkg/runtime >> hack.go >> # Furthermore, searching for that error message in the v3.7 image shows >> that error doesn't exist in the v3.7 image >> bash-4.2$ grep -r 'unable to create' $GOPATH/src/ >> github.com/openshift/ansible-service-broker/pkg >> >> The most likely cause for this is that the broker image was not updated. >> I am open to other possibilities, could you rule this one out please? >> >> Respectfully, >> David Zager >> >> >> >> On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey wrote: >> >>> In case this helps Charles, a temporary work around would be to: oc edit >>> clusterrole asb-auth >>> >>> and add: >>> >>> - apiGroups: ["network.openshift.io", ""] >>> attributeRestrictions: null >>> resources: ["clusternetworks", "netnamespaces"] >>> verbs: ["get"] >>> - apiGroups: ["network.openshift.io", ""] >>> attributeRestrictions: null >>> resources: ["netnamespaces"] >>> verbs: ["update"] >>> - apiGroups: ["networking.k8s.io", ""] >>> attributeRestrictions: null >>> resources: ["networkpolicies"] >>> verbs: ["create", "delete"] >>> >>> >>> Thanks, >>> - Ryan >>> >>> On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard >>> wrote: >>> >>>> We have redeployed using openshift-ansible playbook ASB using image >>>> v3.,7 and networkpolicies issue is still there >>>> >>>> On Thu, Mar 1, 2018 at 4:19 PM, David Zager wrote: >>>> >>>>> Greetings Charles, >>>>> >>>>> The image in question, >>>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>>> >>>>> has been updated to be built using the code from the release-1.0 >>>>> branch >>>>> of the broker project. Apologies for the trouble and thank you for helping >>>>> us find the root cause. >>>>> >>>>> https://github.com/openshift/ansible-service-broker/pull/803 should >>>>> prevent this from happening in the future. >>>>> >>>>> Respectfully, >>>>> David Zager >>>>> >>>>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley >>>>> wrote: >>>>> >>>>>> Hello Charles, >>>>>> >>>>>> It appears that we have had a little mix up on the versions that we >>>>>> tagged. You are currently getting the canary version of the broker. >>>>>> We are working on rebuilding and re-tagging the correct images and >>>>>> will keep everyone informed with this email thread. Sorry about the mix up. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Shawn Hurley >>>>>> >>>>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >>>>>> wrote: >>>>>> >>>>>> I confirm that version 3.7 has been installed >>>>>> >>>>>> >>>>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018-03-01%2006.39.40.png?dl=0 >>>>>> >>>>>> >>>>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>>>> wrote: >>>>>> >>>>>>> Charles, you guys are deploying upstream origin with >>>>>>> openshift-ansible? We discovered today thanks to your report that the >>>>>>> upstream openshift-ansible code was configured to default to "latest" >>>>>>> broker images, which is our 3.9 image. I will see if I can reproduce >>>>>>> your issue as well. >>>>>>> >>>>>>> +1 to shurley's comment, we have to confirm what version of the image >>>>>>> you are running, via tag. >>>>>>> >>>>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>>>>> wrote: >>>>>>> > Hi Charles, >>>>>>> > >>>>>>> > v3.7 should not be attempting to anything with network policies, >>>>>>> can you >>>>>>> > please double check the deployment config and tell us the version >>>>>>> of the >>>>>>> > image that is being deployed. If it is 3.7 then we have another >>>>>>> issue that >>>>>>> > we will need to solve. >>>>>>> > >>>>>>> > ansible_service_broker_image_tag should override the tag value, if >>>>>>> that is >>>>>>> > not working then we will need to do a deeper dive on the >>>>>>> openshift-ansible >>>>>>> > code. >>>>>>> > >>>>>>> > If you would like to just ?work around? this then you could add a >>>>>>> cluster >>>>>>> > role binding and role to grant access to the asb service account to >>>>>>> > manipulate the network policies. >>>>>>> > >>>>>>> > Regards, >>>>>>> > >>>>>>> > Shawn Hurley >>>>>>> > >>>>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard < >>>>>>> cmoullia at redhat.com> wrote: >>>>>>> > >>>>>>> > Hi, >>>>>>> > >>>>>>> > There is still an issue with the ansible playbook installing ASB on >>>>>>> > openshift 3.7 >>>>>>> > When the inventory is configured using these parameters >>>>>>> > >>>>>>> > git clone -b release-3.7 git at github.com >>>>>>> :openshift/openshift-ansible.git >>>>>>> > >>>>>>> > openshift_enable_service_catalog=true >>>>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>>>> > ansible_service_broker_image_tag=v3.7 >>>>>>> > >>>>>>> > then, the following error is reported within the APB pod during >>>>>>> > serviceinstance creation >>>>>>> > >>>>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network >>>>>>> policy object >>>>>>> > - User >>>>>>> "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>>>> "project31": User >>>>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>> cannot create >>>>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>>>> > networkpolicies.networking.k8s.io) >>>>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>>>> > >>>>>>> > As you can see, the clusterrole of asb-auth is still missing the >>>>>>> following >>>>>>> > info >>>>>>> > https://goo.gl/HfJnj8 >>>>>>> > >>>>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>>>> > >>>>>>> > Regards >>>>>>> > >>>>>>> > Charles >>>>>>> > _______________________________________________ >>>>>>> > Ansible-service-broker mailing list >>>>>>> > Ansible-service-broker at redhat.com >>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > _______________________________________________ >>>>>>> > Ansible-service-broker mailing list >>>>>>> > Ansible-service-broker at redhat.com >>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>> > >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Ansible-service-broker mailing list >>>>>> Ansible-service-broker at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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 Fri Mar 2 19:53:47 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 2 Mar 2018 20:53:47 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: I experiment nevertheless a new issue with docker image v3.7 now as no secret is created duriing binding step https://www.dropbox.com/s/ufimavnt8bscdq2/Screenshot%202018-03-02%2020.49.15.png?dl=0 https://gist.github.com/cmoulliard/dc2c947514ba8a30b17b72671650c906 On Fri, Mar 2, 2018 at 8:47 PM, David Zager wrote: > No worries. You were essential to us realizing that what we thought were > release specific broker images were not correct. Thank you for that and > your patience throughout. > > > On Fri, Mar 2, 2018, 14:33 Charles Moulliard wrote: > >> This is my fault as the docker image docker.io/ >> ansibleplaybookbundle/origin-ansible-service-broker:v3.7 wasn't updated >> and still the old one. >> >> I have redeployed and the problem is gone. Thanks >> >> On Fri, Mar 2, 2018 at 3:24 PM, David Zager wrote: >> >>> Something is not right here. The original error message posted was: >>> >>> [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy >>> object - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>> cannot create networkpolicies.networking.k8s.io >>> in the namespace "project31": >>> User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>> create networkpolicies.networking.k8s.io >>> in project "project31" >>> (post networkpolicies.networking.k8s.io >>> )* >>> >>> and it comes from https://github.com/openshift/ >>> ansible-service-broker/blob/ff1f14a421dbdab5834ebd99461508 >>> 1db0f09ac5/pkg/runtime/runtime.go#L225 but pkg/runtime/runtime.go does >>> not exist in the v3.7 image: >>> >>> $ docker pull docker.io/ansibleplaybookbundle/origin- >>> ansible-service-broker:v3.7 >>> Trying to pull repository docker.io/ansibleplaybookbundle/origin- >>> ansible-service-broker ... >>> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: >>> Pulling from docker.io/ansibleplaybookbundle/origin- >>> ansible-service-broker >>> Digest: sha256:25026da783b7b8777f07fc90fefd03 >>> 7bb785424d5a7f364875e9df6d0321d76b >>> Status: Image is up to date for docker.io/ansibleplaybookbundle/origin- >>> ansible-service-broker:v3.7 >>> >>> $ docker run -it --entrypoint /bin/bash docker.io/ >>> ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>> bash-4.2$ ls $GOPATH/src/github.com/openshift/ansible-service- >>> broker/pkg/runtime >>> hack.go >>> # Furthermore, searching for that error message in the v3.7 image shows >>> that error doesn't exist in the v3.7 image >>> bash-4.2$ grep -r 'unable to create' $GOPATH/src/github.com/ >>> openshift/ansible-service-broker/pkg >>> >>> The most likely cause for this is that the broker image was not updated. >>> I am open to other possibilities, could you rule this one out please? >>> >>> Respectfully, >>> David Zager >>> >>> >>> >>> On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey >>> wrote: >>> >>>> In case this helps Charles, a temporary work around would be to: oc >>>> edit clusterrole asb-auth >>>> >>>> and add: >>>> >>>> - apiGroups: ["network.openshift.io", ""] >>>> attributeRestrictions: null >>>> resources: ["clusternetworks", "netnamespaces"] >>>> verbs: ["get"] >>>> - apiGroups: ["network.openshift.io", ""] >>>> attributeRestrictions: null >>>> resources: ["netnamespaces"] >>>> verbs: ["update"] >>>> - apiGroups: ["networking.k8s.io", ""] >>>> attributeRestrictions: null >>>> resources: ["networkpolicies"] >>>> verbs: ["create", "delete"] >>>> >>>> >>>> Thanks, >>>> - Ryan >>>> >>>> On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard >>>> wrote: >>>> >>>>> We have redeployed using openshift-ansible playbook ASB using image >>>>> v3.,7 and networkpolicies issue is still there >>>>> >>>>> On Thu, Mar 1, 2018 at 4:19 PM, David Zager wrote: >>>>> >>>>>> Greetings Charles, >>>>>> >>>>>> The image in question, docker.io/ansibleplaybookbundle/origin- >>>>>> ansible-service-broker:v3.7 >>>>>> >>>>>> has been updated to be built using the code from the release-1.0 >>>>>> branch >>>>>> of the broker project. Apologies for the trouble and thank you for helping >>>>>> us find the root cause. >>>>>> >>>>>> https://github.com/openshift/ansible-service-broker/pull/803 should >>>>>> prevent this from happening in the future. >>>>>> >>>>>> Respectfully, >>>>>> David Zager >>>>>> >>>>>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley >>>>>> wrote: >>>>>> >>>>>>> Hello Charles, >>>>>>> >>>>>>> It appears that we have had a little mix up on the versions that we >>>>>>> tagged. You are currently getting the canary version of the broker. >>>>>>> We are working on rebuilding and re-tagging the correct images and >>>>>>> will keep everyone informed with this email thread. Sorry about the mix up. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Shawn Hurley >>>>>>> >>>>>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >>>>>>> wrote: >>>>>>> >>>>>>> I confirm that version 3.7 has been installed >>>>>>> >>>>>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot% >>>>>>> 202018-03-01%2006.39.40.png?dl=0 >>>>>>> >>>>>>> >>>>>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>>>>> wrote: >>>>>>> >>>>>>>> Charles, you guys are deploying upstream origin with >>>>>>>> openshift-ansible? We discovered today thanks to your report that >>>>>>>> the >>>>>>>> upstream openshift-ansible code was configured to default to >>>>>>>> "latest" >>>>>>>> broker images, which is our 3.9 image. I will see if I can reproduce >>>>>>>> your issue as well. >>>>>>>> >>>>>>>> +1 to shurley's comment, we have to confirm what version of the >>>>>>>> image >>>>>>>> you are running, via tag. >>>>>>>> >>>>>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>>>>>> wrote: >>>>>>>> > Hi Charles, >>>>>>>> > >>>>>>>> > v3.7 should not be attempting to anything with network policies, >>>>>>>> can you >>>>>>>> > please double check the deployment config and tell us the version >>>>>>>> of the >>>>>>>> > image that is being deployed. If it is 3.7 then we have another >>>>>>>> issue that >>>>>>>> > we will need to solve. >>>>>>>> > >>>>>>>> > ansible_service_broker_image_tag should override the tag value, >>>>>>>> if that is >>>>>>>> > not working then we will need to do a deeper dive on the >>>>>>>> openshift-ansible >>>>>>>> > code. >>>>>>>> > >>>>>>>> > If you would like to just ?work around? this then you could add a >>>>>>>> cluster >>>>>>>> > role binding and role to grant access to the asb service account >>>>>>>> to >>>>>>>> > manipulate the network policies. >>>>>>>> > >>>>>>>> > Regards, >>>>>>>> > >>>>>>>> > Shawn Hurley >>>>>>>> > >>>>>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard < >>>>>>>> cmoullia at redhat.com> wrote: >>>>>>>> > >>>>>>>> > Hi, >>>>>>>> > >>>>>>>> > There is still an issue with the ansible playbook installing ASB >>>>>>>> on >>>>>>>> > openshift 3.7 >>>>>>>> > When the inventory is configured using these parameters >>>>>>>> > >>>>>>>> > git clone -b release-3.7 git at github.com:openshift/ >>>>>>>> openshift-ansible.git >>>>>>>> > >>>>>>>> > openshift_enable_service_catalog=true >>>>>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>>>>> > ansible_service_broker_image_tag=v3.7 >>>>>>>> > >>>>>>>> > then, the following error is reported within the APB pod during >>>>>>>> > serviceinstance creation >>>>>>>> > >>>>>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network >>>>>>>> policy object >>>>>>>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>> cannot >>>>>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>>>>> "project31": User >>>>>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>> cannot create >>>>>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>>>>> > networkpolicies.networking.k8s.io) >>>>>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>>>>> > >>>>>>>> > As you can see, the clusterrole of asb-auth is still missing the >>>>>>>> following >>>>>>>> > info >>>>>>>> > https://goo.gl/HfJnj8 >>>>>>>> > >>>>>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>>>>> > >>>>>>>> > Regards >>>>>>>> > >>>>>>>> > Charles >>>>>>>> > _______________________________________________ >>>>>>>> > Ansible-service-broker mailing list >>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > _______________________________________________ >>>>>>>> > Ansible-service-broker mailing list >>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>> > >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Ansible-service-broker mailing list >>>>>>> Ansible-service-broker at redhat.com >>>>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 dzager at redhat.com Fri Mar 2 20:50:49 2018 From: dzager at redhat.com (David Zager) Date: Fri, 02 Mar 2018 20:50:49 +0000 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: Greetings, I am actually working on a PR to explain our Broker + APB Compatibility as well as our versioning strategy. The important line to notice from your error is here : [2018-03-02T19:47:02.516Z] [NOTICE] Spec.Image: docker.io/ansibleplaybookbundle/mysql-apb:latest This is causing issues for you because the v3.7 broker is not compatible with the latest images, looking at the relevant openshift-ansible , it looks like you can override the ansible_service_broker_registry_tag variable with v3.7 to get the appropriate images. On Fri, Mar 2, 2018 at 2:54 PM Charles Moulliard wrote: > I experiment nevertheless a new issue with docker image v3.7 now as no > secret is created duriing binding step > > > https://www.dropbox.com/s/ufimavnt8bscdq2/Screenshot%202018-03-02%2020.49.15.png?dl=0 > > https://gist.github.com/cmoulliard/dc2c947514ba8a30b17b72671650c906 > > On Fri, Mar 2, 2018 at 8:47 PM, David Zager wrote: > >> No worries. You were essential to us realizing that what we thought were >> release specific broker images were not correct. Thank you for that and >> your patience throughout. >> >> >> On Fri, Mar 2, 2018, 14:33 Charles Moulliard wrote: >> >>> This is my fault as the docker image >>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>> wasn't updated and still the old one. >>> >>> I have redeployed and the problem is gone. Thanks >>> >>> On Fri, Mar 2, 2018 at 3:24 PM, David Zager wrote: >>> >>>> Something is not right here. The original error message posted was: >>>> >>>> [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy >>>> object - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>> cannot create networkpolicies.networking.k8s.io >>>> in the namespace "project31": >>>> User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>> create networkpolicies.networking.k8s.io >>>> in project "project31" >>>> (post networkpolicies.networking.k8s.io >>>> )* >>>> >>>> and it comes from >>>> https://github.com/openshift/ansible-service-broker/blob/ff1f14a421dbdab5834ebd994615081db0f09ac5/pkg/runtime/runtime.go#L225 but >>>> pkg/runtime/runtime.go does not exist in the v3.7 image: >>>> >>>> $ docker pull >>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>> Trying to pull repository >>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker ... >>>> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: >>>> Pulling from >>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker >>>> Digest: >>>> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b >>>> Status: Image is up to date for >>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>> >>>> $ docker run -it --entrypoint /bin/bash >>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>> bash-4.2$ ls $GOPATH/src/ >>>> github.com/openshift/ansible-service-broker/pkg/runtime >>>> hack.go >>>> # Furthermore, searching for that error message in the v3.7 image shows >>>> that error doesn't exist in the v3.7 image >>>> bash-4.2$ grep -r 'unable to create' $GOPATH/src/ >>>> github.com/openshift/ansible-service-broker/pkg >>>> >>>> The most likely cause for this is that the broker image was not >>>> updated. I am open to other possibilities, could you rule this one out >>>> please? >>>> >>>> Respectfully, >>>> David Zager >>>> >>>> >>>> >>>> On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey >>>> wrote: >>>> >>>>> In case this helps Charles, a temporary work around would be to: oc >>>>> edit clusterrole asb-auth >>>>> >>>>> and add: >>>>> >>>>> - apiGroups: ["network.openshift.io", ""] >>>>> attributeRestrictions: null >>>>> resources: ["clusternetworks", "netnamespaces"] >>>>> verbs: ["get"] >>>>> - apiGroups: ["network.openshift.io", ""] >>>>> attributeRestrictions: null >>>>> resources: ["netnamespaces"] >>>>> verbs: ["update"] >>>>> - apiGroups: ["networking.k8s.io", ""] >>>>> attributeRestrictions: null >>>>> resources: ["networkpolicies"] >>>>> verbs: ["create", "delete"] >>>>> >>>>> >>>>> Thanks, >>>>> - Ryan >>>>> >>>>> On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard >>>> > wrote: >>>>> >>>>>> We have redeployed using openshift-ansible playbook ASB using image >>>>>> v3.,7 and networkpolicies issue is still there >>>>>> >>>>>> On Thu, Mar 1, 2018 at 4:19 PM, David Zager >>>>>> wrote: >>>>>> >>>>>>> Greetings Charles, >>>>>>> >>>>>>> The image in question, >>>>>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>>>>> >>>>>>> has been updated to be built using the code from the release-1.0 >>>>>>> branch >>>>>>> of the broker project. Apologies for the trouble and thank you for helping >>>>>>> us find the root cause. >>>>>>> >>>>>>> https://github.com/openshift/ansible-service-broker/pull/803 should >>>>>>> prevent this from happening in the future. >>>>>>> >>>>>>> Respectfully, >>>>>>> David Zager >>>>>>> >>>>>>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley >>>>>>> wrote: >>>>>>> >>>>>>>> Hello Charles, >>>>>>>> >>>>>>>> It appears that we have had a little mix up on the versions that we >>>>>>>> tagged. You are currently getting the canary version of the broker. >>>>>>>> We are working on rebuilding and re-tagging the correct images and >>>>>>>> will keep everyone informed with this email thread. Sorry about the mix up. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Shawn Hurley >>>>>>>> >>>>>>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard >>>>>>>> wrote: >>>>>>>> >>>>>>>> I confirm that version 3.7 has been installed >>>>>>>> >>>>>>>> >>>>>>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018-03-01%2006.39.40.png?dl=0 >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Charles, you guys are deploying upstream origin with >>>>>>>>> openshift-ansible? We discovered today thanks to your report that >>>>>>>>> the >>>>>>>>> upstream openshift-ansible code was configured to default to >>>>>>>>> "latest" >>>>>>>>> broker images, which is our 3.9 image. I will see if I can >>>>>>>>> reproduce >>>>>>>>> your issue as well. >>>>>>>>> >>>>>>>>> +1 to shurley's comment, we have to confirm what version of the >>>>>>>>> image >>>>>>>>> you are running, via tag. >>>>>>>>> >>>>>>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>>>>>>> wrote: >>>>>>>>> > Hi Charles, >>>>>>>>> > >>>>>>>>> > v3.7 should not be attempting to anything with network policies, >>>>>>>>> can you >>>>>>>>> > please double check the deployment config and tell us the >>>>>>>>> version of the >>>>>>>>> > image that is being deployed. If it is 3.7 then we have another >>>>>>>>> issue that >>>>>>>>> > we will need to solve. >>>>>>>>> > >>>>>>>>> > ansible_service_broker_image_tag should override the tag value, >>>>>>>>> if that is >>>>>>>>> > not working then we will need to do a deeper dive on the >>>>>>>>> openshift-ansible >>>>>>>>> > code. >>>>>>>>> > >>>>>>>>> > If you would like to just ?work around? this then you could add >>>>>>>>> a cluster >>>>>>>>> > role binding and role to grant access to the asb service account >>>>>>>>> to >>>>>>>>> > manipulate the network policies. >>>>>>>>> > >>>>>>>>> > Regards, >>>>>>>>> > >>>>>>>>> > Shawn Hurley >>>>>>>>> > >>>>>>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard < >>>>>>>>> cmoullia at redhat.com> wrote: >>>>>>>>> > >>>>>>>>> > Hi, >>>>>>>>> > >>>>>>>>> > There is still an issue with the ansible playbook installing ASB >>>>>>>>> on >>>>>>>>> > openshift 3.7 >>>>>>>>> > When the inventory is configured using these parameters >>>>>>>>> > >>>>>>>>> > git clone -b release-3.7 git at github.com >>>>>>>>> :openshift/openshift-ansible.git >>>>>>>>> > >>>>>>>>> > openshift_enable_service_catalog=true >>>>>>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>>>>>> > ansible_service_broker_image_tag=v3.7 >>>>>>>>> > >>>>>>>>> > then, the following error is reported within the APB pod during >>>>>>>>> > serviceinstance creation >>>>>>>>> > >>>>>>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>>>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>>>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network >>>>>>>>> policy object >>>>>>>>> > - User >>>>>>>>> "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>>>>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>>>>>> "project31": User >>>>>>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>>> cannot create >>>>>>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>>>>>> > networkpolicies.networking.k8s.io) >>>>>>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>>>>>> > >>>>>>>>> > As you can see, the clusterrole of asb-auth is still missing the >>>>>>>>> following >>>>>>>>> > info >>>>>>>>> > https://goo.gl/HfJnj8 >>>>>>>>> > >>>>>>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>>>>>> > >>>>>>>>> > Regards >>>>>>>>> > >>>>>>>>> > Charles >>>>>>>>> > _______________________________________________ >>>>>>>>> > Ansible-service-broker mailing list >>>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > _______________________________________________ >>>>>>>>> > Ansible-service-broker mailing list >>>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>> > >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Ansible-service-broker mailing list >>>>>>>> Ansible-service-broker at redhat.com >>>>>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 Fri Mar 2 21:52:19 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Fri, 2 Mar 2018 16:52:19 -0500 Subject: [Ansible-service-broker] Upstream IRC Meeting Time Message-ID: Hey folks, We had a tie for the most people (10) between Tuesdays 9:30-10:30am EST and Thursdays 1:30-2:30pm EST. I'm inclined to go with the Tuesday time and maybe some folks can work around some meetings. I think doing an alternating schedule of Tuesday/Thursday can be hard, so in my opinion we should start with one weekly time and adjust if we feel we need to. What do folks think? First meeting is planned for Tuesday 3/6 @ 9:30 EST/14:00 UTC. Mark your calendars and feel free to start adding items to the agenda ! Thanks, - Ryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Fri Mar 2 21:53:50 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Fri, 2 Mar 2018 22:53:50 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: Thanks. I have redeployed ASB using these parameters within the inventory and openshift ansible - branch 3.7 ansible_service_broker_registry_whitelist=['.*-apb$'] ansible_service_broker_image_tag=v3.7 ansible_service_broker_registry_tag=v3.7 ansible_service_broker_remove=false ansible_service_broker_install=true but I get these errors as the images doesn't exist for the tag v3.7 within docker hub [2018-03-02T21:48:05.831Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/iscsi-demo-target-apb:v3.7' may not exist in registry. [2018-03-02T21:48:05.831Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:06.055Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/proxy-config-apb:v3.7' may not exist in registry. [2018-03-02T21:48:06.056Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:06.862Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/virtualmachines-apb:v3.7' may not exist in registry. [2018-03-02T21:48:06.862Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:07.097Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/photo-album-demo-api-apb:v3.7' may not exist in registry. [2018-03-02T21:48:07.097Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:07.325Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/kibana-apb:v3.7' may not exist in registry. [2018-03-02T21:48:07.325Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:08.007Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/awx-apb:v3.7' may not exist in registry. [2018-03-02T21:48:08.007Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:09.081Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/keycloak-apb:v3.7' may not exist in registry. [2018-03-02T21:48:09.081Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:09.306Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/prometheus-apb:v3.7' may not exist in registry. [2018-03-02T21:48:09.306Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:09.857Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/photo-album-demo-ext-api-apb:v3.7' may not exist in registry. [2018-03-02T21:48:09.857Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:10.084Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/photo-album-demo-app-apb:v3.7' may not exist in registry. [2018-03-02T21:48:10.084Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:11.114Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/mongodb-apb:v3.7' may not exist in registry. [2018-03-02T21:48:11.114Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:11.741Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/s2i-apb:v3.7' may not exist in registry. [2018-03-02T21:48:11.741Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:13.081Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/es-apb:v3.7' may not exist in registry. [2018-03-02T21:48:13.081Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} [2018-03-02T21:48:13.67Z] [ERROR] Image ' docker.io/ansibleplaybookbundle/kubevirt-apb:v3.7' may not exist in registry. [2018-03-02T21:48:13.67Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":{"Tag":"v3.7"}}]} On Fri, Mar 2, 2018 at 9:50 PM, David Zager wrote: > Greetings, > > I am actually working on a PR to explain our Broker + APB Compatibility > as well as > our versioning strategy. The important line to notice from your error is > here > > : > > [2018-03-02T19:47:02.516Z] [NOTICE] Spec.Image: docker.io/ > ansibleplaybookbundle/mysql-apb:latest > > This is causing issues for you because the v3.7 broker is not compatible > with the latest images, looking at the relevant openshift-ansible > , > it looks like you can override the ansible_service_broker_registry_tag variable > with v3.7 to get the appropriate images. > > > On Fri, Mar 2, 2018 at 2:54 PM Charles Moulliard > wrote: > >> I experiment nevertheless a new issue with docker image v3.7 now as no >> secret is created duriing binding step >> >> https://www.dropbox.com/s/ufimavnt8bscdq2/Screenshot% >> 202018-03-02%2020.49.15.png?dl=0 >> >> https://gist.github.com/cmoulliard/dc2c947514ba8a30b17b72671650c906 >> >> On Fri, Mar 2, 2018 at 8:47 PM, David Zager wrote: >> >>> No worries. You were essential to us realizing that what we thought were >>> release specific broker images were not correct. Thank you for that and >>> your patience throughout. >>> >>> >>> On Fri, Mar 2, 2018, 14:33 Charles Moulliard >>> wrote: >>> >>>> This is my fault as the docker image docker.io/ >>>> ansibleplaybookbundle/origin-ansible-service-broker:v3.7 wasn't >>>> updated and still the old one. >>>> >>>> I have redeployed and the problem is gone. Thanks >>>> >>>> On Fri, Mar 2, 2018 at 3:24 PM, David Zager wrote: >>>> >>>>> Something is not right here. The original error message posted was: >>>>> >>>>> [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network policy >>>>> object - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>> cannot create networkpolicies.networking.k8s.io >>>>> in the namespace "project31": >>>>> User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>>> create networkpolicies.networking.k8s.io >>>>> in project "project31" >>>>> (post networkpolicies.networking.k8s.io >>>>> )* >>>>> >>>>> and it comes from https://github.com/openshift/ >>>>> ansible-service-broker/blob/ff1f14a421dbdab5834ebd99461508 >>>>> 1db0f09ac5/pkg/runtime/runtime.go#L225 but pkg/runtime/runtime.go >>>>> does not exist in the v3.7 image: >>>>> >>>>> $ docker pull docker.io/ansibleplaybookbundle/origin- >>>>> ansible-service-broker:v3.7 >>>>> Trying to pull repository docker.io/ansibleplaybookbundle/origin- >>>>> ansible-service-broker ... >>>>> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: >>>>> Pulling from docker.io/ansibleplaybookbundle/origin- >>>>> ansible-service-broker >>>>> Digest: sha256:25026da783b7b8777f07fc90fefd03 >>>>> 7bb785424d5a7f364875e9df6d0321d76b >>>>> Status: Image is up to date for docker.io/ >>>>> ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>>> >>>>> $ docker run -it --entrypoint /bin/bash docker.io/ >>>>> ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>>> bash-4.2$ ls $GOPATH/src/github.com/openshift/ansible-service- >>>>> broker/pkg/runtime >>>>> hack.go >>>>> # Furthermore, searching for that error message in the v3.7 image >>>>> shows that error doesn't exist in the v3.7 image >>>>> bash-4.2$ grep -r 'unable to create' $GOPATH/src/github.com/ >>>>> openshift/ansible-service-broker/pkg >>>>> >>>>> The most likely cause for this is that the broker image was not >>>>> updated. I am open to other possibilities, could you rule this one out >>>>> please? >>>>> >>>>> Respectfully, >>>>> David Zager >>>>> >>>>> >>>>> >>>>> On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey >>>>> wrote: >>>>> >>>>>> In case this helps Charles, a temporary work around would be to: oc >>>>>> edit clusterrole asb-auth >>>>>> >>>>>> and add: >>>>>> >>>>>> - apiGroups: ["network.openshift.io", ""] >>>>>> attributeRestrictions: null >>>>>> resources: ["clusternetworks", "netnamespaces"] >>>>>> verbs: ["get"] >>>>>> - apiGroups: ["network.openshift.io", ""] >>>>>> attributeRestrictions: null >>>>>> resources: ["netnamespaces"] >>>>>> verbs: ["update"] >>>>>> - apiGroups: ["networking.k8s.io", ""] >>>>>> attributeRestrictions: null >>>>>> resources: ["networkpolicies"] >>>>>> verbs: ["create", "delete"] >>>>>> >>>>>> >>>>>> Thanks, >>>>>> - Ryan >>>>>> >>>>>> On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard < >>>>>> cmoullia at redhat.com> wrote: >>>>>> >>>>>>> We have redeployed using openshift-ansible playbook ASB using image >>>>>>> v3.,7 and networkpolicies issue is still there >>>>>>> >>>>>>> On Thu, Mar 1, 2018 at 4:19 PM, David Zager >>>>>>> wrote: >>>>>>> >>>>>>>> Greetings Charles, >>>>>>>> >>>>>>>> The image in question, docker.io/ansibleplaybookbundle/origin- >>>>>>>> ansible-service-broker:v3.7 >>>>>>>> >>>>>>>> has been updated to be built using the code from the release-1.0 >>>>>>>> branch >>>>>>>> of the broker project. Apologies for the trouble and thank you for helping >>>>>>>> us find the root cause. >>>>>>>> >>>>>>>> https://github.com/openshift/ansible-service-broker/pull/803 should >>>>>>>> prevent this from happening in the future. >>>>>>>> >>>>>>>> Respectfully, >>>>>>>> David Zager >>>>>>>> >>>>>>>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hello Charles, >>>>>>>>> >>>>>>>>> It appears that we have had a little mix up on the versions that >>>>>>>>> we tagged. You are currently getting the canary version of the broker. >>>>>>>>> We are working on rebuilding and re-tagging the correct images and >>>>>>>>> will keep everyone informed with this email thread. Sorry about the mix up. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Shawn Hurley >>>>>>>>> >>>>>>>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard < >>>>>>>>> cmoullia at redhat.com> wrote: >>>>>>>>> >>>>>>>>> I confirm that version 3.7 has been installed >>>>>>>>> >>>>>>>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot% >>>>>>>>> 202018-03-01%2006.39.40.png?dl=0 >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Charles, you guys are deploying upstream origin with >>>>>>>>>> openshift-ansible? We discovered today thanks to your report that >>>>>>>>>> the >>>>>>>>>> upstream openshift-ansible code was configured to default to >>>>>>>>>> "latest" >>>>>>>>>> broker images, which is our 3.9 image. I will see if I can >>>>>>>>>> reproduce >>>>>>>>>> your issue as well. >>>>>>>>>> >>>>>>>>>> +1 to shurley's comment, we have to confirm what version of the >>>>>>>>>> image >>>>>>>>>> you are running, via tag. >>>>>>>>>> >>>>>>>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley >>>>>>>>>> wrote: >>>>>>>>>> > Hi Charles, >>>>>>>>>> > >>>>>>>>>> > v3.7 should not be attempting to anything with network >>>>>>>>>> policies, can you >>>>>>>>>> > please double check the deployment config and tell us the >>>>>>>>>> version of the >>>>>>>>>> > image that is being deployed. If it is 3.7 then we have another >>>>>>>>>> issue that >>>>>>>>>> > we will need to solve. >>>>>>>>>> > >>>>>>>>>> > ansible_service_broker_image_tag should override the tag >>>>>>>>>> value, if that is >>>>>>>>>> > not working then we will need to do a deeper dive on the >>>>>>>>>> openshift-ansible >>>>>>>>>> > code. >>>>>>>>>> > >>>>>>>>>> > If you would like to just ?work around? this then you could add >>>>>>>>>> a cluster >>>>>>>>>> > role binding and role to grant access to the asb service >>>>>>>>>> account to >>>>>>>>>> > manipulate the network policies. >>>>>>>>>> > >>>>>>>>>> > Regards, >>>>>>>>>> > >>>>>>>>>> > Shawn Hurley >>>>>>>>>> > >>>>>>>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard < >>>>>>>>>> cmoullia at redhat.com> wrote: >>>>>>>>>> > >>>>>>>>>> > Hi, >>>>>>>>>> > >>>>>>>>>> > There is still an issue with the ansible playbook installing >>>>>>>>>> ASB on >>>>>>>>>> > openshift 3.7 >>>>>>>>>> > When the inventory is configured using these parameters >>>>>>>>>> > >>>>>>>>>> > git clone -b release-3.7 git at github.com:openshift/ >>>>>>>>>> openshift-ansible.git >>>>>>>>>> > >>>>>>>>>> > openshift_enable_service_catalog=true >>>>>>>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>>>>>>> > ansible_service_broker_image_tag=v3.7 >>>>>>>>>> > >>>>>>>>>> > then, the following error is reported within the APB pod during >>>>>>>>>> > serviceinstance creation >>>>>>>>>> > >>>>>>>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>>>>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>>>>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network >>>>>>>>>> policy object >>>>>>>>>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>>>> cannot >>>>>>>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>>>>>>> "project31": User >>>>>>>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>>>> cannot create >>>>>>>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>>>>>>> > networkpolicies.networking.k8s.io) >>>>>>>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>>>>>>> > >>>>>>>>>> > As you can see, the clusterrole of asb-auth is still missing >>>>>>>>>> the following >>>>>>>>>> > info >>>>>>>>>> > https://goo.gl/HfJnj8 >>>>>>>>>> > >>>>>>>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>>>>>>> > >>>>>>>>>> > Regards >>>>>>>>>> > >>>>>>>>>> > Charles >>>>>>>>>> > _______________________________________________ >>>>>>>>>> > Ansible-service-broker mailing list >>>>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > _______________________________________________ >>>>>>>>>> > Ansible-service-broker mailing list >>>>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>>> > >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Ansible-service-broker mailing list >>>>>>>>> Ansible-service-broker at redhat.com >>>>>>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 Sat Mar 3 08:25:49 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Sat, 3 Mar 2018 09:25:49 +0100 Subject: [Ansible-service-broker] Issue with playbook of ansible service broker - missing networkpolicies In-Reply-To: References: <9F8A0664-4F7E-418C-ACDF-3922A71BE373@redhat.com> Message-ID: Ticket opened : https://github.com/openshift/ansible-service-broker/issues/813 On Fri, Mar 2, 2018 at 10:53 PM, Charles Moulliard wrote: > Thanks. I have redeployed ASB using these parameters within the inventory > and openshift ansible - branch 3.7 > > ansible_service_broker_registry_whitelist=['.*-apb$'] > ansible_service_broker_image_tag=v3.7 > ansible_service_broker_registry_tag=v3.7 > ansible_service_broker_remove=false > ansible_service_broker_install=true > > but I get these errors as the images doesn't exist for the tag v3.7 within > docker hub > > [2018-03-02T21:48:05.831Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/iscsi-demo-target-apb:v3.7' may not exist in > registry. > [2018-03-02T21:48:05.831Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:06.055Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/proxy-config-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:06.056Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:06.862Z] [ERROR] Image 'docker.io/ansibleplaybookbundle/ > virtualmachines-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:06.862Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:07.097Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/photo-album-demo-api-apb:v3.7' may not exist in > registry. > [2018-03-02T21:48:07.097Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:07.325Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/kibana-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:07.325Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:08.007Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/awx-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:08.007Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:09.081Z] [ERROR] Image 'docker.io/ansibleplaybookbundle/ > keycloak-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:09.081Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:09.306Z] [ERROR] Image 'docker.io/ansibleplaybookbundle/ > prometheus-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:09.306Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:09.857Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/photo-album-demo-ext-api-apb:v3.7' may not exist in > registry. > [2018-03-02T21:48:09.857Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:10.084Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/photo-album-demo-app-apb:v3.7' may not exist in > registry. > [2018-03-02T21:48:10.084Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:11.114Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/mongodb-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:11.114Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:11.741Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/s2i-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:11.741Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:13.081Z] [ERROR] Image 'docker.io/ > ansibleplaybookbundle/es-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:13.081Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > [2018-03-02T21:48:13.67Z] [ERROR] Image 'docker.io/ansibleplaybookbundle/ > kubevirt-apb:v3.7' may not exist in registry. > [2018-03-02T21:48:13.67Z] [ERROR] {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest > unknown","detail":{"Tag":"v3.7"}}]} > > On Fri, Mar 2, 2018 at 9:50 PM, David Zager wrote: > >> Greetings, >> >> I am actually working on a PR to explain our Broker + APB Compatibility >> as well >> as our versioning strategy. The important line to notice from your error is >> here >> >> : >> >> [2018-03-02T19:47:02.516Z] [NOTICE] Spec.Image: >> docker.io/ansibleplaybookbundle/mysql-apb:latest >> >> This is causing issues for you because the v3.7 broker is not compatible >> with the latest images, looking at the relevant openshift-ansible >> , >> it looks like you can override the ansible_service_broker_registry_tag variable >> with v3.7 to get the appropriate images. >> >> >> On Fri, Mar 2, 2018 at 2:54 PM Charles Moulliard >> wrote: >> >>> I experiment nevertheless a new issue with docker image v3.7 now as no >>> secret is created duriing binding step >>> >>> https://www.dropbox.com/s/ufimavnt8bscdq2/Screenshot%202018- >>> 03-02%2020.49.15.png?dl=0 >>> >>> https://gist.github.com/cmoulliard/dc2c947514ba8a30b17b72671650c906 >>> >>> On Fri, Mar 2, 2018 at 8:47 PM, David Zager wrote: >>> >>>> No worries. You were essential to us realizing that what we thought >>>> were release specific broker images were not correct. Thank you for that >>>> and your patience throughout. >>>> >>>> >>>> On Fri, Mar 2, 2018, 14:33 Charles Moulliard >>>> wrote: >>>> >>>>> This is my fault as the docker image docker.io/ansibleplayboo >>>>> kbundle/origin-ansible-service-broker:v3.7 wasn't updated and still >>>>> the old one. >>>>> >>>>> I have redeployed and the problem is gone. Thanks >>>>> >>>>> On Fri, Mar 2, 2018 at 3:24 PM, David Zager wrote: >>>>> >>>>>> Something is not right here. The original error message posted was: >>>>>> >>>>>> [2018-02-28T20:33:59.598Z] [ERROR] - *unable to create network >>>>>> policy object - User >>>>>> "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>>>> create networkpolicies.networking.k8s.io >>>>>> in the namespace "project31": >>>>>> User "system:serviceaccount:openshift-ansible-service-broker:asb" cannot >>>>>> create networkpolicies.networking.k8s.io >>>>>> in project "project31" >>>>>> (post networkpolicies.networking.k8s.io >>>>>> )* >>>>>> >>>>>> and it comes from https://github.com/openshift/a >>>>>> nsible-service-broker/blob/ff1f14a421dbdab5834ebd994615081db >>>>>> 0f09ac5/pkg/runtime/runtime.go#L225 but pkg/runtime/runtime.go does >>>>>> not exist in the v3.7 image: >>>>>> >>>>>> $ docker pull docker.io/ansibleplaybookbundle/origin-ansible-service- >>>>>> broker:v3.7 >>>>>> Trying to pull repository docker.io/ansibleplaybookbundl >>>>>> e/origin-ansible-service-broker ... >>>>>> sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9df6d0321d76b: >>>>>> Pulling from docker.io/ansibleplaybookbundle/origin-ansible-service- >>>>>> broker >>>>>> Digest: sha256:25026da783b7b8777f07fc90fefd037bb785424d5a7f364875e9d >>>>>> f6d0321d76b >>>>>> Status: Image is up to date for docker.io/ansibleplaybookbundl >>>>>> e/origin-ansible-service-broker:v3.7 >>>>>> >>>>>> $ docker run -it --entrypoint /bin/bash >>>>>> docker.io/ansibleplaybookbundle/origin-ansible-service-broker:v3.7 >>>>>> bash-4.2$ ls $GOPATH/src/github.com/openshi >>>>>> ft/ansible-service-broker/pkg/runtime >>>>>> hack.go >>>>>> # Furthermore, searching for that error message in the v3.7 image >>>>>> shows that error doesn't exist in the v3.7 image >>>>>> bash-4.2$ grep -r 'unable to create' $GOPATH/src/github.com/openshi >>>>>> ft/ansible-service-broker/pkg >>>>>> >>>>>> The most likely cause for this is that the broker image was not >>>>>> updated. I am open to other possibilities, could you rule this one out >>>>>> please? >>>>>> >>>>>> Respectfully, >>>>>> David Zager >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Mar 2, 2018 at 9:12 AM Ryan Hallisey >>>>>> wrote: >>>>>> >>>>>>> In case this helps Charles, a temporary work around would be to: oc >>>>>>> edit clusterrole asb-auth >>>>>>> >>>>>>> and add: >>>>>>> >>>>>>> - apiGroups: ["network.openshift.io", ""] >>>>>>> attributeRestrictions: null >>>>>>> resources: ["clusternetworks", "netnamespaces"] >>>>>>> verbs: ["get"] >>>>>>> - apiGroups: ["network.openshift.io", ""] >>>>>>> attributeRestrictions: null >>>>>>> resources: ["netnamespaces"] >>>>>>> verbs: ["update"] >>>>>>> - apiGroups: ["networking.k8s.io", ""] >>>>>>> attributeRestrictions: null >>>>>>> resources: ["networkpolicies"] >>>>>>> verbs: ["create", "delete"] >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> - Ryan >>>>>>> >>>>>>> On Fri, Mar 2, 2018 at 9:03 AM, Charles Moulliard < >>>>>>> cmoullia at redhat.com> wrote: >>>>>>> >>>>>>>> We have redeployed using openshift-ansible playbook ASB using image >>>>>>>> v3.,7 and networkpolicies issue is still there >>>>>>>> >>>>>>>> On Thu, Mar 1, 2018 at 4:19 PM, David Zager >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Greetings Charles, >>>>>>>>> >>>>>>>>> The image in question, docker.io/ansibleplaybookbundl >>>>>>>>> e/origin-ansible-service-broker:v3.7 >>>>>>>>> >>>>>>>>> has been updated to be built using the code from the release-1.0 >>>>>>>>> branch >>>>>>>>> of the broker project. Apologies for the trouble and thank you for helping >>>>>>>>> us find the root cause. >>>>>>>>> >>>>>>>>> https://github.com/openshift/ansible-service-broker/pull/803 should >>>>>>>>> prevent this from happening in the future. >>>>>>>>> >>>>>>>>> Respectfully, >>>>>>>>> David Zager >>>>>>>>> >>>>>>>>> On Thu, Mar 1, 2018 at 9:45 AM Shawn Hurley >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hello Charles, >>>>>>>>>> >>>>>>>>>> It appears that we have had a little mix up on the versions that >>>>>>>>>> we tagged. You are currently getting the canary version of the broker. >>>>>>>>>> We are working on rebuilding and re-tagging the correct images >>>>>>>>>> and will keep everyone informed with this email thread. Sorry about the mix >>>>>>>>>> up. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> >>>>>>>>>> Shawn Hurley >>>>>>>>>> >>>>>>>>>> On Mar 1, 2018, at 12:40 AM, Charles Moulliard < >>>>>>>>>> cmoullia at redhat.com> wrote: >>>>>>>>>> >>>>>>>>>> I confirm that version 3.7 has been installed >>>>>>>>>> >>>>>>>>>> https://www.dropbox.com/s/h7m72h23k7myjyw/Screenshot%202018- >>>>>>>>>> 03-01%2006.39.40.png?dl=0 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Mar 1, 2018 at 12:47 AM, Erik Nelson >>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> Charles, you guys are deploying upstream origin with >>>>>>>>>>> openshift-ansible? We discovered today thanks to your report >>>>>>>>>>> that the >>>>>>>>>>> upstream openshift-ansible code was configured to default to >>>>>>>>>>> "latest" >>>>>>>>>>> broker images, which is our 3.9 image. I will see if I can >>>>>>>>>>> reproduce >>>>>>>>>>> your issue as well. >>>>>>>>>>> >>>>>>>>>>> +1 to shurley's comment, we have to confirm what version of the >>>>>>>>>>> image >>>>>>>>>>> you are running, via tag. >>>>>>>>>>> >>>>>>>>>>> On Wed, Feb 28, 2018 at 6:42 PM, Shawn Hurley < >>>>>>>>>>> shurley at redhat.com> wrote: >>>>>>>>>>> > Hi Charles, >>>>>>>>>>> > >>>>>>>>>>> > v3.7 should not be attempting to anything with network >>>>>>>>>>> policies, can you >>>>>>>>>>> > please double check the deployment config and tell us the >>>>>>>>>>> version of the >>>>>>>>>>> > image that is being deployed. If it is 3.7 then we have >>>>>>>>>>> another issue that >>>>>>>>>>> > we will need to solve. >>>>>>>>>>> > >>>>>>>>>>> > ansible_service_broker_image_tag should override the tag >>>>>>>>>>> value, if that is >>>>>>>>>>> > not working then we will need to do a deeper dive on the >>>>>>>>>>> openshift-ansible >>>>>>>>>>> > code. >>>>>>>>>>> > >>>>>>>>>>> > If you would like to just ?work around? this then you could >>>>>>>>>>> add a cluster >>>>>>>>>>> > role binding and role to grant access to the asb service >>>>>>>>>>> account to >>>>>>>>>>> > manipulate the network policies. >>>>>>>>>>> > >>>>>>>>>>> > Regards, >>>>>>>>>>> > >>>>>>>>>>> > Shawn Hurley >>>>>>>>>>> > >>>>>>>>>>> > On Feb 28, 2018, at 3:44 PM, Charles Moulliard < >>>>>>>>>>> cmoullia at redhat.com> wrote: >>>>>>>>>>> > >>>>>>>>>>> > Hi, >>>>>>>>>>> > >>>>>>>>>>> > There is still an issue with the ansible playbook installing >>>>>>>>>>> ASB on >>>>>>>>>>> > openshift 3.7 >>>>>>>>>>> > When the inventory is configured using these parameters >>>>>>>>>>> > >>>>>>>>>>> > git clone -b release-3.7 git at github.com:openshift/opens >>>>>>>>>>> hift-ansible.git >>>>>>>>>>> > >>>>>>>>>>> > openshift_enable_service_catalog=true >>>>>>>>>>> > ansible_service_broker_registry_whitelist=['.*-apb$'] >>>>>>>>>>> > ansible_service_broker_image_tag=v3.7 >>>>>>>>>>> > >>>>>>>>>>> > then, the following error is reported within the APB pod during >>>>>>>>>>> > serviceinstance creation >>>>>>>>>>> > >>>>>>>>>>> > [2018-02-28T20:33:59.585Z] [NOTICE] - Creating RoleBinding >>>>>>>>>>> > apb-49d8c2a2-6d12-474c-87a2-a220bda6ba0d >>>>>>>>>>> > [2018-02-28T20:33:59.598Z] [ERROR] - unable to create network >>>>>>>>>>> policy object >>>>>>>>>>> > - User "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>>>>> cannot >>>>>>>>>>> > create networkpolicies.networking.k8s.io in the namespace >>>>>>>>>>> "project31": User >>>>>>>>>>> > "system:serviceaccount:openshift-ansible-service-broker:asb" >>>>>>>>>>> cannot create >>>>>>>>>>> > networkpolicies.networking.k8s.io in project "project31" (post >>>>>>>>>>> > networkpolicies.networking.k8s.io) >>>>>>>>>>> > project "project31" (post networkpolicies.networking.k8s.io) >>>>>>>>>>> > >>>>>>>>>>> > As you can see, the clusterrole of asb-auth is still missing >>>>>>>>>>> the following >>>>>>>>>>> > info >>>>>>>>>>> > https://goo.gl/HfJnj8 >>>>>>>>>>> > >>>>>>>>>>> > Can somebody fix the error please for ansible openshift 3.7 ? >>>>>>>>>>> > >>>>>>>>>>> > Regards >>>>>>>>>>> > >>>>>>>>>>> > Charles >>>>>>>>>>> > _______________________________________________ >>>>>>>>>>> > Ansible-service-broker mailing list >>>>>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > _______________________________________________ >>>>>>>>>>> > Ansible-service-broker mailing list >>>>>>>>>>> > Ansible-service-broker at redhat.com >>>>>>>>>>> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>>>> > >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Ansible-service-broker mailing list >>>>>>>>>> Ansible-service-broker at redhat.com >>>>>>>>>> https://www.redhat.com/mailman/listinfo/ansible-service-broker >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 Sat Mar 3 15:15:54 2018 From: rhallise at redhat.com (rhallise at redhat.com) Date: Sat, 03 Mar 2018 15:15:54 +0000 Subject: [Ansible-service-broker] Invitation: Automation Broker IRC meeting @ Weekly from 9:30am to 10:30am on Tuesday (EST) (ansible-service-broker@redhat.com) Message-ID: <001a114af194b6354005668391ab@google.com> You have been invited to the following event. Title: Automation Broker IRC meeting https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit#heading=h.12ew608coolu Freenode: #asbroker When: Weekly from 9:30am to 10:30am on Tuesday Eastern Time 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=NnQ0NjkwdmI4djlxazcxbGs3cGVhM2psMGEgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjcmhhbGxpc2VAcmVkaGF0LmNvbWM5ZmIzNTRjYmQ0NWQ5NzJjMjU2MDkyODUxYTE5MWYzNzEzM2RjNzA&ctz=America/New_York&hl=en 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: 2030 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2085 bytes Desc: not available URL: From rhallise at redhat.com Tue Mar 6 15:42:19 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Tue, 6 Mar 2018 10:42:19 -0500 Subject: [Ansible-service-broker] 3/6/18 meeting logs Message-ID: ========================== #asbroker: asbroker 3/6/18 ========================== Meeting started by rhallisey at 14:31:16 UTC. The full logs are attached. Meeting summary --------------- * Attendance (rhallisey, 14:31:33) * News (rhallisey, 14:33:07) * LINK: https://wiki.debian.org/MeetBot (rhallisey, 14:34:17) * rhallisey needs to fix brokerbot (rhallisey, 14:35:28) * LINK: https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit# (rhallisey, 14:36:21) * Bugs/Issus triage (rhallisey, 14:36:57) * LINK: https://github.com/openshift/ansible-service-broker/issues/789 (rhallisey, 14:37:09) * LINK: https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/240 (dymurray, 14:38:46) * ACTION: rhallisey: to post wip patch (rhallisey, 14:41:39) * ACTION: shurley: assign himself and push it over the finish line (rhallisey, 14:42:05) * LINK: https://github.com/openshift/ansible-service-broker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug (rhallisey, 14:42:44) * LINK: https://github.com/openshift/ansible-service-broker/issues/347 (rhallisey, 14:44:36) * LINK: https://github.com/openshift/ansible-service-broker/issues/351 (rhallisey, 14:46:21) * duplicate of: https://github.com/openshift/ansible-service-broker/issues/576 (rhallisey, 14:48:15) * ACTION: community needs to follow up on issue (rhallisey, 14:51:24) * LINK: https://github.com/openshift/ansible-service-broker/issues/531 (rhallisey, 14:51:39) * ACTION: maleck13: see if https://github.com/openshift/ansible-service-broker/issues/531 is still occurring (rhallisey, 14:55:02) * LINK: jmhttps:// github.com/openshift/ansible-service-broker/issues?utf8=?&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug (rhallisey, 14:55:27) * LINK: https://github.com/openshift/ansible-service-broker/issues?utf8=?&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug (rhallisey, 14:55:41) * LINK: https://github.com/openshift/ansible-service-broker/issues/585 (rhallisey, 14:55:59) * ACTION: ernelson: check if https://github.com/openshift/ansible-service-broker/issues/585 is fixed and close it (rhallisey, 14:57:51) * Features (rhallisey, 14:58:32) * LINK: https://github.com/openshift/ansible-service-broker/issues/812 (rhallisey, 14:58:39) * LINK: https://github.com/openshift/ansible-service-broker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Afeature (rhallisey, 15:04:52) * 3.10 features (rhallisey, 15:04:59) * LINK: https://github.com/openshift/ansible-service-broker/issues/470 (rhallisey, 15:06:07) * ACTION: jmrodri to look at https://github.com/openshift/ansible-service-broker/issues/470 (rhallisey, 15:07:43) * LINK: https://github.com/openshift/ansible-service-broker/issues/501 (rhallisey, 15:09:05) * ACTION: close https://github.com/openshift/ansible-service-broker/issues/501 and create a new granular issue after vendoring discussion (rhallisey, 15:12:03) * LINK: https://github.com/openshift/ansible-service-broker/issues/530 (rhallisey, 15:12:17) * ACTION: community reviews needed on proposal https://github.com/openshift/ansible-service-broker/pull/809 (rhallisey, 15:13:32) * LINK: https://github.com/openshift/ansible-service-broker/issues/590 (rhallisey, 15:13:49) * LINK: https://github.com/openshift/ansible-service-broker/issues/614 (rhallisey, 15:15:47) * Open Discussion (rhallisey, 15:17:52) * LINK: https://www.contributor-covenant.org/ (jmrodri, 15:18:24) * LINK: https://github.com/kubernetes/community/blob/master/code-of-conduct.md (shurley, 15:20:57) * ACTION: jmrodri and shurley will work on drafting Code of Conduct (rhallisey, 15:20:58) * LINK: https://github.com/ansibleplaybookbundle/hello-world-apb/pull/3 (dzager, 15:23:45) * LINK: https://github.com/ansible/ansible/pull/36789 (dymurray, 15:24:13) * LINK: https://github.com/ansibleplaybookbundle/apb-test-shim to see the APB testing shim and an example .travis.yml for APB devs to get started (dzager, 15:26:08) * ACTION: dzager get hello-world-apb merged (dzager, 15:27:42) * ACTION: rhallisey figure out where to host logs (rhallisey, 15:30:40) Meeting ended at 15:30:58 UTC. Action items, by person ----------------------- * dzager * dzager get hello-world-apb merged * ernelson * ernelson: check if https://github.com/openshift/ansible-service-broker/issues/585 is fixed and close it * jmrodri * jmrodri to look at https://github.com/openshift/ansible-service-broker/issues/470 * jmrodri and shurley will work on drafting Code of Conduct * maleck13 * maleck13: see if https://github.com/openshift/ansible-service-broker/issues/531 is still occurring * rhallisey * rhallisey: to post wip patch * rhallisey figure out where to host logs * shurley * shurley: assign himself and push it over the finish line * jmrodri and shurley will work on drafting Code of Conduct * **UNASSIGNED** * community needs to follow up on issue * close https://github.com/openshift/ansible-service-broker/issues/501 and create a new granular issue after vendoring discussion * community reviews needed on proposal https://github.com/openshift/ansible-service-broker/pull/809 People present (lines said) --------------------------- * rhallisey (161) * jmrodri (82) * brokerbot (55) * ernelson (44) * shurley (30) * dzager (21) * dymurray (19) * maleck13 (17) * lorbus (11) * dwhatley (1) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- 14:31:16 #startmeeting asbroker 3/6/18 14:31:16 Meeting started Tue Mar 6 14:31:16 2018 UTC and is due to finish in 60 minutes. The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:31:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:31:16 The meeting name has been set to 'asbroker_3_6_18' 14:31:16 rhallisey: Error: "startmeeting" is not a valid command. 14:31:33 #topic Attendance 14:31:33 rhallisey: Error: "topic" is not a valid command. 14:31:38 hey folks 14:31:51 hey everyone :) 14:31:54 everyone sound off 14:31:56 Hey guys 14:31:57 please :) 14:32:03 zing 14:32:04 morning 14:32:08 hey 14:32:13 el capitan here 14:32:37 hello 14:32:44 jmrodri + long hair + goatee = Captain Morgan...hmm 14:32:49 Hello 14:33:07 #topic News 14:33:07 rhallisey: Error: "topic" is not a valid command. 14:33:22 welcome to broker's first irc meeting! 14:33:23 woo 14:33:29 +1 14:33:35 \o/ 14:33:37 yay! 14:33:38 first thing I want to do is talk about the bot 14:33:54 as you can see, the bot is splitting out some errors 14:34:07 so just ignore it for now and I'll get it fixed 14:34:17 #link https://wiki.debian.org/MeetBot 14:34:17 rhallisey: Error: "link" is not a valid command. 14:34:29 these are a list of command that you can use with the bot 14:34:53 that's fascinating. 14:34:57 when you want something recorded in the minutes, use the 'Commands for Everyone' section 14:35:05 for example 14:35:28 #info rhallisey needs to fix brokerbot 14:35:28 rhallisey: Error: "info" is not a valid command. 14:35:36 that will be recorded for the summary 14:35:54 so feel free to use those as needed when we cover topics 14:36:18 oh one more thing 14:36:21 #link https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit# 14:36:21 rhallisey: Error: "link" is not a valid command. 14:36:33 google doc for the meeting structure 14:36:44 add things as we go through if needed 14:36:57 #topic Bugs/Issus triage 14:36:57 rhallisey: Error: "topic" is not a valid command. 14:37:09 #link https://github.com/openshift/ansible-service-broker/issues/789 14:37:09 rhallisey: Error: "link" is not a valid command. 14:37:33 first issue to talk about is loading multiple specs 14:37:48 for a short summary 14:38:17 we load specs from the endpoint images, (oc get images) 14:38:23 wow, that looks like a crazy oen. 14:38:25 one 14:38:46 #link https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/240 14:38:46 dymurray: Error: "link" is not a valid command. 14:38:47 but, the correct spec to load is only the latest image not all the images 14:38:52 thank you dymurray 14:39:15 dymurray, has a workaround to delete the images after we push 14:39:18 ^^ I submitted the above PR to help developers remove locally pushed images for this reason just as an FYI 14:39:30 I still think that we should fix this in the registry IMO 14:39:38 +1 14:39:41 shurley: +1 14:39:45 shurley, agree, because what if you aren't using apb push 14:40:05 I can take this bug if no other takers? 14:40:09 shurley: by registry you mean the registry adapters? 14:40:16 correct 14:40:40 Well, TBF the only concern I have is that someone could delete an imagestream and still have the associated image in the internal registry. We just need to document how the broker functions to avoid confusion 14:40:42 shurley, I believe I have a WIP that I can post that can help get this started 14:40:44 +1 making sure I'm on the same page, registry is such an overloaded term. 14:40:45 iirc 14:41:15 A broker will only bootstrap an APB if it has an associated ImageStream... if we go with this fix 14:41:25 so let's add assignees to that issue. Add links to WIP, etc. 14:41:39 #action rhallisey: to post wip patch 14:41:39 rhallisey: Error: "action" is not a valid command. 14:41:58 Assigned to myself 14:42:05 #action shurley: assign himself and push it over the finish line 14:42:05 rhallisey: Error: "action" is not a valid command. 14:42:09 thanks shurley 14:42:44 #link https://github.com/openshift/ansible-service-broker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug 14:42:44 rhallisey: Error: "link" is not a valid command. 14:42:52 next item is 3.10 issues 14:43:02 bigger than I thought 14:43:04 this is the list of open 3.10 issues 14:43:32 can we start from the bottom (oldest ones first)? 14:43:50 sure, but just some ground rules 14:43:56 okay 14:44:01 first I want to get a target release for these 14:44:09 lets 1) make sure it's a bug 14:44:18 2) make sure 3.10 makes sense 14:44:31 so starting from the bottom 14:44:36 #link https://github.com/openshift/ansible-service-broker/issues/347 14:44:36 rhallisey: Error: "link" is not a valid command. 14:44:45 +1 to those rules. I was particularly interested in rule #1 :) 14:44:59 this issue has been lingering for a while 14:45:07 Some of these are relevant, but shouldn't be considered blockers to 3.10 14:45:30 it's not simple IIRC, and not sure how problematic is has been recently. 14:45:37 I would not do this in 3.10 14:45:40 ok 14:45:47 let's kick this to 3.11 14:45:49 I agree 14:45:53 +1 14:46:07 +1 14:46:10 +1 14:46:21 #link https://github.com/openshift/ansible-service-broker/issues/351 14:46:21 rhallisey: Error: "link" is not a valid command. 14:46:51 this is probably related to the highly privileged work going on for 3.10 14:46:51 is this where the APB container image is running as root? 14:46:56 I think this is something we should be addressing soon... ability to declare permissions 14:46:57 I think this is related to kubevirt 14:47:09 kubevirt is able to run with privilaged 14:47:16 from the broker? 14:47:21 I think this is a dup 14:47:32 Sounds like this needs to stay for 3.10 if this is part of the kubevirt work. 14:47:40 ernelson: +1 14:47:51 Should any container image on OpenShift be accessing /root directories? 14:47:59 if it is a dupe, let's link to it in the issue. 14:48:12 dzager, if the administrator allows it yes 14:48:15 #info duplicate of: https://github.com/openshift/ansible-service-broker/issues/576 14:48:15 rhallisey: Error: "info" is not a valid command. 14:48:35 you can make the apb privilaged if you use the login work around 14:48:58 I'm not sure that those are duplicates 14:49:01 rhallisey, right but this issue is really tracking the APBs ability to declare elevated permission requirements right? 14:49:29 Ideally instead of doing the workaround we actually bake this into the APB itself 14:49:56 +1 14:49:57 That way we can control which APBs are displayed to which users etc 14:50:16 -1 that is not as easy right now 14:50:31 I know... just thinking long term. Understand that would require svcat changes 14:50:38 ok let's follow up on this issue then 14:50:41 should we move this to a deep dive session instead? I think we should focus on is it a bug? should it be on 3.10, and assignees for now. 14:50:42 ok, just making sure 14:50:47 I don't want to spend to mush time on the details 14:50:54 I think it's a bug and it targets 3.10 14:50:58 folks agree with that? 14:51:03 +1 sounds good 14:51:05 ok 14:51:09 jmrodri: +1, we have design sessions scheduled for this for 3.10 14:51:24 #action community needs to follow up on issue 14:51:24 rhallisey: Error: "action" is not a valid command. 14:51:39 #link https://github.com/openshift/ansible-service-broker/issues/531 14:51:39 rhallisey: Error: "link" is not a valid command. 14:52:21 seems like they can't get the route during an unbind. 14:52:24 maleck13, you reported this 14:52:38 rhallisey: looking 14:52:39 is it possible something is removed by the time this gets run? 14:52:46 * jmrodri waits for maleck13 input 14:53:29 jmrodri: that would a not found error not a forbidden error I think 14:53:48 I haven't seen that issue for some time, I will take an action to attempt to reproduce to ensure it is still a bug 14:53:49 shurley: good point 14:54:09 should we close for now and maleck13 can reopen if confirmed? 14:54:13 or leave open? 14:54:21 #action maleck13: see if it's still occurring 14:54:21 rhallisey: Error: "action" is not a valid command. 14:54:31 happy to close for now 14:54:36 ok wfm 14:54:43 #undo 14:54:43 Removing item from minutes: #action maleck13: see if it's still occurring 14:54:43 rhallisey: Error: "undo" is not a valid command. 14:54:59 rhallisey: we started the bug issue topic at 9:36, agenda has it for 20 minutes. We have 2 minutes left. 14:55:02 #action maleck13: see if https://github.com/openshift/ansible-service-broker/issues/531 is still occurring 14:55:02 rhallisey: Error: "action" is not a valid command. 14:55:17 jmrodri, we'll do 1 more 14:55:22 closed 14:55:27 #link jmhttps://github.com/openshift/ansible-service-broker/issues?utf8=?&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug 14:55:27 rhallisey: Error: "link" is not a valid command. 14:55:28 rhallisey: +1 14:55:32 #undo 14:55:32 rhallisey: Error: "undo" is not a valid command. 14:55:41 #link https://github.com/openshift/ansible-service-broker/issues?utf8=?&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug 14:55:41 rhallisey: Error: "link" is not a valid command. 14:55:50 #undo 14:55:50 rhallisey: Error: "undo" is not a valid command. 14:55:59 #link https://github.com/openshift/ansible-service-broker/issues/585 14:55:59 rhallisey: Error: "link" is not a valid command. 14:56:02 ok that's the one 14:56:17 I believe this should be resolved? 14:56:31 I think we started tagging things properly. 14:56:35 didn't you do that dzager ? 14:56:38 maybe I jumped the gun, but it sounds related to us tagging things 14:56:47 ernelson: that's what I thought as well 14:56:51 yes, this was also fixed in openshift-ansible 14:56:54 > @jmontleon sounds like this may still be an issue we gotta look into. 14:57:11 reading 14:57:19 rhallisey: this is as of a few days ago 14:57:27 I think we need to confirm, happy to do that 14:57:30 ernelson, awesome 14:57:33 belongs in 3.10 though 14:57:51 #action ernelson: check if https://github.com/openshift/ansible-service-broker/issues/585 is fixed and close it 14:57:51 rhallisey: Error: "action" is not a valid command. 14:58:09 ok we're moving on to features 14:58:13 for posterity, the root issue was that we were setup to deploy "latest" often, which ended up pointing at 3.9 images in the 3.7 branch. 14:58:30 rhallisey: +1 14:58:32 #topic Features 14:58:32 rhallisey: Error: "topic" is not a valid command. 14:58:39 #link https://github.com/openshift/ansible-service-broker/issues/812 14:58:39 rhallisey: Error: "link" is not a valid command. 14:58:46 maleck13, I believe this is you 14:58:57 nope I'm wrong 14:59:11 :) 14:59:17 this is required for 3.10 14:59:22 maleck13, did you have a feature in there? I may have wrote over it 14:59:47 or, appropriately tagged for 3.10. I'm not certain it's a required prereq for accomplishing kubevirt 14:59:48 rhallisey: I did but removed it as the proposal is already labelled 3.10 and had feedback on it 14:59:52 ok anyway, I reported this because in kubevirt some folks wanted to enable nested virt in the apb 15:00:00 maleck13, +! 15:00:02 +1 15:00:09 rhallisey: WOW! 15:00:34 I pushed back a little, but it got me thinking that we don't allow anyone to mount in volumes 15:00:53 for nested virt it would need to mount in /lib/modules 15:01:21 do folks think this needs a proposal? 15:01:27 for my edification, this is a container with nested virt in it? 15:01:27 would that be a volume from another namespace then? 15:01:41 rhallisey: +1 to proposal, seems big 15:01:42 rhallisey: +1 definitely. we also need the security team's blessing on that 15:01:47 ernelson: +1 15:01:51 jmrodri, it enables nested virt on the host machine 15:01:58 It seems quite broad a proposal sounds good to me to narrow down the scope and use cases +1 15:02:21 ok thanks folks. We'll with a proposal 15:02:24 agreed, I'd like to see a solid problem statement explaining the requirement 15:02:39 Is this required for 3.10 though? 15:02:39 an example use case might help 15:02:42 I would contend #812 should be kicked to 3.11 maleck13's proposal is slightly different with respect to mounting volumes 15:02:53 shurley: I would say no, but I'll let rhallisey confirm. 15:02:57 shurley, I was about to ask that. What do folks think ? 15:03:11 I don't think it needs to be 3.10 15:03:18 the proposal can be done for 3.10, but the implementation should be left for 3.11 15:03:21 We have a mandate for kubevirt in 3.10 I believe, is this a blocker for that effort? 15:03:25 I don't think it is trivial 15:03:47 is it a blocker for kubevirt ^ +1 15:03:56 it's not 15:04:03 * dzager votes 3.11 15:04:04 they can enable nested virt without an apb 15:04:11 sounds like it can get pushed then. 15:04:19 ok moving to 3.11 15:04:21 dzager: I second that 15:04:24 sold 3.11 15:04:28 I vote 3.12 15:04:29 +1 15:04:46 shurley: so 3.11 +1 :) 15:04:52 #link https://github.com/openshift/ansible-service-broker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Afeature 15:04:52 rhallisey: Error: "link" is not a valid command. 15:04:59 #info 3.10 features 15:04:59 rhallisey: Error: "info" is not a valid command. 15:05:04 shurley: I guess taht would make it 4.11. oh well, joke fail 15:05:29 we'll start at the bottom again 15:05:35 1) will it make 3.10 15:05:43 2) does it need a proposal 15:05:55 3) who's taking it 15:05:59 +1 15:06:05 +1 15:06:07 #link https://github.com/openshift/ansible-service-broker/issues/470 15:06:07 rhallisey: Error: "link" is not a valid command. 15:06:44 I think we just need to add the user and the service id for this one I say it stays in 3.10 15:06:58 yeah this is pretty straightforward 15:06:59 this may be a quick patch 15:06:59 shurley: +1 15:07:01 +1 15:07:10 ok we'll keep it 15:07:19 anyone interested in working on this? 15:07:20 I can look at this one 15:07:28 service instance id is already there, you are only missing the user 15:07:36 dzager: even better 15:07:43 #action jmrodri to look at https://github.com/openshift/ansible-service-broker/issues/470 15:07:43 rhallisey: Error: "action" is not a valid command. 15:08:03 #link https://github.com/openshift/ansible-service-broker/issues/501 15:08:03 rhallisey: Error: "link" is not a valid command. 15:08:11 #undo 15:08:11 Removing item from minutes: #link https://github.com/openshift/ansible-service-broker/issues/501 15:08:11 rhallisey: Error: "undo" is not a valid command. 15:08:26 DOH! did brokerbot kick ryan 15:08:40 DOH! did brokerbot kick ryan 15:08:42 woops 15:08:47 brokerbot++ 15:08:50 was in the wrong window 15:08:53 rhallisey: you had the entire row here LOLing 15:09:05 #link https://github.com/openshift/ansible-service-broker/issues/501 15:09:05 rhallisey: Error: "link" is not a valid command. 15:09:10 ok that one 15:09:22 this refactor is sort of happening in different areas 15:09:29 3.10 make sense? 15:09:35 I'm not 100% sure if I'd make it a 3.10 blocker though 15:09:39 I would consider this closed with my refactoring work honestly 15:09:40 feels like a 3.10 nice to have 15:09:48 ernelson: even better :) 15:10:03 it condensed the shared behavior, or do we think there's further work to be done here? 15:10:05 ernelson: I wouldn't just yet 15:10:16 we may touch in this some more in coming weeks 15:10:22 I think the APB package still has exported types that should not be exported 15:10:32 I agree shurley 15:10:39 let's leave it open until we have vendor discussions. 15:10:43 Feels like we need to get finer grained with this issue then with work items? 15:10:45 +1 15:10:48 Right now it's a little vague 15:10:48 +1 15:10:55 +1 15:10:58 ernelson: +1 15:11:05 +1 15:11:05 should we create finer issues then? 15:11:12 or just add work items to this issue? 15:11:16 I'm fine either way 15:11:25 can we fold this into another issue? 15:11:30 since it's a specific pkg 15:11:32 do we want to close and just make sure that we create a finer grained issue from the vendor discussion? 15:11:42 shurley: ack, +1 15:11:48 shurley: that sounds better 15:12:03 #action close https://github.com/openshift/ansible-service-broker/issues/501 and create a new granular issue after vendoring discussion 15:12:03 rhallisey: Error: "action" is not a valid command. 15:12:17 #link https://github.com/openshift/ansible-service-broker/issues/530 15:12:17 rhallisey: Error: "link" is not a valid command. 15:12:33 maleck13, I think this may be what you had linked earlier 15:12:44 yes this is covered by my proposal 15:12:53 okay leave this for 3.10 15:12:56 I would like to aim to get it into 3.10 15:12:58 +1 15:13:06 ok this is all set 15:13:08 +1 15:13:16 nice job maleck13 15:13:19 It's assigned to me to keep tracking it. 15:13:32 #action community reviews needed on proposal https://github.com/openshift/ansible-service-broker/pull/809 15:13:32 rhallisey: Error: "action" is not a valid command. 15:13:49 #link https://github.com/openshift/ansible-service-broker/issues/590 15:13:49 rhallisey: Error: "link" is not a valid command. 15:14:25 shurley, should this be 3.10 15:14:50 3.11 unless someone wants to take this. I don't think I'll have the time and it is just a nice to have IMO 15:15:07 any takers? 15:15:08 shurley: +1 15:15:24 if there are, assign yourself 15:15:25 let's move to 3.11 for now. 15:15:38 1 more feature 15:15:47 #link https://github.com/openshift/ansible-service-broker/issues/614 15:15:47 rhallisey: Error: "link" is not a valid command. 15:15:53 this is a good one 15:16:18 3.10? and do we need a proposal? 15:16:34 I can look at this one, I remember doing the recover stuff. 15:16:41 and +1 to proposal 15:16:44 +1 15:16:44 yes, and yes I think 15:16:48 +1 15:17:01 ok thank jmrodri 15:17:03 thanks 15:17:17 * jmrodri will have to double check what I've signed up for :) 15:17:33 rhallisey: I think we've reached the time limit for features 15:17:43 #link Open Discussion 15:17:43 rhallisey: Error: "link" is not a valid command. 15:17:47 #undo 15:17:47 Removing item from minutes: #link Open 15:17:47 rhallisey: Error: "undo" is not a valid command. 15:17:52 #topic Open Discussion 15:17:52 rhallisey: Error: "topic" is not a valid command. 15:18:12 there's an item here for drafting a code of conduct 15:18:22 I believe there was precendence for using the contributor covenant 15:18:24 https://www.contributor-covenant.org/ 15:18:27 the 3rd in the list 15:18:35 how do we want to tackle this process? 15:18:39 jmrodri: what is the precedence? 15:18:41 * dzager votes using contributor covenant 15:18:45 RH legal :) 15:18:53 :) +1 15:18:56 I will confirm with RH legal if there are any issues 15:18:59 I would suggest doing whatever openshift is doing 15:19:05 But it doesn't look like they actually have one. 15:19:08 ernelson: makes sense 15:19:27 do they use k8s maybe 15:19:33 if they don't have any issues with any of the 3, then we can pick whichever one suits our needs. 15:19:34 so possibly just k8s 15:19:34 +1 I would prefer to do the cncf if our stuff is maybe going to go into k8s/sig-apps then we should be using theres 15:19:39 maybe we can start with that code of conduct? 15:19:39 maleck13: yeah 15:19:53 otherwise, I will defer to their decision. 15:19:54 shurley: is cncf == k8s? 15:19:59 yes 15:20:03 who wants to create draft for this? 15:20:14 create a draft* 15:20:17 +1 for cncf, I don't think we need to be drafting this ourselves 15:20:22 rhallisey: I will work with RH legal and shurley :) 15:20:40 +1 cncf 15:20:57 https://github.com/kubernetes/community/blob/master/code-of-conduct.md 15:20:58 #action jmrodri and shurley will work on drafting Code of Conduct 15:20:58 rhallisey: Error: "action" is not a valid command. 15:21:13 and by drafting I mean picking an existing one :) 15:21:19 +1000 15:21:24 sounds good 15:21:33 shurley: +0.1 15:21:39 because if I came up with one it would not be very kind :) Torvalds Code of Conduct :) 15:21:51 that's all I have on the agenda folks. Does anyone want to talk about anything else 15:22:09 I'm good, thanks rhallisey for putting this together. 15:22:15 all good from me. Thanks for this 15:22:18 thanks brokerbot for not hurting rhallisey 15:22:19 just a small q about the new APB structure 15:22:19 +1 15:22:30 lorbus: okay go for it 15:22:33 hey lorbus, go ahead 15:22:38 rhallisey: thank you! very productive. 15:23:04 I assume it is going to be merged soon and I can base my stuff on it already? 15:23:21 lorbus: you are referring to https://github.com/ansibleplaybookbundle/hello-world-apb/pull/3 right? 15:23:29 yes :) 15:23:32 dzager, you the command :) 15:23:36 use* 15:23:42 for links 15:23:45 #link https://github.com/ansibleplaybookbundle/hello-world-apb/pull/3 15:23:45 dzager: Error: "link" is not a valid command. 15:23:48 thanks 15:24:13 #link https://github.com/ansible/ansible/pull/36789 15:24:13 dymurray: Error: "link" is not a valid command. 15:24:14 dzager: is that official yet? 15:24:15 lorbus: yeah, that should be merged shortly. 15:24:26 It's also worth mentioning we are moving to a format that works with Galaxy as well 15:24:35 cool! 15:24:45 So a lot of APB directory changes coming down the pipeline. Mainly just trying to enforce the contract that mhrivnak is working on 15:25:09 nice good stuff 15:25:22 jmrodri: well, until Ansible 2.5 comes out, no to the k8s_raw stuff, but the structure of the APB I would say yes 15:25:37 so does that mean lorbus can start basing his apbs on it? or wait? 15:26:08 #link https://github.com/ansibleplaybookbundle/apb-test-shim to see the APB testing shim and an example .travis.yml for APB devs to get started 15:26:08 dzager: Error: "link" is not a valid command. 15:26:15 so k8s_raw won't be ready until Ansible 2.5 or even after? 15:26:41 lorbus: k8s_raw is Ansible 2.5 (it's already into ansible/ansible master) 15:27:02 you are welcome to use apb-base:canary to access k8s_raw module 15:27:18 that'll work, awesome! :) 15:27:42 #action dzager get hello-world-apb merged 15:27:42 dzager: Error: "action" is not a valid command. 15:27:46 does anyone else have anything else to discuss? 15:27:56 thanks for bringing that up lorbus 15:28:12 np :) 15:28:29 some additional info about this meeting and we'll close it out 15:28:34 I'll post the logs on the ML 15:29:19 during the week leading up to the next meeting try and fill out the meeting template with discussion items 15:29:31 rhallisey: where are the logs going to be hosted? 15:29:45 ernelson, I haven't figured that out yet 15:29:50 It would be nice to get them onto an apache server somewhere 15:29:54 is there a .cal file hosted somewhere to sync the dates? 15:29:56 I was hoping to host on fedora but I didnt get that bot working 15:30:00 we might have some extra spots to put it 15:30:24 actually, those are internal to the RH network, probably want to host it publically somewhere 15:30:29 ya 15:30:40 #action rhallisey figure out where to host logs 15:30:40 rhallisey: Error: "action" is not a valid command. 15:30:43 ernelson: +1 I think fedora can do it even in one of our accounts. 15:30:45 +1 for leveraging fedora infra 15:30:50 I think I can host some on my fedora people page 15:30:54 ok folks that all the time we have 15:30:55 +1 15:30:58 #endmeeting -------------- next part -------------- ========================== #asbroker: asbroker 3/6/18 ========================== Meeting started by rhallisey at 14:31:16 UTC. The full logs are available at asbroker/2018/asbroker.2018-03-06-14.31.log.html . Meeting summary --------------- * Attendance (rhallisey, 14:31:33) * News (rhallisey, 14:33:07) * LINK: https://wiki.debian.org/MeetBot (rhallisey, 14:34:17) * rhallisey needs to fix brokerbot (rhallisey, 14:35:28) * LINK: https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit# (rhallisey, 14:36:21) * Bugs/Issus triage (rhallisey, 14:36:57) * LINK: https://github.com/openshift/ansible-service-broker/issues/789 (rhallisey, 14:37:09) * LINK: https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/240 (dymurray, 14:38:46) * ACTION: rhallisey: to post wip patch (rhallisey, 14:41:39) * ACTION: shurley: assign himself and push it over the finish line (rhallisey, 14:42:05) * LINK: https://github.com/openshift/ansible-service-broker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug (rhallisey, 14:42:44) * LINK: https://github.com/openshift/ansible-service-broker/issues/347 (rhallisey, 14:44:36) * LINK: https://github.com/openshift/ansible-service-broker/issues/351 (rhallisey, 14:46:21) * duplicate of: https://github.com/openshift/ansible-service-broker/issues/576 (rhallisey, 14:48:15) * ACTION: community needs to follow up on issue (rhallisey, 14:51:24) * LINK: https://github.com/openshift/ansible-service-broker/issues/531 (rhallisey, 14:51:39) * ACTION: maleck13: see if https://github.com/openshift/ansible-service-broker/issues/531 is still occurring (rhallisey, 14:55:02) * LINK: jmhttps://github.com/openshift/ansible-service-broker/issues?utf8=?&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug (rhallisey, 14:55:27) * LINK: https://github.com/openshift/ansible-service-broker/issues?utf8=?&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Abug (rhallisey, 14:55:41) * LINK: https://github.com/openshift/ansible-service-broker/issues/585 (rhallisey, 14:55:59) * ACTION: ernelson: check if https://github.com/openshift/ansible-service-broker/issues/585 is fixed and close it (rhallisey, 14:57:51) * Features (rhallisey, 14:58:32) * LINK: https://github.com/openshift/ansible-service-broker/issues/812 (rhallisey, 14:58:39) * LINK: https://github.com/openshift/ansible-service-broker/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A3.10+label%3Afeature (rhallisey, 15:04:52) * 3.10 features (rhallisey, 15:04:59) * LINK: https://github.com/openshift/ansible-service-broker/issues/470 (rhallisey, 15:06:07) * ACTION: jmrodri to look at https://github.com/openshift/ansible-service-broker/issues/470 (rhallisey, 15:07:43) * LINK: https://github.com/openshift/ansible-service-broker/issues/501 (rhallisey, 15:09:05) * ACTION: close https://github.com/openshift/ansible-service-broker/issues/501 and create a new granular issue after vendoring discussion (rhallisey, 15:12:03) * LINK: https://github.com/openshift/ansible-service-broker/issues/530 (rhallisey, 15:12:17) * ACTION: community reviews needed on proposal https://github.com/openshift/ansible-service-broker/pull/809 (rhallisey, 15:13:32) * LINK: https://github.com/openshift/ansible-service-broker/issues/590 (rhallisey, 15:13:49) * LINK: https://github.com/openshift/ansible-service-broker/issues/614 (rhallisey, 15:15:47) * Open Discussion (rhallisey, 15:17:52) * LINK: https://www.contributor-covenant.org/ (jmrodri, 15:18:24) * LINK: https://github.com/kubernetes/community/blob/master/code-of-conduct.md (shurley, 15:20:57) * ACTION: jmrodri and shurley will work on drafting Code of Conduct (rhallisey, 15:20:58) * LINK: https://github.com/ansibleplaybookbundle/hello-world-apb/pull/3 (dzager, 15:23:45) * LINK: https://github.com/ansible/ansible/pull/36789 (dymurray, 15:24:13) * LINK: https://github.com/ansibleplaybookbundle/apb-test-shim to see the APB testing shim and an example .travis.yml for APB devs to get started (dzager, 15:26:08) * ACTION: dzager get hello-world-apb merged (dzager, 15:27:42) * ACTION: rhallisey figure out where to host logs (rhallisey, 15:30:40) Meeting ended at 15:30:58 UTC. Action items, by person ----------------------- * dzager * dzager get hello-world-apb merged * ernelson * ernelson: check if https://github.com/openshift/ansible-service-broker/issues/585 is fixed and close it * jmrodri * jmrodri to look at https://github.com/openshift/ansible-service-broker/issues/470 * jmrodri and shurley will work on drafting Code of Conduct * maleck13 * maleck13: see if https://github.com/openshift/ansible-service-broker/issues/531 is still occurring * rhallisey * rhallisey: to post wip patch * rhallisey figure out where to host logs * shurley * shurley: assign himself and push it over the finish line * jmrodri and shurley will work on drafting Code of Conduct * **UNASSIGNED** * community needs to follow up on issue * close https://github.com/openshift/ansible-service-broker/issues/501 and create a new granular issue after vendoring discussion * community reviews needed on proposal https://github.com/openshift/ansible-service-broker/pull/809 People present (lines said) --------------------------- * rhallisey (161) * jmrodri (82) * brokerbot (55) * ernelson (44) * shurley (30) * dzager (21) * dymurray (19) * maleck13 (17) * lorbus (11) * dwhatley (1) Generated by `MeetBot`_ 0.1.4 From dzager at redhat.com Wed Mar 7 15:03:30 2018 From: dzager at redhat.com (David Zager) Date: Wed, 07 Mar 2018 15:03:30 +0000 Subject: [Ansible-service-broker] Sprint 145 Release Notes Message-ID: Bugs - Bug 1538986 - Remove bad enum values from Update Request (#713) - Bug 1541265 - avoid broker panic, check for nil (#723) - Bug 1541335 - fix auth config parsing (#728) - Bug 1540121 - Return 400 for bad update requests (#736) - Bug 1539308 - Do not report errors on dupe depros (#739) - Bug 1542387 - Print out status of response from RHCC registry if not 200 (#742) - Bug 1543029 - last_operation returns correct body with 410 response (#746) - Bug 1541461 - Deal with buggy encoded scopes from service catalog. (#754) - Bug 1543521 - fix async bind when job already in-progress (#764) - Bug 1539542 - return bindings_retrievable (#776) - Bug 1548311 - Return success on depro extcred miss (#791) - Bug 1550385 - Add .default to proxy docs NO_PROXY (#807) Other Enhancements - No longer only search for apbs that end with -apb (#719) - partial fix for PR #722 Work Item 1 (#725) - initial prop for custom resources. (#722) - Fix vet test (#733) - Make the endpoints headless for local brokers (#731) - Travis merges commits so do a diff against HEAD^ (#737) - Remove redundant validation copy (#741) - Update simple-broker-template to include necessary roles for local_openshift reg (#749) - Add a mailing list subscribe badge (#758) - Remove minishift docs and link to golden source (#672) - Remove upgrade from Ubuntu 14.0 to 16.04 (#762) - Add a warning that the client is an older version (#769) - Proposal for saving extracted credentials (#768) - Remove plan dao methods (#766) - 475 last operation description (#619) - fixing k8s ansible service broker template to include namespace config (#777) - apb pkg public interface overhaul (#773) - Fix last op endpoint unbind response (#765) - rename file to be more consistent. (#779) - Lock asb-brew releaser to 3.10 branch (#788) - Filter everything when whitelist is empty (#781) - Adds docs for installing the broker in minikube. (#792) - Temporarily link to minishift-addons fork (#796) - Save extracted credentials into a secret (#775) - Broker client vendor update (#794) - Remove tmp note re: minishift-addon (#802) - parameterize the 'ansible-service-broker' namespace with the NAMESPACE variable (#800) - Force canary image be built from master (#805) - Broker client dao (#795) - Initial pass at proposal to change subscribers (#727) - Removing links to older fusor GH org (#814) - Adds Service Bundle contract document (#808) - parameterize dao:type. Defaults to etcd (#816) - Document the Broker's versioning strategy (#810) - switching dependency management from glide to dep (#817) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ernelson at redhat.com Fri Mar 9 01:03:09 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 8 Mar 2018 20:03:09 -0500 Subject: [Ansible-service-broker] Default whitelist is now open for the local registry Message-ID: Wanted to call attention to a change we just merged that impacts authors pushing their own APBs. Previously, we had a default whitelist that required "apb push" sourced apb's to be named with an "-apb" suffix before allowing them to be displayed in the catalog. We have relaxed this default setting in our development environments to allow any image name. It became apparent that a lot of folks trying out apb push were understandably unaware of this default expectation, so this is an attempt to help that onboarding experience. Note: this is a configuration setting that broker admins are able to change (make more strict) if desired. The default setting can be found here: https://github.com/openshift/ansible-service-broker/blob/master/templates/deploy-ansible-service-broker.template.yaml#L324 It can be changed on an existing broker by using "oc edit configmap broker-config -n ansible-service-broker", and editing the local registry's white_list regex to your desired whitelist setting. Make sure to apply the new configuration with "oc rollout latest dc/asb". Relevant issue and PR: https://github.com/openshift/ansible-service-broker/issues/823 https://github.com/openshift/ansible-service-broker/pull/827 - Erik From rhallise at redhat.com Mon Mar 12 23:46:31 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Mon, 12 Mar 2018 19:46:31 -0400 Subject: [Ansible-service-broker] IRC meeting Message-ID: <423F10A9-1081-4346-9D43-5D51A400452C@redhat.com> Hey folks, I want to remind everyone to add any discussion topics for tomorrow?s IRC meeting to the google doc. Also, Day light savings has started in the US so for time zones that don?t recognize Day light savings, the meeting will be 1 hour earlier. The calendar invite should reflect the change from EST to EDT. - Ryan From rhallise at redhat.com Tue Mar 13 14:45:52 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Tue, 13 Mar 2018 10:45:52 -0400 Subject: [Ansible-service-broker] Meeting Notes: 3/13/18 Message-ID: ==================================== #asbroker: Automation Broker 3-13-18 ==================================== Meeting started by rhallisey at 13:31:04 UTC. The full logs are attached . Meeting summary --------------- * Attendance (rhallisey, 13:31:20) * News (rhallisey, 13:32:55) * LINK: https://github.com/ansible/ansible/pull/36789 (rhallisey, 13:35:06) * ACTION: dymurray: document https://github.com/ansible/ansible/pull/36789 (rhallisey, 13:36:50) * ACTION: dymurray: also mention new galaxy feature on ML (rhallisey, 13:37:24) * Bugs/Issue triage (rhallisey, 13:37:41) * LINK: https://github.com/openshift/ansible-service-broker/issues/692 (rhallisey, 13:38:09) * ACTION: rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion (rhallisey, 13:46:42) * LINK: https://github.com/openshift/ansible-service-broker/issues/707 (rhallisey, 13:46:56) * LINK: https://github.com/openshift/ansible-service-broker/issues/730 (rhallisey, 13:48:19) * ACTION: rhallisey: switch to using broker release labels (rhallisey, 13:53:07) * LINK: https://github.com/openshift/ansible-service-broker/issues/798 (rhallisey, 13:54:30) * ACTION: community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting (rhallisey, 14:05:53) * Features (rhallisey, 14:06:17) * LINK: https://github.com/openshift/ansible-service-broker/issues/797 (rhallisey, 14:06:25) * ACTION: rhallisey: write up and issue for OSP API and cc interested community members (rhallisey, 14:12:28) * Open Discussion (rhallisey, 14:15:06) * LINK: https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/218 (rhallisey, 14:15:39) * Thoughts on multiple types of binding (rhallisey, 14:22:12) * LINK: https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#types-of-binding (rhallisey, 14:24:18) * Document broker release schedule (rhallisey, 14:30:06) Meeting ended at 14:31:53 UTC. Action Items ------------ * dymurray: document https://github.com/ansible/ansible/pull/36789 * dymurray: also mention new galaxy feature on ML * rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion * rhallisey: switch to using broker release labels * community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting * rhallisey: write up and issue for OSP API and cc interested community members Action Items, by person ----------------------- * dymurray * dymurray: document https://github.com/ansible/ansible/pull/36789 * dymurray: also mention new galaxy feature on ML * rhallisey * rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion * rhallisey: switch to using broker release labels * rhallisey: write up and issue for OSP API and cc interested community members * **UNASSIGNED** * community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting People Present (lines said) --------------------------- * rhallisey (102) * shurley (49) * maleck13 (43) * ernelson (31) * brokerbot (25) * mhrivnak (22) * dymurray (8) * dzager (8) * jmontleon (7) * jmrodri (2) * fabianvf (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- 13:31:04 #startmeeting Automation Broker 3-13-18 13:31:04 Meeting started Tue Mar 13 13:31:04 2018 UTC. The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:31:04 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:31:04 The meeting name has been set to 'automation_broker_3-13-18' 13:31:04 rhallisey: startmeeting startmeeting 13:31:19 nice! no errors! 13:31:20 #topic Attendance 13:31:20 rhallisey: Error: "topic" is not a valid command. 13:31:25 :/ 13:31:35 hey folks 13:31:35 I jinxed you my bad 13:32:03 if your here say hi 13:32:08 Hello 13:32:11 so the bot records it 13:32:12 Hi! 13:32:28 maleck13, around? 13:32:37 rhallisey: yes 13:32:40 hi 13:32:55 #topic News 13:32:55 rhallisey: Error: "topic" is not a valid command. 13:33:14 first things first, google doc: https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit# 13:33:55 The only item I wanted to mention is that the whitelist changed for the local_registry adaptor 13:34:18 it changed to be more permissive, ".*", so it allows everything through 13:34:23 ^I please note I think this is only on the master branch no? 13:34:36 I think so 13:34:56 rhallisey, sorry I put the Galaxy PR in the wrong spot, but would like to call that out 13:35:05 sure 13:35:06 #link https://github.com/ansible/ansible/pull/36789 13:35:06 rhallisey: Error: "link" is not a valid command. 13:35:20 you can now do `ansible-galaxy init --type apb foo-apb` from master to create an APB 13:35:34 +1 nice dymurray 13:35:36 Would love to get people trying that out 13:35:45 oh nice 13:36:03 cool 13:36:05 dymurray, do we have that documented on our side? 13:36:12 +1 13:36:18 rhallisey, its documented in the ansible repo.... I can add a link in our docs +1 13:36:33 I'll add you for an action item 13:36:37 thx 13:36:50 #action dymurray: document https://github.com/ansible/ansible/pull/36789 13:36:50 rhallisey: Error: "action" is not a valid command. 13:36:57 might be worth mentioning on the mailing list also 13:37:24 #action dymurray: also mention new galaxy feature on ML 13:37:24 rhallisey: Error: "action" is not a valid command. 13:37:24 +1 will send out an email once its documented in our repo 13:37:41 #topic Bugs/Issue triage 13:37:41 rhallisey: Error: "topic" is not a valid command. 13:38:07 these are the remaining 3.10 issues we didn't cover from last time 13:38:09 #link https://github.com/openshift/ansible-service-broker/issues/692 13:38:09 rhallisey: Error: "link" is not a valid command. 13:38:41 mhrivnak, around? 13:38:59 hi! 13:38:59 grabbed him 13:39:03 hey mhrivnak 13:39:09 shurley the hero 13:39:26 mhrivnak, just wondering what your thoughts are on that bug? 13:39:57 I think it should be part of a conversation around the service bundle contract definition, and refining that. 13:40:16 As part of that, we'll likely want to separate user-provided input vs. other environmental data that the bundle might need. 13:40:37 And pass them to a bundle as separate objects or subobjects. 13:41:23 do we think that would end up as a breaking change then? or would back compat be maintained 13:41:59 so right now you have a map {'_ap_....':'xxxx', 'userparam': 'xxxx'} like that 13:42:04 Good question, and has scope beyond just this change. It depends. :) 13:42:30 We could keep the current object that's a combo of everything, and introduce new objects that sort them. 13:42:50 what do folks think are the next steps for this? 13:42:52 and we want to change this to be {'bundleParams': { '_apb_..': 'xxx'}, 'UserParams': {...}}? 13:42:53 Or we could use the bundle schema version to know if a bundle wants to receive old-style data or new-style data. 13:42:58 sounds like we need more info 13:43:06 and more discussion around this 13:43:15 I think the next steps are to talk about the service bundle contract top-to-bottom and prioritize what changes we want to make. 13:43:28 And figure out how to do so with backward compatibility. 13:43:36 +1 13:44:15 maybe we can fill a 20min slot in next weeks irc meeting with this? 13:44:19 I am still very confused, sorry you have a broker method to determine if they are equal but this sounds like a contract change between bundle and broker 13:44:43 I am struggling to figure out where the issue is 13:45:16 shurley yes we're doing some stuff on the broker right now to mitigate this, but the fundamental problem is that different kinds of data are being lumped together, and it would be more helpful to separate them. 13:45:53 ok thanks 13:45:56 maybe we can continue this discussion after the meeting 13:46:09 mhrivnak, I'm going to add this to next weeks issue discussion 13:46:14 to fill up this block 13:46:17 rhallisey, sounds good. 13:46:42 #action rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion 13:46:42 rhallisey: Error: "action" is not a valid command. 13:46:56 #link https://github.com/openshift/ansible-service-broker/issues/707 13:46:56 rhallisey: Error: "link" is not a valid command. 13:47:47 this looks pretty straightforward 13:47:57 Ill take it 13:48:07 already assigned myself 13:48:10 perfect 13:48:19 #link https://github.com/openshift/ansible-service-broker/issues/730 13:48:19 rhallisey: Error: "link" is not a valid command. 13:49:06 trying to remember this one 13:49:35 are we just trying to determine if this is in 3.10? I don't think it's required at all, was just something I noticed could be nicer 13:49:57 just determining if we want to discuss it and if it's 3.10 13:50:00 etc... 13:50:05 +1 to all of this. It's a refactor more than a bug report FWIW. 13:50:22 ok let's kick it back to 3.11 then 13:50:26 yeah it's strictly nice to have tech debt 13:50:37 unless you think you can tackle it in the 3.10 timeframe 13:50:41 I shouldve asked that first 13:51:08 ernelson, do you think you can do this for 3.10? 13:51:21 ernelson: TBH this sounds an awful lot like the HTTPStatusError from osb-broker-lib 13:51:36 shurley: it's exactly what I was looking for 13:51:47 I'm happy to help FWIW even if just brainstorming, review, or whatever. I'm interested in learning best practices for this sort of thing in golang. 13:52:05 I've been hoping we can communicate semantic broker cases on a higher level 13:52:18 rhallisey: probably not for 3.10 13:52:25 side question: what is the 3.10 time frame btw 13:52:26 have a lot of catalog work on my plate 13:52:31 I think that this might be "solved" when we can finally use that lib, it is not ready yet, but wondering if we just say we will fix this then? 13:52:37 1 month 13:52:41 I think 13:52:53 thanks 13:52:55 shurley: +1 13:53:02 for "features" bug fixes can be be made after that 13:53:07 #action rhallisey: switch to using broker release labels 13:53:07 rhallisey: Error: "action" is not a valid command. 13:53:28 the labels are tied to openshift, sorry about that 13:53:43 might be wroth documenting our release dates somewhere too 13:53:58 we'll table that until open discussion 13:54:00 +1 would be good 13:54:05 +1 13:54:16 ok so for this one, let's kick it back to 3.11 13:54:30 #link https://github.com/openshift/ansible-service-broker/issues/798 13:54:30 rhallisey: Error: "link" is not a valid command. 13:55:55 we have a difference in opinion on how this should work. I thnk ernelson believes that the executor should panic, while jmrodri thinks it should log an error and not overwrite 13:56:08 sorry back up, does everyone understand the issue/ 13:56:10 ? 13:56:25 can you provide some more issue 13:56:27 info* 13:57:43 so basically the new executor has three methods that are called by itself to end the processing of events. these are finishedWith(success,error) and then there is a update action that is called 13:58:04 update is what is used to send the last op (sorry that is not the actual name doing from memory) 13:58:41 and what happened is if you called finishedWithError but then called update, you could update the executor into a state that is not valid 13:59:13 I would expect that the call to the update method should not do anything if the executor has already been told it should be finished 13:59:48 in this case it was actually the Success overwriting the Error status 13:59:58 my reasoning for a panic is that the case in question is purely developer error, and any time it occurs I would prefer to have an explicit error rather than potentially dangerous and unpredictable behavior 14:00:40 Will the panic here crash the broker though? 14:00:54 or would there be a recover in place 14:00:55 maleck13: yes, deliberately 14:01:16 maleck13: I mean what would you recover too? 14:01:38 it's effectively an assertion 14:01:38 yes it would just be a log of the error I guess without the crash 14:02:43 I would prefer to log (with an error) that this happened with an explanation that the state has already been set to a terminal state (success or error) 14:03:14 and then to ignore that call. 14:03:25 the concern would be if a test case didn't hit this problem then it was hit somehow in the wild 14:03:27 In case a user is the first one to hit this case, if there is any opportunity for the broker to recover and continue, I think it should do so. It can still loudly complain about the problem. 14:03:45 the broker would crash and unless replicated take some time to come back 14:04:00 Panic in a user environment is scary and not confidence-inspiring. Should be a last resort. 14:04:16 We do have the dev mode flag 14:04:20 fair enough, I feel pretty strongly but it seems I am outgunned here. 14:04:23 I'm also hesitant to have it panic 14:04:42 I think we need to get some more discssion on the issue 14:05:02 ^ we should then discuss https://github.com/openshift/ansible-service-broker/issues/753 14:05:09 we can move on and hold that discussion on the issue 14:05:53 #action community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting 14:05:53 rhallisey: Error: "action" is not a valid command. 14:06:03 shurley: IMO, that issue is of a different class, since it's potentially user facing configuration error 14:06:04 we need to move on to features 14:06:08 I think if we are moving to trying to "gracefully" handle things we should at least be consistant 14:06:15 sounds good sorry 14:06:17 #topic Features 14:06:17 rhallisey: Error: "topic" is not a valid command. 14:06:22 whereas the executor hooks are simply a developer problem. 14:06:25 #link https://github.com/openshift/ansible-service-broker/issues/797 14:06:25 rhallisey: Error: "link" is not a valid command. 14:06:36 dynamic params! 14:07:13 maleck13, I've spoken with the UI folks on this. Did you have anything you wanted to bring up about it? 14:07:28 I added this for discussion as I haven't heard anything back from ux yet and we are working around it with the text area approach 14:07:39 would love to hear more 14:07:55 I do like the idea of making YAML input a valid parameter. Not sure if that get's us all the way to dynamic parameters 14:07:57 maleck13, I'll have to cc you on the thread 14:08:09 rhallisey: sounds good 14:08:09 This has to get into the OSB spec right? 14:08:18 shurley, I'm not sure 14:08:28 from the UI folks, they said this would need to be added as metadata 14:08:43 at least considering the idea I put forth 14:08:47 shurley: I don't think that is a requirement, but I think it's important to bring up the use-case with the group 14:08:53 rhallisey: "this" is YAML input or the dynamic parameters part? 14:09:24 dynamic parameters 14:09:37 ernelson: rhallisey correct me if I'm wrong then but that means only openshift-ui would understand those parameters? 14:09:46 yes 14:09:51 shurley: yes 14:09:51 -1 14:09:53 parameter types right now have certain types 14:10:13 let me reprahse that 14:10:37 parameters can only be certain types. That have to be valid json types 14:10:43 as long as bundle author is okay with that then I guess I shouldn't complain, Just think we should call it out for them in case they wanted to work on pure k9s 14:10:46 *k8s 14:10:47 In general, I think we should bring these discussions into SIG to gauge interest and if enough, work it into the spec rather than around it with some kind of metadata 14:11:13 It seems there are use multiple use cases for a parameter display_type of "yaml" or similar. 14:11:26 Proposing that to the SIG sounds like a good next step. 14:11:34 mhrivnak: ernelson +1 14:11:36 +1, can also be used in the Ansible Runner work too 14:11:41 I believe that we should avoid that route if we can. Having the display_type of "yaml" should help here. 14:11:44 ernelson, I agree. I said I would create an issue last meeting, but haven't had the time to put it together 14:11:47 mhrivnak: +1 14:12:07 ack 14:12:25 is there a hard timeframe where some users need this feature? 14:12:28 #action rhallisey: write up and issue for OSP API and cc interested community members 14:12:28 rhallisey: Error: "action" is not a valid command. 14:12:51 I believe it's important for kubevirt, which is 3.10? 14:13:07 I thought GA was 3.11 14:13:09 I'm not sure if it's 3.10 or 3.11 14:13:19 and tech preview for 3.10? 14:13:29 We're already doing this with helm bundles, although that's still in the "experimental" phase. 14:13:30 I think, I'll have to 2x check on that 14:13:40 maleck13, do you have a timeframe for this? 14:13:51 rhallisey: not currently no 14:13:52 time constraint* rather 14:14:14 in reality, we'll probably just have to get this done somehow. it's not going to be in the OSB spec by the time we need it. 14:14:28 but still good to bring up on those chats 14:14:35 ya 14:14:51 we're going to move right to open discussion since we have lots of items there 14:14:54 ^ it would be nice if we could get a "validating-through-implementation" for it for 3.11 14:15:06 #topic Open Discussion 14:15:06 rhallisey: Error: "topic" is not a valid command. 14:15:23 That sounds good. 14:15:32 maleck13, looks like you have the first item 14:15:39 #link https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/218 14:15:39 rhallisey: Error: "link" is not a valid command. 14:15:46 I added this to get some more feedback. I haven't heard much from the svcat team on it. And I am wondering have others come across a need to label the service catalog resources 14:16:51 being able to specify a set of labels on the cluster service class that get applied to all resources created, is the gist of it, however that is also likely a OSB API change 14:17:42 maleck13, might be worth bringing up on the call 14:18:01 rhallisey: right the sig call? 14:18:04 maleck13: "being able to specify a set of labels on the cluster service class that get applied to all resources created" that sounds awesome. 14:18:13 there's a section for community interests 14:18:24 maleck13 the problem I see is that labels might be a k8s only thing. You need to see if this applies to other platforms 14:18:27 IMO 14:18:30 I'm not sure what that would look like in the OSB, considering it's k8s agnostic 14:18:36 ^ yah 14:18:41 yes 14:18:45 what he said :) 14:19:04 so is it something that could be considered at the broker level or is it not really the place 14:19:43 can the broker even do it is another question as it is really the catalog that is managing these resources 14:19:46 Is this something that the broker could? what types of labels are you thinking? 14:20:13 maleck13: It feels to me like a broker thing if it's the ultimate service that needs to get annotated. if it should get automatically annotated on ServiceInstance objects, maybe that's a catalog thing 14:20:25 worth bouncing off those guys in the catalog sig maybe 14:20:53 ernelson: ok 14:21:34 shurley: they would be labels specified by broker. In our case in the apb.yaml 14:21:51 thanks for feedback guys 14:22:06 thanks maleck13 14:22:10 next item 14:22:12 #info Thoughts on multiple types of binding 14:22:12 rhallisey: Error: "info" is not a valid command. 14:22:13 the catalog doesn't know about the ultimate service that gets provisioned (say the mediawiki pod), but our service bundle might? 14:22:28 This is me again rhallisey 14:22:31 :) 14:22:36 great! 14:22:51 I tried to sum it up in the summary 14:23:15 * rhallisey reads 14:24:01 maleck13: are you thinking things like this? https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#types-of-binding 14:24:15 essentially bindings seem a little limited at the moment. As you may have different params for different kinds of bindings 14:24:18 #link https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#types-of-binding 14:24:18 rhallisey: Error: "link" is not a valid command. 14:24:51 shurley: I looked at that, but really I am talking about two credentials bindings 14:25:01 for two different types of client 14:25:16 maleck13, how would the two credential bindings be different? 14:25:46 one would be for a mobile client that needs a public set of credentials 14:26:03 the other would be for a bearer client that needs a private set of credentials 14:26:08 hope this is making sense 14:26:08 fabianvf, I just did an upgrade from 3.7 to 3.9 with openshift-ansible 3.9.7 and my broker configmap still has 3.7 in it 14:26:15 any idea what I may be missing? 14:26:15 shurley: sorry, you want a validating through implementation for what feature? 14:26:19 What are public credentials vs private? 14:26:35 I will be more specific 14:26:35 sounds like another topic for the OSB call 14:26:37 could this be achieved w/ binding parameters? 14:27:01 shurley: yes it could but that presents the problem of having many params some that are relevant and some that are not 14:27:33 jmontleon: did it hit the broker update task or was it skipped for some reason? 14:27:35 shurley: depending on what you are doing. So in the UI for example you would see many params but only need to fill in some of them 14:28:39 perhaps this is more of a UX issue? wanting to hide and show params. I could take it up with ux, just interested in others thoughts 14:29:04 * mhrivnak still doesn't get the full use case 14:29:09 maleck13: what do you think of creating a detailed use case, that way we might be able to talk about specifics for that case? 14:29:22 ya I think an issue would help 14:29:23 shurley: sure will do 14:29:24 That would be very helpful. 14:29:24 with an example 14:29:33 fabianvf, I see a task: TASK [ansible_service_broker : Create config map for ansible-service-broker] *** that I believe is for 3.9 14:29:52 interesting use case maleck13 , thank you 14:30:03 last item real quick 14:30:06 #topic Document broker release schedule 14:30:06 rhallisey: Error: "topic" is not a valid command. 14:30:10 I agree it does sound interesting :) 14:30:16 fabianvf, skipping 14:30:19 does anyone want to take this on? 14:30:24 default: TASK [ansible_service_broker : Create config map for ansible-service-broker] *** 14:30:24 default: skipping: [192.168.120.4.nip.io] 14:30:30 or think it's not worht doing? 14:30:37 looks like all the broker tasks in 3.9 actually are skipping 14:30:46 rhallisey: +1, think there's value in it for sure 14:31:02 are there any volunteers? 14:31:06 we're basically on the same 3mo release cycle k8s and openshift follow 14:31:07 I can create an issue for it 14:31:14 +1 14:31:16 ok 14:31:18 I know that we have a versioning strategy already..I could take this on but I'm not certain the extent 14:31:40 dzager, I'll explain what I'm thinking in an issue 14:31:41 rhallisey: I think we've hit our time. 14:31:46 yup 14:31:49 thanks folks! 14:31:53 #endmeeting -------------- next part -------------- ==================================== #asbroker: Automation Broker 3-13-18 ==================================== Meeting started by rhallisey at 13:31:04 UTC. The full logs are available at asbroker/2018/asbroker.2018-03-13-13.31.log.html . Meeting summary --------------- * Attendance (rhallisey, 13:31:20) * News (rhallisey, 13:32:55) * LINK: https://github.com/ansible/ansible/pull/36789 (rhallisey, 13:35:06) * ACTION: dymurray: document https://github.com/ansible/ansible/pull/36789 (rhallisey, 13:36:50) * ACTION: dymurray: also mention new galaxy feature on ML (rhallisey, 13:37:24) * Bugs/Issue triage (rhallisey, 13:37:41) * LINK: https://github.com/openshift/ansible-service-broker/issues/692 (rhallisey, 13:38:09) * ACTION: rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion (rhallisey, 13:46:42) * LINK: https://github.com/openshift/ansible-service-broker/issues/707 (rhallisey, 13:46:56) * LINK: https://github.com/openshift/ansible-service-broker/issues/730 (rhallisey, 13:48:19) * ACTION: rhallisey: switch to using broker release labels (rhallisey, 13:53:07) * LINK: https://github.com/openshift/ansible-service-broker/issues/798 (rhallisey, 13:54:30) * ACTION: community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting (rhallisey, 14:05:53) * Features (rhallisey, 14:06:17) * LINK: https://github.com/openshift/ansible-service-broker/issues/797 (rhallisey, 14:06:25) * ACTION: rhallisey: write up and issue for OSP API and cc interested community members (rhallisey, 14:12:28) * Open Discussion (rhallisey, 14:15:06) * LINK: https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/pull/218 (rhallisey, 14:15:39) * Thoughts on multiple types of binding (rhallisey, 14:22:12) * LINK: https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#types-of-binding (rhallisey, 14:24:18) * Document broker release schedule (rhallisey, 14:30:06) Meeting ended at 14:31:53 UTC. Action Items ------------ * dymurray: document https://github.com/ansible/ansible/pull/36789 * dymurray: also mention new galaxy feature on ML * rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion * rhallisey: switch to using broker release labels * community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting * rhallisey: write up and issue for OSP API and cc interested community members Action Items, by person ----------------------- * dymurray * dymurray: document https://github.com/ansible/ansible/pull/36789 * dymurray: also mention new galaxy feature on ML * rhallisey * rhallisey: add https://github.com/openshift/ansible-service-broker/issues/692 to next meeting issue section for discussion * rhallisey: switch to using broker release labels * rhallisey: write up and issue for OSP API and cc interested community members * **UNASSIGNED** * community: review https://github.com/openshift/ansible-service-broker/issues/798 and start with more discussion there. Possible topic at next meeting People Present (lines said) --------------------------- * rhallisey (102) * shurley (49) * maleck13 (43) * ernelson (31) * brokerbot (25) * mhrivnak (22) * dymurray (8) * dzager (8) * jmontleon (7) * jmrodri (2) * fabianvf (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From cmoullia at redhat.com Thu Mar 15 10:35:40 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 15 Mar 2018 11:35:40 +0100 Subject: [Ansible-service-broker] Minishift addon question Message-ID: Hi, Should I continue to use for minishift demo (Origin 3.7 and ASB 3.7) this addon - https://github.com/eriknelson/minishift-addons/tree/asb-updates ? FYI : Here is a Lab content which has been played by 38 students this week to demo ASB for Cloud Native Development of SpringBoot applications - https://github.com/snowdrop/cloud-native-lab/blob/master/HANDS_ON_LAB.md Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmoullia at redhat.com Thu Mar 15 10:47:04 2018 From: cmoullia at redhat.com (Charles Moulliard) Date: Thu, 15 Mar 2018 11:47:04 +0100 Subject: [Ansible-service-broker] Error reported by OpenShift Ansible playbook - branch 3.7 Message-ID: Hi, When this command is executed using the inventory (see hereafter) to create a all-in-one cluster, then we get this error Code line : https://github.com/openshift/openshift-ansible/blob/release-3.7/roles/ansible_service_broker/tasks/install.yml#L442 TASK [ansible_service_broker : Create the Broker resource in the catalog] ************************************************************************************************************************************************************************** fatal: [192.168.99.50]: FAILED! => {"changed": false, "failed": true, "msg": {"cmd": "/usr/bin/oc create -f /tmp/brokerout-dJmL1S -n default", "results": {}, "returncode": 1, "stderr": "error: unable to recognize \"/tmp/brokerout-dJmL1S\": *no matches for servicecatalog.k8s.io/ , Kind=ClusterServiceBroke*r\n", "stdout": ""}} 1) Command git clone -b release-3.7 https://github.com/openshift/openshift-ansible.git ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml 2) Inventory [OSEv3:children] masters nodes etcd [OSEv3:vars] ansible_user=root public_ip_address = 192.168.99.50 host_key_checking = False containerized = false openshift_release=v3.7 openshift_image_tag=v3.7.0 openshift_pkg_version="-3.7.0" openshift_deployment_type=origin openshift_hostname=192.168.99.50 openshift_master_cluster_public_hostname=192.168.99.50 openshift_master_default_subdomain=192.168.99.50.nip.io openshift_master_unsupported_embedded_etcd=true openshift_disable_check = docker_storage,memory_availability,disk_availability,docker_image_availability,package_version openshift_enable_service_catalog=true ansible_python_interpreter=/usr/bin/python ansible_service_broker_registry_whitelist=['.*-apb$'] ansible_service_broker_image_tag=v3.7 ansible_service_broker_registry_tag=v3.7 ansible_service_broker_remove=false ansible_service_broker_install=true [masters] 192.168.99.50 openshift_public_hostname=192.168.99.50 openshift_ip=192.168.99.50 [etcd] 192.168.99.50 openshift_ip=192.168.99.50 [nodes] 192.168.99.50 openshift_node_labels="{'region':'infra','zone':'default'}" openshift_ip=192.168.99.50 openshift_public_hostname=192.168.99.50 openshift_schedulable=true Is there a workaround ? Regards Charles -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmatthew at redhat.com Thu Mar 15 12:06:36 2018 From: jmatthew at redhat.com (John Matthews) Date: Thu, 15 Mar 2018 08:06:36 -0400 Subject: [Ansible-service-broker] Error reported by OpenShift Ansible playbook - branch 3.7 In-Reply-To: References: Message-ID: When we see the below error, it means the Service Catalog install failed. no matches for servicecatalog.k8s.io/, Kind=ClusterServiceBroker\n" There were several bugs related to issues with upgrade from 3.6. to 3.7 that hit this, but not aware of a bug with a new install in 3.7 with this. If you ping fabian/jmontleon in #asbroker (on freenode), they can help guide you through troubleshooting what might be wrong. On Thu, Mar 15, 2018 at 6:47 AM, Charles Moulliard wrote: > Hi, > > When this command is executed using the inventory (see hereafter) to > create a all-in-one cluster, then we get this error > > Code line : https://github.com/openshift/openshift-ansible/ > blob/release-3.7/roles/ansible_service_broker/tasks/install.yml#L442 > > TASK [ansible_service_broker : Create the Broker resource in the catalog] > ************************************************************ > ************************************************************ > ************************************************** > fatal: [192.168.99.50]: FAILED! => {"changed": false, "failed": true, > "msg": {"cmd": "/usr/bin/oc create -f /tmp/brokerout-dJmL1S -n default", > "results": {}, "returncode": 1, "stderr": "error: unable to recognize > \"/tmp/brokerout-dJmL1S\": *no matches for servicecatalog.k8s.io/ > , Kind=ClusterServiceBroke*r\n", "stdout": > ""}} > > 1) Command > > git clone -b release-3.7 https://github.com/openshift/ > openshift-ansible.git > ansible-playbook -i inventory openshift-ansible/playbooks/byo/config.yml > > 2) Inventory > > [OSEv3:children] > masters > nodes > etcd > > [OSEv3:vars] > ansible_user=root > > public_ip_address = 192.168.99.50 > host_key_checking = False > > containerized = false > > openshift_release=v3.7 > openshift_image_tag=v3.7.0 > openshift_pkg_version="-3.7.0" > > openshift_deployment_type=origin > > openshift_hostname=192.168.99.50 > openshift_master_cluster_public_hostname=192.168.99.50 > openshift_master_default_subdomain=192.168.99.50.nip.io > openshift_master_unsupported_embedded_etcd=true > openshift_disable_check = docker_storage,memory_availability,disk_ > availability,docker_image_availability,package_version > > openshift_enable_service_catalog=true > > ansible_python_interpreter=/usr/bin/python > > ansible_service_broker_registry_whitelist=['.*-apb$'] > ansible_service_broker_image_tag=v3.7 > ansible_service_broker_registry_tag=v3.7 > ansible_service_broker_remove=false > ansible_service_broker_install=true > > [masters] > 192.168.99.50 openshift_public_hostname=192.168.99.50 > openshift_ip=192.168.99.50 > > [etcd] > 192.168.99.50 openshift_ip=192.168.99.50 > > [nodes] > 192.168.99.50 openshift_node_labels="{'region':'infra','zone':'default'}" > openshift_ip=192.168.99.50 openshift_public_hostname=192.168.99.50 > openshift_schedulable=true > > > Is there a workaround ? > > 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 jmatthew at redhat.com Thu Mar 15 12:09:06 2018 From: jmatthew at redhat.com (John Matthews) Date: Thu, 15 Mar 2018 08:09:06 -0400 Subject: [Ansible-service-broker] Error reported by OpenShift Ansible playbook - branch 3.7 In-Reply-To: References: Message-ID: On Thu, Mar 15, 2018 at 8:06 AM, John Matthews wrote: > When we see the below error, it means the Service Catalog install failed. > no matches for servicecatalog.k8s.io/, Kind=ClusterServiceBroker\n" > > There were several bugs related to issues with upgrade from 3.6. to 3.7 > that hit this, but not aware of a bug with a new install in 3.7 with this. > (Link to main BZ I was thinking about: https://bugzilla.redhat.com/show_bug.cgi?id=1523298) > > If you ping fabian/jmontleon in #asbroker (on freenode), they can help > guide you through troubleshooting what might be wrong. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ernelson at redhat.com Thu Mar 15 13:02:00 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 15 Mar 2018 09:02:00 -0400 Subject: [Ansible-service-broker] Minishift addon question In-Reply-To: References: Message-ID: Hi Charles, > Should I continue to use for minishift demo (Origin 3.7 and ASB 3.7) this > addon - https://github.com/eriknelson/minishift-addons/tree/asb-updates ? You should move to using https://github.com/minishift/minishift-addons/tree/master/add-ons/ansible-service-broker, which is the "official" github repo for minishift addons. My PR was merged, so you shouldn't need to use my branch any longer. > FYI : Here is a Lab content which has been played by 38 students this week > to demo ASB for Cloud Native Development of SpringBoot applications - > https://github.com/snowdrop/cloud-native-lab/blob/master/HANDS_ON_LAB.md Very cool! I will take a look. > Regards > > Charles > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > From ssadeghi at redhat.com Fri Mar 16 12:41:36 2018 From: ssadeghi at redhat.com (Siamak Sadeghianfar) Date: Fri, 16 Mar 2018 12:41:36 +0000 Subject: [Ansible-service-broker] Instantiating APB with CLI Message-ID: Hi, I have been trying to use oc to create services so that it can be automated in Jenkins, etc. There is a flow that works but leaves quite a lot to be desired. Is there a better way to do this with "oc new-app" similar to images, imagestreams and templates? Here is the flow: 1. List APBs oc get clusterserviceclasses --all-namespaces -o custom-columns=NAME:. metadata.name,DISPLAYNAME:spec.externalMetadata.displayName | grep APB 2. Find out the selected APB's external name oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o yaml 3. Find the source of the APB (apb.yml) to figure out the parameter names and plans e.g. https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/apb.yml 4. Create a yml file for the serviceinstance, specifying values for external apb name, params, plans, etc 5. Create the service instance using CLI oc create -f postgresql-si.yml Kind Regards, Siamak Sadeghianfar Principal Technical Marketing Manager OpenShift, Red Hat Inc. M: +46-73-183-5553 <+46%2073%20183%2055%2053> | T: @siamaks redhat.com | TRIED. TESTED. TRUSTED. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Fri Mar 16 13:38:04 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Fri, 16 Mar 2018 09:38:04 -0400 Subject: [Ansible-service-broker] Instantiating APB with CLI In-Reply-To: References: Message-ID: Hey Siamak, In the apb tool, there's the command ```apb serviceinstance```. It will generate 'most' of a serviceinstance template. You will still need to lookup the external name, so I recommend using ```oc get clusterserviceclass -o custom-columns=Name:spec.externalName,externalID:spec.externalID,Broker:spec.clusterServiceBrokerName```. The 'serviceinstance' command has a lot of potential improvement, so if you have anything you want to contribute feel free to! Thanks, -Ryan On Fri, Mar 16, 2018 at 8:41 AM, Siamak Sadeghianfar wrote: > Hi, > > I have been trying to use oc to create services so that it can be > automated in Jenkins, etc. There is a flow that works but leaves quite a > lot to be desired. Is there a better way to do this with "oc new-app" > similar to images, imagestreams and templates? > > Here is the flow: > > 1. List APBs > > oc get clusterserviceclasses --all-namespaces -o custom-columns=NAME:. > metadata.name,DISPLAYNAME:spec.externalMetadata.displayName | grep APB > > 2. Find out the selected APB's external name > > oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o yaml > > 3. Find the source of the APB (apb.yml) to figure out the parameter names > and plans e.g. > https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/ > apb.yml > > 4. Create a yml file for the serviceinstance, specifying values for > external apb name, params, plans, etc > > 5. Create the service instance using CLI > oc create -f postgresql-si.yml > > > Kind Regards, > Siamak Sadeghianfar > Principal Technical Marketing Manager > OpenShift, Red Hat Inc. > M: +46-73-183-5553 <+46%2073%20183%2055%2053> | T: @siamaks > redhat.com | TRIED. TESTED. TRUSTED. > > > > > _______________________________________________ > 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 jmatthew at redhat.com Fri Mar 16 13:53:40 2018 From: jmatthew at redhat.com (John Matthews) Date: Fri, 16 Mar 2018 09:53:40 -0400 Subject: [Ansible-service-broker] Instantiating APB with CLI In-Reply-To: References: Message-ID: Siamak, Maybe svcat would help for what you are after? It's a cli tool service-catalog is offering (contributed by Azure folks recently). The experience with svcat is a little better than current oc command. https://github.com/kubernetes-incubator/service-catalog/blob/master/docs/cli.md#service-catalog-cli On Fri, Mar 16, 2018 at 9:38 AM, Ryan Hallisey wrote: > Hey Siamak, > > In the apb tool, there's the command ```apb serviceinstance```. It will > generate 'most' of a serviceinstance template. You will still need to > lookup the external name, so I recommend using ```oc get > clusterserviceclass -o custom-columns=Name:spec. > externalName,externalID:spec.externalID,Broker:spec. > clusterServiceBrokerName```. > > The 'serviceinstance' command > > has a lot of potential improvement, so if you have anything you want to > contribute feel free to! > > Thanks, > -Ryan > > On Fri, Mar 16, 2018 at 8:41 AM, Siamak Sadeghianfar > wrote: > >> Hi, >> >> I have been trying to use oc to create services so that it can be >> automated in Jenkins, etc. There is a flow that works but leaves quite a >> lot to be desired. Is there a better way to do this with "oc new-app" >> similar to images, imagestreams and templates? >> >> Here is the flow: >> >> 1. List APBs >> >> oc get clusterserviceclasses --all-namespaces -o custom-columns=NAME:. >> metadata.name,DISPLAYNAME:spec.externalMetadata.displayName | grep APB >> >> 2. Find out the selected APB's external name >> >> oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o yaml >> >> 3. Find the source of the APB (apb.yml) to figure out the parameter names >> and plans e.g. >> https://github.com/ansibleplaybookbundle/postgresql-apb/ >> blob/master/apb.yml >> >> 4. Create a yml file for the serviceinstance, specifying values for >> external apb name, params, plans, etc >> >> 5. Create the service instance using CLI >> oc create -f postgresql-si.yml >> >> >> Kind Regards, >> Siamak Sadeghianfar >> Principal Technical Marketing Manager >> OpenShift, Red Hat Inc. >> M: +46-73-183-5553 <+46%2073%20183%2055%2053> | T: @siamaks >> redhat.com | TRIED. TESTED. TRUSTED. >> >> >> >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> >> > > _______________________________________________ > 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 jmontleo at redhat.com Fri Mar 16 14:03:11 2018 From: jmontleo at redhat.com (Jason Montleon) Date: Fri, 16 Mar 2018 10:03:11 -0400 Subject: [Ansible-service-broker] Instantiating APB with CLI In-Reply-To: References: Message-ID: svcat is friendlier output if you want to build it from source: https://github.com/kubernetes-incubator/service-catalog/tree/master/cmd/svcat Or if you're on EL7 or Fedora 26/27 I've created an rpm until official ones come along. This page has instructions for setting up the repo. https://copr.fedorainfracloud.org/coprs/g/ansible-service-broker/ansible-service-broker-latest/ From there yum or dnf install svcat I've played spacing for sake of clarity in email but output is roughly: $ svcat get classes NAME DESCRIPTION UUID +-----------------+-------------------+--------------------------------+ dh-pyzip-demo-apb Python Zip Demo APB 0e991006d21029e47abe71acc255e807 ... On 03/16/2018 09:38 AM, Ryan Hallisey wrote: > Hey Siamak, > > In the apb tool, there's the command ```apb serviceinstance```. It will > generate 'most' of a serviceinstance template.? You will still need to > lookup the external name, so I recommend using ```oc get > clusterserviceclass -o > custom-columns=Name:spec.externalName,externalID:spec.externalID,Broker:spec.clusterServiceBrokerName```. > > The 'serviceinstance' command > > has a lot of potential improvement, so if you have anything you want to > contribute feel free to! > > Thanks, > -Ryan > > On Fri, Mar 16, 2018 at 8:41 AM, Siamak Sadeghianfar > > wrote: > > Hi, > > I have been trying to use oc?to create services so that it can be > automated in Jenkins, etc. There is a flow that works but leaves > quite a lot to be desired. Is there a better way to do this with "oc > new-app" similar to images, imagestreams and templates? > > Here is the flow: > > 1. List APBs > > oc get clusterserviceclasses --all-namespaces -o > custom-columns=NAME:.metadata.name > ,DISPLAYNAME:spec.externalMetadata.displayName > | grep APB > > 2. Find out the selected APB's external name > > oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o yaml > > 3. Find the source of the APB (apb.yml) to figure out the parameter > names and plans e.g. > https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/apb.yml > > > 4. Create a yml file for?the serviceinstance, specifying values for > external apb name, params, plans, etc > > 5. Create the service instance using CLI > oc create -f postgresql-si.yml > > > Kind Regards, > Siamak Sadeghianfar > Principal Technical Marketing Manager > OpenShift, Red Hat Inc. > M: +46-73-183-5553 | T: @siamaks > redhat.com | TRIED. TESTED. TRUSTED. > > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker > -- Jason Montleon | email: jmontleo at redhat.com Software Engineer | gpg key: 0x069E3022 Red Hat, Inc. | irc: jmontleo desk: 978-392-3930 | cell: 508-496-0663 From ssadeghi at redhat.com Thu Mar 22 15:32:43 2018 From: ssadeghi at redhat.com (Siamak Sadeghianfar) Date: Thu, 22 Mar 2018 15:32:43 +0000 Subject: [Ansible-service-broker] Instantiating APB with CLI In-Reply-To: References: Message-ID: Jason, svcat helps but it means that users now have to download two different CLIs to create apps on OpenShift. To me as a user it makes no difference that one thing comes from the service catalog and the other from a template. I just need to create for example a MySQL pod which doesn't seem to be possible via OpenShift CLI if the service is provisioned via the service catalog. Kind Regards, Siamak On Fri, Mar 16, 2018 at 3:03 PM Jason Montleon wrote: > svcat is friendlier output if you want to build it from source: > > https://github.com/kubernetes-incubator/service-catalog/tree/master/cmd/svcat > > Or if you're on EL7 or Fedora 26/27 I've created an rpm until official > ones come along. This page has instructions for setting up the repo. > > > https://copr.fedorainfracloud.org/coprs/g/ansible-service-broker/ansible-service-broker-latest/ > > From there yum or dnf install svcat > I've played spacing for sake of clarity in email but output is roughly: > $ svcat get classes > NAME DESCRIPTION UUID > +-----------------+-------------------+--------------------------------+ > dh-pyzip-demo-apb Python Zip Demo APB 0e991006d21029e47abe71acc255e807 > ... > > On 03/16/2018 09:38 AM, Ryan Hallisey wrote: > > Hey Siamak, > > > > In the apb tool, there's the command ```apb serviceinstance```. It will > > generate 'most' of a serviceinstance template. You will still need to > > lookup the external name, so I recommend using ```oc get > > clusterserviceclass -o > > > custom-columns=Name:spec.externalName,externalID:spec.externalID,Broker:spec.clusterServiceBrokerName```. > > > > The 'serviceinstance' command > > < > https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/blob/master/src/apb/engine.py#L1235 > > > > has a lot of potential improvement, so if you have anything you want to > > contribute feel free to! > > > > Thanks, > > -Ryan > > > > On Fri, Mar 16, 2018 at 8:41 AM, Siamak Sadeghianfar > > > wrote: > > > > Hi, > > > > I have been trying to use oc to create services so that it can be > > automated in Jenkins, etc. There is a flow that works but leaves > > quite a lot to be desired. Is there a better way to do this with "oc > > new-app" similar to images, imagestreams and templates? > > > > Here is the flow: > > > > 1. List APBs > > > > oc get clusterserviceclasses --all-namespaces -o > > custom-columns=NAME:.metadata.name > > ,DISPLAYNAME:spec.externalMetadata.displayName > > | grep APB > > > > 2. Find out the selected APB's external name > > > > oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o yaml > > > > 3. Find the source of the APB (apb.yml) to figure out the parameter > > names and plans e.g. > > > https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/apb.yml > > < > https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/apb.yml > > > > > > 4. Create a yml file for the serviceinstance, specifying values for > > external apb name, params, plans, etc > > > > 5. Create the service instance using CLI > > oc create -f postgresql-si.yml > > > > > > Kind Regards, > > Siamak Sadeghianfar > > Principal Technical Marketing Manager > > OpenShift, Red Hat Inc. > > M: +46-73-183-5553 <+46%2073%20183%2055%2053> > | T: @siamaks > > redhat.com | TRIED. TESTED. TRUSTED. > > > > > > > > > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > > > > > > > _______________________________________________ > > Ansible-service-broker mailing list > > Ansible-service-broker at redhat.com > > https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > -- > Jason Montleon | email: jmontleo at redhat.com > Software Engineer | gpg key: 0x069E3022 > Red Hat, Inc. | irc: jmontleo > desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 > <(508)%20496-0663> > > _______________________________________________ > 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 ssadeghi at redhat.com Thu Mar 22 15:35:37 2018 From: ssadeghi at redhat.com (Siamak Sadeghianfar) Date: Thu, 22 Mar 2018 15:35:37 +0000 Subject: [Ansible-service-broker] Instantiating APB with CLI In-Reply-To: References: Message-ID: Ryan, Any plans to merge that functionality into OpenShift CLI? To me as a user, there is no difference between the items that are in the service catalog but I'm forced now to know who i OpenShift deploys that item (template broker, ansible broker, etc) and download multiple CLI tools to interact with each separately. Kind Regards, Siamak On Fri, Mar 16, 2018 at 2:38 PM Ryan Hallisey wrote: > Hey Siamak, > > In the apb tool, there's the command ```apb serviceinstance```. It will > generate 'most' of a serviceinstance template. You will still need to > lookup the external name, so I recommend using ```oc get > clusterserviceclass -o > custom-columns=Name:spec.externalName,externalID:spec.externalID,Broker:spec.clusterServiceBrokerName```. > > The 'serviceinstance' command > > has a lot of potential improvement, so if you have anything you want to > contribute feel free to! > > Thanks, > -Ryan > > On Fri, Mar 16, 2018 at 8:41 AM, Siamak Sadeghianfar > wrote: > >> Hi, >> >> I have been trying to use oc to create services so that it can be >> automated in Jenkins, etc. There is a flow that works but leaves quite a >> lot to be desired. Is there a better way to do this with "oc new-app" >> similar to images, imagestreams and templates? >> >> Here is the flow: >> >> 1. List APBs >> >> oc get clusterserviceclasses --all-namespaces -o custom-columns=NAME:. >> metadata.name,DISPLAYNAME:spec.externalMetadata.displayName | grep APB >> >> 2. Find out the selected APB's external name >> >> oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o yaml >> >> 3. Find the source of the APB (apb.yml) to figure out the parameter names >> and plans e.g. >> >> https://github.com/ansibleplaybookbundle/postgresql-apb/blob/master/apb.yml >> >> 4. Create a yml file for the serviceinstance, specifying values for >> external apb name, params, plans, etc >> >> 5. Create the service instance using CLI >> oc create -f postgresql-si.yml >> >> >> Kind Regards, >> Siamak Sadeghianfar >> Principal Technical Marketing Manager >> OpenShift, Red Hat Inc. >> M: +46-73-183-5553 <+46%2073%20183%2055%2053> | T: @siamaks >> redhat.com | TRIED. TESTED. TRUSTED. >> >> >> >> >> _______________________________________________ >> 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 Thu Mar 22 16:05:44 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Thu, 22 Mar 2018 12:05:44 -0400 Subject: [Ansible-service-broker] Instantiating APB with CLI In-Reply-To: References: Message-ID: It's something that's been brought up in the past Siamak. We are planning a large refactoring of the apb tool that should make it more compatible with the oc client. After that, we should have an easier time bringing this up with the client folks and potentially merging this in oc client. Thanks for your perspective on this. - Ryan On Thu, Mar 22, 2018 at 11:32 AM, Siamak Sadeghianfar wrote: > Jason, > > svcat helps but it means that users now have to download two different > CLIs to create apps on OpenShift. To me as a user it makes no difference > that one thing comes from the service catalog and the other from a > template. I just need to create for example a MySQL pod which doesn't seem > to be possible via OpenShift CLI if the service is provisioned via the > service catalog. > > Kind Regards, > Siamak > > > On Fri, Mar 16, 2018 at 3:03 PM Jason Montleon > wrote: > >> svcat is friendlier output if you want to build it from source: >> https://github.com/kubernetes-incubator/service-catalog/ >> tree/master/cmd/svcat >> >> Or if you're on EL7 or Fedora 26/27 I've created an rpm until official >> ones come along. This page has instructions for setting up the repo. >> >> https://copr.fedorainfracloud.org/coprs/g/ansible-service- >> broker/ansible-service-broker-latest/ >> >> From there yum or dnf install svcat >> I've played spacing for sake of clarity in email but output is roughly: >> $ svcat get classes >> NAME DESCRIPTION UUID >> +-----------------+-------------------+--------------------------------+ >> dh-pyzip-demo-apb Python Zip Demo APB 0e991006d21029e47abe71acc255e807 >> ... >> >> On 03/16/2018 09:38 AM, Ryan Hallisey wrote: >> > Hey Siamak, >> > >> > In the apb tool, there's the command ```apb serviceinstance```. It will >> > generate 'most' of a serviceinstance template. You will still need to >> > lookup the external name, so I recommend using ```oc get >> > clusterserviceclass -o >> > custom-columns=Name:spec.externalName,externalID:spec. >> externalID,Broker:spec.clusterServiceBrokerName```. >> > >> > The 'serviceinstance' command >> > > playbook-bundle/blob/master/src/apb/engine.py#L1235> >> > has a lot of potential improvement, so if you have anything you want to >> > contribute feel free to! >> > >> > Thanks, >> > -Ryan >> > >> > On Fri, Mar 16, 2018 at 8:41 AM, Siamak Sadeghianfar >> > > wrote: >> > >> > Hi, >> > >> > I have been trying to use oc to create services so that it can be >> > automated in Jenkins, etc. There is a flow that works but leaves >> > quite a lot to be desired. Is there a better way to do this with "oc >> > new-app" similar to images, imagestreams and templates? >> > >> > Here is the flow: >> > >> > 1. List APBs >> > >> > oc get clusterserviceclasses --all-namespaces -o >> > custom-columns=NAME:.metadata.name >> > ,DISPLAYNAME:spec. >> externalMetadata.displayName >> > | grep APB >> > >> > 2. Find out the selected APB's external name >> > >> > oc get clusterserviceclasses e171fe1a84c3750a0957e7e917af9530 -o >> yaml >> > >> > 3. Find the source of the APB (apb.yml) to figure out the parameter >> > names and plans e.g. >> > https://github.com/ansibleplaybookbundle/ >> postgresql-apb/blob/master/apb.yml >> > > postgresql-apb/blob/master/apb.yml> >> > >> > 4. Create a yml file for the serviceinstance, specifying values for >> > external apb name, params, plans, etc >> > >> > 5. Create the service instance using CLI >> > oc create -f postgresql-si.yml >> > >> > >> > Kind Regards, >> > Siamak Sadeghianfar >> > Principal Technical Marketing Manager >> > OpenShift, Red Hat Inc. >> > M: +46-73-183-5553 <+46%2073%20183%2055%2053> >> | T: @siamaks >> > redhat.com | TRIED. TESTED. TRUSTED. >> > >> > >> > >> > >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> > >> > >> > >> > >> > _______________________________________________ >> > Ansible-service-broker mailing list >> > Ansible-service-broker at redhat.com >> > https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> >> -- >> Jason Montleon | email: jmontleo at redhat.com >> Software Engineer | gpg key: 0x069E3022 >> Red Hat, Inc. | irc: jmontleo >> desk: 978-392-3930 <(978)%20392-3930> | cell: 508-496-0663 >> <(508)%20496-0663> >> >> _______________________________________________ >> Ansible-service-broker mailing list >> Ansible-service-broker at redhat.com >> https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > > _______________________________________________ > 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 jkim at redhat.com Fri Mar 23 21:24:26 2018 From: jkim at redhat.com (John Kim) Date: Fri, 23 Mar 2018 17:24:26 -0400 Subject: [Ansible-service-broker] Custom Error Messages Message-ID: Hello, The following video shows how you can display custom error messages from a service bundle, in the event of a fatal error. https://youtu.be/GiJrTX05Jno Basic concept is to write out the error you want displayed to the termination log, '/dev/termination-log'. Broker will be able to extract the error and send back to the Service Catalog. An example is here: https://github.com/johnkim76/aws-servicebroker-sqs/blob/error_demo/roles/sqs-apb-openshift/tasks/main.yml#L46 V/R, John Kim -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhrivnak at redhat.com Tue Mar 27 13:27:47 2018 From: mhrivnak at redhat.com (Michael Hrivnak) Date: Tue, 27 Mar 2018 09:27:47 -0400 Subject: [Ansible-service-broker] bundle contract improvement ideas Message-ID: I created a shared document where we can collect ideas for how to improve the Service Bundle Contract. I seeded it with a few ideas I know have come up recently. Please add your ideas and questions, and we'll use the resulting document in a follow-up meeting. https://docs.google.com/document/d/1QBY4XskWqJ7KcaYoRwjmDXlfswJtX69lzmoiYkLFduc/edit?usp=sharing -- Michael Hrivnak Principal Software Engineer, RHCE Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhrivnak at redhat.com Tue Mar 27 13:29:48 2018 From: mhrivnak at redhat.com (Michael Hrivnak) Date: Tue, 27 Mar 2018 09:29:48 -0400 Subject: [Ansible-service-broker] bundle contract improvement ideas In-Reply-To: References: Message-ID: Sorry, stand by for the correct link... On Tue, Mar 27, 2018 at 9:27 AM, Michael Hrivnak wrote: > I created a shared document where we can collect ideas for how to improve > the Service Bundle Contract. I seeded it with a few ideas I know have come > up recently. Please add your ideas and questions, and we'll use the > resulting document in a follow-up meeting. > > https://docs.google.com/document/d/1QBY4XskWqJ7KcaYoRwjmDXlfswJtX > 69lzmoiYkLFduc/edit?usp=sharing > > -- > > Michael Hrivnak > > Principal Software Engineer, RHCE > > Red Hat > -- Michael Hrivnak Principal Software Engineer, RHCE Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhrivnak at redhat.com Tue Mar 27 13:34:16 2018 From: mhrivnak at redhat.com (Michael Hrivnak) Date: Tue, 27 Mar 2018 09:34:16 -0400 Subject: [Ansible-service-broker] bundle contract improvement ideas In-Reply-To: References: Message-ID: Sorry for the blip; the original link is working. On Tue, Mar 27, 2018 at 9:29 AM, Michael Hrivnak wrote: > Sorry, stand by for the correct link... > > On Tue, Mar 27, 2018 at 9:27 AM, Michael Hrivnak > wrote: > >> I created a shared document where we can collect ideas for how to improve >> the Service Bundle Contract. I seeded it with a few ideas I know have come >> up recently. Please add your ideas and questions, and we'll use the >> resulting document in a follow-up meeting. >> >> https://docs.google.com/document/d/1QBY4XskWqJ7KcaYoRwjmDXlf >> swJtX69lzmoiYkLFduc/edit?usp=sharing >> >> -- >> >> Michael Hrivnak >> >> Principal Software Engineer, RHCE >> >> Red Hat >> > > > > -- > > Michael Hrivnak > > Principal Software Engineer, RHCE > > Red Hat > -- Michael Hrivnak Principal Software Engineer, RHCE Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From rhallise at redhat.com Tue Mar 27 14:21:34 2018 From: rhallise at redhat.com (Ryan Hallisey) Date: Tue, 27 Mar 2018 10:21:34 -0400 Subject: [Ansible-service-broker] Automation Broker 3-27-18 IRC Meeting Message-ID: ==================================== #asbroker: Automation Broker 3-27-18 ==================================== Meeting started by rhallisey at 13:30:57 UTC. The full logs are attached. Meeting summary --------------- * Attendance (rhallisey, 13:31:15) * News (rhallisey, 13:32:00) * OpenShift 3.10 feature freeze 4/4/18 (rhallisey, 13:32:09) * OpenShift 3.11 feature freeze around 7/4/18 (rhallisey, 13:34:11) * Bugs/Issue triage (rhallisey, 13:35:27) * WIP] displayWhen for conditional rendering of fields (rhallisey, 13:35:38) * [WIP] displayWhen for conditional rendering of fields (rhallisey, 13:35:46) * LINK: https://github.com/openshift/ansible-service-broker/pull/834 (rhallisey, 13:36:06) * ACTION: : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue (rhallisey, 13:44:57) * ACTION: jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal (rhallisey, 13:46:17) * k8s/origin object naming (rhallisey, 13:46:32) * LINK: https://github.com/ansibleplaybookbundle/postgresql-apb/issues/40 (rhallisey, 13:46:39) * LINK: https://github.com/openshift/ansible-service-broker/issues/853 (rhallisey, 13:46:46) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1542235 (dzager, 13:46:53) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1542235 (rhallisey, 13:47:04) * ACTION: dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming (rhallisey, 13:54:11) * Features (rhallisey, 13:55:01) * APB state support targeting 3.11 now (rhallisey, 13:55:09) * bundle-lib (rhallisey, 13:57:19) * Open Discussion (rhallisey, 13:59:47) * Debugging CI build failures (rhallisey, 13:59:56) Meeting ended at 14:09:17 UTC. Action Items ------------ * : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue * jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal * dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming Action Items, by person ----------------------- * dzager * dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming * jmrodri * jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal * **UNASSIGNED** * : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue People Present (lines said) --------------------------- * rhallisey (66) * shurley (41) * brokerbot (28) * jmrodri (26) * dzager (26) * maleck13 (25) * ernelson (19) * dymurray (9) * mhrivnak (5) * jmontleon (2) * fabianvf (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- 13:30:57 #startmeeting Automation Broker 3-27-18 13:30:57 Meeting started Tue Mar 27 13:30:57 2018 UTC. The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:30:57 The meeting name has been set to 'automation_broker_3-27-18' 13:30:57 rhallisey: startmeeting Meeting Agenda https://docs.google.com/document/d/1Mj7bVYJ8NK-TwU_mxeZLprmBBZZ-xOq-Hg4CiD3E6pM/edit?usp=sharing 13:31:15 #topic Attendance 13:31:15 rhallisey: topic 13:31:18 hey folks 13:31:25 hello 13:31:27 Hey guys 13:31:30 hey 13:31:37 o/ 13:32:00 #topic News 13:32:00 rhallisey: topic 13:32:03 hello! 13:32:09 #info OpenShift 3.10 feature freeze 4/4/18 13:32:09 rhallisey: info 13:32:22 the openshift feature freeze is right around the corner 13:32:38 8 days from today 13:32:59 it is really good to know these dates. 13:33:08 things that are targeted for 3.10 need to get in soon 13:33:32 maleck13, I'll create a doc for this after the meeting. I didn't get to it this morning 13:33:51 rhallisey: +1 13:34:11 #info OpenShift 3.11 feature freeze around 7/4/18 13:34:11 rhallisey: info 13:34:26 3.11 feature freeze is july 4th 13:34:28 wow really 13:34:41 yeah thought we should call that now 13:34:50 who picked july 4th :/ 13:35:05 I mean it will probably change, but around that date 13:35:13 shurley, +q 13:35:15 +1 13:35:27 #topic Bugs/Issue triage 13:35:27 rhallisey: topic 13:35:35 sorry I'm late 13:35:38 #info WIP] displayWhen for conditional rendering of fields 13:35:38 rhallisey: Error: Spurious "]". You may want to quote your arguments with double quotes in order to prevent extra brackets from being evaluated as nested commands. 13:35:46 #info [WIP] displayWhen for conditional rendering of fields 13:35:46 rhallisey: Error: "WIP" is not a valid command. 13:36:06 #link https://github.com/openshift/ansible-service-broker/pull/834 13:36:06 rhallisey: link 13:36:16 I wanted to talk about the displayWhen PRs that out. did we decide if we are going to merge this? 13:36:23 and is it still in WIP? 13:36:46 last meeting I think we said we will merge it then follow up with the UI folks 13:36:48 Isn't that technically part of the discussion we had yesterday around JSON schema? or no? 13:36:49 PRs because there is now a PR against bundle-lib and broker 13:36:56 dymurray: yes, absolutely related 13:37:16 i wouldn't plan on running catasb right now if you have a cluster up; i have no idea why it's not working; something wrong with the router 13:37:26 rhallisey: +1 I recall that 13:37:28 Just want to make sure we follow up with him on the root problem and that we are addressing the problem 13:38:07 ok, so we need to get this out of WIP and merge? 13:38:15 is that what I am hearing? 13:38:23 dymurray: yeah the displayName is related. The dilemma is do we fix things peace meal, allow stop gaps, or halt it until the solution is done. 13:38:33 I was under the impression the UI did not support this yet 13:38:35 looks like https://github.com/automationbroker/bundle-lib/pull/41 needs to go in first 13:38:37 so it was not functional 13:38:45 is that not true? 13:38:56 ernelson, yes 13:38:57 ernelson: good question, unsure. 13:39:02 it's not functional 13:39:09 if the UI doesn't support it yet, then I wouldn't push to get this in yet. 13:39:09 so why are we merging it then? 13:39:15 ernelson: +1 13:39:25 +1 I'm hesitant to merge 13:39:33 ok then lets close it 13:39:33 we said last meeting we would merge it then speak to the UI folks 13:39:45 shurley: you don't like lingering PRs huh? 13:39:47 lets not just leave it open 13:39:47 :) 13:40:08 Something like this is definitely needed, IMO not sure if this is it however 13:40:12 if no one wants to merge it, the feature would work (is that right?) then close it 13:40:13 I'm already a little uneasy about having front-end related things in the codebase, I would rather not have it merged if it also doesn't work. 13:40:32 maleck13: +1 13:40:51 when you say it doesn;t work, we are saying the UI does not respect the displayWhen 13:40:54 correct? 13:40:55 shurley: yes. 13:40:57 ernelson: doesn't work "because the UI does not take part of it" 13:41:00 do we have a proposal for this change? 13:41:06 shurley: that's the way I understood it :) 13:41:07 oh then lets close please 13:41:26 Unless there has been something on the UI side that I was unaware of. 13:41:35 dzager: I don't remember, I wanted to say I vaguely remember it, but I can't be 100% sure 13:41:36 what are the next steps in the UI 13:41:39 we should log a public issue about the more rich UI stuff we are working on 13:41:44 So do we want a proposal for how this might work from a params definition and loop in the UX team 13:42:03 I will start a proposal for the stuff we talked about yesterday 13:42:14 I'm fine with closing this if we open something else 13:42:16 and then group this into that? 13:42:18 I think lots of stuff is happening RE: ui 13:42:18 jmrodri: yeah. It feels like something that would have had one but I don't remember it. 13:42:26 I think we have to sit and wait for second on this 13:42:27 IMO 13:42:29 opening an issue sounds correct to me 13:42:32 they're basically freezing UI dev as of now 13:42:35 moving to react. 13:42:49 I don't know how much progress we are going to have getting support into the current console (read: none) 13:43:11 ernelson: interesting we have a ton of work planned for the console 13:43:29 I think we capture all of these and we do work forward on them. But we are kind of at the mercy of the UI team. 13:43:37 shurley: I took your comment 'we have to sit and wait for a second on this' to mean that we should log an issue and think about how we want to solve it. Is that right? 13:43:54 dzager: +1 13:44:04 dzager: +1 13:44:08 +! 13:44:11 +1 13:44:14 yes that is what I think we have to do. I just don't like keeping PRs open if we are not going to merge 13:44:36 shurley: okay then sounds like open issue, close this PR, start a proposal 13:44:38 who wants to log the issue and close? 13:44:38 +1 13:44:43 that sound like a good summary? 13:44:43 shurley: that sounds reasonable to me. Open an issue, leave it open to proposal PRs, close the PR in question 13:44:50 # action: community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue 13:44:50 rhallisey: Error: "action:" is not a valid command. 13:44:56 jmrodri: can we really do a proposal in the broker for this though? 13:44:56 * dzager sees that jmrodri types faster 13:44:57 #action: community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue 13:44:57 rhallisey: Error: "action:" is not a valid command. 13:44:58 shurley: I can log the issue and start the propsoal 13:45:08 #action community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue 13:45:08 rhallisey: action 13:45:15 shurley: not specifically for this, but the all encompassing parameters issue 13:45:19 I see this as related 13:45:21 +1 13:45:39 I would group this into the other. So for this SPECIFIC PR. close it, file issue. 13:45:42 I can do both 13:45:48 sounds good 13:45:52 rhallisey: assign both actions to me please 13:45:54 thanks jmrodri 13:45:57 thanks everyone 13:46:00 #undo 13:46:00 Removing item from minutes: ACTION by rhallisey at 13:45:08 : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue 13:46:17 #action jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal 13:46:17 rhallisey: action 13:46:32 #topic k8s/origin object naming 13:46:32 rhallisey: topic 13:46:39 #link https://github.com/ansibleplaybookbundle/postgresql-apb/issues/40 13:46:39 rhallisey: link 13:46:46 #link https://github.com/openshift/ansible-service-broker/issues/853 13:46:46 rhallisey: link 13:46:52 Most Service Bundles (APBs) suffer from a bug 13:46:53 #link https://bugzilla.redhat.com/show_bug.cgi?id=1542235 13:46:53 dzager: Error: You don't have the admin capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified. 13:47:04 #link https://bugzilla.redhat.com/show_bug.cgi?id=1542235 13:47:04 rhallisey: link 13:47:11 The problem is that, for example, when you provision the hello-world-apb all of the created objects are hardcoded to 'hello-world'. This makes it impossible to have multiple instances of the same bundle provisioned in the same namespace. 13:47:20 There are a handful of ways around this: 13:47:22 1) name the objects based on the service instance id (ie. hello-world-1234-5678) 13:47:24 2) take the name as a parameter (ie. https://github.com/ansibleplaybookbundle/hello-world-apb/pull/3) 13:47:26 3) wait for the asb save state and use generateName 13:47:37 My concern with #3 is that only gets you part of the way. Since you need to know the name of the deployment in order to properly construct the service, etc. The method I presented as an example was #2, but thought we should discuss this. 13:47:39 1 or 3 13:47:42 IMO 13:48:01 my issue with #1 is the names are ugly as hell 13:48:17 ok, but have some gurantee of uniqueness 13:48:22 Agreed , 1 or 3 to keep it easy. 13:48:44 parameter has no way to check uniqueness, it will fail in a very odd and bad way IMO 13:48:44 I like 1 13:48:59 shurley: that is a fair point 13:49:04 Names will be ugly but at least that value is accessible from deprovision and bind/unbind 13:49:09 I like 1 also 13:49:10 I think 1 makes the most sense 13:49:16 +1 13:49:17 1 follows the convention of for example what pod names look like under a replica set. 13:49:21 in the end. what should be communicated is that it is up to the servicebundle developer to handle this 13:49:27 I prefer 3 once it becomes a thing 13:49:28 er, replication controller. 13:49:33 mhrivnak, +1 13:49:41 but 1 should work and requires no work from the broker 13:50:15 shurley: I think if bundle developers want to do that, that is fine. I will update the issue to reflect that there are not any plans for the broker to be involved in the object naming. 13:50:24 which also means it would work seamlessly if the service bundle is run by something other than the broker 13:50:27 is there any implications on upgrades here if the naming convention change? 13:51:00 good question 13:51:05 As in for existing service deployed via the broker 13:51:15 I think a bundle would have to manage that themselves no? 13:51:20 maleck13: none that I am aware of. the service instance id is available to the bundle on all actions 13:51:55 shurley, +1 13:52:01 maybe I missing something. But is this change to the module 13:52:05 ie. if you always say name = 'hello-world' + _apb_service_instance_id then you should be able to handle it for provision/update/deprovision/etc 13:52:12 that created things like the deployment configs 13:52:39 maleck13: no. This is for bundles in general. Most hardcode the name to something like 'postgresql' 13:52:45 ok 13:53:02 +1 13:53:39 thank you shurley for bringing up your concerns, I will update the hello-world-apb to use #1 and update the issue to state the broker's place in naming (read: none) 13:54:11 #action dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming 13:54:11 rhallisey: action 13:54:25 the broker gives the bundle identifying information and it can name objects however it chooses 13:54:48 and the hello-world-apb PR lives one more day :) 13:54:55 :) 13:55:01 #topic Features 13:55:01 rhallisey: topic 13:55:09 #info APB state support targeting 3.11 now 13:55:09 rhallisey: info 13:55:32 nothing more on that just info 13:55:32 maleck13, I was under the impression this was close to being done 13:55:55 april 4th done? 13:56:07 rhallisey: no only starting to look at now and have a number of other time commitments 13:56:18 maleck13, ok thanks for the update 13:56:20 the proposal only closed recently 13:56:56 did anyone want to talk about other features they are working on? 13:57:07 if not I'll move to open discussion 13:57:12 I can quickly talk about bundle-lib 13:57:15 sure 13:57:19 #info bundle-lib 13:57:19 rhallisey: info 13:57:28 bundle-lib is in pre-release, we have a milestone to get it to 1.0 13:57:28 For oc cluster up not working: https://github.com/openshift/origin/issues/19109 13:57:38 if you see anything that you want to take, please do 13:58:11 I am still finding pain points as I try to use it for other things and will be making updates to it that way 13:58:14 shurley: just FYI, the CRD work I took is probably on a backburner until I finish my catalog committments 13:58:15 shurley, are all the open issue for 1.0 or only a sub set? 13:58:29 I can take myself off it if someone else wants to pick it up 13:59:05 all right now 13:59:28 ok 13:59:47 #topic Open Discussion 13:59:47 rhallisey: topic 13:59:56 #info Debugging CI build failures 13:59:56 rhallisey: info 14:00:40 agree with maleck13, docs would be great 14:01:02 do any of our internal documents discuss the travis gate? 14:01:03 I can help write them 14:01:06 I mean, I just want them to work :) at this point 14:01:32 If so, I think it makes sense to make that public. 14:01:39 maleck13: I was trying to help debug your PR yesterday but got busy 14:02:01 I think that unbind might not be working and that is the reason the gate is broken 14:02:15 shurley: thanks I think I have an idea now but also the broker runs in a different config during the ci right 14:02:34 I think it uses whatever catasb does 14:02:51 not really that different. they both use the deployment template 14:03:22 ok I noticed it used not launcing apb on bind for example 14:03:32 that is the default still 14:03:49 ok good know 14:03:55 I think. jmrodri ^^ 14:04:20 Yeah believe that's still the default, is there a timeline on when that's changing? 14:04:37 I created an issue on that so we don't need to discuss during this meeting. 14:04:51 It is really just a general note around helping external contributions 14:04:59 reading back 14:05:17 maleck13, If I have time today I'll put together some docs identifying how ci runs 14:05:46 rhallisey: cool happy to collaborate with anything I learn while debugging my build 14:05:56 maleck13, that would be great 14:05:57 launch_apb_on_bind tells the broker to actually run an APB when bind or unbind is called. It is also gated on the the async flag (accepts_incomplete) 14:06:18 seems to me that if launch_apb_on_bind is false that unbind should attempt to remove any binds 14:06:27 just so everyone is aware, oc client is breaking in the openshift travis job. Planning to fix it here: https://github.com/openshift/ansible-service-broker/pull/856 14:06:28 (or deprovision? I think it was deprovision) 14:07:20 jmrodri: have an issue here which I will update with more details https://github.com/openshift/ansible-service-broker/issues/858 14:07:26 don't want to derail the meeting 14:07:40 maleck13: okay I will look at that, thanks 14:07:45 is there any more open discussion items 14:08:26 I'd love to get some review on this: https://github.com/ansibleplaybookbundle/helm2bundle/pull/4 14:08:43 Just a reminder; no other detail to discuss now. 14:09:00 cool mhrivnak, thanks 14:09:14 ok thanks folks! 14:09:17 #endmeeting -------------- next part -------------- ==================================== #asbroker: Automation Broker 3-27-18 ==================================== Meeting started by rhallisey at 13:30:57 UTC. The full logs are available at asbroker/2018/asbroker.2018-03-27-13.30.log.html . Meeting summary --------------- * Attendance (rhallisey, 13:31:15) * News (rhallisey, 13:32:00) * OpenShift 3.10 feature freeze 4/4/18 (rhallisey, 13:32:09) * OpenShift 3.11 feature freeze around 7/4/18 (rhallisey, 13:34:11) * Bugs/Issue triage (rhallisey, 13:35:27) * WIP] displayWhen for conditional rendering of fields (rhallisey, 13:35:38) * [WIP] displayWhen for conditional rendering of fields (rhallisey, 13:35:46) * LINK: https://github.com/openshift/ansible-service-broker/pull/834 (rhallisey, 13:36:06) * ACTION: : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue (rhallisey, 13:44:57) * ACTION: jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal (rhallisey, 13:46:17) * k8s/origin object naming (rhallisey, 13:46:32) * LINK: https://github.com/ansibleplaybookbundle/postgresql-apb/issues/40 (rhallisey, 13:46:39) * LINK: https://github.com/openshift/ansible-service-broker/issues/853 (rhallisey, 13:46:46) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1542235 (dzager, 13:46:53) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1542235 (rhallisey, 13:47:04) * ACTION: dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming (rhallisey, 13:54:11) * Features (rhallisey, 13:55:01) * APB state support targeting 3.11 now (rhallisey, 13:55:09) * bundle-lib (rhallisey, 13:57:19) * Open Discussion (rhallisey, 13:59:47) * Debugging CI build failures (rhallisey, 13:59:56) Meeting ended at 14:09:17 UTC. Action Items ------------ * : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue * jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal * dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming Action Items, by person ----------------------- * dzager * dzager use option 1) name the objects based on the service instance id (ie. hello-world-1234-5678) of naming * jmrodri * jmrodri to close https://github.com/openshift/ansible-service-broker/pull/834 and open a proposal * **UNASSIGNED** * : community to close https://github.com/openshift/ansible-service-broker/pull/834 and open an issue People Present (lines said) --------------------------- * rhallisey (66) * shurley (41) * brokerbot (28) * jmrodri (26) * dzager (26) * maleck13 (25) * ernelson (19) * dymurray (9) * mhrivnak (5) * jmontleon (2) * fabianvf (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot From ernelson at redhat.com Tue Mar 27 15:50:21 2018 From: ernelson at redhat.com (Erik Nelson) Date: Tue, 27 Mar 2018 11:50:21 -0400 Subject: [Ansible-service-broker] 03/26 Service Catalog SIG Meeting Summary Message-ID: Hi folks, I've been attending the Catalog SIG meetings and thought I would forward a quick summary of what's going on over there since some of it affects what we do: * Discussion about moving Paul's broker client library out of his personal repo and into either the osb-kit org (https://github.com/osbkit), or a new https://github.com/kubernetes-sigs repo. The kubernetes-sigs org allows freedom for sigs to create and manage their own repos, amongst other benefits. Decision forthcoming. * Allow deletion of binding with incorrect service reference PR (https://github.com/kubernetes-incubator/service-catalog/pull/1827). Sounds like there is a garbage collection routine that will kick in and handle this case, PR closed. * Proposal for Default Service Plans introduced: https://github.com/kubernetes-incubator/service-catalog/issues/1873, I recommend reading through the attached doc for the problem statement and full details. It's interesting from a helm perspective. * PodPresets are on the horizon: https://github.com/kubernetes-incubator/service-catalog/pull/1754 Other stuff: * Microsoft is hosting a F2F for the catalog/OSB groups the week of April 9th, so there will likely be a batch of news coming out of that. - Erik From shurley at redhat.com Tue Mar 27 20:58:14 2018 From: shurley at redhat.com (Shawn Hurley) Date: Tue, 27 Mar 2018 16:58:14 -0400 Subject: [Ansible-service-broker] Release 0.1.1 of Bundle-Lib Message-ID: <8B1916FB-4B83-453F-B544-2C776C2C3012@redhat.com> Hello all, Just letting everyone know that 0.1.1 of bundle-lib was created. https://github.com/automationbroker/bundle-lib/releases/tag/0.1.1 Thanks, Shawn Hurley -------------- next part -------------- An HTML attachment was scrubbed... URL: From edube at redhat.com Wed Mar 28 15:34:22 2018 From: edube at redhat.com (Eric Dube) Date: Wed, 28 Mar 2018 11:34:22 -0400 Subject: [Ansible-service-broker] Ansible APBs possible problems In-Reply-To: References: Message-ID: Jorge- > On Mar 28, 2018, at 11:03 AM, Jorge Morales Pou wrote: > > Hi team, > Was singing my coffee during my PTO and looking at the 3.9 announcement on the blog where we highlight a feature of the ansible broker for update preserving data. While I personally think that the implementation should be only taken as an example and the "caveats" should be properly documented (e.g. this won't work on any scenario like big data migration that don't fit on the container storage), All of RH?s published APB?s are intended to be ?examples?. All of them leverage RHSCL database images and as such fall under the support terms outlined here: https://access.redhat.com/articles/183263 > I went to look into the apb implementation, and saw that it will not work as a user would expect. The apbs for database in our blog linked have the following hardcoded: "app: rhscl-postgresql-apb" > Assuming that the application where the database will be deployed have a fixed name and also making all the databases deployed in a project with multiple applications be grouped not on the user's app but on the same ?rhscl-postgresql-app", which is probably not aligned with any user's intention. I?ll defer this to one of the developers on this list to comment on. > Also I noted that for provisioning, binding, etc... it creates an ephemeral project. There's many environments where a user might not be allowed to create projects. Not sure who's creating this projects, if it's the OAB or the OAB on behalf of the user (I think the latter). I'm any case, I personally don't think this is a viable model in many environments. Perhaps I?m not following you, but are you saying that no one will be deploying services via the Service Catalog? Perhaps you can explain more as I?ve seen a lot of interest around this use case with customers. > I ask that we revisit these ASAP, as this is GA and seems like we do support it. The earliest we get this right, the less issues we'll have open. > > Resuming my coffee. > > Cheers, > > Jorge Morales > Red Hat OpenShift > EMEA Field Product Manager | Developer Advocate > http://jorgemoral.es | @UnPOUcoDe > > This mail has been written from a mobile device. Excuse any typo. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmatthew at redhat.com Wed Mar 28 15:53:27 2018 From: jmatthew at redhat.com (John Matthews) Date: Wed, 28 Mar 2018 11:53:27 -0400 Subject: [Ansible-service-broker] Ansible APBs possible problems In-Reply-To: References: Message-ID: On Wed, Mar 28, 2018 at 11:34 AM, Eric Dube wrote: > Jorge- > > On Mar 28, 2018, at 11:03 AM, Jorge Morales Pou > wrote: > > Hi team, > Was singing my coffee during my PTO and looking at the 3.9 announcement on > the blog where we highlight a feature of the ansible broker for update > preserving data. While I personally think that the implementation should be > only taken as an example and the "caveats" should be properly documented > (e.g. this won't work on any scenario like big data migration that don't > fit on the container storage), > > > All of RH?s published APB?s are intended to be ?examples?. All of them > leverage RHSCL database images and as such fall under the support terms > outlined here: https://access.redhat.com/articles/183263 > > I went to look into the apb implementation, and saw that it will not work > as a user would expect. The apbs for database in our blog linked have the > following hardcoded: "app: rhscl-postgresql-apb" > Assuming that the application where the database will be deployed have a > fixed name and also making all the databases deployed in a project with > multiple applications be grouped not on the user's app but on the same > ?rhscl-postgresql-app", which is probably not aligned with any user's > intention. > > > I?ll defer this to one of the developers on this list to comment on. > Our example APBs are intended to support deploying 1 instance of a specific ServiceClass per namespace. Open to considering improvements if you'd like to file an RFE. > > Also I noted that for provisioning, binding, etc... it creates an > ephemeral project. There's many environments where a user might not be > allowed to create projects. Not sure who's creating this projects, if it's > the OAB or the OAB on behalf of the user (I think the latter). I'm any > case, I personally don't think this is a viable model in many environments. > > > Perhaps I?m not following you, but are you saying that no one will be > deploying services via the Service Catalog? Perhaps you can explain more as > I?ve seen a lot of interest around this use case with customers. > The broker is creating an ephemeral/transient namespace to run the APBs for security purposes, effectively we create a sandbox to execute the APB then we delete the transient namespace to ensure nothing is left hanging around other than the artifacts the APB intended to create in the target namespace. This behavior is configurable and can be disabled if an administrator wanted to forgo the 'sandbox' and run the APB directly in target namespace. Might be good for us to schedule a call so we can discuss some of your concerns in real time. If that would be helpful, please schedule a meeting and include myself, Todd Sanders, and Eric Dube. Thank you for the feedback. > > I ask that we revisit these ASAP, as this is GA and seems like we do > support it. The earliest we get this right, the less issues we'll have open. > > Resuming my coffee. > > Cheers, > > Jorge Morales > Red Hat OpenShift > EMEA Field Product Manager | Developer Advocate > http://jorgemoral.es | @UnPOUcoDe > > This mail has been written from a mobile device. Excuse any typo. > > > > _______________________________________________ > 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 dzager at redhat.com Wed Mar 28 15:59:29 2018 From: dzager at redhat.com (David Zager) Date: Wed, 28 Mar 2018 15:59:29 +0000 Subject: [Ansible-service-broker] Ansible APBs possible problems In-Reply-To: References: Message-ID: Greetings, Comments in line. Respectfully, David Zager On Wed, Mar 28, 2018, 11:35 Eric Dube wrote: > Jorge- > > On Mar 28, 2018, at 11:03 AM, Jorge Morales Pou > wrote: > > Hi team, > Was singing my coffee during my PTO and looking at the 3.9 announcement on > the blog where we highlight a feature of the ansible broker for update > preserving data. While I personally think that the implementation should be > only taken as an example and the "caveats" should be properly documented > (e.g. this won't work on any scenario like big data migration that don't > fit on the container storage), > > > All of RH?s published APB?s are intended to be ?examples?. All of them > leverage RHSCL database images and as such fall under the support terms > outlined here: https://access.redhat.com/articles/183263 > > I went to look into the apb implementation, and saw that it will not work > as a user would expect. The apbs for database in our blog linked have the > following hardcoded: "app: rhscl-postgresql-apb" > Assuming that the application where the database will be deployed have a > fixed name and also making all the databases deployed in a project with > multiple applications be grouped not on the user's app but on the same > ?rhscl-postgresql-app", which is probably not aligned with any user's > intention. > > > I?ll defer this to one of the developers on this list to comment on. > You are correct. Only one postgresql-apb can be properly provisioned in a single namespace at this time. We have a bug for this: https://bugzilla.redhat.com/show_bug.cgi?id=1542235 > Also I noted that for provisioning, binding, etc... it creates an > ephemeral project. There's many environments where a user might not be > allowed to create projects. Not sure who's creating this projects, if it's > the OAB or the OAB on behalf of the user (I think the latter). I'm any > case, I personally don't think this is a viable model in many environments. > > > Perhaps I?m not following you, but are you saying that no one will be > deploying services via the Service Catalog? Perhaps you can explain more as > I?ve seen a lot of interest around this use case with customers. > As far as I understand the OAB is creating the ephemeral project with the permissions granted to the broker and not on behalf of any particular user. I am interested in knowing more about environments where the OAB would not have appropriate permissions to create the ephemeral project (or sandbox project) that wasn't an error in the way the OAB was deployed. > I ask that we revisit these ASAP, as this is GA and seems like we do > support it. The earliest we get this right, the less issues we'll have open. > > Resuming my coffee. > > Cheers, > > Jorge Morales > Red Hat OpenShift > EMEA Field Product Manager | Developer Advocate > http://jorgemoral.es | @UnPOUcoDe > > This mail has been written from a mobile device. Excuse any typo. > > > _______________________________________________ > 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 Wed Mar 28 17:38:39 2018 From: jesusr at redhat.com (jesus m. rodriguez) Date: Wed, 28 Mar 2018 13:38:39 -0400 Subject: [Ansible-service-broker] OSB call summary 3/27 Message-ID: <1522258719.4255.14.camel@redhat.com> The Open Service Broker API spec group meets every Tuesday @ 12:30pm ET. I have been attending these meetings since Nov 2017. I thought it might be good to share the meeting notes that may affect the Automation Broker community. Here is a summary from this weeks call. * team attendees: Jesus, Erik, & Michael * Acked a few PRs that were waiting for reviews * A discussion about the clarify of the Originating Identity header: https://github.com/openservicebrokerapi/servicebroker/issues/476 * discussion was cut time boxed, more to occur later * the key issue is how k8s handles subsequent Spec updates * declaration of service instance dependencies, proposal to be created before F2F by Florian (SAP) https://github.com/openservicebrokerapi/servicebroker/issues/427 * updatable credentials in bindings? (service-catalog) https://github.com/kubernetes-incubator/service-catalog/issues/1831 * Scott (Google) to revive the update bindings issue with regards to credential rotation, can creds change in between GET requests, etc * We (automation broker) will investigate to see how this affects us 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) +---------------------------------------------+ | "Those who cannot remember the past | | are condemned to repeat it." | | -- George Santayana | +---------------------------------------------+ From cbrookes at redhat.com Thu Mar 29 08:02:05 2018 From: cbrookes at redhat.com (Craig Brookes) Date: Thu, 29 Mar 2018 09:02:05 +0100 Subject: [Ansible-service-broker] development workflow Message-ID: Wondering what the workflow is now with the bundle-lib and the broker. Is it a case of making changes there and bumping the release on the lib repo, then updating the broker with the new version of the dependency? Some issues I am looking at need changes in the lib and in the broker -- Craig Brookes RHMAP @maleck13 Github -------------- next part -------------- An HTML attachment was scrubbed... URL: From jesusr at redhat.com Thu Mar 29 11:37:15 2018 From: jesusr at redhat.com (jesus m. rodriguez) Date: Thu, 29 Mar 2018 07:37:15 -0400 Subject: [Ansible-service-broker] development workflow In-Reply-To: References: Message-ID: <4ffa7f82-5c52-4dc3-8ebb-76fb82d0bc34@redhat.com> Craig, That is one work flow and probably the most stable. I recently started making changes to the bundle-lib in vendor so I could test things faster. then I create a patch using gendiff to apply it to the bundle-lib repo. I think symlinks were brought up but not sure if that will work as Go is finicky with symlinks. Sincerely, Jesus ?Sent from Blue ? On Mar 29, 2018, 4:02 AM, at 4:02 AM, Craig Brookes wrote: >Wondering what the workflow is now with the bundle-lib and the broker. >Is >it a case of making changes there and bumping the release on the lib >repo, >then updating the broker with the new version of the dependency? >Some issues I am looking at need changes in the lib and in the broker > >-- >Craig Brookes >RHMAP >@maleck13 Github > > >------------------------------------------------------------------------ > >_______________________________________________ >Ansible-service-broker mailing list >Ansible-service-broker at redhat.com >https://www.redhat.com/mailman/listinfo/ansible-service-broker From ernelson at redhat.com Thu Mar 29 11:41:06 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 29 Mar 2018 07:41:06 -0400 Subject: [Ansible-service-broker] development workflow In-Reply-To: <4ffa7f82-5c52-4dc3-8ebb-76fb82d0bc34@redhat.com> References: <4ffa7f82-5c52-4dc3-8ebb-76fb82d0bc34@redhat.com> Message-ID: > I think symlinks were brought up but not sure if that will work as Go is finicky with symlinks. This is a path of great pain and sorrow. I would love to hear the "gopher" solution to this, because I've gotten so frustrated with this dep dev experience that I've started to bind mount into vendor. > Sincerely, > Jesus > > ?Sent from Blue > > On Mar 29, 2018, 4:02 AM, at 4:02 AM, Craig Brookes wrote: >>Wondering what the workflow is now with the bundle-lib and the broker. >>Is >>it a case of making changes there and bumping the release on the lib >>repo, >>then updating the broker with the new version of the dependency? >>Some issues I am looking at need changes in the lib and in the broker >> >>-- >>Craig Brookes >>RHMAP >>@maleck13 Github >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>Ansible-service-broker mailing list >>Ansible-service-broker at redhat.com >>https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > _______________________________________________ > Ansible-service-broker mailing list > Ansible-service-broker at redhat.com > https://www.redhat.com/mailman/listinfo/ansible-service-broker From cbrookes at redhat.com Thu Mar 29 12:36:11 2018 From: cbrookes at redhat.com (Craig Brookes) Date: Thu, 29 Mar 2018 13:36:11 +0100 Subject: [Ansible-service-broker] development workflow In-Reply-To: References: <4ffa7f82-5c52-4dc3-8ebb-76fb82d0bc34@redhat.com> Message-ID: It is an (lets call it interesting) problem when you have a library that is a core part of another application. We faced similar problems and headaches with our nodejs applications. On Thu, Mar 29, 2018 at 12:41 PM, Erik Nelson wrote: > > I think symlinks were brought up but not sure if that will work as Go is > finicky with symlinks. > > This is a path of great pain and sorrow. > > I would love to hear the "gopher" solution to this, because I've > gotten so frustrated with this dep dev experience that I've started to > bind mount into vendor. > > > Sincerely, > > Jesus > > > > ?Sent from Blue > > > > On Mar 29, 2018, 4:02 AM, at 4:02 AM, Craig Brookes > wrote: > >>Wondering what the workflow is now with the bundle-lib and the broker. > >>Is > >>it a case of making changes there and bumping the release on the lib > >>repo, > >>then updating the broker with the new version of the dependency? > >>Some issues I am looking at need changes in the lib and in the broker > >> > >>-- > >>Craig Brookes > >>RHMAP > >>@maleck13 Github > >> > >> > >>------------------------------------------------------------------------ > >> > >>_______________________________________________ > >>Ansible-service-broker mailing list > >>Ansible-service-broker at redhat.com > >>https://www.redhat.com/mailman/listinfo/ansible-service-broker > > > > > > _______________________________________________ > > 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 ernelson at redhat.com Thu Mar 29 12:40:48 2018 From: ernelson at redhat.com (Erik Nelson) Date: Thu, 29 Mar 2018 08:40:48 -0400 Subject: [Ansible-service-broker] development workflow In-Reply-To: References: <4ffa7f82-5c52-4dc3-8ebb-76fb82d0bc34@redhat.com> Message-ID: On Thu, Mar 29, 2018 at 8:36 AM, Craig Brookes wrote: > It is an (lets call it interesting) problem when you have a library that is > a core part of another application. We faced similar problems and headaches > with our nodejs applications. npm at least has first class support for "link" (https://docs.npmjs.com/cli/link), allowing you to link in a dependency from your system. pip has editable installs. Rust cargo has local module references. Developing on a library containing your core functionality and consuming that in a variety of mains is a very common and well-worn pattern. It is disappointing there is no apparent thought around this with go, but it's also clear dependency management as a whole was a complete afterthought. > On Thu, Mar 29, 2018 at 12:41 PM, Erik Nelson wrote: >> >> > I think symlinks were brought up but not sure if that will work as Go is >> > finicky with symlinks. >> >> This is a path of great pain and sorrow. >> >> I would love to hear the "gopher" solution to this, because I've >> gotten so frustrated with this dep dev experience that I've started to >> bind mount into vendor. >> >> > Sincerely, >> > Jesus >> > >> > ?Sent from Blue >> > >> > On Mar 29, 2018, 4:02 AM, at 4:02 AM, Craig Brookes >> > wrote: >> >>Wondering what the workflow is now with the bundle-lib and the broker. >> >>Is >> >>it a case of making changes there and bumping the release on the lib >> >>repo, >> >>then updating the broker with the new version of the dependency? >> >>Some issues I am looking at need changes in the lib and in the broker >> >> >> >>-- >> >>Craig Brookes >> >>RHMAP >> >>@maleck13 Github >> >> >> >> >> >>------------------------------------------------------------------------ >> >> >> >>_______________________________________________ >> >>Ansible-service-broker mailing list >> >>Ansible-service-broker at redhat.com >> >>https://www.redhat.com/mailman/listinfo/ansible-service-broker >> > >> > >> > _______________________________________________ >> > 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