Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packaging Distribution and Management Hill #1440

Closed
stevenhorsman opened this issue Jun 16, 2020 · 3 comments
Closed

Packaging Distribution and Management Hill #1440

stevenhorsman opened this issue Jun 16, 2020 · 3 comments
Labels

Comments

@stevenhorsman
Copy link
Member

stevenhorsman commented Jun 16, 2020

Hills:
**As a z/OS System Programmer I can manage extensions to Zowe in a reliable, repeatable and consistent manner across conformant offerings, through download, install, configure into an existing Zowe instance, auditability of which extensions are active, upgrade, uninstall

As a z/OS conformant extension I can package my offering in a way that z/OS system programmers can download and install/extend/configure their existing Zowe instances in a consistent way.**

Notes:
There are a number of issues with the current version of Zowe that make it quite coupled and not very flexible. This will cause challenges going forward when thinking about HA, hybridisation/containerisation of Zowe and adoption by extenders.

Extending Zowe Lifecycle.pptx

@1000TurquoisePogs
Copy link
Member

package management edit

Here's an edit I made to clarify package manager metadata versus zowe metadata, from today's call.

@1000TurquoisePogs
Copy link
Member

an example of how you may package code so that runtime structure is not disturbed from latest experiments:
https://github.com/zowe/zlux-build/blob/staging/conda/README.md

@1000TurquoisePogs
Copy link
Member

Implemented in v2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants