Open RASakach opened 3 weeks ago
Evaluation Information from SHARE KC:
Optimizing Zowe’s API Mediation Layer for Complex Enterprise Workloads
Making the mainframe simple again with the Zowe command line interface
Top 10 Administrative Tips for Achieving and regtaining a healthy, high-performing Zowe
Zowe v3 is coming in September. Learn what to expect, and please tell us what’s missing
Let’s Talk Zowe! End Users Share Their Stories
From Ansible to Zowe, Learn how Open Source Technology is Changing the Face of Mainframe Computing.
(This was hosted by the Open Source Track in their room so we could ask them to have it in their agenda for DC or else we could put it in the Zowe track, either way it looks like it resonated with the attendees).
**Learn How Zowe Explorer Is Empowering Both New and Experienced Mainframers
Preliminary plans:
Zowe Slots (9)
I really like the idea of showcasing the explorers together.
The Top 10 tips session was also good for Zowe APIML. How about we widen that to be all of Zowe so we cover tips from Zowe Explorer, CLI, Zowe Desktop, APIML, ...
In Nola we did a session on vendor extensions where we had Segus, Phoenix and BMC. What about
Showcasing vendor extensions for the Zowe ecosystem. We could see if Ulf from Segus will be in KC (or Roy) to present, and likely Ed from PSI will be there to showcase EJS. We could also see if HCL are readly to present their CICS Interdependency Analyzer extension (which will be GA by then).
For Zowe CLI powering mainframe automation, I think this should be a wider Zowe CLI session not just focusing on automation. In KC I presented "How Zowe CLI is making the mainframe simple again" that covered everything from REXX scripts, SSH, JES, CICS, MQ, Db2 (so all core Zowe CLI and core extensions). For me automation really needs vendor products like CA7 or Ansible and I think we should keep the presentation sweet and simple without overcooking it.
The session with Adaptigent went well too, so I'll reach out to see if they want to be involved with an APIML talk.
I don't think we should do a Zowe APIML install and config lab. In my experience users run into problems because their systems have particular quirks that need custom config and we won't be able to create enough variety in whatever systems we host the labs with. The Install and Config talk should be enough if we cover the golden path install and config as well as the quirks that issues like networking, custom user IDs, different ESMs, different kinds of cert, all throw in the path of a successful config.
I'm thinking about this one: Zowe Ecosystem: a session to explain (again) what are the components of the Zowe, both for the client side and the server side (of course, there are a lot of them, so from my perspective, I see it like a "speedrun" session, showcasing all the things Zowe has, dividing the client and server side). The reason of the idea for this session - we are encountering misconceptions in Zowe products list. There are still such questions like "I installed Zowe, what to do next?", and then we are trying to figure out, what the "intstalled Zowe" actually is: is it the server-side components, or the client-side ones, or both of them.
+1 for the explorers together session, @JillieBeanSim and I had this idea back in Orlando, didn't discuss in details.
Zowe Community Sessions Wish-List
(1) Zowe V3 Overview - having Community Members there; SHARE KC was well attended (2) Top 10 for Zowe Clients (similar to what we did for Zowe Server in KC) (3) Customer Panel Session: Different Customers and new topics