Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

handle users pre-existing project in OSO gracefully #1031

Open
2 tasks
kbsingh opened this issue Sep 27, 2017 · 5 comments
Open
2 tasks

handle users pre-existing project in OSO gracefully #1031

kbsingh opened this issue Sep 27, 2017 · 5 comments

Comments

@kbsingh
Copy link
Collaborator

kbsingh commented Sep 27, 2017

In many cases, when a user logs into OSIO, they might already have some project / namespace or app deployed in their OSO space. Since we need to config this namespace as the users dev environment, we should handle the condition gracefully, doing either one of the following options:

  • When the user logs into OSIO, they are asked to link their OSO account - at this point, we should sanity check their OSO account to ensure its in a good state, if not, offer the user a choice to clean it up for them
  • Alternatively, we just use whatever project the tenant already has setup, as their dev environ and just modify that space with whatever acl's and privileges we need.

Sub-task(s):

@kbsingh kbsingh added this to the OpenShift.io Backlog milestone Sep 27, 2017
@kbsingh kbsingh changed the title handle users existing workload in OSO gracefully handle users pre-existing project in OSO gracefully Sep 27, 2017
@kbsingh
Copy link
Collaborator Author

kbsingh commented Sep 27, 2017

@joshuawilson assigning to you, to triage and route accordingly.

@joshuawilson
Copy link
Member

This will need input from @qodfathr @catrobson @alexeykazakov @aslakknutsen @maxandersen and you @kbsingh

@ldimaggi
Copy link
Collaborator

The first choice sounds like a smaller task - build a tool to examine a user's environment, and if the state does not match our predefined concept of a "good" state, clean it up.

The second choice sounds more involved as we would be performing discrete modifications to a user's environment.

@catrobson
Copy link
Collaborator

The challenge is that this project/dev environment needs to live in a space somewhere. I think the ideal situation here long term is that we would have a unique UI flow to handle this situation, as it may be a likely situation for many people on-boarding into OSIO. I can add this to the UX Backlog. If we want to do a fix until then, I agree that asking the users to clean if we see this is a fine hold-over until we can implement the proper pathway.

@catrobson
Copy link
Collaborator

Added UX issue here: fabric8-ui/fabric8-ux#687

@joshuawilson joshuawilson removed their assignment Nov 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.