[feedhenry-dev] Change of Scope for 3Scale/APICast Integration for 5.x

[Craig Brookes]

Correct. We left the BF with a working debug build. Video for that coming
shortly. However there were other things we would have liked to do with the
BF which are currently in the backlog. So reducing the scope of 3scale
integration, means we may get a little more done on the BF (private repo
build etc)

Craig

On Wed, Oct 11, 2017 at 1:22 PM, Joe O'Reilly <joreilly at redhat.com> wrote:

> I'd thought we'd agreed that adding BF got us an end-to-end flow, making
> the overall POC really compelling (as is) & that the 3Scale would follow on
> afterwards?
>
>
>
> On 11 October 2017 at 13:18, Craig Brookes <cbrookes at redhat.com> wrote:
>
>> @Joe build farm issues are at the top of the backlog for the remaining
>> work. So if the integration for 3scale goes well they will be the first
>> ones brought in to the sprint
>>
>> Craig
>>
>> On Wed, Oct 11, 2017 at 1:12 PM, Joe O'Reilly <joreilly at redhat.com>
>> wrote:
>>
>>> Thanks David,
>>>
>>> re. Jason's mail - Where was that sent (not sure myself or Nano received
>>> it)?
>>>
>>> As for the rest - looks fine, the only Q I have is where this leaves the
>>> integration of the BuildFarm effort?
>>>
>>> Thanks,
>>>
>>> Joe.
>>>
>>>
>>> On 11 October 2017 at 12:37, David Martin <davmarti at redhat.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> As per Jason's mail with subject 'MCP PoC - Sprint 5 Goals',
>>>> the Goal of the 5.x team current sprint [0] is:
>>>>
>>>> "looking into 3scale apicast fronting Sync and KeyCloak"
>>>>
>>>> This Goal is actually 2 sub-goals.
>>>> - Put 3Scale in front of Sync, using App ID/App Key authentication
>>>> - Put 3Scale in front of Sync, using OpenID Connect authtentication via
>>>>
>>>> To give some context, the 3Scale integration will require/involve:
>>>> - having a 3Scale SaaS account on 3scale.net (90 day trial accounts
>>>> are available)
>>>> - provisioning the 3Scale gateway (APICast) via the Service Catalog in
>>>> OpenShift
>>>> - MCP will autoconfigure your 3Scale SaaS a/c for sitting in front of
>>>> Sync with App ID/Key authentication
>>>> - APICast will make a call to 3Scale SaaS on startup to get it's
>>>> confguration for doing authentication & proxying to Sync
>>>>
>>>>
>>>> I propose that for this sprint we only focus on the first of these
>>>> sub-goals.
>>>> The OpenID Connect authentication integration can be deferred.
>>>>
>>>>
>>>> Rationale for this proposal:
>>>> - the OpenID Connect authentication option is currently not generally
>>>> available in 3Scale SaaS (may be in the near future, based on activity on
>>>> the apicast repo [1])
>>>> - the Keycloak service will need to be publicly accessible to 3Scale
>>>> SaaS to allow it to configure the necessary client(s) in your Keycloak
>>>>
>>>>
>>>> Thoughts & comments welcome
>>>> Thanks
>>>>
>>>>
>>>> [0] https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=4143
>>>> [1] https://github.com/3scale/apicast
>>>>
>>>>
>>>> --
>>>> David Martin
>>>> Red Hat Mobile
>>>> Twitter: @irldavem
>>>> IRC: @irldavem (feedhenry, mobile-internal)
>>>>
>>>
>>>
>>>
>>> --
>>> Joe O'ReILLY
>>>
>>> GLOBAL PRODUCT MANAGER
>>>
>>> Red Hat Mobile <https://www.redhat.com/>
>>>
>>> Red Hat :  Communications House,
>>>
>>> Cork Road, Waterford City, Ireland X91NY33
>>>
>>> joreilly at redhat.com    M: +353 878205731 <+353%2087%20820%205731>
>>> <https://red.ht/sig> TRIED. TESTED. TRUSTED.
>>> <https://redhat.com/trusted>
>>>
>>
>>
>>
>> --
>> Craig Brookes
>> RHMAP
>> @maleck13 Github
>>
>
>
>
> --
> Joe O'ReILLY
>
> GLOBAL PRODUCT MANAGER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> Red Hat :  Communications House,
>
> Cork Road, Waterford City, Ireland X91NY33
>
> joreilly at redhat.com    M: +353 878205731 <+353%2087%20820%205731>
> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>



-- 
Craig Brookes
RHMAP
@maleck13 Github
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20171011/cf1bef98/attachment.htm>