Re: [forge-dev] Openshift plugin

Hi Rafael there's no such function in the client library for now. Xavier implemented this in the Eclipse tooling. Afaik (had a quick look) it's using jgit to open an ssh session reads from the session and puts in to the eclipse console (TailServerLogAction# startTailProcess): <snip> RemoteSession remoteSession = sshSessionFactory.getSession(uri, CredentialsProvider.getDefault(), FS.DETECTED, 0); // "ssh -t #{app_uuid}(a)#{app}-#{namespace}.#{rhc_domain} 'tail#{opt['opts'] ? ' --opts ' + Base64::encode64(opt['opts']).chomp : ''} #{file_glob}'" final String command = buildCommand(logFilePath, options); Process process = remoteSession.exec(command, 0); return new TailServerLogWorker(console, process, remoteSession); </snip> http://anonsvn.jboss.org/repos/jbosstools/trunk/openshift/plugins/org.jbo... Cheers André On 10/10/2012 06:01 PM, 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 <mailto:forge-dev@lists.jboss.org> >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>