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

Wed Oct 11 12:38:44 UTC 2017

@Joe - as we are still in a POC phase, we are trying to explore and de-risk
as mush as possible. The build Farm is a known quantity and we now have a
steel thread.

By comparison, 3Scale and where/how it fits is a pretty big unknown at the
moment - hence the prioritisation to explore and de-risk this integration.

--
John Frizelle
Chief Architect, Red Hat Mobile
Consulting Engineer

mobile: *+353 87 290 1644 <//+353872901644>*
twitter:* @johnfriz*
skype: *john_frizelle*
mail: *jfrizell at redhat.com <jfrizell at redhat.com>*

On 11 October 2017 at 13:31, David Martin <davmarti at redhat.com> wrote:

> Hey Joe,
>
> re: "re. Jason's mail - Where was that sent (not sure myself or Nano
> received it)? "
>
> There were a mail sent out by Jason in the last day summarising the Build
> Farm integration sprint (Sprint 4), and the 3Scale integration sprint plans
> (Sprint 5).
> Both were sent out to feedhenry-dev (like this mail).
> Maybe you have it filtered? (i cc'd you directly on this one, which may be
> why you saw it)
>
> Here is an archive of the mail anyways
> http://feedhenry-dev.2363497.n4.nabble.com/MCP-PoC-Sprint-
> 5-Goals-and-a-brief-recap-on-Sprint-4-tt197.html
>
>
> On 11 October 2017 at 13:24, Craig Brookes <cbrookes at redhat.com> wrote:
>
>> 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
>>
>
>
>
> --
> David Martin
> Red Hat Mobile
> Twitter: @irldavem
> IRC: @irldavem (feedhenry, mobile-internal)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20171011/49c02e52/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 11472 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/feedhenry-dev/attachments/20171011/49c02e52/attachment.png>