May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24004) Explore possibilities of automated bare metal windows provisioning

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24004?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-24004: --------------------------------------- Cc: [~mmalina] Any ideas here what else could be done here in this jira? > Explore possibilities of automated bare metal windows provisioning > ------------------------------------------------------------------ > > Key: JBIDE-24004 > URL: https://issues.jboss.org/browse/JBIDE-24004 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk, central-ci, devsuite > Fix For: 4.4.x > > > Figure out how to provision bare metal windows machine with any tool in an automated manner. We want to have reliable windows machine that are capable of virtualization and thus, we can move on with our effort in CI process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24495) Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24495: ---------------------------------------- Summary: 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 [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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1112?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1112. ------------------------------------ Verified with Devstudio IS 10.3.0.GA which contains {code} org.jboss.tools.bpel.feature_1.3.300.Final-v20170522-1257-B14 {code} > BPEL version was downgraded from 1.3.200 to 1.3.3 > ------------------------------------------------- > > Key: JBTIS-1112 > URL: https://issues.jboss.org/browse/JBTIS-1112 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: BPEL, distribution > Affects Versions: 10.3.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.3.0.GA, 4.4.3.Final > > > BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature > | Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 | > | Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 | > I didn't find any difference except the version definition. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Description: I deployed the Camel Fuse Teampltes available in Fuse Tooling I restarted my Eclipse I reconnected to the same CDK - select application in OpenShift Instance view - go to Build Configs tab in properties view - select the element available Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) alternatively: * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... * create an app using the s2i-spring-boot-camel-xml template * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Issue Type: Feature Request (was: Bug) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Issue Type: Bug (was: Feature Request) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > > I deployed the Camel Fuse Teampltes available in Fuse Tooling > I restarted my Eclipse > I reconnected to the same CDK > - select application in OpenShift Instance view > - go to Build Configs tab in properties view > - select the element available > Source properties are not shown (JBIDE-23815 fixed the NPE that was occurring before) > alternatively: > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/fis... > * oc create -f https://raw.githubusercontent.com/jboss-fuse/application-templates/GA/qui... > * create an app using the s2i-spring-boot-camel-xml template > * manually change the build config that results from it as shown here: https://issues.jboss.org/browse/JBIDE-23815?focusedCommentId=13364807&pag... > * open up "Properties" and select the "Build Config" tab, selecting the fuse entry. Look into the details if you can find a "Source" cathegory with children. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24491: ------------------------------------- Issue Type: Feature Request (was: Bug) > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24482) CDK server adapter: creates a connection with erroneous "Image Registry URL"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24482?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24482: ------------------------------------- Steps to Reproduce: # ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling fall back to an erroneous default) # ASSERT: have a CDK3/minishift server adapter # ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer # EXEC: launch CDK3/minishift server adapter # ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created # EXEC: in OpenShift explorer: pick "Edit Connection..." # ASSERT: connection wizard pops up # EXEC: hit "Advanced >>" and inspect "Image Registry URL" Result: !image-2017-05-17-22-07-43-235.png! The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/ Expected result: the correct value for the docker registry can be fetched from minishift by doing (in cmd-line): {code} ./minishift openshift registry {code} In the current state of CDK3/minishift, where the docker registry is not publicly reachable, the correct value that is reported is an internal IP: {code} 172.30.1.1:5000 {code} was: # ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling most likely fall back to an erroneous default) # ASSERT: have a CDK3/minishift server adapter # ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer # EXEC: launch CDK3/minishift server adapter # ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created # EXEC: in OpenShift explorer: pick "Edit Connection..." # ASSERT: connection wizard pops up # EXEC: hit "Advanced >>" and inspect "Image Registry URL" Result: !image-2017-05-17-22-07-43-235.png! The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/ Expected result: the correct value for the docker registry can be fetched from minishift by doing (in cmd-line): {code} ./minishift openshift registry {code} In the current state of CDK3/minishift, where the docker registry is not publicly reachable, the correct value that is reported is an internal IP: {code} 172.30.1.1:5000 {code} > CDK server adapter: creates a connection with erroneous "Image Registry URL" > ---------------------------------------------------------------------------- > > Key: JBIDE-24482 > URL: https://issues.jboss.org/browse/JBIDE-24482 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: image-2017-05-17-22-07-43-235.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24482) CDK server adapter: creates a connection with erroneous "Image Registry URL"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24482?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24482: ------------------------------------- Steps to Reproduce: # ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling most likely fall back to an erroneous default) # ASSERT: have a CDK3/minishift server adapter # ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer # EXEC: launch CDK3/minishift server adapter # ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created # EXEC: in OpenShift explorer: pick "Edit Connection..." # ASSERT: connection wizard pops up # EXEC: hit "Advanced >>" and inspect "Image Registry URL" Result: !image-2017-05-17-22-07-43-235.png! The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/ Expected result: the correct value for the docker registry can be fetched from minishift by doing (in cmd-line): {code} ./minishift openshift registry {code} In the current state of CDK3/minishift, where the docker registry is not publicly reachable, the correct value that is reported is an internal IP: {code} 172.30.1.1:5000 {code} was: # ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling most likely fall back to an erroneous default) # ASSERT: have a CDK3/minishift server adapter # ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer # EXEC: launch CDK3/minishift server adapter # ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created # EXEC: in OpenShift explorer: pick "Edit Connection..." # ASSERT: connection wizard pops up # EXEC: hit "Advanced >>" and inspect "Image Registry URL" Result: !image-2017-05-17-22-07-43-235.png! The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/ Expected result: the correct value for the docker registry can be fetched from minishift by doing (in cmd-line): {code} ./minishift openshift registry {code} In the current state of CDK3/minishift, where the docker registry is not publicly reachable the value that is reported is an internal IP: {code} 172.30.1.1:5000 {code} > CDK server adapter: creates a connection with erroneous "Image Registry URL" > ---------------------------------------------------------------------------- > > Key: JBIDE-24482 > URL: https://issues.jboss.org/browse/JBIDE-24482 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: image-2017-05-17-22-07-43-235.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24482) CDK server adapter: creates a connection with erroneous "Image Registry URL"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24482?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24482: ------------------------------------- Steps to Reproduce: # ASSERT: have a CDK3/minishift binary that's renamed (this makes sure that it wont inform about the docker registry making the tooling most likely fall back to an erroneous default) # ASSERT: have a CDK3/minishift server adapter # ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer # EXEC: launch CDK3/minishift server adapter # ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created # EXEC: in OpenShift explorer: pick "Edit Connection..." # ASSERT: connection wizard pops up # EXEC: hit "Advanced >>" and inspect "Image Registry URL" Result: !image-2017-05-17-22-07-43-235.png! The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/ Expected result: the correct value for the docker registry can be fetched from minishift by doing (in cmd-line): {code} ./minishift openshift registry {code} In the current state of CDK3/minishift, where the docker registry is not publicly reachable the value that is reported is an internal IP: {code} 172.30.1.1:5000 {code} was: # ASSERT: have a CDK3/minishift server adapter # ASSERT: make sure that you *DONT* have a connection to CDK3/minishift in the OpenShift Explorer # EXEC: launch CDK3/minishift server adapter # ASSERT: in OpenShift explorer: a new connection to the CDK3/minishift is created # EXEC: in OpenShift explorer: pick "Edit Connection..." # ASSERT: connection wizard pops up # EXEC: hit "Advanced >>" and inspect "Image Registry URL" Result: !image-2017-05-17-22-07-43-235.png! The image registry URL that is unveiled is clearly wrong. It is https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/ Expected result: the correct value for the docker registry can be fetched from minishift by doing (in cmd-line): {code} ./minishift openshift registry {code} In the current state of CDK3/minishift, where the docker registry is not publicly reachable the value that is reported is an internal IP: {code} 172.30.1.1:5000 {code} > CDK server adapter: creates a connection with erroneous "Image Registry URL" > ---------------------------------------------------------------------------- > > Key: JBIDE-24482 > URL: https://issues.jboss.org/browse/JBIDE-24482 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: image-2017-05-17-22-07-43-235.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017