[Ansible-service-broker] Ansible APBs possible problems

[Eric Dube]

Jorge-

> On Mar 28, 2018, at 11:03 AM, Jorge Morales Pou <jmorales at redhat.com> 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 <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 <http://jorgemoral.es/> | @UnPOUcoDe
> 
> This mail has been written from a mobile device. Excuse any typo.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ansible-service-broker/attachments/20180328/c33386bc/attachment.htm>