Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

Feedback on the "OpenShift and The Organization" guide #241

Open
raffaelespazzoli opened this issue Jan 31, 2018 · 3 comments
Open

Feedback on the "OpenShift and The Organization" guide #241

raffaelespazzoli opened this issue Jan 31, 2018 · 3 comments

Comments

@raffaelespazzoli
Copy link
Contributor

Sorry I'm late to this, but here is my feedback:

  • replace PaaS with Container Platform
  • provide navigation link from the fundamentals page
  • Assignment of Actions to Existing Roles: I'm not sure I find this title pertinent with the content of the paragraph. I like the content though, maybe a better title would be 'In the beginning`
  • Assignment of Actions to Existing Roles: one other immediate benefit of a container platform beside self servicing is confidence in the releases. I find that many early adopter gets to there pretty quickly, so maybe it's worth while mentioning.
  • Responsibilities for IT Organizations Using OpenShift capacity management maybe missing as an activity here, unless it is manage platform scale. Also security maybe missing here, putting platform authn and authz under Installation and Management of the OpenShift Platform maybe reductive for large organization and security is much more anyway.
  • Roles for IT Organizations Using OpenShift I can't map the concept of application production support (or tenants ops as some customers call it) to the roles listed here, maybe it's missing, or maybe the roles need more explanation. Can we add a general description of what each role is supposed to do and the we follow with the details in the RACI table?
@etsauer etsauer assigned etsauer and unassigned etsauer Feb 13, 2018
@etsauer
Copy link
Contributor

etsauer commented Feb 14, 2018

Bullet by bullet response:

  • Agreed, let's change it
  • not a problem
  • I agree the title doesn't make sense, but i think In the beginning is a bit too nebulous. Perhaps something like Early Stages of Container Adoption
  • Do you have a suggestion for the language there?
  • Would manage platform capacity make more sense? As far as security goes, that is a very cross-cutting concern, so I don't know that it goes under any one responsibility, unless we come up with some security-specific activity for each responsibility
  • Yeah, we definitely need much more verbose descriptions of the roles.

@etsauer
Copy link
Contributor

etsauer commented Feb 21, 2018

@raffaelespazzoli bump.

@raffaelespazzoli
Copy link
Contributor Author

raffaelespazzoli commented Feb 21, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants