Re: [che-dev] CHE Single user - do we need it?

[Angel Misevski <amisevsk@xxxxxxxxxx>]

Hi Roman,

On 08/27/2018 09:44 AM, Roman Iuvshyn wrote:
> Hello everyone, I wanted to rise this $subject question.
> today QE team spend a lot of extra time to analyze CHE Single user 
> daily testing reports on different infras / flavors and also we waster 
> a lot compute resources on CI to run these tests...
> Do we really still need to support CHE Single user package? Who is 
> using that? May we drop it and have only one package of CHE Multiuser.
> In the past, we've been using single user CHE on docker because it was 
> easier for devs to do development things not related to multiuser 
> features, but now we are using multiuser for development and testing 
> because we use multiuser in PROD.
> I see only benefits of removing CHE Singe user package but I wonder 
> what others think about it.
One issue with removing Che single user is that it's the only version of 
Che offered
as a minishift addon [1]. This is probably the easiest way for an 
OpenShift-oriented user
to try Che on OpenShift.

Also I have some issues with the multi-user Che's memory requirements. 
Running multi-
user locally would mean a laptop upgrade in my case; I just don't have 
enough RAM to
do it. It's useful to be able to iterate quickly on single-user (e.g. 
not pushing images,
quicker debugging) for issues that are unrelated to the 
single/multi-user decision.

Cheers,

Angel

[1] - https://github.com/minishift/minishift/tree/master/addons/che