Closed solsu01 closed 4 years ago
I have added Sean for his review of the slide - also trying to add Peter Fandel but checking with him on whether he has OMP/Zowe github id.
'off-host' is probably not the term you want but I was thinking something like this zowe_offhost_clientSDK.pptx
Thanks for the review!
On the "off-host" term - I am not sure if that's needed in addition to "client". In fact, I don't think there's anything stopping someone from building a python (thanks to Rocket..) or node app using this SDK that runs on z/OS - sorry if I miscommunicated this on the ZLC call.
The "Client" part of SDK just shows that this SDK is a client of server side REST APIs, but the client could be an app running on z/OS or off-platform.
zowe_landscape_update 01.pptx @solsu01 - I've added a 02 chart to the deck with what I think the landscape chart could show - it's not polished but I wanted to
I'll try to put more polish on the slide but heads down trying to get Zowe 1.9 out the door the next couple of days ! Many thanks for taking the initiative on getting this slide updated.
Updates from ZLC call 2/19 Cartier is ok to use this ppt at SHARE: zowe_clientSDK.pptx
For the longer term updated landscape diagram, we'll continue to iterate and refine this ppt: zowe_landscape_update.02.pptx
Looks good to me (who didn't know the knot of snakes logo).....thanks for the edits
Bruce Armstrong IBM System Z Offering Manager- zowe.org 4205 S MIAMI BLVD, DURHAM NC 27703-9141 Email: armstrob@us.ibm.com Tel: 919-254-8773 Cell: 919-931-3132
From: Sujay Solomon notifications@github.com To: zowe/zlc zlc@noreply.github.com Cc: Bruce Armstrong armstrob@us.ibm.com, Assign assign@noreply.github.com Date: 02/19/2020 08:13 AM Subject: [EXTERNAL] Re: [zowe/zlc] Proposal for a new Zowe landscape diagram (#160)
Updates from ZLC call 2/19 Cartier is ok to use this ppt at SHARE: zowe_clientSDK.pptx For the longer term updated landscape diagram, we'll continue to iterate and refine this ppt: zowe_landscape_update.02.pptx — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.
I have had a lot of requests from squad leads, users and the community for an updated landscape diagram, so I've taken another stab at it with the intent of keeping it simple, but covering all the high level active sub-projects and incubation sub-projects: zowe_landscape_update.03.pptx
It would be helpful to settle on this as I'm noticing folks starting to create their own versions since there isn't a standard one to use.
This looks good. I was playing around with the format to try and clarify client/user components from server components, but there's not much real estate to shuffle things around. I made an edit with the some arrows modifications - not sure if this clarifies the diagram or just makes it more busy.
Hi, I would like to ask for your permission if I could use the updated Zowe landscape on the upcoming webcast that I am going to present. I will briefly discuss about Zowe components and I would like the Zowe Mobile App to be part of it.
@MarkAckert @solsu01 I am confused with the arrows on update#04. Is the arrow pointing to APIML means that I am calling the APIML APIs? And the App Framework doesn't do that?
@jellypuno - The API Mediation Layer is an edge server that is able to collate all of the z/OS services used by clients, so that there is one certificate and one endpoint port that needs to be surfaced to clients. APIML also offers the ability to generate a one time use token for authentication that means it can support multi factor authentication (MFA) and for the credential challenge it only occurs once giving the user a single sign-on (SSO) experience. The App Framework (aka web desktop) can be run on its own if a user wishes to, but by default with Zowe both the App Framework and APIML are started, and in this case the App Framework sees the APIML is running and will work behind it as shown in the diagram. This means all of its function works through the APIML port, and SSO occurs between its web desktop and the APIML catalog. You're right that the Zowe Mobile App doesn't work via the APIML, I believe you just call out to the z/OSMF endpoints directly, but going forward having the mobile app work with the APIML is something that would be good to validate with users as a way going forward so that if you wanted to access other services behind the APIML (such as CICS, DB2, CA Endeavor, ...) then you could do so benefitting from SSO/MFA, single certificate, ... Maybe it'd be good to explain that mobile is an incubator project and currently doesn't go via APIML, but as part of maturing to be a Zowe core app that's something being looked at to ensure there is a consistent experience across the suite.
@Joe-Winchester Thank you for the explanation. I appreciate it 😊
I guess first comment is that I thought we were going to try to use the slide for the upcoming OMP webinar as the slide for what is Zowe? This was out growth of the ZLC working sessions (both words and pictures). Maybe this slide has not gotten wide enough review for us to settle on it.
My second comment is maybe we should just admit that we are unlikely to decide on just one picture for Zowe. Comparing the OMP webinar slide to the 04 version above it looks like one provides more detail that a technical audience may care about. We should at least be consistent in whether Zowe components are at the top of the page or bottom. (I do like OMP slide rendering that shows plugs both out of the box (in blue) and custom extensions (in green)).
Maybe we can take a few mins in the ZLC call today to discuss.....maybe we have a couple versions in a central location to be used depending on the audience and how comfortable the presenter is with the technical detail. I recall an attempt to have a github repo of slides at one time.
@jellypuno - The API Mediation Layer is an edge server that is able to collate all of the z/OS services used by clients, so that there is one certificate and one endpoint port that needs to be surfaced to clients. APIML also offers the ability to generate a one time use token for authentication that means it can support multi factor authentication (MFA) and for the credential challenge it only occurs once giving the user a single sign-on (SSO) experience. The App Framework (aka web desktop) can be run on its own if a user wishes to, but by default with Zowe both the App Framework and APIML are started, and in this case the App Framework sees the APIML is running and will work behind it as shown in the diagram. This means all of its function works through the APIML port, and SSO occurs between its web desktop and the APIML catalog. You're right that the Zowe Mobile App doesn't work via the APIML, I believe you just call out to the z/OSMF endpoints directly, but going forward having the mobile app work with the APIML is something that would be good to validate with users as a way going forward so that if you wanted to access other services behind the APIML (such as CICS, DB2, CA Endeavor, ...) then you could do so benefitting from SSO/MFA, single certificate, ... Maybe it'd be good to explain that mobile is an incubator project and currently doesn't go via APIML, but as part of maturing to be a Zowe core app that's something being looked at to ensure there is a consistent experience across the suite.
I believe the Mobile app does go through the API ML.
As discussed on ZLC 6/3, I'm working on a "current" and "future" version of these slides by repurposing @PeterFandelAtRocket 's one from the OMP webinar (for current) and my previous rev in this issue (for future).
Please review this version of "today" and "future" versions with inspiration from the webinar slide that Bruce shared:
If we are good with this, I'd like to place this in the zowe community github for others to use.
@solsu01 with "release" of this ppt in the PI planning do we want to consider this one closed?
Yes, good with me to close.
As discussed in ZLC meeting 2/12, let's collaborate on updating the Zowe landscape diagram with the new sub-projects like Mobile App and ZDK (Python, NodeJS). zowe_landscape_update.pptx