[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24498:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.x
>
> Attachments: image-2017-05-23-11-07-21-461.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-23431) Remote server over ssh does not work with cygwin
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23431?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23431:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Remote server over ssh does not work with cygwin
> ------------------------------------------------
>
> Key: JBIDE-23431
> URL: https://issues.jboss.org/browse/JBIDE-23431
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> Today [~rawagner] reported to me that he cannot run a remote server over ssh on Windows.
> So I tried it and I get the same error as him:
> {code}
> cd /
> cd /
> echo $PWD'>'
> echo $PWD'>'
> java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone&
> echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$!
> Last login: Thu Nov 3 10:47:34 2016 from 10.40.4.40
> 0;~
> jbossqa@DESKTOP-QOUU1SV ~
> $ cd /
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $ cd /
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $ echo $PWD'>'
> />
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $ echo $PWD'>'
> />
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $ java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.re solver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInter val=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs= org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/ c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration =file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging. properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jb oss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss -modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as .standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/c ygdrive/c/mmalina/wildfly-10.0.0.Final/standalone&
> [1] 7888
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $ echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$!
> JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:7888
> 0;/
> jbossqa@DESKTOP-QOUU1SV /
> $ Error: Unable to access jarfile /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar
> wait 7888; echo "JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x147816649407 6:" $?
> [1]+ Exit 1 java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone
> JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x1478166494076: 1
> {code}
> I'm not sure what's going on, /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar is accessible for me just fine over ssh. One may think that perhaps the java process has to use windows paths. But when I try to run ./standalone.sh in cygwin there, it works just fine. So I guess there is no reason why it shouldn't work over ssh then. We just need to figure out what's wrong.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24495) Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24495?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24495:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"
> ---------------------------------------------------------------------------
>
> Key: JBIDE-24495
> URL: https://issues.jboss.org/browse/JBIDE-24495
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.x
>
>
> [Helloworld MSA|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-msa/master/re...] - the reference examples for openshift - is using the command line client "oc" to create the applications in OpenShift.
> A typical approach is doing the following:
> {code}
> $ oc new-build --binary --name=hola -l app=hola
> $ mvn package; oc start-build hola --from-dir=. --follow
> $ oc new-app hola -l app=hola,hystrix.enabled=true
> $ oc expose service hola
> {code}
> For people to be able to run those with Eclipse tooling people should be able to run the equivalent in Eclipse.
> The alternative approach, that's currently available in Eclipse is imbo less evident: Users can currently build docker images locally and deploy them to OpenShift.
> The tricky part though - for now - is that the CDK is not providing access to the docker registry from the outside: the docker registry address is a private IP that's only reachable within OpenShift. Users can get around this limitation by building docker images using the docker daemon in OpenShift, which is publicly reachable. Once available in the OpenShift docker daemon it can be pushed to the OpenShift docker registry.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21652:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.Final)
> We should make OS 3 application status more visible for users
> -------------------------------------------------------------
>
> Key: JBIDE-21652
> URL: https://issues.jboss.org/browse/JBIDE-21652
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Alexey Kazakov
> Fix For: 4.5.x
>
>
> Currently it can be confusing for users when an application is not available because it's building.
> We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters).
> For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible.
> OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months