zowe / zac

Zowe Leadership Committee collaboration
Creative Commons Attribution 4.0 International
14 stars 14 forks source link

Zowe Sub-Project Proposal: Zowe on the go (Mobile App) #157

Closed MarkAckert closed 4 years ago

MarkAckert commented 4 years ago

Zowe on the go

"Interacting with Zowe from your mobile device is now within reach"

This project was developed during a Zowe Hackathon at Broadcom. The goal of this project was to develop a fast, on-the-move identification/triage application for mainframe operations and systems support. "As an on-call support, my immediate needs are to check the status of running services and to perform a number of jobs services: get a list of jobs, get content from a job file output, submit a job, and more." This project adds another way modern developers and system/operations support interact with the mainframe, built against Zowe API Mediation Layer, thus bringing more value to the Zowe ecosystem and its adopters.

The mobile application aligns with Broadcom’s direction to support and contribute to Zowe. The applications ties directly into Zowe (see project description).

Mark Ackert, Jean-Louis

To be contributed as Eclipse Public License 2.0

Github (Public Repository Link to be added)

N/A (Use existing Zowe build infrastructure)

Slack Channel

Github

Incubation

MarkAckert commented 4 years ago

@jellypuno @crawr @jandadav @muzikovam @zowe/zlc

All, this is the sub-project proposal as brought up on the ZLC this week.

The team is planning to present/discuss the proposal to the ZLC on the January 15th meeting, and a public Github repository with the corresponding code should be added next week.

Please review this proposal prior to the January 15th date. Thank you!

jplinardon commented 4 years ago

I have a few questions:

  1. Would this project be a mobile application only or would it/could it be considered a framework for Zowe mobile application development
  2. What considerations are provided for authentication and communication security
  3. Given the stated purpose of monitoring services and jobs, would a backend/server be part of this project, or would it only poll existing APIs?
jellypuno commented 4 years ago

Hi @jplinardon

Would this project be a mobile application only or would it/could it be considered a framework for Zowe mobile application development

At its current state, It is a mobile application that accesses Zowe Services through REST APIs. Will it be a framework for future Zowe mobile development? This is open for discussion.

What considerations are provided for authentication and communication security

We are communicating with API Mediation Layer in terms of authentication with credentials. Currently we are using Basic Authentication to access the services. But in future, when the changes are available in API-ML, we can use tokens and maybe 2FA.

Given the stated purpose of monitoring services and jobs, would a backend/server be part of this project, or would it only poll existing APIs?

It is only using existing APIs. Basically, the concept that we have is to fire APIs that are available in z/OS and discovered by API ML. We are accessing via the base URL provided by Mediation Layer.

jellypuno commented 4 years ago

Github https://github.com/jellypuno/Zowe-on-the-go

armstro commented 4 years ago

Many thanks to the team for the presentation - would someone please post the slides that describe the project. I will discuss with OMP (John Mertic) on how we get the code scanned and included into the project. Posting the slides here would be great for future reference.

jellypuno commented 4 years ago

Hi, I have added the slides in the repo: https://github.com/jellypuno/Zowe-on-the-go/tree/master/app/resources/presentation

MarkAckert commented 4 years ago

Contribution complete; closing.