4 Replies Latest reply on Jun 20, 2013 6:30 AM by Aslak Knutsen

    Arquillian OpenShift refresh plan

    Karel Piwko Master

      Hi,

       

      currently our OpenShift container is pretty old stuff, created in time when there were actually Expess and Flex containers. This does not reflect current situation.

       

      Apart from naming, the container biggest issue is that it is terribly slow, the reason is Jsch library that does not handle SSH payload effectively. Also, the other problem is that container contains numerous hacks, such as ping servlet and archive servlet scanning to emulate functionally normally provided by container.

       

      I'm planning to make OpenShift container more lightweigth, putting together a layer that establish port forwarding and afterwards connects via a AS7 Remote Adaptor. This approach is inspired by JBoss Tools and I believe the big ammount of code can actually be shared in between the projects.

       

      What's your opinion on that?

       

      Thanks,

       

      Karel

        • 1. Re: Arquillian OpenShift refresh plan
          Aslak Knutsen Master

          Sounds like a good plan!

           

          Start of as a alternative to the existing one, or fully replace it of the bet?

           

          You plan to reuse the AS7 containers ? Any thoughts on handling AS 7 vs EAP 6 vs Wildfly 8 ?

          • 2. Re: Arquillian OpenShift refresh plan
            Karel Piwko Master

            I've spent some time debugging the problem. Now I'm sure that problem does not lie within JSch itself. Most of the time is actually spend in waiting for the report of git push results - that are by default bound to mvn package & deploy & restart.

             

            Even if we have some markers there to skip to build, there is still restart phase. This can be skipped as well via different marker. However, now the most reasonable approach would be to keep using JSch, but instead of git-pushing the deployment, scpy it.

             

            This would be the first interation. Proven it works, I'll keep it as next version of current openshift container implementation. Otherwise, I'll start working the solution described in the first post.

             

            Speaking about AS7/EAP6/WF8, if that happens, it needs to be based on top of stuff created by ALR, where container adaptor for Arquillian is standalone.

            • 3. Re: Arquillian OpenShift refresh plan
              Aslak Knutsen Master

              > Speaking about AS7/EAP6/WF8, if that happens, it needs to be based on top of stuff created by ALR, where container adaptor for Arquillian is standalone.

               

              You would probably need two containers then. One for testing on JBoss App servers, and one for just pure deployment what ever it is. As far as I remember, the original contianer has, or atleast intended to have support for e.g. python.

              • 4. Re: Arquillian OpenShift refresh plan
                Aslak Knutsen Master

                Or possible it will have a optional 'sub container', which could be any 'remote' container.