[forge-dev] Openshift plugin

Lincoln Baxter, III lincolnbaxter at gmail.com
Sat Oct 6 14:00:58 EDT 2012


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 at gmail.com> wrote:

> It's FORGEPLUGINS-89 - That's the idea
>
> including me again on CC ;)
>
>
>
> 2012/10/5 Max Rydahl Andersen <max.andersen at redhat.com>
>
>> 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 at redhat.com> 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-openshift-java-client-in-a-nutshell
>> >>
>> >> 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 at lists.jboss.org
>> >>> https://lists.jboss.org/mailman/listinfo/forge-dev
>> >>
>> > _______________________________________________
>> > forge-dev mailing list
>> > forge-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>>
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>


-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20121006/be58fd9c/attachment.html 


More information about the forge-dev mailing list