[JBoss JIRA] (JBIDE-25134) Implement multi cluster and multi accounts in OSIO login
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-25134:
----------------------------------
Summary: Implement multi cluster and multi accounts in OSIO login
Key: JBIDE-25134
URL: https://issues.jboss.org/browse/JBIDE-25134
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.5.1.AM3
Reporter: Jeff MAURY
Fix For: 4.5.x
The current OpenShift.io integration supports only production OpenShift.io cluster and a single account. The model is already there but there is no way to add new clusters or new accounts
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBDS-4572) Install Eclipse Che with DevSuite Installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4572?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4572:
--------------------------------
Labels: doc (was: )
> Install Eclipse Che with DevSuite Installer
> -------------------------------------------
>
> Key: JBDS-4572
> URL: https://issues.jboss.org/browse/JBDS-4572
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 11.1.0.AM2
> Environment: Windows/macOS/RHEL
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: doc
> Fix For: 11.1.0.GA
>
>
> DevSuite Installer should have Eclipse Che available for installation. It should run on CDK and therefore CDK would be requirement for Eclipse Che and would be selected for installation automatically if Che selected.
> Installer for Che would enable CDK to run Eclipse Che through enabling add-on(?) and would not actually start Che inside CDK during installation. Last step of installer would provide link to online documentation how to start Eclipse Che on CDK.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBDS-4572) Install Eclipse Che with DevSuite Installer
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4572:
-----------------------------------
Summary: Install Eclipse Che with DevSuite Installer
Key: JBDS-4572
URL: https://issues.jboss.org/browse/JBDS-4572
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 11.1.0.AM2
Environment: Windows/macOS/RHEL
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 11.1.0.GA
DevSuite Installer should have Eclipse Che available for installation. It should run on CDK and therefore CDK would be requirement for Eclipse Che and would be selected for installation automatically if Che selected.
Installer for Che would enable CDK to run Eclipse Che through enabling add-on(?) and would not actually start Che inside CDK during installation. Last step of installer would provide link to online documentation how to start Eclipse Che on CDK.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24868 at 10/2/17 6:24 PM:
-------------------------------------------------------------------
talking to pcameron in #openshift-dev we found out that the haproxy in the router-pod had processed the instruction. The timeout really is set to the timeout that's specified in the annotation.
{code}
[adietish@localhost jbosstools-openshift]$ oc project default
[adietish@localhost jbosstools-openshift]$ oc rsh router-1-z56wl
sh-4.2$ cat haproxy.config
{code}
{code}
....
# Plain http backend
backend be_http:node:nodejs-mongo-persistent
mode http
option redispatch
option forwardfor
balance leastconn
timeout server 2h
{code}
So there's no explanation so far to why the haproxy would answer with a gateway error.
He told me to talk to bbennett
was (Author: adietish):
talking to pcameron in #openshift-dev we found out that the haproxy in the router-pod had processed the instruction. The timeout really is set to the timeout that's specified in the annotation.
{code}
[adietish@localhost jbosstools-openshift]$ oc project default
[adietish@localhost jbosstools-openshift]$ oc rsh router-1-z56wl
sh-4.2$ cat haproxy.config
{code}
{code}
....
# Plain http backend
backend be_http:node:nodejs-mongo-persistent
mode http
option redispatch
option forwardfor
balance leastconn
timeout server 2h
{code}
So there's no explanation so far to why the haproxy would answer with a gateway error.
> Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24868
> URL: https://issues.jboss.org/browse/JBIDE-24868
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.0.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.1.AM3
>
> Attachments: application-is-not-available.png, breakpoint-suspend-thread.png, webui_edit-add-service.png
>
>
> it will avoid to have "debug connections always killed after 30s staying in a breakpoint"
> see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion
> k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months