Hi all, After taking a deep dive on openshift plugin, I'm returning this to discussion as asked by Pete. The intention is to get the idea of what items the actual openshift plugin lacks of. Pete and Lincoln talked about some of them in JavaOne here are some: * support for embedding cartridges * support for eap * tail files I also got those: * setup when openshift application exists * snapshot management ? * key management ? * alias management * enable scaling on create app ? * Use alternate openshift config file * config port forward ? So basically I want to get your opinion about what is important and what is not and any other ideas and the priorities about all this items. Thank you. -- Rafael Benevides | Senior Software Engineer Red Hat Brazil +55-61-9269-6576 Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened!

>> Pete and Lincoln talked about some of them in JavaOne here are some: >> * support for embedding cartridges >> * support for eap >> * tail files

>> I also got those: >> * setup when openshift application exists >> * snapshot management ? >> * key management ? >> * alias management >> * enable scaling on create app ? >> * Use alternate openshift config file

>> * config port forward ?

> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! Oh I was wondering why EAP wasn't supported. Didn't realize the forge openshift install was jboss specific. One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools added support for naming the remote used so you could align them. If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >>> Pete and Lincoln talked about some of them in JavaOne here are some: >>> * support for embedding cartridges >>> * support for eap >>> * tail files all of the above is available for use from the new openshift client. >>> I also got those: >>> * setup when openshift application exists >>> * snapshot management ? >>> * key management ? >>> * alias management >>> * enable scaling on create app ? >>> * Use alternate openshift config file whats this one ? >>> * config port forward ? we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? /max _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! > > Oh I was wondering why EAP wasn't supported. > Didn't realize the forge openshift install was jboss specific. Yeah, I didn't support any more cartridges than just JBoss, as the focus for Forge is definitely on Java / Java EE projects!

I don't think Bill added many features, just massively improved the ones I put in ;-) On 4 Oct 2012, at 10:47, Max Rydahl Andersen wrote: >>>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>> Oh I was wondering why EAP wasn't supported. >>> Didn't realize the forge openshift install was jboss specific. >> Yeah, I didn't support any more cartridges than just JBoss, as the focus for Forge is definitely on Java / Java EE projects! > yeah I get that - for some reason I thought Bill Dc. added more support to the forge tools but that might just have been daydreaming ;) > > /max

Hi! So I think that's the final list and its priorities, right ? * support for eap (done!) (1) (FORGEPLUGINS-88) * setup when openshift app exists (1) * support for embedding cartridges (1) * tail files / checking all the log output (2) * check the jenkins support (2) * enable scaling on create app (3)

What about this items bellow? Is it desired or not ? * snapshot management ? * key management ? * alias management ? * Use alternate openshift config file ? * config port forward ?

I'll open separate issues for each one Em 04-10-2012 10:24, Xavier Coulon escreveu: > Hi ! > > As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). > > Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... > > Best regards, > /Xavier > > > > On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: > >> >>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >> >> Oh I was wondering why EAP wasn't supported. >> Didn't realize the forge openshift install was jboss specific. >> >> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >> >> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >> added support for naming the remote used so you could align them. >> >> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >> >>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>> * support for embedding cartridges >>>>> * support for eap >>>>> * tail files >> >> all of the above is available for use from the new openshift client. >> >>>>> I also got those: >>>>> * setup when openshift application exists >>>>> * snapshot management ? >>>>> * key management ? >>>>> * alias management >>>>> * enable scaling on create app ? >>>>> * Use alternate openshift config file >> >> whats this one ? >> >>>>> * config port forward ? >> >> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >> >> /max >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >

>>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >> >> Oh I was wondering why EAP wasn't supported. >> Didn't realize the forge openshift install was jboss specific. > > Yeah, I didn't support any more cartridges than just JBoss, as the focus for Forge is definitely on Java / Java EE projects! yeah I get that - for some reason I thought Bill Dc. added more support to the forge tools but that might just have been daydreaming ;)

Hi! So I think that's the final list and its priorities, right ? * support for eap (done!) (1) (FORGEPLUGINS-88) * setup when openshift app exists (1) * support for embedding cartridges (1) * tail files / checking all the log output (2) * check the jenkins support (2) * enable scaling on create app (3) What about this items bellow? Is it desired or not ? * snapshot management ? * key management ? * alias management ? * Use alternate openshift config file ? * config port forward ? I'll open separate issues for each one Em 04-10-2012 10:24, Xavier Coulon escreveu: > Hi ! > > As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). > > Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... > > Best regards, > /Xavier > > > > On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: > >> >>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >> >> Oh I was wondering why EAP wasn't supported. >> Didn't realize the forge openshift install was jboss specific. >> >> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >> >> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >> added support for naming the remote used so you could align them. >> >> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >> >>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>> * support for embedding cartridges >>>>> * support for eap >>>>> * tail files >> >> all of the above is available for use from the new openshift client. >> >>>>> I also got those: >>>>> * setup when openshift application exists >>>>> * snapshot management ? >>>>> * key management ? >>>>> * alias management >>>>> * enable scaling on create app ? >>>>> * Use alternate openshift config file >> >> whats this one ? >> >>>>> * config port forward ? >> >> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >> >> /max >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

It's FORGEPLUGINS-89 - That's the idea including me again on CC ;) 2012/10/5 Max Rydahl Andersen <max.andersen(a)redhat.com&gt; > Which one is the "check openshift can work with projects created by rhc > CLI and/or JBoss Tools" ? > > basically the plugin should check if one of the existing remotes looks > like a openshift repo (i.e. does the master have an .openshift folder, then > yeah - use that remote instead of adding a new) > > /max > > On 04 Oct 2012, at 22:04, Rafael Benevides <benevides(a)redhat.com&gt; wrote: > > > Hi! > > > > So I think that's the final list and its priorities, right ? > > > > * support for eap (done!) (1) (FORGEPLUGINS-88) > > * setup when openshift app exists (1) > > * support for embedding cartridges (1) > > * tail files / checking all the log output (2) > > * check the jenkins support (2) > > * enable scaling on create app (3) > > > > What about this items bellow? Is it desired or not ? > > > > * snapshot management ? > > * key management ? > > * alias management ? > > * Use alternate openshift config file ? > > * config port forward ? > > > > I'll open separate issues for each one > > > > Em 04-10-2012 10:24, Xavier Coulon escreveu: > >> Hi ! > >> > >> As Max mentioned, you should find all the API you need to implement > the features listed below in the Forge plugin in the new > openshift-java-client (V2.0), except maybe the 'tail files' feature which > we implemented in JBossTools because we use specific Eclipse APIs to > display the output in a MessageConsole. Maybe this could be refactored and > moved partially into the java-client library, though (we did not need to do > that when we worked on it a few months ago). > >> > >> Also, if you haven't already seen it, André recently wrote an article > about the new client library: > https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... > >> > >> Best regards, > >> /Xavier > >> > >> > >> > >> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: > >> > >>> > >>>> So I just started working on EAP support. > https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! > >>> > >>> Oh I was wondering why EAP wasn't supported. > >>> Didn't realize the forge openshift install was jboss specific. > >>> > >>> One item I got is that we check if the projects setup by JBoss Tools, > openshift client and OpenShift Forge client are compatible or can be made > compatible. > >>> > >>> i.e. forge *always* uses "openshift" as the remote afaik - openshift > client always create projects where the remote is in "origin" - as a > consequence jboss tools > >>> added support for naming the remote used so you could align them. > >>> > >>> If openshift could allow naming the remote or pick up the existing > remote pointing to openshift these things could be aligned. > >>> > >>>>>> Pete and Lincoln talked about some of them in JavaOne here are > some: > >>>>>> * support for embedding cartridges > >>>>>> * support for eap > >>>>>> * tail files > >>> > >>> all of the above is available for use from the new openshift client. > >>> > >>>>>> I also got those: > >>>>>> * setup when openshift application exists > >>>>>> * snapshot management ? > >>>>>> * key management ? > >>>>>> * alias management > >>>>>> * enable scaling on create app ? > >>>>>> * Use alternate openshift config file > >>> > >>> whats this one ? > >>> > >>>>>> * config port forward ? > >>> > >>> we got this in jbosstools - for forge I guess it requires running a > jsch port forward (or launch ssh native in separate process) ? > >>> > >>> /max > >>> _______________________________________________ > >>> forge-dev mailing list > >>> forge-dev(a)lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/forge-dev > >> > > _______________________________________________ > > forge-dev mailing list > > forge-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/forge-dev > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

I wasn't even reaching that far (though I do encourage the idea, particularly for TorqueBox, Immuntant, etc projects). My point is that Spring projects need to be on equal footing with Java EE projects in Forge. There are numerous arguments as to why, ranging from a wide user base, being competitive with Roo and--for those who want to move to JCP standards--migration. I don't think it benefits us (the Forge community) to look at Spring as inferior, just different. What we want is for developers to be productive, regardless of choice. If that was already implied, then pardon the interruption. -Dan -- Sent from my CyanogenMod-powered Android device, an open platform for carriers, developers and consumers. On Oct 6, 2012 12:01 PM, "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com&gt; wrote: > Regarding supporting more than Java EE. > > We should definitely start with first-class support for EE projects, but > if we can also do the same for other cartridges like PHP and Ruby, then > great! > > ~Lincoln > > On Fri, Oct 5, 2012 at 7:52 AM, Rafael Benevides <rafabene(a)gmail.com&gt;wrote: > >> It's FORGEPLUGINS-89 - That's the idea >> >> including me again on CC ;) >> >> >> >> 2012/10/5 Max Rydahl Andersen <max.andersen(a)redhat.com&gt; >> >>> Which one is the "check openshift can work with projects created by rhc >>> CLI and/or JBoss Tools" ? >>> >>> basically the plugin should check if one of the existing remotes looks >>> like a openshift repo (i.e. does the master have an .openshift folder, then >>> yeah - use that remote instead of adding a new) >>> >>> /max >>> >>> On 04 Oct 2012, at 22:04, Rafael Benevides <benevides(a)redhat.com&gt; >>> wrote: >>> >>> > Hi! >>> > >>> > So I think that's the final list and its priorities, right ? >>> > >>> > * support for eap (done!) (1) (FORGEPLUGINS-88) >>> > * setup when openshift app exists (1) >>> > * support for embedding cartridges (1) >>> > * tail files / checking all the log output (2) >>> > * check the jenkins support (2) >>> > * enable scaling on create app (3) >>> > >>> > What about this items bellow? Is it desired or not ? >>> > >>> > * snapshot management ? >>> > * key management ? >>> > * alias management ? >>> > * Use alternate openshift config file ? >>> > * config port forward ? >>> > >>> > I'll open separate issues for each one >>> > >>> > Em 04-10-2012 10:24, Xavier Coulon escreveu: >>> >> Hi ! >>> >> >>> >> As Max mentioned, you should find all the API you need to implement >>> the features listed below in the Forge plugin in the new >>> openshift-java-client (V2.0), except maybe the 'tail files' feature which >>> we implemented in JBossTools because we use specific Eclipse APIs to >>> display the output in a MessageConsole. Maybe this could be refactored and >>> moved partially into the java-client library, though (we did not need to do >>> that when we worked on it a few months ago). >>> >> >>> >> Also, if you haven't already seen it, André recently wrote an >>> article about the new client library: >>> https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >>> >> >>> >> Best regards, >>> >> /Xavier >>> >> >>> >> >>> >> >>> >> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>> >> >>> >>> >>> >>>> So I just started working on EAP support. >>> https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>> >>> >>> >>> Oh I was wondering why EAP wasn't supported. >>> >>> Didn't realize the forge openshift install was jboss specific. >>> >>> >>> >>> One item I got is that we check if the projects setup by JBoss >>> Tools, openshift client and OpenShift Forge client are compatible or can be >>> made compatible. >>> >>> >>> >>> i.e. forge *always* uses "openshift" as the remote afaik - >>> openshift client always create projects where the remote is in "origin" - >>> as a consequence jboss tools >>> >>> added support for naming the remote used so you could align them. >>> >>> >>> >>> If openshift could allow naming the remote or pick up the existing >>> remote pointing to openshift these things could be aligned. >>> >>> >>> >>>>>> Pete and Lincoln talked about some of them in JavaOne here are >>> some: >>> >>>>>> * support for embedding cartridges >>> >>>>>> * support for eap >>> >>>>>> * tail files >>> >>> >>> >>> all of the above is available for use from the new openshift client. >>> >>> >>> >>>>>> I also got those: >>> >>>>>> * setup when openshift application exists >>> >>>>>> * snapshot management ? >>> >>>>>> * key management ? >>> >>>>>> * alias management >>> >>>>>> * enable scaling on create app ? >>> >>>>>> * Use alternate openshift config file >>> >>> >>> >>> whats this one ? >>> >>> >>> >>>>>> * config port forward ? >>> >>> >>> >>> we got this in jbosstools - for forge I guess it requires running a >>> jsch port forward (or launch ssh native in separate process) ? >>> >>> >>> >>> /max >>> >>> _______________________________________________ >>> >>> forge-dev mailing list >>> >>> forge-dev(a)lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >> >>> > _______________________________________________ >>> > forge-dev mailing list >>> > forge-dev(a)lists.jboss.org >>> > https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> > > > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Hi ! As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... Best regards, /Xavier On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: > >> So I just started working on EAP support. >> https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! > > Oh I was wondering why EAP wasn't supported. > Didn't realize the forge openshift install was jboss specific. > > One item I got is that we check if the projects setup by JBoss Tools, > openshift client and OpenShift Forge client are compatible or can be > made compatible. > > i.e. forge *always* uses "openshift" as the remote afaik - openshift > client always create projects where the remote is in "origin" - as a > consequence jboss tools > added support for naming the remote used so you could align them. > > If openshift could allow naming the remote or pick up the existing > remote pointing to openshift these things could be aligned. > >>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>> * support for embedding cartridges >>>> * support for eap >>>> * tail files > > all of the above is available for use from the new openshift client. > >>>> I also got those: >>>> * setup when openshift application exists >>>> * snapshot management ? >>>> * key management ? >>>> * alias management >>>> * enable scaling on create app ? >>>> * Use alternate openshift config file > > whats this one ? > >>>> * config port forward ? > > we got this in jbosstools - for forge I guess it requires running a > jsch port forward (or launch ssh native in separate process) ? > > /max > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/forge-dev

Bill / Andre / Xavier I didn't find on openshift-java-client how to tail files. Does it have this feature ? Thanks Em 04-10-2012 10:24, Xavier Coulon escreveu: > Hi ! > > As Max mentioned, you should find all the API you need to implement > the features listed below in the Forge plugin in the new > openshift-java-client (V2.0), except maybe the 'tail files' feature > which we implemented in JBossTools because we use specific Eclipse > APIs to display the output in a MessageConsole. Maybe this could be > refactored and moved partially into the java-client library, though > (we did not need to do that when we worked on it a few months ago). > > Also, if you haven't already seen it, André recently wrote an article > about the new client library: > https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... > > > Best regards, > /Xavier > > > > On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: > >> >>> So I just started working on EAP support. >>> https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >> >> Oh I was wondering why EAP wasn't supported. >> Didn't realize the forge openshift install was jboss specific. >> >> One item I got is that we check if the projects setup by JBoss >> Tools, openshift client and OpenShift Forge client are compatible or >> can be made compatible. >> >> i.e. forge *always* uses "openshift" as the remote afaik - openshift >> client always create projects where the remote is in "origin" - as a >> consequence jboss tools >> added support for naming the remote used so you could align them. >> >> If openshift could allow naming the remote or pick up the existing >> remote pointing to openshift these things could be aligned. >> >>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>> * support for embedding cartridges >>>>> * support for eap >>>>> * tail files >> >> all of the above is available for use from the new openshift client. >> >>>>> I also got those: >>>>> * setup when openshift application exists >>>>> * snapshot management ? >>>>> * key management ? >>>>> * alias management >>>>> * enable scaling on create app ? >>>>> * Use alternate openshift config file >> >> whats this one ? >> >>>>> * config port forward ? >> >> we got this in jbosstools - for forge I guess it requires running a >> jsch port forward (or launch ssh native in separate process) ? >> >> /max >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/forge-dev >

Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. On 10/10/12 9:01 AM, Rafael Benevides wrote: Bill / Andre / Xavier I didn't find on openshift-java-client how to tail files. Does it have this feature ? Thanks Em 04-10-2012 10:24, Xavier Coulon escreveu: Hi ! As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... Best regards, /Xavier On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! Oh I was wondering why EAP wasn't supported. Didn't realize the forge openshift install was jboss specific. One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools added support for naming the remote used so you could align them. If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. Pete and Lincoln talked about some of them in JavaOne here are some: * support for embedding cartridges * support for eap * tail files all of the above is available for use from the new openshift client. I also got those: * setup when openshift application exists * snapshot management ? * key management ? * alias management * enable scaling on create app ? * Use alternate openshift config file whats this one ? * config port forward ? we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? /max _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Bill DeCoste Principal Software Engineer, Red Hat978-204-0920wdecoste(a)redhat.com _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Good question! I was just investigating a solution for Windows environment. 2012/10/10 Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; Isn't the current JBoss Tools way of doing this OS-specific? E.g. The user > would need to have openSSH installed in windows to make this work? Or is > that assumed? > > ~Lincoln > > > On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste <wdecoste(a)redhat.com&gt;wrote: > >> Unfortunately not yet. The REST API does not expose this feature yet. >> It's on the roadmap. It will probably be exposed as status. >> >> >> On 10/10/12 9:01 AM, Rafael Benevides wrote: >> >> Bill / Andre / Xavier >> >> I didn't find on openshift-java-client how to tail files. >> >> Does it have this feature ? >> >> >> Thanks >> >> Em 04-10-2012 10:24, Xavier Coulon escreveu: >> >> Hi ! >> >> As Max mentioned, you should find all the API you need to implement >> the features listed below in the Forge plugin in the new >> openshift-java-client (V2.0), except maybe the 'tail files' feature which >> we implemented in JBossTools because we use specific Eclipse APIs to >> display the output in a MessageConsole. Maybe this could be refactored and >> moved partially into the java-client library, though (we did not need to do >> that when we worked on it a few months ago). >> >> Also, if you haven't already seen it, André recently wrote an article >> about the new client library: >> https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >> >> >> Best regards, >> /Xavier >> >> >> >> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >> >> >> So I just started working on EAP support. >> https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >> >> >> Oh I was wondering why EAP wasn't supported. >> Didn't realize the forge openshift install was jboss specific. >> >> One item I got is that we check if the projects setup by JBoss Tools, >> openshift client and OpenShift Forge client are compatible or can be made >> compatible. >> >> i.e. forge *always* uses "openshift" as the remote afaik - openshift >> client always create projects where the remote is in "origin" - as a >> consequence jboss tools >> added support for naming the remote used so you could align them. >> >> If openshift could allow naming the remote or pick up the existing >> remote pointing to openshift these things could be aligned. >> >> Pete and Lincoln talked about some of them in JavaOne here are some: >> >> * support for embedding cartridges >> >> * support for eap >> >> * tail files >> >> >> all of the above is available for use from the new openshift client. >> >> I also got those: >> >> * setup when openshift application exists >> >> * snapshot management ? >> >> * key management ? >> >> * alias management >> >> * enable scaling on create app ? >> >> * Use alternate openshift config file >> >> >> whats this one ? >> >> * config port forward ? >> >> >> we got this in jbosstools - for forge I guess it requires running a jsch >> port forward (or launch ssh native in separate process) ? >> >> /max >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> >> >> -- >> Bill DeCoste >> Principal Software Engineer, Red Hat978-204-0920wdecoste(a)redhat.com >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> > > > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > >

Isn't the current JBoss Tools way of doing this OS-specific? E.g. The user would need to have openSSH installed in windows to make this work? Or is that assumed? ~Lincoln On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste <wdecoste(a)redhat.com&gt; wrote: Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. On 10/10/12 9:01 AM, Rafael Benevides wrote: > Bill / Andre / Xavier > > I didn't find on openshift-java-client how to tail files. > > Does it have this feature ? > > > Thanks > > Em 04-10-2012 10:24, Xavier Coulon escreveu: >> Hi ! >> >> As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). >> >> Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >> >> Best regards, >> /Xavier >> >> >> >> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >> >>> >>>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>> >>> Oh I was wondering why EAP wasn't supported. >>> Didn't realize the forge openshift install was jboss specific. >>> >>> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >>> >>> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >>> added support for naming the remote used so you could align them. >>> >>> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >>> >>>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>>> * support for embedding cartridges >>>>>> * support for eap >>>>>> * tail files >>> >>> all of the above is available for use from the new openshift client. >>> >>>>>> I also got those: >>>>>> * setup when openshift application exists >>>>>> * snapshot management ? >>>>>> * key management ? >>>>>> * alias management >>>>>> * enable scaling on create app ? >>>>>> * Use alternate openshift config file >>> >>> whats this one ? >>> >>>>>> * config port forward ? >>> >>> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >>> >>> /max >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> -- Bill DeCoste Principal Software Engineer, Red Hat 978-204-0920 wdecoste(a)redhat.com _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Lincoln. I've run git installation on Windows (like suggested on Installing Forge Guide) and now I choose to install Unix tools on Windows Unix tools comes with ssh and it worked pretty well. Maybe we can update the forge installation guide ( http://forge.jboss.org/docs/using/) to suggest installation of Unix tools when installing Git. It will not only reduce issues with this plugin, but maybe with many others possible issues with other plugins. 2012/10/10 Rafael Benevides <rafabene(a)gmail.com&gt; > I've just tested plink.exe from > http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and it > worked on Windows environment. > > openshift plugin can propose its installation if NativeSystemCall returns > an error on Windows Environment. What you think ? > > > 2012/10/10 Rafael Benevides <rafabene(a)gmail.com&gt; > >> Good question! >> >> I was just investigating a solution for Windows environment. >> >> 2012/10/10 Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; >> >> Isn't the current JBoss Tools way of doing this OS-specific? E.g. The >>> user would need to have openSSH installed in windows to make this work? Or >>> is that assumed? >>> >>> ~Lincoln >>> >>> >>> On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste <wdecoste(a)redhat.com&gt;wrote: >>> >>>> Unfortunately not yet. The REST API does not expose this feature yet. >>>> It's on the roadmap. It will probably be exposed as status. >>>> >>>> >>>> On 10/10/12 9:01 AM, Rafael Benevides wrote: >>>> >>>> Bill / Andre / Xavier >>>> >>>> I didn't find on openshift-java-client how to tail files. >>>> >>>> Does it have this feature ? >>>> >>>> >>>> Thanks >>>> >>>> Em 04-10-2012 10:24, Xavier Coulon escreveu: >>>> >>>> Hi ! >>>> >>>> As Max mentioned, you should find all the API you need to implement >>>> the features listed below in the Forge plugin in the new >>>> openshift-java-client (V2.0), except maybe the 'tail files' feature which >>>> we implemented in JBossTools because we use specific Eclipse APIs to >>>> display the output in a MessageConsole. Maybe this could be refactored and >>>> moved partially into the java-client library, though (we did not need to do >>>> that when we worked on it a few months ago). >>>> >>>> Also, if you haven't already seen it, André recently wrote an >>>> article about the new client library: >>>> https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >>>> >>>> >>>> Best regards, >>>> /Xavier >>>> >>>> >>>> >>>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>>> >>>> >>>> So I just started working on EAP support. >>>> https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>>> >>>> >>>> Oh I was wondering why EAP wasn't supported. >>>> Didn't realize the forge openshift install was jboss specific. >>>> >>>> One item I got is that we check if the projects setup by JBoss Tools, >>>> openshift client and OpenShift Forge client are compatible or can be made >>>> compatible. >>>> >>>> i.e. forge *always* uses "openshift" as the remote afaik - openshift >>>> client always create projects where the remote is in "origin" - as a >>>> consequence jboss tools >>>> added support for naming the remote used so you could align them. >>>> >>>> If openshift could allow naming the remote or pick up the existing >>>> remote pointing to openshift these things could be aligned. >>>> >>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>> >>>> * support for embedding cartridges >>>> >>>> * support for eap >>>> >>>> * tail files >>>> >>>> >>>> all of the above is available for use from the new openshift client. >>>> >>>> I also got those: >>>> >>>> * setup when openshift application exists >>>> >>>> * snapshot management ? >>>> >>>> * key management ? >>>> >>>> * alias management >>>> >>>> * enable scaling on create app ? >>>> >>>> * Use alternate openshift config file >>>> >>>> >>>> whats this one ? >>>> >>>> * config port forward ? >>>> >>>> >>>> we got this in jbosstools - for forge I guess it requires running a >>>> jsch port forward (or launch ssh native in separate process) ? >>>> >>>> /max >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> >>>> >>>> -- >>>> Bill DeCoste >>>> Principal Software Engineer, Red Hat978-204-0920wdecoste(a)redhat.com >>>> >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> >>> >>> >>> -- >>> Lincoln Baxter, III >>> http://ocpsoft.org >>> "Simpler is better." >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> >> >

there should be *zero* need to use ssh command lines for this stuff. jsch is sufficient afaik. /max On 11 Oct 2012, at 16:00, Rafael Benevides&lt;rafabene(a)gmail.com&gt; wrote: > Lincoln, > > Never mind the comment below. ssh.exe comes with the most basic git installation on windows. Anyway I think that there won't be a problem with Windows. > > 2012/10/10 Rafael Benevides&lt;rafabene(a)gmail.com&gt; > Lincoln. > > I've run git installation on Windows (like suggested on Installing Forge Guide) and now I choose to install Unix tools on Windows > > Unix tools comes with ssh and it worked pretty well. > > Maybe we can update the forge installation guide (http://forge.jboss.org/docs/using/) to suggest installation of Unix tools when installing Git. It will not only reduce issues with this plugin, but maybe with many others possible issues with other plugins. > > > > 2012/10/10 Rafael Benevides&lt;rafabene(a)gmail.com&gt; > I've just tested plink.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and it worked on Windows environment. > > openshift plugin can propose its installation if NativeSystemCall returns an error on Windows Environment. What you think ? > > > 2012/10/10 Rafael Benevides&lt;rafabene(a)gmail.com&gt; > Good question! > > I was just investigating a solution for Windows environment. > > 2012/10/10 Lincoln Baxter, III&lt;lincolnbaxter(a)gmail.com&gt; > > Isn't the current JBoss Tools way of doing this OS-specific? E.g. The user would need to have openSSH installed in windows to make this work? Or is that assumed? > > ~Lincoln > > > On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste&lt;wdecoste(a)redhat.com&gt; wrote: > Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. > > > On 10/10/12 9:01 AM, Rafael Benevides wrote: >> Bill / Andre / Xavier >> >> I didn't find on openshift-java-client how to tail files. >> >> Does it have this feature ? >> >> >> Thanks >> >> Em 04-10-2012 10:24, Xavier Coulon escreveu: >>> Hi ! >>> >>> As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). >>> >>> Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >>> >>> Best regards, >>> /Xavier >>> >>> >>> >>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>> >>>>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>>> Oh I was wondering why EAP wasn't supported. >>>> Didn't realize the forge openshift install was jboss specific. >>>> >>>> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >>>> >>>> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >>>> added support for naming the remote used so you could align them. >>>> >>>> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >>>> >>>>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>>>> * support for embedding cartridges >>>>>>> * support for eap >>>>>>> * tail files >>>> all of the above is available for use from the new openshift client. >>>> >>>>>>> I also got those: >>>>>>> * setup when openshift application exists >>>>>>> * snapshot management ? >>>>>>> * key management ? >>>>>>> * alias management >>>>>>> * enable scaling on create app ? >>>>>>> * Use alternate openshift config file >>>> whats this one ? >>>> >>>>>>> * config port forward ? >>>> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >>>> >>>> /max >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev > -- > Bill DeCoste > Principal Software Engineer, Red Hat > > 978-204-0920 > wdecoste(a)redhat.com > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev

The tail used to be via status for some cart types. The arch board is discussing the best and consistent way to provide both.

On 10/11/12 1:16 AM, Max Rydahl Andersen wrote: > >> Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. > tailing of files as a status ? that seems like two different concerns ? > > /max > >> On 10/10/12 9:01 AM, Rafael Benevides wrote: >>> Bill / Andre / Xavier >>> >>> I didn't find on openshift-java-client how to tail files. >>> >>> Does it have this feature ? >>> >>> >>> Thanks >>> >>> Em 04-10-2012 10:24, Xavier Coulon escreveu: >>>> Hi ! >>>> >>>> As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). >>>> >>>> Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >>>> >>>> Best regards, >>>> /Xavier >>>> >>>> >>>> >>>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>>> >>>>>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>>>> Oh I was wondering why EAP wasn't supported. >>>>> Didn't realize the forge openshift install was jboss specific. >>>>> >>>>> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >>>>> >>>>> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >>>>> added support for naming the remote used so you could align them. >>>>> >>>>> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >>>>> >>>>>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>>>>> * support for embedding cartridges >>>>>>>> * support for eap >>>>>>>> * tail files >>>>> all of the above is available for use from the new openshift client. >>>>> >>>>>>>> I also got those: >>>>>>>> * setup when openshift application exists >>>>>>>> * snapshot management ? >>>>>>>> * key management ? >>>>>>>> * alias management >>>>>>>> * enable scaling on create app ? >>>>>>>> * Use alternate openshift config file >>>>> whats this one ? >>>>> >>>>>>>> * config port forward ? >>>>> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >>>>> >>>>> /max >>>>> _______________________________________________ >>>>> forge-dev mailing list >>>>> forge-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >> -- >> Bill DeCoste >> Principal Software Engineer, Red Hat >> 978-204-0920 >> >> wdecoste(a)redhat.com >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev -- Bill DeCoste Principal Software Engineer, Red Hat 978-204-0920 wdecoste(a)redhat.com

The tail used to be via status for some cart types. The arch board is discussing the best and consistent way to provide both.

On 10/11/12 1:16 AM, Max Rydahl Andersen wrote: > >> Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. > tailing of files as a status ? that seems like two different concerns ? > > /max > >> On 10/10/12 9:01 AM, Rafael Benevides wrote: >>> Bill / Andre / Xavier >>> >>> I didn't find on openshift-java-client how to tail files. >>> >>> Does it have this feature ? >>> >>> >>> Thanks >>> >>> Em 04-10-2012 10:24, Xavier Coulon escreveu: >>>> Hi ! >>>> >>>> As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). >>>> >>>> Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >>>> >>>> Best regards, >>>> /Xavier >>>> >>>> >>>> >>>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>>> >>>>>> So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>>>> Oh I was wondering why EAP wasn't supported. >>>>> Didn't realize the forge openshift install was jboss specific. >>>>> >>>>> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >>>>> >>>>> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >>>>> added support for naming the remote used so you could align them. >>>>> >>>>> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >>>>> >>>>>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>>>>> * support for embedding cartridges >>>>>>>> * support for eap >>>>>>>> * tail files >>>>> all of the above is available for use from the new openshift client. >>>>> >>>>>>>> I also got those: >>>>>>>> * setup when openshift application exists >>>>>>>> * snapshot management ? >>>>>>>> * key management ? >>>>>>>> * alias management >>>>>>>> * enable scaling on create app ? >>>>>>>> * Use alternate openshift config file >>>>> whats this one ? >>>>> >>>>>>>> * config port forward ? >>>>> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >>>>> >>>>> /max >>>>> _______________________________________________ >>>>> forge-dev mailing list >>>>> forge-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >> -- >> Bill DeCoste >> Principal Software Engineer, Red Hat >> 978-204-0920 >> >> wdecoste(a)redhat.com >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev -- Bill DeCoste Principal Software Engineer, Red Hat 978-204-0920 wdecoste(a)redhat.com

Hi guys. Tail implemented using Jsch. Thanks #jbosstools guys for the help! Em 11-10-2012 16:24, Xavier Coulon escreveu: > Raphael, > > You probably need to implement your own UserInfo as shown in this > example: http://www.jcraft.com/jsch/examples/Exec.java.html > This is also one of the reason our "tail" code is in the Eclipse > plugin and not in the client-library: we can plug into Eclipse SSH2 > Key management infrastructure (eg: SSH2 Key preferences, passpharse > prompt dialog, etc..). Since you're going towards a full CLI-based > approach, you'll certainly need to look at the user's private key(s) > and prompt its passphrase. The jcraft website has some good example > how UserInfo implementations. > > HTH > Best regards, > /Xavier > > > > On Oct 11, 2012, at 5:49 PM, Rafael Benevides wrote: > >> >> The first impl was command line based. Now I reopened >> https://issues.jboss.org/browse/FORGEPLUGINS-91 so I'm changing the >> impl to use jsch. >> >> I'm facing problems with "auth fail" and public-key authentication. >> Do you guys have any clue ?! It's the first time I'm using jgit/jsch >> API so I still searching how to do it. >> >> Em 11-10-2012 12:31, Max Rydahl Andersen escreveu: >>> there should be *zero* need to use ssh command lines for this stuff. jsch is sufficient afaik. >>> >>> /max >>> >>> On 11 Oct 2012, at 16:00, Rafael Benevides&lt;rafabene(a)gmail.com&gt; wrote: >>> >>>> Lincoln, >>>> >>>> Never mind the comment below. ssh.exe comes with the most basic git installation on windows. Anyway I think that there won't be a problem with Windows. >>>> >>>> 2012/10/10 Rafael Benevides&lt;rafabene(a)gmail.com&gt; >>>> Lincoln. >>>> >>>> I've run git installation on Windows (like suggested on Installing Forge Guide) and now I choose to install Unix tools on Windows >>>> >>>> Unix tools comes with ssh and it worked pretty well. >>>> >>>> Maybe we can update the forge installation guide (http://forge.jboss.org/docs/using/) to suggest installation of Unix tools when installing Git. It will not only reduce issues with this plugin, but maybe with many others possible issues with other plugins. >>>> >>>> >>>> >>>> 2012/10/10 Rafael Benevides&lt;rafabene(a)gmail.com&gt; >>>> I've just tested plink.exe fromhttp://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and it worked on Windows environment. >>>> >>>> openshift plugin can propose its installation if NativeSystemCall returns an error on Windows Environment. What you think ? >>>> >>>> >>>> 2012/10/10 Rafael Benevides&lt;rafabene(a)gmail.com&gt; >>>> Good question! >>>> >>>> I was just investigating a solution for Windows environment. >>>> >>>> 2012/10/10 Lincoln Baxter, III&lt;lincolnbaxter(a)gmail.com&gt; >>>> >>>> Isn't the current JBoss Tools way of doing this OS-specific? E.g. The user would need to have openSSH installed in windows to make this work? Or is that assumed? >>>> >>>> ~Lincoln >>>> >>>> >>>> On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste&lt;wdecoste(a)redhat.com&gt; wrote: >>>> Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. >>>> >>>> >>>> On 10/10/12 9:01 AM, Rafael Benevides wrote: >>>>> Bill / Andre / Xavier >>>>> >>>>> I didn't find on openshift-java-client how to tail files. >>>>> >>>>> Does it have this feature ? >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Em 04-10-2012 10:24, Xavier Coulon escreveu: >>>>>> Hi ! >>>>>> >>>>>> As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). >>>>>> >>>>>> Also, if you haven't already seen it, André recently wrote an article about the new client library:https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-... >>>>>> >>>>>> Best regards, >>>>>> /Xavier >>>>>> >>>>>> >>>>>> >>>>>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>>>>> >>>>>>>> So I just started working on EAP support.https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>>>>>> Oh I was wondering why EAP wasn't supported. >>>>>>> Didn't realize the forge openshift install was jboss specific. >>>>>>> >>>>>>> One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. >>>>>>> >>>>>>> i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools >>>>>>> added support for naming the remote used so you could align them. >>>>>>> >>>>>>> If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. >>>>>>> >>>>>>>>>> Pete and Lincoln talked about some of them in JavaOne here are some: >>>>>>>>>> * support for embedding cartridges >>>>>>>>>> * support for eap >>>>>>>>>> * tail files >>>>>>> all of the above is available for use from the new openshift client. >>>>>>> >>>>>>>>>> I also got those: >>>>>>>>>> * setup when openshift application exists >>>>>>>>>> * snapshot management ? >>>>>>>>>> * key management ? >>>>>>>>>> * alias management >>>>>>>>>> * enable scaling on create app ? >>>>>>>>>> * Use alternate openshift config file >>>>>>> whats this one ? >>>>>>> >>>>>>>>>> * config port forward ? >>>>>>> we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? >>>>>>> >>>>>>> /max >>>>>>> _______________________________________________ >>>>>>> forge-dev mailing list >>>>>>> forge-dev(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> -- >>>> Bill DeCoste >>>> Principal Software Engineer, Red Hat >>>> >>>> 978-204-0920 >>>> wdecoste(a)redhat.com >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> >>>> >>>> >>>> -- >>>> Lincoln Baxter, III >>>> http://ocpsoft.org >>>> "Simpler is better." >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/forge-dev >

This is what the java client used to use, but was removed when we moved to the new REST api. On 10/16/12 2:28 PM, Rafael Benevides wrote: Hi guys. Tail implemented using Jsch. Thanks #jbosstools guys for the help! Em 11-10-2012 16:24, Xavier Coulon escreveu: Raphael, You probably need to implement your own UserInfo as shown in this example: http://www.jcraft.com/jsch/examples/Exec.java.html This is also one of the reason our "tail" code is in the Eclipse plugin and not in the client-library: we can plug into Eclipse SSH2 Key management infrastructure (eg: SSH2 Key preferences, passpharse prompt dialog, etc..). Since you're going towards a full CLI-based approach, you'll certainly need to look at the user's private key(s) and prompt its passphrase. The jcraft website has some good example how UserInfo implementations. HTH Best regards, /Xavier On Oct 11, 2012, at 5:49 PM, Rafael Benevides wrote: The first impl was command line based. Now I reopened https://issues.jboss.org/browse/FORGEPLUGINS-91 so I'm changing the impl to use jsch. I'm facing problems with "auth fail" and public-key authentication. Do you guys have any clue ?! It's the first time I'm using jgit/jsch API so I still searching how to do it. Em 11-10-2012 12:31, Max Rydahl Andersen escreveu: there should be *zero* need to use ssh command lines for this stuff. jsch is sufficient afaik. /max On 11 Oct 2012, at 16:00, Rafael Benevides <rafabene(a)gmail.com&gt; <rafabene(a)gmail.com&gt; wrote: Lincoln, Never mind the comment below. ssh.exe comes with the most basic git installation on windows. Anyway I think that there won't be a problem with Windows. 2012/10/10 Rafael Benevides <rafabene(a)gmail.com&gt; <rafabene(a)gmail.com&gt; Lincoln. I've run git installation on Windows (like suggested on Installing Forge Guide) and now I choose to install Unix tools on Windows Unix tools comes with ssh and it worked pretty well. Maybe we can update the forge installation guide (http://forge.jboss.org/docs/using/) to suggest installation of Unix tools when installing Git. It will not only reduce issues with this plugin, but maybe with many others possible issues with other plugins. 2012/10/10 Rafael Benevides <rafabene(a)gmail.com&gt; <rafabene(a)gmail.com&gt; I've just tested plink.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and it worked on Windows environment. openshift plugin can propose its installation if NativeSystemCall returns an error on Windows Environment. What you think ? 2012/10/10 Rafael Benevides <rafabene(a)gmail.com&gt; <rafabene(a)gmail.com&gt; Good question! I was just investigating a solution for Windows environment. 2012/10/10 Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; <lincolnbaxter(a)gmail.com&gt; Isn't the current JBoss Tools way of doing this OS-specific? E.g. The user would need to have openSSH installed in windows to make this work? Or is that assumed? ~Lincoln On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste <wdecoste(a)redhat.com&gt; <wdecoste(a)redhat.com&gt; wrote: Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status. On 10/10/12 9:01 AM, Rafael Benevides wrote: Bill / Andre / Xavier I didn't find on openshift-java-client how to tail files. Does it have this feature ? Thanks Em 04-10-2012 10:24, Xavier Coulon escreveu: Hi ! As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago). Also, if you haven't already seen it, André recently wrote an article about the new client library: https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... Best regards, /Xavier On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: So I just started working on EAP support. https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! Oh I was wondering why EAP wasn't supported. Didn't realize the forge openshift install was jboss specific. One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible. i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools added support for naming the remote used so you could align them. If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned. Pete and Lincoln talked about some of them in JavaOne here are some: * support for embedding cartridges * support for eap * tail files all of the above is available for use from the new openshift client. I also got those: * setup when openshift application exists * snapshot management ? * key management ? * alias management * enable scaling on create app ? * Use alternate openshift config file whats this one ? * config port forward ? we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ? /max _______________________________________________ forge-dev mailing listforge-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/forge-dev -- Bill DeCoste Principal Software Engineer, Red Hat 978-204-0920wdecoste(a)redhat.com _______________________________________________ forge-dev mailing listforge-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/forge-dev -- Lincoln Baxter, IIIhttp://ocpsoft.org "Simpler is better." _______________________________________________ forge-dev mailing listforge-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing listforge-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev -- Bill DeCoste Principal Software Engineer, Red Hat978-204-0920wdecoste(a)redhat.com _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Em 04-10-2012 17:24, Pete Muir escreveu: > On 4 Oct 2012, at 13:04, Rafael Benevides wrote: > >> Hi! >> >> So I think that's the final list and its priorities, right ? >> >> * support for eap (done!) (1) FORGEPLUGINS-88 >> * setup when openshift app exists (1) FORGEPLUGINS-89 >> * support for embedding cartridges (1) FORGEPLUGINS-90 >> * tail files / checking all the log output (2) FORGEPLUGINS-91 >> * check the jenkins support (2) FORGEPLUGINS-92 >> * enable scaling on create app (3) FORGEPLUGINS-93 > Agreed. > >> What about this items bellow? Is it desired or not ? >> >> * snapshot management ? >> * key management ? >> * alias management ? >> * Use alternate openshift config file ? >> * config port forward ? > Definitely useful, but maybe Bill can take some of these once he some > time. > >> I'll open separate issues for each one >> >> Em 04-10-2012 10:24, Xavier Coulon escreveu: >>> Hi ! >>> >>> As Max mentioned, you should find all the API you need to implement >>> the features listed below in the Forge plugin in the new >>> openshift-java-client (V2.0), except maybe the 'tail files' feature >>> which we implemented in JBossTools because we use specific Eclipse >>> APIs to display the output in a MessageConsole. Maybe this could be >>> refactored and moved partially into the java-client library, though >>> (we did not need to do that when we worked on it a few months ago). >>> >>> Also, if you haven't already seen it, André recently wrote an >>> article about the new client library: >>> https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope... >>> >>> Best regards, >>> /Xavier >>> >>> >>> >>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote: >>> >>>>> So I just started working on EAP support. >>>>> https://issues.jboss.org/browse/FORGEPLUGINS-88 opened! >>>> Oh I was wondering why EAP wasn't supported. >>>> Didn't realize the forge openshift install was jboss specific. >>>> >>>> One item I got is that we check if the projects setup by JBoss >>>> Tools, openshift client and OpenShift Forge client are compatible >>>> or can be made compatible. >>>> >>>> i.e. forge *always* uses "openshift" as the remote afaik - >>>> openshift client always create projects where the remote is in >>>> "origin" - as a consequence jboss tools >>>> added support for naming the remote used so you could align them. >>>> >>>> If openshift could allow naming the remote or pick up the existing >>>> remote pointing to openshift these things could be aligned. >>>> >>>>>>> Pete and Lincoln talked about some of them in JavaOne here are >>>>>>> some: >>>>>>> * support for embedding cartridges >>>>>>> * support for eap >>>>>>> * tail files >>>> all of the above is available for use from the new openshift client. >>>> >>>>>>> I also got those: >>>>>>> * setup when openshift application exists >>>>>>> * snapshot management ? >>>>>>> * key management ? >>>>>>> * alias management >>>>>>> * enable scaling on create app ? >>>>>>> * Use alternate openshift config file >>>> whats this one ? >>>> >>>>>>> * config port forward ? >>>> we got this in jbosstools - for forge I guess it requires running >>>> a jsch port forward (or launch ssh native in separate process) ? >>>> >>>> /max >>>> _______________________________________________ >>>> forge-dev mailing list >>>> forge-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/forge-dev