May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22313) Deploy Docker Image wizard: need unit tests

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22313?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22313: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Deploy Docker Image wizard: need unit tests > ------------------------------------------- > > Key: JBIDE-22313 > URL: https://issues.jboss.org/browse/JBIDE-22313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.4.0.Alpha3 > > > There are currently only 2 unit tests for the Deploy Docker Image Wizard in DeployImageWizardModelTest. The wizard is not properly covered by tests yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-13) Allow for connection settings edition [EBZ#476387]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/ERT-13?page=com.atlassian.jira.plugin.sys... ] Fred Bricon updated ERT-13: --------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Allow for connection settings edition [EBZ#476387] > -------------------------------------------------- > > Key: ERT-13 > URL: https://issues.jboss.org/browse/ERT-13 > Project: Eclipse Release Train > Issue Type: Feature Request > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Attachments: 2016-04-19 09.48.bmml, 2016-04-19 09.48.png > > > The user should be able to view and edit the connection settings once the connection exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22193: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Can't deploy locally built docker images > ---------------------------------------- > > Key: JBIDE-22193 > URL: https://issues.jboss.org/browse/JBIDE-22193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha3 > > > I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift > Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything > Here's what the CLI generates from > {quote} > eval "$(vagrant service-manager env docker)" > $ oc login 10.1.2.2:8443 -u openshift-dev -p devel > Login successful. > $ oc new-project my-ghost > Now using project "my-ghost" on server "https://10.1.2.2:8443". > $ docker pull ghost > $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io > $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ oc new-app --image-stream=ghost --name=ghost > $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io > {quote} > Deployment Config > {noformat} > { > "kind" : "DeploymentConfig", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost", > "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29849", > "creationTimestamp" : "2016-04-16T11:45:02Z", > "labels" : {"app" : "ghost"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["ghost"], > "from" : { > "kind" : "ImageStreamTag", > "namespace" : "my-ghost", > "name" : "ghost:latest" > }, > "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > } > } > ], > "replicas" : 1, > "selector" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "template" : { > "metadata" : { > "labels" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "annotations" : { > "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]", > "openshift.io/generated-by" : "OpenShiftNewApp" > } > }, > "spec" : { > "volumes" : [{"name" : "ghost-volume-1"}], > "containers" : [{ > "name" : "ghost", > "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "ports" : [{ > "containerPort" : 2368, > "protocol" : "TCP" > }], > "volumeMounts" : [{ > "name" : "ghost-volume-1", > "mountPath" : "/var/lib/ghost" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "status" : { > "latestVersion" : 1, > "details" : {"causes" : [{"type" : "ConfigChange"}]} > } > } > {noformat} > Image Stream > {noformat} > { > "kind" : "ImageStream", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost", > "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29842", > "creationTimestamp" : "2016-04-16T11:44:37Z", > "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"} > }, > "status" : { > "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost", > "tags" : [{ > "tag" : "latest", > "items" : [{ > "created" : "2016-04-16T11:44:37Z", > "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > }] > }] > } > } > {noformat} > When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy. > {quote} > - Clone https://github.com/burrsutter/cdk_helloworlds/ > - import java/wildflyswarm_helloworld as a Maven Project > - Run a Maven build (Run As > Maven > package) > - Edit Dockerfile: replace `FROM rhel7` with `FROM centos` > - right click on Dockerfile > Run As > Docker Image build > - Select `CDK Server Adapter at localhost` connection > - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm > - from OpenShift explorer, create a fredo project > - In OpenShift explorer, right-click the fredo project and Deploy Docker Image... > - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image > - swarm as resource name > - click next > - Deployment configuration & scalability page displays, click next > - click add route button, click finish > - resources are created, but no deployment happens > {quote} > Here are the resources created from Eclipse: > Deployment Config > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm", > "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30206", > "creationTimestamp" : "2016-04-16T12:10:17Z", > "labels" : {"deploymentconfig" : "swarm"}, > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["swarm"], > "from" : { > "kind" : "ImageStreamTag", > "name" : "swarm:latest" > } > } > } > ], > "replicas" : 1, > "selector" : {"deploymentconfig" : "swarm"}, > "template" : { > "metadata" : {"labels" : {"deploymentconfig" : "swarm"}}, > "spec" : { > "containers" : [{ > "name" : "swarm", > "image" : "fredo/swarm:latest", > "ports" : [{ > "name" : "8080-tcp", > "containerPort" : 8080, > "protocol" : "TCP" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "apiVersion" : "v1", > "kind" : "DeploymentConfig" > } > {noformat} > Image Stream > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm", > "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30202", > "creationTimestamp" : "2016-04-16T12:10:16Z", > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"}, > "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"}, > "apiVersion" : "v1", > "kind" : "ImageStream" > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22319: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21857: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.4.x > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22320) Update Openshift EAP/Wildfly Images to Enable JMX

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22320?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22320: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Update Openshift EAP/Wildfly Images to Enable JMX > ------------------------------------------------- > > Key: JBIDE-22320 > URL: https://issues.jboss.org/browse/JBIDE-22320 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > The EAP image for Openshift does not allow a connection to the jmx remoting port. We need changes to the startup scripts to allow opening the jmx connection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22321) Use Same ServerHotCodeReplaceListener as for local wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22321?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22321: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Use Same ServerHotCodeReplaceListener as for local wildfly > ---------------------------------------------------------- > > Key: JBIDE-22321 > URL: https://issues.jboss.org/browse/JBIDE-22321 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > We need to port the fix we have for wildfly to the OpenShiftServer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22165: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22165 > URL: https://issues.jboss.org/browse/JBIDE-22165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Thomas Mäder > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself... > At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22326) Enable JMX Connections Over "remoting-jmx"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22326?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22326: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Enable JMX Connections Over "remoting-jmx" > ------------------------------------------ > > Key: JBIDE-22326 > URL: https://issues.jboss.org/browse/JBIDE-22326 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Need to add "remoting-jmx" library and support that kind of connection for jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21134) Move easymport plugins from playground component

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21134?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21134: ---------------------------------------- I hate code freeze! For such an example, it just seems like that the fact that we're not branching prevents us from producing and delivering features for a week. I much prefer the branch approach that allowed things to keep on moving, > Move easymport plugins from playground component > ------------------------------------------------ > > Key: JBIDE-21134 > URL: https://issues.jboss.org/browse/JBIDE-21134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.4.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > Easymport is in the default installation of JBDS so it might be time to move it from playground component? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 May 2016