Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] 6.12.0 release notes - request for help
Hello, Dave

Adding support of the ephemeral workspaces (using `emptyDir` volume
instead of PVC) via 'persistVolumes' attribute

On OpenShift/Kubernetes infrastructure it is possible to configure workspaces to be ephemeral (with no PVC attached) via persistVolumes attribute set to 'false' in the workspace config:

"attributes": {
  "persistVolumes": "false"
}

In this case, regardless of the PVC strategy, all volumes would be created as emptyDir for the given workspace. When a workspace Pod is removed for any reason, the data in the emptyDir volume is deleted forever.


On Fri, Oct 5, 2018 at 12:02 PM Oleksandr Garagatyi <ogaragat@xxxxxxxxxx> wrote:
Hello, Dave.
Change CHE-11408: Disable probes of Che master when debug is enabled is rather internal and interesting for development of Che itself. It simplifies debugging of Che master deployed to OCP.

Change 
Make Theia sidecar/stack secure, add an ability to use new JWT auth on a per-workspace basis
make Theia secure in multi-user Che for:
- Theia stack
- Workspace.Next
It also allows enabling new implementation of workspace security on a per-workspace basis to check how it fits a particular Che deployment needs.

Changes: 
Change default sidecar memory limit to 128MB
Change default sidecar memory limit to 512MB to let Theia work OOTB
Add a property for default sidecar mem limit
are just parts of the same story - make Workspace.Next sidecars consume less memory by default and allowing to override sidecar memory limit on a per-workspace basis for cases when sidecar needs a lot of memory for a heavy workspace. An example if the development of Che master with JDT.LS sidecar. Since Che is a pretty big project JDT.LS requires a lot of RAM not to get OOM killed. But for smaller projects 2GB of RAM is way too much, so default memory limit should be not very big and a user can adjust the value in his particular workspace. 

Change Add an ability to configure Pull policy for broker is also more interesting for the development purposes to customize version of Workspace.Next plugins broker image.

Hope this helped, 
Alex

On Fri, Oct 5, 2018 at 12:12 PM Dmytro Nochevnov <dnochevn@xxxxxxxxxx> wrote:
Hello, Dave!

Commit "Stores logs of test workspaces which do not have RUNNING status" doesn't have an impact on Eclipse Che itself. 
It is about improvement of E2E selenium tests, therefor it is not so important for end users to be included into the release notes.

On Fri, Oct 5, 2018 at 10:35 AM Anna Shumilova <ashumilo@xxxxxxxxxx> wrote:
Hello, Dave,

About "Add plugins widget on workspace creation":
This feature is part of workspace.next flow and brings the ability to manage the list of workspace plugins, when user creates new workspace. First, user chooses the stack and it may already contain the Che plugins inside, thus user can easily access that information and modify(enable or disable ones) before creating the workspace.
_______________________________________________
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


--
With best regards,
Dmytro Nochevnov
Codenvy Associate
_______________________________________________
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


--

OLEKSANDR GARAGATYI

SENIOR SOFTWARE ENGINEER

Red Hat 

_______________________________________________
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


--

ILYA BUZIUK

SENIOR SOFTWARE ENGINEER

Red Hat 

ibuziuk@xxxxxxxxxx   

Back to the top