[JBoss JIRA] (JBIDE-21868) Performance issue on Deploy Docker Image wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21868?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21868.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B233.
> Performance issue on Deploy Docker Image wizard
> -----------------------------------------------
>
> Key: JBIDE-21868
> URL: https://issues.jboss.org/browse/JBIDE-21868
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> When the user inputs an image name in the "Deploy Docker Image" wizard, there is a performance issue due to the fact that some data are initialized as the user inputs the image name.
> This is even more significant if the user wants to use an image that was not pulled, i.e., a remote call will be performed for each new character typed in the {{Image Name}} field.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21891) Performance issue on Deploy Docker Image wizard
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21891:
-------------------------------------
Summary: Performance issue on Deploy Docker Image wizard
Key: JBIDE-21891
URL: https://issues.jboss.org/browse/JBIDE-21891
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.1.CR1, 4.4.0.Alpha1
When the user inputs an image name in the "Deploy Docker Image" wizard, there is a performance issue due to the fact that some data are initialized as the user inputs the image name.
This is even more significant if the user wants to use an image that was not pulled, i.e., a remote call will be performed for each new character typed in the {{Image Name}} field.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21734) Deploying of a docker image from docker explorer has ambiguous connection
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21734.
-------------------------------
Verified in 4.3.1.CR1 with OS tooling 3.1.0.CR1-v20160317-B233.
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21734
> URL: https://issues.jboss.org/browse/JBIDE-21734
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: ambiguous_connection.png, DeployImage_ConnectionRenderingEnhanced.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21890) Deploying of a docker image from docker explorer has ambiguous connection
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21890?page=com.atlassian.jira.plugi... ]
Jan Richter resolved JBIDE-21890.
---------------------------------
Resolution: Done
Clone of JBIDE-21734 for master branch.
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21890
> URL: https://issues.jboss.org/browse/JBIDE-21890
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: ambiguous_connection.png, DeployImage_ConnectionRenderingEnhanced.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21890) Deploying of a docker image from docker explorer has ambiguous connection
by Jan Richter (JIRA)
Jan Richter created JBIDE-21890:
-----------------------------------
Summary: Deploying of a docker image from docker explorer has ambiguous connection
Key: JBIDE-21890
URL: https://issues.jboss.org/browse/JBIDE-21890
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.CR1
When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
!ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21890) Deploying of a docker image from docker explorer has ambiguous connection
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21890?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-21890:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Deploying of a docker image from docker explorer has ambiguous connection
> -------------------------------------------------------------------------
>
> Key: JBIDE-21890
> URL: https://issues.jboss.org/browse/JBIDE-21890
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: ambiguous_connection.png, DeployImage_ConnectionRenderingEnhanced.png
>
>
> When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot
> !ambiguous_connection.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21886) Have a label for when there is no project in your openshift connection
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21886?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21886:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Have a label for when there is no project in your openshift connection
> ----------------------------------------------------------------------
>
> Key: JBIDE-21886
> URL: https://issues.jboss.org/browse/JBIDE-21886
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Fix For: 4.4.0.Alpha1
>
>
> Marian and I were discussing the issue that it's not clear whether or not a connection to OpenShift 3 is established or not - in the OpenShift Explorer view.
> So here's a suggestion:
> When you expand your OpenShift connection and there is no project yet, we could display an item like this:
> No projects are available. Click this link to create a new project...
> This would be similar to what Server view display if there are no servers yet.
> This is related to JBIDE-21871 where we discussed how to make it clearer that an OpenShift connection is active and working.
> For CDK, we will hopefully have a default project via https://github.com/projectatomic/adb-utils/pull/78 so this won't be an issue, but you cannot guarantee that there will always be a project on all OpenShift 3 instances, so it would still be a good idea to have what we suggest above.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21869 at 3/17/16 8:57 AM:
--------------------------------------------------------------
The web console displays the characters properly:
{noformat}
express(a)4.13.4 node_modules/express
├── escape-html(a)1.0.3
├── array-flatten(a)1.1.1
├── utils-merge(a)1.0.0
├── cookie-signature(a)1.0.6
├── merge-descriptors(a)1.0.1
├── fresh(a)0.3.0
├── range-parser(a)1.0.3
├── methods(a)1.1.2
├── vary(a)1.0.1
├── path-to-regexp(a)0.1.7
├── parseurl(a)1.3.1
├── cookie(a)0.1.5
├── content-type(a)1.0.1
├── etag(a)1.7.0
├── content-disposition(a)0.5.1
├── serve-static(a)1.10.2
├── depd(a)1.1.0
├── qs(a)4.0.0
├── finalhandler(a)0.4.1 (unpipe(a)1.0.0)
├── on-finished(a)2.3.0 (ee-first(a)1.1.1)
├── debug(a)2.2.0 (ms(a)0.7.1)
├── proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
├── send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
├── type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
└── accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
mongodb(a)2.1.7 node_modules/mongodb
├── es6-promise(a)3.0.2
├── readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
└── mongodb-core(a)1.3.1 (bson(a)0.4.22, require_optional(a)1.0.0)
{noformat}
was (Author: fbricon):
The web console displays the characters properly:
{noformat}
express(a)4.13.4 node_modules/express
776 ├── escape-html(a)1.0.3
777 ├── array-flatten(a)1.1.1
778 ├── utils-merge(a)1.0.0
779 ├── cookie-signature(a)1.0.6
780 ├── merge-descriptors(a)1.0.1
781 ├── fresh(a)0.3.0
782 ├── range-parser(a)1.0.3
783 ├── methods(a)1.1.2
784 ├── vary(a)1.0.1
785 ├── path-to-regexp(a)0.1.7
786 ├── parseurl(a)1.3.1
787 ├── cookie(a)0.1.5
788 ├── content-type(a)1.0.1
789 ├── etag(a)1.7.0
790 ├── content-disposition(a)0.5.1
791 ├── serve-static(a)1.10.2
792 ├── depd(a)1.1.0
793 ├── qs(a)4.0.0
794 ├── finalhandler(a)0.4.1 (unpipe(a)1.0.0)
795 ├── on-finished(a)2.3.0 (ee-first(a)1.1.1)
796 ├── debug(a)2.2.0 (ms(a)0.7.1)
797 ├── proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
798 ├── send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
799 ├── type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
800 └── accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
801
802 mongodb(a)2.1.7 node_modules/mongodb
803 ├── es6-promise(a)3.0.2
804 ├── readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
805 └── mongodb-core(a)1.3.1 (bson(a)0.4.22, require_optional(a)1.0.0)
{noformat}
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21869:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years