| Re: [che-dev] CHE Single user - do we need it? |
I am assuming so - today we only support Docker for single-user mode so if we remove single-user mode we remove Docker support. Or am I misunderstanding?On Mon, Aug 27, 2018 at 1:53 PM Yevhen Ivantsov <yivantso@xxxxxxxxxx> wrote:_______________________________________________Are we talking about retiring Docker support?On Mon, Aug 27, 2018, 20:46 Brad Micklea <bmicklea@xxxxxxxxxx> wrote:I'd want to see resource utilization and startup times for Che server+dashboard and a typical workspace on Docker vs. Docker k8s before we think about switching. I agree that it's mostly a docker vs. kube argument but it's relevant here.On Mon, Aug 27, 2018 at 12:08 PM Yevhen Ivantsov <yivantso@xxxxxxxxxx> wrote:Mario,On Docker, it is possible to mount local binaries into che-server image. So, yes, you are right._______________________________________________On Mon, Aug 27, 2018 at 7:00 PM, Mario <mario.loriedo@xxxxxxxxx> wrote:Thank you Roman for starting the thread and Angel and Brad for providing your feedback.Che single user is that it's the only version of Che offered as a minishift addonTrue, but that can be easily fixed (rhche minishift addon already support multiuser)I just don't have enough RAM to do itThat was my major concern until I tried it: postgre container uses ~3MB only and keycloak ~500MB. That's a total of ~500 MB and it's relatively small if we think about the RAM needed to properly run a Che java workspace (>4GB).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 decisionThat's seems to me a docker vs openshift argument rather than single vs multi-user. We cannot refresh without rebuilding/pushing Che image on OpenShift/K8s but we can avoid that with Docker. Am I right?for someone who is just wanting to quickly look at Che on their laptop with Docker for Mac / Docker for Windows it's super helpfulLooks like a docker vs openshift argument too. And now that kubernetes bundled with Docker for Mac / Docker we should be able to easily run k8s based Che on those platforms (but that should be verified and documented).On Mon, Aug 27, 2018 at 5:27 PM Brad Micklea <bmicklea@xxxxxxxxxx> wrote:I agree with Angel. It's not something that's useful for our team, but for someone who is just wanting to quickly look at Che on their laptop with Docker for Mac / Docker for Windows it's super helpful because it downloads faster, needs fewer resources and has fewer potential problems. We need to keep it for that reason.On Mon, Aug 27, 2018 at 10:20 AM Angel Misevski <amisevsk@xxxxxxxxxx> wrote: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
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________Brad Micklea // BU Lead // Developer Tools & Program // 416.707.0792
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
--
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________Brad Micklea // BU Lead // Developer Tools & Program // 416.707.0792
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________Brad Micklea // BU Lead // Developer Tools & Program // 416.707.0792
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev