Guidance for shared installs

[ijmitch]

What is best practice for shared installs?

Guidance needs to cover at least:

• where to put zopen in the filesystem
• user profile updates
• managing upgrades
• mixing a subset of the tools which are shared with users installing additional tools privately

[ijmitch]

Probably need a scenario where there's OEF installs mixed with zopen too.

[lbdyck]

This does need to be addressed - especially for the smaller shops with less staff and those shops with less experienced staff.

[lbdyck]

Include

1. update existing zot filesystem or update another and swap mount points
2. split zot into functional subsets or leave as one full set
3. testing and validation prior to production rollout and how to backout if necessary
4. how to document the updates for change control, for management, for users

[IgorTodorovskiIBM]

Important topic! Here's a related discussion from 2023: https://github.com/orgs/ZOSOpenTools/discussions/465

There's also the zopen promote command that @DevonianTeuchter implemented which will help with item 1 from @lbdyck's list.

[lbdyck]

This entire topic should probably be expanded upon for zot and also for the OEF

[MikeFultonDev]

Probably need a scenario where there's OEF installs mixed with zopen too.

and also 3rd party versions of tools

[MikeFultonDev]

audit comes into this as well I would say - your shared install plan needs to factor in how audit and CVE management could cause updates.