October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23375) Application wizard: Duplicated templates shown on a project with same name as cluster namespace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23375?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23375: ------------------------------------------ [~mlabuda] is this hurting in any way or is this simply visually disturbing? Do you face any error upon using one of these? > Application wizard: Duplicated templates shown on a project with same name as cluster namespace > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23375 > URL: https://issues.jboss.org/browse/JBIDE-23375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Attachments: duplicate_templates.png > > > When I change a cluster namespace and I am using this namespace with a user who has a project with same name, templates shown in New OpenShift Application wizard are duplicated. > !duplicate_templates.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23373) Application Wizard: Connection info could be visible on first wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23373?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23373: ------------------------------------- Fix Version/s: 4.4.x > Application Wizard: Connection info could be visible on first wizard page > ------------------------------------------------------------------------- > > Key: JBIDE-23373 > URL: https://issues.jboss.org/browse/JBIDE-23373 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > In New OpenShift Application wizard on the first wizard page there is a project combo to choose a project for a new application. We are missing a connection info on this page so user don't see for which connection is an application created. It seems to be obvious, that it is for selected project from OpenShift Explorer (if view is visible = modal dialog is not on top of it at that moment) but in case of several connections with same project, it could cause troubles. > We could have it similar as it is in Deploy Docker Image wizard, where we display connection info. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23376) Deploy Docker Wizard: Wizard is streched to display height

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23376: ------------------------------------- Priority: Minor (was: Major) > Deploy Docker Wizard: Wizard is streched to display height > ---------------------------------------------------------- > > Key: JBIDE-23376 > URL: https://issues.jboss.org/browse/JBIDE-23376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > > When opening a Deploy Image to OpenShift from context menu of a docker image in Docker Explorer and I don't have selected any OpenShift connection, first wizard page contains selection of an OpenShift connection. Upon clicking on Next button, the next wizard page Deploy an Image is stretched to whole height of a display. I think it could be caused by changes in JBIDE-22912. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23376) Deploy Docker Wizard: Wizard is streched to display height

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23376: ------------------------------------- Fix Version/s: 4.4.x > Deploy Docker Wizard: Wizard is streched to display height > ---------------------------------------------------------- > > Key: JBIDE-23376 > URL: https://issues.jboss.org/browse/JBIDE-23376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > > When opening a Deploy Image to OpenShift from context menu of a docker image in Docker Explorer and I don't have selected any OpenShift connection, first wizard page contains selection of an OpenShift connection. Upon clicking on Next button, the next wizard page Deploy an Image is stretched to whole height of a display. I think it could be caused by changes in JBIDE-22912. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23361) Filter text field in Server Editor's Deployment tab is too tall

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23361?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23361. --------------------------------- Fix Version/s: 4.4.2.AM3 Resolution: Done pushed in commit b0d07b737c0eaed709639d063eeddfa3b182b0b6 > Filter text field in Server Editor's Deployment tab is too tall > --------------------------------------------------------------- > > Key: JBIDE-23361 > URL: https://issues.jboss.org/browse/JBIDE-23361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM3 > > Attachments: deployment-filter.png > > > After JBIDE-23134 changed the overall layout of the Deployment tab in Server Editor and the modules table, the filter text field is now too tall, as if it was 2 lines high. > Otherwise it seems to work perfectly fine. > !deployment-filter.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23352: ------------------------------------------ @Jeff Maury I also believe that we should either remove Add/remove/Edit ports (neither oc nor web-ui offers these) or mark the custom (edited, added) ports as not being exposed in the docker image/container - and the user should be sure that there are actual processes on the docker container that listen to these. > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > !no_route_selected.png! > It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23352: ------------------------------------- Comment: was deleted (was: @Jeff Maury I also believe that we should either remove Add/remove/Edit ports (neither oc nor web-ui offers these) or mark the custom (edited, added) ports as not being exposed in the docker image/container - and the user should be sure that there are actual processes on the docker container that listen to these. ) > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > !no_route_selected.png! > It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23352 at 10/17/16 4:56 PM: -------------------------------------------------------------------- [~jeffmaury] I believe that we should add an explanatory label or info that tells the user, that when no port is selected for the route, the route will round-robin to all available ones. I also believe that we should either remove Add/remove/Edit ports (neither oc nor web-ui offers these) or mark the custom (edited, added) ports as not being exposed in the docker image/container - and the user should be sure that there are actual processes on the docker container that listen to these. was (Author: adietish): [~jeffmaury] I believe that we should add an explanatory label or info that tells the user, that when no port is selected for the route, the route will round-robin to all available ones. > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > steps to reproduce: > # EXEC: In Docker Explroer: pick an image and choose "Deploy to OpenShift..." in the context menu > # EXEC: get to the "Services & Routing Settings" page > !no_route_selected.png! > It's not obvious to the user what the wizard will create: A service that "exposes" pod ports and a route that points to this service. Furthermore it's not obvious that without a "checked" (used by route) port, the route will round-robin through the available ports. Additionally we should show the user what ports are exposed by the pod, and which ones are ports that the user added while no explicit exposure is defined in the pod (so he's on his own, if there's nothing listening on them he'll have users face non-functional or no reposonses at all). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23368 at 10/17/16 4:53 PM: -------------------------------------------------------------------- [~mlabuda] talked about this to [~jcantrill] today and I believe that the port setting should not be set to the replication controller. [~jcantrill] can you please replicate your rationale? [~jeffmaury] Thoughts? was (Author: adietish): [~mlabuda] talked about this to [~jcantrill] today and I believe that the port setting should not be set to the replication controller. I believe that we should either remove Add/remove/Edit ports or mark them as not being exposed in the docker image/container [~jeffmaury] Thoughts? > Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23368 > URL: https://issues.jboss.org/browse/JBIDE-23368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available) > Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23381) foundation.checker is UI and should not be dep'd by foundation.core

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23381?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23381: ----------------------------------- Assignee: Rob Stryker Resolution: Done pushed > foundation.checker is UI and should not be dep'd by foundation.core > ------------------------------------------------------------------- > > Key: JBIDE-23381 > URL: https://issues.jboss.org/browse/JBIDE-23381 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: foundation > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > The checker plugin has UI deps and should not be positioned below foundation.core. This pollutes our entire dependency tree. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016