[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-23872 at 2/20/17 6:34 AM:
----------------------------------------------------------------
I tried this on Mac and I can reproduce the issue.
In my case I tried to strictly follow the steps. So I did not stop the server before quitting Eclipse (but the java process gets terminated).
After launching devstudio again, the server said "Republish". I then did a Publish on the server and then started the server again. At this point I no longer could access the main web page (using module -> Show In Web Browser) - it said "Forbidden".
Here's the diff of the file structures:
{code}
$ diff ~/tmp/good.txt ~/tmp/bad.txt
22,34d21
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data/MemberListProducer.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data/MemberRepository.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/model
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/model/Member.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/service
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/service/MemberRegistration.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/util
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/util/Resources.class
43,70d29
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/beans.xml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/controller
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/controller/MemberController.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest/JaxRsActivator.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest/MemberResourceRESTService.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/util
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/util/WebResources.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/faces-config.xml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/templates
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/templates/default.xhtml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/index.html
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/index.xhtml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/css
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/css/screen.css
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/asidebkg.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/banner.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/bkg-blkheader.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/headerbkg.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/rhjb_eap_logo.png
{code}
That's 40 changes out of original 70 files (including directories).
[~rob.stryker], since I seem to be able to replicate this and you're not, please ping me and I can try to get more debug information for you (unless what Claudio offers is sufficient).
was (Author: mmalina):
I tried this on Mac and I can reproduce the issue.
In my case I tried to strictly follow the steps. So I did not stop the server before quitting Eclipse (but the java process gets terminated).
After launching devstudio again, the server said "Republish". I then did a Publish on the server and then started the server again. At this point I no longer could access the main web page (using module -> Show In Web Browser) - it said "Forbidden".
Here's the diff of the file structures:
{code}
$ diff ~/tmp/good.txt ~/tmp/bad.txt
22,34d21
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data/MemberListProducer.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data/MemberRepository.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/model
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/model/Member.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/service
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/service/MemberRegistration.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/util
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/util/Resources.class
43,70d29
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/beans.xml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/controller
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/controller/MemberController.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest/JaxRsActivator.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest/MemberResourceRESTService.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/util
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/util/WebResources.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/faces-config.xml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/templates
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/templates/default.xhtml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/index.html
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/index.xhtml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/css
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/css/screen.css
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/asidebkg.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/banner.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/bkg-blkheader.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/headerbkg.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/rhjb_eap_logo.png
{code}
That's 40 changes out of original 70 files (including directories).
> Tools clear war deployed files
> ------------------------------
>
> Key: JBIDE-23872
> URL: https://issues.jboss.org/browse/JBIDE-23872
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: Windows 7 64
> JDK 8
> Eclipse Neon 1
> JBoss Tools 4.4
> WildFly 10.1
> Reporter: Claudio Weiler
> Assignee: Rob Stryker
> Fix For: 4.4.3.Final
>
> Attachments: publish.log
>
>
> After an Eclipse start war deployed files are deleted and not republished.
> I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource:
> "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23872:
---------------------------------------
I tried this on Mac and I can reproduce the issue.
In my case I tried to strictly follow the steps. So I did not stop the server before quitting Eclipse (but the java process gets terminated).
After launching devstudio again, the server said "Republish". I then did a Publish on the server and then started the server again. At this point I no longer could access the main web page (using module -> Show In Web Browser) - it said "Forbidden".
Here's the diff of the file structures:
{code}
$ diff ~/tmp/good.txt ~/tmp/bad.txt
22,34d21
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data/MemberListProducer.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/data/MemberRepository.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/model
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/model/Member.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/service
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/service/MemberRegistration.class
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/util
< jboss-javaee-multi.ear/jboss-javaee-multi-ejb.jar/org/jboss/tools/example/util/Resources.class
43,70d29
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/beans.xml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/controller
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/controller/MemberController.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest/JaxRsActivator.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/rest/MemberResourceRESTService.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/util
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/classes/org/jboss/tools/example/util/WebResources.class
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/faces-config.xml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/templates
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/WEB-INF/templates/default.xhtml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/index.html
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/index.xhtml
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/css
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/css/screen.css
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/asidebkg.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/banner.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/bkg-blkheader.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/headerbkg.png
< jboss-javaee-multi.ear/jboss-javaee-multi-web.war/resources/gfx/rhjb_eap_logo.png
{code}
That's 40 changes out of original 70 files (including directories).
> Tools clear war deployed files
> ------------------------------
>
> Key: JBIDE-23872
> URL: https://issues.jboss.org/browse/JBIDE-23872
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: Windows 7 64
> JDK 8
> Eclipse Neon 1
> JBoss Tools 4.4
> WildFly 10.1
> Reporter: Claudio Weiler
> Assignee: Rob Stryker
> Fix For: 4.4.3.Final
>
> Attachments: publish.log
>
>
> After an Eclipse start war deployed files are deleted and not republished.
> I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource:
> "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23490:
---------------------------------------
Ok once again ;) This issue was created by [~aurelien.pupier] as an initial request to provide an option to link server adapter to running pods. I think (please correct me if I am wrong [~aurelien.pupier]) than the reason why this issue was created was initially misunderstanding of how OpenShift works and how to utilize it. Service should (probably, haven't seen a case so far where ) always exists for an application. Thus I am still having difficulties to see the reason/use case of having a server adapter linked to a deployment config/replication controller.
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23825) Improve eap compatibility test execution
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23825?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23825:
----------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> Improve eap compatibility test execution
> ----------------------------------------
>
> Key: JBIDE-23825
> URL: https://issues.jboss.org/browse/JBIDE-23825
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, server
> Affects Versions: 4.4.3.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.4.AM1
>
>
> This is a followup of JBIDE-23756 - with that, we are once again able to execute compatibility tests for eap. But there are a few things missing:
> For now I will make it work with what we have, but there are several things that need to be fixed:
> 1. Even if you only run the eap7x-compatibility profile, all of the runtimes (jboss as 4, as 5, as 7, wildfly...) will be downloaded anyway, because this is set up in as/itests/pom.xml - we need to come up with a way to only do this if the compatibility profile is not active. Maybe we need to switch to profile activation by property, e.g. eap7x-compatibility - the profile in as/itests/org.jboss.tools.as.ui.bot.itests/pom.xml would be activated by this, whereas all the other runtime downloads in as/itests/pom.xml would be in a profile that is deactivated using this property.
> 2. https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/org...
> The eap7x-compatibility profile has jboss-eap-7.0 server directory hardcoded. You can still override the whole property with something else for eap 7.1, but it would be nice to improve this.
> For reference, this is a job where Radim demonstrated the new way to execute tests:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job...
> And these are the two jobs EAP QE uses for the compatibilty testing:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-70x-jbds-c...
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23825) Improve eap compatibility test execution
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23825?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23825:
----------------------------------
Sprint: devex #128 February 2017 (was: devex #127 February 2017)
> Improve eap compatibility test execution
> ----------------------------------------
>
> Key: JBIDE-23825
> URL: https://issues.jboss.org/browse/JBIDE-23825
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, server
> Affects Versions: 4.4.3.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.4.AM1
>
>
> This is a followup of JBIDE-23756 - with that, we are once again able to execute compatibility tests for eap. But there are a few things missing:
> For now I will make it work with what we have, but there are several things that need to be fixed:
> 1. Even if you only run the eap7x-compatibility profile, all of the runtimes (jboss as 4, as 5, as 7, wildfly...) will be downloaded anyway, because this is set up in as/itests/pom.xml - we need to come up with a way to only do this if the compatibility profile is not active. Maybe we need to switch to profile activation by property, e.g. eap7x-compatibility - the profile in as/itests/org.jboss.tools.as.ui.bot.itests/pom.xml would be activated by this, whereas all the other runtime downloads in as/itests/pom.xml would be in a profile that is deactivated using this property.
> 2. https://github.com/jbosstools/jbosstools-server/blob/master/as/itests/org...
> The eap7x-compatibility profile has jboss-eap-7.0 server directory hardcoded. You can still override the whole property with something else for eap 7.1, but it would be nice to improve this.
> For reference, this is a job where Radim demonstrated the new way to execute tests:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job...
> And these are the two jobs EAP QE uses for the compatibilty testing:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-70x-jbds-c...
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-23490 at 2/20/17 6:00 AM:
-------------------------------------------------------------
I have to repeat myself but the feature is designed in a way that you can create the server adapter from a pod but the server adapter will be associated with the most relevant OpenShift resource associated with that pod.
In the following order of existence:
* service
* deployement config
* replication controller
was (Author: jeffmaury):
I have to repeat myself but the feature is designed in a way that you can create the server adapter from a pod but the server adater will be associated with the most relevant OpenShift resource associated with that pod.
In the following order of existence:
* service
* deployement config
* replication controller
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23490:
------------------------------------
I have to repeat myself but the feature is design in a way that you can create the server adapter from a pod but the server adater will be associated with the most relevant OpenShift resource associated with that pod.
In the following order of existence:
* service
* deployement config
* replication controller
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-23490 at 2/20/17 5:59 AM:
-------------------------------------------------------------
I have to repeat myself but the feature is designed in a way that you can create the server adapter from a pod but the server adater will be associated with the most relevant OpenShift resource associated with that pod.
In the following order of existence:
* service
* deployement config
* replication controller
was (Author: jeffmaury):
I have to repeat myself but the feature is design in a way that you can create the server adapter from a pod but the server adater will be associated with the most relevant OpenShift resource associated with that pod.
In the following order of existence:
* service
* deployement config
* replication controller
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23490:
---------------------------------------
[~adietish] correct. Even if you would try to edit route to point to a pod instead of a service, OpenShift would not allow it. It would result into an error. Basically in hierarchy is Pod --> Service ---> Route. By exposing a pod you get a service which point to all relevant pods (specified by a selector). And by exposing a Service you get a routing to manage traffic to pods via pointing to a service.
I am still not sure why there is a need of having a Server adapter pointing to a pod instead of a Service. Pods are volatile, but they are managed by replication controller so there is still a pod for application if needed. And to easily access an application we have a service which always know which pods belong to app. By pointing a server adapter to a pod we could throw away all what OpenShift offer. It would basically get down to a docker level - plain containers without orchestration, management... If server adapter would work for a pod instead of service there are other issues linked to the nature of pods - restarting in debug would make it unusable (it starts different pod), scaling won't be possible (there is a Service for it to point to multiple pods). I am replying because in the document (Fuse Integration Services and its integration to OpenShift) I haven't seen any answer since 11/2016 when I last time was wondering why is this "workflow" desired.
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month