Current Hosted Che "Terms of service" allows using only 3GB of RAM for workspace. At the same time some of the devfiles from the registry like java-web-spring are failing with the quota issue:


NOTE: event though globalMemoryLimit: 2674Mi is set in the meta.yaml, I suspect it does not take into account the jwt-proxy pod
We need to:
[1] https://www.eclipse.org/che/docs/che-7/hosted-che.html#terms-of-service_{context}
@Katka92 @ScrewTSW could you please provide a list of Hosted Che quota incompatible devfiles from - https://github.com/eclipse/che-devfile-registry/tree/master/devfiles ?
This could be simply tested on prod-preview ?url=https://raw.githubusercontent.com/eclipse/che-devfile-registry/master/devfiles/java-web-spring/devfile.yaml (import via factory) e.g. https://che.prod-preview.openshift.io/f?url=https://raw.githubusercontent.com/eclipse/che-devfile-registry/master/devfiles/java-web-spring/devfile.yaml
Devfiles failing because of quota issues:
All the other devfiles started correctly for me when I was doing the testing (19.7.2019)
@sleshchenko any comments on this issue. Do you happen to know if we could shrink RAM for those devfiles or current memory settings reflect the absolute minimum ?
in previous version of Che 7, the Apache Camel stack was working. it was using smaller memory values, see https://github.com/eclipse/che/issues/13832#issuecomment-514148086
[23.07.2019]
Check for worksapce startup quotes with the latest version of devfile registry at prod-preview:
I don't know if this is the place but we should concider having 5GB quota limitations (and having less users capacity)
@sunix you could add this proposal to the upcoming briefs for Q3, but 5GB quota & less users capacity definitely not smth we are going to address by GA
@ibuziuk that doesn't look like a blocker right? Setting it as P1. I mean if we cannot reduce the amount of memory we can remove the devfiles from the openshift.io registry.
yeah, not a blocker indeed
I mean if we cannot reduce the amount of memory we can remove the devfiles from the openshift.io registry.
for Apache Camel stack, we can reduce the memory, see https://github.com/eclipse/che-devfile-registry/pull/46 and https://github.com/eclipse/che/issues/13832
so nto having Apache Camel stack on che.openshift.io is not blocker?
an alternate solution if there is a different registry to use is to set back the working memory values only in the rh-che repository?
@apupier if it works we would merge it and make available ;-)
@apupier if it works we would merge it and make available ;-)
my last manual tests on preprod are working https://github.com/eclipse/che-devfile-registry/pull/46#issuecomment-514515189
created a separate issue for UD improvement that should be tackled after GA - https://github.com/eclipse/che/issues/14001
All PRs have been merged. Closing
Most helpful comment
[23.07.2019]
Check for worksapce startup quotes with the latest version of devfile registry at prod-preview:
and [Follow-up](https://github.com/eclipse/che-devfile-registry/pull/60)]